Skip to main content

Multiple Dialog Usages in the Session Initiation Protocol
RFC 5057

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Several methods in the Session Initiation Protocol (SIP) can create an association between endpoints known as …
Received changes through RFC Editor sync (changed abstract to '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 a different, but related, association within an existing dialog. These multiple associations, or dialog usages, require carefully coordinated processing as they have independent life-cycles, but share common dialog state. Processing multiple dialog usages correctly is not completely understood. What is understood is difficult to implement.

This memo argues that multiple dialog usages should be avoided. It discusses alternatives to their use and clarifies essential behavior for elements that cannot currently avoid them.

This is an informative document and makes no normative statements of any kind. This memo provides information for the Internet community.')
2015-10-14
(System) Notify list changed from sipping-chairs@ietf.org to (None)
2007-11-07
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2007-11-07
Amy Vezza [Note]: 'RFC 5057' added by Amy Vezza
2007-11-06
(System) RFC published