[Fecframe] Protocol Action: 'Raptor FEC Schemes for FECFRAME' to Proposed Standard (draft-ietf-fecframe-raptor-11.txt)

The IESG <iesg-secretary@ietf.org> Mon, 14 May 2012 22:36 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: fecframe@ietfa.amsl.com
Delivered-To: fecframe@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0CB6F21F8907; Mon, 14 May 2012 15:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id vHTD6XKo5VCq; Mon, 14 May 2012 15:36:48 -0700 (PDT)
Received: from ietfa.amsl.com (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 088EB21F8903; Mon, 14 May 2012 15:36:48 -0700 (PDT)
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.02
Message-ID: <20120514223648.3715.26552.idtracker@ietfa.amsl.com>
Date: Mon, 14 May 2012 15:36:48 -0700
Cc: fecframe chair <fecframe-chairs@tools.ietf.org>, fecframe mailing list <fecframe@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Fecframe] Protocol Action: 'Raptor FEC Schemes for FECFRAME' to Proposed Standard (draft-ietf-fecframe-raptor-11.txt)
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Mon, 14 May 2012 22:36:49 -0000

The IESG has approved the following document:
- 'Raptor FEC Schemes for FECFRAME'
  (draft-ietf-fecframe-raptor-11.txt) as Proposed Standard

This document is the product of the FEC Framework Working Group.

The IESG contact persons are Martin Stiemerling and Wesley Eddy.

A URL of this Internet Draft is:

Technical Summary

   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.

Working Group Summary

   There has been controversy over this document in the past, but by now it
   represents WG consensus.

   IPR was declared, and announced in 2009
   updated in 2011 http://www.ietf.org/mail-archive/web/fecframe/current/msg00886.html,
   and updated in 2012 http://www.ietf.org/mail-archive/web/fecframe/current/msg00985.html
   The WG is aware of the IPR and is fine with the situation.  

Document Quality

   The document was reviewed by the WG and also by non-WG members.


   Document Shepherd: Greg Shepherd
   Responsible Area Director: Martin Stiemerling