RFC 8873: Message Session Relay Protocol (MSRP) over Data Channels
In plain English — editorial summary, not part of the RFC
This document specifies how a Web Real-Time Communication (WebRTC) data channel can be used as a transport mechanism for the Message Session Relay Protocol (MSRP) and how the Session Description Protocol (SDP) offer/answer mechanism can be used to negotiate such a data channel, referred to as an MSRP data channel. Two network configurations are supported: the connection of two MSRP data channel endpoints; and a gateway configuration, which connects an MSRP data channel endpoint with an MSRP endpoint that uses either TCP or TLS. This document updates RFC 4975.
Document record
- Document ID
- RFC8873
- Published
- January 2021
- Authors
- JM. Recio; C. Holmberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 17
- Also known as
- —
- Updates:
- RFC 4975
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8865T.140 Real-Time Text Conversation over WebRTC Data ChannelsCurrent
January 2021
- RFC 8858Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)Current
January 2021
- RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
- RFC 8844Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)Current
January 2021
- RFC 8836Congestion Control Requirements for Interactive Real-Time MediaCurrent
January 2021
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
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?