RFC 5850: A Call Control and Multi-Party Usage Framework for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document defines a framework and the requirements for call control and multi-party usage of the Session Initiation Protocol (SIP). To enable discussion of multi-party features and applications, we define an abstract call model for describing the media relationships required by many of these. The model and actions described here are specifically chosen to be independent of the SIP signaling and/or mixing approach chosen to actually set up the media relationships. In addition to its dialog manipulation aspect, this framework includes requirements for communicating related information and events such as conference and session state and session history. This framework also describes other goals that embody the spirit of SIP applications as used on the Internet such as the definition of primitives (not services), invoker and participant oriented primitives, signaling and mixing model independence, and others. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5850
- Published
- May 2010
- Authors
- R. Mahy; R. Sparks; J. Rosenberg; D. Petrie; A. Johnston
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 44
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5589Session Initiation Protocol (SIP) Call Control - TransferCurrent
June 2009
- RFC 5359Session Initiation Protocol Service ExamplesCurrent
October 2008
- RFC 3892The Session Initiation Protocol (SIP) Referred-By MechanismUpdated
September 2004
- RFC 3891The Session Initiation Protocol (SIP) "Replaces" HeaderCurrent
September 2004
- RFC 3725Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)Current
April 2004
- RFC 8076A Usage for Shared Resources in RELOAD (ShaRe)Current
March 2017
- RFC 8723Double Encryption Procedures for the Secure Real-Time Transport Protocol (SRTP)Current
April 2020
- RFC 2879Content Feature Schema for Internet Fax (V2)Current
August 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?