Re: [multrans] Draft Multrans BoF request

Tina Tsou <tena@huawei.com> Mon, 13 June 2011 21:41 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 1325511E80AC for <multrans@ietfa.amsl.com>; Mon, 13 Jun 2011 14:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.194
X-Spam-Level:
X-Spam-Status: No, score=-105.194 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 fLRXaWk9Kjis for <multrans@ietfa.amsl.com>; Mon, 13 Jun 2011 14:41:02 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id AB60011E80A1 for <multrans@ietf.org>; Mon, 13 Jun 2011 14:41:01 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LMR00151088IN@szxga04-in.huawei.com> for multrans@ietf.org; Tue, 14 Jun 2011 05:40:56 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LMR00DAN0882B@szxga04-in.huawei.com> for multrans@ietf.org; Tue, 14 Jun 2011 05:40:56 +0800 (CST)
Received: from [192.35.167.6] (iPad.dhcp.nanog.merit.net [192.35.167.6]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPSA id <0LMR000Z7084U0@szxml11-in.huawei.com>; Tue, 14 Jun 2011 05:40:56 +0800 (CST)
Date: Mon, 13 Jun 2011 15:42:02 -0600
From: Tina Tsou <tena@huawei.com>
In-reply-to: <4DF6441C.4030301@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
Message-id: <516A794B-C2CB-4FD5-83E8-F37BB65BB655@huawei.com>
MIME-version: 1.0
X-Mailer: iPad Mail (8J3)
Content-type: multipart/alternative; boundary="Boundary_(ID_GM7MVlUXB2lTBNHeESH1Uw)"
References: <CA1B6430.10305%yiu_lee@cable.comcast.com> <4DF6441C.4030301@piuha.net>
Cc: "multrans@ietf.org" <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: Mon, 13 Jun 2011 21:41:03 -0000

> 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?
Jari, 
There are people from FT and Comcast as the author of the problem statements, indicating they are asking not just deploying multicast separately for the two IP versions. It does not have to mean their deployments are exactly the same as the document.
In addition, in my mind, the deployment of SSM and ASM on the dual stack network is also part of multicast transition. Some operators are asking it. Though the priority could be discussed, the scope could be discussed.

Best regards,
Tina TSOU
http://tinatsou.weebly.com/

On Jun 13, 2011, at 11:08 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> 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 
>> Drafts: [ jaclee-behave-v4v6-mcast-ps] 
>> Agenda: [ agenda] 
>> Charter: TBD 
>> Status: Under consideration
> 
> Jari
>