draft-ietf-fecframe-raptor-08.txt   draft-ietf-fecframe-raptor-09.txt 
FEC Framework M. Watson FEC Framework M. Watson
Internet-Draft Netflix Internet-Draft Netflix
Intended status: Standards Track T. Stockhammer Intended status: Standards Track T. Stockhammer
Expires: August 27, 2012 Nomor Research Expires: September 2, 2012 Nomor Research
M. Luby M. Luby
Qualcomm Incorporated Qualcomm Incorporated
February 24, 2012 March 1, 2012
Raptor FEC Schemes for FECFRAME Raptor FEC Schemes for FECFRAME
draft-ietf-fecframe-raptor-08 draft-ietf-fecframe-raptor-09
Abstract Abstract
This document describes Fully-Specified Forward Error Correction This document describes Fully-Specified Forward Error Correction
(FEC) Schemes for the Raptor and RaptorQ codes and their application (FEC) Schemes for the Raptor and RaptorQ codes and their application
to reliable delivery of media streams in the context of FEC to reliable delivery of media streams in the context of FEC
Framework. The Raptor and RaptorQ codes are systematic codes, where Framework. The Raptor and RaptorQ codes are systematic codes, where
a number of repair symbols are generated from a set of source symbols a number of repair symbols are generated from a set of source symbols
and sent in one or more repair flows in addition to the source and sent in one or more repair flows in addition to the source
symbols that are sent to the receiver(s) within a source flow. The symbols that are sent to the receiver(s) within a source flow. The
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 27, 2012. This Internet-Draft will expire on September 2, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
skipping to change at page 3, line 52 skipping to change at page 3, line 52
Information . . . . . . . . . . . . . . . . . . . . . 17 Information . . . . . . . . . . . . . . . . . . . . . 17
8.2.3. Repair packet construction . . . . . . . . . . . . . . 19 8.2.3. Repair packet construction . . . . . . . . . . . . . . 19
8.2.4. Procedures for RTP source flows . . . . . . . . . . . 19 8.2.4. Procedures for RTP source flows . . . . . . . . . . . 19
8.3. FEC Code Specification . . . . . . . . . . . . . . . . . . 19 8.3. FEC Code Specification . . . . . . . . . . . . . . . . . . 19
9. Security Considerations . . . . . . . . . . . . . . . . . . . 19 9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
10. Session Description Protocol (SDP) Signaling . . . . . . . . . 19 10. Session Description Protocol (SDP) Signaling . . . . . . . . . 19
11. Congestion Control Considerations . . . . . . . . . . . . . . 20 11. Congestion Control Considerations . . . . . . . . . . . . . . 20
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
12.1. Registration of FEC Scheme IDs . . . . . . . . . . . . . . 20 12.1. Registration of FEC Scheme IDs . . . . . . . . . . . . . . 20
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
14.1. Normative References . . . . . . . . . . . . . . . . . . . 21 14.1. Normative References . . . . . . . . . . . . . . . . . . . 22
14.2. Informative References . . . . . . . . . . . . . . . . . . 21 14.2. Informative References . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
The FEC Framework [RFC6363] describes a general framework for the use The FEC Framework [RFC6363] describes a general framework for the use
of Forward Error Correction in association with arbitrary packet of Forward Error Correction in association with arbitrary packet
flows. Modeled after the FEC Building Block developed by the IETF flows. Modeled after the FEC Building Block developed by the IETF
Reliable Multicast Transport working group [RFC5052], the FEC Reliable Multicast Transport working group [RFC5052], the FEC
Framework defines the concept of FEC Schemes which provide specific Framework defines the concept of FEC Schemes which provide specific
Forward Error Correction schemes. This document describes six FEC Forward Error Correction schemes. This document describes six FEC
skipping to change at page 9, line 27 skipping to change at page 9, line 27
When used with Raptor codes, this scheme is equivalent to that When used with Raptor codes, this scheme is equivalent to that
specified in [MBMSTS]. specified in [MBMSTS].
6.2. Formats and Codes 6.2. Formats and Codes
6.2.1. FEC Framework Configuration Information 6.2.1. FEC Framework Configuration Information
6.2.1.1. FEC Scheme ID 6.2.1.1. FEC Scheme ID
The value of the FEC Scheme ID for the fully-specified FEC scheme The value of the FEC Scheme ID for the fully-specified FEC scheme
defined in this section is XXX(RFC5053-ARBITRARY) when [RFC5053] is defined in this section is XXX1 when [RFC5053] is used and XXX2 when
used and XXX(RFC6330-ARBITRARY) when [RFC6330] is used, as assigned [RFC6330] is used, as assigned by IANA.
by IANA.
NOTE: To the RFC Editor: please change these XXX notations once
assigned, and remove this NOTE.
6.2.1.2. Scheme-Specific Elements 6.2.1.2. Scheme-Specific Elements
The scheme-specific elements of the FEC Framework Configuration The scheme-specific elements of the FEC Framework Configuration
information for this scheme are as follows: information for this scheme are as follows:
MSBL Value range: A decimal non-negative integer less than 8192 MSBL Value range: A decimal non-negative integer less than 8192
(for Raptor) or 56403 (for RaptorQ), in units of symbols (for Raptor) or 56403 (for RaptorQ), in units of symbols
Encoding Symbol Size Name: "T", Value range: A decimal non- Encoding Symbol Size Name: "T", Value range: A decimal non-
skipping to change at page 14, line 21 skipping to change at page 14, line 21
scheme is equivalent to that specified in [dvbts] for arbitrary scheme is equivalent to that specified in [dvbts] for arbitrary
packet flows. packet flows.
7.2. Formats and Codes 7.2. Formats and Codes
7.2.1. FEC Framework Configuration Information 7.2.1. FEC Framework Configuration Information
7.2.1.1. FEC Scheme ID 7.2.1.1. FEC Scheme ID
The value of the FEC Scheme ID for the fully-specified FEC scheme The value of the FEC Scheme ID for the fully-specified FEC scheme
defined in this section is XXX(RFC5053-OPTIMISED) when [RFC5053] is defined in this section is XXX3 when [RFC5053] is used and XXX4 when
used and XXX(RFC6330-OPTIMISED) when [RFC6330] is used, as assigned [RFC6330] is used, as assigned by IANA.
by IANA.
NOTE: To the RFC Editor: please change these XXX notations once
assigned, and remove this NOTE.
7.2.1.2. FEC Scheme specific information 7.2.1.2. FEC Scheme specific information
See . (Section 6.2.1.2). The MSBL value is one of the values as See . (Section 6.2.1.2). The MSBL value is one of the values as
defined in section . (Section 7.4). defined in section . (Section 7.4).
7.2.2. Source FEC Payload ID 7.2.2. Source FEC Payload ID
See Section 6.2.2. See Section 6.2.2.
skipping to change at page 15, line 43 skipping to change at page 15, line 45
8. Raptor FEC Scheme for a single sequenced flow 8. Raptor FEC Scheme for a single sequenced flow
8.1. Formats and codes 8.1. Formats and codes
8.1.1. FEC Framework Configuration Information 8.1.1. FEC Framework Configuration Information
8.1.1.1. FEC Scheme ID 8.1.1.1. FEC Scheme ID
The value of the FEC Scheme ID for the fully-specified FEC scheme The value of the FEC Scheme ID for the fully-specified FEC scheme
defined in this section is XXX(RFC5053-SINGLE) when [RFC5053] is used defined in this section is XXX5 when [RFC5053] is used and XXX6 when
and XXX(RFC6330-SINGLE) when [RFC6330] is used, as assigned by IANA. [RFC6330] is used, as assigned by IANA.
NOTE: To the RFC Editor: please change these XXX notations once
assigned, and remove this NOTE.
8.1.1.2. Scheme-specific elements 8.1.1.2. Scheme-specific elements
See Section 6.2.1.2 See Section 6.2.1.2
8.1.2. Source FEC Payload ID 8.1.2. Source FEC Payload ID
The Source FEC Payload ID field is not used by this FEC Scheme. The Source FEC Payload ID field is not used by this FEC Scheme.
Source packets are not modified by this FEC Scheme. Source packets are not modified by this FEC Scheme.
skipping to change at page 20, line 35 skipping to change at page 20, line 35
12. IANA Considerations 12. IANA Considerations
12.1. Registration of FEC Scheme IDs 12.1. Registration of FEC Scheme IDs
The value of FEC Scheme IDs is subject to IANA registration. For The value of FEC Scheme IDs is subject to IANA registration. For
general guidelines on IANA considerations as they apply to this general guidelines on IANA considerations as they apply to this
document, refer to [RFC6363]. document, refer to [RFC6363].
This document registers six values in the FEC Framework (FECFRAME) This document registers six values in the FEC Framework (FECFRAME)
FEC Encoding IDs registry as follows: FEC Encoding IDs registry (http://www.iana.org/assignments/
rmt-fec-parameters/rmt-fec-parameters.xml#fecframe-fec-encoding-ids)
o 1 for the Raptor FEC Scheme for Arbitrary Packet Flows (Section 6 as provided in Table 1. Each value refers to a fully-specified FEC
using Raptor [RFC5053]. scheme.
o 2 for the RaptorQ FEC Scheme for Arbitrary Packet Flows (Section 6
using RaptorQ [RFC6330].
o 3 for the Optimised Raptor FEC Scheme for Arbitrary Packet Flows
(Section 7) using Raptor [RFC5053].
o 4 for the Optimised RaptorQ FEC Scheme for Arbitrary Packet Flows NOTE: To the RFC Editor: please change these XXX notations once
(Section 7) using RaptorQ [RFC6330]. assigned, and remove this NOTE.
o 5 for the Raptor FEC Scheme for a single sequence flow (Section 8) +----------+---------------------+----------------------------------+
using Raptor [RFC5053]. | FEC | FEC Scheme | Reference |
| Encoding | Description | |
| ID | | |
+----------+---------------------+----------------------------------+
| XXX1 | Raptor FEC Scheme | Section 6 in this document using |
| | for Arbitrary | [RFC5053] |
| | Packet Flows | |
+----------+---------------------+----------------------------------+
| XXX2 | RaptorQ FEC Scheme | Section 6 in this document using |
| | for Arbitrary | [RFC6330]. |
| | Packet Flows | |
+----------+---------------------+----------------------------------+
| XXX3 | Raptor FEC Scheme | Section 7 in this document using |
| | Optimised for | Raptor [RFC5053]. |
| | Arbitrary Packet | |
| | Flows | |
+----------+---------------------+----------------------------------+
| XXX4 | RaptorQ FEC Scheme | XXX4 for the Optimised RaptorQ |
| | Optimised for | FEC Scheme for Arbitrary Packet |
| | Arbitrary Packet | Flows (Section 7) using RaptorQ |
| | Flows | [RFC6330]. |
+----------+---------------------+----------------------------------+
| XXX5 | Raptor FEC Scheme | XXX5 for the Raptor FEC Scheme |
| | for a single | for a single sequence flow |
| | sequence flow | (Section 8) using Raptor |
| | | [RFC5053]. |
+----------+---------------------+----------------------------------+
| XXX6 | RaptorQ FEC Scheme | XXX6 for the RaptorQ FEC Scheme |
| | for a single | for a single sequence flow |
| | sequence flow | (Section 8) using RaptorQ |
| | | [RFC6330]. |
+----------+---------------------+----------------------------------+
o 6 for the RaptorQ FEC Scheme for a single sequence flow Table 1: FEC Framework (FECFRAME) FEC Encoding IDs
(Section 8) using RaptorQ [RFC6330].
13. Acknowledgements 13. Acknowledgements
Thanks are due to Ali C. Begen and David Harrington for thorough Thanks are due to Ali C. Begen and David Harrington for thorough
review of earlier draft versions of this document. review of earlier draft versions of this document.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC6363] Watson, M., Begen, A., and V. Roca, "Forward Error [RFC6363] Watson, M., Begen, A., and V. Roca, "Forward Error
Correction (FEC) Framework", RFC 6363, October 2011. Correction (FEC) Framework", RFC 6363, October 2011.
[RFC5053] Luby, M., Shokrollahi, A., Watson, M., and T. Stockhammer, [RFC5053] Luby, M., Shokrollahi, A., Watson, M., and T. Stockhammer,
"Raptor Forward Error Correction Scheme for Object "Raptor Forward Error Correction Scheme for Object
Delivery", RFC 5053, October 2007. Delivery", RFC 5053, October 2007.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
 End of changes. 13 change blocks. 
32 lines changed or deleted 62 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/