[multrans] Draft agenda for multicast transition interim

Tina TSOU <Tina.Tsou.Zouting@huawei.com> Tue, 06 December 2011 01:04 UTC

Return-Path: <Tina.Tsou.Zouting@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 BFBA31F0C35; Mon, 5 Dec 2011 17:04:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.486
X-Spam-Level:
X-Spam-Status: No, score=-6.486 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, 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 BZmKnwcqaV8M; Mon, 5 Dec 2011 17:04:01 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 325C51F0C34; Mon, 5 Dec 2011 17:04:01 -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 <0LVR008ZYCAO85@szxga03-in.huawei.com>; Tue, 06 Dec 2011 09:04:00 +0800 (CST)
Received: from szxrg02-dlp.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 <0LVR007QUCAG2Y@szxga03-in.huawei.com>; Tue, 06 Dec 2011 09:04:00 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AFK77994; Tue, 06 Dec 2011 09:04:00 +0800
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 06 Dec 2011 09:03:58 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.37]) by szxeml418-hub.china.huawei.com ([10.82.67.157]) with mapi id 14.01.0323.003; Tue, 06 Dec 2011 09:03:51 +0800
Date: Tue, 06 Dec 2011 01:03:51 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
X-Originating-IP: [10.193.34.145]
To: "multrans@ietf.org" <multrans@ietf.org>, MBONED WG <mboned@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C216ECF@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-language: en-US
Content-transfer-encoding: 7bit
Accept-Language: en-US, zh-CN
Thread-topic: Draft agenda for multicast transition interim
Thread-index: AQHMs6Ffjh6RlJwL9UOCkcshob2Wj5XN/LJg
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
Subject: [multrans] Draft agenda for multicast transition interim
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: Tue, 06 Dec 2011 01:04:01 -0000

Dear all,
It is proposed to hold the multicast transition interim meeting as a 
series of short meetings. Timing of individual meetings may be set to 
spread inconvenient hours around the globe. The objective of these 
meetings is to achieve technical progress in the indicated topics. Here 
is the proposed agenda:

1. Use Cases (1 hour)

Ensure we are all clear on what use cases will be in scope.


2. Multicast address discovery by the receiver (2 hours)

How does the receiver learn the multicast addresses corresponding to 
specific programs, in the IP version that the receiver understands?


3. Multicast address translation (2 hours)

Stateless translation between IPv4 and IPv6 addresses should get 
priority in this discussion, but we may go on to the broader topic if 
there appears to be a need.


4. What and how an adaptation function between the receiver and the network works (2 hours)

In cases where the receiver and the multicast-enabled network to which 
it is attached support different IP versions, an adaptation function 
(AF) is required between them. What are the requirements on that AF for 
the handling of multicast signalling and the handling of multicast content?

5. What and how an adaptation function between two networks works (2 hours)

In cases where two adjacent multicast-enabled networks support different 
IP versions, another type of adaptation function is needed. What are the 
requirements on that AF for the handling of multicast signalling and the 
handling of multicast content?

Comments on this draft agenda are invited.

Tina