RFC 6801: Pseudo Content Delivery Protocol (CDP) for Protecting Multiple Source Flows in the Forward Error Correction (FEC) Framework
In plain English — editorial summary, not part of the RFC
This document provides a pseudo Content Delivery Protocol (CDP) to protect multiple source flows with one or more repair flows based on the Forward Error Correction (FEC) Framework and the Session Description Protocol (SDP) elements defined for the framework. The purpose of the document is not to provide a full-fledged protocol but to show how the defined framework and SDP elements can be combined together to implement a CDP. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6801
- Published
- November 2012
- Authors
- U. Kozat; A. Begen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6789Congestion Exposure (ConEx) Concepts and Use CasesCurrent
December 2012
- RFC 6816Simple Low-Density Parity Check (LDPC) Staircase Forward Error Correction (FEC) Scheme for FECFRAMECurrent
December 2012
- RFC 6817Low Extra Delay Background Transport (LEDBAT)Current
December 2012
- RFC 6824TCP Extensions for Multipath Operation with Multiple AddressesObsoleted
January 2013
- RFC 6773DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT TraversalCurrent
November 2012
- RFC 6865Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAMECurrent
February 2013
- RFC 6726FLUTE - File Delivery over Unidirectional TransportCurrent
November 2012
- RFC 6888Common Requirements for Carrier-Grade NATs (CGNs)Current
April 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?