[Fecframe] Last Call: <draft-ietf-fecframe-raptor-10.txt> (Raptor FEC Schemes for FECFRAME) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 06 March 2012 22:59 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: fecframe@ietfa.amsl.com
Delivered-To: fecframe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D16921E804B; Tue, 6 Mar 2012 14:59:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level:
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R1VCUwAFrwbs; Tue, 6 Mar 2012 14:59:29 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E771D21F851E; Tue, 6 Mar 2012 14:59:29 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.00
Message-ID: <20120306225929.21687.52941.idtracker@ietfa.amsl.com>
Date: Tue, 06 Mar 2012 14:59:29 -0800
Cc: fecframe@ietf.org
Subject: [Fecframe] Last Call: <draft-ietf-fecframe-raptor-10.txt> (Raptor FEC Schemes for FECFRAME) to Proposed Standard
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Discussion of FEC Framework <fecframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 06 Mar 2012 22:59:30 -0000

The IESG has received a request from the FEC Framework WG (fecframe) to
consider the following document:
- 'Raptor FEC Schemes for FECFRAME'
  <draft-ietf-fecframe-raptor-10.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-03-20. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document describes Fully-Specified Forward Error Correction
   (FEC) Schemes for the Raptor and RaptorQ codes and their application
   to reliable delivery of media streams in the context of FEC
   Framework.  The Raptor and RaptorQ codes are systematic codes, where
   a number of repair symbols are generated from a set of source symbols
   and sent in one or more repair flows in addition to the source
   symbols that are sent to the receiver(s) within a source flow.  The
   Raptor and RaptorQ codes offer close to optimal protection against
   arbitrary packet losses at a low computational complexity.  Six FEC
   Schemes are defined, two for protection of arbitrary packet flows,
   two that are optimised for small source blocks and another two for
   protection of a single flow that already contains a sequence number.
   Repair data may be sent over arbitrary datagram transport (e.g.  UDP)
   or using RTP.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-fecframe-raptor/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-fecframe-raptor/ballot/


The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/1186/
   http://datatracker.ietf.org/ipr/1290/
   http://datatracker.ietf.org/ipr/1509/