RTP Payload Format for Raptor Forward Error Correction (FEC)
RFC 6682
|
| Document |
Type |
|
RFC - Proposed Standard
(August 2012; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-watson-fecframe-rtp-raptor
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 6682 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Martin Stiemerling
|
|
IESG note |
|
Greg Shepherd (gjshep@gmail.com) is the document shepherd.
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force (IETF) M. Watson
Request for Comments: 6682 Netflix
Category: Standards Track T. Stockhammer
ISSN: 2070-1721 Nomor Research
M. Luby
Qualcomm Incorporated
August 2012
RTP Payload Format for Raptor Forward Error Correction (FEC)
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by
the Internet Engineering Steering Group (IESG). Further
information on Internet Standards is available in Section 2 of
RFC 5741.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6682.
Watson, et al. Standards Track [Page 1]
RFC 6682 RTP Payload Format for Raptor August 2012
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................3
2. Conventions, Definitions, and Acronyms ..........................3
3. Media Format Background .........................................3
4. Payload Format for FEC Repair Packets ...........................4
4.1. RTP Header Usage ...........................................4
4.2. Payload Header .............................................5
4.3. Payload Data ...............................................5
5. Congestion Control Considerations ...............................5
6. Media Types .....................................................5
6.1. Registration of the 'application/raptorfec' Media Type .....5
6.1.1. Media Type Definition ...............................5
6.2. Registration of the 'video/raptorfec' Media Type ...........7
6.2.1. Media Type Definition ...............................7
6.3. Registration of the 'audio/raptorfec' Media Type ...........8
6.3.1. Media Type Definition ...............................8
6.4. Registration of the 'text/raptorfec' Media Type ...........10
6.4.1. Media Type Definition ..............................10
7. Mapping to the Session Description Protocol (SDP) ..............12
8. Offer/Answer Considerations ....................................12
9. Declarative SDP Considerations .................................13
10. Repair Flow Generation and Recovery Procedures ................13
10.1. Overview .................................................13
10.2. Repair Packet Construction ...............................14
10.3. Usage of RTCP ............................................14
10.4. Source Packet Reconstruction .............................14
11. Session Description Protocol (SDP) Example ....................14
12. IANA Considerations ...........................................15
13. Security Considerations .......................................15
14. References ....................................................16
14.1. Normative References .....................................16
14.2. Informative References ...................................17
Watson, et al. Standards Track [Page 2]
RFC 6682 RTP Payload Format for Raptor August 2012
1. Introduction
The FEC Framework [RFC6363] defines a general framework for the use
of Forward Error Correction in association with arbitrary packet
Show full document text