[Fecframe] FW: Last Call: <draft-ietf-fecframe-framework-15.txt>(Forward Error Correction (FEC) Framework) to Proposed Standard
"David Harrington" <ietfdbh@comcast.net> Wed, 15 June 2011 13:32 UTC
Return-Path: <ietfdbh@comcast.net>
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 F30AB11E8135 for <fecframe@ietfa.amsl.com>; Wed, 15 Jun 2011 06:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.441
X-Spam-Level:
X-Spam-Status: No, score=-102.441 tagged_above=-999 required=5 tests=[AWL=0.158, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2eg-Ixq3lU2y for <fecframe@ietfa.amsl.com>; Wed, 15 Jun 2011 06:32:14 -0700 (PDT)
Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [76.96.27.211]) by ietfa.amsl.com (Postfix) with ESMTP id 72B9D11E8126 for <fecframe@ietf.org>; Wed, 15 Jun 2011 06:32:14 -0700 (PDT)
Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta11.emeryville.ca.mail.comcast.net with comcast id wCwS1g0061u4NiLABDYCyu; Wed, 15 Jun 2011 13:32:12 +0000
Received: from davidPC ([67.189.235.106]) by omta21.emeryville.ca.mail.comcast.net with comcast id wDXX1g00B2JQnJT8hDXdQY; Wed, 15 Jun 2011 13:31:40 +0000
From: David Harrington <ietfdbh@comcast.net>
To: fecframe@ietf.org, 'Transport Directorate' <tsv-dir@ietf.org>
Date: Wed, 15 Jun 2011 09:31:53 -0400
Message-ID: <74597C0D9E6240B093FC18D88F27F846@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16776
Thread-index: AcwquRXNER3LevDoQf+0FcjfPZqa0QAp3LPw
Subject: [Fecframe] FW: Last Call: <draft-ietf-fecframe-framework-15.txt>(Forward Error Correction (FEC) Framework) to Proposed Standard
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: Wed, 15 Jun 2011 13:32:15 -0000
-----Original Message----- From: fecframe-bounces@ietf.org [mailto:fecframe-bounces@ietf.org] On Behalf Of The IESG Sent: Tuesday, June 14, 2011 1:33 PM To: IETF-Announce Cc: fecframe@ietf.org Subject: [Fecframe] Last Call: <draft-ietf-fecframe-framework-15.txt>(Forward Error Correction (FEC) Framework) to Proposed Standard The IESG has received a request from the FEC Framework WG (fecframe) to consider the following document: - 'Forward Error Correction (FEC) Framework' <draft-ietf-fecframe-framework-15.txt> as a Proposed Standard The IESG reviewed this draft and requested substantial changes. This is a second Last Call, running for one week, to ensure the community has an opportunity to review the changes. 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-06-22. 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 a framework for using Forward Error Correction (FEC) codes with applications in public and private IP networks to provide protection against packet loss. The framework supports applying FEC to arbitrary packet flows over unreliable transport and is primarily intended for real-time, or streaming, media. This framework can be used to define Content Delivery Protocols that provide FEC for streaming media delivery or other packet flows. Content Delivery Protocols defined using this framework can support any FEC scheme (and associated FEC codes) which is compliant with various requirements defined in this document. Thus, Content Delivery Protocols can be defined which are not specific to a particular FEC scheme, and FEC schemes can be defined which are not specific to a particular Content Delivery Protocol. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-fecframe-framework/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-fecframe-framework/ No IPR declarations have been submitted directly on this I-D. _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www.ietf.org/mailman/listinfo/fecframe
- [Fecframe] FW: Last Call: <draft-ietf-fecframe-fr… David Harrington