RFC 6567: Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIP
In plain English — editorial summary, not part of the RFC
This document introduces the transport of call control User-to-User Information (UUI) using the Session Initiation Protocol (SIP) and develops several requirements for a new SIP mechanism. Some SIP sessions are established by or related to a non-SIP application. This application may have information that needs to be transported between the SIP User Agents during session establishment. In addition to interworking with the Integrated Services Digital Network (ISDN) UUI Service, this extension will also be used for native SIP endpoints requiring application UUI. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6567
- Published
- April 2012
- Authors
- A. Johnston; L. Liess
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6623IANA Registry for MEDIACTRL Interactive Voice Response Control PackageCurrent
May 2012
- RFC 6505A Mixer Control Package for the Media Control Channel FrameworkCurrent
March 2012
- RFC 6504Centralized Conferencing Manipulation Protocol (CCMP) Call Flow ExamplesCurrent
March 2012
- RFC 6503Centralized Conferencing Manipulation ProtocolCurrent
March 2012
- RFC 6502Conference Event Package Data Format Extension for Centralized Conferencing (XCON)Current
March 2012
- RFC 6501Conference Information Data Model for Centralized Conferencing (XCON)Current
March 2012
- RFC 6447Filtering Location Notifications in the Session Initiation Protocol (SIP)Current
January 2012
- RFC 6714Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)Current
August 2012
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?