RFC 8122: Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)
In plain English — editorial summary, not part of the RFC
This document specifies how to establish secure connection-oriented media transport sessions over the Transport Layer Security (TLS) protocol using the Session Description Protocol (SDP). It defines the SDP protocol identifier, 'TCP/TLS'. It also defines the syntax and semantics for an SDP 'fingerprint' attribute that identifies the certificate that will be presented for the TLS session. This mechanism allows media transport over TLS connections to be established securely, so long as the integrity of session descriptions is assured. This document obsoletes RFC 4572 by clarifying the usage of multiple fingerprints.
Document record
- Document ID
- RFC8122
- Published
- March 2017
- Authors
- J. Lennox; C. Holmberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 18
- 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 8858Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)Current
January 2021
- RFC 8035Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP MultiplexingCurrent
November 2016
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
- RFC 6337Session Initiation Protocol (SIP) Usage of the Offer/Answer ModelCurrent
August 2011
- RFC 7261Offer/Answer Considerations for G723 Annex A and G729 Annex BCurrent
May 2014
- RFC 8373Negotiating Human Language in Real-Time CommunicationsUpdated
May 2018
- RFC 7825A Network Address Translator (NAT) Traversal Mechanism for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
December 2016
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?