[AVT] Re: avt Digest, Vol 15, Issue 16

Girish Chandran <gchandran@newtecamerica.com> Fri, 15 July 2005 12:04 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtOvt-0004I5-Tn; Fri, 15 Jul 2005 08:04:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtOvr-0004I0-4W for avt@megatron.ietf.org; Fri, 15 Jul 2005 08:04:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28888 for <avt@ietf.org>; Fri, 15 Jul 2005 08:04:41 -0400 (EDT)
Received: from ranger.electric.net ([216.129.90.29]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtPOc-0005vQ-6x for avt@ietf.org; Fri, 15 Jul 2005 08:34:29 -0400
Received: from root by ranger.electric.net with emc1-ok (Exim 4.24) id 1DtOvG-0008DD-UQ for avt@ietf.org; Fri, 15 Jul 2005 05:04:06 -0700
Received: by emcmailer; Fri, Jul 15 2005 05:04:06 -0700
Received: from [64.69.103.254] (helo=mailhost.newtecamerica.com) by ranger.electric.net with esmtp (Exim 4.24) id 1DtOvF-0008Cq-V6 for avt@ietf.org; Fri, 15 Jul 2005 05:04:05 -0700
Received: from [192.168.16.28] ([192.168.16.28]) by mailhost.newtecamerica.com; Fri, 15 Jul 2005 08:03:58 -0500
Message-ID: <42D7A62C.7000004@newtecamerica.com>
Date: Fri, 15 Jul 2005 08:03:56 -0400
From: Girish Chandran <gchandran@newtecamerica.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Flag: NO
X-Spam-Checker-Version: GEE Whiz 2.0 b1624
X-Spam-Score: 0.00/4.00
X-Spam-Flag: NO
X-Spam-Checker-Version: GEE Whiz 2.0 b1624
X-Spam-Score: 0.00/4.00
X-Virus-Status: Scanned by VirusSMART (s)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Content-Transfer-Encoding: 7bit
Subject: [AVT] Re: avt Digest, Vol 15, Issue 16
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org

Pro-MPEG forum has also done some work on FEC for streamed media.


Girish Chandran

avt-request@ietf.org wrote:

>Send avt mailing list submissions to
>	avt@ietf.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://www1.ietf.org/mailman/listinfo/avt
>or, via email, send a message with subject or body 'help' to
>	avt-request@ietf.org
>
>You can reach the person managing the list at
>	avt-owner@ietf.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of avt digest..."
>
>
>Today's Topics:
>
>   1. Proposed FEC Streaming Framework (Magnus Westerlund)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Thu, 14 Jul 2005 09:42:27 +0200
>From: Magnus Westerlund <magnus.westerlund@ericsson.com>
>Subject: [AVT] Proposed FEC Streaming Framework
>To: IETF AVT WG <avt@ietf.org>, rmt@ietf.org
>Cc: Stephan.Wenger@nokia.com
>Message-ID: <42D61763.20704@ericsson.com>
>Content-Type: text/plain; charset=iso-8859-1; format=flowed
>
>All,
>
>The below messge was sent to TSVWG. If you have comments on this please 
>respond to us author or the TSVWG.
>
>/Magnus Westerlund
>
>-----
>
>A few of us have been working on a framework for FEC protection of
>streaming media, based on some work done recently in 3GPP and making use
>of the FEC Building Block defined by RMT (so that the framework is not
>specific to a particular FEC code).
>
>This proposal is described in
>http://www.ietf.org/internet-drafts/draft-watson-tsvwg-fec-sf-00.txt.
>Although intended primarily for streaming, it is not specific to RTP,
>defining instead an FEC protection layer above UDP, which can protect a
>set of several UDP flows.
>
>Since the proposal is not specific to either multicast or RTP, we are
>bringing it first to TSVWG, rather than RMT or AVT. It will be discussed
>at the Paris meeting, so please put it on your reading list.
>
>The questions for the TSVWG are (at least):
>1) is the objective of extending the RMT FEC Building Block framework to
>streaming a good one ?
>2) is this a good approach to that objective ?
>3) what is the relationship with the ULP work in AVT ?
>4) whether the proposal should best be progressed in AVT (where there is
>streaming expertise), in RMT (where there is FEC expertise) or in TSVWG
>?
>
>Regards,
>
>Mark Watson
>Digital Fountain
>
>
>
>
>
>------------------------------
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt
>
>
>End of avt Digest, Vol 15, Issue 16
>***********************************
>
>
>  
>





_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt