RFC 8681: Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Schemes for FECFRAME
In plain English — editorial summary, not part of the RFC
This document describes two fully specified Forward Erasure Correction (FEC) Schemes for Sliding Window Random Linear Codes (RLC), one for RLC over the Galois Field (a.k.a., Finite Field) GF(2), a second one for RLC over the Galois Field GF(2^8), each time with the possibility of controlling the code density. They can protect arbitrary media streams along the lines defined by FECFRAME extended to Sliding Window FEC Codes. These Sliding Window FEC Codes rely on an encoding window that slides over the source symbols, generating new repair symbols whenever needed. Compared to block FEC codes, these Sliding Window FEC Codes offer key advantages with real-time flows in terms of reduced FEC-related latency while often providing improved packet erasure recovery capabilities.
Document record
- Document ID
- RFC8681
- Published
- January 2020
- Authors
- V. Roca; B. Teibi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8680Forward Error Correction (FEC) Framework Extension to Sliding Window CodesCurrent
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 8513A YANG Data Model for Dual-Stack Lite (DS-Lite)Current
January 2019
- RFC 9655Egress Validation in Label Switched Path Ping and Traceroute MechanismsCurrent
November 2024
- RFC 7585Dynamic Peer Discovery for RADIUS/TLS and RADIUS/DTLS Based on the Network Access Identifier (NAI)Current
October 2015
- RFC 6971Depth-First Forwarding (DFF) in Unreliable NetworksCurrent
June 2013
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?