Re: [multrans] Issues charts for presentation at the BoF
Tina Tsou <tena@huawei.com> Tue, 28 June 2011 17:13 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 31F98228015 for <multrans@ietfa.amsl.com>; Tue, 28 Jun 2011 10:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 SK69EykE-m8e for <multrans@ietfa.amsl.com>; Tue, 28 Jun 2011 10:13:16 -0700 (PDT)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by ietfa.amsl.com (Postfix) with ESMTP id 7F3C322800E for <multrans@ietf.org>; Tue, 28 Jun 2011 10:13:14 -0700 (PDT)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNI009GHFU1ZW@usaga03-in.huawei.com> for multrans@ietf.org; Tue, 28 Jun 2011 12:13:13 -0500 (CDT)
Received: from TingZousc1 ([12.207.18.43]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LNI00HFKFU01A@usaga03-in.huawei.com> for multrans@ietf.org; Tue, 28 Jun 2011 12:13:13 -0500 (CDT)
Date: Tue, 28 Jun 2011 10:13:12 -0700
From: Tina Tsou <tena@huawei.com>
In-reply-to: <010101cc35b4$8695c750$93c155f0$@com>
To: 'Dan Wing' <dwing@cisco.com>, 'Tom Taylor' <tom111.taylor@bell.net>, 'Jacni Qin' <jacniq@gmail.com>
Message-id: <018a01cc35b6$a9b80070$fd280150$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="utf-8"
Content-language: en-us
Content-transfer-encoding: quoted-printable
Thread-index: Acw1knC/60hbZ2juTDaxlpA+lHkTiQAIZpqgAACerJA=
References: <BLU0-SMTP581602B6944276BA936378D8570@phx.gbl> <BANLkTikEew1+36VpGHh2S-_=EywqRjzjBg@mail.gmail.com> <BLU0-SMTP466BD36F829964D1FA1F99D8560@phx.gbl> <010101cc35b4$8695c750$93c155f0$@com>
Cc: 'Multicast Transition' <multrans@ietf.org>
Subject: Re: [multrans] Issues charts for presentation at the BoF
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, 28 Jun 2011 17:13:17 -0000
We keep our promises with one another – no matter what! Best Regards, Tina TSOU http://tinatsou.weebly.com/contact.html -----Original Message----- From: multrans-bounces@ietf.org [mailto:multrans-bounces@ietf.org] On Behalf Of Dan Wing Sent: Tuesday, June 28, 2011 9:58 AM To: 'Tom Taylor'; 'Jacni Qin' Cc: 'Multicast Transition' Subject: Re: [multrans] Issues charts for presentation at the BoF > -----Original Message----- > From: multrans-bounces@ietf.org [mailto:multrans-bounces@ietf.org] On > Behalf Of Tom Taylor > Sent: Tuesday, June 28, 2011 5:54 AM > To: Jacni Qin > Cc: Multicast Transition > Subject: Re: [multrans] Issues charts for presentation at the BoF > > Thank you for your comments. Responses below. > > On 27/06/2011 10:45 PM, Jacni Qin wrote: > > hi Tom, > > > > Some comments, > > > > Page 8: > > Issue: translation of a given address tends to happen > > at multiple nodes, and at different stages within the > > same node. > > ● Need the same mapping or its inverse, as applicable, to be > > used each time a given address is translated. Implies inter- > > nodal coordination in some form. > > > > Jacni>: The coordination is probably required in the stateful > > translation. While in some stateless cases, maybe not. > > [PTT] I agree there is less coordination for stateless, but at least > the > different nodes have to be provisioned with the special prefix being > used to construct IPv4-embedded IPv6 addresses in this network. They need not necessarily be 'provisioned' (configured). They could learn the network's prefix for multicast translation. draft-ietf-behave-nat64-learn-analysis discussed a bunch of techniques for learning unicast NAT64; I expect almost all of those could be useful for multicast NAT64 (or multicast NAT46) and have pros/cons. [Tina: So what changes do you want to see from Page 8?] -d > > Page 9: > > Jacni>: I do agree with that the original design of DS-Lite or 6rd > > (unicast-based tunnel) > > should not be used for multicast delivery, but that can NOT lead to > the > > conclusion stated in the second bullet ("Possible to use > encapsulation in > > the form of a softwire mesh between multicast routers."). > > Mesh is a different use case, the mesh approaches do not apply to DS- > Lite or > > 6rd cases either. > > [PTT] I can drop the term "softwire mesh" and say simply that it is > possible to use tunnels between the multicast routers, if you want. But > isn't a mesh required to support the routing of the PIM signalling? I > thought I was using the term in the same sense as > draft-xu-softwire-mesh-multicast-01. > > > > > > Page 10: > > Jacni>: The discussions about dual-stack network are a little > confusing. The > > network may be dual-stack enabled from the device connected to > headends, to > > the IGMP/MLD Querier. > > Or the network may be partially dual-stack enabled. The latter one is > > "native transport + translation", and can be simplified as a > translation > > case. > > Please refer to the -01 of the PS draft, maybe some text in the > Section 3.3 > > can be reused: > > http://tools.ietf.org/html/draft-jaclee-behave-v4v6-mcast-ps-01#page- > 8 > > > [PTT] Page 10 deals with the specific case of a single dual stack > network between the sources and the receivers. I actually have mixed > versions in mind at both ends, although I know that IPv6 sources have > lower priority. So the intention is to indicate some strategies for > network operations under those particular assumptions. > > I think you are saying that this is not the use case that you are > pointing at in section 3.3 of the problem statement. I did not intend > it > to be so. What I should do is expand this page to two charts, giving > the > assumptions I just stated and adding the diagrams Dan suggested. > > > > Cheers, > > Jacni > > > > On Tue, Jun 28, 2011 at 4:13 AM, Tom Taylor<tom111.taylor@bell.net> > wrote: > > > >> Attached are the charts I propose should be presented on the > "issues" topic > >> at the MULTRANS BoF. Comments in advance are welcome. > >> > >> Tom Taylor > >> > >> _______________________________________________ > >> multrans mailing list > >> multrans@ietf.org > >> https://www.ietf.org/mailman/listinfo/multrans > >> > >> > > > _______________________________________________ > multrans mailing list > multrans@ietf.org > https://www.ietf.org/mailman/listinfo/multrans _______________________________________________ multrans mailing list multrans@ietf.org https://www.ietf.org/mailman/listinfo/multrans
- [multrans] Issues charts for presentation at the … Tom Taylor
- Re: [multrans] Issues charts for presentation at … Joel M. Halpern
- Re: [multrans] Issues charts for presentation at … Tom Taylor
- Re: [multrans] Issues charts for presentation at … Dan Wing
- Re: [multrans] Issues charts for presentation at … Lee, Yiu
- Re: [multrans] Issues charts for presentation at … Lee, Yiu
- Re: [multrans] Issues charts for presentation at … Dan Wing
- Re: [multrans] Issues charts for presentation at … Tom Taylor
- Re: [multrans] Issues charts for presentation at … Jacni Qin
- Re: [multrans] Issues charts for presentation at … Jacni Qin
- Re: [multrans] Issues charts for presentation at … Tom Taylor
- Re: [multrans] Issues charts for presentation at … Dan Wing
- Re: [multrans] Issues charts for presentation at … Tina Tsou
- Re: [multrans] Issues charts for presentation at … Dan Wing
- Re: [multrans] Issues charts for presentation at … Tom Taylor
- Re: [multrans] Issues charts for presentation at … Tina Tsou
- Re: [multrans] Issues charts for presentation at … Jacni Qin
- Re: [multrans] Issues charts for presentation at … Jacni Qin
- Re: [multrans] Issues charts for presentation at … Tina Tsou
- Re: [multrans] Issues charts for presentation at … Jacni Qin
- Re: [multrans] Issues charts for presentation at … Tom Taylor
- Re: [multrans] Issues charts for presentation at … Jacni Qin