RFC 8839: Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)
In plain English — editorial summary, not part of the RFC
This document describes Session Description Protocol (SDP) Offer/Answer procedures for carrying out Interactive Connectivity Establishment (ICE) between the agents. This document obsoletes RFCs 5245 and 6336.
Document record
- Document ID
- RFC8839
- Published
- January 2021
- Authors
- M. Petit-Huguenin; S. Nandakumar; C. Holmberg; A. Keränen; R. Shpount
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 38
- Also known as
- —
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8838Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) ProtocolUpdated
January 2021
- RFC 8840A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)Updated
January 2021
- RFC 8841Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) TransportCurrent
January 2021
- RFC 8842Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)Updated
January 2021
- RFC 8843Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Obsoleted
January 2021
- RFC 8844Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)Current
January 2021
- RFC 8845Framework for Telepresence Multi-StreamsCurrent
January 2021
- RFC 8846An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data ModelCurrent
January 2021
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?