[Fecframe] Protocol Action: 'RTP Payload Format for Raptor FEC' to Proposed Standard (draft-ietf-fecframe-rtp-raptor-07.txt)

The IESG <iesg-secretary@ietf.org> Sat, 25 February 2012 01:05 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 5308321E801C; Fri, 24 Feb 2012 17:05:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.491
X-Spam-Level:
X-Spam-Status: No, score=-102.491 tagged_above=-999 required=5 tests=[AWL=0.108, 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 kvx9Gc4gwJUP; Fri, 24 Feb 2012 17:05:13 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2440C21E8027; Fri, 24 Feb 2012 17:05:13 -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: 3.64p2
Message-ID: <20120225010513.7473.97428.idtracker@ietfa.amsl.com>
Date: Fri, 24 Feb 2012 17:05:13 -0800
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: 'RTP Payload Format for Raptor FEC' to Proposed Standard (draft-ietf-fecframe-rtp-raptor-07.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: Sat, 25 Feb 2012 01:05:14 -0000

The IESG has approved the following document:
- 'RTP Payload Format for Raptor FEC'
  (draft-ietf-fecframe-rtp-raptor-07.txt) as a Proposed Standard

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

The IESG contact persons are David Harrington and Wesley Eddy.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-fecframe-rtp-raptor/




Technical Summary

This document specifies an RTP payload format for Forward Error
Correction / (FEC) repair data produced by the Raptor FEC schemes.
Raptor FEC schemes are specified for use with the IETF FEC Framework
which supports transport of repair data over both UDP and RTP. This
document specifies the payload format which is required for the use of
RTP to carry Raptor repair flows.


Working Group Summary

There were no seriously contentious issues during the WG process.

IETF Last Call ends 11/3, the requested date for a telechat. If there 
are substantive comments during IETF LC, I will push this to a later telechat.

Document Quality

The Working Group feedback covered both the quality of the document
itself as well as the technical issues with the content of the
document.

Personnel

Document Shepherd - Greg Shepherd
Responsible Area Director - David Harrington <ietfdbh@comcast.net>; 

RFC Editor Note

1) references need updating; fecframe-framework and fecframe-sdp-elements have been published.
2) in the Introduction s/MAY/might/g
3) in multiple places, the Controller should be the PAYLOAD WG rather than the AVT WG
4) some examples will be provided for "applications that use ..."