datatracker.ietf.org
Sign in
Version 5.9.0, 2014-12-18
Report a bug

The Generalized Object Encoding (GOE) LDPC-Staircase FEC Scheme
draft-roca-rmt-goe-ldpc-01

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-02-01 (latest revision 2012-07-31)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-roca-rmt-goe-ldpc-01.txt

Abstract

This document describes a Generalized Object Encoding (GOE) FEC Scheme for the protection of one or multiple objects, in the context of a Content Delivery Protocol (CDP) like FLUTE/ALC, FCAST/ALC or FCAST/NORM. Unlike [RFC5052], the GOE approach [GOE] decouples the definition of Generalized Objects over which FEC encoding takes place homogeneously, from the natural source object boundaries. This separation enables either an Unequal Erasure Protection (UEP) of different portions of a given source object, or an efficient and global protection of a set of potentially small files, depending on the way the Generalized Objects are defined. The present document defines the GOE LDPC-Staircase FEC Scheme, i.e., the GOE version of the FEC Encoding ID 3 (LDPC-Staircase) defined in [RFC5170] with the further restriction that the number of encoding symbols per group (i.e., the number of symbols sent in the same packet) MUST be equal to 1 (G=1). This document does not change the LDPC-Staircase code definition, and therefore it inherits most of [RFC5170]. It only modifies the FEC Payload ID and FEC OTI, i.e., it addresses the problem of UEP and efficient file bundle protection by means of pure signaling approach.

Authors

Vincent Roca <vincent.roca@inria.fr>
Aline Roumy <aline.roumy@inria.fr>
Bessem Sayadi <bessem.sayadi@alcatel-lucent.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)