Re: [multrans] List of work items

Tom Taylor <tom111.taylor@bell.net> Fri, 22 July 2011 19:42 UTC

Return-Path: <tom111.taylor@bell.net>
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 0BEA121F891F for <multrans@ietfa.amsl.com>; Fri, 22 Jul 2011 12:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.442
X-Spam-Level:
X-Spam-Status: No, score=-101.442 tagged_above=-999 required=5 tests=[AWL=0.354, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, 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 d5+tXucPVuR3 for <multrans@ietfa.amsl.com>; Fri, 22 Jul 2011 12:42:01 -0700 (PDT)
Received: from blu0-omc4-s1.blu0.hotmail.com (blu0-omc4-s1.blu0.hotmail.com [65.55.111.140]) by ietfa.amsl.com (Postfix) with ESMTP id 7B6A421F88E5 for <multrans@ietf.org>; Fri, 22 Jul 2011 12:42:01 -0700 (PDT)
Received: from BLU0-SMTP57 ([65.55.111.135]) by blu0-omc4-s1.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 22 Jul 2011 12:42:01 -0700
X-Originating-IP: [65.94.104.44]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP576D6EAB2E61B66C7FA944D84E0@phx.gbl>
Received: from [192.168.2.17] ([65.94.104.44]) by BLU0-SMTP57.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 22 Jul 2011 12:42:00 -0700
Date: Fri, 22 Jul 2011 15:41:58 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Yiqun Cai <ycai@cisco.com>
References: <CA4E54C1.ADC9A%ycai@cisco.com>
In-Reply-To: <CA4E54C1.ADC9A%ycai@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Jul 2011 19:42:00.0683 (UTC) FILETIME=[6CABABB0:01CC48A7]
Cc: Multicast Transition <multrans@ietf.org>
Subject: Re: [multrans] List of work items
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, 22 Jul 2011 19:42:02 -0000

My personal view of the allocation of effort would be as follows:

MULTRANS: Problem statement, architecture, applicability statements 
(with Softwires and maybe Behave looking over our shoulders, depending 
on which transition mechanisms we document). I could see the possibility 
of some protocol development in MULTRANS, but not in the initial effort. 
I think there might be two waves of effort here, starting with the 
restrictions in the current version of the Problem Statement and then 
relaxing some of them (allowing a mixture of IPv4 and IPv6 endpoints 
which can be both sources and receivers). I'm not sure if the MIB work 
should be done here as a separate work item or tied into the 
applicability statements.

PIM: new IGMP/MLD/PIM interworking specifications.

BEHAVE: the multicast equivalent to RFC 6052.

Jacni and I have already disagreed on how the application to DS-Lite 
gets documented. I've drawn up an initial version of the multicast 
transition architecture document as I see it, and hope to get it on the 
table in the next few days so people can see what I have in mind. That 
document can make key contributions in discussion of operations and 
mangement and security issues associated with multicast transition.

On 22/07/2011 1:12 AM, Yiqun Cai wrote:
> Tina,
>
> I would like to suggest that you provide some reasoning and give some advice
> on what piece of work is best done in softwire, behave or multrans (if it
> becomes a working group).  I am sure this discussion will come up and it
> will be lively.
>
> Thanks.
>
> P.S.,  I would like to make the same comment for Tom too.
>
>
> On 7/21/11 9:21 PM, "Tina TSOU"<Tina.Tsou.Zouting@huawei.com>  wrote:
>
>> Hi all,
>> Attached is the presentation of List of work items.
>> Comments are welcome.
>>
>>
>> Best Regards,
>> Tina TSOU
>> http://tinatsou.weebly.com/contact.html
>>
>>
>> _______________________________________________
>> multrans mailing list
>> multrans@ietf.org
>> https://www.ietf.org/mailman/listinfo/multrans
>
>