Re: [multrans] Draft Multrans BoF request

Tina Tsou <tena@huawei.com> Tue, 14 June 2011 07:03 UTC

Return-Path: <tena@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 9154021F852E for <multrans@ietfa.amsl.com>; Tue, 14 Jun 2011 00:03:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.261
X-Spam-Level:
X-Spam-Status: No, score=-106.261 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2FwSAQU2JHy for <multrans@ietfa.amsl.com>; Tue, 14 Jun 2011 00:03:49 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by ietfa.amsl.com (Postfix) with ESMTP id C211C21F851E for <multrans@ietf.org>; Tue, 14 Jun 2011 00:03:49 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LMR001CYQAC6Z@usaga02-in.huawei.com> for multrans@ietf.org; Tue, 14 Jun 2011 02:03:49 -0500 (CDT)
Received: from TingZousc1 ([10.212.244.185]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LMR00A1GQA8H0@usaga02-in.huawei.com> for multrans@ietf.org; Tue, 14 Jun 2011 02:03:48 -0500 (CDT)
Date: Tue, 14 Jun 2011 01:03:41 -0600
From: Tina Tsou <tena@huawei.com>
In-reply-to: <4DF6441C.4030301@piuha.net>
To: 'Jari Arkko' <jari.arkko@piuha.net>
Message-id: <000501cc2a61$34292dd0$9c7b8970$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_2jzLN0Cak454UPi1yDVVEg)"
Content-language: en-us
Thread-index: Acwp7LHdMTwb/tP3SHCReZ56gF/8zwAc60wA
References: <CA1B6430.10305%yiu_lee@cable.comcast.com> <4DF6441C.4030301@piuha.net>
Cc: multrans@ietf.org
Subject: Re: [multrans] Draft Multrans BoF request
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, 14 Jun 2011 07:03:52 -0000

Jari,
About the proposed charter, here is a copy from the presentation in
IPv4-IPv6 multicast meetings in Prague in March.
 
The task of this Working Group is to devise the means whereby existing
multicast distribution mechanisms can work when signalling and content have
to traverse one or more boundaries where IP version changes.
 
The Working Group will consider three cases:
-- provider distributed multicast (including IPTV);
-- multicast networks connected directly to a multicast backbone network;
-- multicast networks separated from the backbone network by unicast
networks.
 
The Working Group's first task is to create a Problem Statement. This
documents will specify the requirements that must be satisfied by multicast
transition solutions for the three cases listed above. It will describe the
scenarios that need to be considered and the challenges posed by those
scenarios in those three cases. Finally, the Problem Statement will specify
the new functional capabilities required to enable the solution of the
multicast transition problem in the different scenarios.
 
The Working Group will follow up with one or more framework documents
analyzing the potential multicast transition solutions for specific
scenarios or groups of scenarios. The circumstances under which the
different solution approaches are applicable will be described, taking
account of the unicast transition mechanisms that may be deployed in a
given network. The framework drafts should include a view of the evolution
path for multicast transition over time, possibly though not necessarily as
a function of the associated unicast transition path. The final outcome of
the framework drafts should be recommendations for preferred solution
approaches.
 
Finally, the Working Group will produce a small set of solution drafts for
the cases considered to be of the highest priority before re-chartering or
disbandment. Specifically, the Working Group will provide one or two
solutions for the provider distributed multicast case when the multicast
source and receiver are IPv4 and there is an intervening IPv6 network. The
solution(s) must be compatible with the unicast translation (NAT64) and
tunneling (DS Lite, Gateway-Initiated DS lite) transition mechanisms. The
solution(s) must discuss the considerations specifically relevant to these
three unicast transition mechanisms to the extent this discussion is not
covered by the framework document. The Working Group will also provide a
solution for the case of multicast networks connected directly to a
multicast backbone network.
 
Relations: Behave, Softwires, PIM, Mboned, V6ops
 
Deliverables:
Problem Statement (Informational)
Framework for the provider distributed multicast case (Informational)
Framework for the case of multicast networks connected directly to a
multicast backbone network (Informational)
Solutions (2-3) (Proposed Standard)
 
We keep our promises with one another - no matter what!
 
Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html
 
From: Jari Arkko [mailto:jari.arkko@piuha.net] 
Sent: Monday, June 13, 2011 11:09 AM
To: Tina Tsou
Cc: Lee, Yiu; 'Tom Taylor'; mohamed.boucadair@orange-ftgroup.com;
multrans@ietf.org
Subject: Re: [multrans] Draft Multrans BoF request
 
Tina, others,

I'm trying to construct a wiki entry for this BOF so that the IESG and IAB
have all the information available to them to make decisions on what BOFs to
approve on Thursday. What other drafts than the ps I should list? Is there a
pointer to a mailing list post or some web site for the proposed charter?
Also, for my background: are there providers who are asking for multicast
transition solutions? I.e., not just deploying multicast separately for the
two IP versions?

Here's what we have so far:



MULTRANS - Multicast Transition 
Description: Proposed BOF to gather efforts around enabling IPv4-IPv6
coexistence and transition with multicast traffic. This proposal has
relationships to existing chartered work in SOFTWIRE and BEHAVE working
groups.
Length of session: 120 minutes 
Responsible AD: Jari Arkko, Ralph Droms, and David Harrington 
Mailing list:  <https://www.ietf.org/mailman/listinfo/multrans>
https://www.ietf.org/mailman/listinfo/multrans 
Drafts: [ <http://tools.ietf.org/html/draft-jaclee-behave-v4v6-mcast-ps-02>
jaclee-behave-v4v6-mcast-ps] 
Agenda: [ <http://www.arkko.com/ietf/ietf-81/multrans/agenda.txt>  agenda] 
Charter: TBD 
Status: Under consideration 

Jari