RFC 7433: A Mechanism for Transporting User-to-User Call Control Information in SIP
In plain English — editorial summary, not part of the RFC
There is a class of applications that benefit from using SIP to exchange User-to-User Information (UUI) data during session establishment. This information, known as call control UUI data, is a small piece of data inserted by an application initiating the session and utilized by an application accepting the session. The syntax and semantics for the UUI data used by a specific application are defined by a UUI package. This UUI data is opaque to SIP and its function is unrelated to any basic SIP function. This document defines a new SIP header field, User-to-User, to transport UUI data, along with an extension mechanism.
Document record
- Document ID
- RFC7433
- Published
- January 2015
- Authors
- A. Johnston; J. Rafferty
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4233Integrated Services Digital Network (ISDN) Q.921-User Adaptation LayerUpdated
January 2006
- RFC 3903Session Initiation Protocol (SIP) Extension for Event State PublicationUpdated
November 2004
- RFC 3525Gateway Control Protocol Version 1Obsoleted
June 2003
- RFC 3057ISDN Q.921-User Adaptation LayerObsoleted
February 2001
- RFC 3015Megaco Protocol Version 1.0Obsoleted
November 2000
- RFC 2886Megaco ErrataObsoleted
August 2000
- RFC 2885Megaco Protocol version 0.8Obsoleted
August 2000
- RFC 2719Framework Architecture for Signaling TransportCurrent
October 1999
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?