[Fecframe] [Fwd: New Version Notification for draft-roca-fecframe-rs-00]
Vincent Roca <vincent.roca@inrialpes.fr> Wed, 04 March 2009 15:58 UTC
Return-Path: <vincent.roca@inrialpes.fr>
X-Original-To: fecframe@core3.amsl.com
Delivered-To: fecframe@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C543928C3BA for <fecframe@core3.amsl.com>; Wed, 4 Mar 2009 07:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 sRRnzwcGLDxX for <fecframe@core3.amsl.com>; Wed, 4 Mar 2009 07:58:10 -0800 (PST)
Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by core3.amsl.com (Postfix) with ESMTP id 71C9328C3B9 for <fecframe@ietf.org>; Wed, 4 Mar 2009 07:57:54 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,301,1233529200"; d="scan'208";a="25058510"
Received: from ornon.inrialpes.fr (HELO [194.199.24.115]) ([194.199.24.115]) by mail1-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Mar 2009 16:58:19 +0100
Message-ID: <49AEA51A.5050107@inrialpes.fr>
Date: Wed, 04 Mar 2009 16:58:18 +0100
From: Vincent Roca <vincent.roca@inrialpes.fr>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: fecframe@ietf.org
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Subject: [Fecframe] [Fwd: New Version Notification for draft-roca-fecframe-rs-00]
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of FEC Framework <fecframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/fecframe>, <mailto:fecframe-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fecframe>
List-Post: <mailto:fecframe@ietf.org>
List-Help: <mailto:fecframe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fecframe>, <mailto:fecframe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 15:58:10 -0000
Hello, FYI, we just submitted an I-D describing the use of Reed-Solomon codes in the context of FecFrame (I should say "starting to describe" since several sections are still TBD) . http://www.ietf.org/internet-drafts/draft-roca-fecframe-rs-00.txt This document inherits from http://tools.ietf.org/html/draft-ietf-rmt-bb-fec-rs-05 https://datatracker.ietf.org/idtracker/draft-ietf-rmt-bb-fec-rs/ the code specifications. Regards, Vincent, Mathieu, Jerome, Amine, and Kazu. -------- Original Message -------- Subject: New Version Notification for draft-roca-fecframe-rs-00 Date: Wed, 4 Mar 2009 07:46:10 -0800 (PST) From: IETF I-D Submission Tool <idsubmission@ietf.org> To: vincent.roca@inria.fr CC: kazuhisa@sfc.wide.ad.jp, jerome.lacan@isae.fr, mathieu.cunche@inria.fr, Amine.Bouabdallah@isae.fr A new version of I-D, draft-roca-fecframe-rs-00.txt has been successfuly submitted by Vincent Roca and posted to the IETF repository. Filename: draft-roca-fecframe-rs Revision: 00 Title: Reed-Solomon Forward Error Correction (FEC) Schemes for FECFRAME Creation_date: 2009-03-04 WG ID: Independent Submission Number_of_pages: 32 Abstract: This document describes four fully-specified FEC schemes for Reed- Solomon codes that can be used to protect 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 sparse parity check based FEC codes. However, this complexity remains compatible with software codecs. The first scheme is for Reed-Solomon codes over GF(2^^m), with m in {2..16}, a global FEC encoding and arbitrary packet flows. The second scheme is for Reed-Solomon codes over GF(2^^m), with m in {2..16}, the general case FEC encoding, and arbitrary packet flows. The third (resp. fourth) scheme is similar to the first (resp. second) scheme, with the exception that it is for a single sequenced flow. The IETF Secretariat.
- [Fecframe] [Fwd: New Version Notification for dra… Vincent Roca