RFC 8828: WebRTC IP Address Handling Requirements
In plain English — editorial summary, not part of the RFC
This document provides information and requirements for how IP addresses should be handled by Web Real-Time Communication (WebRTC) implementations.
Document record
- Document ID
- RFC8828
- Published
- January 2021
- Authors
- J. Uberti; G. Shieh
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9458Oblivious HTTPCurrent
January 2024
- RFC 9666Area Proxy for IS-ISCurrent
October 2024
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 9209The Proxy-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9298Proxying UDP in HTTPUpdated
August 2022
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
- RFC 9484Proxying IP in HTTPCurrent
October 2023
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?