RFC 6695: Methods to Convey Forward Error Correction (FEC) Framework Configuration Information
In plain English — editorial summary, not part of the RFC
The Forward Error Correction (FEC) Framework document (RFC 6363) defines the FEC Framework Configuration Information necessary for the FEC Framework operation. This document describes how to use signaling protocols such as the Session Announcement Protocol (SAP), the Session Initiation Protocol (SIP), the Real Time Streaming Protocol (RTSP), etc. for determining and communicating the configuration information between sender(s) and receiver(s). This document doesn't define any new signaling protocol. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6695
- Published
- August 2012
- Authors
- R. Asati
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 15
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6683Guidelines for Implementing Digital Video Broadcasting - IPTV (DVB-IPTV) Application-Layer Hybrid Forward Error Correction (FEC) ProtectionCurrent
August 2012
- RFC 6682RTP Payload Format for Raptor Forward Error Correction (FEC)Current
August 2012
- RFC 6681Raptor Forward Error Correction (FEC) Schemes for FECFRAMECurrent
August 2012
- RFC 6726FLUTE - File Delivery over Unidirectional TransportCurrent
November 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
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?