RFC 8831: WebRTC Data Channels
In plain English — editorial summary, not part of the RFC
The WebRTC framework specifies protocol support for direct, interactive, rich communication using audio, video, and data between two peers' web browsers. This document specifies the non-media data transport aspects of the WebRTC framework. It provides an architectural overview of how the Stream Control Transmission Protocol (SCTP) is used in the WebRTC context as a generic transport service that allows web browsers to exchange generic data from peer to peer.
Document record
- Document ID
- RFC8831
- Published
- January 2021
- Authors
- R. Jesup; S. Loreto; M. Tüxen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8832WebRTC Data Channel Establishment ProtocolCurrent
January 2021
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 8833Application-Layer Protocol Negotiation (ALPN) for WebRTCCurrent
January 2021
- RFC 8834Media Transport and Use of RTP in WebRTCCurrent
January 2021
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 8827WebRTC Security ArchitectureCurrent
January 2021
- RFC 8835Transports for WebRTCCurrent
January 2021
- RFC 8826Security Considerations for WebRTCCurrent
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?