RFC 7879: DTLS-SRTP Handling in SIP Back-to-Back User Agents
In plain English — editorial summary, not part of the RFC
Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs) exist on the signaling and media paths between the endpoints. This document describes the behavior of B2BUAs when Secure Real-time Transport (SRTP) security context is set up with the Datagram Transport Layer Security (DTLS) protocol.
Document record
- Document ID
- RFC7879
- Published
- May 2016
- Authors
- R. Ravindranath; T. Reddy; G. Salgueiro; V. Pascual; P. Ravindran
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7989End-to-End Session Identification in IP-Based Multimedia Communication NetworksCurrent
October 2016
- RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
- RFC 7702Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): GroupchatCurrent
December 2015
- RFC 7621A Clarification on the Use of Globally Routable User Agent URIs (GRUUs) in the SIP Event Notification FrameworkCurrent
August 2015
- RFC 7573Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat SessionsCurrent
June 2015
- RFC 7092A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User AgentsCurrent
December 2013
- RFC 9409The 'sip-trunking-capability' Link Relation TypeCurrent
July 2023
- RFC 6357Design Considerations for Session Initiation Protocol (SIP) Overload ControlCurrent
August 2011
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?