RFC 8680: Forward Error Correction (FEC) Framework Extension to Sliding Window Codes
In plain English — editorial summary, not part of the RFC
RFC 6363 describes a framework for using Forward Error Correction (FEC) codes to provide protection against packet loss. The framework supports applying FEC to arbitrary packet flows over unreliable transport and is primarily intended for real-time, or streaming, media. However, FECFRAME as per RFC 6363 is restricted to block FEC codes. This document updates RFC 6363 to support FEC codes based on a sliding encoding window, in addition to block FEC codes, in a backward-compatible way. During multicast/broadcast real-time content delivery, the use of sliding window codes significantly improves robustness in harsh environments, with less repair traffic and lower FEC-related added latency.
Document record
- Document ID
- RFC8680
- Published
- January 2020
- Authors
- V. Roca; A. Begen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 19
- Also known as
- —
- Updates:
- RFC 6363
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8681Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Schemes for FECFRAMECurrent
January 2020
- RFC 8854WebRTC Forward Error Correction RequirementsCurrent
January 2021
- RFC 9002QUIC Loss Detection and Congestion ControlCurrent
May 2021
- RFC 8627RTP Payload Format for Flexible Forward Error Correction (FEC)Current
July 2019
- RFC 9655Egress Validation in Label Switched Path Ping and Traceroute MechanismsCurrent
November 2024
- RFC 6683Guidelines for Implementing Digital Video Broadcasting - IPTV (DVB-IPTV) Application-Layer Hybrid Forward Error Correction (FEC) ProtectionCurrent
August 2012
- RFC 6659Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) MethodCurrent
July 2012
- RFC 6178Label Edge Router Forwarding of IPv4 Option PacketsCurrent
March 2011
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?