RFC 6682: RTP Payload Format for Raptor Forward Error Correction (FEC)
In plain English — editorial summary, not part of the RFC
This document specifies an RTP payload format for the Forward Error Correction (FEC) repair data produced by the Raptor FEC Schemes. Raptor FEC Schemes are specified for use with the IETF FEC Framework that supports the transport of repair data over both UDP and RTP. This document specifies the payload format that is required for the use of RTP to carry Raptor repair flows. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6682
- Published
- August 2012
- Authors
- M. Watson; T. Stockhammer; M. Luby
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 18
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6681Raptor Forward Error Correction (FEC) Schemes for FECFRAMECurrent
August 2012
- RFC 6683Guidelines for Implementing Digital Video Broadcasting - IPTV (DVB-IPTV) Application-Layer Hybrid Forward Error Correction (FEC) ProtectionCurrent
August 2012
- RFC 6695Methods to Convey Forward Error Correction (FEC) Framework Configuration InformationCurrent
August 2012
- RFC 6663Requirements for Signaling of Pre-Congestion Information in a Diffserv DomainCurrent
July 2012
- RFC 6662Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of OperationCurrent
July 2012
- RFC 6661Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Controlled Load (CL) Mode of OperationCurrent
July 2012
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 6646DECoupled Application Data Enroute (DECADE) Problem StatementCurrent
July 2012
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?