Re: [AVT] New Version Notification for draft-xia-avt-proxy-rapid-acquisition-01
Jinwei Xia <xiajinwei@huawei.com> Wed, 10 March 2010 04:13 UTC
Return-Path: <xiajinwei@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C3553A6B34 for <avt@core3.amsl.com>; Tue, 9 Mar 2010 20:13:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level:
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAYNur58qUpi for <avt@core3.amsl.com>; Tue, 9 Mar 2010 20:13:33 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 3B6633A6B41 for <avt@ietf.org>; Tue, 9 Mar 2010 20:13:28 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZ100AOOT2AYY@szxga03-in.huawei.com> for avt@ietf.org; Wed, 10 Mar 2010 12:13:22 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZ100FK6T2AX2@szxga03-in.huawei.com> for avt@ietf.org; Wed, 10 Mar 2010 12:13:22 +0800 (CST)
Received: from x65217 ([10.164.12.70]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KZ100I4GT2AZ5@szxml06-in.huawei.com> for avt@ietf.org; Wed, 10 Mar 2010 12:13:22 +0800 (CST)
Date: Wed, 10 Mar 2010 12:13:22 +0800
From: Jinwei Xia <xiajinwei@huawei.com>
In-reply-to: <20100308094437.C725C3A67E7@core3.amsl.com>
To: avt@ietf.org
Message-id: <009501cac008$05ea4130$460ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: Acq+pA1Ehwdw9xN6Q2GVjX7LaZizRgBYXS1w
Subject: Re: [AVT] New Version Notification for draft-xia-avt-proxy-rapid-acquisition-01
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 04:13:42 -0000
Hi all, The update addresses several open issues, especially clarify the motivation why adopt a proxy to perform rapid acquisiton on behalf of RTP receiver, as well as the behavours of proxy. The updated draft link: http://tools.ietf.org/html/draft-xia-avt-proxy-rapid-acquisition-01 There are a few remaining open items and we are hoping to address them before this meeting. Comments are welcome. Thank you in advance. BR Jinwei > -----Original Message----- > From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] > Sent: Monday, March 08, 2010 5:45 PM > To: xiajinwei@huawei.com > Cc: sunseawq@huawei.com; asaeda@wide.ad.jp > Subject: New Version Notification for > draft-xia-avt-proxy-rapid-acquisition-01 > > > A new version of I-D, > draft-xia-avt-proxy-rapid-acquisition-01.txt has been > successfuly submitted by Jinwei Xia and posted to the IETF repository. > > Filename: draft-xia-avt-proxy-rapid-acquisition > Revision: 01 > Title: Proxy Rapid Acquisition of Multicast > RTP Sessions > Creation_date: 2010-03-08 > WG ID: Independent Submission > Number_of_pages: 25 > > Abstract: > This document describes a proxy rapid acquisition mechanism > which reduces acquisition delay for an RTP receiver without > supporting any rapid acquisition related functionality. The > network is responsible for managing rapid acquisition on > behalf of the RTP receiver, including detecting SFGMP message > as proxy specified in [RFC4605] from the RTP receiver and > launching the required rapid acquisition signaling instead of > the RTP receiver. This proxy rapid acquisition of multicast > RTP session in this document is referred to as Proxy Rapid > Acquisition of Multicast Sessions. > > > > > The IETF Secretariat. > >