RFC 5057: Multiple Dialog Usages in the Session Initiation Protocol

Several methods in the Session Initiation Protocol (SIP) can create an association between endpoints known as a dialog. Some of these methods can also create…

Read RFC 5057 on the RFC Editor

Outgoing relationships (10 related RFCs)

Informative reference — RFC 3261: SIP: Session Initiation Protocol
Informative reference — RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification
Informative reference — RFC 3515: The Session Initiation Protocol (SIP) Refer Method
Informative reference — RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers
Informative reference — RFC 3903: Session Initiation Protocol (SIP) Extension for Event State Publication
Informative reference — RFC 3891: The Session Initiation Protocol (SIP) "Replaces" Header
Informative reference — RFC 4538: Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)
Informative reference — RFC 4730: A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML)
Informative reference — RFC 3911: The Session Initiation Protocol (SIP) "Join" Header
Informative reference — RFC 4488: Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription

Incoming relationships (7 related RFCs)

Informatively referenced by — RFC 6665: SIP-Specific Event Notification
Informatively referenced by — RFC 7614: Explicit Subscriptions for the REFER Method
Informatively referenced by — RFC 7647: Clarifications for the Use of REFER with RFC 6665
Informatively referenced by — RFC 8197: A SIP Response Code for Unwanted Calls
Informatively referenced by — RFC 5079: Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 5407: Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 6228: Session Initiation Protocol (SIP) Response Code for Indication of Terminated Dialog