RFC 7983: Multiplexing Scheme Updates for Secure Real-time Transport Protocol (SRTP) Extension for Datagram Transport Layer Security (DTLS)
In plain English — editorial summary, not part of the RFC
This document defines how Datagram Transport Layer Security (DTLS), Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP), Session Traversal Utilities for NAT (STUN), Traversal Using Relays around NAT (TURN), and ZRTP packets are multiplexed on a single receiving socket. It overrides the guidance from RFC 5764 ("SRTP Extension for DTLS"), which suffered from four issues described and fixed in this document. This document updates RFC 5764.
Document record
- Document ID
- RFC7983
- Published
- September 2016
- Authors
- M. Petit-Huguenin; G. Salgueiro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 13
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7635Session Traversal Utilities for NAT (STUN) Extension for Third-Party AuthorizationCurrent
August 2015
- RFC 8656Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Current
February 2020
- RFC 6156Traversal Using Relays around NAT (TURN) Extension for IPv6Obsoleted
April 2011
- RFC 6062Traversal Using Relays around NAT (TURN) Extensions for TCP AllocationsCurrent
November 2010
- RFC 5766Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Obsoleted
April 2010
- RFC 5389Session Traversal Utilities for NAT (STUN)Obsoleted
October 2008
- RFC 8470Using Early Data in HTTPCurrent
September 2018
- RFC 3436Transport Layer Security over Stream Control Transmission ProtocolUpdated
December 2002
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?