[AVT] draft-ietf-avt-tfrc-profile-07.txt

Ladan Gharai <ladan@isi.edu> Sat, 03 March 2007 02:13 UTC

Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNJka-000449-D7; Fri, 02 Mar 2007 21:13:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNJkA-0003hb-4o for avt@ietf.org; Fri, 02 Mar 2007 21:13:06 -0500
Received: from porter.east.isi.edu ([65.114.168.19]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNJk6-00077x-Sb for avt@ietf.org; Fri, 02 Mar 2007 21:13:06 -0500
Received: from [65.114.168.149] (java.east.isi.edu [65.114.168.149]) by porter.east.isi.edu (Postfix) with ESMTP id 9AE671CB0 for <avt@ietf.org>; Fri, 2 Mar 2007 21:13:02 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v728)
References: <E1HNEhW-0002W7-GW@stiedprstage1.ietf.org>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <96FA85F4-2C9B-4394-85F3-9138E2A7981D@isi.edu>
Content-Transfer-Encoding: 7bit
From: Ladan Gharai <ladan@isi.edu>
Date: Fri, 02 Mar 2007 21:15:28 -0500
To: IETF AVT Working Group <avt@ietf.org>
X-Mailer: Apple Mail (2.728)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [AVT] draft-ietf-avt-tfrc-profile-07.txt
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>
Errors-To: avt-bounces@ietf.org

Dear AVT'ers:

A new version of draft-ietf-avt-tfrc-profile has been posted.

The most significant change to the draft is that it no longer defines  
a new profile (although it still uses the name -avt-tfrc-profile).

In order to use TFRC with RTP, the draft defines the exchange of info  
between TFRC senders and receivers by using:
     1.  the general RTP header extensions; and
     2. a new AVPF feedback packet.

Please read the draft and send you comments and feedback!

thank you,
Ladan



Begin forwarded message:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Audio/Video Transport Working  
> Group of the IETF.
>
>     Title        : RTP Profile for TCP Friendly Rate Control
>     Author(s)    : L. Gharai
>     Filename    : draft-ietf-avt-tfrc-profile-07.txt
>     Pages        : 10
>     Date        : 2007-3-2
>
> This memo specifies how the TCP Friendly Rate Control (TFRC) of RTP
>    flows can be supported using the RTP/AVPF profile and the  
> general RTP
>    header extension mechanism.  AVPF feedback packets and RTP header
>    extensions are defined to support the exchange of control  
> information
>    between RTP TFRC senders and receivers. TFRC is an equation based
>    congestion control scheme for unicast flows operating in a best
>    effort Internet environment.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-tfrc-profile-07.txt
>
>


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