RFC 7092: A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents

In many SIP deployments, SIP entities exist in the SIP signaling path between the originating and final terminating endpoints, which go beyond the definition…

Read RFC 7092 on the RFC Editor

Incoming relationships (8 related RFCs)

Normatively referenced by — RFC 7584: Session Traversal Utilities for NAT (STUN) Message Handling for SIP Back-to-Back User Agents (B2BUAs)
Informatively referenced by — RFC 8811: DDoS Open Threat Signaling (DOTS) Architecture
Informatively referenced by — RFC 7879: DTLS-SRTP Handling in SIP Back-to-Back User Agents
Informatively referenced by — RFC 8873: Message Session Relay Protocol (MSRP) over Data Channels
Informatively referenced by — RFC 7989: End-to-End Session Identification in IP-Based Multimedia Communication Networks
Informatively referenced by — RFC 8079: Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)
Informatively referenced by — RFC 8688: A Session Initiation Protocol (SIP) Response Code for Rejected Calls
Informatively referenced by — RFC 10006: Automatic SIP Trunking and Peering