Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAME
draft-ietf-fecframe-simple-rs-04
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (fecframe WG)
|
|
Authors |
|
Vincent Roca
,
Mathieu Cunche
,
Jerome Lacan
,
Amine Bouabdallah
,
Kazuhisa Matsuzono
|
|
Last updated |
|
2012-10-25
(latest revision 2012-10-03)
|
|
Stream |
|
Internent Engineering Task Force (IETF)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
IESG |
IESG state |
|
Waiting for AD Go-Ahead::Revised I-D Needed
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Martin Stiemerling
|
|
IESG note |
|
Greg Shepherd (gjshep@gmail.com) is the document shepherd
|
|
Send notices to |
|
fecframe-chairs@tools.ietf.org, draft-ietf-fecframe-simple-rs@tools.ietf.org
|
FecFrame V. Roca
Internet-Draft INRIA
Intended status: Standards Track M. Cunche
Expires: April 6, 2013 INSA-Lyon/INRIA
J. Lacan
A. Bouabdallah
ISAE, Univ. of Toulouse
K. Matsuzono
Keio University
October 3, 2012
Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAME
draft-ietf-fecframe-simple-rs-04
Abstract
This document describes a fully-specified simple FEC scheme for Reed-
Solomon codes over GF(2^^m), with 2 <= m <= 16, that can be used to
protect arbitrary media streams along the lines defined by the
FECFRAME framework. Reed-Solomon codes belong to the class of
Maximum Distance Separable (MDS) codes which means they offer optimal
protection against packet erasures. They are also systematic codes,
which means that the source symbols are part of the encoding symbols.
The price to pay is a limit on the maximum source block size, on the
maximum number of encoding symbols, and a computational complexity
higher than that of LDPC codes for instance.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 6, 2013.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
Roca, et al. Expires April 6, 2013 [Page 1]
Internet-Draft Simple Reed-Solomon FEC Scheme October 2012
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Definitions Notations and Abbreviations . . . . . . . . . . . 5
3.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Notations . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 8
4. Common Procedures Related to the ADU Block and Source
Block Creation . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Restrictions . . . . . . . . . . . . . . . . . . . . . . . 8
4.2. ADU Block Creation . . . . . . . . . . . . . . . . . . . . 8
4.3. Source Block Creation . . . . . . . . . . . . . . . . . . 9
5. Simple Reed-Solomon FEC Scheme over GF(2^^m) for Arbitrary
ADU Flows . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.1. Formats and Codes . . . . . . . . . . . . . . . . . . . . 11
5.1.1. FEC Framework Configuration Information . . . . . . . 11
5.1.2. Explicit Source FEC Payload ID . . . . . . . . . . . . 13
5.1.3. Repair FEC Payload ID . . . . . . . . . . . . . . . . 14
5.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . . 15
5.3. FEC Code Specification . . . . . . . . . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
6.1. Attacks Against the Data Flow . . . . . . . . . . . . . . 16
6.1.1. Access to Confidential Content . . . . . . . . . . . . 16
6.1.2. Content Corruption . . . . . . . . . . . . . . . . . . 16
6.2. Attacks Against the FEC Parameters . . . . . . . . . . . . 16
6.3. When Several Source Flows are to be Protected Together . . 17
6.4. Baseline Secure FEC Framework Operation . . . . . . . . . 18
Show full document text