From fecframe-bounces@ietf.org Fri Apr 14 12:34:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FURFx-0004Dg-58; Fri, 14 Apr 2006 12:34:49 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FURFv-0004Bo-Vt for fecframe@ietf.org; Fri, 14 Apr 2006 12:34:47 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FURFu-0007w7-Nk for fecframe@ietf.org; Fri, 14 Apr 2006 12:34:47 -0400 Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP id 4441360 for fecframe@ietf.org; Fri, 14 Apr 2006 12:33:47 -0400 Mime-Version: 1.0 (Apple Message framework v749.3) References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4E04098E-72EA-477D-822E-E723DAD435DC@multicasttech.com> Content-Transfer-Encoding: 7bit From: Marshall Eubanks Date: Fri, 14 Apr 2006 12:35:01 -0400 To: fecframe@ietf.org X-Mailer: Apple Mail (2.749.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Subject: [Fecframe] Fwd: [AVT] Pointer for the IETF-for-pro-production folks ... X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: fecframe-bounces@ietf.org For those who are not on the AVT list. Begin forwarded message: > > > -----Original Message----- > From: lazzaro [mailto:lazzaro@eecs.berkeley.edu] > Sent: Thursday, April 13, 2006 11:23 PM > To: avt@ietf.org > Cc: lazzaro > Subject: [AVT] Pointer for the IETF-for-pro-production folks ... > > Hi everyone, > > Interesting article in Mix Magazine > this month: > > http://mixonline.com/mag/audio_hidef_backbone/ > > on the backbone networks that US > TV networks are putting into their production facilities in > preparation > for the switch-over to digital TV terrestrial. Audio-centric given > Mix's > orientation. > > By and large, store-and-forward media flows are going over IP, > but real-time media flows use mostly circuit-switched standards ... > the > article gives a good sense of type and scale of problems we'd need to > solve in the IETF multimedia stack in order to be viable in this > application area. > > --- > John Lazzaro > http://www.cs.berkeley.edu/~lazzaro > lazzaro [at] cs [dot] berkeley [dot] edu > --- > > > > _______________________________________________ > Audio/Video Transport Working Group > avt@ietf.org > https://www1.ietf.org/mailman/listinfo/avt > > _______________________________________________ > Audio/Video Transport Working Group > avt@ietf.org > https://www1.ietf.org/mailman/listinfo/avt _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Sat Apr 15 05:16:23 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FUgtD-0001Jo-7K; Sat, 15 Apr 2006 05:16:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FUgtB-0001Hs-Np for fecframe@ietf.org; Sat, 15 Apr 2006 05:16:21 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FUg8S-0006LR-6m for fecframe@ietf.org; Sat, 15 Apr 2006 04:28:04 -0400 Received: from mailgw4.ericsson.se ([193.180.251.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FUfsP-00069o-B8 for fecframe@ietf.org; Sat, 15 Apr 2006 04:11:31 -0400 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 44D2DBB4 for ; Sat, 15 Apr 2006 10:11:22 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sat, 15 Apr 2006 10:11:21 +0200 Received: from [153.88.12.37] ([153.88.12.37]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sat, 15 Apr 2006 10:11:21 +0200 Message-ID: <4440AAA9.3090909@ericsson.com> Date: Sat, 15 Apr 2006 10:11:21 +0200 From: Magnus Westerlund User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "fecframe@ietf.org" Content-Type: multipart/mixed; boundary="------------040209060509040201000108" X-OriginalArrivalTime: 15 Apr 2006 08:11:21.0719 (UTC) FILETIME=[2E589070:01C66064] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: -2.6 (--) X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92 Subject: [Fecframe] [Fwd: WG Review: FEC Framework (fecframe)] X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: fecframe-bounces@ietf.org This is a multi-part message in MIME format. --------------040209060509040201000108 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi, The external review of the FEC frame charter is now on its way. Please note that there where some changes happening due to the IESG review of the charter. So you should probably re-read the charter proposal now and provide any comments. Cheers Magnus Westerlund Multimedia Technologies, Ericsson Research EAB/TVA/A ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com --------------040209060509040201000108 Content-Type: message/rfc822; name="WG Review: FEC Framework (fecframe)" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="WG Review: FEC Framework (fecframe)" >From - Sat Apr 15 10:01:41 2006 Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw103.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 14 Apr 2006 22:16:52 +0200 Received: from esealmw126.eemea.ericsson.se ([130.100.184.161]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 14 Apr 2006 22:16:52 +0200 Received: from mailgw2.ericsson.se ([193.180.251.48]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 14 Apr 2006 22:16:52 +0200 Received: from megatron.ietf.org (stiedprmman1.ietf.org [156.154.16.145]) by mailgw2.ericsson.se (Symantec Mail Security) with ESMTP id C75F393 for ; Fri, 14 Apr 2006 22:16:51 +0200 (CEST) Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FUUik-0004et-RD; Fri, 14 Apr 2006 16:16:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FUUih-0004cq-Mw; Fri, 14 Apr 2006 16:16:43 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=cypress.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FUUih-0007LA-Ez; Fri, 14 Apr 2006 16:16:43 -0400 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k3EKGh0e012151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Apr 2006 20:16:43 GMT Received: from mirror by ietf.org with local (Exim 4.43) id 1FUUih-0002e7-0F; Fri, 14 Apr 2006 16:16:43 -0400 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list From: IESG Secretary Message-Id: Date: Fri, 14 Apr 2006 16:16:43 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: Subject: WG Review: FEC Framework (fecframe) X-BeenThere: iesg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: iesg.ietf.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iesg-bounces@ietf.org X-Brightmail-Tracker: AAAAAA== Return-Path: iesg-bounces@ietf.org X-OriginalArrivalTime: 14 Apr 2006 20:16:52.0357 (UTC) FILETIME=[5E370B50:01C66000] A new IETF working group has been proposed in the Transport Area. The IESG has not made any determination as yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by April 21st. +++ FEC Framework (fecframe) ========================= Current Status: Proposed Working Group Chairs: TBD Transport Area Director(s): Magnus Westerlund (magnus.westerlund@ericsson.com) Lars Eggert (lars.eggert@netlab.nec.de) Transport Area Advisor: TBD Charter for FECFrame Working Group The object of this group is to develop specifications for using forward error correction (FEC) codes with applications in the Internet to provide protection against packet loss. The group will develop a protocol framework for application of FEC codes to arbitrary packet flows over unreliable transport protocols over both IP multicast and unicast. The application of the FEC codec on an aggregate of multiple packet flows may be investigated and considered to be included in the solution. The FECFrame working group will use the building block approach (RFC 3269), especially the FEC Building Block (RFC 3452), developed by the RMT working group. The FEC Building Block was developed to ensure that the RMT framework developed can support multiple FEC codes and maintain independence between FEC codes and protocols based on the framework. The FECFrame WG may develop new FEC schemes if necessary to provide substantial performance gains for the intended applications. However the acceptance of any FEC scheme will require multiple, prior, detailed reviews of the FEC code by independent experts from both the IETF and the broader community, since it is likely that the IETF working group will not include a large enough number of suitable experts in its working set. If these reviews are positive, then Working Group acceptance of an FEC scheme work item still needs the approval of the responsible Area Director. A primary objective of this framework is to support FEC for real-time media applications using RTP over UDP, such as on demand streaming and audio/video broadcast. Other potential usages of the framework may be brought to the working group for consideration during the development of the requirements, to enable future support of those usages. The group will coordinate closely with the AVT and MMUSIC working groups to ensure that the streaming use-case is fully specified both in terms of interactions with RTP/RTCP and application layer signalling. The group will also coordinate with the DCCP working group, at least to consider that transport protocol's role in streaming media. The interactions of the framework with existing and used security mechanisms must also be considered. The group will work with the RMT working group to ensure that the FEC Building Block defined in RMT supports both the RMT use-cases (object delivery over multicast) and the more general FEC protection of flow(s) over unreliable unicast and multicast transport. Specification of hybrid schemes involving both retransmission and forward error correction is out of scope of the group. MILESTONES: Nov 06 - Working Group consensus on requirements and their prioritization for the FEC protocol framework Mar 07 - Completed selection of solution to develop and mature Nov 07 - FEC Streaming Framework submitted as Proposed Standard Nov 07 - FEC framework requirements submitted as Informational Mar 08 - Usage of FEC framework with RTP submitted as Proposed Standard Mar 08 - FEC framework signalling specification submitted as Proposed Standard Mar 08 - Discuss re-chartering --------------040209060509040201000108 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe --------------040209060509040201000108--