RFC 8826: Security Considerations for WebRTC
In plain English — editorial summary, not part of the RFC
WebRTC is a protocol suite for use with real-time applications that can be deployed in browsers -- "real-time communication on the Web". This document defines the WebRTC threat model and analyzes the security threats of WebRTC in that model.
Document record
- Document ID
- RFC8826
- Published
- January 2021
- Authors
- E. Rescorla
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 21
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8827WebRTC Security ArchitectureCurrent
January 2021
- RFC 8825Overview: Real-Time Protocols for Browser-Based ApplicationsCurrent
January 2021
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 8831WebRTC Data ChannelsCurrent
January 2021
- RFC 8832WebRTC Data Channel Establishment ProtocolCurrent
January 2021
- RFC 8833Application-Layer Protocol Negotiation (ALPN) for WebRTCCurrent
January 2021
- RFC 8834Media Transport and Use of RTP in 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?