RFC 5510: Reed-Solomon Forward Error Correction (FEC) Schemes
In plain English — editorial summary, not part of the RFC
This document describes a Fully-Specified Forward Error Correction (FEC) Scheme for the Reed-Solomon FEC codes over GF(2^^m), where m is in {2..16}, and its application to the reliable delivery of data objects on the packet erasure channel (i.e., a communication path where packets are either received without any corruption or discarded during transmission). This document also describes a Fully-Specified FEC Scheme for the special case of Reed-Solomon codes over GF(2^^8) when there is no encoding symbol group. Finally, in the context of the Under-Specified Small Block Systematic FEC Scheme (FEC Encoding ID 129), this document assigns an FEC Instance ID to the special case of Reed-Solomon codes over GF(2^^8). Reed-Solomon codes belong to the class of Maximum Distance Separable (MDS) codes, i.e., they enable a receiver to recover the k source symbols from any set of k received symbols. The schemes described here are compatible with the implementation from Luigi Rizzo. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5510
- Published
- April 2009
- Authors
- J. Lacan; V. Roca; J. Peltotalo; S. Peltotalo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5508NAT Behavioral Requirements for ICMPUpdated
April 2009
- RFC 5525Reliable Server Pooling MIB Module DefinitionCurrent
April 2009
- RFC 5559Pre-Congestion Notification (PCN) ArchitectureCurrent
June 2009
- RFC 5445Basic Forward Error Correction (FEC) SchemesCurrent
March 2009
- RFC 5595The Datagram Congestion Control Protocol (DCCP) Service CodesUpdated
September 2009
- RFC 5596Datagram Congestion Control Protocol (DCCP) Simultaneous-Open Technique to Facilitate NAT/Middlebox TraversalCurrent
September 2009
- RFC 5597Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control ProtocolCurrent
September 2009
- RFC 5401Multicast Negative-Acknowledgment (NACK) Building BlocksCurrent
November 2008
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?