datatracker.ietf.org
Sign in
Version 5.6.3, 2014-09-19
Report a bug

The Generalized Object Encoding (GOE) Approach for the Forward Erasure Correction (FEC) Protection of Objects and its Application to Reed- Solomon Codes over GF(2^^8)
draft-roca-rmt-goe-fec-02

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-fec-02.txt

Abstract

This document describes a Generalized Object Encoding (GOE) approach 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 first of all introduces the GOE approach. Then it defines the GOE Reed-Solomon FEC Scheme for the particular case of Reed-Solomon codes over GF(2^^8) and no encoding symbol group, the GOE equivalent to FEC Encoding ID 5 defined in RFC5510.

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)