RFC 7433: A Mechanism for Transporting User-to-User Call Control Information in SIP

There is a class of applications that benefit from using SIP to exchange User-to-User Information (UUI) data during session establishment. This information,…

Read RFC 7433 on the RFC Editor

Outgoing relationships (14 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 3261: SIP: Session Initiation Protocol
Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 3840: Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
Normative reference — RFC 4474: Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)
Normative reference — RFC 3891: The Session Initiation Protocol (SIP) "Replaces" Header
Normative reference — RFC 4916: Connected Identity in the Session Initiation Protocol (SIP)
Informative reference — RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
Informative reference — RFC 4475: Session Initiation Protocol (SIP) Torture Test Messages
Informative reference — RFC 6086: Session Initiation Protocol (SIP) INFO Method and Package Framework
Informative reference — RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area
Informative reference — RFC 3372: Session Initiation Protocol for Telephones (SIP-T): Context and Architectures
Informative reference — RFC 6567: Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIP