[Rmt] RFC 5510 on Reed-Solomon Forward Error Correction (FEC) Schemes

rfc-editor@rfc-editor.org Tue, 28 April 2009 23:56 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: rmt@core3.amsl.com
Delivered-To: rmt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCEAC3A6BA6; Tue, 28 Apr 2009 16:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.923
X-Spam-Level:
X-Spam-Status: No, score=-16.923 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0KaBUGd5ax6e; Tue, 28 Apr 2009 16:56:10 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 82E2B3A6C7F; Tue, 28 Apr 2009 16:56:03 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id CEB7A293E4C; Tue, 28 Apr 2009 16:54:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090428235439.CEB7A293E4C@bosco.isi.edu>
Date: Tue, 28 Apr 2009 16:54:39 -0700
Cc: rmt@ietf.org, rfc-editor@rfc-editor.org
Subject: [Rmt] RFC 5510 on Reed-Solomon Forward Error Correction (FEC) Schemes
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmt>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2009 23:56:10 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5510

        Title:      Reed-Solomon Forward Error Correction (FEC) 
                    Schemes 
        Author:     J. Lacan, V. Roca,
                    J. Peltotalo, S. Peltotalo
        Status:     Standards Track
        Date:       April 2009
        Mailbox:    jerome.lacan@isae.fr, 
                    vincent.roca@inria.fr, 
                    jani.peltotalo@tut.fi,  sami.peltotalo@tut.fi
        Pages:      28
        Characters: 57493
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmt-bb-fec-rs-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5510.txt

This document describes a Fully-Specified Forward Error Correction
(FEC) Scheme for the Reed-Solomon FEC codes over GF(2^^m), where m is
in {2..16}, and its application to the reliable delivery of data
objects on the packet erasure channel (i.e., a communication path
where packets are either received without any corruption or discarded
during transmission).  This document also describes a Fully-Specified
FEC Scheme for the special case of Reed-Solomon codes over GF(2^^8)
when there is no encoding symbol group.  Finally, in the context of
the Under-Specified Small Block Systematic FEC Scheme (FEC Encoding
ID 129), this document assigns an FEC Instance ID to the special case
of Reed-Solomon codes over GF(2^^8).

Reed-Solomon codes belong to the class of Maximum Distance Separable
(MDS) codes, i.e., they enable a receiver to recover the k source
symbols from any set of k received symbols.  The schemes described
here are compatible with the implementation from Luigi Rizzo.  
[STANDARDS TRACK]

This document is a product of the Reliable Multicast Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute