[Fecframe] Last Call: <draft-ietf-fecframe-rtp-raptor-05.txt> (RTP Payload Format for Raptor FEC) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Thu, 20 October 2011 13:47 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 BDF4721F8B5D; Thu, 20 Oct 2011 06:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level:
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, 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 9Tj+5GEuAXNx; Thu, 20 Oct 2011 06:47:16 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C41221F86DD; Thu, 20 Oct 2011 06:47:16 -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: 3.61
Message-ID: <20111020134716.20244.40862.idtracker@ietfa.amsl.com>
Date: Thu, 20 Oct 2011 06:47:16 -0700
Cc: fecframe@ietf.org
Subject: [Fecframe] Last Call: <draft-ietf-fecframe-rtp-raptor-05.txt> (RTP Payload Format for Raptor FEC) 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: Thu, 20 Oct 2011 13:47:16 -0000
The IESG has received a request from the FEC Framework WG (fecframe) to consider the following document: - 'RTP Payload Format for Raptor FEC' <draft-ietf-fecframe-rtp-raptor-05.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 2011-11-03. 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 specifies an RTP Payload Format for Forward Error Correction 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. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-fecframe-rtp-raptor/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-fecframe-rtp-raptor/ No IPR declarations have been submitted directly on this I-D.
- [Fecframe] Last Call: <draft-ietf-fecframe-rtp-ra… The IESG
- Re: [Fecframe] Last Call: <draft-ietf-fecframe-rt… Vincent Roca
- Re: [Fecframe] Last Call: <draft-ietf-fecframe-rt… Thomas Stockhammer