[multrans] New Version Notification of draft-zhou-multrans-af1-specification-00 for the 4th item "an adaptation function between the receiver and the network" of the interim meeting

"Cathy Zhou(Qian)" <cathy.zhou@huawei.com> Fri, 16 December 2011 07:34 UTC

Return-Path: <cathy.zhou@huawei.com>
X-Original-To: multrans@ietfa.amsl.com
Delivered-To: multrans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E1111E809A; Thu, 15 Dec 2011 23:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eusN2TNdXrOx; Thu, 15 Dec 2011 23:34:41 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 4F08311E8093; Thu, 15 Dec 2011 23:34:41 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWA00KUOD1DUS@szxga05-in.huawei.com>; Fri, 16 Dec 2011 15:34:25 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWA008YKD1D5L@szxga05-in.huawei.com>; Fri, 16 Dec 2011 15:34:25 +0800 (CST)
Received: from szxeml207-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AFW04418; Fri, 16 Dec 2011 15:34:24 +0800
Received: from SZXEML421-HUB.china.huawei.com (10.82.67.160) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 16 Dec 2011 15:34:07 +0800
Received: from SZXEML527-MBX.china.huawei.com ([169.254.3.201]) by szxeml421-hub.china.huawei.com ([10.82.67.160]) with mapi id 14.01.0323.003; Fri, 16 Dec 2011 15:34:14 +0800
Date: Fri, 16 Dec 2011 07:34:14 +0000
From: "Cathy Zhou(Qian)" <cathy.zhou@huawei.com>
X-Originating-IP: [10.70.39.106]
To: "multrans@ietf.org" <multrans@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Message-id: <A6A061BEE5DDC94A9692D9D81AF776DF0AB265EF@szxeml527-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_vNs33gt/t7/td3bHwyC6lA)"
Content-language: zh-CN
Accept-Language: zh-CN, en-US
Thread-topic: [multrans] New Version Notification of draft-zhou-multrans-af1-specification-00 for the 4th item "an adaptation function between the receiver and the network" of the interim meeting
Thread-index: Acy7xRu42eaFbqKLQxOkBaNs0wVlAg==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
Subject: [multrans] New Version Notification of draft-zhou-multrans-af1-specification-00 for the 4th item "an adaptation function between the receiver and the network" of the interim meeting
X-BeenThere: multrans@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discuss the work of IPv4-IPv6 multicast." <multrans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multrans>, <mailto:multrans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multrans>
List-Post: <mailto:multrans@ietf.org>
List-Help: <mailto:multrans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multrans>, <mailto:multrans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 07:34:45 -0000

Dear all,

Here is a new draft to work from for the 4th item " Specification of an adaptation function between the receiver and the network" of the interim meeting.

http://tools.ietf.org/html/draft-zhou-multrans-af1-specification-00





Abstract:

   Discussion of the problem of multicast transition has brought out a

   number of scenarios that are the most likely to be encountered in

   practice.  In some of these scenarios the IP version supported by the

   multicast receiver differs from that supported by the provider

   network to which it is attached.  In such cases an adaptation

   function is required between the receiver and the network, to mediate

   the signalling and data flows between them.  This memo uses the term

   &quot;Type 1 Adaptation Function&quot; (AF1) for such a function.  It is

   written for the purpose of specifying the functions performed by an

   AF1.



   The scope of this memo is limited to the case where flows are

   unidirectional, from a designated set of sources to a designated (and

   normally much more numerous) set of receivers.  The IP television

   (IPTV) case falls within this scope.

Comments are welcome.

Best Regards,
Cathy ZHOU & Tom Taylor