RFC 7433

A Mechanism for Transporting User-to-User Call Control Information in SIP, January 2015

Canonical URL:
https://www.rfc-editor.org/rfc/rfc7433.txt
File formats:
Plain TextPDF
Status:
PROPOSED STANDARD
Authors:
A. Johnston
J. Rafferty
Stream:
IETF
Source:
cuss (rai)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC7433

Discuss this RFC: Send questions or comments to cuss@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader