RFC 8854: WebRTC Forward Error Correction Requirements
In plain English — editorial summary, not part of the RFC
This document provides information and requirements for the use of Forward Error Correction (FEC) by WebRTC implementations.
Document record
- Document ID
- RFC8854
- Published
- January 2021
- Authors
- J. Uberti
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5576Source-Specific Media Attributes in the Session Description Protocol (SDP)Current
June 2009
- RFC 2733An RTP Payload Format for Generic Forward Error CorrectionObsoleted
December 1999
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 8888RTP Control Protocol (RTCP) Feedback for Congestion ControlCurrent
January 2021
- RFC 9002QUIC Loss Detection and Congestion ControlCurrent
May 2021
- RFC 8681Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Schemes for FECFRAMECurrent
January 2020
- RFC 8680Forward Error Correction (FEC) Framework Extension to Sliding Window CodesCurrent
January 2020
- 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?