RTP Payload Format for Generic Forward Error Correction
RFC 5109, “RTP Payload Format for Generic Forward Error Correction”, is a Proposed Standard document published in December 2007 by A. Li. It obsoletes RFC 2733, RFC 3009. The canonical text is published by the RFC Editor.
Abstract
This document specifies a payload format for generic Forward Error Correction (FEC) for media data encapsulated in RTP. It is based on the exclusive-or (parity) operation. The payload format described in this document allows end systems to apply protection using various protection lengths and levels, in addition to using various protection group sizes to adapt to different media and channel characteristics. It enables complete recovery of the protected packets or partial recovery of the critical parts of the payload depending on the packet loss situation. This scheme is completely compatible with non-FEC-capable hosts, so the receivers in a multicast group that do not implement FEC can still work by simply ignoring the protection data. This specification obsoletes RFC 2733 and RFC 3009. The FEC specified in this document is not backward compatible with RFC 2733 and RFC 3009. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5109 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5105 ENUM Validation Token Format Definition
- RFC 5096 Mobile IPv6 Experimental Messages
- RFC 5095 Deprecation of Type 0 Routing Headers in IPv6
- RFC 5094 Mobile IPv6 Vendor Specific Option
- RFC 5093 BT's eXtended Network Quality RTP Control Protocol Extended Reports
- RFC 5092 IMAP URL Scheme
- RFC 5091 Identity-Based Cryptography Standard #1: Supersingular Curve Implementations of the BF and BB1 Cryptosystems
- RFC 5131 A MIB Textual Convention for Language Tags