Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Author:

R. Sparks

Stream:

IETF

Source:

sipping (rai)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5057

Discuss this RFC: Send questions or comments to the mailing listsipping@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5057

Abstract

Several methods in the Session Initiation Protocol (SIP) can createan association between endpoints known as a dialog. Some of thesemethods can also create a different, but related, association withinan existing dialog. These multiple associations, or dialog usages,require carefully coordinated processing as they have independentlife-cycles, but share common dialog state. Processing multipledialog usages correctly is not completely understood. What isunderstood is difficult to implement.

This memo argues that multiple dialog usages should be avoided. Itdiscusses alternatives to their use and clarifies essential behaviorfor elements that cannot currently avoid them.

This is an informative document and makes no normative statements ofany kind. This memo provides information for the Internet community.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.