
From rbonica@juniper.net  Mon Jun  4 12:10:57 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89EA811E80C0 for <mboned@ietfa.amsl.com>; Mon,  4 Jun 2012 12:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.491
X-Spam-Level: 
X-Spam-Status: No, score=-106.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 k-Qo4bJqLJFE for <mboned@ietfa.amsl.com>; Mon,  4 Jun 2012 12:10:56 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 84D5B11E80BA for <mboned@ietf.org>; Mon,  4 Jun 2012 12:10:56 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKT80IPd1uwec+oRC0b7E3AuR8LSMFuHCJ@postini.com; Mon, 04 Jun 2012 12:10:56 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 4 Jun 2012 12:09:53 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 4 Jun 2012 12:09:52 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Mon, 4 Jun 2012 15:09:46 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Mon, 4 Jun 2012 15:09:44 -0400
Thread-Topic: draft-ietf-mboned-64-multicast-address-format
Thread-Index: Ac1ChZn9QyZUW90HTS2vUwZeJ6aksA==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76C5D948E@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [MBONED] draft-ietf-mboned-64-multicast-address-format
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 19:10:57 -0000

All,

The 6man WG has requested that draft-ietf-mboned-64-multicast-address-forma=
t move from the MBONED WG to 6man. Their request is undeniable because:

- the 6man charter clearly includes maintenance of the IPv6 addressing sche=
me
- draft-ietf-mboned-64-multicast-address-format updates RFC 4291 (The IPv6 =
Addressing Scheme)

I have conferred with the MBONED chairs and they agree that the work falls =
clearly in the 6man charter. So, MBONED will cease work in this area and th=
e authors are asked to bring the problem to 6man.=20

--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf



From Tina.Tsou.Zouting@huawei.com  Mon Jun  4 21:44:56 2012
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37D6521F85FD for <mboned@ietfa.amsl.com>; Mon,  4 Jun 2012 21:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.439
X-Spam-Level: 
X-Spam-Status: No, score=-6.439 tagged_above=-999 required=5 tests=[AWL=0.160,  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 nS8BWglBqTfp for <mboned@ietfa.amsl.com>; Mon,  4 Jun 2012 21:44:54 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5B04721F84FA for <mboned@ietf.org>; Mon,  4 Jun 2012 21:44:54 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGP11896; Tue, 05 Jun 2012 00:44:54 -0400 (EDT)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 4 Jun 2012 21:41:11 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.80]) by dfweml404-hub.china.huawei.com ([10.193.5.203]) with mapi id 14.01.0323.003; Mon, 4 Jun 2012 21:41:08 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Leonard Giuliano <lenny@juniper.net>, MBONED WG <mboned@ietf.org>
Thread-Topic: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0olW4tpAJfzZWwTw2lKRKI4vlTgAGPwEowAN1yb4AEIrrosA==
Date: Tue, 5 Jun 2012 04:41:06 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A80D3C5CAC@dfweml513-mbx.china.huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <20120514132102.U91557@eng-mail01.juniper.net>
In-Reply-To: <20120514132102.U91557@eng-mail01.juniper.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.212.246.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 04:44:56 -0000

Well, gentlemen, how do you call it?

(1) WG accepts work item and=20
draft-tsou-mboned-multrans-addr-acquisition is a candidate;

(2) WG accepts work item and=20
draft-tsou-mboned-multrans-addr-acquisition is a candidate if rewritten; or

(3) WG does not accept work item.

Tina

> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf
> Of Leonard Giuliano
> Sent: Monday, May 14, 2012 1:24 PM
> To: MBONED WG
> Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
>=20
>=20
> We would like to poll the WG to decide if
> draft-tsou-mboned-multrans-addr-acquisition-01 should be adopted as an
> MBONED document.  Please respnd by May 29 if you thing this doc should or
> should not be adopted by MBONED.
>=20
>=20
> -MBONED Chairs
>=20
>=20
> On Thu, 10 May 2012, Tina TSOU wrote:
>=20
> -) Dear chairs,
> -) Would you ask the WG for adoption of draft-tsou-mboned-multrans-addr-
> acquisition-01 as WG document?
> -)
> -) Thank you and have a good day.
> -)
> -) Tina and co-authors
> -)
> -) From: Tina TSOU
> -) Sent: Wednesday, May 02, 2012 11:58 AM
> -) To: mboned@ietf.org
> -) Subject: draft-tsou-mboned-multrans-addr-acquisition-01
> -)
> -)
> -) Now that the multicast transition framework document is officially
> accepted, is the Working Group prepared also to take on the topic of
> address acquisition, which is one of the tasks it identifies?
> -) If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be
> acceptable as a starting point?
> -)
> -) Tina
> -)
> -)
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From gbumgard@cisco.com  Wed Jun  6 11:50:44 2012
Return-Path: <gbumgard@cisco.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1432221F8567 for <mboned@ietfa.amsl.com>; Wed,  6 Jun 2012 11:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 KlGAgll3ooFj for <mboned@ietfa.amsl.com>; Wed,  6 Jun 2012 11:50:43 -0700 (PDT)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id A930921F847E for <mboned@ietf.org>; Wed,  6 Jun 2012 11:50:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gbumgard@cisco.com; l=4688; q=dns/txt; s=iport; t=1339008637; x=1340218237; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=6vjFj1+rFRMV+frBQV7SXx4ofNZOyawRYMwM8wLEHYM=; b=P/NLA6dyXsLwmU7lJQtmJGHeotCccjmzzJC+KdzFRugS/MXqP6WWEGFC 0//AIr94HCNn28dOIxCL5zKfti3LQvlM5ff/ZatcLSCAkzuov4pUGvsbU hg2VMZ2ZKqQCg8ERZF9rE5eMaFuYYemra2V81g2nb/+b94Gd+QZG9uVpM s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EABqmz09Io8UY/2dsb2JhbABFtT2CGAEBAQMBAQEBDwFUBwsFBwQLEQQBAQEnByEGHwkIBhMih1sDBgULmFGWFw2JSgSKOGCFOWADiECMXYVThSuDFoFmgwA
X-IronPort-AV: E=Sophos;i="4.75,725,1330905600"; d="scan'208";a="13886241"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 06 Jun 2012 18:50:34 +0000
Received: from [10.20.185.152] (sjc-gbumgard-8917.cisco.com [10.20.185.152]) by bgl-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q56IoWFx006136; Wed, 6 Jun 2012 18:50:33 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Greg Bumgardner <gbumgard@cisco.com>
In-Reply-To: <9B30768B8155174FB7C6B21ABDCD24C001DC5DA8@GAALPA1MSGUSR9N.ITServices.sbc.com>
Date: Wed, 6 Jun 2012 11:50:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F51BA8F-1C20-484C-B42F-D6849064CAD8@cisco.com>
References: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com> <CABFReBof8GKz=yzmPxLGk+eTsUE20PYvZOyO9fqMcY8oFcwnow@mail.gmail.com> <9B30768B8155174FB7C6B21ABDCD24C001DC5DA8@GAALPA1MSGUSR9N.ITServices.sbc.com>
To: "SAYKO, ROBERT J" <rs1983@att.com>
X-Mailer: Apple Mail (2.1084)
Cc: mboned@ietf.org
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 18:50:44 -0000

Bob,

Thanks for the review. Comments below.

-g.b.

On May 31, 2012, at 9:45 AM, SAYKO, ROBERT J wrote:

> Greg, et al,
>=20
>=20
> Here are our comments.
>=20
>=20
> A) Our expectation is that multicast datagrams may be fragmented and =
contained in more than one AMT Data message.   The document seems pretty =
consistent that an AMT Multicast data message contains the entire IP =
multicast datagram is there a disconnect here?
>=20
> There are several places where this should be addressed:
>=20
> Section 4.2.1 "Multicast Data:  Sent by relays to deliver an =
encapsulated IP multicast datagram to a gateway"  =E0 ".. to deliver an =
encapsulated IP multicast datagram (or fragment thereof) to a gateway."
> Section 4.2.2.3 "each multicast IP datagram that arrives at the relay =
is encapsulated in an AMT message" =E0 "encapsulated in one or more AMT =
message"
> Section 5.1.6 "A relay sends a Multicast Data message to deliver an IP =
multicast packet" =E0 "sends one or more Multicast Data messages."
> Section 5.1.6.4 "A complete IPv4 or IPv6 Multicast datagram" =E0 "A =
complete or fragment of an IPv4 ."
>=20
I could probably have fixed this by changing datagram to packet, but I =
will do as you suggest and include fragment in the descriptions.
>=20
>=20
> B) Would like to recommend the following text from section "5.3.3.2. =
Handling a Relay Discovery Message":
>=20
> 	If the Relay Discovery message was received as an IPv4 datagram, =
the
> 	relay MUST return an IPv4 address in the Relay Address field of =
the
> 	Relay Advertisement message.  If the Relay Discovery message was
> 	received as an IPv6 datagram, the relay may return an IPv4 or =
IPv6
> 	address in the Relay Address field.
>=20
> included in section "5.1.2.5 Relay Address" as well. =20
>=20
>=20
> C) Would like to recommend some clarification regarding the "Response =
MAC" in the Teardown message.  Section "5.1.7.4. Response MAC" states:=20=

>=20
> 	A 48-bit value copied from the Response MAC field (Section =
5.1.4.6)
> 	in the last Membership Query message the relay sent to the =
gateway
> 	endpoint address of the tunnel to be torn down.  The gateway =
endpoint
> 	address is provided by the Gateway IP Address and Gateway Port =
Number
> 	fields carried by the Membership Query message.
>=20
> We believe this implies that the Relay will need to keep track of the =
last "Response MAC" sent to the Gateway.

I'm not sure why one would read it this way as other portions of the =
document indicate that the relay does NOT need to keep track of the =
Response MAC as the information required to compute and verify the value =
is carried by the Teardown message. The relay only uses the MAC to =
verify that the Teardown message was sent in response to an earlier =
Membership Query message. The only state maintained by the relay is the =
private secret used to generate recent Response MAC values.

>=20
>=20
> If this is the intention, then section "4.2.1.3. Teardown Sequence" =
bullet "8" and section "5.3.3.5. Handling a Teardown Message" should be =
updated accordingly. =20
>=20
> If this is not the intention, then section "5.1.7.4. Response MAC" =
should be reworded. =20

I will add a blub regarding the stateless-ness of the Response MAC.

>=20
>=20
> Regards,
> Bob Sayko and the AT&T AMT team.
>=20
> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On =
Behalf Of Greg Shepherd
> Sent: Monday, May 21, 2012 3:31 PM
> To: mboned@ietf.org
> Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
>=20
> We're half way through the 3 week WGLC for AMT and we've received no
> responses. Please read and respond ASAP so we can progress.
>=20
> Thanks,
> Greg
>=20
> On Thu, May 10, 2012 at 10:33 AM, Greg Shepherd <gjshep@gmail.com> =
wrote:
>> *,
>>=20
>> Yes, I think we may finally be here! The Paris and post-Paris
>> discussions were addressed in the finally rev so it is now time for
>> WGLC for draft-ietf-mboned-auto-multicast-13:
>>=20
>> https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/
>>=20
>> It is quite long so we'll give it three weeks for responses before
>> moving it along. Please respond by May 31st. And as always, we need
>> votes of approval as much as comments and issues. Let's see this
>> finally move to req pub!
>>=20
>> Thanks to everyone who has been involved throughout the past +decade. =
:p
>>=20
>> MBONED Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From gbumgard@cisco.com  Wed Jun  6 11:50:47 2012
Return-Path: <gbumgard@cisco.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7D5511E80AE for <mboned@ietfa.amsl.com>; Wed,  6 Jun 2012 11:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 al0S-n3AopNy for <mboned@ietfa.amsl.com>; Wed,  6 Jun 2012 11:50:46 -0700 (PDT)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD6D21F859B for <mboned@ietf.org>; Wed,  6 Jun 2012 11:50:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gbumgard@cisco.com; l=4688; q=dns/txt; s=iport; t=1339008645; x=1340218245; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=6vjFj1+rFRMV+frBQV7SXx4ofNZOyawRYMwM8wLEHYM=; b=b6WbbwKloNBACl/7YSwnNHxPGFzjvxU3G++63xeahWDZDMVo6h/i2wUT WBTTHdSAnHcoW1+yAu/JEjbEbhhMdUbhDNI0hApfQR4ANv0jMVQJNwXI/ bT+dKZL7HfEjSf7MVyVLlqiF08gEpu0SVrV0zkvUfIfGOBOI+0PqoFyIa o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EABqmz09Io8UY/2dsb2JhbABFtT2CGAEBAQMBAQEBDwFUBwsFBwQLEQQBAQEnByEGHwkIBhMih1sDBgULmFGWFw2JSgSKOGCFOWADiECMXYVThSuDFoFmgwA
X-IronPort-AV: E=Sophos;i="4.75,725,1330905600"; d="scan'208";a="13886864"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 06 Jun 2012 18:50:43 +0000
Received: from [10.20.185.152] (sjc-gbumgard-8917.cisco.com [10.20.185.152]) by bgl-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q56IoWG0006136; Wed, 6 Jun 2012 18:50:42 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Greg Bumgardner <gbumgard@cisco.com>
In-Reply-To: <9B30768B8155174FB7C6B21ABDCD24C001DC5DA8@GAALPA1MSGUSR9N.ITServices.sbc.com>
Date: Wed, 6 Jun 2012 11:50:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <59F2FB97-D19D-4E8A-9AB2-058ADB3EF92A@cisco.com>
References: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com> <CABFReBof8GKz=yzmPxLGk+eTsUE20PYvZOyO9fqMcY8oFcwnow@mail.gmail.com> <9B30768B8155174FB7C6B21ABDCD24C001DC5DA8@GAALPA1MSGUSR9N.ITServices.sbc.com>
To: "SAYKO, ROBERT J" <rs1983@att.com>
X-Mailer: Apple Mail (2.1084)
Cc: mboned@ietf.org
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 18:50:47 -0000

Bob,

Thanks for the review. Comments below.

-g.b.

On May 31, 2012, at 9:45 AM, SAYKO, ROBERT J wrote:

> Greg, et al,
>=20
>=20
> Here are our comments.
>=20
>=20
> A) Our expectation is that multicast datagrams may be fragmented and =
contained in more than one AMT Data message.   The document seems pretty =
consistent that an AMT Multicast data message contains the entire IP =
multicast datagram is there a disconnect here?
>=20
> There are several places where this should be addressed:
>=20
> Section 4.2.1 "Multicast Data:  Sent by relays to deliver an =
encapsulated IP multicast datagram to a gateway"  =E0 ".. to deliver an =
encapsulated IP multicast datagram (or fragment thereof) to a gateway."
> Section 4.2.2.3 "each multicast IP datagram that arrives at the relay =
is encapsulated in an AMT message" =E0 "encapsulated in one or more AMT =
message"
> Section 5.1.6 "A relay sends a Multicast Data message to deliver an IP =
multicast packet" =E0 "sends one or more Multicast Data messages."
> Section 5.1.6.4 "A complete IPv4 or IPv6 Multicast datagram" =E0 "A =
complete or fragment of an IPv4 ."
>=20
I could probably have fixed this by changing datagram to packet, but I =
will do as you suggest and include fragment in the descriptions.
>=20
>=20
> B) Would like to recommend the following text from section "5.3.3.2. =
Handling a Relay Discovery Message":
>=20
> 	If the Relay Discovery message was received as an IPv4 datagram, =
the
> 	relay MUST return an IPv4 address in the Relay Address field of =
the
> 	Relay Advertisement message.  If the Relay Discovery message was
> 	received as an IPv6 datagram, the relay may return an IPv4 or =
IPv6
> 	address in the Relay Address field.
>=20
> included in section "5.1.2.5 Relay Address" as well. =20
>=20
>=20
> C) Would like to recommend some clarification regarding the "Response =
MAC" in the Teardown message.  Section "5.1.7.4. Response MAC" states:=20=

>=20
> 	A 48-bit value copied from the Response MAC field (Section =
5.1.4.6)
> 	in the last Membership Query message the relay sent to the =
gateway
> 	endpoint address of the tunnel to be torn down.  The gateway =
endpoint
> 	address is provided by the Gateway IP Address and Gateway Port =
Number
> 	fields carried by the Membership Query message.
>=20
> We believe this implies that the Relay will need to keep track of the =
last "Response MAC" sent to the Gateway.

I'm not sure why one would read it this way as other portions of the =
document indicate that the relay does NOT need to keep track of the =
Response MAC as the information required to compute and verify the value =
is carried by the Teardown message. The relay only uses the MAC to =
verify that the Teardown message was sent in response to an earlier =
Membership Query message. The only state maintained by the relay is the =
private secret used to generate recent Response MAC values.

>=20
>=20
> If this is the intention, then section "4.2.1.3. Teardown Sequence" =
bullet "8" and section "5.3.3.5. Handling a Teardown Message" should be =
updated accordingly. =20
>=20
> If this is not the intention, then section "5.1.7.4. Response MAC" =
should be reworded. =20

I will add a blub regarding the stateless-ness of the Response MAC.

>=20
>=20
> Regards,
> Bob Sayko and the AT&T AMT team.
>=20
> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On =
Behalf Of Greg Shepherd
> Sent: Monday, May 21, 2012 3:31 PM
> To: mboned@ietf.org
> Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
>=20
> We're half way through the 3 week WGLC for AMT and we've received no
> responses. Please read and respond ASAP so we can progress.
>=20
> Thanks,
> Greg
>=20
> On Thu, May 10, 2012 at 10:33 AM, Greg Shepherd <gjshep@gmail.com> =
wrote:
>> *,
>>=20
>> Yes, I think we may finally be here! The Paris and post-Paris
>> discussions were addressed in the finally rev so it is now time for
>> WGLC for draft-ietf-mboned-auto-multicast-13:
>>=20
>> https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/
>>=20
>> It is quite long so we'll give it three weeks for responses before
>> moving it along. Please respond by May 31st. And as always, we need
>> votes of approval as much as comments and issues. Let's see this
>> finally move to req pub!
>>=20
>> Thanks to everyone who has been involved throughout the past +decade. =
:p
>>=20
>> MBONED Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From gbumgard@cisco.com  Wed Jun  6 12:39:45 2012
Return-Path: <gbumgard@cisco.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2429C21F889A for <mboned@ietfa.amsl.com>; Wed,  6 Jun 2012 12:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 GfDz7obqEkq0 for <mboned@ietfa.amsl.com>; Wed,  6 Jun 2012 12:39:43 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 6C0CD21F88B7 for <mboned@ietf.org>; Wed,  6 Jun 2012 12:39:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gbumgard@cisco.com; l=3581; q=dns/txt; s=iport; t=1339011583; x=1340221183; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=myXV2L5QRGCq+0lqEZt0AAP2hWw7oYA2tEvVjXH8rCk=; b=KHWB9XYoJJK6wQFKToNqHsiScmFZ42CJSR/Jy+UHjYuS1JMdv70o4VV2 AqMsgeYm7IBFOnLPeT8jhCbFmalHUS46/sq5zXO6pbVa+hJShAuKUPkI9 0uxLUoYYs/7hEqUY1+8zSJYy9bmOqadPzLynO35I3TjhF2OptOvjLmOND I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAJmxz0+rRDoI/2dsb2JhbABFtDaBB4IYAQEBAwEBAQEPASc0CwULC0YnMAYTIodkBAyYV59yBIsYhTlgA4hAjF2FU4hBgWaDAA
X-IronPort-AV: E=Sophos;i="4.75,725,1330905600"; d="scan'208";a="45347445"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 06 Jun 2012 19:39:43 +0000
Received: from [10.20.185.152] (sjc-gbumgard-8917.cisco.com [10.20.185.152]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q56JdgAl012457; Wed, 6 Jun 2012 19:39:42 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Greg Bumgardner <gbumgard@cisco.com>
In-Reply-To: <4FC6E255.7040500@gmail.com>
Date: Wed, 6 Jun 2012 12:39:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B65A35A8-2812-4D55-A39E-0F9DB89504AC@cisco.com>
References: <4FC6E255.7040500@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 19:39:45 -0000

Tom,

Thanks for the input. I'm always surprised at how many =
grammatical/typographic/cut&paste errors make it through each pass.

Additional comments below.

-g.b.

On May 30, 2012, at 8:15 PM, Tom Taylor wrote:

> I have reviewed the document and found it good to go. One substantive =
query: the last paragraph of section 5.3.3.2 says:
>=20
>  "If the Relay Discovery message was
>   received as an IPv6 datagram, the relay may return an IPv4 or IPv6
>   address in the Relay Address field."
>=20
> This seems to impose a requirement that any Gateway supporting IPv6 =
transport MUST also support IPv4. Is that the intention?
>=20
> Nits:
>=20
> 4.2.2.1 second para, first sentence: s/change/changes/ to agree with =
"address".
>=20
> 5.1.5 typos:
>=20
> - second para, first line: s/a receives/it receives/
>=20
> - third para end of third line: s/Message/Membership/ (Update message)
>=20
> 5.2.1 third para, third-last line: s/primary/primarily/
>=20
> 5.2.2.1 and 5.2.2.2: Don't these appear in reverse order of usage? I'd =
suggest taking the word "Static" out of the sub-section titles and =
reversing their order.
>=20
> 5.2.3.6.1 final paragraph seems out of place -- it refers to "the =
datagram", where that is not present in the immediately preceding text. =
I suggest moving the final paragraph up to precede the paragraph =
beginning: "A gateway that waits to start ...".

I reworded the last couple of paragraphs to indicate that messages are =
(conceptually) stored/queued/delivered as IP datagrams. I also changed =
the last paragraph:

"
   A gateway that waits to start a membership update cycle until after
   it receives a datagram containing an IGMP/MLD state-change message
   MAY:

   o  Discard IGMP or MLD datagrams until it receives a Membership Query
      message, at which time it processes the Membership Query message
      as normal to eventually produce a current-state report on the
      pseudo-interface which describes the end state (RECOMMENDED).

   o  Insert IGMP or MLD datagrams into a queue for transmission after
      it receives a Membership Query message.

   If and when a gateway receives a Membership Query message (for IGMP
   or MLD) it sends any queued or incoming IGMP or MLD datagrams to the
   relay as described in the next section.
"

>=20
> 5.3.1 fourth para, first line: s/,Section/in Section/
>=20
> 5.3.2: Should the second paragraph specify that the assigned addresses =
are globally reachable?

I intentionally avoiding including any requirements regarding =
reachability to allow for the possibility of intranet (vs internet) AMT =
deployment.

>=20
> 5.3.3.3:
> - eighth para (third down on p. 64), tenth line: missing text. That =
line and the one following currently read:
>=20
> "This exception is made because any address that a relay might may not
>                                                            ^^^^^
> be a valid source address on any gateway interface.  The rationale =
..."
>=20
> - second-last para, last sentence (top of p. 65):
>        s/a membership/membership/
>=20
> 5.3.3.4, third-last para: missing "of" between "form" and "group".
>=20
> 5.3.3.6 first para, last line: s/follow/following/
>=20
> 5.3.3.8 last para, second line: s/reach/reached/
>=20
> 7.1.1 second para: missing space
>=20
> I didn't check the Appendix.
>=20
> Tom Taylor
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From gbumgard@cisco.com  Wed Jun  6 16:34:23 2012
Return-Path: <gbumgard@cisco.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B02B21F864C for <mboned@ietfa.amsl.com>; Wed,  6 Jun 2012 16:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 omWS88RtiV5q for <mboned@ietfa.amsl.com>; Wed,  6 Jun 2012 16:34:21 -0700 (PDT)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id 0CA9021F8634 for <mboned@ietf.org>; Wed,  6 Jun 2012 16:34:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gbumgard@cisco.com; l=2755; q=dns/txt; s=iport; t=1339025645; x=1340235245; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=bvlj3TjhoKiZuDGlcCK/dMOJkc5csmpWdRgYv34a5Zo=; b=TA42Z9trqjTLPY8uBQ4uDUkg8adj7J842CvLWNABOfGPahysRh5V8tRL vjAheAS37UjtYq+bxxULLk6cgr4NHThCXMYvphvpB4dMAI80rbhTgm7od i8H0vQgbIgNIr62W8cOeZLq+4iEec8tyaUmb8GSwpKA8F00fSacgHabxX 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EABToz09Io8UY/2dsb2JhbABFtUKCGAEBAQMBAQEBDwEnNAsFBwQLEQQBASgHJx8JCAYTIodkBQuYa59sBIsYhSlgA4hAjF2FU4hBgWaDAA
X-IronPort-AV: E=Sophos;i="4.75,726,1330905600"; d="scan'208";a="13892783"
Received: from vla196-nat.cisco.com (HELO bgl-core-1.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 06 Jun 2012 23:34:03 +0000
Received: from [10.20.185.152] (sjc-gbumgard-8917.cisco.com [10.20.185.152]) by bgl-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q56NY0hm021980; Wed, 6 Jun 2012 23:34:01 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Greg Bumgardner <gbumgard@cisco.com>
In-Reply-To: <189716C74BBB9C4095FE8CA503B1FC3A59241537C0@EMBX02-HQ.jnpr.net>
Date: Wed, 6 Jun 2012 16:34:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5958EE3-7B35-48E7-8E6D-4A2A5A7D2C2F@cisco.com>
References: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com> <189716C74BBB9C4095FE8CA503B1FC3A59241537C0@EMBX02-HQ.jnpr.net>
To: Kurt Windisch <kurtw@juniper.net>
X-Mailer: Apple Mail (2.1084)
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 23:34:23 -0000

Kurt,

Comments below...

Thanks,

-g.b.

On May 30, 2012, at 5:35 PM, Kurt Windisch wrote:

> Sorry for the 11th-hour response to this WGLC.
>=20
> I do have a couple of comments:
>=20
> 1. The IGMPv3 spec calls for the type-of-service bit for IP control to =
be set on all IGMP packets (section 4 of RFC 3376, "Every IGMP message =
described in this document is sent with ... IP Precedence of =
Internetwork Control (e.g., Type of Service 0xc0) ...". It seems logical =
that IPv4 AMT control messages should have the same TOS as the control =
packets that they encapsulate. Thus, I'd like to suggest that all IPv4 =
AMT control packets (AMT packets EXCEPT the AMT Data packet) should have =
TOS 0xc0.=20
>=20

I'm not set against making this change, but I do want to point out that =
some gateways will not be able to set the TOS (at all or to this value), =
so this would definitely be a SHOULD or MAY requirement.  If we were to =
apply this rule to encapsulated IGMP packets, then shouldn't we be doing =
the same for encapsulated MLD packets (even though the MLD spec(s) do =
not appear to set forth any requirements regarding IPv6 traffic class)?

> 2. (nit) In the new text of section 5.2.3.5.4, it states: The IGMP and =
MLD protocol specifications indicate that senders should use a =
link-local source IP address in message datagrams." This is incorrect =
since it is only applies to MLD and only the MLD specs make such a =
statement.
>=20
> I don't see any problems with the rest of the document or changes.
>=20
> Thanks
> --Kurt
>=20
> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On =
Behalf Of Greg Shepherd
> Sent: Thursday, May 10, 2012 10:33 AM
> To: mboned@ietf.org
> Subject: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
>=20
> *,
>=20
> Yes, I think we may finally be here! The Paris and post-Paris
> discussions were addressed in the finally rev so it is now time for
> WGLC for draft-ietf-mboned-auto-multicast-13:
>=20
> https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/
>=20
> It is quite long so we'll give it three weeks for responses before
> moving it along. Please respond by May 31st. And as always, we need
> votes of approval as much as comments and issues. Let's see this
> finally move to req pub!
>=20
> Thanks to everyone who has been involved throughout the past +decade. =
:p
>=20
> MBONED Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From gbumgard@cisco.com  Wed Jun  6 17:22:47 2012
Return-Path: <gbumgard@cisco.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C85DD21F85B4 for <mboned@ietfa.amsl.com>; Wed,  6 Jun 2012 17:22:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.409
X-Spam-Level: 
X-Spam-Status: No, score=-9.409 tagged_above=-999 required=5 tests=[AWL=-1.191, BAYES_00=-2.599, HTML_COMMENT_SAVED_URL=0.114, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_HI=-8, SARE_HTML_SINGLETS=1.666]
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 WVJbhDol8pS7 for <mboned@ietfa.amsl.com>; Wed,  6 Jun 2012 17:22:43 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 300E021F85AE for <mboned@ietf.org>; Wed,  6 Jun 2012 17:22:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gbumgard@cisco.com; l=142980; q=dns/txt; s=iport; t=1339028561; x=1340238161; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=BGxWDXeD3WY6mlJbnvnwar289ri5dKERRhm55jlSS98=; b=Hlqj3dwQ1bGdML/wRWXIjbls4mZyu0GOt98FWgNtD0STUepgvsctbU1L tAPrXwGr4HBOvwLIyDLBpaJg741gniwv3LOulliHvWgLFMMAJVhE/C8NU Ac6ZYyEu3vu9x83B6m7cbQ0uE6dhY4Nj1YeFrDnvYhTEhHmGucUDSNAKm 8=;
X-Files: diff-draft-ietf-mboned-auto-multicast-13v14.html : 140746
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlcFAIjzz0+rRDoH/2dsb2JhbABFiC6jAQGIe4EHghkBAQQBAQEPAQcBEjoHBgUQCxImAQ0nIg4GEyKHaAyYcJ9tixgUhRVgA4hAhXeGZoEShEGIQYFmgS2BU4E2AgUe
X-IronPort-AV: E=Sophos;i="4.75,726,1330905600";  d="html'217?scan'217,208,217";a="47885452"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 07 Jun 2012 00:22:39 +0000
Received: from [10.20.185.152] (sjc-gbumgard-8917.cisco.com [10.20.185.152]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q570Mco4015542; Thu, 7 Jun 2012 00:22:38 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/mixed; boundary=Apple-Mail-22--55894346
From: Greg Bumgardner <gbumgard@cisco.com>
In-Reply-To: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com>
Date: Wed, 6 Jun 2012 17:22:38 -0700
Message-Id: <E4321BB1-F286-4AC9-B1F9-F2622AA07375@cisco.com>
References: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com>
To: "mboned@ietf.org WG" <mboned@ietf.org>
X-Mailer: Apple Mail (2.1084)
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 00:22:47 -0000

--Apple-Mail-22--55894346
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

All,

I have made changes to the draft based on WGLC comments. I would like =
those of you who responded to take a look at the attached diff to see if =
the changes are satisfactory. I would like to publish draft #14 in the =
next day or so.

Thanks,=20

-g.b.

--Apple-Mail-22--55894346
Content-Disposition: attachment;
	filename=diff-draft-ietf-mboned-auto-multicast-13v14.html
Content-Type: text/html;
	name="diff-draft-ietf-mboned-auto-multicast-13v14.html"
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- saved from url=(0029)http://tools.ietf.org/rfcdiff -->
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> 
   
  <meta http-equiv="Content-Style-Type" content="text/css"> 
  <title>Diff: draft-ietf-mboned-auto-multicast-13final.txt - draft-ietf-mboned-auto-multicast-14pre1.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body> 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tbody><tr bgcolor="orange"><th></th><th><a href="http://tools.ietf.org/rfcdiff?url2=draft-ietf-mboned-auto-multicast-13final.txt" style="color:#008; text-decoration:none;">&lt;</a>&nbsp;<a href="http://tools.ietf.org/html/draft-ietf-mboned-auto-multicast-13final.txt" style="color:#008">draft-ietf-mboned-auto-multicast-13final.txt</a>&nbsp;</th><th> </th><th>&nbsp;<a href="http://tools.ietf.org/html/draft-ietf-mboned-auto-multicast-14pre1.txt" style="color:#008">draft-ietf-mboned-auto-multicast-14pre1.txt</a>&nbsp;<a href="http://tools.ietf.org/rfcdiff?url1=draft-ietf-mboned-auto-multicast-14pre1.txt" style="color:#008; text-decoration:none;">&gt;</a></th><th></th></tr> 
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Network Working Group                                      G. Bumgardner</td><td> </td><td class="right">Network Working Group                                      G. Bumgardner</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Internet-Draft                                                     Cisco</td><td> </td><td class="right">Internet-Draft                                                     Cisco</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Intended status: Standards Track                          <span class="delete">April 23,</span> 2012</td><td> </td><td class="rblock">Intended status: Standards Track                            <span class="insert">June 6,</span> 2012</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: <span class="delete">October 25,</span> 2012</td><td> </td><td class="rblock">Expires: <span class="insert">December 8,</span> 2012</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                     Automatic Multicast Tunneling</td><td> </td><td class="right">                     Automatic Multicast Tunneling</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                  draft-ietf-mboned-auto-multicast-1<span class="delete">3</span></td><td> </td><td class="rblock">                  draft-ietf-mboned-auto-multicast-1<span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document describes Automatic Multicast Tunneling (AMT), a</td><td> </td><td class="right">   This document describes Automatic Multicast Tunneling (AMT), a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   protocol for delivering multicast traffic from sources in a</td><td> </td><td class="right">   protocol for delivering multicast traffic from sources in a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   multicast-enabled network to receivers that lack multicast</td><td> </td><td class="right">   multicast-enabled network to receivers that lack multicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   connectivity to the source network.  The protocol uses UDP</td><td> </td><td class="right">   connectivity to the source network.  The protocol uses UDP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   encapsulation and unicast replication to provide this functionality.</td><td> </td><td class="right">   encapsulation and unicast replication to provide this functionality.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The AMT protocol is specifically designed to support rapid deployment</td><td> </td><td class="right">   The AMT protocol is specifically designed to support rapid deployment</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l2"><small>skipping to change at</small><em> page 1, line 37</em></a></th><th> </th><th><a name="part-r2"><small>skipping to change at</small><em> page 1, line 37</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right">   Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right">   and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   time.  It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right">   time.  It is inappropriate to use Internet-Drafts as reference</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   material or to cite them other than as "work in progress."</td><td> </td><td class="right">   material or to cite them other than as "work in progress."</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">October 25</span>, 2012.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">December 8</span>, 2012.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Copyright (c) 2012 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2012 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l3"><small>skipping to change at</small><em> page 2, line 33</em></a></th><th> </th><th><a name="part-r3"><small>skipping to change at</small><em> page 2, line 33</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   2.  Applicability  . . . . . . . . . . . . . . . . . . . . . . . .  4</td><td> </td><td class="right">   2.  Applicability  . . . . . . . . . . . . . . . . . . . . . . . .  4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     3.1.  Requirements Notation  . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">     3.1.  Requirements Notation  . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     3.2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">     3.2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     3.3.  Abbreviations  . . . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">     3.3.  Abbreviations  . . . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   4.  Protocol Overview  . . . . . . . . . . . . . . . . . . . . . .  8</td><td> </td><td class="right">   4.  Protocol Overview  . . . . . . . . . . . . . . . . . . . . . .  8</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     4.1.  General Architecture . . . . . . . . . . . . . . . . . . .  8</td><td> </td><td class="right">     4.1.  General Architecture . . . . . . . . . . . . . . . . . . .  8</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     4.2.  General Operation  . . . . . . . . . . . . . . . . . . . . 17</td><td> </td><td class="right">     4.2.  General Operation  . . . . . . . . . . . . . . . . . . . . 17</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   5.  Protocol Description . . . . . . . . . . . . . . . . . . . . . 32</td><td> </td><td class="right">   5.  Protocol Description . . . . . . . . . . . . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     5.1.  Protocol Messages  . . . . . . . . . . . . . . . . . . . . 32</td><td> </td><td class="right">     5.1.  Protocol Messages  . . . . . . . . . . . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     5.2.  Gateway Operation  . . . . . . . . . . . . . . . . . . . . <span class="delete">46</span></td><td> </td><td class="rblock">     5.2.  Gateway Operation  . . . . . . . . . . . . . . . . . . . . <span class="insert">47</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     5.3.  Relay Operation  . . . . . . . . . . . . . . . . . . . . . <span class="delete">61</span></td><td> </td><td class="rblock">     5.3.  Relay Operation  . . . . . . . . . . . . . . . . . . . . . <span class="insert">62</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . <span class="delete">72</span></td><td> </td><td class="rblock">   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . <span class="insert">73</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="delete">75</span></td><td> </td><td class="rblock">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="insert">76</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     7.2.  IPv4 Address Prefix Allocation for IGMP Source</td><td> </td><td class="right">     7.2.  IPv4 Address Prefix Allocation for IGMP Source</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">           Addresses  . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">75</span></td><td> </td><td class="rblock">           Addresses  . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">76</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   8.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">76</span></td><td> </td><td class="rblock">   8.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">77</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">77</span></td><td> </td><td class="rblock">   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">78</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">78</span></td><td> </td><td class="rblock">   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">79</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     10.1. Normative References . . . . . . . . . . . . . . . . . . . <span class="delete">78</span></td><td> </td><td class="rblock">     10.1. Normative References . . . . . . . . . . . . . . . . . . . <span class="insert">79</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     10.2. Informative References . . . . . . . . . . . . . . . . . . <span class="delete">78</span></td><td> </td><td class="rblock">     10.2. Informative References . . . . . . . . . . . . . . . . . . <span class="insert">79</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix A.  Implementation Notes  . . . . . . . . . . . . . . . . <span class="delete">81</span></td><td> </td><td class="rblock">   Appendix A.  Implementation Notes  . . . . . . . . . . . . . . . . <span class="insert">82</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">84</span></td><td> </td><td class="rblock">   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">85</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The advantages and benefits provided by multicast technologies are</td><td> </td><td class="right">   The advantages and benefits provided by multicast technologies are</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   well known.  There are a number of application areas that are ideal</td><td> </td><td class="right">   well known.  There are a number of application areas that are ideal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   candidates for the use of multicast, including media broadcasting,</td><td> </td><td class="right">   candidates for the use of multicast, including media broadcasting,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   video conferencing, collaboration, real-time data feeds, data</td><td> </td><td class="right">   video conferencing, collaboration, real-time data feeds, data</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   replication, and software updates.  Unfortunately, many of these</td><td> </td><td class="right">   replication, and software updates.  Unfortunately, many of these</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   applications lack multicast connectivity to networks that carry</td><td> </td><td class="right">   applications lack multicast connectivity to networks that carry</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   traffic generated by multicast sources.  The reasons for the lack of</td><td> </td><td class="right">   traffic generated by multicast sources.  The reasons for the lack of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l4"><small>skipping to change at</small><em> page 17, line 35</em></a></th><th> </th><th><a name="part-r4"><small>skipping to change at</small><em> page 17, line 35</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Query:</td><td> </td><td class="right">   Membership Query:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Sent by relays as a response to a Request message.  Used to</td><td> </td><td class="right">      Sent by relays as a response to a Request message.  Used to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      deliver an encapsulated IGMPv3 or MLDv2 query message to the</td><td> </td><td class="right">      deliver an encapsulated IGMPv3 or MLDv2 query message to the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      gateway.</td><td> </td><td class="right">      gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Update:</td><td> </td><td class="right">   Membership Update:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Sent by gateways to deliver an encapsulated IGMP or MLD report/</td><td> </td><td class="right">      Sent by gateways to deliver an encapsulated IGMP or MLD report/</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      leave/done message to a relay.</td><td> </td><td class="right">      leave/done message to a relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Multicast Data:</td><td> </td><td class="right">   Multicast Data:</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      Sent by relays to deliver an encapsulated IP multicast datagram to</td><td> </td><td class="rblock">      Sent by relays to deliver an encapsulated IP multicast datagram <span class="insert">or</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      a gateway.</td><td> </td><td class="rblock"><span class="insert">      datagram fragment</span> to a gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Teardown:</td><td> </td><td class="right">   Teardown:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Sent by gateways to stop the delivery of Multicast Data messages</td><td> </td><td class="right">      Sent by gateways to stop the delivery of Multicast Data messages</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      requested in an earlier Membership Update message.</td><td> </td><td class="right">      requested in an earlier Membership Update message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The following sections describe how these messages are exchanged to</td><td> </td><td class="right">   The following sections describe how these messages are exchanged to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   execute the protocol.</td><td> </td><td class="right">   execute the protocol.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.2.1.1.  Relay Discovery Sequence</td><td> </td><td class="right">4.2.1.1.  Relay Discovery Sequence</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l5"><small>skipping to change at</small><em> page 28, line 37</em></a></th><th> </th><th><a name="part-r5"><small>skipping to change at</small><em> page 28, line 37</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   UDP/IP address-port pair provided by the Membership Update message.</td><td> </td><td class="right">   UDP/IP address-port pair provided by the Membership Update message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.2.2.1.  Address Roaming</td><td> </td><td class="right">4.2.2.1.  Address Roaming</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   As described above, each time a relay receives a Membership Update</td><td> </td><td class="right">   As described above, each time a relay receives a Membership Update</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   message from a new source address-port pair, the group subscriptions</td><td> </td><td class="right">   message from a new source address-port pair, the group subscriptions</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   described by that message apply to the tunnel endpoint identified by</td><td> </td><td class="right">   described by that message apply to the tunnel endpoint identified by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   that address.</td><td> </td><td class="right">   that address.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This can cause problems for a gateway if the address carried by the</td><td> </td><td class="right">   This can cause problems for a gateway if the address carried by the</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0007"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   messages it sends to a relay change unexpectedly.  These changes may</td><td> </td><td class="rblock">   messages it sends to a relay change<span class="insert">s</span> unexpectedly.  These changes may</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   cause the relay to transmit duplicate, undeliverable or unrequested</td><td> </td><td class="right">   cause the relay to transmit duplicate, undeliverable or unrequested</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   traffic back towards the gateway or an intermediate device.  This may</td><td> </td><td class="right">   traffic back towards the gateway or an intermediate device.  This may</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   create congestion and have negative consequences for the gateway, its</td><td> </td><td class="right">   create congestion and have negative consequences for the gateway, its</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   network, or multicast receivers, and in some cases, may also produce</td><td> </td><td class="right">   network, or multicast receivers, and in some cases, may also produce</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   a significant amount of ICMP traffic directed back towards the relay</td><td> </td><td class="right">   a significant amount of ICMP traffic directed back towards the relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   by a NAT, router or gateway host.</td><td> </td><td class="right">   by a NAT, router or gateway host.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   There are several scenarios in which the address carried by messages</td><td> </td><td class="right">   There are several scenarios in which the address carried by messages</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   sent by a gateway may change without that gateway's knowledge, as for</td><td> </td><td class="right">   sent by a gateway may change without that gateway's knowledge, as for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   example, when:</td><td> </td><td class="right">   example, when:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l6"><small>skipping to change at</small><em> page 30, line 42</em></a></th><th> </th><th><a name="part-r6"><small>skipping to change at</small><em> page 30, line 42</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   |       |&lt;--------------------------------------------------|       |</td><td> </td><td class="right">   |       |&lt;--------------------------------------------------|       |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   |_______|  ^  |___|  ^  |___|__|  ^  |__|___|  ^  |___|  ^  |_______|</td><td> </td><td class="right">   |_______|  ^  |___|  ^  |___|__|  ^  |__|___|  ^  |___|  ^  |_______|</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              |         |            |            |         |</td><td> </td><td class="right">              |         |            |            |         |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">             IP      AMT:IP    IP:UDP:AMT:IP    AMT:IP      IP</td><td> </td><td class="right">             IP      AMT:IP    IP:UDP:AMT:IP    AMT:IP      IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                             AMT Encapsulation</td><td> </td><td class="right">                             AMT Encapsulation</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The IGMP and MLD messages used in AMT are exchanged as complete IP</td><td> </td><td class="right">   The IGMP and MLD messages used in AMT are exchanged as complete IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   datagrams.  These IP datagrams are encapsulated in AMT messages that</td><td> </td><td class="right">   datagrams.  These IP datagrams are encapsulated in AMT messages that</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   are transmitted using UDP.  The same holds true for multicast traffic</td><td> </td><td class="right">   are transmitted using UDP.  The same holds true for multicast traffic</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0008"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   - each multicast IP datagram that arrives at the relay is</td><td> </td><td class="rblock">   - each multicast IP datagram <span class="insert">or datagram fragment</span> that arrives at the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   encapsulated in an AMT message and transmitted to one or more</td><td> </td><td class="rblock">   relay is encapsulated in an AMT message and transmitted to one or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   gateways via UDP.</td><td> </td><td class="rblock">   more gateways via UDP.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The IP protocol of the encapsulated packets need not match the IP</td><td> </td><td class="right">   The IP protocol of the encapsulated packets need not match the IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   protocol used to send the AMT messages.  AMT messages sent via IPv4</td><td> </td><td class="right">   protocol used to send the AMT messages.  AMT messages sent via IPv4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   may carry IPv6/MLD packets and AMT messages sent via IPv6 may carry</td><td> </td><td class="right">   may carry IPv6/MLD packets and AMT messages sent via IPv6 may carry</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IPv4/IGMP packets.</td><td> </td><td class="right">   IPv4/IGMP packets.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The checksum field contained in the UDP header of the messages</td><td> </td><td class="right">   The checksum field contained in the UDP header of the messages</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   requires special consideration.  Of primary concern is the cost of</td><td> </td><td class="right">   requires special consideration.  Of primary concern is the cost of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   computing a checksum on each replicated multicast packet after it is</td><td> </td><td class="right">   computing a checksum on each replicated multicast packet after it is</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   encapsulated for delivery to a gateway.  Many routing/forwarding</td><td> </td><td class="right">   encapsulated for delivery to a gateway.  Many routing/forwarding</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l7"><small>skipping to change at</small><em> page 35, line 17</em></a></th><th> </th><th><a name="part-r7"><small>skipping to change at</small><em> page 35, line 17</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A 32-bit value copied from the Discovery Nonce field</td><td> </td><td class="right">   A 32-bit value copied from the Discovery Nonce field</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 5.1.1.4) contained in the Relay Discovery message.  The</td><td> </td><td class="right">   (Section 5.1.1.4) contained in the Relay Discovery message.  The</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateway uses this value to match a Relay Advertisement to a Relay</td><td> </td><td class="right">   gateway uses this value to match a Relay Advertisement to a Relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Discovery message.</td><td> </td><td class="right">   Discovery message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.2.5.  Relay Address</td><td> </td><td class="right">5.1.2.5.  Relay Address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The unicast IPv4 or IPv6 address of the relay.  A gateway uses the</td><td> </td><td class="right">   The unicast IPv4 or IPv6 address of the relay.  A gateway uses the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   length of the UDP datagram containing the Relay Advertisement message</td><td> </td><td class="right">   length of the UDP datagram containing the Relay Advertisement message</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   to determine the address family; i.e. length - 8 = 4 (IPv4) or 16</td><td> </td><td class="right">   to determine the address family; i.e. length - 8 = 4 (IPv4) or 16</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0009"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   (IPv6).</td><td> </td><td class="rblock">   (IPv6).  <span class="insert">The relay returns an IP address for the protocol used to</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   send the Relay Discovery message, i.e. an IPv4 relay address for an</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   IPv4 discovery address or an IPv6 relay address for an IPv6 discovery</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   address.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.3.  Request</td><td> </td><td class="right">5.1.3.  Request</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway sends a Request message to a relay to solicit a Membership</td><td> </td><td class="right">   A gateway sends a Request message to a relay to solicit a Membership</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Query response.</td><td> </td><td class="right">   Query response.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The successful delivery of this message marks the start of the first</td><td> </td><td class="right">   The successful delivery of this message marks the start of the first</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   stage in the three-way handshake used to create or update state</td><td> </td><td class="right">   stage in the three-way handshake used to create or update state</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   within a relay.</td><td> </td><td class="right">   within a relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l8"><small>skipping to change at</small><em> page 42, line 34</em></a></th><th> </th><th><a name="part-r8"><small>skipping to change at</small><em> page 43, line 22</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      IPv6:MLDv1 Multicast Listener Done</td><td> </td><td class="right">      IPv6:MLDv1 Multicast Listener Done</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      IPv6:MLDv2 Multicast Listener Report</td><td> </td><td class="right">      IPv6:MLDv2 Multicast Listener Report</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The source address carried by the message should be set as described</td><td> </td><td class="right">   The source address carried by the message should be set as described</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   in Section 5.2.1.</td><td> </td><td class="right">   in Section 5.2.1.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.6.  Multicast Data</td><td> </td><td class="right">5.1.6.  Multicast Data</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0010"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   A relay sends a Multicast Data message to deliver an <span class="delete">IP</span> multicast</td><td> </td><td class="rblock">   A relay sends a Multicast Data message to deliver an multicast <span class="insert">IP</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">packet</span> to a gateway.</td><td> </td><td class="rblock"><span class="insert">   datagram or datagram fragment</span> to a gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The checksum field in the UDP header of this message MAY contain a</td><td> </td><td class="right">   The checksum field in the UDP header of this message MAY contain a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   value of zero when sent over IPv4 but SHOULD, if possible, contain a</td><td> </td><td class="right">   value of zero when sent over IPv4 but SHOULD, if possible, contain a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   valid, non-zero value when sent over IPv6 (See Section 4.2.2.3).</td><td> </td><td class="right">   valid, non-zero value when sent over IPv6 (See Section 4.2.2.3).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The UDP/IP datagram containing this message MUST carry the following</td><td> </td><td class="right">   The UDP/IP datagram containing this message MUST carry the following</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IP address and UDP port values:</td><td> </td><td class="right">   IP address and UDP port values:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Source IP Address -  The unicast IP address of the relay.</td><td> </td><td class="right">   Source IP Address -  The unicast IP address of the relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l9"><small>skipping to change at</small><em> page 43, line 40</em></a></th><th> </th><th><a name="part-r9"><small>skipping to change at</small><em> page 44, line 34</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The type number for this message is 6.</td><td> </td><td class="right">   The type number for this message is 6.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.6.3.  Reserved</td><td> </td><td class="right">5.1.6.3.  Reserved</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Bits that MUST be set to zero by the relay and ignored by the</td><td> </td><td class="right">   Bits that MUST be set to zero by the relay and ignored by the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateway.</td><td> </td><td class="right">   gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.6.4.  IP Multicast Data</td><td> </td><td class="right">5.1.6.4.  IP Multicast Data</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0011"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   A complete IPv4 or IPv6 <span class="delete">Multicast datagram</span>.</td><td> </td><td class="rblock">   A complete IPv4 or IPv6 <span class="insert">multicast datagram or datagram fragment</span>.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.7.  Teardown</td><td> </td><td class="right">5.1.7.  Teardown</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway sends a Teardown message to a relay to request that it stop</td><td> </td><td class="right">   A gateway sends a Teardown message to a relay to request that it stop</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   sending Multicast Data messages to a tunnel endpoint created by an</td><td> </td><td class="right">   sending Multicast Data messages to a tunnel endpoint created by an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   earlier Membership Update message.  A gateway sends this message when</td><td> </td><td class="right">   earlier Membership Update message.  A gateway sends this message when</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   it detects that a Request message sent to the relay carries an</td><td> </td><td class="right">   it detects that a Request message sent to the relay carries an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address that differs from that carried by a previous Request message.</td><td> </td><td class="right">   address that differs from that carried by a previous Request message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The gateway uses the Gateway IP Address and Gateway Port Number</td><td> </td><td class="right">   The gateway uses the Gateway IP Address and Gateway Port Number</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Fields in the Membership Query message to detect these address</td><td> </td><td class="right">   Fields in the Membership Query message to detect these address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l10"><small>skipping to change at</small><em> page 45, line 24</em></a></th><th> </th><th><a name="part-r10"><small>skipping to change at</small><em> page 46, line 16</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Reserved bits that MUST be set to zero by the gateway and ignored by</td><td> </td><td class="right">   Reserved bits that MUST be set to zero by the gateway and ignored by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the relay.</td><td> </td><td class="right">   the relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.7.4.  Response MAC</td><td> </td><td class="right">5.1.7.4.  Response MAC</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A 48-bit value copied from the Response MAC field (Section 5.1.4.6)</td><td> </td><td class="right">   A 48-bit value copied from the Response MAC field (Section 5.1.4.6)</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   in the last Membership Query message the relay sent to the gateway</td><td> </td><td class="right">   in the last Membership Query message the relay sent to the gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   endpoint address of the tunnel to be torn down.  The gateway endpoint</td><td> </td><td class="right">   endpoint address of the tunnel to be torn down.  The gateway endpoint</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address is provided by the Gateway IP Address and Gateway Port Number</td><td> </td><td class="right">   address is provided by the Gateway IP Address and Gateway Port Number</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0012"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   fields carried by the Membership Query message.</td><td> </td><td class="rblock">   fields carried by the Membership Query message.  <span class="insert">The relay validates</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   the Teardown message by comparing this value with one computed from</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   the Request Nonce, Gateway Port Number and Gateway IP Address fields</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   (just as it does in the Membership Update message).</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.7.5.  Request Nonce</td><td> </td><td class="right">5.1.7.5.  Request Nonce</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A 32-bit value copied from the Request Nonce field (Section 5.1.4.7)</td><td> </td><td class="right">   A 32-bit value copied from the Request Nonce field (Section 5.1.4.7)</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   in the last Membership Query message the relay sent to the gateway</td><td> </td><td class="right">   in the last Membership Query message the relay sent to the gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   endpoint address of the tunnel to be torn down.  The gateway endpoint</td><td> </td><td class="right">   endpoint address of the tunnel to be torn down.  The gateway endpoint</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address is provided by the Gateway IP Address and Gateway Port Number</td><td> </td><td class="right">   address is provided by the Gateway IP Address and Gateway Port Number</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   fields carried by the Membership Query message.  This value must</td><td> </td><td class="right">   fields carried by the Membership Query message.  This value must</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   match that used by the relay to compute the value stored in the</td><td> </td><td class="right">   match that used by the relay to compute the value stored in the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Response MAC field.</td><td> </td><td class="right">   Response MAC field.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l11"><small>skipping to change at</small><em> page 46, line 48</em></a></th><th> </th><th><a name="part-r11"><small>skipping to change at</small><em> page 47, line 42</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   options and header values called for in [RFC3376], with the following</td><td> </td><td class="right">   options and header values called for in [RFC3376], with the following</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   exception; the source IP address for an IGMP report datagram MAY be</td><td> </td><td class="right">   exception; the source IP address for an IGMP report datagram MAY be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   set to the "unspecified" address (all octets are zero ) but SHOULD be</td><td> </td><td class="right">   set to the "unspecified" address (all octets are zero ) but SHOULD be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   set to an address in the address range specifically assigned by IANA</td><td> </td><td class="right">   set to an address in the address range specifically assigned by IANA</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   for use in the IGMP messages sent from a gateway to a relay (i.e.</td><td> </td><td class="right">   for use in the IGMP messages sent from a gateway to a relay (i.e.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   154.7.1.2 through 154.7.1.254 as described in Section 7).  This</td><td> </td><td class="right">   154.7.1.2 through 154.7.1.254 as described in Section 7).  This</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   exception is made because the gateway pseudo-interface might not</td><td> </td><td class="right">   exception is made because the gateway pseudo-interface might not</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   possess an assigned address, and even if such an address exists, that</td><td> </td><td class="right">   possess an assigned address, and even if such an address exists, that</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address would not be a valid link-local source address on any relay</td><td> </td><td class="right">   address would not be a valid link-local source address on any relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interface.  The rationale for using the aforementioned source</td><td> </td><td class="right">   interface.  The rationale for using the aforementioned source</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0013"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   addresses is <span class="delete">primary</span> one of convenience - a relay will accept an IGMP</td><td> </td><td class="rblock">   addresses is <span class="insert">primarly</span> one of convenience - a relay will accept an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   report carried by a Membership Update message regardless of the</td><td> </td><td class="rblock">   IGMP report carried by a Membership Update message regardless of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   source address it carries.  See Section 5.3.1.</td><td> </td><td class="right">   source address it carries.  See Section 5.3.1.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The IP-encapsulated MLD messages generated by the gateway IPv6/MLD</td><td> </td><td class="right">   The IP-encapsulated MLD messages generated by the gateway IPv6/MLD</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   implementation MUST conform to the description found in Section 5 of</td><td> </td><td class="right">   implementation MUST conform to the description found in Section 5 of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3810].  These datagrams MUST possess the IP headers, header</td><td> </td><td class="right">   [RFC3810].  These datagrams MUST possess the IP headers, header</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   options and header values called for in [RFC3810], with the following</td><td> </td><td class="right">   options and header values called for in [RFC3810], with the following</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   exception; the source IP address for an MLD report datagram MAY be</td><td> </td><td class="right">   exception; the source IP address for an MLD report datagram MAY be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   set to the "unspecified" address (all octets are zero ) but SHOULD be</td><td> </td><td class="right">   set to the "unspecified" address (all octets are zero ) but SHOULD be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   set to an IPv6 link-local address in the range FE80::/64 excluding</td><td> </td><td class="right">   set to an IPv6 link-local address in the range FE80::/64 excluding</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   FE80::1 and FE80::2.  This exception is made because the gateway</td><td> </td><td class="right">   FE80::1 and FE80::2.  This exception is made because the gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l12"><small>skipping to change at</small><em> page 47, line 47</em></a></th><th> </th><th><a name="part-r12"><small>skipping to change at</small><em> page 48, line 41</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   accept the MLD datagram regardless of the IP source address carried</td><td> </td><td class="right">   accept the MLD datagram regardless of the IP source address carried</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   by that datagram.</td><td> </td><td class="right">   by that datagram.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.2.2.  Pseudo-Interface Configuration</td><td> </td><td class="right">5.2.2.  Pseudo-Interface Configuration</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway host may possess or create multiple gateway pseudo-</td><td> </td><td class="right">   A gateway host may possess or create multiple gateway pseudo-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interfaces, each with a unique configuration that describes a binding</td><td> </td><td class="right">   interfaces, each with a unique configuration that describes a binding</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   to a specific IP protocol, relay address, relay discovery address or</td><td> </td><td class="right">   to a specific IP protocol, relay address, relay discovery address or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   upstream network interface.</td><td> </td><td class="right">   upstream network interface.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0014"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">5.2.2.1.  Static Relay <span class="delete">Address</span></td><td> </td><td class="rblock">5.2.2.1.  Static Relay Discovery Address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Before a gateway implementation can execute the AMT protocol to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request and receive multicast traffic, it must be supplied with a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   unicast relay address.  A gateway implementation may rely on static</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   address assignment or support some form of dynamic address discovery.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   This specification does not require the use of any particular method</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to obtain a relay address - an implementation may employ any method</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   that returns a suitable relay address.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">5.2.2.2.  Static Relay</span> Discovery Address</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If a gateway implementation uses AMT relay discovery to obtain a</td><td> </td><td class="right">   If a gateway implementation uses AMT relay discovery to obtain a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   relay address, it must first be supplied with a relay discovery</td><td> </td><td class="right">   relay address, it must first be supplied with a relay discovery</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address.  The relay discovery address may be an anycast or unicast</td><td> </td><td class="right">   address.  The relay discovery address may be an anycast or unicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address.  A gateway implementation may rely on a static address</td><td> </td><td class="right">   address.  A gateway implementation may rely on a static address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   assignment or some form of dynamic address discovery.  This</td><td> </td><td class="right">   assignment or some form of dynamic address discovery.  This</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   specification does not require that a gateway implementation use any</td><td> </td><td class="right">   specification does not require that a gateway implementation use any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   particular method to obtain a relay discovery address - an</td><td> </td><td class="right">   particular method to obtain a relay discovery address - an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   implementation may employ any method that returns a suitable relay</td><td> </td><td class="right">   implementation may employ any method that returns a suitable relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   discovery address.</td><td> </td><td class="right">   discovery address.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0015"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">5.2.2.2.  Static Relay Address</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Before a gateway implementation can execute the AMT protocol to</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   request and receive multicast traffic, it must be supplied with a</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   unicast relay address.  A gateway implementation may rely on static</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   address assignment or support some form of dynamic address discovery.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   This specification does not require the use of any particular method</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   to obtain a relay address - an implementation may employ any method</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   that returns a suitable relay address.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.2.2.3.  Upstream Interface Selection</td><td> </td><td class="right">5.2.2.3.  Upstream Interface Selection</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway host that possesses multiple network interfaces or</td><td> </td><td class="right">   A gateway host that possesses multiple network interfaces or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   addresses may allow for an explicit selection of the interface to use</td><td> </td><td class="right">   addresses may allow for an explicit selection of the interface to use</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   when communicating with a relay.  The selection might be made to</td><td> </td><td class="right">   when communicating with a relay.  The selection might be made to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   satisfy connectivity, tunneling or IP protocol requirements.</td><td> </td><td class="right">   satisfy connectivity, tunneling or IP protocol requirements.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.2.2.4.  Optional Retransmission Parameters</td><td> </td><td class="right">5.2.2.4.  Optional Retransmission Parameters</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway implementation that supports retransmission MAY require the</td><td> </td><td class="right">   A gateway implementation that supports retransmission MAY require the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l13"><small>skipping to change at</small><em> page 56, line 40</em></a></th><th> </th><th><a name="part-r13"><small>skipping to change at</small><em> page 57, line 40</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   fields for use in sending subsequent Membership Update and Teardown</td><td> </td><td class="right">   fields for use in sending subsequent Membership Update and Teardown</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   messages.</td><td> </td><td class="right">   messages.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The gateway extracts the encapsulated IP datagram and forwards it to</td><td> </td><td class="right">   The gateway extracts the encapsulated IP datagram and forwards it to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the local IP protocol implementation for checksum verification and</td><td> </td><td class="right">   the local IP protocol implementation for checksum verification and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   dispatching to the IGMP or MLD implementation running on the pseudo-</td><td> </td><td class="right">   dispatching to the IGMP or MLD implementation running on the pseudo-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interface.  The gateway MUST NOT forward any octets that might exist</td><td> </td><td class="right">   interface.  The gateway MUST NOT forward any octets that might exist</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   between the encapsulated IP datagram and the end of the message or</td><td> </td><td class="right">   between the encapsulated IP datagram and the end of the message or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Gateway Address fields.</td><td> </td><td class="right">   Gateway Address fields.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0016"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">IGMP and</span> MLD protocol <span class="delete">specifications indicate</span> that senders should</td><td> </td><td class="rblock">   The MLD protocol <span class="insert">specification indicates</span> that senders should use a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   use a link-local source IP address in message datagrams.  This</td><td> </td><td class="rblock">   link-local source IP address in message datagrams.  This requirement</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   requirement must be relaxed for AMT because gateways and relays do</td><td> </td><td class="rblock">   must be relaxed for AMT because gateways and relays do not <span class="insert">normally</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   not share a common subnet.  For this reason, a gateway implementation</td><td> </td><td class="rblock">   share a common subnet.  For this reason, a gateway implementation</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   MUST accept <span class="delete">IGMP and</span> MLD query message datagrams regardless of the</td><td> </td><td class="rblock">   MUST accept MLD <span class="insert">(and IGMP)</span> query message datagrams regardless of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   source IP address they carry.</td><td> </td><td class="rblock">   source IP address they carry.  <span class="insert">This may require additional processing</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   on the part of the gateway that might be avoided if the relay and</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   gateway use the IPv4 and IPv6 addresses allocated for use in AMT</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   encapsulated control packets as described in Section 5.2.1.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The gateway MUST start a timer that will trigger the next iteration</td><td> </td><td class="right">   The gateway MUST start a timer that will trigger the next iteration</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the membership update cycle by executing the membership query</td><td> </td><td class="right">   of the membership update cycle by executing the membership query</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   procedure.  The gateway SHOULD compute the timer duration from the</td><td> </td><td class="right">   procedure.  The gateway SHOULD compute the timer duration from the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Querier's Query Interval Code carried by the general-query.  A</td><td> </td><td class="right">   Querier's Query Interval Code carried by the general-query.  A</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateway MAY use a smaller timer duration if required to refresh a NAT</td><td> </td><td class="right">   gateway MAY use a smaller timer duration if required to refresh a NAT</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   mapping that would otherwise timeout.  A gateway MAY use a larger</td><td> </td><td class="right">   mapping that would otherwise timeout.  A gateway MAY use a larger</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   timer duration if it has no group subscriptions to report.</td><td> </td><td class="right">   timer duration if it has no group subscriptions to report.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the gateway supports the Teardown message and the G-flag is set in</td><td> </td><td class="right">   If the gateway supports the Teardown message and the G-flag is set in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l14"><small>skipping to change at</small><em> page 58, line 24</em></a></th><th> </th><th><a name="part-r14"><small>skipping to change at</small><em> page 59, line 26</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  IPv6 datagrams that carry an MLDv1 or MLDv2 Multicast Listener</td><td> </td><td class="right">   o  IPv6 datagrams that carry an MLDv1 or MLDv2 Multicast Listener</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Report or an MLDv1 Multicast Listener Done message as described in</td><td> </td><td class="right">      Report or an MLDv1 Multicast Listener Done message as described in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Section 5 of [RFC3810].</td><td> </td><td class="right">      Section 5 of [RFC3810].</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The gateway must be prepared to receive these messages any time the</td><td> </td><td class="right">   The gateway must be prepared to receive these messages any time the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   pseudo-interface is running.  The gateway MUST ignore any datagrams</td><td> </td><td class="right">   pseudo-interface is running.  The gateway MUST ignore any datagrams</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   not listed above.</td><td> </td><td class="right">   not listed above.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway that waits to start a membership update cycle until after</td><td> </td><td class="right">   A gateway that waits to start a membership update cycle until after</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0017"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   it receives an IGMP/MLD state-change message MAY:</td><td> </td><td class="rblock">   it receives <span class="insert">a datagram containing</span> an IGMP/MLD state-change message</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   MAY:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0018"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  Discard datagrams <span class="delete">containing IGMP/MLD messages</span> until it receives a</td><td> </td><td class="rblock">   o  Discard <span class="insert">IGMP or MLD</span> datagrams until it receives a Membership Query</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      Membership Query message, at which time it processes the</td><td> </td><td class="rblock">      message, at which time it processes the Membership Query message</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      Membership Query message as normal to eventually produce a</td><td> </td><td class="rblock">      as normal to eventually produce a current-state report on the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      current-state report on the pseudo-interface which describes the</td><td> </td><td class="rblock">      pseudo-interface which describes the end state (RECOMMENDED).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      end state (RECOMMENDED).</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0019"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  Insert <span class="delete">IGMP/MLD messages</span> into a queue for transmission after it</td><td> </td><td class="rblock">   o  Insert <span class="insert">IGMP or MLD datagrams</span> into a queue for transmission after</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      receives a Membership Query message.</td><td> </td><td class="rblock">      it receives a Membership Query message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0020"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   If <span class="delete">the datagram contains</span> a <span class="delete">valid</span> IGMP or <span class="delete">MLD message, the gateway</span></td><td> </td><td class="rblock">   If <span class="insert">and when</span> a <span class="insert">gateway receives a Membership Query message (for</span> IGMP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   sends</span> it to the relay as described in the next section.</td><td> </td><td class="rblock">   or <span class="insert">MLD)</span> it <span class="insert">sends any queued or incoming IGMP or MLD datagrams</span> to the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   relay as described in the next section.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.2.3.6.2.  Sending a Membership Update Message</td><td> </td><td class="right">5.2.3.6.2.  Sending a Membership Update Message</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway cannot send a Membership Update message to a relay until it</td><td> </td><td class="right">   A gateway cannot send a Membership Update message to a relay until it</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   has received a Membership Query message from a relay.  If the gateway</td><td> </td><td class="right">   has received a Membership Query message from a relay.  If the gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   has not yet located a relay with which to communicate, it MUST first</td><td> </td><td class="right">   has not yet located a relay with which to communicate, it MUST first</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   execute the relay discovery procedure described in Section 5.2.3.4 to</td><td> </td><td class="right">   execute the relay discovery procedure described in Section 5.2.3.4 to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   obtain a relay address.  If the gateway has a relay address, but has</td><td> </td><td class="right">   obtain a relay address.  If the gateway has a relay address, but has</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   not yet received a Membership Query message, it MUST first execute</td><td> </td><td class="right">   not yet received a Membership Query message, it MUST first execute</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the membership query procedure described in Section 5.2.3.5 to obtain</td><td> </td><td class="right">   the membership query procedure described in Section 5.2.3.5 to obtain</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l15"><small>skipping to change at</small><em> page 61, line 47</em></a></th><th> </th><th><a name="part-r15"><small>skipping to change at</small><em> page 62, line 50</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay requires a subset of router-mode IGMP and MLD functionality</td><td> </td><td class="right">   A relay requires a subset of router-mode IGMP and MLD functionality</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   to provide group membership tracking and report processing.</td><td> </td><td class="right">   to provide group membership tracking and report processing.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay accessible via IPv4 MUST support IPv4/IGMPv3 and MAY support</td><td> </td><td class="right">   A relay accessible via IPv4 MUST support IPv4/IGMPv3 and MAY support</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IPv6/MLDv2.  A relay accessible via IPv6 MUST support IPv6/MLDv2 and</td><td> </td><td class="right">   IPv6/MLDv2.  A relay accessible via IPv6 MUST support IPv6/MLDv2 and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   MAY support IPv4/IGMPv3.</td><td> </td><td class="right">   MAY support IPv4/IGMPv3.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay MUST apply the forwarding rules described in Section 6.3 of</td><td> </td><td class="right">   A relay MUST apply the forwarding rules described in Section 6.3 of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3376] and Section 7.3 of [RFC3810].</td><td> </td><td class="right">   [RFC3376] and Section 7.3 of [RFC3810].</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0021"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   A relay MUST handle incoming reports as described <span class="delete">,</span>Section 6.4 of</td><td> </td><td class="rblock">   A relay MUST handle incoming reports as described Section 6.4 of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3376] and Section 7.4 of [RFC3810] with the exception that</td><td> </td><td class="right">   [RFC3376] and Section 7.4 of [RFC3810] with the exception that</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   actions that lead to queries MAY be modified to eliminate query</td><td> </td><td class="right">   actions that lead to queries MAY be modified to eliminate query</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   generation.  A relay MUST accept IGMP and MLD report datagrams</td><td> </td><td class="right">   generation.  A relay MUST accept IGMP and MLD report datagrams</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   regardless of the IP source address carried by those datagrams.</td><td> </td><td class="right">   regardless of the IP source address carried by those datagrams.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   All other aspects of IGMP/MLD router behavior, such as the handling</td><td> </td><td class="right">   All other aspects of IGMP/MLD router behavior, such as the handling</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of queries, querier election, etc., are not used or required for</td><td> </td><td class="right">   of queries, querier election, etc., are not used or required for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   relay operation.</td><td> </td><td class="right">   relay operation.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.3.2.  Startup</td><td> </td><td class="right">5.3.2.  Startup</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l16"><small>skipping to change at</small><em> page 63, line 21</em></a></th><th> </th><th><a name="part-r16"><small>skipping to change at</small><em> page 64, line 26</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the Relay Discovery as the source IP address and UDP port to</td><td> </td><td class="right">   of the Relay Discovery as the source IP address and UDP port to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   ensure successful NAT traversal.</td><td> </td><td class="right">   ensure successful NAT traversal.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The relay MUST copy the value contained in the Discovery Nonce field</td><td> </td><td class="right">   The relay MUST copy the value contained in the Discovery Nonce field</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the Relay Discovery message into the Discovery Nonce field in the</td><td> </td><td class="right">   of the Relay Discovery message into the Discovery Nonce field in the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the Relay Advertisement message.</td><td> </td><td class="right">   the Relay Advertisement message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the Relay Discovery message was received as an IPv4 datagram, the</td><td> </td><td class="right">   If the Relay Discovery message was received as an IPv4 datagram, the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   relay MUST return an IPv4 address in the Relay Address field of the</td><td> </td><td class="right">   relay MUST return an IPv4 address in the Relay Address field of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Relay Advertisement message.  If the Relay Discovery message was</td><td> </td><td class="right">   Relay Advertisement message.  If the Relay Discovery message was</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0022"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   received as an IPv6 datagram, the relay <span class="delete">may</span> return an <span class="delete">IPv4 or</span> IPv6</td><td> </td><td class="rblock">   received as an IPv6 datagram, the relay <span class="insert">MUST</span> return an IPv6 address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   address in the Relay Address field.</td><td> </td><td class="rblock">   in the Relay Address field.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.3.3.3.  Handling a Request Message</td><td> </td><td class="right">5.3.3.3.  Handling a Request Message</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This section describes relay requirements related to the membership</td><td> </td><td class="right">   This section describes relay requirements related to the membership</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   query portion of the message sequence described in Section 4.2.1.2.</td><td> </td><td class="right">   query portion of the message sequence described in Section 4.2.1.2.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   When a relay receives a Request message it responds by sending a</td><td> </td><td class="right">   When a relay receives a Request message it responds by sending a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Query message back to the source of the Request message.</td><td> </td><td class="right">   Membership Query message back to the source of the Request message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The relay MUST use the source IP address and UDP port of the Request</td><td> </td><td class="right">   The relay MUST use the source IP address and UDP port of the Request</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l17"><small>skipping to change at</small><em> page 64, line 13</em></a></th><th> </th><th><a name="part-r17"><small>skipping to change at</small><em> page 65, line 17</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the P-flag in the Request message is 0, the relay MUST return an</td><td> </td><td class="right">   If the P-flag in the Request message is 0, the relay MUST return an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IPv4-encapsulated IGMPv3 general query in the Membership Query</td><td> </td><td class="right">   IPv4-encapsulated IGMPv3 general query in the Membership Query</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   message.  If the P-flag is 1, the relay MUST return an IPv6-</td><td> </td><td class="right">   message.  If the P-flag is 1, the relay MUST return an IPv6-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   encapsulated MLDv2 general query in the Membership Query message.</td><td> </td><td class="right">   encapsulated MLDv2 general query in the Membership Query message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the relay is not accepting Membership Update messages that create</td><td> </td><td class="right">   If the relay is not accepting Membership Update messages that create</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   new tunnel endpoints due to resource limitations, it SHOULD set the</td><td> </td><td class="right">   new tunnel endpoints due to resource limitations, it SHOULD set the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   L-flag in the Membership Query message to notify the gateway of this</td><td> </td><td class="right">   L-flag in the Membership Query message to notify the gateway of this</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   state.  Support for the L-flag is OPTIONAL.  See Section 5.3.3.8.</td><td> </td><td class="right">   state.  Support for the L-flag is OPTIONAL.  See Section 5.3.3.8.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0023"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">An</span> IGMPv3 general query datagram that a relay encapsulates within a</td><td> </td><td class="rblock">   <span class="insert">The</span> IGMPv3 general query datagram that a relay encapsulates within a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Query message MUST conform to the descriptions found in</td><td> </td><td class="right">   Membership Query message MUST conform to the descriptions found in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Section 4.1 of [RFC3376].  These datagrams MUST possess the IP</td><td> </td><td class="right">   Section 4.1 of [RFC3376].  These datagrams MUST possess the IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   headers, header options and header values called for in [RFC3376],</td><td> </td><td class="right">   headers, header options and header values called for in [RFC3376],</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   with the following exception; the source IP address for an IGMP</td><td> </td><td class="right">   with the following exception; the source IP address for an IGMP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   general query datagram MAY be set to the "unspecified" address (all</td><td> </td><td class="right">   general query datagram MAY be set to the "unspecified" address (all</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   octets are zero) but SHOULD be set to an address in the address range</td><td> </td><td class="right">   octets are zero) but SHOULD be set to an address in the address range</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   specifically assigned by IANA for use in the IGMP messages sent from</td><td> </td><td class="right">   specifically assigned by IANA for use in the IGMP messages sent from</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   a relay to a gateway (i.e. 154.7.1.1 as described in Section 7).</td><td> </td><td class="right">   a relay to a gateway (i.e. 154.7.1.1 as described in Section 7).</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0024"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This exception is made because <span class="delete">any</span> address that a relay might may not</td><td> </td><td class="rblock">   This exception is made because <span class="insert">the source</span> address that a relay might</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   be a valid source address on any gateway interface.  The rationale</td><td> </td><td class="rblock">   <span class="insert">normally send</span> may not be a valid source address on any gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   for using the aforementioned source addresses is primary one of</td><td> </td><td class="rblock">   interface.  The rationale for using the aforementioned source</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   convenience - a gateway will accept an IGMP query regardless of the</td><td> </td><td class="rblock">   addresses is primary one of convenience - a gateway will accept an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   source address it carries.  See Section 5.2.1.</td><td> </td><td class="rblock">   IGMP query regardless of the source address it carries.  See</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   Section 5.2.1.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0025"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">An</span> MLDv2 general query datagram that a relay encapsulates within a</td><td> </td><td class="rblock">   <span class="insert">The</span> MLDv2 general query datagram that a relay encapsulates within a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Query message MUST conform to the descriptions found in</td><td> </td><td class="right">   Membership Query message MUST conform to the descriptions found in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Section 5.1 of [RFC3810].  These datagrams MUST possess the IP</td><td> </td><td class="right">   Section 5.1 of [RFC3810].  These datagrams MUST possess the IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   headers, header options and header values called for in [RFC3810],</td><td> </td><td class="right">   headers, header options and header values called for in [RFC3810],</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   with the following exception; the source IP address for an MLD</td><td> </td><td class="right">   with the following exception; the source IP address for an MLD</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   general query datagram MAY be set to the "unspecified" address (all</td><td> </td><td class="right">   general query datagram MAY be set to the "unspecified" address (all</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   octets are zero) but SHOULD be set to an IPv6 link-local address in</td><td> </td><td class="right">   octets are zero) but SHOULD be set to an IPv6 link-local address in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the range FE80::/64.  A relay may use a dynamically-generated link-</td><td> </td><td class="right">   the range FE80::/64.  A relay may use a dynamically-generated link-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   local address or the fixed address FE80::2.  As with IGMP, a gateway</td><td> </td><td class="right">   local address or the fixed address FE80::2.  As with IGMP, a gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   will accept an MLD query regardless of the source address it carries.</td><td> </td><td class="right">   will accept an MLD query regardless of the source address it carries.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   See Section 5.2.1.</td><td> </td><td class="right">   See Section 5.2.1.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l18"><small>skipping to change at</small><em> page 65, line 4</em></a></th><th> </th><th><a name="part-r18"><small>skipping to change at</small><em> page 66, line 9</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   duration to use for the membership query timer.  The QQIC field is</td><td> </td><td class="right">   duration to use for the membership query timer.  The QQIC field is</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   defined in Section 4.1.1 in [RFC3376] and Section 5.1.3 in [RFC3810].</td><td> </td><td class="right">   defined in Section 4.1.1 in [RFC3376] and Section 5.1.3 in [RFC3810].</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay MAY adjust this value to affect the rate at which the Request</td><td> </td><td class="right">   A relay MAY adjust this value to affect the rate at which the Request</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   messages are sent from a gateway.  However, a gateway is allowed to</td><td> </td><td class="right">   messages are sent from a gateway.  However, a gateway is allowed to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   use a shorter duration than specified in the QQIC field, so a relay</td><td> </td><td class="right">   use a shorter duration than specified in the QQIC field, so a relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   may be limited in its ability to spread out Requests coming from a</td><td> </td><td class="right">   may be limited in its ability to spread out Requests coming from a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateway.</td><td> </td><td class="right">   gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay MUST set the Querier's Robustness Variable (QRV) field in the</td><td> </td><td class="right">   A relay MUST set the Querier's Robustness Variable (QRV) field in the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   general query to a non-zero value.  This value SHOULD be greater than</td><td> </td><td class="right">   general query to a non-zero value.  This value SHOULD be greater than</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0026"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   one.  If a gateway retransmits <span class="delete">a </span>membership state change messages, it</td><td> </td><td class="rblock">   one.  If a gateway retransmits membership state change messages, it</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   will retransmit them (robustness variable - 1) times.</td><td> </td><td class="right">   will retransmit them (robustness variable - 1) times.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay SHOULD set the Max Resp Code field in the general query to a</td><td> </td><td class="right">   A relay SHOULD set the Max Resp Code field in the general query to a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   value of 1 to trigger an immediate response from the gateway (some</td><td> </td><td class="right">   value of 1 to trigger an immediate response from the gateway (some</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   host IGMP/MLD implementations may not accept a value of zero).  A</td><td> </td><td class="right">   host IGMP/MLD implementations may not accept a value of zero).  A</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   relay SHOULD NOT use the IGMPv2/MLDv2 Query Response Interval</td><td> </td><td class="right">   relay SHOULD NOT use the IGMPv2/MLDv2 Query Response Interval</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   variable, if available, to generate the Max Resp Code field value as</td><td> </td><td class="right">   variable, if available, to generate the Max Resp Code field value as</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the Query Response Interval variable is used in setting the duration</td><td> </td><td class="right">   the Query Response Interval variable is used in setting the duration</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of group state timers and must not be set to such a small value.  See</td><td> </td><td class="right">   of group state timers and must not be set to such a small value.  See</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Section 5.3.3.7.</td><td> </td><td class="right">   Section 5.3.3.7.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l19"><small>skipping to change at</small><em> page 68, line 45</em></a></th><th> </th><th><a name="part-r19"><small>skipping to change at</small><em> page 69, line 51</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   state and possibly send prune/leave messages towards upstream</td><td> </td><td class="right">   state and possibly send prune/leave messages towards upstream</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   routers.</td><td> </td><td class="right">   routers.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.3.3.6.  Handling Multicast IP Datagrams</td><td> </td><td class="right">5.3.3.6.  Handling Multicast IP Datagrams</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   When a multicast IP datagram is forwarded to the relay pseudo-</td><td> </td><td class="right">   When a multicast IP datagram is forwarded to the relay pseudo-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interface, the relay MUST, for each gateway that has expressed an</td><td> </td><td class="right">   interface, the relay MUST, for each gateway that has expressed an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interest in receiving the datagram, encapsulate the IP datagram into</td><td> </td><td class="right">   interest in receiving the datagram, encapsulate the IP datagram into</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   a Multicast Data message and send that message to the gateway.  This</td><td> </td><td class="right">   a Multicast Data message and send that message to the gateway.  This</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   process is highly implementation dependent, but conceptually requires</td><td> </td><td class="right">   process is highly implementation dependent, but conceptually requires</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0027"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   the follow steps:</td><td> </td><td class="rblock">   the follow<span class="insert">ing</span> steps:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Use the IP datagram source and destination address to look up the</td><td> </td><td class="right">   o  Use the IP datagram source and destination address to look up the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      appropriate (*,G) or (S,G) entry in the endpoint forwarding table</td><td> </td><td class="right">      appropriate (*,G) or (S,G) entry in the endpoint forwarding table</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      created for the pseudo-interface as a result of IGMP/MLD</td><td> </td><td class="right">      created for the pseudo-interface as a result of IGMP/MLD</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      processing.</td><td> </td><td class="right">      processing.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Possibly replicate the datagram for each gateway endpoint listed</td><td> </td><td class="right">   o  Possibly replicate the datagram for each gateway endpoint listed</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      for that (*,G) or (S,G) entry.</td><td> </td><td class="right">      for that (*,G) or (S,G) entry.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Encapsulate the IP datagram in a UDP/IP Membership Data message,</td><td> </td><td class="right">   o  Encapsulate the IP datagram in a UDP/IP Membership Data message,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l20"><small>skipping to change at</small><em> page 70, line 26</em></a></th><th> </th><th><a name="part-r20"><small>skipping to change at</small><em> page 71, line 31</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   SHOULD set the L-flag in any Membership Query messages it returns to</td><td> </td><td class="right">   SHOULD set the L-flag in any Membership Query messages it returns to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateways while in this state.</td><td> </td><td class="right">   gateways while in this state.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the relay receives an update from a gateway that adds group</td><td> </td><td class="right">   If the relay receives an update from a gateway that adds group</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   membership or forwarding state for an endpoint that has already</td><td> </td><td class="right">   membership or forwarding state for an endpoint that has already</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   reached maximum allowable state entries, the relay SHOULD continue to</td><td> </td><td class="right">   reached maximum allowable state entries, the relay SHOULD continue to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   accept updates from the gateway but ignore any group membership/</td><td> </td><td class="right">   accept updates from the gateway but ignore any group membership/</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   forwarding state additions requested by that gateway.</td><td> </td><td class="right">   forwarding state additions requested by that gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the relay receives an update from a gateway that would create a</td><td> </td><td class="right">   If the relay receives an update from a gateway that would create a</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0028"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   new tunnel endpoint for a source IP address that has already <span class="delete">reach</span></td><td> </td><td class="rblock">   new tunnel endpoint for a source IP address that has already <span class="insert">reached</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   maximum allowable number of endpoints (maximum UDP ports), it should</td><td> </td><td class="rblock"><span class="insert">   the</span> maximum allowable number of endpoints (maximum UDP ports), it</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   simply ignore the Membership Update.</td><td> </td><td class="rblock">   should simply ignore the Membership Update.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.3.4.  Shutdown</td><td> </td><td class="right">5.3.4.  Shutdown</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The following steps should be treated as an abstract description of</td><td> </td><td class="right">   The following steps should be treated as an abstract description of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the shutdown procedure for a relay:</td><td> </td><td class="right">   the shutdown procedure for a relay:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Withdraw the Relay Discovery Address Prefix advertisement (if</td><td> </td><td class="right">   o  Withdraw the Relay Discovery Address Prefix advertisement (if</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      used).</td><td> </td><td class="right">      used).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Stop listening for Relay Discovery messages.</td><td> </td><td class="right">   o  Stop listening for Relay Discovery messages.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l21"><small>skipping to change at</small><em> page 75, line 19</em></a></th><th> </th><th><a name="part-r21"><small>skipping to change at</small><em> page 76, line 19</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IANA should allocate an IPv4 prefix and an IPv6 prefix dedicated to</td><td> </td><td class="right">   IANA should allocate an IPv4 prefix and an IPv6 prefix dedicated to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the public AMT Relays to advertise to the native multicast backbone</td><td> </td><td class="right">   the public AMT Relays to advertise to the native multicast backbone</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (as described in Section 4.1.4).  The prefix length should be</td><td> </td><td class="right">   (as described in Section 4.1.4).  The prefix length should be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   determined by the IANA; the prefix should be large enough to</td><td> </td><td class="right">   determined by the IANA; the prefix should be large enough to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   guarantee advertisement in the default-free BGP networks.</td><td> </td><td class="right">   guarantee advertisement in the default-free BGP networks.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">7.1.1.  IPv4</td><td> </td><td class="right">7.1.1.  IPv4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A prefix length of 24 will meet this requirement.</td><td> </td><td class="right">   A prefix length of 24 will meet this requirement.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0029"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Internet Systems Consortium (ISC) has offered154.7.0/24 for this</td><td> </td><td class="rblock">   Internet Systems Consortium (ISC) has offered<span class="insert"> </span>154.7.0/24 for this</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   purpose.</td><td> </td><td class="right">   purpose.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">7.1.2.  IPv6</td><td> </td><td class="right">7.1.2.  IPv6</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A prefix length of 32 will meet this requirement.  IANA has</td><td> </td><td class="right">   A prefix length of 32 will meet this requirement.  IANA has</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   previously set aside the range 2001::/16 for allocating prefixes for</td><td> </td><td class="right">   previously set aside the range 2001::/16 for allocating prefixes for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   this purpose.</td><td> </td><td class="right">   this purpose.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">7.2.  IPv4 Address Prefix Allocation for IGMP Source Addresses</td><td> </td><td class="right">7.2.  IPv4 Address Prefix Allocation for IGMP Source Addresses</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 29 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>72 lines changed or deleted</i></th><th><i> </i></th><th><i>83 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br>This html diff was produced by rfcdiff 1.41. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/">http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
   </tbody></table>
   
   
</body></html>
--Apple-Mail-22--55894346
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii



On May 10, 2012, at 10:33 AM, Greg Shepherd wrote:

> *,
> 
> Yes, I think we may finally be here! The Paris and post-Paris
> discussions were addressed in the finally rev so it is now time for
> WGLC for draft-ietf-mboned-auto-multicast-13:
> 
> https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/
> 
> It is quite long so we'll give it three weeks for responses before
> moving it along. Please respond by May 31st. And as always, we need
> votes of approval as much as comments and issues. Let's see this
> finally move to req pub!
> 
> Thanks to everyone who has been involved throughout the past +decade. :p
> 
> MBONED Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


--Apple-Mail-22--55894346--

From gbumgard@cisco.com  Thu Jun  7 00:44:30 2012
Return-Path: <gbumgard@cisco.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8275A21F8670 for <mboned@ietfa.amsl.com>; Thu,  7 Jun 2012 00:44:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.409
X-Spam-Level: 
X-Spam-Status: No, score=-9.409 tagged_above=-999 required=5 tests=[AWL=-1.191, BAYES_00=-2.599, HTML_COMMENT_SAVED_URL=0.114, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_HI=-8, SARE_HTML_SINGLETS=1.666]
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 WXTDR8FC0aD5 for <mboned@ietfa.amsl.com>; Thu,  7 Jun 2012 00:44:24 -0700 (PDT)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id 08ABE21F865B for <mboned@ietf.org>; Thu,  7 Jun 2012 00:44:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gbumgard@cisco.com; l=224510; q=dns/txt; s=iport; t=1339055060; x=1340264660; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=ZenhfNnd68AAgxFZULbyP6ebnbv8bQDXHNlIf5kIKZY=; b=IFTgi9KRLp4kN8v1RA/6ZdsWc94/8JzbaGG+7CvTezphe/+fZfWe54bU dAxy5u93qP6S5zdA2Wyl57SZ0/Dcs0a9BPqabM2e4ZQQcWq4u6s5Y91py jyfT0gA5mpFKQvNXtQ0ksmpFmBI85RdNrypCo8FyxiuDfrGehn8Yew1+V 8=;
X-Files: diff_draft-ietf-mboned-auto-multicast-13v14pre2.html : 220686
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsUEAJlb0E9Io8UY/2dsb2JhbABFiC6idgGJf4IYAQEBAwEBAQEPAQcBDAY4AgcGBQULCxIGDRMBDSciDgYTGweFb4F1BQuYeZ95ix0UAYUTYAOIQIV3hmaBEoRBiEGBZoEtgVOBNgEBBQIc
X-IronPort-AV: E=Sophos;i="4.75,728,1330905600";  d="html'217?scan'217,208,217";a="13917410"
Received: from vla196-nat.cisco.com (HELO bgl-core-1.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 07 Jun 2012 07:44:05 +0000
Received: from [10.20.185.152] (sjc-gbumgard-8917.cisco.com [10.20.185.152]) by bgl-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q577i1fO027933; Thu, 7 Jun 2012 07:44:02 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/mixed; boundary=Apple-Mail-25--29412545
From: Greg Bumgardner <gbumgard@cisco.com>
In-Reply-To: <4FCFFEBA.4020600@gmail.com>
Date: Thu, 7 Jun 2012 00:44:00 -0700
Message-Id: <ED236176-3A53-491E-81AC-07997B2D22EE@cisco.com>
References: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com> <E4321BB1-F286-4AC9-B1F9-F2622AA07375@cisco.com> <4FCFFEBA.4020600@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "mboned@ietf.org WG" <mboned@ietf.org>
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 07:44:30 -0000

--Apple-Mail-25--29412545
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks Tom.

Just a couple of comments below.

I corrected the errors you identified and fixed a few more that I found =
after running the document through a better spell checker. These changes =
appear in the attached diff.

Thanks again,

-g.b.


--Apple-Mail-25--29412545
Content-Disposition: attachment;
	filename=diff_draft-ietf-mboned-auto-multicast-13v14pre2.html
Content-Type: text/html;
	name="diff_draft-ietf-mboned-auto-multicast-13v14pre2.html"
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- saved from url=(0029)http://tools.ietf.org/rfcdiff -->
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> 
   
  <meta http-equiv="Content-Style-Type" content="text/css"> 
  <title>Diff: draft-ietf-mboned-auto-multicast-13final.txt - draft-ietf-mboned-auto-multicast-14pre2.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body> 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tbody><tr bgcolor="orange"><th></th><th><a href="http://tools.ietf.org/rfcdiff?url2=draft-ietf-mboned-auto-multicast-13final.txt" style="color:#008; text-decoration:none;">&lt;</a>&nbsp;<a href="http://tools.ietf.org/html/draft-ietf-mboned-auto-multicast-13final.txt" style="color:#008">draft-ietf-mboned-auto-multicast-13final.txt</a>&nbsp;</th><th> </th><th>&nbsp;<a href="http://tools.ietf.org/html/draft-ietf-mboned-auto-multicast-14pre2.txt" style="color:#008">draft-ietf-mboned-auto-multicast-14pre2.txt</a>&nbsp;<a href="http://tools.ietf.org/rfcdiff?url1=draft-ietf-mboned-auto-multicast-14pre2.txt" style="color:#008; text-decoration:none;">&gt;</a></th><th></th></tr> 
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Network Working Group                                      G. Bumgardner</td><td> </td><td class="right">Network Working Group                                      G. Bumgardner</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Internet-Draft                                                     Cisco</td><td> </td><td class="right">Internet-Draft                                                     Cisco</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Intended status: Standards Track                          <span class="delete">April 23,</span> 2012</td><td> </td><td class="rblock">Intended status: Standards Track                            <span class="insert">June 6,</span> 2012</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: <span class="delete">October 25,</span> 2012</td><td> </td><td class="rblock">Expires: <span class="insert">December 8,</span> 2012</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                     Automatic Multicast Tunneling</td><td> </td><td class="right">                     Automatic Multicast Tunneling</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                  draft-ietf-mboned-auto-multicast-1<span class="delete">3</span></td><td> </td><td class="rblock">                  draft-ietf-mboned-auto-multicast-1<span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document describes Automatic Multicast Tunneling (AMT), a</td><td> </td><td class="right">   This document describes Automatic Multicast Tunneling (AMT), a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   protocol for delivering multicast traffic from sources in a</td><td> </td><td class="right">   protocol for delivering multicast traffic from sources in a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   multicast-enabled network to receivers that lack multicast</td><td> </td><td class="right">   multicast-enabled network to receivers that lack multicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   connectivity to the source network.  The protocol uses UDP</td><td> </td><td class="right">   connectivity to the source network.  The protocol uses UDP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   encapsulation and unicast replication to provide this functionality.</td><td> </td><td class="right">   encapsulation and unicast replication to provide this functionality.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The AMT protocol is specifically designed to support rapid deployment</td><td> </td><td class="right">   The AMT protocol is specifically designed to support rapid deployment</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l2"><small>skipping to change at</small><em> page 1, line 37</em></a></th><th> </th><th><a name="part-r2"><small>skipping to change at</small><em> page 1, line 37</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right">   Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right">   and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   time.  It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right">   time.  It is inappropriate to use Internet-Drafts as reference</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   material or to cite them other than as "work in progress."</td><td> </td><td class="right">   material or to cite them other than as "work in progress."</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">October 25</span>, 2012.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">December 8</span>, 2012.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Copyright (c) 2012 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2012 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l3"><small>skipping to change at</small><em> page 2, line 33</em></a></th><th> </th><th><a name="part-r3"><small>skipping to change at</small><em> page 2, line 33</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   2.  Applicability  . . . . . . . . . . . . . . . . . . . . . . . .  4</td><td> </td><td class="right">   2.  Applicability  . . . . . . . . . . . . . . . . . . . . . . . .  4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     3.1.  Requirements Notation  . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">     3.1.  Requirements Notation  . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     3.2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  5</td><td> </td><td class="right">     3.2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     3.3.  Abbreviations  . . . . . . . . . . . . . . . . . . . . . .  6</td><td> </td><td class="right">     3.3.  Abbreviations  . . . . . . . . . . . . . . . . . . . . . .  6</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   4.  Protocol Overview  . . . . . . . . . . . . . . . . . . . . . .  8</td><td> </td><td class="right">   4.  Protocol Overview  . . . . . . . . . . . . . . . . . . . . . .  8</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     4.1.  General Architecture . . . . . . . . . . . . . . . . . . .  8</td><td> </td><td class="right">     4.1.  General Architecture . . . . . . . . . . . . . . . . . . .  8</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     4.2.  General Operation  . . . . . . . . . . . . . . . . . . . . 17</td><td> </td><td class="right">     4.2.  General Operation  . . . . . . . . . . . . . . . . . . . . 17</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   5.  Protocol Description . . . . . . . . . . . . . . . . . . . . . 32</td><td> </td><td class="right">   5.  Protocol Description . . . . . . . . . . . . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     5.1.  Protocol Messages  . . . . . . . . . . . . . . . . . . . . 32</td><td> </td><td class="right">     5.1.  Protocol Messages  . . . . . . . . . . . . . . . . . . . . 32</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     5.2.  Gateway Operation  . . . . . . . . . . . . . . . . . . . . <span class="delete">46</span></td><td> </td><td class="rblock">     5.2.  Gateway Operation  . . . . . . . . . . . . . . . . . . . . <span class="insert">47</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     5.3.  Relay Operation  . . . . . . . . . . . . . . . . . . . . . <span class="delete">61</span></td><td> </td><td class="rblock">     5.3.  Relay Operation  . . . . . . . . . . . . . . . . . . . . . <span class="insert">62</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . <span class="delete">72</span></td><td> </td><td class="rblock">   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . <span class="insert">73</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="delete">75</span></td><td> </td><td class="rblock">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="insert">76</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     7.2.  IPv4 Address Prefix Allocation for IGMP Source</td><td> </td><td class="right">     7.2.  IPv4 Address Prefix Allocation for IGMP Source</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">           Addresses  . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">75</span></td><td> </td><td class="rblock">           Addresses  . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">76</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   8.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">76</span></td><td> </td><td class="rblock">   8.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">77</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">77</span></td><td> </td><td class="rblock">   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">78</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">78</span></td><td> </td><td class="rblock">   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">79</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     10.1. Normative References . . . . . . . . . . . . . . . . . . . <span class="delete">78</span></td><td> </td><td class="rblock">     10.1. Normative References . . . . . . . . . . . . . . . . . . . <span class="insert">79</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     10.2. Informative References . . . . . . . . . . . . . . . . . . <span class="delete">78</span></td><td> </td><td class="rblock">     10.2. Informative References . . . . . . . . . . . . . . . . . . <span class="insert">79</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix A.  Implementation Notes  . . . . . . . . . . . . . . . . <span class="delete">81</span></td><td> </td><td class="rblock">   Appendix A.  Implementation Notes  . . . . . . . . . . . . . . . . <span class="insert">82</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">84</span></td><td> </td><td class="rblock">   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">85</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The advantages and benefits provided by multicast technologies are</td><td> </td><td class="right">   The advantages and benefits provided by multicast technologies are</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   well known.  There are a number of application areas that are ideal</td><td> </td><td class="right">   well known.  There are a number of application areas that are ideal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   candidates for the use of multicast, including media broadcasting,</td><td> </td><td class="right">   candidates for the use of multicast, including media broadcasting,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   video conferencing, collaboration, real-time data feeds, data</td><td> </td><td class="right">   video conferencing, collaboration, real-time data feeds, data</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   replication, and software updates.  Unfortunately, many of these</td><td> </td><td class="right">   replication, and software updates.  Unfortunately, many of these</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   applications lack multicast connectivity to networks that carry</td><td> </td><td class="right">   applications lack multicast connectivity to networks that carry</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   traffic generated by multicast sources.  The reasons for the lack of</td><td> </td><td class="right">   traffic generated by multicast sources.  The reasons for the lack of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l4"><small>skipping to change at</small><em> page 15, line 32</em></a></th><th> </th><th><a name="part-r4"><small>skipping to change at</small><em> page 15, line 32</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Relays may take themselves offline when they exhaust resources</td><td> </td><td class="right">   o  Relays may take themselves offline when they exhaust resources</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      required to service additional gateways.  Existing gateway</td><td> </td><td class="right">      required to service additional gateways.  Existing gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      connections may be preserved, but new gateway requests would be</td><td> </td><td class="right">      connections may be preserved, but new gateway requests would be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      routed to the next-nearest relay.</td><td> </td><td class="right">      routed to the next-nearest relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.1.4.1.  Public Versus Private</td><td> </td><td class="right">4.1.4.1.  Public Versus Private</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Ideally, the AMT protocol would provide a universal solution for</td><td> </td><td class="right">   Ideally, the AMT protocol would provide a universal solution for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   connecting receivers to multicast sources - that any gateway could be</td><td> </td><td class="right">   connecting receivers to multicast sources - that any gateway could be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   used to access any globally advertised multicast source via publicly-</td><td> </td><td class="right">   used to access any globally advertised multicast source via publicly-</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   accessible, widely-deployed relays.  Unfortunately, today's <span class="delete">i</span>nternet</td><td> </td><td class="rblock">   accessible, widely-deployed relays.  Unfortunately, today's <span class="insert">I</span>nternet</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   does not yet allow this, because many relays will lack native</td><td> </td><td class="right">   does not yet allow this, because many relays will lack native</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   multicast access to sources even though they may be globally</td><td> </td><td class="right">   multicast access to sources even though they may be globally</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   accessible via unicast.</td><td> </td><td class="right">   accessible via unicast.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   In these cases, a provider may deploy relays within their own source</td><td> </td><td class="right">   In these cases, a provider may deploy relays within their own source</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   network to allow for multicast distribution within that network.</td><td> </td><td class="right">   network to allow for multicast distribution within that network.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Gateways that use these relays must use a provider-specific relay</td><td> </td><td class="right">   Gateways that use these relays must use a provider-specific relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   discovery mechanism or a private anycast address to obtain access to</td><td> </td><td class="right">   discovery mechanism or a private anycast address to obtain access to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   these relays.</td><td> </td><td class="right">   these relays.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l5"><small>skipping to change at</small><em> page 17, line 35</em></a></th><th> </th><th><a name="part-r5"><small>skipping to change at</small><em> page 17, line 35</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Query:</td><td> </td><td class="right">   Membership Query:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Sent by relays as a response to a Request message.  Used to</td><td> </td><td class="right">      Sent by relays as a response to a Request message.  Used to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      deliver an encapsulated IGMPv3 or MLDv2 query message to the</td><td> </td><td class="right">      deliver an encapsulated IGMPv3 or MLDv2 query message to the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      gateway.</td><td> </td><td class="right">      gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Update:</td><td> </td><td class="right">   Membership Update:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Sent by gateways to deliver an encapsulated IGMP or MLD report/</td><td> </td><td class="right">      Sent by gateways to deliver an encapsulated IGMP or MLD report/</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      leave/done message to a relay.</td><td> </td><td class="right">      leave/done message to a relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Multicast Data:</td><td> </td><td class="right">   Multicast Data:</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0007"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      Sent by relays to deliver an encapsulated IP multicast datagram to</td><td> </td><td class="rblock">      Sent by relays to deliver an encapsulated IP multicast datagram <span class="insert">or</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      a gateway.</td><td> </td><td class="rblock"><span class="insert">      datagram fragment</span> to a gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Teardown:</td><td> </td><td class="right">   Teardown:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Sent by gateways to stop the delivery of Multicast Data messages</td><td> </td><td class="right">      Sent by gateways to stop the delivery of Multicast Data messages</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      requested in an earlier Membership Update message.</td><td> </td><td class="right">      requested in an earlier Membership Update message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The following sections describe how these messages are exchanged to</td><td> </td><td class="right">   The following sections describe how these messages are exchanged to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   execute the protocol.</td><td> </td><td class="right">   execute the protocol.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.2.1.1.  Relay Discovery Sequence</td><td> </td><td class="right">4.2.1.1.  Relay Discovery Sequence</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l6"><small>skipping to change at</small><em> page 18, line 44</em></a></th><th> </th><th><a name="part-r6"><small>skipping to change at</small><em> page 18, line 44</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">       relay.</td><td> </td><td class="right">       relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   3.  When the gateway receives the Relay Advertisement message it</td><td> </td><td class="right">   3.  When the gateway receives the Relay Advertisement message it</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">       verifies that the nonce matches the one sent in the Relay</td><td> </td><td class="right">       verifies that the nonce matches the one sent in the Relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">       Discovery message, and if it does, uses the relay address carried</td><td> </td><td class="right">       Discovery message, and if it does, uses the relay address carried</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">       by the Relay Advertisement as the destination address for</td><td> </td><td class="right">       by the Relay Advertisement as the destination address for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">       subsequent AMT messages.</td><td> </td><td class="right">       subsequent AMT messages.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Note that the responder need not be a relay - the responder may</td><td> </td><td class="right">   Note that the responder need not be a relay - the responder may</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   obtain a relay address by some other means and return the result in</td><td> </td><td class="right">   obtain a relay address by some other means and return the result in</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0008"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   the Relay Advertisement (i.e. the responder is a load-balancer or</td><td> </td><td class="rblock">   the Relay Advertisement (i.e.<span class="insert">,</span> the responder is a load-balancer or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   broker).</td><td> </td><td class="right">   broker).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.2.1.2.  Membership Update Sequence</td><td> </td><td class="right">4.2.1.2.  Membership Update Sequence</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   There exists a significant difference between normal IGMP and MLD</td><td> </td><td class="right">   There exists a significant difference between normal IGMP and MLD</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   behavior and that required by AMT.  An IGMP/MLD router acting as a</td><td> </td><td class="right">   behavior and that required by AMT.  An IGMP/MLD router acting as a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   querier normally transmits query messages on a network interface to</td><td> </td><td class="right">   querier normally transmits query messages on a network interface to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   construct and refresh group membership state for the connected</td><td> </td><td class="right">   construct and refresh group membership state for the connected</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   network.  These query messages are multicast to all IGMP/MLD enabled</td><td> </td><td class="right">   network.  These query messages are multicast to all IGMP/MLD enabled</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   hosts on the network.  Each host responds by multicasting report</td><td> </td><td class="right">   hosts on the network.  Each host responds by multicasting report</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l7"><small>skipping to change at</small><em> page 28, line 37</em></a></th><th> </th><th><a name="part-r7"><small>skipping to change at</small><em> page 28, line 37</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   UDP/IP address-port pair provided by the Membership Update message.</td><td> </td><td class="right">   UDP/IP address-port pair provided by the Membership Update message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.2.2.1.  Address Roaming</td><td> </td><td class="right">4.2.2.1.  Address Roaming</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   As described above, each time a relay receives a Membership Update</td><td> </td><td class="right">   As described above, each time a relay receives a Membership Update</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   message from a new source address-port pair, the group subscriptions</td><td> </td><td class="right">   message from a new source address-port pair, the group subscriptions</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   described by that message apply to the tunnel endpoint identified by</td><td> </td><td class="right">   described by that message apply to the tunnel endpoint identified by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   that address.</td><td> </td><td class="right">   that address.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This can cause problems for a gateway if the address carried by the</td><td> </td><td class="right">   This can cause problems for a gateway if the address carried by the</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0009"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   messages it sends to a relay change unexpectedly.  These changes may</td><td> </td><td class="rblock">   messages it sends to a relay change<span class="insert">s</span> unexpectedly.  These changes may</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   cause the relay to transmit duplicate, undeliverable or unrequested</td><td> </td><td class="right">   cause the relay to transmit duplicate, undeliverable or unrequested</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   traffic back towards the gateway or an intermediate device.  This may</td><td> </td><td class="right">   traffic back towards the gateway or an intermediate device.  This may</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   create congestion and have negative consequences for the gateway, its</td><td> </td><td class="right">   create congestion and have negative consequences for the gateway, its</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   network, or multicast receivers, and in some cases, may also produce</td><td> </td><td class="right">   network, or multicast receivers, and in some cases, may also produce</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   a significant amount of ICMP traffic directed back towards the relay</td><td> </td><td class="right">   a significant amount of ICMP traffic directed back towards the relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   by a NAT, router or gateway host.</td><td> </td><td class="right">   by a NAT, router or gateway host.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   There are several scenarios in which the address carried by messages</td><td> </td><td class="right">   There are several scenarios in which the address carried by messages</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   sent by a gateway may change without that gateway's knowledge, as for</td><td> </td><td class="right">   sent by a gateway may change without that gateway's knowledge, as for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   example, when:</td><td> </td><td class="right">   example, when:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l8"><small>skipping to change at</small><em> page 30, line 42</em></a></th><th> </th><th><a name="part-r8"><small>skipping to change at</small><em> page 30, line 42</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   |       |&lt;--------------------------------------------------|       |</td><td> </td><td class="right">   |       |&lt;--------------------------------------------------|       |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   |_______|  ^  |___|  ^  |___|__|  ^  |__|___|  ^  |___|  ^  |_______|</td><td> </td><td class="right">   |_______|  ^  |___|  ^  |___|__|  ^  |__|___|  ^  |___|  ^  |_______|</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              |         |            |            |         |</td><td> </td><td class="right">              |         |            |            |         |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">             IP      AMT:IP    IP:UDP:AMT:IP    AMT:IP      IP</td><td> </td><td class="right">             IP      AMT:IP    IP:UDP:AMT:IP    AMT:IP      IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                             AMT Encapsulation</td><td> </td><td class="right">                             AMT Encapsulation</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The IGMP and MLD messages used in AMT are exchanged as complete IP</td><td> </td><td class="right">   The IGMP and MLD messages used in AMT are exchanged as complete IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   datagrams.  These IP datagrams are encapsulated in AMT messages that</td><td> </td><td class="right">   datagrams.  These IP datagrams are encapsulated in AMT messages that</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   are transmitted using UDP.  The same holds true for multicast traffic</td><td> </td><td class="right">   are transmitted using UDP.  The same holds true for multicast traffic</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0010"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   - each multicast IP datagram that arrives at the relay is</td><td> </td><td class="rblock">   - each multicast IP datagram <span class="insert">or datagram fragment</span> that arrives at the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   encapsulated in an AMT message and transmitted to one or more</td><td> </td><td class="rblock">   relay is encapsulated in an AMT message and transmitted to one or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   gateways via UDP.</td><td> </td><td class="rblock">   more gateways via UDP.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The IP protocol of the encapsulated packets need not match the IP</td><td> </td><td class="right">   The IP protocol of the encapsulated packets need not match the IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   protocol used to send the AMT messages.  AMT messages sent via IPv4</td><td> </td><td class="right">   protocol used to send the AMT messages.  AMT messages sent via IPv4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   may carry IPv6/MLD packets and AMT messages sent via IPv6 may carry</td><td> </td><td class="right">   may carry IPv6/MLD packets and AMT messages sent via IPv6 may carry</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IPv4/IGMP packets.</td><td> </td><td class="right">   IPv4/IGMP packets.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The checksum field contained in the UDP header of the messages</td><td> </td><td class="right">   The checksum field contained in the UDP header of the messages</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   requires special consideration.  Of primary concern is the cost of</td><td> </td><td class="right">   requires special consideration.  Of primary concern is the cost of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   computing a checksum on each replicated multicast packet after it is</td><td> </td><td class="right">   computing a checksum on each replicated multicast packet after it is</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   encapsulated for delivery to a gateway.  Many routing/forwarding</td><td> </td><td class="right">   encapsulated for delivery to a gateway.  Many routing/forwarding</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l9"><small>skipping to change at</small><em> page 33, line 5</em></a></th><th> </th><th><a name="part-r9"><small>skipping to change at</small><em> page 33, line 5</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Source IP Address -  The IP address of the gateway interface on which</td><td> </td><td class="right">   Source IP Address -  The IP address of the gateway interface on which</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      the gateway will listen for a relay response.  Note: The value of</td><td> </td><td class="right">      the gateway will listen for a relay response.  Note: The value of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      this field may be changed as a result of network address</td><td> </td><td class="right">      this field may be changed as a result of network address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      translation before arriving at the relay.</td><td> </td><td class="right">      translation before arriving at the relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Source UDP Port -  The UDP port number on which the gateway will</td><td> </td><td class="right">   Source UDP Port -  The UDP port number on which the gateway will</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      listen for a relay response.  Note: The value of this field may be</td><td> </td><td class="right">      listen for a relay response.  Note: The value of this field may be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      changed as a result of network address translation before arriving</td><td> </td><td class="right">      changed as a result of network address translation before arriving</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      at the relay.</td><td> </td><td class="right">      at the relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0011"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Destination IP Address -  An anycast or unicast IP address, i.e. the</td><td> </td><td class="rblock">   Destination IP Address -  An anycast or unicast IP address, i.e.<span class="insert">,</span> the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Relay Discovery Address advertised by a relay.</td><td> </td><td class="right">      Relay Discovery Address advertised by a relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Destination UDP Port -  The IANA-assigned AMT port number.</td><td> </td><td class="right">   Destination UDP Port -  The IANA-assigned AMT port number.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">    0                   1                   2                   3</td><td> </td><td class="right">    0                   1                   2                   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1</td><td> </td><td class="right">    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td> </td><td class="right">   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   |  V=0  |Type=1 |     Reserved                                  |</td><td> </td><td class="right">   |  V=0  |Type=1 |     Reserved                                  |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td> </td><td class="right">   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   |                        Discovery Nonce                        |</td><td> </td><td class="right">   |                        Discovery Nonce                        |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l10"><small>skipping to change at</small><em> page 34, line 6</em></a></th><th> </th><th><a name="part-r10"><small>skipping to change at</small><em> page 34, line 6</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The Relay Advertisement message is used to supply a gateway with a</td><td> </td><td class="right">   The Relay Advertisement message is used to supply a gateway with a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   unicast IP address of a relay.  A relay sends this message to a</td><td> </td><td class="right">   unicast IP address of a relay.  A relay sends this message to a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateway when it receives a Relay Discovery message from that gateway.</td><td> </td><td class="right">   gateway when it receives a Relay Discovery message from that gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The UDP/IP datagram containing this message MUST carry a valid, non-</td><td> </td><td class="right">   The UDP/IP datagram containing this message MUST carry a valid, non-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   zero UDP checksum and carry the following IP address and UDP port</td><td> </td><td class="right">   zero UDP checksum and carry the following IP address and UDP port</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   values:</td><td> </td><td class="right">   values:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Source IP Address -  The destination IP address carried by the Relay</td><td> </td><td class="right">   Source IP Address -  The destination IP address carried by the Relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0012"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      Discovery message (i.e. the Relay Discovery Address advertised by</td><td> </td><td class="rblock">      Discovery message (i.e.<span class="insert">,</span> the Relay Discovery Address advertised by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      the relay).</td><td> </td><td class="right">      the relay).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Source UDP Port -  The destination UDP port carried by the Relay</td><td> </td><td class="right">   Source UDP Port -  The destination UDP port carried by the Relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0013"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      Discovery message (i.e. the IANA-assigned AMT port number).</td><td> </td><td class="rblock">      Discovery message (i.e.<span class="insert">,</span> the IANA-assigned AMT port number).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Destination IP Address -  The source IP address carried by the Relay</td><td> </td><td class="right">   Destination IP Address -  The source IP address carried by the Relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Discovery message.  Note: The value of this field may be changed</td><td> </td><td class="right">      Discovery message.  Note: The value of this field may be changed</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      as a result of network address translation before arriving at the</td><td> </td><td class="right">      as a result of network address translation before arriving at the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      gateway.</td><td> </td><td class="right">      gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Destination UDP Port -  The source UDP port carried by the Relay</td><td> </td><td class="right">   Destination UDP Port -  The source UDP port carried by the Relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Discovery message.  Note: The value of this field may be changed</td><td> </td><td class="right">      Discovery message.  Note: The value of this field may be changed</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      as a result of network address translation before arriving at the</td><td> </td><td class="right">      as a result of network address translation before arriving at the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      gateway.</td><td> </td><td class="right">      gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l11"><small>skipping to change at</small><em> page 35, line 16</em></a></th><th> </th><th><a name="part-r11"><small>skipping to change at</small><em> page 35, line 16</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A 32-bit value copied from the Discovery Nonce field</td><td> </td><td class="right">   A 32-bit value copied from the Discovery Nonce field</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 5.1.1.4) contained in the Relay Discovery message.  The</td><td> </td><td class="right">   (Section 5.1.1.4) contained in the Relay Discovery message.  The</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateway uses this value to match a Relay Advertisement to a Relay</td><td> </td><td class="right">   gateway uses this value to match a Relay Advertisement to a Relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Discovery message.</td><td> </td><td class="right">   Discovery message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.2.5.  Relay Address</td><td> </td><td class="right">5.1.2.5.  Relay Address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The unicast IPv4 or IPv6 address of the relay.  A gateway uses the</td><td> </td><td class="right">   The unicast IPv4 or IPv6 address of the relay.  A gateway uses the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   length of the UDP datagram containing the Relay Advertisement message</td><td> </td><td class="right">   length of the UDP datagram containing the Relay Advertisement message</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0014"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   to determine the address family; <span class="delete">i.e.</span> length - 8 = 4 (IPv4) or 16</td><td> </td><td class="rblock">   to determine the address family; <span class="insert">i.e.,</span> length - 8 = 4 (IPv4) or 16</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   (IPv6).</td><td> </td><td class="rblock">   (IPv6).  <span class="insert">The relay returns an IP address for the protocol used to</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   send the Relay Discovery message, i.e., an IPv4 relay address for an</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   IPv4 discovery address or an IPv6 relay address for an IPv6 discovery</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   address.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.3.  Request</td><td> </td><td class="right">5.1.3.  Request</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway sends a Request message to a relay to solicit a Membership</td><td> </td><td class="right">   A gateway sends a Request message to a relay to solicit a Membership</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Query response.</td><td> </td><td class="right">   Query response.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The successful delivery of this message marks the start of the first</td><td> </td><td class="right">   The successful delivery of this message marks the start of the first</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   stage in the three-way handshake used to create or update state</td><td> </td><td class="right">   stage in the three-way handshake used to create or update state</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   within a relay.</td><td> </td><td class="right">   within a relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l12"><small>skipping to change at</small><em> page 37, line 10</em></a></th><th> </th><th><a name="part-r12"><small>skipping to change at</small><em> page 37, line 20</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The successful delivery of this message to a gateway marks the start</td><td> </td><td class="right">   The successful delivery of this message to a gateway marks the start</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the second-stage in the three-way handshake used to create or</td><td> </td><td class="right">   of the second-stage in the three-way handshake used to create or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   update tunnel state within a relay.</td><td> </td><td class="right">   update tunnel state within a relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The UDP/IP datagram containing this message MUST carry a valid, non-</td><td> </td><td class="right">   The UDP/IP datagram containing this message MUST carry a valid, non-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   zero UDP checksum and carry the following IP address and UDP port</td><td> </td><td class="right">   zero UDP checksum and carry the following IP address and UDP port</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   values:</td><td> </td><td class="right">   values:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Source IP Address -  The destination IP address carried by the</td><td> </td><td class="right">   Source IP Address -  The destination IP address carried by the</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0015"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      Request message (i.e. the unicast IP address of the relay).</td><td> </td><td class="rblock">      Request message (i.e.<span class="insert">,</span> the unicast IP address of the relay).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Source UDP Port -  The destination UDP port carried by the Request</td><td> </td><td class="right">   Source UDP Port -  The destination UDP port carried by the Request</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0016"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      message (i.e. the IANA-assigned AMT port number).</td><td> </td><td class="rblock">      message (i.e.<span class="insert">,</span> the IANA-assigned AMT port number).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Destination IP Address -  The source IP address carried by the</td><td> </td><td class="right">   Destination IP Address -  The source IP address carried by the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Request message.  Note: The value of this field may be changed as</td><td> </td><td class="right">      Request message.  Note: The value of this field may be changed as</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      a result of network address translation before arriving at the</td><td> </td><td class="right">      a result of network address translation before arriving at the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      gateway.</td><td> </td><td class="right">      gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Destination UDP Port -  The source UDP port carried by the Request</td><td> </td><td class="right">   Destination UDP Port -  The source UDP port carried by the Request</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      message.  Note: The value of this field may be changed as a result</td><td> </td><td class="right">      message.  Note: The value of this field may be changed as a result</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      of network address translation before arriving at the gateway.</td><td> </td><td class="right">      of network address translation before arriving at the gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l13"><small>skipping to change at</small><em> page 38, line 35</em></a></th><th> </th><th><a name="part-r13"><small>skipping to change at</small><em> page 39, line 14</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   this flag before attempting to create new group subscription state on</td><td> </td><td class="right">   this flag before attempting to create new group subscription state on</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the relay to determine whether it should restart relay discovery.  A</td><td> </td><td class="right">   the relay to determine whether it should restart relay discovery.  A</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateway that has already created group subscriptions on the relay may</td><td> </td><td class="right">   gateway that has already created group subscriptions on the relay may</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   ignore this flag.  Support for this flag is RECOMMENDED.</td><td> </td><td class="right">   ignore this flag.  Support for this flag is RECOMMENDED.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.4.5.  Gateway Address (G) Flag</td><td> </td><td class="right">5.1.4.5.  Gateway Address (G) Flag</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A 1-bit flag set to 0 to indicate that the message does NOT carry the</td><td> </td><td class="right">   A 1-bit flag set to 0 to indicate that the message does NOT carry the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Gateway Port and Gateway IP Address fields, and 1 to indicate that it</td><td> </td><td class="right">   Gateway Port and Gateway IP Address fields, and 1 to indicate that it</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   does.  A relay implementation that supports the optional teardown</td><td> </td><td class="right">   does.  A relay implementation that supports the optional teardown</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0017"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   procedure (See Section 5.3.3.5) SHOULD set this flag and <span class="delete">and</span> the</td><td> </td><td class="rblock">   procedure (See Section 5.3.3.5) SHOULD set this flag and the Gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Gateway Address field values.  If a relay sets this flag, it MUST</td><td> </td><td class="rblock">   Address field values.  If a relay sets this flag, it MUST also</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   also include the Gateway Address fields in the message.  A gateway</td><td> </td><td class="rblock">   include the Gateway Address fields in the message.  A gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   implementation that does not support the optional teardown procedure</td><td> </td><td class="right">   implementation that does not support the optional teardown procedure</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (See Section 5.2.3.7) MAY ignore this flag and the Gateway Address</td><td> </td><td class="right">   (See Section 5.2.3.7) MAY ignore this flag and the Gateway Address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   fields if they are present.</td><td> </td><td class="right">   fields if they are present.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.4.6.  Response MAC</td><td> </td><td class="right">5.1.4.6.  Response MAC</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A 48-bit source authentication hash generated by the relay as</td><td> </td><td class="right">   A 48-bit source authentication hash generated by the relay as</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   described in Section 5.3.5.  The gateway echoes this value in</td><td> </td><td class="right">   described in Section 5.3.5.  The gateway echoes this value in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   subsequent Membership Update messages to allow the relay to verify</td><td> </td><td class="right">   subsequent Membership Update messages to allow the relay to verify</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   that the sender of a Membership Update message was the intended</td><td> </td><td class="right">   that the sender of a Membership Update message was the intended</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l14"><small>skipping to change at</small><em> page 39, line 43</em></a></th><th> </th><th><a name="part-r14"><small>skipping to change at</small><em> page 40, line 19</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Update messages, and optionally, the number of times to</td><td> </td><td class="right">   Membership Update messages, and optionally, the number of times to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   send a Teardown message.</td><td> </td><td class="right">   send a Teardown message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.4.9.  Gateway Address Fields</td><td> </td><td class="right">5.1.4.9.  Gateway Address Fields</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The Gateway Port Number and Gateway Address fields are present in the</td><td> </td><td class="right">   The Gateway Port Number and Gateway Address fields are present in the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Query message if, and only if, the "G" flag is set.</td><td> </td><td class="right">   Membership Query message if, and only if, the "G" flag is set.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway need not parse the encapsulated IP datagram to determine</td><td> </td><td class="right">   A gateway need not parse the encapsulated IP datagram to determine</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the position of these fields within the UDP datagram containing the</td><td> </td><td class="right">   the position of these fields within the UDP datagram containing the</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0018"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Membership Query mess<span class="delete">s</span>age - if the G-flag is set, the gateway may</td><td> </td><td class="rblock">   Membership Query message - if the G-flag is set, the gateway may</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   simply subtract the total length of the fields (18 bytes) from the</td><td> </td><td class="right">   simply subtract the total length of the fields (18 bytes) from the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   total length of the UDP datagram to obtain the offset.</td><td> </td><td class="right">   total length of the UDP datagram to obtain the offset.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.4.9.1.  Gateway Port Number</td><td> </td><td class="right">5.1.4.9.1.  Gateway Port Number</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A 16-bit UDP port containing a UDP port value.</td><td> </td><td class="right">   A 16-bit UDP port containing a UDP port value.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The Relay sets this field to the value of the UDP source port of the</td><td> </td><td class="right">   The Relay sets this field to the value of the UDP source port of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Request message that triggered the Query message.</td><td> </td><td class="right">   Request message that triggered the Query message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l15"><small>skipping to change at</small><em> page 40, line 36</em></a></th><th> </th><th><a name="part-r15"><small>skipping to change at</small><em> page 41, line 13</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway cannot send a Membership Update message until a receives a</td><td> </td><td class="right">   A gateway cannot send a Membership Update message until a receives a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Query from a relay because the gateway must copy the</td><td> </td><td class="right">   Membership Query from a relay because the gateway must copy the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Request Nonce and Response MAC values carried by a Membership Query</td><td> </td><td class="right">   Request Nonce and Response MAC values carried by a Membership Query</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   into any subsequent Membership Update messages it sends back to that</td><td> </td><td class="right">   into any subsequent Membership Update messages it sends back to that</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   relay.  These values are used by the relay to verify that the sender</td><td> </td><td class="right">   relay.  These values are used by the relay to verify that the sender</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the Membership Update message was the recipient of the Membership</td><td> </td><td class="right">   of the Membership Update message was the recipient of the Membership</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Query message from which these values were copied.</td><td> </td><td class="right">   Query message from which these values were copied.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The successful delivery of this message to the relay marks the start</td><td> </td><td class="right">   The successful delivery of this message to the relay marks the start</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the final stage in the three-way handshake.  This stage concludes</td><td> </td><td class="right">   of the final stage in the three-way handshake.  This stage concludes</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0019"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   when the relay successfully verifies that sender of the Me<span class="delete">ssage</span></td><td> </td><td class="rblock">   when the relay successfully verifies that sender of the Me<span class="insert">mbership</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Update message was the recipient of a Membership Query message sent</td><td> </td><td class="right">   Update message was the recipient of a Membership Query message sent</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   earlier.  At this point, the relay may proceed to process the</td><td> </td><td class="right">   earlier.  At this point, the relay may proceed to process the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   encapsulated IGMP or MLD message to create or update group membership</td><td> </td><td class="right">   encapsulated IGMP or MLD message to create or update group membership</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and forwarding state on behalf of the gateway.</td><td> </td><td class="right">   and forwarding state on behalf of the gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The UDP/IP datagram containing this message MUST carry a valid, non-</td><td> </td><td class="right">   The UDP/IP datagram containing this message MUST carry a valid, non-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   zero UDP checksum and carry the following IP address and UDP port</td><td> </td><td class="right">   zero UDP checksum and carry the following IP address and UDP port</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   values:</td><td> </td><td class="right">   values:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Source IP Address -  The IP address of the gateway interface on which</td><td> </td><td class="right">   Source IP Address -  The IP address of the gateway interface on which</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l16"><small>skipping to change at</small><em> page 42, line 34</em></a></th><th> </th><th><a name="part-r16"><small>skipping to change at</small><em> page 43, line 22</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      IPv6:MLDv1 Multicast Listener Done</td><td> </td><td class="right">      IPv6:MLDv1 Multicast Listener Done</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      IPv6:MLDv2 Multicast Listener Report</td><td> </td><td class="right">      IPv6:MLDv2 Multicast Listener Report</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The source address carried by the message should be set as described</td><td> </td><td class="right">   The source address carried by the message should be set as described</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   in Section 5.2.1.</td><td> </td><td class="right">   in Section 5.2.1.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.6.  Multicast Data</td><td> </td><td class="right">5.1.6.  Multicast Data</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0020"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   A relay sends a Multicast Data message to deliver an <span class="delete">IP</span> multicast</td><td> </td><td class="rblock">   A relay sends a Multicast Data message to deliver an multicast <span class="insert">IP</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">packet</span> to a gateway.</td><td> </td><td class="rblock"><span class="insert">   datagram or datagram fragment</span> to a gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The checksum field in the UDP header of this message MAY contain a</td><td> </td><td class="right">   The checksum field in the UDP header of this message MAY contain a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   value of zero when sent over IPv4 but SHOULD, if possible, contain a</td><td> </td><td class="right">   value of zero when sent over IPv4 but SHOULD, if possible, contain a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   valid, non-zero value when sent over IPv6 (See Section 4.2.2.3).</td><td> </td><td class="right">   valid, non-zero value when sent over IPv6 (See Section 4.2.2.3).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The UDP/IP datagram containing this message MUST carry the following</td><td> </td><td class="right">   The UDP/IP datagram containing this message MUST carry the following</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IP address and UDP port values:</td><td> </td><td class="right">   IP address and UDP port values:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Source IP Address -  The unicast IP address of the relay.</td><td> </td><td class="right">   Source IP Address -  The unicast IP address of the relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Source UDP Port -  The IANA-assigned AMT port number.</td><td> </td><td class="right">   Source UDP Port -  The IANA-assigned AMT port number.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0021"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Destination IP Address -  A tunnel endpoint IP address, i.e. the</td><td> </td><td class="rblock">   Destination IP Address -  A tunnel endpoint IP address, i.e.<span class="insert">,</span> the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      source IP address carried by the Membership Update message sent by</td><td> </td><td class="right">      source IP address carried by the Membership Update message sent by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      a gateway to indicate an interest in receiving the multicast</td><td> </td><td class="right">      a gateway to indicate an interest in receiving the multicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      packet.  Note: The value of this field may be changed as a result</td><td> </td><td class="right">      packet.  Note: The value of this field may be changed as a result</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      of network address translation before arriving at the gateway.</td><td> </td><td class="right">      of network address translation before arriving at the gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0022"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Destination UDP Port -  A tunnel endpoint UDP port, i.e. the source</td><td> </td><td class="rblock">   Destination UDP Port -  A tunnel endpoint UDP port, i.e.<span class="insert">,</span> the source</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      UDP port carried by the Membership Update message sent by a</td><td> </td><td class="right">      UDP port carried by the Membership Update message sent by a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      gateway to indicate an interest in receiving the multicast packet.</td><td> </td><td class="right">      gateway to indicate an interest in receiving the multicast packet.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Note: The value of this field may be changed as a result of</td><td> </td><td class="right">      Note: The value of this field may be changed as a result of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      network address translation before arriving at the gateway.</td><td> </td><td class="right">      network address translation before arriving at the gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">    0                   1                   2                   3</td><td> </td><td class="right">    0                   1                   2                   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1</td><td> </td><td class="right">    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td> </td><td class="right">   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   |  V=0  |Type=6 |    Reserved   |                               |</td><td> </td><td class="right">   |  V=0  |Type=6 |    Reserved   |                               |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               +</td><td> </td><td class="right">   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               +</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l17"><small>skipping to change at</small><em> page 43, line 40</em></a></th><th> </th><th><a name="part-r17"><small>skipping to change at</small><em> page 44, line 34</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The type number for this message is 6.</td><td> </td><td class="right">   The type number for this message is 6.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.6.3.  Reserved</td><td> </td><td class="right">5.1.6.3.  Reserved</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Bits that MUST be set to zero by the relay and ignored by the</td><td> </td><td class="right">   Bits that MUST be set to zero by the relay and ignored by the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateway.</td><td> </td><td class="right">   gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.6.4.  IP Multicast Data</td><td> </td><td class="right">5.1.6.4.  IP Multicast Data</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0023"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   A complete IPv4 or IPv6 <span class="delete">Multicast datagram</span>.</td><td> </td><td class="rblock">   A complete IPv4 or IPv6 <span class="insert">multicast datagram or datagram fragment</span>.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.7.  Teardown</td><td> </td><td class="right">5.1.7.  Teardown</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway sends a Teardown message to a relay to request that it stop</td><td> </td><td class="right">   A gateway sends a Teardown message to a relay to request that it stop</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   sending Multicast Data messages to a tunnel endpoint created by an</td><td> </td><td class="right">   sending Multicast Data messages to a tunnel endpoint created by an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   earlier Membership Update message.  A gateway sends this message when</td><td> </td><td class="right">   earlier Membership Update message.  A gateway sends this message when</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   it detects that a Request message sent to the relay carries an</td><td> </td><td class="right">   it detects that a Request message sent to the relay carries an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address that differs from that carried by a previous Request message.</td><td> </td><td class="right">   address that differs from that carried by a previous Request message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The gateway uses the Gateway IP Address and Gateway Port Number</td><td> </td><td class="right">   The gateway uses the Gateway IP Address and Gateway Port Number</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Fields in the Membership Query message to detect these address</td><td> </td><td class="right">   Fields in the Membership Query message to detect these address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l18"><small>skipping to change at</small><em> page 45, line 24</em></a></th><th> </th><th><a name="part-r18"><small>skipping to change at</small><em> page 46, line 16</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Reserved bits that MUST be set to zero by the gateway and ignored by</td><td> </td><td class="right">   Reserved bits that MUST be set to zero by the gateway and ignored by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the relay.</td><td> </td><td class="right">   the relay.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.7.4.  Response MAC</td><td> </td><td class="right">5.1.7.4.  Response MAC</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A 48-bit value copied from the Response MAC field (Section 5.1.4.6)</td><td> </td><td class="right">   A 48-bit value copied from the Response MAC field (Section 5.1.4.6)</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   in the last Membership Query message the relay sent to the gateway</td><td> </td><td class="right">   in the last Membership Query message the relay sent to the gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   endpoint address of the tunnel to be torn down.  The gateway endpoint</td><td> </td><td class="right">   endpoint address of the tunnel to be torn down.  The gateway endpoint</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address is provided by the Gateway IP Address and Gateway Port Number</td><td> </td><td class="right">   address is provided by the Gateway IP Address and Gateway Port Number</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0024"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   fields carried by the Membership Query message.</td><td> </td><td class="rblock">   fields carried by the Membership Query message.  <span class="insert">The relay validates</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   the Teardown message by comparing this value with one computed from</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   the Request Nonce, Gateway Port Number and Gateway IP Address fields</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   (just as it does in the Membership Update message).</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.1.7.5.  Request Nonce</td><td> </td><td class="right">5.1.7.5.  Request Nonce</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A 32-bit value copied from the Request Nonce field (Section 5.1.4.7)</td><td> </td><td class="right">   A 32-bit value copied from the Request Nonce field (Section 5.1.4.7)</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   in the last Membership Query message the relay sent to the gateway</td><td> </td><td class="right">   in the last Membership Query message the relay sent to the gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   endpoint address of the tunnel to be torn down.  The gateway endpoint</td><td> </td><td class="right">   endpoint address of the tunnel to be torn down.  The gateway endpoint</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address is provided by the Gateway IP Address and Gateway Port Number</td><td> </td><td class="right">   address is provided by the Gateway IP Address and Gateway Port Number</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   fields carried by the Membership Query message.  This value must</td><td> </td><td class="right">   fields carried by the Membership Query message.  This value must</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   match that used by the relay to compute the value stored in the</td><td> </td><td class="right">   match that used by the relay to compute the value stored in the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Response MAC field.</td><td> </td><td class="right">   Response MAC field.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l19"><small>skipping to change at</small><em> page 46, line 48</em></a></th><th> </th><th><a name="part-r19"><small>skipping to change at</small><em> page 47, line 42</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   options and header values called for in [RFC3376], with the following</td><td> </td><td class="right">   options and header values called for in [RFC3376], with the following</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   exception; the source IP address for an IGMP report datagram MAY be</td><td> </td><td class="right">   exception; the source IP address for an IGMP report datagram MAY be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   set to the "unspecified" address (all octets are zero ) but SHOULD be</td><td> </td><td class="right">   set to the "unspecified" address (all octets are zero ) but SHOULD be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   set to an address in the address range specifically assigned by IANA</td><td> </td><td class="right">   set to an address in the address range specifically assigned by IANA</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   for use in the IGMP messages sent from a gateway to a relay (i.e.</td><td> </td><td class="right">   for use in the IGMP messages sent from a gateway to a relay (i.e.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   154.7.1.2 through 154.7.1.254 as described in Section 7).  This</td><td> </td><td class="right">   154.7.1.2 through 154.7.1.254 as described in Section 7).  This</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   exception is made because the gateway pseudo-interface might not</td><td> </td><td class="right">   exception is made because the gateway pseudo-interface might not</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   possess an assigned address, and even if such an address exists, that</td><td> </td><td class="right">   possess an assigned address, and even if such an address exists, that</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address would not be a valid link-local source address on any relay</td><td> </td><td class="right">   address would not be a valid link-local source address on any relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interface.  The rationale for using the aforementioned source</td><td> </td><td class="right">   interface.  The rationale for using the aforementioned source</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0025"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   addresses is <span class="delete">primary</span> one of convenience - a relay will accept an IGMP</td><td> </td><td class="rblock">   addresses is <span class="insert">primarily</span> one of convenience - a relay will accept an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   report carried by a Membership Update message regardless of the</td><td> </td><td class="rblock">   IGMP report carried by a Membership Update message regardless of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   source address it carries.  See Section 5.3.1.</td><td> </td><td class="right">   source address it carries.  See Section 5.3.1.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The IP-encapsulated MLD messages generated by the gateway IPv6/MLD</td><td> </td><td class="right">   The IP-encapsulated MLD messages generated by the gateway IPv6/MLD</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   implementation MUST conform to the description found in Section 5 of</td><td> </td><td class="right">   implementation MUST conform to the description found in Section 5 of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3810].  These datagrams MUST possess the IP headers, header</td><td> </td><td class="right">   [RFC3810].  These datagrams MUST possess the IP headers, header</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   options and header values called for in [RFC3810], with the following</td><td> </td><td class="right">   options and header values called for in [RFC3810], with the following</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   exception; the source IP address for an MLD report datagram MAY be</td><td> </td><td class="right">   exception; the source IP address for an MLD report datagram MAY be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   set to the "unspecified" address (all octets are zero ) but SHOULD be</td><td> </td><td class="right">   set to the "unspecified" address (all octets are zero ) but SHOULD be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   set to an IPv6 link-local address in the range FE80::/64 excluding</td><td> </td><td class="right">   set to an IPv6 link-local address in the range FE80::/64 excluding</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   FE80::1 and FE80::2.  This exception is made because the gateway</td><td> </td><td class="right">   FE80::1 and FE80::2.  This exception is made because the gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l20"><small>skipping to change at</small><em> page 47, line 47</em></a></th><th> </th><th><a name="part-r20"><small>skipping to change at</small><em> page 48, line 41</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   accept the MLD datagram regardless of the IP source address carried</td><td> </td><td class="right">   accept the MLD datagram regardless of the IP source address carried</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   by that datagram.</td><td> </td><td class="right">   by that datagram.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.2.2.  Pseudo-Interface Configuration</td><td> </td><td class="right">5.2.2.  Pseudo-Interface Configuration</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway host may possess or create multiple gateway pseudo-</td><td> </td><td class="right">   A gateway host may possess or create multiple gateway pseudo-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interfaces, each with a unique configuration that describes a binding</td><td> </td><td class="right">   interfaces, each with a unique configuration that describes a binding</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   to a specific IP protocol, relay address, relay discovery address or</td><td> </td><td class="right">   to a specific IP protocol, relay address, relay discovery address or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   upstream network interface.</td><td> </td><td class="right">   upstream network interface.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0026"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">5.2.2.1.  <span class="delete">Static Relay Address</span></td><td> </td><td class="rblock">5.2.2.1.  Relay Discovery Address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Before a gateway implementation can execute the AMT protocol to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request and receive multicast traffic, it must be supplied with a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   unicast relay address.  A gateway implementation may rely on static</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   address assignment or support some form of dynamic address discovery.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   This specification does not require the use of any particular method</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to obtain a relay address - an implementation may employ any method</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   that returns a suitable relay address.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">5.2.2.2.  Static</span> Relay Discovery Address</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If a gateway implementation uses AMT relay discovery to obtain a</td><td> </td><td class="right">   If a gateway implementation uses AMT relay discovery to obtain a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   relay address, it must first be supplied with a relay discovery</td><td> </td><td class="right">   relay address, it must first be supplied with a relay discovery</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address.  The relay discovery address may be an anycast or unicast</td><td> </td><td class="right">   address.  The relay discovery address may be an anycast or unicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   address.  A gateway implementation may rely on a static address</td><td> </td><td class="right">   address.  A gateway implementation may rely on a static address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   assignment or some form of dynamic address discovery.  This</td><td> </td><td class="right">   assignment or some form of dynamic address discovery.  This</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   specification does not require that a gateway implementation use any</td><td> </td><td class="right">   specification does not require that a gateway implementation use any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   particular method to obtain a relay discovery address - an</td><td> </td><td class="right">   particular method to obtain a relay discovery address - an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   implementation may employ any method that returns a suitable relay</td><td> </td><td class="right">   implementation may employ any method that returns a suitable relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   discovery address.</td><td> </td><td class="right">   discovery address.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0027"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">5.2.2.2.  Relay Address</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Before a gateway implementation can execute the AMT protocol to</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   request and receive multicast traffic, it must be supplied with a</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   unicast relay address.  A gateway implementation may rely on static</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   address assignment or support some form of dynamic address discovery.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   This specification does not require the use of any particular method</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   to obtain a relay address - an implementation may employ any method</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   that returns a suitable relay address.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.2.2.3.  Upstream Interface Selection</td><td> </td><td class="right">5.2.2.3.  Upstream Interface Selection</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway host that possesses multiple network interfaces or</td><td> </td><td class="right">   A gateway host that possesses multiple network interfaces or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   addresses may allow for an explicit selection of the interface to use</td><td> </td><td class="right">   addresses may allow for an explicit selection of the interface to use</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   when communicating with a relay.  The selection might be made to</td><td> </td><td class="right">   when communicating with a relay.  The selection might be made to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   satisfy connectivity, tunneling or IP protocol requirements.</td><td> </td><td class="right">   satisfy connectivity, tunneling or IP protocol requirements.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.2.2.4.  Optional Retransmission Parameters</td><td> </td><td class="right">5.2.2.4.  Optional Retransmission Parameters</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway implementation that supports retransmission MAY require the</td><td> </td><td class="right">   A gateway implementation that supports retransmission MAY require the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l21"><small>skipping to change at</small><em> page 50, line 13</em></a></th><th> </th><th><a name="part-r21"><small>skipping to change at</small><em> page 51, line 7</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway MUST ignore a Multicast Data message if it fails to satisfy</td><td> </td><td class="right">   A gateway MUST ignore a Multicast Data message if it fails to satisfy</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   any of the following requirements:</td><td> </td><td class="right">   any of the following requirements:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  The source IP address and UDP port carried by the Multicast Data</td><td> </td><td class="right">   o  The source IP address and UDP port carried by the Multicast Data</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      message MUST be equal to the destination IP address and UDP port</td><td> </td><td class="right">      message MUST be equal to the destination IP address and UDP port</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      carried by the matching Membership Update message (i.e., the</td><td> </td><td class="right">      carried by the matching Membership Update message (i.e., the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      current relay address).</td><td> </td><td class="right">      current relay address).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  The destination address carried by the encapsulated IP datagram</td><td> </td><td class="right">   o  The destination address carried by the encapsulated IP datagram</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      MUST fall within the multicast address allocation assigned to the</td><td> </td><td class="right">      MUST fall within the multicast address allocation assigned to the</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0028"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      rel<span class="delete">ave</span>nt IP protocol, i.e., 224.0.0.0/4 for IPv4 and FF00::/8 for</td><td> </td><td class="rblock">      rel<span class="insert">eva</span>nt IP protocol, i.e., 224.0.0.0/4 for IPv4 and FF00::/8 for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      IPv6.</td><td> </td><td class="right">      IPv6.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The gateway extracts the encapsulated IP datagram and forwards it to</td><td> </td><td class="right">   The gateway extracts the encapsulated IP datagram and forwards it to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the local IP protocol implementation for checksum verification,</td><td> </td><td class="right">   the local IP protocol implementation for checksum verification,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   fragmented datagram reassembly, source and group filtering, and</td><td> </td><td class="right">   fragmented datagram reassembly, source and group filtering, and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   transport-layer protocol processing.</td><td> </td><td class="right">   transport-layer protocol processing.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Because AMT uses UDP encapsulation to deliver multicast datagrams to</td><td> </td><td class="right">   Because AMT uses UDP encapsulation to deliver multicast datagrams to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateways, it qualifies as a tunneling protocol subject to the</td><td> </td><td class="right">   gateways, it qualifies as a tunneling protocol subject to the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   limitations described in [I-D.ietf-6man-udpzero].  If supported, a</td><td> </td><td class="right">   limitations described in [I-D.ietf-6man-udpzero].  If supported, a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l22"><small>skipping to change at</small><em> page 50, line 47</em></a></th><th> </th><th><a name="part-r22"><small>skipping to change at</small><em> page 51, line 41</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway may start or restart the relay discovery procedure in</td><td> </td><td class="right">   A gateway may start or restart the relay discovery procedure in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   response to the following events:</td><td> </td><td class="right">   response to the following events:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  When a gateway pseudo-interface is started (enabled).</td><td> </td><td class="right">   o  When a gateway pseudo-interface is started (enabled).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  When the gateway wishes to report a group subscription when none</td><td> </td><td class="right">   o  When the gateway wishes to report a group subscription when none</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      currently exist.</td><td> </td><td class="right">      currently exist.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Before sending the next Request message in a membership update</td><td> </td><td class="right">   o  Before sending the next Request message in a membership update</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0029"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      cycle, i.e. each time the query timer expires (see below).</td><td> </td><td class="rblock">      cycle, i.e.<span class="insert">,</span> each time the query timer expires (see below).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  After the gateway fails to receive a response to a Request</td><td> </td><td class="right">   o  After the gateway fails to receive a response to a Request</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      message.</td><td> </td><td class="right">      message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  After the gateway receives a Membership Query message with the</td><td> </td><td class="right">   o  After the gateway receives a Membership Query message with the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      L-flag set to 1.</td><td> </td><td class="right">      L-flag set to 1.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.2.3.4.2.  Sending a Relay Discovery Message</td><td> </td><td class="right">5.2.3.4.2.  Sending a Relay Discovery Message</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway sends a Relay Discovery message to a relay to start the</td><td> </td><td class="right">   A gateway sends a Relay Discovery message to a relay to start the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l23"><small>skipping to change at</small><em> page 56, line 12</em></a></th><th> </th><th><a name="part-r23"><small>skipping to change at</small><em> page 57, line 12</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   datagram within it, if the message fails to satisfy any of the</td><td> </td><td class="right">   datagram within it, if the message fails to satisfy any of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   following requirements:</td><td> </td><td class="right">   following requirements:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  The gateway MUST be waiting for a Membership Query message.</td><td> </td><td class="right">   o  The gateway MUST be waiting for a Membership Query message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  The Request Nonce value contained in the Membership Query MUST</td><td> </td><td class="right">   o  The Request Nonce value contained in the Membership Query MUST</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      equal the Request Nonce value contained in the Request message.</td><td> </td><td class="right">      equal the Request Nonce value contained in the Request message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  The source IP address and UDP port of the Membership Query MUST</td><td> </td><td class="right">   o  The source IP address and UDP port of the Membership Query MUST</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      equal the destination IP address and UDP port of the matching</td><td> </td><td class="right">      equal the destination IP address and UDP port of the matching</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0030"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      Request message (i.e. the current relay address).</td><td> </td><td class="rblock">      Request message (i.e.<span class="insert">,</span> the current relay address).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  The encapsulated IP datagram MUST carry an IGMPv3 or MLDv2</td><td> </td><td class="right">   o  The encapsulated IP datagram MUST carry an IGMPv3 or MLDv2</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      message.  The protocol MUST match the protocol identified by the</td><td> </td><td class="right">      message.  The protocol MUST match the protocol identified by the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      "P" flag in the Request message.</td><td> </td><td class="right">      "P" flag in the Request message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  The IGMPv3 or MLDv2 message MUST be a general query message.</td><td> </td><td class="right">   o  The IGMPv3 or MLDv2 message MUST be a general query message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  The total length of the encapsulated IP datagram as computed from</td><td> </td><td class="right">   o  The total length of the encapsulated IP datagram as computed from</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      the lengths contained in the datagram header(s) MUST NOT exceed</td><td> </td><td class="right">      the lengths contained in the datagram header(s) MUST NOT exceed</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      the available field length within the Membership Query message.</td><td> </td><td class="right">      the available field length within the Membership Query message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l24"><small>skipping to change at</small><em> page 56, line 40</em></a></th><th> </th><th><a name="part-r24"><small>skipping to change at</small><em> page 57, line 40</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   fields for use in sending subsequent Membership Update and Teardown</td><td> </td><td class="right">   fields for use in sending subsequent Membership Update and Teardown</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   messages.</td><td> </td><td class="right">   messages.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The gateway extracts the encapsulated IP datagram and forwards it to</td><td> </td><td class="right">   The gateway extracts the encapsulated IP datagram and forwards it to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the local IP protocol implementation for checksum verification and</td><td> </td><td class="right">   the local IP protocol implementation for checksum verification and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   dispatching to the IGMP or MLD implementation running on the pseudo-</td><td> </td><td class="right">   dispatching to the IGMP or MLD implementation running on the pseudo-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interface.  The gateway MUST NOT forward any octets that might exist</td><td> </td><td class="right">   interface.  The gateway MUST NOT forward any octets that might exist</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   between the encapsulated IP datagram and the end of the message or</td><td> </td><td class="right">   between the encapsulated IP datagram and the end of the message or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Gateway Address fields.</td><td> </td><td class="right">   Gateway Address fields.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0031"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">IGMP and</span> MLD protocol <span class="delete">specifications indicate</span> that senders should</td><td> </td><td class="rblock">   The MLD protocol <span class="insert">specification indicates</span> that senders should use a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   use a link-local source IP address in message datagrams.  This</td><td> </td><td class="rblock">   link-local source IP address in message datagrams.  This requirement</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   requirement must be relaxed for AMT because gateways and relays do</td><td> </td><td class="rblock">   must be relaxed for AMT because gateways and relays do not <span class="insert">normally</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   not share a common subnet.  For this reason, a gateway implementation</td><td> </td><td class="rblock">   share a common subnet.  For this reason, a gateway implementation</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   MUST accept <span class="delete">IGMP and</span> MLD query message datagrams regardless of the</td><td> </td><td class="rblock">   MUST accept MLD <span class="insert">(and IGMP)</span> query message datagrams regardless of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   source IP address they carry.</td><td> </td><td class="rblock">   source IP address they carry.  <span class="insert">This may require additional processing</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   on the part of the gateway that might be avoided if the relay and</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   gateway use the IPv4 and IPv6 addresses allocated for use in AMT</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   encapsulated control packets as described in Section 5.2.1.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The gateway MUST start a timer that will trigger the next iteration</td><td> </td><td class="right">   The gateway MUST start a timer that will trigger the next iteration</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the membership update cycle by executing the membership query</td><td> </td><td class="right">   of the membership update cycle by executing the membership query</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   procedure.  The gateway SHOULD compute the timer duration from the</td><td> </td><td class="right">   procedure.  The gateway SHOULD compute the timer duration from the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Querier's Query Interval Code carried by the general-query.  A</td><td> </td><td class="right">   Querier's Query Interval Code carried by the general-query.  A</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateway MAY use a smaller timer duration if required to refresh a NAT</td><td> </td><td class="right">   gateway MAY use a smaller timer duration if required to refresh a NAT</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   mapping that would otherwise timeout.  A gateway MAY use a larger</td><td> </td><td class="right">   mapping that would otherwise timeout.  A gateway MAY use a larger</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   timer duration if it has no group subscriptions to report.</td><td> </td><td class="right">   timer duration if it has no group subscriptions to report.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the gateway supports the Teardown message and the G-flag is set in</td><td> </td><td class="right">   If the gateway supports the Teardown message and the G-flag is set in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l25"><small>skipping to change at</small><em> page 58, line 24</em></a></th><th> </th><th><a name="part-r25"><small>skipping to change at</small><em> page 59, line 26</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  IPv6 datagrams that carry an MLDv1 or MLDv2 Multicast Listener</td><td> </td><td class="right">   o  IPv6 datagrams that carry an MLDv1 or MLDv2 Multicast Listener</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Report or an MLDv1 Multicast Listener Done message as described in</td><td> </td><td class="right">      Report or an MLDv1 Multicast Listener Done message as described in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Section 5 of [RFC3810].</td><td> </td><td class="right">      Section 5 of [RFC3810].</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The gateway must be prepared to receive these messages any time the</td><td> </td><td class="right">   The gateway must be prepared to receive these messages any time the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   pseudo-interface is running.  The gateway MUST ignore any datagrams</td><td> </td><td class="right">   pseudo-interface is running.  The gateway MUST ignore any datagrams</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   not listed above.</td><td> </td><td class="right">   not listed above.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway that waits to start a membership update cycle until after</td><td> </td><td class="right">   A gateway that waits to start a membership update cycle until after</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0032"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   it receives an IGMP/MLD state-change message MAY:</td><td> </td><td class="rblock">   it receives <span class="insert">a datagram containing</span> an IGMP/MLD state-change message</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   MAY:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0033"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  Discard datagrams <span class="delete">containing IGMP/MLD messages</span> until it receives a</td><td> </td><td class="rblock">   o  Discard <span class="insert">IGMP or MLD</span> datagrams until it receives a Membership Query</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      Membership Query message, at which time it processes the</td><td> </td><td class="rblock">      message, at which time it processes the Membership Query message</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      Membership Query message as normal to eventually produce a</td><td> </td><td class="rblock">      as normal to eventually produce a current-state report on the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      current-state report on the pseudo-interface which describes the</td><td> </td><td class="rblock">      pseudo-interface which describes the end state (RECOMMENDED).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      end state (RECOMMENDED).</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0034"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  Insert <span class="delete">IGMP/MLD messages</span> into a queue for transmission after it</td><td> </td><td class="rblock">   o  Insert <span class="insert">IGMP or MLD datagrams</span> into a queue for transmission after</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      receives a Membership Query message.</td><td> </td><td class="rblock">      it receives a Membership Query message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0035"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   If <span class="delete">the datagram contains</span> a <span class="delete">valid</span> IGMP or <span class="delete">MLD message, the gateway</span></td><td> </td><td class="rblock">   If <span class="insert">and when</span> a <span class="insert">gateway receives a Membership Query message (for</span> IGMP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   sends</span> it to the relay as described in the next section.</td><td> </td><td class="rblock">   or <span class="insert">MLD)</span> it <span class="insert">sends any queued or incoming IGMP or MLD datagrams</span> to the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   relay as described in the next section.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.2.3.6.2.  Sending a Membership Update Message</td><td> </td><td class="right">5.2.3.6.2.  Sending a Membership Update Message</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway cannot send a Membership Update message to a relay until it</td><td> </td><td class="right">   A gateway cannot send a Membership Update message to a relay until it</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   has received a Membership Query message from a relay.  If the gateway</td><td> </td><td class="right">   has received a Membership Query message from a relay.  If the gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   has not yet located a relay with which to communicate, it MUST first</td><td> </td><td class="right">   has not yet located a relay with which to communicate, it MUST first</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   execute the relay discovery procedure described in Section 5.2.3.4 to</td><td> </td><td class="right">   execute the relay discovery procedure described in Section 5.2.3.4 to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   obtain a relay address.  If the gateway has a relay address, but has</td><td> </td><td class="right">   obtain a relay address.  If the gateway has a relay address, but has</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   not yet received a Membership Query message, it MUST first execute</td><td> </td><td class="right">   not yet received a Membership Query message, it MUST first execute</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the membership query procedure described in Section 5.2.3.5 to obtain</td><td> </td><td class="right">   the membership query procedure described in Section 5.2.3.5 to obtain</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l26"><small>skipping to change at</small><em> page 59, line 51</em></a></th><th> </th><th><a name="part-r26"><small>skipping to change at</small><em> page 61, line 7</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   group memberships created by the gateway.</td><td> </td><td class="right">   group memberships created by the gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   When a gateway constructs a Teardown message, it MUST copy the</td><td> </td><td class="right">   When a gateway constructs a Teardown message, it MUST copy the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Request Nonce, Response MAC, Gateway IP Address and Gateway Port</td><td> </td><td class="right">   Request Nonce, Response MAC, Gateway IP Address and Gateway Port</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Number fields from the Membership Query message that provided the</td><td> </td><td class="right">   Number fields from the Membership Query message that provided the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Response MAC for the last Membership Update message sent, into the</td><td> </td><td class="right">   Response MAC for the last Membership Update message sent, into the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   corresponding fields of the Teardown message.</td><td> </td><td class="right">   corresponding fields of the Teardown message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A gateway MUST send the Teardown message using the Relay Address and</td><td> </td><td class="right">   A gateway MUST send the Teardown message using the Relay Address and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IANA-assigned AMT port number as the destination.  A gateway MAY send</td><td> </td><td class="right">   IANA-assigned AMT port number as the destination.  A gateway MAY send</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0036"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   the <span class="delete">the </span>Teardown message multiple times for robustness.  The gateway</td><td> </td><td class="rblock">   the Teardown message multiple times for robustness.  The gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   SHOULD use the Querier's Robustness Variable (QRV) field contained in</td><td> </td><td class="right">   SHOULD use the Querier's Robustness Variable (QRV) field contained in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the query encapsulated within the last Membership Query to set the</td><td> </td><td class="right">   the query encapsulated within the last Membership Query to set the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   limit on the number of retransmissions.  If the gateway sends the</td><td> </td><td class="right">   limit on the number of retransmissions.  If the gateway sends the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Teardown message multiple times, it SHOULD insert a delay between</td><td> </td><td class="right">   Teardown message multiple times, it SHOULD insert a delay between</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   each transmission using the timing algorithm employed in IGMP/MLD for</td><td> </td><td class="right">   each transmission using the timing algorithm employed in IGMP/MLD for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   transmitting unsolicited state-change reports.  The RECOMMENDED</td><td> </td><td class="right">   transmitting unsolicited state-change reports.  The RECOMMENDED</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   default delay value is 1 second.</td><td> </td><td class="right">   default delay value is 1 second.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   When a gateway sends a Teardown message, it may be notified that an</td><td> </td><td class="right">   When a gateway sends a Teardown message, it may be notified that an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   ICMP Destination Unreachable message was received as a result of an</td><td> </td><td class="right">   ICMP Destination Unreachable message was received as a result of an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l27"><small>skipping to change at</small><em> page 61, line 47</em></a></th><th> </th><th><a name="part-r27"><small>skipping to change at</small><em> page 62, line 50</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay requires a subset of router-mode IGMP and MLD functionality</td><td> </td><td class="right">   A relay requires a subset of router-mode IGMP and MLD functionality</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   to provide group membership tracking and report processing.</td><td> </td><td class="right">   to provide group membership tracking and report processing.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay accessible via IPv4 MUST support IPv4/IGMPv3 and MAY support</td><td> </td><td class="right">   A relay accessible via IPv4 MUST support IPv4/IGMPv3 and MAY support</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IPv6/MLDv2.  A relay accessible via IPv6 MUST support IPv6/MLDv2 and</td><td> </td><td class="right">   IPv6/MLDv2.  A relay accessible via IPv6 MUST support IPv6/MLDv2 and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   MAY support IPv4/IGMPv3.</td><td> </td><td class="right">   MAY support IPv4/IGMPv3.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay MUST apply the forwarding rules described in Section 6.3 of</td><td> </td><td class="right">   A relay MUST apply the forwarding rules described in Section 6.3 of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3376] and Section 7.3 of [RFC3810].</td><td> </td><td class="right">   [RFC3376] and Section 7.3 of [RFC3810].</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0037"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   A relay MUST handle incoming reports as described <span class="delete">,</span>Section 6.4 of</td><td> </td><td class="rblock">   A relay MUST handle incoming reports as described <span class="insert">in </span>Section 6.4 of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3376] and Section 7.4 of [RFC3810] with the exception that</td><td> </td><td class="right">   [RFC3376] and Section 7.4 of [RFC3810] with the exception that</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   actions that lead to queries MAY be modified to eliminate query</td><td> </td><td class="right">   actions that lead to queries MAY be modified to eliminate query</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   generation.  A relay MUST accept IGMP and MLD report datagrams</td><td> </td><td class="right">   generation.  A relay MUST accept IGMP and MLD report datagrams</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   regardless of the IP source address carried by those datagrams.</td><td> </td><td class="right">   regardless of the IP source address carried by those datagrams.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   All other aspects of IGMP/MLD router behavior, such as the handling</td><td> </td><td class="right">   All other aspects of IGMP/MLD router behavior, such as the handling</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of queries, querier election, etc., are not used or required for</td><td> </td><td class="right">   of queries, querier election, etc., are not used or required for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   relay operation.</td><td> </td><td class="right">   relay operation.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.3.2.  Startup</td><td> </td><td class="right">5.3.2.  Startup</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l28"><small>skipping to change at</small><em> page 63, line 16</em></a></th><th> </th><th><a name="part-r28"><small>skipping to change at</small><em> page 64, line 21</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   When a relay receives a Relay Discovery message it responds by</td><td> </td><td class="right">   When a relay receives a Relay Discovery message it responds by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   sending a Relay Advertisement message back to the source of the Relay</td><td> </td><td class="right">   sending a Relay Advertisement message back to the source of the Relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Discovery message.  The relay MUST use the source IP address and UDP</td><td> </td><td class="right">   Discovery message.  The relay MUST use the source IP address and UDP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   port of the Relay Discovery message as the destination IP address and</td><td> </td><td class="right">   port of the Relay Discovery message as the destination IP address and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   UDP port.  The relay MUST use the destination IP address and UDP port</td><td> </td><td class="right">   UDP port.  The relay MUST use the destination IP address and UDP port</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the Relay Discovery as the source IP address and UDP port to</td><td> </td><td class="right">   of the Relay Discovery as the source IP address and UDP port to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   ensure successful NAT traversal.</td><td> </td><td class="right">   ensure successful NAT traversal.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The relay MUST copy the value contained in the Discovery Nonce field</td><td> </td><td class="right">   The relay MUST copy the value contained in the Discovery Nonce field</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the Relay Discovery message into the Discovery Nonce field in the</td><td> </td><td class="right">   of the Relay Discovery message into the Discovery Nonce field in the</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0038"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">the </span>Relay Advertisement message.</td><td> </td><td class="rblock">   Relay Advertisement message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the Relay Discovery message was received as an IPv4 datagram, the</td><td> </td><td class="right">   If the Relay Discovery message was received as an IPv4 datagram, the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   relay MUST return an IPv4 address in the Relay Address field of the</td><td> </td><td class="right">   relay MUST return an IPv4 address in the Relay Address field of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Relay Advertisement message.  If the Relay Discovery message was</td><td> </td><td class="right">   Relay Advertisement message.  If the Relay Discovery message was</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0039"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   received as an IPv6 datagram, the relay <span class="delete">may</span> return an <span class="delete">IPv4 or</span> IPv6</td><td> </td><td class="rblock">   received as an IPv6 datagram, the relay <span class="insert">MUST</span> return an IPv6 address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   address in the Relay Address field.</td><td> </td><td class="rblock">   in the Relay Address field.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.3.3.3.  Handling a Request Message</td><td> </td><td class="right">5.3.3.3.  Handling a Request Message</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This section describes relay requirements related to the membership</td><td> </td><td class="right">   This section describes relay requirements related to the membership</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   query portion of the message sequence described in Section 4.2.1.2.</td><td> </td><td class="right">   query portion of the message sequence described in Section 4.2.1.2.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   When a relay receives a Request message it responds by sending a</td><td> </td><td class="right">   When a relay receives a Request message it responds by sending a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Query message back to the source of the Request message.</td><td> </td><td class="right">   Membership Query message back to the source of the Request message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The relay MUST use the source IP address and UDP port of the Request</td><td> </td><td class="right">   The relay MUST use the source IP address and UDP port of the Request</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l29"><small>skipping to change at</small><em> page 64, line 13</em></a></th><th> </th><th><a name="part-r29"><small>skipping to change at</small><em> page 65, line 17</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the P-flag in the Request message is 0, the relay MUST return an</td><td> </td><td class="right">   If the P-flag in the Request message is 0, the relay MUST return an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IPv4-encapsulated IGMPv3 general query in the Membership Query</td><td> </td><td class="right">   IPv4-encapsulated IGMPv3 general query in the Membership Query</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   message.  If the P-flag is 1, the relay MUST return an IPv6-</td><td> </td><td class="right">   message.  If the P-flag is 1, the relay MUST return an IPv6-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   encapsulated MLDv2 general query in the Membership Query message.</td><td> </td><td class="right">   encapsulated MLDv2 general query in the Membership Query message.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the relay is not accepting Membership Update messages that create</td><td> </td><td class="right">   If the relay is not accepting Membership Update messages that create</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   new tunnel endpoints due to resource limitations, it SHOULD set the</td><td> </td><td class="right">   new tunnel endpoints due to resource limitations, it SHOULD set the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   L-flag in the Membership Query message to notify the gateway of this</td><td> </td><td class="right">   L-flag in the Membership Query message to notify the gateway of this</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   state.  Support for the L-flag is OPTIONAL.  See Section 5.3.3.8.</td><td> </td><td class="right">   state.  Support for the L-flag is OPTIONAL.  See Section 5.3.3.8.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0040"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">An</span> IGMPv3 general query datagram that a relay encapsulates within a</td><td> </td><td class="rblock">   <span class="insert">The</span> IGMPv3 general query datagram that a relay encapsulates within a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Query message MUST conform to the descriptions found in</td><td> </td><td class="right">   Membership Query message MUST conform to the descriptions found in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Section 4.1 of [RFC3376].  These datagrams MUST possess the IP</td><td> </td><td class="right">   Section 4.1 of [RFC3376].  These datagrams MUST possess the IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   headers, header options and header values called for in [RFC3376],</td><td> </td><td class="right">   headers, header options and header values called for in [RFC3376],</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   with the following exception; the source IP address for an IGMP</td><td> </td><td class="right">   with the following exception; the source IP address for an IGMP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   general query datagram MAY be set to the "unspecified" address (all</td><td> </td><td class="right">   general query datagram MAY be set to the "unspecified" address (all</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   octets are zero) but SHOULD be set to an address in the address range</td><td> </td><td class="right">   octets are zero) but SHOULD be set to an address in the address range</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   specifically assigned by IANA for use in the IGMP messages sent from</td><td> </td><td class="right">   specifically assigned by IANA for use in the IGMP messages sent from</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   a relay to a gateway (i.e. 154.7.1.1 as described in Section 7).</td><td> </td><td class="right">   a relay to a gateway (i.e. 154.7.1.1 as described in Section 7).</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0041"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This exception is made because <span class="delete">any</span> address that a relay might may not</td><td> </td><td class="rblock">   This exception is made because <span class="insert">the source</span> address that a relay might</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   be a valid source address on any gateway interface.  The rationale</td><td> </td><td class="rblock">   <span class="insert">normally send</span> may not be a valid source address on any gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   for using the aforementioned source addresses is primary one of</td><td> </td><td class="rblock">   interface.  The rationale for using the aforementioned source</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   convenience - a gateway will accept an IGMP query regardless of the</td><td> </td><td class="rblock">   addresses is primary one of convenience - a gateway will accept an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   source address it carries.  See Section 5.2.1.</td><td> </td><td class="rblock">   IGMP query regardless of the source address it carries.  See</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   Section 5.2.1.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0042"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">An</span> MLDv2 general query datagram that a relay encapsulates within a</td><td> </td><td class="rblock">   <span class="insert">The</span> MLDv2 general query datagram that a relay encapsulates within a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Membership Query message MUST conform to the descriptions found in</td><td> </td><td class="right">   Membership Query message MUST conform to the descriptions found in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Section 5.1 of [RFC3810].  These datagrams MUST possess the IP</td><td> </td><td class="right">   Section 5.1 of [RFC3810].  These datagrams MUST possess the IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   headers, header options and header values called for in [RFC3810],</td><td> </td><td class="right">   headers, header options and header values called for in [RFC3810],</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   with the following exception; the source IP address for an MLD</td><td> </td><td class="right">   with the following exception; the source IP address for an MLD</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   general query datagram MAY be set to the "unspecified" address (all</td><td> </td><td class="right">   general query datagram MAY be set to the "unspecified" address (all</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   octets are zero) but SHOULD be set to an IPv6 link-local address in</td><td> </td><td class="right">   octets are zero) but SHOULD be set to an IPv6 link-local address in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the range FE80::/64.  A relay may use a dynamically-generated link-</td><td> </td><td class="right">   the range FE80::/64.  A relay may use a dynamically-generated link-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   local address or the fixed address FE80::2.  As with IGMP, a gateway</td><td> </td><td class="right">   local address or the fixed address FE80::2.  As with IGMP, a gateway</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   will accept an MLD query regardless of the source address it carries.</td><td> </td><td class="right">   will accept an MLD query regardless of the source address it carries.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   See Section 5.2.1.</td><td> </td><td class="right">   See Section 5.2.1.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l30"><small>skipping to change at</small><em> page 65, line 4</em></a></th><th> </th><th><a name="part-r30"><small>skipping to change at</small><em> page 66, line 9</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   duration to use for the membership query timer.  The QQIC field is</td><td> </td><td class="right">   duration to use for the membership query timer.  The QQIC field is</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   defined in Section 4.1.1 in [RFC3376] and Section 5.1.3 in [RFC3810].</td><td> </td><td class="right">   defined in Section 4.1.1 in [RFC3376] and Section 5.1.3 in [RFC3810].</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay MAY adjust this value to affect the rate at which the Request</td><td> </td><td class="right">   A relay MAY adjust this value to affect the rate at which the Request</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   messages are sent from a gateway.  However, a gateway is allowed to</td><td> </td><td class="right">   messages are sent from a gateway.  However, a gateway is allowed to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   use a shorter duration than specified in the QQIC field, so a relay</td><td> </td><td class="right">   use a shorter duration than specified in the QQIC field, so a relay</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   may be limited in its ability to spread out Requests coming from a</td><td> </td><td class="right">   may be limited in its ability to spread out Requests coming from a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateway.</td><td> </td><td class="right">   gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay MUST set the Querier's Robustness Variable (QRV) field in the</td><td> </td><td class="right">   A relay MUST set the Querier's Robustness Variable (QRV) field in the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   general query to a non-zero value.  This value SHOULD be greater than</td><td> </td><td class="right">   general query to a non-zero value.  This value SHOULD be greater than</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0043"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   one.  If a gateway retransmits <span class="delete">a </span>membership state change messages, it</td><td> </td><td class="rblock">   one.  If a gateway retransmits membership state change messages, it</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   will retransmit them (robustness variable - 1) times.</td><td> </td><td class="right">   will retransmit them (robustness variable - 1) times.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay SHOULD set the Max Resp Code field in the general query to a</td><td> </td><td class="right">   A relay SHOULD set the Max Resp Code field in the general query to a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   value of 1 to trigger an immediate response from the gateway (some</td><td> </td><td class="right">   value of 1 to trigger an immediate response from the gateway (some</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   host IGMP/MLD implementations may not accept a value of zero).  A</td><td> </td><td class="right">   host IGMP/MLD implementations may not accept a value of zero).  A</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   relay SHOULD NOT use the IGMPv2/MLDv2 Query Response Interval</td><td> </td><td class="right">   relay SHOULD NOT use the IGMPv2/MLDv2 Query Response Interval</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   variable, if available, to generate the Max Resp Code field value as</td><td> </td><td class="right">   variable, if available, to generate the Max Resp Code field value as</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the Query Response Interval variable is used in setting the duration</td><td> </td><td class="right">   the Query Response Interval variable is used in setting the duration</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of group state timers and must not be set to such a small value.  See</td><td> </td><td class="right">   of group state timers and must not be set to such a small value.  See</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Section 5.3.3.7.</td><td> </td><td class="right">   Section 5.3.3.7.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l31"><small>skipping to change at</small><em> page 67, line 30</em></a></th><th> </th><th><a name="part-r31"><small>skipping to change at</small><em> page 68, line 36</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   number of endpoints, or a limit on the total number of endpoints for</td><td> </td><td class="right">   number of endpoints, or a limit on the total number of endpoints for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   a given source address, then the relay MAY ignore the Membership</td><td> </td><td class="right">   a given source address, then the relay MAY ignore the Membership</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Update message and possibly withdraw any Relay Discovery Address</td><td> </td><td class="right">   Update message and possibly withdraw any Relay Discovery Address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Prefix announcement that it might have made.  See Section 5.3.3.8.</td><td> </td><td class="right">   Prefix announcement that it might have made.  See Section 5.3.3.8.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay MUST maintain some form of group membership database for each</td><td> </td><td class="right">   A relay MUST maintain some form of group membership database for each</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   endpoint.  The per-endpoint databases are used update a forwarding</td><td> </td><td class="right">   endpoint.  The per-endpoint databases are used update a forwarding</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   table containing entries that map an (*,G) or (S,G) subscription to a</td><td> </td><td class="right">   table containing entries that map an (*,G) or (S,G) subscription to a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   list of tunnel endpoints.</td><td> </td><td class="right">   list of tunnel endpoints.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0044"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   A relay MUST maintain some form group membership database</td><td> </td><td class="rblock">   A relay MUST maintain some form <span class="insert">of </span>group membership database</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   representing a merger of the group membership databases of all</td><td> </td><td class="right">   representing a merger of the group membership databases of all</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   endpoints.  The merged group membership database is used to update</td><td> </td><td class="right">   endpoints.  The merged group membership database is used to update</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   upstream multicast forwarding state.</td><td> </td><td class="right">   upstream multicast forwarding state.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A relay MUST maintain a forwarding table that maps each unique (*,G)</td><td> </td><td class="right">   A relay MUST maintain a forwarding table that maps each unique (*,G)</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and (S,G) subscription to a list of tunnel endpoints.  A relay uses</td><td> </td><td class="right">   and (S,G) subscription to a list of tunnel endpoints.  A relay uses</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   this forwarding table to provide the destination address when</td><td> </td><td class="right">   this forwarding table to provide the destination address when</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   performing UDP/IP encapsulation of the incoming multicast IP</td><td> </td><td class="right">   performing UDP/IP encapsulation of the incoming multicast IP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   datagrams to form Multicast Data messages.</td><td> </td><td class="right">   datagrams to form Multicast Data messages.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l32"><small>skipping to change at</small><em> page 68, line 45</em></a></th><th> </th><th><a name="part-r32"><small>skipping to change at</small><em> page 69, line 51</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   state and possibly send prune/leave messages towards upstream</td><td> </td><td class="right">   state and possibly send prune/leave messages towards upstream</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   routers.</td><td> </td><td class="right">   routers.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.3.3.6.  Handling Multicast IP Datagrams</td><td> </td><td class="right">5.3.3.6.  Handling Multicast IP Datagrams</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   When a multicast IP datagram is forwarded to the relay pseudo-</td><td> </td><td class="right">   When a multicast IP datagram is forwarded to the relay pseudo-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interface, the relay MUST, for each gateway that has expressed an</td><td> </td><td class="right">   interface, the relay MUST, for each gateway that has expressed an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interest in receiving the datagram, encapsulate the IP datagram into</td><td> </td><td class="right">   interest in receiving the datagram, encapsulate the IP datagram into</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   a Multicast Data message and send that message to the gateway.  This</td><td> </td><td class="right">   a Multicast Data message and send that message to the gateway.  This</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   process is highly implementation dependent, but conceptually requires</td><td> </td><td class="right">   process is highly implementation dependent, but conceptually requires</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0045"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   the follow steps:</td><td> </td><td class="rblock">   the follow<span class="insert">ing</span> steps:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Use the IP datagram source and destination address to look up the</td><td> </td><td class="right">   o  Use the IP datagram source and destination address to look up the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      appropriate (*,G) or (S,G) entry in the endpoint forwarding table</td><td> </td><td class="right">      appropriate (*,G) or (S,G) entry in the endpoint forwarding table</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      created for the pseudo-interface as a result of IGMP/MLD</td><td> </td><td class="right">      created for the pseudo-interface as a result of IGMP/MLD</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      processing.</td><td> </td><td class="right">      processing.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Possibly replicate the datagram for each gateway endpoint listed</td><td> </td><td class="right">   o  Possibly replicate the datagram for each gateway endpoint listed</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      for that (*,G) or (S,G) entry.</td><td> </td><td class="right">      for that (*,G) or (S,G) entry.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Encapsulate the IP datagram in a UDP/IP Membership Data message,</td><td> </td><td class="right">   o  Encapsulate the IP datagram in a UDP/IP Membership Data message,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l33"><small>skipping to change at</small><em> page 70, line 26</em></a></th><th> </th><th><a name="part-r33"><small>skipping to change at</small><em> page 71, line 31</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   SHOULD set the L-flag in any Membership Query messages it returns to</td><td> </td><td class="right">   SHOULD set the L-flag in any Membership Query messages it returns to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gateways while in this state.</td><td> </td><td class="right">   gateways while in this state.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the relay receives an update from a gateway that adds group</td><td> </td><td class="right">   If the relay receives an update from a gateway that adds group</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   membership or forwarding state for an endpoint that has already</td><td> </td><td class="right">   membership or forwarding state for an endpoint that has already</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   reached maximum allowable state entries, the relay SHOULD continue to</td><td> </td><td class="right">   reached maximum allowable state entries, the relay SHOULD continue to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   accept updates from the gateway but ignore any group membership/</td><td> </td><td class="right">   accept updates from the gateway but ignore any group membership/</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   forwarding state additions requested by that gateway.</td><td> </td><td class="right">   forwarding state additions requested by that gateway.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If the relay receives an update from a gateway that would create a</td><td> </td><td class="right">   If the relay receives an update from a gateway that would create a</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0046"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   new tunnel endpoint for a source IP address that has already <span class="delete">reach</span></td><td> </td><td class="rblock">   new tunnel endpoint for a source IP address that has already <span class="insert">reached</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   maximum allowable number of endpoints (maximum UDP ports), it should</td><td> </td><td class="rblock"><span class="insert">   the</span> maximum allowable number of endpoints (maximum UDP ports), it</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   simply ignore the Membership Update.</td><td> </td><td class="rblock">   should simply ignore the Membership Update.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.3.4.  Shutdown</td><td> </td><td class="right">5.3.4.  Shutdown</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The following steps should be treated as an abstract description of</td><td> </td><td class="right">   The following steps should be treated as an abstract description of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the shutdown procedure for a relay:</td><td> </td><td class="right">   the shutdown procedure for a relay:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Withdraw the Relay Discovery Address Prefix advertisement (if</td><td> </td><td class="right">   o  Withdraw the Relay Discovery Address Prefix advertisement (if</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      used).</td><td> </td><td class="right">      used).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Stop listening for Relay Discovery messages.</td><td> </td><td class="right">   o  Stop listening for Relay Discovery messages.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray"><td></td><th><a name="part-l34"><small>skipping to change at</small><em> page 75, line 19</em></a></th><th> </th><th><a name="part-r34"><small>skipping to change at</small><em> page 76, line 19</em></a></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IANA should allocate an IPv4 prefix and an IPv6 prefix dedicated to</td><td> </td><td class="right">   IANA should allocate an IPv4 prefix and an IPv6 prefix dedicated to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the public AMT Relays to advertise to the native multicast backbone</td><td> </td><td class="right">   the public AMT Relays to advertise to the native multicast backbone</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (as described in Section 4.1.4).  The prefix length should be</td><td> </td><td class="right">   (as described in Section 4.1.4).  The prefix length should be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   determined by the IANA; the prefix should be large enough to</td><td> </td><td class="right">   determined by the IANA; the prefix should be large enough to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   guarantee advertisement in the default-free BGP networks.</td><td> </td><td class="right">   guarantee advertisement in the default-free BGP networks.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">7.1.1.  IPv4</td><td> </td><td class="right">7.1.1.  IPv4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A prefix length of 24 will meet this requirement.</td><td> </td><td class="right">   A prefix length of 24 will meet this requirement.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0047"></a></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Internet Systems Consortium (ISC) has offered154.7.0/24 for this</td><td> </td><td class="rblock">   Internet Systems Consortium (ISC) has offered<span class="insert"> </span>154.7.0/24 for this</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   purpose.</td><td> </td><td class="right">   purpose.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">7.1.2.  IPv6</td><td> </td><td class="right">7.1.2.  IPv6</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   A prefix length of 32 will meet this requirement.  IANA has</td><td> </td><td class="right">   A prefix length of 32 will meet this requirement.  IANA has</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   previously set aside the range 2001::/16 for allocating prefixes for</td><td> </td><td class="right">   previously set aside the range 2001::/16 for allocating prefixes for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   this purpose.</td><td> </td><td class="right">   this purpose.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">7.2.  IPv4 Address Prefix Allocation for IGMP Source Addresses</td><td> </td><td class="right">7.2.  IPv4 Address Prefix Allocation for IGMP Source Addresses</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 47 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>93 lines changed or deleted</i></th><th><i> </i></th><th><i>104 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br>This html diff was produced by rfcdiff 1.41. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/">http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
   </tbody></table>
   
   
</body></html>
--Apple-Mail-25--29412545
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



On Jun 6, 2012, at 6:07 PM, Tom Taylor wrote:

> In 5.1.5, still have "Message Update message" rather than "Membership =
Update message".
>=20
I must have skipped over that one when I was going through the e-mails.

> In 5.2.1, you did primary -> primarly -- still missing the 'i'.
>=20
> In 5.3.1, you got rid of the comma before "Section", but didn't add =
the "in" in front of it.
>=20
> 5.3.3.4, third-last para: missing "of" between "form" and "group".
>=20
I definitely remember fixing this, now see that this mistake was =
repeated in the adjacent paragraph.

> Still wondering why you have "Static" in the section titles of 5.2.2.1 =
and 5.2.2.2.
>=20
I removed "Static" from the section titles (though it is still used =
within the section text).=20

> On 06/06/2012 8:22 PM, Greg Bumgardner wrote:
>> All,
>>=20
>> I have made changes to the draft based on WGLC comments. I would like =
those of you who responded to take a look at the attached diff to see if =
the changes are satisfactory. I would like to publish draft #14 in the =
next day or so.
>>=20
>> Thanks,
>>=20
>> -g.b.
>>=20
>>=20
>>=20
>>=20
>>=20
>> On May 10, 2012, at 10:33 AM, Greg Shepherd wrote:
>>=20
>>> *,
>>>=20
>>> Yes, I think we may finally be here! The Paris and post-Paris
>>> discussions were addressed in the finally rev so it is now time for
>>> WGLC for draft-ietf-mboned-auto-multicast-13:
>>>=20
>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/
>>>=20
>>> It is quite long so we'll give it three weeks for responses before
>>> moving it along. Please respond by May 31st. And as always, we need
>>> votes of approval as much as comments and issues. Let's see this
>>> finally move to req pub!
>>>=20
>>> Thanks to everyone who has been involved throughout the past =
+decade. :p
>>>=20
>>> MBONED Chairs
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>>=20


--Apple-Mail-25--29412545--

From marshall.eubanks@gmail.com  Thu Jun  7 10:30:44 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F22311E812F for <mboned@ietfa.amsl.com>; Thu,  7 Jun 2012 10:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.492
X-Spam-Level: 
X-Spam-Status: No, score=-103.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 Uu0DH27tejlE for <mboned@ietfa.amsl.com>; Thu,  7 Jun 2012 10:30:43 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8AFE811E812C for <mboned@ietf.org>; Thu,  7 Jun 2012 10:30:23 -0700 (PDT)
Received: by lagv3 with SMTP id v3so765343lag.31 for <mboned@ietf.org>; Thu, 07 Jun 2012 10:30:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/KkK/j1aA8SqD/9zjcj5VqhnOt7ASFj4sM4uCHMN5Zw=; b=KCKP3MaoAcApqT2wY4O8d32xTN56T4iIIlcJO/s+lsQYZQXKrF/TBmbmTislkUPEF8 9h6+i6zUkq1tM05kPal19OiBCz7nEF34KMgKYum+bsqDQ9o3Gff2OMNlwiTYxrfdJhhN QEsYfNKZlPS6tEmEZ4lIWMpVYNB7zPKVA8ezVhqtP/1ePM4GgJ3eKUiHpgTnbxwkJghF x2Jr6A8BbH+SJIfRDHCYBl7mf4hYXeQoVKZpzL2Qiu2uy1u2HG4mOaLHlLhGiRiT2Nyv +waLYLlA4kmwrK9PTm735HzgiNXZ4zwjoC0tbTJtGLZhlOUewLKL1l+qGnD3oUQcc3mN uKyQ==
MIME-Version: 1.0
Received: by 10.112.98.225 with SMTP id el1mr1810275lbb.30.1339090222519; Thu, 07 Jun 2012 10:30:22 -0700 (PDT)
Received: by 10.112.132.65 with HTTP; Thu, 7 Jun 2012 10:30:22 -0700 (PDT)
In-Reply-To: <CBE85C8C.2063B%cuiyong@tsinghua.edu.cn>
References: <CBE85C8C.2063B%cuiyong@tsinghua.edu.cn>
Date: Thu, 7 Jun 2012 13:30:22 -0400
Message-ID: <CAJNg7V+7LySZ-MVw7oFjmzOzqv1-+0ES_b7JKmmD9gsnxAHvTw@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: mboned@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [MBONED] Fwd: [Softwires] WG last call on draft-ietf-softwire-dslite-multicast-02
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 17:30:44 -0000

Sorry for being so late on this, but it occurred to me that this
should be at least posted here, if not last called here.

Regards
Marshall


---------- Forwarded message ----------
From: Yong Cui <cuiyong@tsinghua.edu.cn>
Date: Sun, May 27, 2012 at 10:34 AM
Subject: [Softwires] WG last call on draft-ietf-softwire-dslite-multicast-02
To: softwires@ietf.org
Cc: Yong Cui <cuiyong@tsinghua.edu.cn>


Hi folks,

This is a wg last call on draft-ietf-softwire-dslite-multicast-02.
http://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/

As usual, please send editorial comments to the authors and
substantive comments to the mailing list.

This wg last call will end on June 10 at 12pm EDT.


Yong & Alain



_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

From lenny@juniper.net  Thu Jun  7 13:38:24 2012
Return-Path: <lenny@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A66A511E8149 for <mboned@ietfa.amsl.com>; Thu,  7 Jun 2012 13:38:24 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yAOxenWJLP6W for <mboned@ietfa.amsl.com>; Thu,  7 Jun 2012 13:38:24 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 0569D11E80AA for <mboned@ietf.org>; Thu,  7 Jun 2012 13:38:23 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKT9ERPmyNV3vKzh7QsXexAGZd/S8X5a/C@postini.com; Thu, 07 Jun 2012 13:38:24 PDT
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB01-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 7 Jun 2012 13:34:50 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id q57KYo101727; Thu, 7 Jun 2012 13:34:50 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 20D241145A;  Thu,  7 Jun 2012 13:34:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 14F6911446; Thu,  7 Jun 2012 13:34:50 -0700 (PDT)
Date: Thu, 7 Jun 2012 13:34:50 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
Message-ID: <20120607132832.I69151@eng-mail01.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Cc: Ronald Bonica <rbonica@juniper.net>
Subject: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 20:38:24 -0000

The multicast transition work within MBONED was initially intended to 
consist of ~ 3 document with limited scope.  In a very short amount of 
time, we've seen 7 drafts (and counting) with scope widening.

In order to make sure we are focusing on work that is of actual value to 
the community and prevent a flood of high volume/low value drafts, we 
would like to revisit the basic questions of multicast transition within 
MBONED.  We would like to hear answers from the WG to the following 
questions before continuing any work on multicast transition in MBONED:

1) Which operators intend to source multicast traffic from one IP version 
and receive it over another IP version?

2) For those who answer 1), please identify the use-cases of interest in 
draft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions 
for those use cases.


MBONED Chairs

From albert.e.manfredi@boeing.com  Thu Jun  7 14:46:48 2012
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18BD921F8523 for <mboned@ietfa.amsl.com>; Thu,  7 Jun 2012 14:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level: 
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.373,  BAYES_00=-2.599]
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 z7QNJbtzvDbq for <mboned@ietfa.amsl.com>; Thu,  7 Jun 2012 14:46:47 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 8487F11E8156 for <mboned@ietf.org>; Thu,  7 Jun 2012 14:46:47 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q57LkkYH001703 for <mboned@ietf.org>; Thu, 7 Jun 2012 14:46:46 -0700
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.128.218]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q57LkkEN001700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 7 Jun 2012 14:46:46 -0700
Received: from slb-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q57Lkjgt000845; Thu, 7 Jun 2012 14:46:45 -0700
Received: from XCH-MWHT-01.mw.nos.boeing.com (xch-mwht-01.mw.nos.boeing.com [134.57.113.35]) by slb-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q57LkjwA000832 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 7 Jun 2012 14:46:45 -0700
Received: from XCH-MWHT-07.mw.nos.boeing.com (134.57.118.77) by XCH-MWHT-01.mw.nos.boeing.com (134.57.113.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 7 Jun 2012 16:46:44 -0500
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.118.180]) by XCH-MWHT-07.mw.nos.boeing.com ([134.57.118.77]) with mapi; Thu, 7 Jun 2012 16:46:44 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Leonard Giuliano <lenny@juniper.net>, MBONED WG <mboned@ietf.org>
Date: Thu, 7 Jun 2012 16:46:43 -0500
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: Ac1E7X8remnAyDlvQ3+5sYCZz/YZ/wACPh2Q
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com>
References: <20120607132832.I69151@eng-mail01.juniper.net>
In-Reply-To: <20120607132832.I69151@eng-mail01.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
Cc: Ronald Bonica <rbonica@juniper.net>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 21:46:48 -0000

Hi guys,

1. For our shipboard networks, which are dual-stack, we intend to allow for=
 IPv4 multicast sources to feed IPv6 clients, and vice versa. The networks =
are dual stack throughout, but the end systems are not likely to be. My pre=
ference is to send both v4 and v6 multicasts through the network, doing the=
 conversion (if necessary) at the edge router connecting to the source.

2. Use cases 3.4 and 3.5.

Thanks!

Bert

-----Original Message-----
From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of=
 Leonard Giuliano
Sent: Thursday, June 07, 2012 4:35 PM
To: MBONED WG
Cc: Ronald Bonica
Subject: [MBONED] Multicast transition work in MBONED


The multicast transition work within MBONED was initially intended to=20
consist of ~ 3 document with limited scope.  In a very short amount of=20
time, we've seen 7 drafts (and counting) with scope widening.

In order to make sure we are focusing on work that is of actual value to=20
the community and prevent a flood of high volume/low value drafts, we=20
would like to revisit the basic questions of multicast transition within=20
MBONED.  We would like to hear answers from the WG to the following=20
questions before continuing any work on multicast transition in MBONED:

1) Which operators intend to source multicast traffic from one IP version=20
and receive it over another IP version?

2) For those who answer 1), please identify the use-cases of interest in=20
draft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions=20
for those use cases.


MBONED Chairs
_______________________________________________
MBONED mailing list
MBONED@ietf.org
https://www.ietf.org/mailman/listinfo/mboned

From cathy.zhou@huawei.com  Fri Jun  8 00:50:33 2012
Return-Path: <cathy.zhou@huawei.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3533921F88A6 for <mboned@ietfa.amsl.com>; Fri,  8 Jun 2012 00:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.788
X-Spam-Level: **
X-Spam-Status: No, score=2.788 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
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 VVoiqPjRxgj5 for <mboned@ietfa.amsl.com>; Fri,  8 Jun 2012 00:50:30 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0614421F88A3 for <mboned@ietf.org>; Fri,  8 Jun 2012 00:50:26 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGR91535; Fri, 08 Jun 2012 03:50:26 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 8 Jun 2012 00:47:03 -0700
Received: from SZXEML436-HUB.china.huawei.com (10.72.61.64) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 8 Jun 2012 00:47:01 -0700
Received: from SZXEML527-MBX.china.huawei.com ([169.254.3.174]) by szxeml436-hub.china.huawei.com ([10.72.61.64]) with mapi id 14.01.0323.003; Fri, 8 Jun 2012 15:46:58 +0800
From: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Leonard Giuliano <lenny@juniper.net>, MBONED WG <mboned@ietf.org>
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: AQHNRO2JTFaUoVGNgku32+SK5nx9j5bu3haAgAEsiTA=
Date: Fri, 8 Jun 2012 07:46:57 +0000
Message-ID: <A6A061BEE5DDC94A9692D9D81AF776DF2D4400C8@szxeml527-mbx.china.huawei.com>
References: <20120607132832.I69151@eng-mail01.juniper.net> <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.77.118]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Ronald Bonica <rbonica@juniper.net>
Subject: [MBONED] =?gb2312?b?tPC4tDogIE11bHRpY2FzdCB0cmFuc2l0aW9uIHdvcmsg?= =?gb2312?b?aW4gTUJPTkVE?=
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 07:50:33 -0000

SGkgQmVydCwNCkZvciB0aGUgZmlyc3QgY2FzZSwgcGxlYXNlIHJlZmVyIHRvIG15IGRyYWZ0Og0K
aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtemhvdS1tYm9uZWQtbXVsdHJhbnMtcGF0
aC1vcHRpbWl6YXRpb24tMDENCllvdXIgY29tbWVudHMgYXJlIHdlbGNvbWUuDQoNCkJlc3QgUmVn
YXJkcywNCkNhdGh5DQotLS0tLdPKvP7Urbz+LS0tLS0NCreivP7IyzogbWJvbmVkLWJvdW5jZXNA
aWV0Zi5vcmcgW21haWx0bzptYm9uZWQtYm91bmNlc0BpZXRmLm9yZ10gtPqx7SBNYW5mcmVkaSwg
QWxiZXJ0IEUNCreiy83KsbzkOiAyMDEyxOo21MI4yNUgNTo0Nw0KytW8/sjLOiBMZW9uYXJkIEdp
dWxpYW5vOyBNQk9ORUQgV0cNCrOty806IFJvbmFsZCBCb25pY2ENCtb3zOI6IFJlOiBbTUJPTkVE
XSBNdWx0aWNhc3QgdHJhbnNpdGlvbiB3b3JrIGluIE1CT05FRA0KDQpIaSBndXlzLA0KDQoxLiBG
b3Igb3VyIHNoaXBib2FyZCBuZXR3b3Jrcywgd2hpY2ggYXJlIGR1YWwtc3RhY2ssIHdlIGludGVu
ZCB0byBhbGxvdyBmb3IgSVB2NCBtdWx0aWNhc3Qgc291cmNlcyB0byBmZWVkIElQdjYgY2xpZW50
cywgYW5kIHZpY2UgdmVyc2EuIFRoZSBuZXR3b3JrcyBhcmUgZHVhbCBzdGFjayB0aHJvdWdob3V0
LCBidXQgdGhlIGVuZCBzeXN0ZW1zIGFyZSBub3QgbGlrZWx5IHRvIGJlLiBNeSBwcmVmZXJlbmNl
IGlzIHRvIHNlbmQgYm90aCB2NCBhbmQgdjYgbXVsdGljYXN0cyB0aHJvdWdoIHRoZSBuZXR3b3Jr
LCBkb2luZyB0aGUgY29udmVyc2lvbiAoaWYgbmVjZXNzYXJ5KSBhdCB0aGUgZWRnZSByb3V0ZXIg
Y29ubmVjdGluZyB0byB0aGUgc291cmNlLg0KDQoyLiBVc2UgY2FzZXMgMy40IGFuZCAzLjUuDQoN
ClRoYW5rcyENCg0KQmVydA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogbWJv
bmVkLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzptYm9uZWQtYm91bmNlc0BpZXRmLm9yZ10gT24g
QmVoYWxmIE9mIExlb25hcmQgR2l1bGlhbm8NClNlbnQ6IFRodXJzZGF5LCBKdW5lIDA3LCAyMDEy
IDQ6MzUgUE0NClRvOiBNQk9ORUQgV0cNCkNjOiBSb25hbGQgQm9uaWNhDQpTdWJqZWN0OiBbTUJP
TkVEXSBNdWx0aWNhc3QgdHJhbnNpdGlvbiB3b3JrIGluIE1CT05FRA0KDQoNClRoZSBtdWx0aWNh
c3QgdHJhbnNpdGlvbiB3b3JrIHdpdGhpbiBNQk9ORUQgd2FzIGluaXRpYWxseSBpbnRlbmRlZCB0
byANCmNvbnNpc3Qgb2YgfiAzIGRvY3VtZW50IHdpdGggbGltaXRlZCBzY29wZS4gIEluIGEgdmVy
eSBzaG9ydCBhbW91bnQgb2YgDQp0aW1lLCB3ZSd2ZSBzZWVuIDcgZHJhZnRzIChhbmQgY291bnRp
bmcpIHdpdGggc2NvcGUgd2lkZW5pbmcuDQoNCkluIG9yZGVyIHRvIG1ha2Ugc3VyZSB3ZSBhcmUg
Zm9jdXNpbmcgb24gd29yayB0aGF0IGlzIG9mIGFjdHVhbCB2YWx1ZSB0byANCnRoZSBjb21tdW5p
dHkgYW5kIHByZXZlbnQgYSBmbG9vZCBvZiBoaWdoIHZvbHVtZS9sb3cgdmFsdWUgZHJhZnRzLCB3
ZSANCndvdWxkIGxpa2UgdG8gcmV2aXNpdCB0aGUgYmFzaWMgcXVlc3Rpb25zIG9mIG11bHRpY2Fz
dCB0cmFuc2l0aW9uIHdpdGhpbiANCk1CT05FRC4gIFdlIHdvdWxkIGxpa2UgdG8gaGVhciBhbnN3
ZXJzIGZyb20gdGhlIFdHIHRvIHRoZSBmb2xsb3dpbmcgDQpxdWVzdGlvbnMgYmVmb3JlIGNvbnRp
bnVpbmcgYW55IHdvcmsgb24gbXVsdGljYXN0IHRyYW5zaXRpb24gaW4gTUJPTkVEOg0KDQoxKSBX
aGljaCBvcGVyYXRvcnMgaW50ZW5kIHRvIHNvdXJjZSBtdWx0aWNhc3QgdHJhZmZpYyBmcm9tIG9u
ZSBJUCB2ZXJzaW9uIA0KYW5kIHJlY2VpdmUgaXQgb3ZlciBhbm90aGVyIElQIHZlcnNpb24/DQoN
CjIpIEZvciB0aG9zZSB3aG8gYW5zd2VyIDEpLCBwbGVhc2UgaWRlbnRpZnkgdGhlIHVzZS1jYXNl
cyBvZiBpbnRlcmVzdCBpbiANCmRyYWZ0LWlldGYtbWJvbmVkLXY0djYtbWNhc3QtcHMgc28gd2Ug
Y2FuIGxpbWl0IGRpc2N1c3Npb24gdG8gc29sdXRpb25zIA0KZm9yIHRob3NlIHVzZSBjYXNlcy4N
Cg0KDQpNQk9ORUQgQ2hhaXJzDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KTUJPTkVEIG1haWxpbmcgbGlzdA0KTUJPTkVEQGlldGYub3JnDQpodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21ib25lZA0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCk1CT05FRCBtYWlsaW5nIGxpc3QNCk1CT05F
REBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tYm9uZWQN
Cg==

From simon.perreault@viagenie.ca  Fri Jun  8 05:39:21 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA5721F8904 for <mboned@ietfa.amsl.com>; Fri,  8 Jun 2012 05:39:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599, NO_RELAYS=-0.001]
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 yo-LexxVyem4 for <mboned@ietfa.amsl.com>; Fri,  8 Jun 2012 05:39:20 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 9A5E321F8877 for <mboned@ietf.org>; Fri,  8 Jun 2012 05:39:20 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c064:b4da:23a8:649d:b10c]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 01F4A415D3 for <mboned@ietf.org>; Fri,  8 Jun 2012 08:39:19 -0400 (EDT)
Message-ID: <4FD1F277.8060608@viagenie.ca>
Date: Fri, 08 Jun 2012 08:39:19 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
To: mboned@ietf.org
References: <20120607132832.I69151@eng-mail01.juniper.net> <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 12:39:21 -0000

On 2012-06-07 17:46, Manfredi, Albert E wrote:
> 1. For our shipboard networks, which are dual-stack, we intend to
> allow for IPv4 multicast sources to feed IPv6 clients, and vice
> versa. The networks are dual stack throughout, but the end systems
> are not likely to be. My preference is to send both v4 and v6
> multicasts through the network, doing the conversion (if necessary)
> at the edge router connecting to the source.

Will that double the amount of multicast traffic in your network? If so, 
is it a problem?

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From sarikaya2012@gmail.com  Fri Jun  8 08:59:31 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E52321F880B for <mboned@ietfa.amsl.com>; Fri,  8 Jun 2012 08:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.43
X-Spam-Level: 
X-Spam-Status: No, score=-3.43 tagged_above=-999 required=5 tests=[AWL=0.169,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 N8jrZrSnFuX2 for <mboned@ietfa.amsl.com>; Fri,  8 Jun 2012 08:59:30 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0B31F21F87DE for <mboned@ietf.org>; Fri,  8 Jun 2012 08:59:29 -0700 (PDT)
Received: by yenq13 with SMTP id q13so1609203yen.31 for <mboned@ietf.org>; Fri, 08 Jun 2012 08:59:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=sIPUiDJ+yPudvqZS+ZlkqgxSqlzKpg2WZoV/uJqXPXs=; b=ZiJv1yS6xlNoIVABHSAYuttzkFpKZQDLv77iE+rWPNU6fXfbso8tq6E1bH/ZK3R2PB 2hcSodX8aw6ELCM14ohc/y/0H7SFKdGafMae5Sb1Hw731VfefS2f0KhLSx/IhpLtoXPv 0Sg4jkOJR3I57DFehM3/M7qoIk19KyL5SCe3O3eWNc4lZbg/ERod+XLQfm4tNKTouQww 7LcUw0vqpHAJVKEh00bE1EehUzyrxKn8Zw5zpOQG2zoMO6X5c6Uq0TX4jdTQet7G5GN3 nTt8fvRD4sDxEJuQbdqGbplmdas4LjDnXQGgnznclX7rejiPXMct19FvHCjRRlvOxc6S W0ng==
MIME-Version: 1.0
Received: by 10.50.187.135 with SMTP id fs7mr3047575igc.63.1339171169337; Fri, 08 Jun 2012 08:59:29 -0700 (PDT)
Received: by 10.231.118.210 with HTTP; Fri, 8 Jun 2012 08:59:29 -0700 (PDT)
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com>
References: <20120607132832.I69151@eng-mail01.juniper.net> <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com>
Date: Fri, 8 Jun 2012 10:59:29 -0500
Message-ID: <CAC8QAcdfOCcr9+q53SYEDW9hjzR2x8OAdKroZSqGobZnZnOLjg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: MBONED WG <mboned@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 15:59:31 -0000

If you have a dual stack network both in unicast and multicast, it is
probably not very efficient but also you have no problem as well in
serving the users in both unicast and multicast in IPv4 and IPv6.

What would be more interesting is to hear from the land operators of
fixed and mobile networks.

I would add a Question 0 to Lenny's questions:

0. Which of the v6 transition technologies (NAT64, 6rd, DS-Lite, 4rd)
have you deployed or plan on deploying? Your interest in providing
multicast to the users of these transition technologies?

Regards,

Behcet

On Thu, Jun 7, 2012 at 4:46 PM, Manfredi, Albert E
<albert.e.manfredi@boeing.com> wrote:
> Hi guys,
>
> 1. For our shipboard networks, which are dual-stack, we intend to allow f=
or IPv4 multicast sources to feed IPv6 clients, and vice versa. The network=
s are dual stack throughout, but the end systems are not likely to be. My p=
reference is to send both v4 and v6 multicasts through the network, doing t=
he conversion (if necessary) at the edge router connecting to the source.
>
> 2. Use cases 3.4 and 3.5.
>
> Thanks!
>
> Bert
>
> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf =
Of Leonard Giuliano
> Sent: Thursday, June 07, 2012 4:35 PM
> To: MBONED WG
> Cc: Ronald Bonica
> Subject: [MBONED] Multicast transition work in MBONED
>
>
> The multicast transition work within MBONED was initially intended to
> consist of ~ 3 document with limited scope. =A0In a very short amount of
> time, we've seen 7 drafts (and counting) with scope widening.
>
> In order to make sure we are focusing on work that is of actual value to
> the community and prevent a flood of high volume/low value drafts, we
> would like to revisit the basic questions of multicast transition within
> MBONED. =A0We would like to hear answers from the WG to the following
> questions before continuing any work on multicast transition in MBONED:
>
> 1) Which operators intend to source multicast traffic from one IP version
> and receive it over another IP version?
>
> 2) For those who answer 1), please identify the use-cases of interest in
> draft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions
> for those use cases.
>
>
> MBONED Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From stig@venaas.com  Fri Jun  8 11:54:48 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36DFA11E80F1 for <mboned@ietfa.amsl.com>; Fri,  8 Jun 2012 11:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 P07ipJzRWQGO for <mboned@ietfa.amsl.com>; Fri,  8 Jun 2012 11:54:47 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 9633821F86B7 for <mboned@ietf.org>; Fri,  8 Jun 2012 11:54:47 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 5085D8042; Fri,  8 Jun 2012 20:54:46 +0200 (CEST)
Message-ID: <4FD24A73.6010402@venaas.com>
Date: Fri, 08 Jun 2012 11:54:43 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Marshall Eubanks <marshall.eubanks@gmail.com>
References: <CBE85C8C.2063B%cuiyong@tsinghua.edu.cn> <CAJNg7V+7LySZ-MVw7oFjmzOzqv1-+0ES_b7JKmmD9gsnxAHvTw@mail.gmail.com>
In-Reply-To: <CAJNg7V+7LySZ-MVw7oFjmzOzqv1-+0ES_b7JKmmD9gsnxAHvTw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mboned@ietf.org
Subject: Re: [MBONED] Fwd: [Softwires] WG last call on draft-ietf-softwire-dslite-multicast-02
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 18:54:48 -0000

On 6/7/2012 10:30 AM, Marshall Eubanks wrote:
> Sorry for being so late on this, but it occurred to me that this
> should be at least posted here, if not last called here.

The draft seems to specify an entirely generic solution for tunneling
IPv4 multicast through an IPv6 multicast network. There is nothing
directly related to dslite in the draft, except that the solution is
also useful for dslite deployments.

Since this is a generic solution, I think it should be reviewed by
people in mboned. So please have a look. It should maybe also go
through WGLC here. It does also discuss translation, so it relates
directly to topics we're discussing in mboned.

Stig

>
> Regards
> Marshall
>
>
> ---------- Forwarded message ----------
> From: Yong Cui<cuiyong@tsinghua.edu.cn>
> Date: Sun, May 27, 2012 at 10:34 AM
> Subject: [Softwires] WG last call on draft-ietf-softwire-dslite-multicast-02
> To: softwires@ietf.org
> Cc: Yong Cui<cuiyong@tsinghua.edu.cn>
>
>
> Hi folks,
>
> This is a wg last call on draft-ietf-softwire-dslite-multicast-02.
> http://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/
>
> As usual, please send editorial comments to the authors and
> substantive comments to the mailing list.
>
> This wg last call will end on June 10 at 12pm EDT.
>
>
> Yong&  Alain
>
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From albert.e.manfredi@boeing.com  Fri Jun  8 12:27:08 2012
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A20E511E80D1 for <mboned@ietfa.amsl.com>; Fri,  8 Jun 2012 12:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599]
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 ABYPhNJ8vIFz for <mboned@ietfa.amsl.com>; Fri,  8 Jun 2012 12:27:08 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id 2ABBC21F8875 for <mboned@ietf.org>; Fri,  8 Jun 2012 12:26:55 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q58JQhWR027773 for <mboned@ietf.org>; Fri, 8 Jun 2012 14:26:43 -0500
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.16.37]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q58JQg8u027739 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 8 Jun 2012 14:26:43 -0500
Received: from blv-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q58JQrYW032618; Fri, 8 Jun 2012 12:26:53 -0700
Received: from XCH-MWHT-02.mw.nos.boeing.com (xch-mwht-02.mw.nos.boeing.com [134.57.113.20]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q58JQrZa032592 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 8 Jun 2012 12:26:53 -0700
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.118.180]) by XCH-MWHT-02.mw.nos.boeing.com ([134.57.113.20]) with mapi; Fri, 8 Jun 2012 14:26:52 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Simon Perreault <simon.perreault@viagenie.ca>, "mboned@ietf.org" <mboned@ietf.org>
Date: Fri, 8 Jun 2012 14:26:52 -0500
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: Ac1Fc74gaobW/tEJS+iVikfF2x80aQAN1H8A
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02BC38DC1C@XCH-MW-08V.mw.nos.boeing.com>
References: <20120607132832.I69151@eng-mail01.juniper.net> <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com> <4FD1F277.8060608@viagenie.ca>
In-Reply-To: <4FD1F277.8060608@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 19:27:08 -0000

> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On
> Behalf Of Simon Perreault
> Sent: Friday, June 08, 2012 8:39 AM
> To: mboned@ietf.org
> Subject: Re: [MBONED] Multicast transition work in MBONED
>=20
> On 2012-06-07 17:46, Manfredi, Albert E wrote:
> > 1. For our shipboard networks, which are dual-stack, we intend to
> > allow for IPv4 multicast sources to feed IPv6 clients, and vice
> > versa. The networks are dual stack throughout, but the end systems
> > are not likely to be. My preference is to send both v4 and v6
> > multicasts through the network, doing the conversion (if necessary)
> > at the edge router connecting to the source.
>=20
> Will that double the amount of multicast traffic in your network? If
> so,
> is it a problem?

Yes, it could be double the bandwidth, if MLD and IGMP both indicate member=
ship. For us, that's not a problem. What it means is that the IPv6 and IPv4=
 versions will go through the network along multicast trees that are optimi=
zed for each respective IP version.

The alternative approach is to allow sources to transmit either v4 or v6 mu=
lticasts, and then to do the translation at the destination edge routers, b=
ased on whether these edge routers receive IGMP or MLD join reports. In pri=
nciple, that works too. But it's far messier. There's nothing easier than m=
essing with the source side of the multicast, the way IP multicast works. T=
he source always has the easiest job of all.

Bert


From tony@lavanauts.org  Sat Jun  9 10:53:00 2012
Return-Path: <tony@lavanauts.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5115921F87E1 for <mboned@ietfa.amsl.com>; Sat,  9 Jun 2012 10:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 pxDm1bq1N99A for <mboned@ietfa.amsl.com>; Sat,  9 Jun 2012 10:52:59 -0700 (PDT)
Received: from slimemold.creativedynamo.com (slimemold.creativedynamo.com [IPv6:2605:b00:0:2:211:2fff:fef6:4287]) by ietfa.amsl.com (Postfix) with ESMTP id EFDD921F87F1 for <mboned@ietf.org>; Sat,  9 Jun 2012 10:52:58 -0700 (PDT)
Received: from sol.manaikaika.com (sol.manaikaika.com [IPv6:2605:b00:1:0:230:1bff:fe3f:6050]) (authenticated bits=0) by slimemold.creativedynamo.com (8.13.8/8.13.8) with ESMTP id q59Hquws018709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mboned@ietf.org>; Sat, 9 Jun 2012 07:52:57 -1000
Date: Sat, 9 Jun 2012 07:51:54 -1000 (HST)
From: Antonio Querubin <tony@lavanauts.org>
X-X-Sender: tony@sol.manaikaika.com
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BC38DC1C@XCH-MW-08V.mw.nos.boeing.com>
Message-ID: <alpine.LRH.2.02.1206090747380.2910@sol.manaikaika.com>
References: <20120607132832.I69151@eng-mail01.juniper.net> <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com> <4FD1F277.8060608@viagenie.ca> <B0147C3DD45E42478038FC347CCB65FE02BC38DC1C@XCH-MW-08V.mw.nos.boeing.com>
User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
ReSent-Date: Sat, 9 Jun 2012 07:52:46 -1000 (HST)
ReSent-From: Antonio Querubin <tony@lavanauts.org>
ReSent-To: mboned@ietf.org
ReSent-Subject: Re: [MBONED] Multicast transition work in MBONED
ReSent-Message-ID: <alpine.LRH.2.02.1206090752460.2910@sol.manaikaika.com>
ReSent-User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 17:53:00 -0000

On Fri, 8 Jun 2012, Manfredi, Albert E wrote:

>> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On
>> Behalf Of Simon Perreault

>> On 2012-06-07 17:46, Manfredi, Albert E wrote:

>>> 1. For our shipboard networks, which are dual-stack, we intend to
>>> allow for IPv4 multicast sources to feed IPv6 clients, and vice
>>> versa. The networks are dual stack throughout, but the end systems
>>> are not likely to be. My preference is to send both v4 and v6
>>> multicasts through the network, doing the conversion (if necessary)
>>> at the edge router connecting to the source.
>>
>> Will that double the amount of multicast traffic in your network? If
>> so,
>> is it a problem?
>
> Yes, it could be double the bandwidth, if MLD and IGMP both indicate 
> membership. For us, that's not a problem. What it means is that the IPv6 
> and IPv4 versions will go through the network along multicast trees that 
> are optimized for each respective IP version.
>
> The alternative approach is to allow sources to transmit either v4 or v6 
> multicasts, and then to do the translation at the destination edge 
> routers, based on whether these edge routers receive IGMP or MLD join 
> reports. In principle, that works too. But it's far messier. There's 
> nothing easier than messing with the source side of the multicast, the 
> way IP multicast works. The source always has the easiest job of all.

I concur.  I had a similar problem a few years ago and went through the 
same analysis - and similar conclusion.  Either let the source stream in 
both IPv4 and IPv6 directly, or if the source isn't configurable that way, 
run a local translator directly on the source to do the translation.  Let 
the network decide which streams need replication - all the way to the 
source.

Antonio Querubin
e-mail:  tony@lavanauts.org
xmpp:  antonioquerubin@gmail.com


From simon.perreault@viagenie.ca  Mon Jun 11 06:30:56 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEDC121F85B7 for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 06:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 JCaIl0FbK31Z for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 06:30:55 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id D24AD21F85A2 for <mboned@ietf.org>; Mon, 11 Jun 2012 06:30:55 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c064:84e5:4ccb:c690:6774]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 40E77412D6; Mon, 11 Jun 2012 09:30:55 -0400 (EDT)
Message-ID: <4FD5F30E.50504@viagenie.ca>
Date: Mon, 11 Jun 2012 09:30:54 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
To: Antonio Querubin <tony@lavanauts.org>
References: <20120607132832.I69151@eng-mail01.juniper.net> <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com> <4FD1F277.8060608@viagenie.ca> <B0147C3DD45E42478038FC347CCB65FE02BC38DC1C@XCH-MW-08V.mw.nos.boeing.com> <alpine.LRH.2.02.1206090747380.2910@sol.manaikaika.com>
In-Reply-To: <alpine.LRH.2.02.1206090747380.2910@sol.manaikaika.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 13:30:56 -0000

On 2012-06-09 13:51, Antonio Querubin wrote:
>>>> 1. For our shipboard networks, which are dual-stack, we intend to
>>>> allow for IPv4 multicast sources to feed IPv6 clients, and vice
>>>> versa. The networks are dual stack throughout, but the end systems
>>>> are not likely to be. My preference is to send both v4 and v6
>>>> multicasts through the network, doing the conversion (if necessary)
>>>> at the edge router connecting to the source.
>>>
>>> Will that double the amount of multicast traffic in your network? If
>>> so,
>>> is it a problem?
>>
>> Yes, it could be double the bandwidth, if MLD and IGMP both indicate
>> membership. For us, that's not a problem. What it means is that the
>> IPv6 and IPv4 versions will go through the network along multicast
>> trees that are optimized for each respective IP version.
>>
>> The alternative approach is to allow sources to transmit either v4 or
>> v6 multicasts, and then to do the translation at the destination edge
>> routers, based on whether these edge routers receive IGMP or MLD join
>> reports. In principle, that works too. But it's far messier. There's
>> nothing easier than messing with the source side of the multicast, the
>> way IP multicast works. The source always has the easiest job of all.
>
> I concur. I had a similar problem a few years ago and went through the
> same analysis - and similar conclusion. Either let the source stream in
> both IPv4 and IPv6 directly, or if the source isn't configurable that
> way, run a local translator directly on the source to do the
> translation. Let the network decide which streams need replication - all
> the way to the source.

Understood, thanks.

Let's call this the "dual-stack approach", whether or not a very simple 
stateless translator, presumably based on RFC 6145, is used at the 
source. You have a dual-stack multicast network, that's what matters.

For a number of operational reasons, several operators are unable to use 
the dual-stack approach. Either they are forced to migrate their 
IPv4-only network directly to IPv6-only, or they cannot afford to have 
multicast streams flowing over both IPv4 and IPv6 simultaneously.

In my understanding, the multicast translation work that is being 
proposed in MBONED is targeted at operators that are unable to use the 
dual-stack approach. I think it could be fine to say, as it has been 
said for unicast, that the dual-stack approach is to be preferred. If 
it's impossible to go dual-stack, then here is a more complex 
translation framework that we can propose.

Makes sense?

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From albert.e.manfredi@boeing.com  Mon Jun 11 10:44:09 2012
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B339921F8622 for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 10:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 lCXNMHXIBKRi for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 10:44:08 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id E2C6321F8617 for <mboned@ietf.org>; Mon, 11 Jun 2012 10:44:08 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q5BHi5i2024269 for <mboned@ietf.org>; Mon, 11 Jun 2012 10:44:05 -0700
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.16.37]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q5BHi4wG024256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 11 Jun 2012 10:44:04 -0700
Received: from blv-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q5BHi6ug003102; Mon, 11 Jun 2012 10:44:06 -0700
Received: from XCH-MWHT-01.mw.nos.boeing.com (xch-mwht-01.mw.nos.boeing.com [134.57.113.35]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q5BHi5aW003031 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 11 Jun 2012 10:44:06 -0700
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.118.180]) by XCH-MWHT-01.mw.nos.boeing.com ([134.57.113.35]) with mapi; Mon, 11 Jun 2012 12:44:05 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Date: Mon, 11 Jun 2012 12:44:03 -0500
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: Ac1H1nIzOX+Ct5X0S0yTDftjqpoOPQAIn4jw
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02BC38DED8@XCH-MW-08V.mw.nos.boeing.com>
References: <20120607132832.I69151@eng-mail01.juniper.net> <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com> <4FD1F277.8060608@viagenie.ca> <B0147C3DD45E42478038FC347CCB65FE02BC38DC1C@XCH-MW-08V.mw.nos.boeing.com> <alpine.LRH.2.02.1206090747380.2910@sol.manaikaika.com> <4FD5F30E.50504@viagenie.ca>
In-Reply-To: <4FD5F30E.50504@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 17:44:09 -0000

> -----Original Message-----
> From: Simon Perreault [mailto:simon.perreault@viagenie.ca]
> Sent: Monday, June 11, 2012 9:31 AM
> To: Antonio Querubin

> > I concur. I had a similar problem a few years ago and went through
> the
> > same analysis - and similar conclusion. Either let the source stream
> in
> > both IPv4 and IPv6 directly, or if the source isn't configurable that
> > way, run a local translator directly on the source to do the
> > translation. Let the network decide which streams need replication -
> all
> > the way to the source.
>=20
> Understood, thanks.
>=20
> Let's call this the "dual-stack approach", whether or not a very simple
> stateless translator, presumably based on RFC 6145, is used at the
> source. You have a dual-stack multicast network, that's what matters.
>=20
> For a number of operational reasons, several operators are unable to
> use
> the dual-stack approach. Either they are forced to migrate their
> IPv4-only network directly to IPv6-only, or they cannot afford to have
> multicast streams flowing over both IPv4 and IPv6 simultaneously.
>=20
> In my understanding, the multicast translation work that is being
> proposed in MBONED is targeted at operators that are unable to use the
> dual-stack approach. I think it could be fine to say, as it has been
> said for unicast, that the dual-stack approach is to be preferred. If
> it's impossible to go dual-stack, then here is a more complex
> translation framework that we can propose.
>=20
> Makes sense?

Makes sense as one option. However even there, if I'm the operator of a dua=
l stack terrestrial network, with multicasts arriving from single stack net=
works, no matter IPv4 or IPv6, I might opt to create the "other" multicast =
version at the ingress gateway regardless. Just for the sake of simplicity.

So it would be good to know how one creates the extra IPv6 bits when receiv=
ing IPv4 multicasts, assuming we need one standard way of doing this. Other=
wise, if that IPv6 multicast traverses my network on its way to another IPv=
6 network, it might look different from the original. Whether this matters =
or not is probably case-specific.

Bert



From bill@cse.concordia.ca  Mon Jun 11 10:59:36 2012
Return-Path: <bill@cse.concordia.ca>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCDF621F854C for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 10:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 s3Dj-OAswagP for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 10:59:36 -0700 (PDT)
Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.94]) by ietfa.amsl.com (Postfix) with ESMTP id E444F21F845B for <mboned@ietf.org>; Mon, 11 Jun 2012 10:59:35 -0700 (PDT)
Received: from [IPv6:::1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from bill@cse.concordia.ca) (8.13.7/8.13.7) with ESMTP id q5BHxUaQ015339;  Mon, 11 Jun 2012 13:59:30 -0400
Message-ID: <4FD63203.7070701@cse.concordia.ca>
Date: Mon, 11 Jun 2012 13:59:31 -0400
From: Bill Atwood <bill@cse.concordia.ca>
Organization: Concordia University, Department of Computer Science and Software Engineering
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Greg Bumgardner <gbumgard@cisco.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2012/06/11 13:59:31 EDT
Cc: mboned@ietf.org
Subject: [MBONED] AMT spec
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 17:59:37 -0000

Greg,

Since our email to mboned (on 2011-03-23) about the security of AMT
evoked no responses, I have read the "Security Considerations" section
of the AMT draft carefully.

We presented two attacks: a Relay Impersonation attack and an attack
where a bogus message appears to come from a gateway, requesting
disconnection.

The description of the Relay Impersonation attack in the draft is
specific to the introduction of bogus routes.  Would it be worthwhile to
note that any method of impersonation (such as MitM) is a potential
attack here?

The bogus message case is well covered in the draft text.

One nit: Page 74, para 1, line 4.  "choose ignore" -> "choose to ignore"

  Bill
-- 

Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
Department of Computer Science
   and Software Engineering
Concordia University EV 3.185     email:bill@cse.concordia.ca
1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8

From lenny@juniper.net  Mon Jun 11 13:01:43 2012
Return-Path: <lenny@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 380BF11E809A for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 13:01:43 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kwHbCdBk1aQP for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 13:01:42 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 20DE611E808C for <mboned@ietf.org>; Mon, 11 Jun 2012 13:01:35 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKT9ZOngHXnYtJ/ih2GeirukpETEYk5nQ7@postini.com; Mon, 11 Jun 2012 13:01:42 PDT
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB01-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 11 Jun 2012 13:00:35 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id q5BK0B110918; Mon, 11 Jun 2012 13:00:34 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 152801145A;  Mon, 11 Jun 2012 13:00:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 081571144F; Mon, 11 Jun 2012 13:00:10 -0700 (PDT)
Date: Mon, 11 Jun 2012 13:00:09 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Simon Perreault <simon.perreault@viagenie.ca>
In-Reply-To: <4FD5F30E.50504@viagenie.ca>
Message-ID: <20120611125643.L37921@eng-mail01.juniper.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com> <4FD1F277.8060608@viagenie.ca> <B0147C3DD45E42478038FC347CCB65FE02BC38DC1C@XCH-MW-08V.mw.nos.boeing.com> <alpine.LRH.2.02.1206090747380.2910@sol.manaikaika.com> <4FD5F30E.50504@viagenie.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 20:01:43 -0000

On Mon, 11 Jun 2012, Simon Perreault wrote:

SNIP
-) 
-) For a number of operational reasons, several operators are unable to use the
-) dual-stack approach. Either they are forced to migrate their IPv4-only
-) network directly to IPv6-only, or they cannot afford to have multicast
-) streams flowing over both IPv4 and IPv6 simultaneously.
-) 
-) In my understanding, the multicast translation work that is being proposed in
-) MBONED is targeted at operators that are unable to use the dual-stack
-) approach. I think it could be fine to say, as it has been said for unicast,
-) that the dual-stack approach is to be preferred. If it's impossible to go
-) dual-stack, then here is a more complex translation framework that we can
-) propose.
-) 

Well, that's the main reason for this poll.  We want to understand what 
operators really are doing so that we are focusing our work on what is 
truly needed and not answering questions that no one is asking.

From gbumgard@cisco.com  Mon Jun 11 13:07:25 2012
Return-Path: <gbumgard@cisco.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E9BE21F845C for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 13:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 dt8k13n+Of9A for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 13:07:24 -0700 (PDT)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id D00DF21F854C for <mboned@ietf.org>; Mon, 11 Jun 2012 13:07:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gbumgard@cisco.com; l=1153; q=dns/txt; s=iport; t=1339445244; x=1340654844; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=xReTdAVNsvHkFaUBnx+vD+B9Jse5H+lBBacASrnutfc=; b=M15qPp1SxTeEqW3kqUY6vNO3QLCa2BJuJ4WQtQ+18140QV4jFEjSB0RZ +IPmyujjJvR6MlsvN182pUcW/cGZ2Xskq1Bc0K61+IbiIU0QIWbuT5tn0 q20+4cAwCu4ouY9PKqnYfnwmdwbHhtjop7/taoFwONhhYpqrE5L37zhbs o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqoFAHRO1k9Io8UY/2dsb2JhbABFsUGEX4IYAQEBBBIBFBFAARALGAkWDwkDAgECAUUGDQEHAQEeh2mZAJ9oiyQahU8DiECMXoVTiEKBZoMAgT8
X-IronPort-AV: E=Sophos;i="4.75,751,1330905600"; d="scan'208";a="14042614"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 11 Jun 2012 20:07:20 +0000
Received: from [10.20.185.146] (sjc-gbumgard-8911.cisco.com [10.20.185.146]) by bgl-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q5BK7J1H013635; Tue, 12 Jun 2012 01:37:19 +0530
Message-ID: <4FD64FFE.7030706@cisco.com>
Date: Mon, 11 Jun 2012 13:07:26 -0700
From: Greg Bumgardner <gbumgard@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Bill Atwood <bill@cse.concordia.ca>
References: <4FD63203.7070701@cse.concordia.ca>
In-Reply-To: <4FD63203.7070701@cse.concordia.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mboned@ietf.org
Subject: Re: [MBONED] AMT spec
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 20:07:25 -0000

  Bill,

Thank you for reviewing the draft. I recall we had a very short 
discussion regarding protocol security at an earlier IETF meeting but 
don't recall the e-mail you mention. I'll take a look in the list archive.

I can add a blurb regarding the protocols susceptibility to a MitM 
attack and post the change to the list.

Again, Thanks,

-g.b.


On 6/11/2012 10:59 AM, Bill Atwood wrote:
> Greg,
>
> Since our email to mboned (on 2011-03-23) about the security of AMT
> evoked no responses, I have read the "Security Considerations" section
> of the AMT draft carefully.
>
> We presented two attacks: a Relay Impersonation attack and an attack
> where a bogus message appears to come from a gateway, requesting
> disconnection.
>
> The description of the Relay Impersonation attack in the draft is
> specific to the introduction of bogus routes.  Would it be worthwhile to
> note that any method of impersonation (such as MitM) is a potential
> attack here?
>
> The bogus message case is well covered in the draft text.
>
> One nit: Page 74, para 1, line 4.  "choose ignore" ->  "choose to ignore"
>
>    Bill


From tom.taylor.stds@gmail.com  Mon Jun 11 13:17:02 2012
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5E521F85C4 for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 13:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 cag+zpUIAn1e for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 13:17:02 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id B089421F85C3 for <mboned@ietf.org>; Mon, 11 Jun 2012 13:17:01 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so4669727lbb.31 for <mboned@ietf.org>; Mon, 11 Jun 2012 13:16:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=GadySbU1HJlNNlOx8GGInUGsog5r00stO/xjCk66FlQ=; b=z9+zql6DuhVmdJR+Mgyhll2cub2UuE/X2LZhR0044byxlLIcaVVdsRu4ldtiWyZDvu rAv8se/MxuVjQzni3diIyXI+iaC7hyj4EJMHg2feZGubsPjMn9Cpr+bJ1dsGVwBoUsX9 DTwrm9hlmUwwTYJhJD22swiFAWGQ8Otq/PnzLEd+nP5k+8c/WBxTS0E0IL8yOJfVFelT gz2Rv4r8rDGbPdUQDwMhhIDUHlDqDQXHFl61znonDQC9lta9uI9kM+dhddvmAbwsWUI+ W6EVrEs4L0xR4v5z/dNm3bQNNjZyDtRmhyOVTkWw+GxPO5o3N4joI8jlQnZF50BspSQ4 snFw==
Received: by 10.152.147.33 with SMTP id th1mr18771942lab.9.1339445818567; Mon, 11 Jun 2012 13:16:58 -0700 (PDT)
Received: from [127.0.0.1] (dsl-173-206-85-206.tor.primus.ca. [173.206.85.206]) by mx.google.com with ESMTPS id gt19sm25865643lab.17.2012.06.11.13.16.55 (version=SSLv3 cipher=OTHER); Mon, 11 Jun 2012 13:16:57 -0700 (PDT)
Message-ID: <4FD65235.1090904@gmail.com>
Date: Mon, 11 Jun 2012 16:16:53 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
References: <20120607132832.I69151@eng-mail01.juniper.net> <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com> <4FD1F277.8060608@viagenie.ca> <B0147C3DD45E42478038FC347CCB65FE02BC38DC1C@XCH-MW-08V.mw.nos.boeing.com> <alpine.LRH.2.02.1206090747380.2910@sol.manaikaika.com> <4FD5F30E.50504@viagenie.ca> <B0147C3DD45E42478038FC347CCB65FE02BC38DED8@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BC38DED8@XCH-MW-08V.mw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120611-0, 11/06/2012), Outbound message
X-Antivirus-Status: Clean
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 20:17:02 -0000

On 11/06/2012 1:44 PM, Manfredi, Albert E wrote:
>> -----Original Message-----
>> From: Simon Perreault [mailto:simon.perreault@viagenie.ca]
>> Sent: Monday, June 11, 2012 9:31 AM
>> To: Antonio Querubin
>
>>> I concur. I had a similar problem a few years ago and went through
>> the
>>> same analysis - and similar conclusion. Either let the source stream
>> in
>>> both IPv4 and IPv6 directly, or if the source isn't configurable that
>>> way, run a local translator directly on the source to do the
>>> translation. Let the network decide which streams need replication -
>> all
>>> the way to the source.
>>
>> Understood, thanks.
>>
>> Let's call this the "dual-stack approach", whether or not a very simple
>> stateless translator, presumably based on RFC 6145, is used at the
>> source. You have a dual-stack multicast network, that's what matters.
>>
>> For a number of operational reasons, several operators are unable to
>> use
>> the dual-stack approach. Either they are forced to migrate their
>> IPv4-only network directly to IPv6-only, or they cannot afford to have
>> multicast streams flowing over both IPv4 and IPv6 simultaneously.
>>
>> In my understanding, the multicast translation work that is being
>> proposed in MBONED is targeted at operators that are unable to use the
>> dual-stack approach. I think it could be fine to say, as it has been
>> said for unicast, that the dual-stack approach is to be preferred. If
>> it's impossible to go dual-stack, then here is a more complex
>> translation framework that we can propose.
>>
>> Makes sense?
>
> Makes sense as one option. However even there, if I'm the operator of a dual stack terrestrial network, with multicasts arriving from single stack networks, no matter IPv4 or IPv6, I might opt to create the "other" multicast version at the ingress gateway regardless. Just for the sake of simplicity.
>
> So it would be good to know how one creates the extra IPv6 bits when receiving IPv4 multicasts, assuming we need one standard way of doing this. Otherwise, if that IPv6 multicast traverses my network on its way to another IPv6 network, it might look different from the original. Whether this matters or not is probably case-specific.
>
> Bert
>
I think the gateway also requires translation within PIM in the 
signalling direction. To move my PIM transition thinking forward, I've 
been look at existing implementations (XORP in particular) to see what 
would have to change.

Tom Taylor

From simon.perreault@viagenie.ca  Mon Jun 11 13:22:40 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DCFC21F85AF for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 13:22:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 3dOe2CtQQmyE for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 13:22:40 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 7E00F21F8568 for <mboned@ietf.org>; Mon, 11 Jun 2012 13:22:39 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c064:84e5:4ccb:c690:6774]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B25E0425D7; Mon, 11 Jun 2012 16:22:38 -0400 (EDT)
Message-ID: <4FD6538E.70701@viagenie.ca>
Date: Mon, 11 Jun 2012 16:22:38 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
To: Leonard Giuliano <lenny@juniper.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <B0147C3DD45E42478038FC347CCB65FE02BC38D9C7@XCH-MW-08V.mw.nos.boeing.com> <4FD1F277.8060608@viagenie.ca> <B0147C3DD45E42478038FC347CCB65FE02BC38DC1C@XCH-MW-08V.mw.nos.boeing.com> <alpine.LRH.2.02.1206090747380.2910@sol.manaikaika.com> <4FD5F30E.50504@viagenie.ca> <20120611125643.L37921@eng-mail01.juniper.net>
In-Reply-To: <20120611125643.L37921@eng-mail01.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 20:22:40 -0000

On 2012-06-11 16:00, Leonard Giuliano wrote:
> Well, that's the main reason for this poll.  We want to understand what
> operators really are doing so that we are focusing our work on what is
> truly needed and not answering questions that no one is asking.

Are you looking for answers from operators other than the ones 
co-authoring the drafts?

I mean, just by looking at the two adopted drafts I'm counting 4 
operators among the authors lists. 3 more in the acknowledgements 
section. Many others have been involved in the mailing list discussions.

Why are we asking this question yet again?

Isn't the problem statement draft supposed to be the definitive answer 
to this question?

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From rbonica@juniper.net  Mon Jun 11 21:27:10 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA33811E8098 for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 21:27:10 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q75Hdt11htUP for <mboned@ietfa.amsl.com>; Mon, 11 Jun 2012 21:27:10 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 2E03F11E8087 for <mboned@ietf.org>; Mon, 11 Jun 2012 21:27:09 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKT9bFHGMUgn8osH/7n6pFtulvbBYVXTED@postini.com; Mon, 11 Jun 2012 21:27:09 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 11 Jun 2012 21:25:16 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Tue, 12 Jun 2012 00:25:15 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Tue, 12 Jun 2012 00:25:14 -0400
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: Ac1ID/WIGyCV/JBcQ1yQPD/Spyv+zQAOUkyg
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76CC42530@EMBX01-WF.jnpr.net>
References: <mailman.237.1339446160.3336.mboned@ietf.org>
In-Reply-To: <mailman.237.1339446160.3336.mboned@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 04:27:10 -0000

Simon,

Lenny's question is not only appropriate, but necessary. In order to scope =
the MLTRANS work, the WG needs to know which of the use-cases described in =
draft-ietf-mboned-v4v6-mcast-ps are likely to be deployed.

So far, exactly one operator has stepped forward to say that he is deployin=
g use-cases 3.4 and 3.5 (aka, the dual-stack use-cases). In response to tha=
t post, the WG has identified the following solutions:

1) Source the stream twice, once over IPv4 and once over IPv6
2) Source the stream once. Deploy a box near the source that translates the=
 stream from IPvX to IPvY and sources the stream a second time over IPvY (A=
ntonio, Do I have that right?)
3) Source the stream once. Deploy multicast routers that are capable of gra=
fting IPvX receivers onto IPvY distribution trees.

Solutions 1 and 2 are simple, but may consume twice as much bandwidth as So=
lution 3. Solution 3 trades simplicity for bandwidth.=20

Of the operators who are deploying use-cases 3.4 and 3.5, do any prefer Sol=
ution 3 over the other two solutions? Are any operators planning to deploy =
use-cases other than 3.4 and 3.5?

Lacking this information, the WG has no idea what protocol machinery is act=
ually required.

                                                   Ron
                                                   /speaking as AD




>=20
> Are you looking for answers from operators other than the ones co-
> authoring the drafts?
>=20
> I mean, just by looking at the two adopted drafts I'm counting 4
> operators among the authors lists. 3 more in the acknowledgements
> section. Many others have been involved in the mailing list
> discussions.
>=20
> Why are we asking this question yet again?
>=20
> Isn't the problem statement draft supposed to be the definitive answer
> to this question?
>=20
> Simon


From tony@lavanauts.org  Tue Jun 12 06:40:23 2012
Return-Path: <tony@lavanauts.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F86421F8562 for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 06:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 rAynXLz+OE27 for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 06:40:23 -0700 (PDT)
Received: from slimemold.creativedynamo.com (slimemold.creativedynamo.com [IPv6:2605:b00:0:2:211:2fff:fef6:4287]) by ietfa.amsl.com (Postfix) with ESMTP id 3D0FB21F8554 for <mboned@ietf.org>; Tue, 12 Jun 2012 06:40:22 -0700 (PDT)
Received: from sol.manaikaika.com (sol.manaikaika.com [IPv6:2605:b00:1:0:230:1bff:fe3f:6050]) (authenticated bits=0) by slimemold.creativedynamo.com (8.13.8/8.13.8) with ESMTP id q5CDe38W003926 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Jun 2012 03:40:05 -1000
Date: Tue, 12 Jun 2012 03:40:03 -1000 (HST)
From: Antonio Querubin <tony@lavanauts.org>
X-X-Sender: tony@sol.manaikaika.com
To: Ronald Bonica <rbonica@juniper.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76CC42530@EMBX01-WF.jnpr.net>
Message-ID: <alpine.LRH.2.02.1206112302050.2259@sol.manaikaika.com>
References: <mailman.237.1339446160.3336.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D76CC42530@EMBX01-WF.jnpr.net>
User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 13:40:23 -0000

On Tue, 12 Jun 2012, Ronald Bonica wrote:

> 2) Source the stream once. Deploy a box near the source that translates 
> the stream from IPvX to IPvY and sources the stream a second time over 
> IPvY (Antonio, Do I have that right?)

On or near, depending on whether the source box itself is dual-stack.  I 
suspect it's pretty rare to find an OS that is not dual-stack capable any 
more.

Antonio Querubin
e-mail:  tony@lavanauts.org
xmpp:  antonioquerubin@gmail.com

From bingxuere@gmail.com  Tue Jun 12 07:11:57 2012
Return-Path: <bingxuere@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C904C21F861E for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 07:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.932
X-Spam-Level: 
X-Spam-Status: No, score=-1.932 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
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 49+qly06v0Tu for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 07:11:57 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2769E21F8617 for <mboned@ietf.org>; Tue, 12 Jun 2012 07:11:56 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so4035707ggn.31 for <mboned@ietf.org>; Tue, 12 Jun 2012 07:11:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qheIQYZ/rrwBPZ/UlLRtHe6xgZeQ5udxcs1wKNhyzCI=; b=umxUQlOyZ4Zf1at/oJ4rTQxGsvFETZvMVmJXlYbCarjJfTuDK90xZun9VTgaOcvYXm oK211flFVoo9RWCOjOkFcdbOvBkT/WwP4+/ffLSrUzNR40CyABEJSHJccjuRcdnJudqG J+wUVAh+iS67o15mInS7phiHv5ruYeAs7o81AKBvQ9awO0FvmiBXF56ZII6/OfxY2z3u cQbrWz9OPRMayZPVojH3opdaKNCbd/g8l8yPTILTQTHDzAVclFvenDZECRt5YXhhyD1D GnxwiKWZOI0LVSyhMbfgxIYYG9wlMGn9XGErjUv/xsX3inNJUHKg0BNja4pRjP1p2WaZ d8Ag==
Received: by 10.50.189.228 with SMTP id gl4mr8413753igc.43.1339510316206; Tue, 12 Jun 2012 07:11:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.46.6 with HTTP; Tue, 12 Jun 2012 07:11:16 -0700 (PDT)
In-Reply-To: <20120607132832.I69151@eng-mail01.juniper.net>
References: <20120607132832.I69151@eng-mail01.juniper.net>
From: Qiong <bingxuere@gmail.com>
Date: Tue, 12 Jun 2012 22:11:16 +0800
Message-ID: <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com>
To: Leonard Giuliano <lenny@juniper.net>
Content-Type: multipart/alternative; boundary=14dae9340ebb9209fb04c2470cff
Cc: MBONED WG <mboned@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 14:11:57 -0000

--14dae9340ebb9209fb04c2470cff
Content-Type: text/plain; charset=UTF-8

Dear all,

1. In our situation, the source may still remian in IPv4, while the
receiver will be IPv6-only since there is no more IPv4 address anymore.
However, the network might be IPv4-only, which can not support IPv6
multicast yet; or the network can support IPv6 multicast. This is the case
of 6-4.
Another situation is: the access network is still IPv4-only, and the core
netowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.

2. Use case: 3.2, 3.4,

Best wishes
Qiong

On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <lenny@juniper.net> wrote:

>
> The multicast transition work within MBONED was initially intended to
> consist of ~ 3 document with limited scope.  In a very short amount of
> time, we've seen 7 drafts (and counting) with scope widening.
>
> In order to make sure we are focusing on work that is of actual value to
> the community and prevent a flood of high volume/low value drafts, we would
> like to revisit the basic questions of multicast transition within MBONED.
>  We would like to hear answers from the WG to the following questions
> before continuing any work on multicast transition in MBONED:
>
> 1) Which operators intend to source multicast traffic from one IP version
> and receive it over another IP version?
>
> 2) For those who answer 1), please identify the use-cases of interest in
> draft-ietf-mboned-v4v6-mcast-**ps so we can limit discussion to solutions
> for those use cases.
>
>
> MBONED Chairs
> ______________________________**_________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/**listinfo/mboned<https://www.ietf.org/mailman/listinfo/mboned>
>

--14dae9340ebb9209fb04c2470cff
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Dear all,<br><br>1. In our situation, the source may still remian in IPv4, =
while the receiver will be IPv6-only since there is no more IPv4 address an=
ymore. However, the network might be IPv4-only, which can not support IPv6 =
multicast yet; or the network can support IPv6 multicast. This is the case =
of 6-4. <br>

Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.=
<br><br>2. Use case: 3.2, 3.4,<br><br>Best wishes<br>Qiong<br><br><div clas=
s=3D"gmail_quote">

On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:lenny@juniper.net" target=3D"_blank">lenny@juniper.net</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
The multicast transition work within MBONED was initially intended to consi=
st of ~ 3 document with limited scope. =C2=A0In a very short amount of time=
, we&#39;ve seen 7 drafts (and counting) with scope widening.<br>
<br>
In order to make sure we are focusing on work that is of actual value to th=
e community and prevent a flood of high volume/low value drafts, we would l=
ike to revisit the basic questions of multicast transition within MBONED. =
=C2=A0We would like to hear answers from the WG to the following questions =
before continuing any work on multicast transition in MBONED:<br>


<br>
1) Which operators intend to source multicast traffic from one IP version a=
nd receive it over another IP version?<br>
<br>
2) For those who answer 1), please identify the use-cases of interest in dr=
aft-ietf-mboned-v4v6-mcast-<u></u>ps so we can limit discussion to solution=
s for those use cases.<br>
<br>
<br>
MBONED Chairs<br>
______________________________<u></u>_________________<br>
MBONED mailing list<br>
<a href=3D"mailto:MBONED@ietf.org" target=3D"_blank">MBONED@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mboned" target=3D"_blank">=
https://www.ietf.org/mailman/<u></u>listinfo/mboned</a><br>
</blockquote></div><br>

--14dae9340ebb9209fb04c2470cff--

From simon.perreault@viagenie.ca  Tue Jun 12 07:46:07 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 432DC21F86D5 for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 07:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 KdyvDUyhmxSL for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 07:46:06 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 6FAAB21F86D0 for <mboned@ietf.org>; Tue, 12 Jun 2012 07:46:06 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c064:9938:7779:38d:513d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B875A4037F; Tue, 12 Jun 2012 10:46:04 -0400 (EDT)
Message-ID: <4FD7562C.8010502@viagenie.ca>
Date: Tue, 12 Jun 2012 10:46:04 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <mailman.237.1339446160.3336.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D76CC42530@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76CC42530@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 14:46:07 -0000

On 2012-06-12 00:25, Ronald Bonica wrote:
> Lenny's question is not only appropriate, but necessary. In order to scope the MLTRANS work, the WG needs to know which of the use-cases described in draft-ietf-mboned-v4v6-mcast-ps are likely to be deployed.

Yes the question is appropriate and necessary, but I feel like it has 
been asked and answered many times before.

> So far, exactly one operator has stepped forward

What about the operators co-authoring the drafts? Can we count them too?

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From rbonica@juniper.net  Tue Jun 12 08:33:41 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A28621F86DE for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 08:33:41 -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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 QBk2Qcho67MJ for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 08:33:40 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id D8FA421F86DB for <mboned@ietf.org>; Tue, 12 Jun 2012 08:33:39 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKT9dhUYnO2fxboGKS1IfQ2zAci0HmKfdt@postini.com; Tue, 12 Jun 2012 08:33:39 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 12 Jun 2012 08:30:39 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe01-hq.jnpr.net (172.24.192.59) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 12 Jun 2012 08:30:38 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Tue, 12 Jun 2012 11:30:37 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Simon Perreault <simon.perreault@viagenie.ca>
Date: Tue, 12 Jun 2012 11:30:36 -0400
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: Ac1Iqhmk1QTtVTycRl28HpM9X9YN2wABcqtQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76CC429DB@EMBX01-WF.jnpr.net>
References: <mailman.237.1339446160.3336.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D76CC42530@EMBX01-WF.jnpr.net> <4FD7562C.8010502@viagenie.ca>
In-Reply-To: <4FD7562C.8010502@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 15:33:41 -0000

Simon,

I may have missed something. Can you point me to a set of emails in which o=
perators identify the specific use-cases in which they are interested. So f=
ar, I only see two such messages and both were in response to Lenny's reque=
st.

                                                        Ron


> -----Original Message-----
> From: Simon Perreault [mailto:simon.perreault@viagenie.ca]
> Sent: Tuesday, June 12, 2012 10:46 AM
> To: Ronald Bonica
> Cc: mboned@ietf.org
> Subject: Re: [MBONED] Multicast transition work in MBONED
>=20
> On 2012-06-12 00:25, Ronald Bonica wrote:
> > Lenny's question is not only appropriate, but necessary. In order to
> scope the MLTRANS work, the WG needs to know which of the use-cases
> described in draft-ietf-mboned-v4v6-mcast-ps are likely to be deployed.
>=20
> Yes the question is appropriate and necessary, but I feel like it has
> been asked and answered many times before.
>=20
> > So far, exactly one operator has stepped forward
>=20
> What about the operators co-authoring the drafts? Can we count them
> too?
>=20
> Simon
> --
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> STUN/TURN server               --> http://numb.viagenie.ca

From simon.perreault@viagenie.ca  Tue Jun 12 09:30:01 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D39EE21F861D for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 09:30:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 rCyMA8KBj1RL for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 09:30:01 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 1D87A21F8613 for <mboned@ietf.org>; Tue, 12 Jun 2012 09:30:01 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c064:9938:7779:38d:513d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 8422E4037F; Tue, 12 Jun 2012 12:30:00 -0400 (EDT)
Message-ID: <4FD76E87.3060303@viagenie.ca>
Date: Tue, 12 Jun 2012 12:29:59 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <mailman.237.1339446160.3336.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D76CC42530@EMBX01-WF.jnpr.net> <4FD7562C.8010502@viagenie.ca> <13205C286662DE4387D9AF3AC30EF456D76CC429DB@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76CC429DB@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 16:30:02 -0000

On 2012-06-12 11:30, Ronald Bonica wrote:
> I may have missed something. Can you point me to a set of emails in which operators identify the specific use-cases in which they are interested. So far, I only see two such messages and both were in response to Lenny's request.

I don't think you have missed anything, but maybe we're not talking 
about the same thing. In my view, almost all discussions around 
multicast translation have been about use cases. There was a dedicated 
mailing list:

http://www.ietf.org/mail-archive/web/multrans/current/maillist.html


Two BOFs were taken on this topic:

IETF 81
Slides: http://www.ietf.org/proceedings/81/multrans.html
Minutes: http://www.ietf.org/jabber/logs/multrans/2011-07-25.html


IETF 82
Slides: http://www.ietf.org/proceedings/82/multrans.html
Minutes: http://www.ietf.org/jabber/logs/multrans/2011-11-17.html


The culmination of these discussions is 
draft-ietf-mboned-v4v6-mcast-ps-00. The whole point of this draft is 
answering the question of use cases.

I don't see why we're having some kind of vote instead of simply 
discussing the draft, just like any other draft. Let's argue about use 
cases that are in the draft but should not, and use cases that are not 
in the draft but should be. That would be productive. It would make the 
draft better, and chairs (of mboned and other working groups) could then 
use the draft, and the building of a consensus around it, as guidance.

Or maybe Lenny's question was intended to generate discussion on the 
draft, and I misinterpreted it as some kind of vote?

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From internet-drafts@ietf.org  Tue Jun 12 12:35:27 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88E2421F86FE; Tue, 12 Jun 2012 12:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 P3iBMATs8C4K; Tue, 12 Jun 2012 12:35:25 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F67421F86F7; Tue, 12 Jun 2012 12:35:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.20
Message-ID: <20120612193525.11546.60198.idtracker@ietfa.amsl.com>
Date: Tue, 12 Jun 2012 12:35:25 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-auto-multicast-14.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 19:35:27 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the MBONE Deployment Working Group of the IET=
F.

	Title           : Automatic Multicast Tunneling
	Author(s)       : Gregory Bumgardner
	Filename        : draft-ietf-mboned-auto-multicast-14.txt
	Pages           : 85
	Date            : 2012-06-12

Abstract:
   This document describes Automatic Multicast Tunneling (AMT), a
   protocol for delivering multicast traffic from sources in a
   multicast-enabled network to receivers that lack multicast
   connectivity to the source network.  The protocol uses UDP
   encapsulation and unicast replication to provide this functionality.

   The AMT protocol is specifically designed to support rapid deployment
   by requiring minimal changes to existing network infrastructure.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast

There's also a htmlized version available at:
http://tools.ietf.org/html/submission.filename }}-14

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-auto-multicast-14


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From rbonica@juniper.net  Tue Jun 12 12:58:04 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEAAE21F8546 for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 12:58:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brTQy4VAwF0K for <mboned@ietfa.amsl.com>; Tue, 12 Jun 2012 12:58:04 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 0972821F850D for <mboned@ietf.org>; Tue, 12 Jun 2012 12:58:03 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKT9efSxfCBbjqs3i5YRVdPE0UARo9uLVA@postini.com; Tue, 12 Jun 2012 12:58:04 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 12 Jun 2012 12:56:33 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 12 Jun 2012 12:56:33 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Tue, 12 Jun 2012 15:56:32 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Tue, 12 Jun 2012 15:56:31 -0400
Thread-Topic: Multicast transition work in MBONED 
Thread-Index: Ac1IuKL7Xa3yALX8SSWXNguOuex53wAHGkgQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76CC42FE7@EMBX01-WF.jnpr.net>
References: <mailman.456.1339518602.3336.mboned@ietf.org>
In-Reply-To: <mailman.456.1339518602.3336.mboned@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 19:58:04 -0000

>=20
> Or maybe Lenny's question was intended to generate discussion on the
> draft, and I misinterpreted it as some kind of vote?
>=20

Rest assured, nobody is voting. We are simply trying to figure out which us=
e-cases are likely to see deployment. Only the use-cases that will be deplo=
yed should motivate protocol work.


                                                        Ron


From rbonica@juniper.net  Mon Jun 18 08:11:27 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA5A21F86DC for <mboned@ietfa.amsl.com>; Mon, 18 Jun 2012 08:11:27 -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=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 kFpFsRfKQ1Dk for <mboned@ietfa.amsl.com>; Mon, 18 Jun 2012 08:11:27 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id E5D9921F86F9 for <mboned@ietf.org>; Mon, 18 Jun 2012 08:11:25 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKT99FHddHTtDS6eOTWoTFKpU/gHiiXQfL@postini.com; Mon, 18 Jun 2012 08:11:26 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 18 Jun 2012 08:07:33 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Mon, 18 Jun 2012 11:07:31 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Qiong <bingxuere@gmail.com>, Lenny Giuliano <lenny@juniper.net>
Date: Mon, 18 Jun 2012 11:07:30 -0400
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: Ac1IpVTGpX1nfmx8TUaEAaFuFgisCgEvUiuQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com>
In-Reply-To: <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_13205C286662DE4387D9AF3AC30EF456D76E909B8EEMBX01WFjnprn_"
MIME-Version: 1.0
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 15:11:27 -0000

--_000_13205C286662DE4387D9AF3AC30EF456D76E909B8EEMBX01WFjnprn_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUWlvbmcsDQoNCklmIHlvdSB3ZXJlIHRvIGVuYWJsZSBJUHY2IG11bHRpY2FzdCB0aHJvdWdo
b3V0IHlvdXIgbmV0d29yayBiZWZvcmUgZGVwbG95aW5nIElQdjYgb25seSByZWNlaXZlcnMsIHdv
dWxkIHlvdSBub3QgZmFsbCBpbnRvIHVzZSBjYXNlcyAzLjQgYW5kIDMuNSAodGhlIGR1YWwgc3Rh
Y2sgc2NlbmFyaW9zKS4gU2luY2UgeW91IGFyZSBnb2luZyB0byBoYXZlIHRvIGVuYWJsZSBJUHY2
IG11bHRpY2FzdCB0aHJvdWdob3V0IHlvdXIgbmV0d29yayBhbnl3YXksIHdvdWxkbuKAmXQgaXQg
YmUgYSBnb29kIGlkZWEgdG8gZG8gc28gc29vbmVyIHRoYW4gbGF0ZXI/DQoNCiAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICBSb24NCg0KRnJvbTogUWlvbmcgW21haWx0bzpiaW5neHVlcmVAZ21haWwuY29tXQ0KU2VudDog
VHVlc2RheSwgSnVuZSAxMiwgMjAxMiAxMDoxMSBBTQ0KVG86IExlbm55IEdpdWxpYW5vDQpDYzog
TUJPTkVEIFdHOyBSb25hbGQgQm9uaWNhDQpTdWJqZWN0OiBSZTogW01CT05FRF0gTXVsdGljYXN0
IHRyYW5zaXRpb24gd29yayBpbiBNQk9ORUQNCg0KRGVhciBhbGwsDQoNCjEuIEluIG91ciBzaXR1
YXRpb24sIHRoZSBzb3VyY2UgbWF5IHN0aWxsIHJlbWlhbiBpbiBJUHY0LCB3aGlsZSB0aGUgcmVj
ZWl2ZXIgd2lsbCBiZSBJUHY2LW9ubHkgc2luY2UgdGhlcmUgaXMgbm8gbW9yZSBJUHY0IGFkZHJl
c3MgYW55bW9yZS4gSG93ZXZlciwgdGhlIG5ldHdvcmsgbWlnaHQgYmUgSVB2NC1vbmx5LCB3aGlj
aCBjYW4gbm90IHN1cHBvcnQgSVB2NiBtdWx0aWNhc3QgeWV0OyBvciB0aGUgbmV0d29yayBjYW4g
c3VwcG9ydCBJUHY2IG11bHRpY2FzdC4gVGhpcyBpcyB0aGUgY2FzZSBvZiA2LTQuDQpBbm90aGVy
IHNpdHVhdGlvbiBpczogdGhlIGFjY2VzcyBuZXR3b3JrIGlzIHN0aWxsIElQdjQtb25seSwgYW5k
IHRoZSBjb3JlIG5ldG93cmsgKG9yIGFwcGxpY2F0aW9uIHBsYXRmb3JtKSBpcyBJUHY2LCB0aGVu
IHRoYXQgaXMgdGhlIGNhc2Ugb2YgNi00LTYtNC4NCg0KMi4gVXNlIGNhc2U6IDMuMiwgMy40LA0K
DQpCZXN0IHdpc2hlcw0KUWlvbmcNCk9uIEZyaSwgSnVuIDgsIDIwMTIgYXQgNDozNCBBTSwgTGVv
bmFyZCBHaXVsaWFubyA8bGVubnlAanVuaXBlci5uZXQ8bWFpbHRvOmxlbm55QGp1bmlwZXIubmV0
Pj4gd3JvdGU6DQoNClRoZSBtdWx0aWNhc3QgdHJhbnNpdGlvbiB3b3JrIHdpdGhpbiBNQk9ORUQg
d2FzIGluaXRpYWxseSBpbnRlbmRlZCB0byBjb25zaXN0IG9mIH4gMyBkb2N1bWVudCB3aXRoIGxp
bWl0ZWQgc2NvcGUuICBJbiBhIHZlcnkgc2hvcnQgYW1vdW50IG9mIHRpbWUsIHdlJ3ZlIHNlZW4g
NyBkcmFmdHMgKGFuZCBjb3VudGluZykgd2l0aCBzY29wZSB3aWRlbmluZy4NCg0KSW4gb3JkZXIg
dG8gbWFrZSBzdXJlIHdlIGFyZSBmb2N1c2luZyBvbiB3b3JrIHRoYXQgaXMgb2YgYWN0dWFsIHZh
bHVlIHRvIHRoZSBjb21tdW5pdHkgYW5kIHByZXZlbnQgYSBmbG9vZCBvZiBoaWdoIHZvbHVtZS9s
b3cgdmFsdWUgZHJhZnRzLCB3ZSB3b3VsZCBsaWtlIHRvIHJldmlzaXQgdGhlIGJhc2ljIHF1ZXN0
aW9ucyBvZiBtdWx0aWNhc3QgdHJhbnNpdGlvbiB3aXRoaW4gTUJPTkVELiAgV2Ugd291bGQgbGlr
ZSB0byBoZWFyIGFuc3dlcnMgZnJvbSB0aGUgV0cgdG8gdGhlIGZvbGxvd2luZyBxdWVzdGlvbnMg
YmVmb3JlIGNvbnRpbnVpbmcgYW55IHdvcmsgb24gbXVsdGljYXN0IHRyYW5zaXRpb24gaW4gTUJP
TkVEOg0KDQoxKSBXaGljaCBvcGVyYXRvcnMgaW50ZW5kIHRvIHNvdXJjZSBtdWx0aWNhc3QgdHJh
ZmZpYyBmcm9tIG9uZSBJUCB2ZXJzaW9uIGFuZCByZWNlaXZlIGl0IG92ZXIgYW5vdGhlciBJUCB2
ZXJzaW9uPw0KDQoyKSBGb3IgdGhvc2Ugd2hvIGFuc3dlciAxKSwgcGxlYXNlIGlkZW50aWZ5IHRo
ZSB1c2UtY2FzZXMgb2YgaW50ZXJlc3QgaW4gZHJhZnQtaWV0Zi1tYm9uZWQtdjR2Ni1tY2FzdC1w
cyBzbyB3ZSBjYW4gbGltaXQgZGlzY3Vzc2lvbiB0byBzb2x1dGlvbnMgZm9yIHRob3NlIHVzZSBj
YXNlcy4NCg0KDQpNQk9ORUQgQ2hhaXJzDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KTUJPTkVEIG1haWxpbmcgbGlzdA0KTUJPTkVEQGlldGYub3JnPG1h
aWx0bzpNQk9ORURAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL21ib25lZA0KDQo=

--_000_13205C286662DE4387D9AF3AC30EF456D76E909B8EEMBX01WFjnprn_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0
aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQt
ZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYi
O30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNw
YW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y
OnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE3
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
Iiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28t
c3R5bGUtdHlwZTpleHBvcnQtb25seTt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVp
biAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2Vj
dGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28g
OV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+
DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5
b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9v
OnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPjwvaGVhZD48Ym9keSBsYW5nPUVOLVVTIGxp
bms9Ymx1ZSB2bGluaz1wdXJwbGU+PGRpdiBjbGFzcz1Xb3JkU2VjdGlvbjE+PHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJp
Iiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+SGkgUWlvbmcsPG86cD48L286cD48L3NwYW4+
PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdE
Jz5JZiB5b3Ugd2VyZSB0byBlbmFibGUgSVB2NiBtdWx0aWNhc3QgdGhyb3VnaG91dCB5b3VyIG5l
dHdvcmsgYmVmb3JlIGRlcGxveWluZyBJUHY2IG9ubHkgcmVjZWl2ZXJzLCB3b3VsZCB5b3Ugbm90
IGZhbGwgaW50byB1c2UgY2FzZXMgMy40IGFuZCAzLjUgKHRoZSBkdWFsIHN0YWNrIHNjZW5hcmlv
cykuIFNpbmNlIHlvdSBhcmUgZ29pbmcgdG8gaGF2ZSB0byBlbmFibGUgSVB2NiBtdWx0aWNhc3Qg
dGhyb3VnaG91dCB5b3VyIG5ldHdvcmsgYW55d2F5LCB3b3VsZG7igJl0IGl0IGJlIGEgZ29vZCBp
ZGVhIHRvIGRvIHNvIHNvb25lciB0aGFuIGxhdGVyPyA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAg
Y2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPsKgwqDC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg
wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC
oMKgwqDCoMKgwqDCoMKgwqDCoCBSb248bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJp
Iiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
PjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFk
ZGluZzowaW4gMGluIDBpbiA0LjBwdCc+PGRpdj48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3Jk
ZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbic+PHAg
Y2xhc3M9TXNvTm9ybWFsPjxiPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIic+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIic+IFFpb25n
IFttYWlsdG86YmluZ3h1ZXJlQGdtYWlsLmNvbV0gPGJyPjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBK
dW5lIDEyLCAyMDEyIDEwOjExIEFNPGJyPjxiPlRvOjwvYj4gTGVubnkgR2l1bGlhbm88YnI+PGI+
Q2M6PC9iPiBNQk9ORUQgV0c7IFJvbmFsZCBCb25pY2E8YnI+PGI+U3ViamVjdDo8L2I+IFJlOiBb
TUJPTkVEXSBNdWx0aWNhc3QgdHJhbnNpdGlvbiB3b3JrIGluIE1CT05FRDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD48L2Rpdj48L2Rpdj48cCBjbGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48
L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtYXJnaW4tYm90dG9tOjEyLjBwdCc+RGVhciBh
bGwsPGJyPjxicj4xLiBJbiBvdXIgc2l0dWF0aW9uLCB0aGUgc291cmNlIG1heSBzdGlsbCByZW1p
YW4gaW4gSVB2NCwgd2hpbGUgdGhlIHJlY2VpdmVyIHdpbGwgYmUgSVB2Ni1vbmx5IHNpbmNlIHRo
ZXJlIGlzIG5vIG1vcmUgSVB2NCBhZGRyZXNzIGFueW1vcmUuIEhvd2V2ZXIsIHRoZSBuZXR3b3Jr
IG1pZ2h0IGJlIElQdjQtb25seSwgd2hpY2ggY2FuIG5vdCBzdXBwb3J0IElQdjYgbXVsdGljYXN0
IHlldDsgb3IgdGhlIG5ldHdvcmsgY2FuIHN1cHBvcnQgSVB2NiBtdWx0aWNhc3QuIFRoaXMgaXMg
dGhlIGNhc2Ugb2YgNi00LiA8YnI+QW5vdGhlciBzaXR1YXRpb24gaXM6IHRoZSBhY2Nlc3MgbmV0
d29yayBpcyBzdGlsbCBJUHY0LW9ubHksIGFuZCB0aGUgY29yZSBuZXRvd3JrIChvciBhcHBsaWNh
dGlvbiBwbGF0Zm9ybSkgaXMgSVB2NiwgdGhlbiB0aGF0IGlzIHRoZSBjYXNlIG9mIDYtNC02LTQu
PGJyPjxicj4yLiBVc2UgY2FzZTogMy4yLCAzLjQsPGJyPjxicj5CZXN0IHdpc2hlczxicj5RaW9u
ZzxvOnA+PC9vOnA+PC9wPjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPk9uIEZyaSwgSnVuIDgsIDIw
MTIgYXQgNDozNCBBTSwgTGVvbmFyZCBHaXVsaWFubyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmxlbm55
QGp1bmlwZXIubmV0IiB0YXJnZXQ9Il9ibGFuayI+bGVubnlAanVuaXBlci5uZXQ8L2E+Jmd0OyB3
cm90ZTo8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PGJyPlRoZSBtdWx0aWNhc3Qg
dHJhbnNpdGlvbiB3b3JrIHdpdGhpbiBNQk9ORUQgd2FzIGluaXRpYWxseSBpbnRlbmRlZCB0byBj
b25zaXN0IG9mIH4gMyBkb2N1bWVudCB3aXRoIGxpbWl0ZWQgc2NvcGUuICZuYnNwO0luIGEgdmVy
eSBzaG9ydCBhbW91bnQgb2YgdGltZSwgd2UndmUgc2VlbiA3IGRyYWZ0cyAoYW5kIGNvdW50aW5n
KSB3aXRoIHNjb3BlIHdpZGVuaW5nLjxicj48YnI+SW4gb3JkZXIgdG8gbWFrZSBzdXJlIHdlIGFy
ZSBmb2N1c2luZyBvbiB3b3JrIHRoYXQgaXMgb2YgYWN0dWFsIHZhbHVlIHRvIHRoZSBjb21tdW5p
dHkgYW5kIHByZXZlbnQgYSBmbG9vZCBvZiBoaWdoIHZvbHVtZS9sb3cgdmFsdWUgZHJhZnRzLCB3
ZSB3b3VsZCBsaWtlIHRvIHJldmlzaXQgdGhlIGJhc2ljIHF1ZXN0aW9ucyBvZiBtdWx0aWNhc3Qg
dHJhbnNpdGlvbiB3aXRoaW4gTUJPTkVELiAmbmJzcDtXZSB3b3VsZCBsaWtlIHRvIGhlYXIgYW5z
d2VycyBmcm9tIHRoZSBXRyB0byB0aGUgZm9sbG93aW5nIHF1ZXN0aW9ucyBiZWZvcmUgY29udGlu
dWluZyBhbnkgd29yayBvbiBtdWx0aWNhc3QgdHJhbnNpdGlvbiBpbiBNQk9ORUQ6PGJyPjxicj4x
KSBXaGljaCBvcGVyYXRvcnMgaW50ZW5kIHRvIHNvdXJjZSBtdWx0aWNhc3QgdHJhZmZpYyBmcm9t
IG9uZSBJUCB2ZXJzaW9uIGFuZCByZWNlaXZlIGl0IG92ZXIgYW5vdGhlciBJUCB2ZXJzaW9uPzxi
cj48YnI+MikgRm9yIHRob3NlIHdobyBhbnN3ZXIgMSksIHBsZWFzZSBpZGVudGlmeSB0aGUgdXNl
LWNhc2VzIG9mIGludGVyZXN0IGluIGRyYWZ0LWlldGYtbWJvbmVkLXY0djYtbWNhc3QtcHMgc28g
d2UgY2FuIGxpbWl0IGRpc2N1c3Npb24gdG8gc29sdXRpb25zIGZvciB0aG9zZSB1c2UgY2FzZXMu
PGJyPjxicj48YnI+TUJPTkVEIENoYWlyczxicj5fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXzxicj5NQk9ORUQgbWFpbGluZyBsaXN0PGJyPjxhIGhyZWY9Im1h
aWx0bzpNQk9ORURAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5NQk9ORURAaWV0Zi5vcmc8L2E+
PGJyPjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWJvbmVk
IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9t
Ym9uZWQ8L2E+PG86cD48L286cD48L3A+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPjwvZGl2PjwvZGl2PjwvYm9keT48L2h0bWw+

--_000_13205C286662DE4387D9AF3AC30EF456D76E909B8EEMBX01WFjnprn_--

From gjshep@gmail.com  Mon Jun 18 08:33:07 2012
Return-Path: <gjshep@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD9DF21F85D1 for <mboned@ietfa.amsl.com>; Mon, 18 Jun 2012 08:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 WLuoczkyG36D for <mboned@ietfa.amsl.com>; Mon, 18 Jun 2012 08:33:06 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8AC6121F86B9 for <mboned@ietf.org>; Mon, 18 Jun 2012 08:33:06 -0700 (PDT)
Received: by bkty8 with SMTP id y8so4744036bkt.31 for <mboned@ietf.org>; Mon, 18 Jun 2012 08:33:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=jpeOmV/xxKefoWYsp1R6CmWv1YneStKU2/VrH9X9dcg=; b=Ilr1oSs0SN0fp2c4rxCf5zw2ShzyLjqitBEAYarKtENYobx1NcTCLihKgC51DtF681 1elL6F/lGjScOcRGmAAw1PoxrIHMLkuQ2APCL6Md5E6hKI491T/rRouv+qejEYH/+3sz BgKAcsk49B9+cVjVXEBn62GhZUCa7eCgGhnKpU3a4UaLLZi2owARWaF29WBsAVfWbB7p 2Lff9iDLgHwBoViJLKxWtfmqLh48Fjn8mZF62aHE70FeO3YvunMcwGmcwgp27gzStl29 WqJpNc8eVcRRnKc0gpt1NZbOcqN7FZzNS8ZOCQvo7vRSmLDiO4xweLqJ64nxcumRjaMz qD3A==
MIME-Version: 1.0
Received: by 10.204.149.216 with SMTP id u24mr6535641bkv.36.1340033585463; Mon, 18 Jun 2012 08:33:05 -0700 (PDT)
Received: by 10.204.68.13 with HTTP; Mon, 18 Jun 2012 08:33:05 -0700 (PDT)
Date: Mon, 18 Jun 2012 08:33:05 -0700
Message-ID: <CABFReBqM+_2M0UbNUkNgbrnMZ_FgDF6GnyO3GU8EKYawMuVQOg@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
To: mboned@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [MBONED] WGLC -> Fwd: I-D Action: draft-ietf-mboned-auto-multicast-14.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gjshep@gmail.com
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 15:33:07 -0000

One more two week timer started for WGLC on the latest AMT draft.
Thanks to all who've been reading, responding, and progressing this
work. We're getting really close here.. I can feel it.

Read, resound (with corrections and/or support) by July 6th.

Thanks!,
Chairs


---------- Forwarded message ----------
From:  <internet-drafts@ietf.org>
Date: Tue, Jun 12, 2012 at 12:35 PM
Subject: [MBONED] I-D Action: draft-ietf-mboned-auto-multicast-14.txt
To: i-d-announce@ietf.org
Cc: mboned@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
=A0This draft is a work item of the MBONE Deployment Working Group of the I=
ETF.

=A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Automatic Multicast Tunneling
=A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Gregory Bumgardner
=A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-mboned-auto-multicast-1=
4.txt
=A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 85
=A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2012-06-12

Abstract:
=A0 This document describes Automatic Multicast Tunneling (AMT), a
=A0 protocol for delivering multicast traffic from sources in a
=A0 multicast-enabled network to receivers that lack multicast
=A0 connectivity to the source network. =A0The protocol uses UDP
=A0 encapsulation and unicast replication to provide this functionality.

=A0 The AMT protocol is specifically designed to support rapid deployment
=A0 by requiring minimal changes to existing network infrastructure.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast

There's also a htmlized version available at:
http://tools.ietf.org/html/submission.filename }}-14

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-auto-multicast-14


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
MBONED mailing list
MBONED@ietf.org
https://www.ietf.org/mailman/listinfo/mboned

From bingxuere@gmail.com  Mon Jun 18 19:03:22 2012
Return-Path: <bingxuere@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90FB311E80CB for <mboned@ietfa.amsl.com>; Mon, 18 Jun 2012 19:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.765
X-Spam-Level: 
X-Spam-Status: No, score=-2.765 tagged_above=-999 required=5 tests=[AWL=0.833,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 FPV-GDEEan9w for <mboned@ietfa.amsl.com>; Mon, 18 Jun 2012 19:03:21 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 91BD511E8097 for <mboned@ietf.org>; Mon, 18 Jun 2012 19:03:21 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so4687169ggn.31 for <mboned@ietf.org>; Mon, 18 Jun 2012 19:03:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=BJp2wG3YWTvQYlQlfJO/LbrnXjyMmkcblqA0QbBIrlY=; b=ZLRgKa3BBMwvjq3zr2YpIOfCL32x9qWe4FfNpGrD88cOp6uSnSu/pBLmCETqSTtyEX 7WGoCDjgQkItK5OhAozBb4nP3X3szFifcUQoIop8Igvq9R7RpElmwtVmQI5IG2yDd2FT 7c+YC2FaaR+GRN5Lc6ggpMoN1xPkxU7wKboi48jI36uHOW9RAjZ9owbkOTKhQ6B5Sfep FKceGCH5qoL+OaIth7uQE51B8Ddw0hemmOSS0263e/v9pcEZ+Ove1AGxb9MFL58nsRiL PI0wWAl+w2cEzRHKlxvUZbdqlSh2U31qiBleVRQ/3YbVNSUxWDNUD0ewKPuChiMUCPNb pASQ==
Received: by 10.50.154.201 with SMTP id vq9mr10237018igb.2.1340071400663; Mon, 18 Jun 2012 19:03:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.46.6 with HTTP; Mon, 18 Jun 2012 19:02:39 -0700 (PDT)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net>
From: Qiong <bingxuere@gmail.com>
Date: Tue, 19 Jun 2012 10:02:39 +0800
Message-ID: <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: multipart/alternative; boundary=14dae934081dcf69f304c2c9af87
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 02:03:22 -0000

--14dae934081dcf69f304c2c9af87
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Ronald,

I agree we do would like to enable IPv6 multicast in our network. However,
all these things can not be achieved within one night. We still have a lot
of old devices which can not support IPv6 multicast in our network, but we
are running out of IPv4 address right now. So we can not wait until the
whole network is ready for IPv6 multicast.

Hope it clarifies.

Best wishes
Qiong

On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica <rbonica@juniper.net> wrote=
:

> Hi Qiong,****
>
> ** **
>
> If you were to enable IPv6 multicast throughout your network before
> deploying IPv6 only receivers, would you not fall into use cases 3.4 and
> 3.5 (the dual stack scenarios). Since you are going to have to enable IPv=
6
> multicast throughout your network anyway, wouldn=E2=80=99t it be a good i=
dea to do
> so sooner than later? ****
>
> ** **
>
>                                                                       Ron=
*
> ***
>
> ** **
>
> *From:* Qiong [mailto:bingxuere@gmail.com]
> *Sent:* Tuesday, June 12, 2012 10:11 AM
> *To:* Lenny Giuliano
> *Cc:* MBONED WG; Ronald Bonica
>
> *Subject:* Re: [MBONED] Multicast transition work in MBONED****
>
> ** **
>
> Dear all,
>
>
> 1. In our situation, the source may still remian in IPv4, while the
> receiver will be IPv6-only since there is no more IPv4 address anymore.
> However, the network might be IPv4-only, which can not support IPv6
> multicast yet; or the network can support IPv6 multicast. This is the cas=
e
> of 6-4.
> Another situation is: the access network is still IPv4-only, and the core
> netowrk (or application platform) is IPv6, then that is the case of 6-4-6=
-4.
>
> 2. Use case: 3.2, 3.4,
>
> Best wishes
> Qiong****
>
> On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <lenny@juniper.net>
> wrote:****
>
>
> The multicast transition work within MBONED was initially intended to
> consist of ~ 3 document with limited scope.  In a very short amount of
> time, we've seen 7 drafts (and counting) with scope widening.
>
> In order to make sure we are focusing on work that is of actual value to
> the community and prevent a flood of high volume/low value drafts, we wou=
ld
> like to revisit the basic questions of multicast transition within MBONED=
.
>  We would like to hear answers from the WG to the following questions
> before continuing any work on multicast transition in MBONED:
>
> 1) Which operators intend to source multicast traffic from one IP version
> and receive it over another IP version?
>
> 2) For those who answer 1), please identify the use-cases of interest in
> draft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions f=
or
> those use cases.
>
>
> MBONED Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned****
>
> ** **
>

--14dae934081dcf69f304c2c9af87
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Ronald,<br><br>I agree we do would like to enable IPv6 multicast in our =
network. However, all these things can not be achieved within one night. We=
 still have a lot of old devices which can not support IPv6 multicast in ou=
r network, but we are running out of IPv4 address right now. So we can not =
wait until the whole network is ready for IPv6 multicast.<br>

<br>Hope it clarifies.<br><br>Best wishes<br>Qiong<br><br><div class=3D"gma=
il_quote">On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:rbonica@juniper.net" target=3D"_blank">rbonica@junip=
er.net</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"=
EN-US"><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Qiong,<u><=
/u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">If you were to enab=
le IPv6 multicast throughout your network before deploying IPv6 only receiv=
ers, would you not fall into use cases 3.4 and 3.5 (the dual stack scenario=
s). Since you are going to have to enable IPv6 multicast throughout your ne=
twork anyway, wouldn=E2=80=99t it be a good idea to do so sooner than later=
? <u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Ron<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0i=
n 0in 4.0pt">

<div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt=
 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span s=
tyle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&qu=
ot;"> Qiong [mailto:<a href=3D"mailto:bingxuere@gmail.com" target=3D"_blank=
">bingxuere@gmail.com</a>] <br>

<b>Sent:</b> Tuesday, June 12, 2012 10:11 AM<br><b>To:</b> Lenny Giuliano<b=
r><b>Cc:</b> MBONED WG; Ronald Bonica</span></p><div class=3D"im"><br><b>Su=
bject:</b> Re: [MBONED] Multicast transition work in MBONED<u></u><u></u></=
div>

<p></p></div></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=
=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Dear all,</p><div><div class=
=3D"h5"><br><br>1. In our situation, the source may still remian in IPv4, w=
hile the receiver will be IPv6-only since there is no more IPv4 address any=
more. However, the network might be IPv4-only, which can not support IPv6 m=
ulticast yet; or the network can support IPv6 multicast. This is the case o=
f 6-4. <br>

Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.=
<br><br>2. Use case: 3.2, 3.4,<br><br>Best wishes<br>Qiong<u></u><u></u></d=
iv>

</div><p></p><div><div class=3D"h5"><div><p class=3D"MsoNormal">On Fri, Jun=
 8, 2012 at 4:34 AM, Leonard Giuliano &lt;<a href=3D"mailto:lenny@juniper.n=
et" target=3D"_blank">lenny@juniper.net</a>&gt; wrote:<u></u><u></u></p><p =
class=3D"MsoNormal">

<br>The multicast transition work within MBONED was initially intended to c=
onsist of ~ 3 document with limited scope. =C2=A0In a very short amount of =
time, we&#39;ve seen 7 drafts (and counting) with scope widening.<br><br>In=
 order to make sure we are focusing on work that is of actual value to the =
community and prevent a flood of high volume/low value drafts, we would lik=
e to revisit the basic questions of multicast transition within MBONED. =C2=
=A0We would like to hear answers from the WG to the following questions bef=
ore continuing any work on multicast transition in MBONED:<br>

<br>1) Which operators intend to source multicast traffic from one IP versi=
on and receive it over another IP version?<br><br>2) For those who answer 1=
), please identify the use-cases of interest in draft-ietf-mboned-v4v6-mcas=
t-ps so we can limit discussion to solutions for those use cases.<br>

<br><br>MBONED Chairs<br>_______________________________________________<br=
>MBONED mailing list<br><a href=3D"mailto:MBONED@ietf.org" target=3D"_blank=
">MBONED@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/m=
boned" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mboned</a><u=
></u><u></u></p>

</div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div></div></div></di=
v></div></blockquote></div><br>

--14dae934081dcf69f304c2c9af87--

From rbonica@juniper.net  Wed Jun 20 01:48:48 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C96821F864F for <mboned@ietfa.amsl.com>; Wed, 20 Jun 2012 01:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.584
X-Spam-Level: 
X-Spam-Status: No, score=-106.584 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 lkmouDkG2HHz for <mboned@ietfa.amsl.com>; Wed, 20 Jun 2012 01:48:47 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id DB71021F8634 for <mboned@ietf.org>; Wed, 20 Jun 2012 01:48:46 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKT+GObMtxZy4oqt2fKsmFqZG7RokqE9I5@postini.com; Wed, 20 Jun 2012 01:48:46 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 20 Jun 2012 01:48:40 -0700
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 20 Jun 2012 01:48:39 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 20 Jun 2012 04:48:38 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Qiong <bingxuere@gmail.com>
Date: Wed, 20 Jun 2012 04:48:36 -0400
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: Ac1Nv7UrVW6kWSugTJWmpLLyTBVU9ABAMcGA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com>
In-Reply-To: <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_13205C286662DE4387D9AF3AC30EF456D76ECA6070EMBX01WFjnprn_"
MIME-Version: 1.0
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 08:48:48 -0000

--_000_13205C286662DE4387D9AF3AC30EF456D76ECA6070EMBX01WFjnprn_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

UWlvbmcsDQoNCldoaWNoIG9mIHRoZSBmb2xsb3dpbmcgZG8geW91IHRoaW5rIHdpbGwgcmVxdWly
ZSBtb3JlIG1vbmV5L2VmZm9ydDoNCg0KDQotICAgICAgICAgIFRvIGRlcGxveSBJUHY2IG11bHRp
Y2FzdCB0aHJvdWdob3V0IHlvdXIgbmV0d29yaw0KDQotICAgICAgICAgIFRvIGRlcGxveSB0aGUg
TUxUUkFOUyBtZWNoYW5pc21zIHRoYXQgeW91IHdpbGwgcmVxdWlyZSB0byBjb21wZW5zYXRlIGZv
ciB0aGUgbGFjayB0aGUgYWJvdmUgbWVudGlvbmVkIGNhcGFiaWxpdHkNCg0KSG93IG11Y2ggbW9y
ZSBtb25leS9lZmZvcnQ/IFdoeT8NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIFJvbg0KDQoNCkZyb206IFFpb25nIFttYWlsdG86YmluZ3h1ZXJlQGdt
YWlsLmNvbV0NClNlbnQ6IE1vbmRheSwgSnVuZSAxOCwgMjAxMiAxMDowMyBQTQ0KVG86IFJvbmFs
ZCBCb25pY2ENCkNjOiBMZW5ueSBHaXVsaWFubzsgTUJPTkVEIFdHDQpTdWJqZWN0OiBSZTogW01C
T05FRF0gTXVsdGljYXN0IHRyYW5zaXRpb24gd29yayBpbiBNQk9ORUQNCg0KSGkgUm9uYWxkLA0K
DQpJIGFncmVlIHdlIGRvIHdvdWxkIGxpa2UgdG8gZW5hYmxlIElQdjYgbXVsdGljYXN0IGluIG91
ciBuZXR3b3JrLiBIb3dldmVyLCBhbGwgdGhlc2UgdGhpbmdzIGNhbiBub3QgYmUgYWNoaWV2ZWQg
d2l0aGluIG9uZSBuaWdodC4gV2Ugc3RpbGwgaGF2ZSBhIGxvdCBvZiBvbGQgZGV2aWNlcyB3aGlj
aCBjYW4gbm90IHN1cHBvcnQgSVB2NiBtdWx0aWNhc3QgaW4gb3VyIG5ldHdvcmssIGJ1dCB3ZSBh
cmUgcnVubmluZyBvdXQgb2YgSVB2NCBhZGRyZXNzIHJpZ2h0IG5vdy4gU28gd2UgY2FuIG5vdCB3
YWl0IHVudGlsIHRoZSB3aG9sZSBuZXR3b3JrIGlzIHJlYWR5IGZvciBJUHY2IG11bHRpY2FzdC4N
Cg0KSG9wZSBpdCBjbGFyaWZpZXMuDQoNCkJlc3Qgd2lzaGVzDQpRaW9uZw0KT24gTW9uLCBKdW4g
MTgsIDIwMTIgYXQgMTE6MDcgUE0sIFJvbmFsZCBCb25pY2EgPHJib25pY2FAanVuaXBlci5uZXQ8
bWFpbHRvOnJib25pY2FAanVuaXBlci5uZXQ+PiB3cm90ZToNCkhpIFFpb25nLA0KDQpJZiB5b3Ug
d2VyZSB0byBlbmFibGUgSVB2NiBtdWx0aWNhc3QgdGhyb3VnaG91dCB5b3VyIG5ldHdvcmsgYmVm
b3JlIGRlcGxveWluZyBJUHY2IG9ubHkgcmVjZWl2ZXJzLCB3b3VsZCB5b3Ugbm90IGZhbGwgaW50
byB1c2UgY2FzZXMgMy40IGFuZCAzLjUgKHRoZSBkdWFsIHN0YWNrIHNjZW5hcmlvcykuIFNpbmNl
IHlvdSBhcmUgZ29pbmcgdG8gaGF2ZSB0byBlbmFibGUgSVB2NiBtdWx0aWNhc3QgdGhyb3VnaG91
dCB5b3VyIG5ldHdvcmsgYW55d2F5LCB3b3VsZG7igJl0IGl0IGJlIGEgZ29vZCBpZGVhIHRvIGRv
IHNvIHNvb25lciB0aGFuIGxhdGVyPw0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUm9uDQoNCkZyb206IFFpb25n
IFttYWlsdG86YmluZ3h1ZXJlQGdtYWlsLmNvbTxtYWlsdG86YmluZ3h1ZXJlQGdtYWlsLmNvbT5d
DQpTZW50OiBUdWVzZGF5LCBKdW5lIDEyLCAyMDEyIDEwOjExIEFNDQpUbzogTGVubnkgR2l1bGlh
bm8NCkNjOiBNQk9ORUQgV0c7IFJvbmFsZCBCb25pY2ENCg0KU3ViamVjdDogUmU6IFtNQk9ORURd
IE11bHRpY2FzdCB0cmFuc2l0aW9uIHdvcmsgaW4gTUJPTkVEDQoNCkRlYXIgYWxsLA0KDQoNCjEu
IEluIG91ciBzaXR1YXRpb24sIHRoZSBzb3VyY2UgbWF5IHN0aWxsIHJlbWlhbiBpbiBJUHY0LCB3
aGlsZSB0aGUgcmVjZWl2ZXIgd2lsbCBiZSBJUHY2LW9ubHkgc2luY2UgdGhlcmUgaXMgbm8gbW9y
ZSBJUHY0IGFkZHJlc3MgYW55bW9yZS4gSG93ZXZlciwgdGhlIG5ldHdvcmsgbWlnaHQgYmUgSVB2
NC1vbmx5LCB3aGljaCBjYW4gbm90IHN1cHBvcnQgSVB2NiBtdWx0aWNhc3QgeWV0OyBvciB0aGUg
bmV0d29yayBjYW4gc3VwcG9ydCBJUHY2IG11bHRpY2FzdC4gVGhpcyBpcyB0aGUgY2FzZSBvZiA2
LTQuDQpBbm90aGVyIHNpdHVhdGlvbiBpczogdGhlIGFjY2VzcyBuZXR3b3JrIGlzIHN0aWxsIElQ
djQtb25seSwgYW5kIHRoZSBjb3JlIG5ldG93cmsgKG9yIGFwcGxpY2F0aW9uIHBsYXRmb3JtKSBp
cyBJUHY2LCB0aGVuIHRoYXQgaXMgdGhlIGNhc2Ugb2YgNi00LTYtNC4NCg0KMi4gVXNlIGNhc2U6
IDMuMiwgMy40LA0KDQpCZXN0IHdpc2hlcw0KUWlvbmcNCk9uIEZyaSwgSnVuIDgsIDIwMTIgYXQg
NDozNCBBTSwgTGVvbmFyZCBHaXVsaWFubyA8bGVubnlAanVuaXBlci5uZXQ8bWFpbHRvOmxlbm55
QGp1bmlwZXIubmV0Pj4gd3JvdGU6DQoNClRoZSBtdWx0aWNhc3QgdHJhbnNpdGlvbiB3b3JrIHdp
dGhpbiBNQk9ORUQgd2FzIGluaXRpYWxseSBpbnRlbmRlZCB0byBjb25zaXN0IG9mIH4gMyBkb2N1
bWVudCB3aXRoIGxpbWl0ZWQgc2NvcGUuICBJbiBhIHZlcnkgc2hvcnQgYW1vdW50IG9mIHRpbWUs
IHdlJ3ZlIHNlZW4gNyBkcmFmdHMgKGFuZCBjb3VudGluZykgd2l0aCBzY29wZSB3aWRlbmluZy4N
Cg0KSW4gb3JkZXIgdG8gbWFrZSBzdXJlIHdlIGFyZSBmb2N1c2luZyBvbiB3b3JrIHRoYXQgaXMg
b2YgYWN0dWFsIHZhbHVlIHRvIHRoZSBjb21tdW5pdHkgYW5kIHByZXZlbnQgYSBmbG9vZCBvZiBo
aWdoIHZvbHVtZS9sb3cgdmFsdWUgZHJhZnRzLCB3ZSB3b3VsZCBsaWtlIHRvIHJldmlzaXQgdGhl
IGJhc2ljIHF1ZXN0aW9ucyBvZiBtdWx0aWNhc3QgdHJhbnNpdGlvbiB3aXRoaW4gTUJPTkVELiAg
V2Ugd291bGQgbGlrZSB0byBoZWFyIGFuc3dlcnMgZnJvbSB0aGUgV0cgdG8gdGhlIGZvbGxvd2lu
ZyBxdWVzdGlvbnMgYmVmb3JlIGNvbnRpbnVpbmcgYW55IHdvcmsgb24gbXVsdGljYXN0IHRyYW5z
aXRpb24gaW4gTUJPTkVEOg0KDQoxKSBXaGljaCBvcGVyYXRvcnMgaW50ZW5kIHRvIHNvdXJjZSBt
dWx0aWNhc3QgdHJhZmZpYyBmcm9tIG9uZSBJUCB2ZXJzaW9uIGFuZCByZWNlaXZlIGl0IG92ZXIg
YW5vdGhlciBJUCB2ZXJzaW9uPw0KDQoyKSBGb3IgdGhvc2Ugd2hvIGFuc3dlciAxKSwgcGxlYXNl
IGlkZW50aWZ5IHRoZSB1c2UtY2FzZXMgb2YgaW50ZXJlc3QgaW4gZHJhZnQtaWV0Zi1tYm9uZWQt
djR2Ni1tY2FzdC1wcyBzbyB3ZSBjYW4gbGltaXQgZGlzY3Vzc2lvbiB0byBzb2x1dGlvbnMgZm9y
IHRob3NlIHVzZSBjYXNlcy4NCg0KDQpNQk9ORUQgQ2hhaXJzDQpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KTUJPTkVEIG1haWxpbmcgbGlzdA0KTUJPTkVE
QGlldGYub3JnPG1haWx0bzpNQk9ORURAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL21ib25lZA0KDQoNCg==

--_000_13205C286662DE4387D9AF3AC30EF456D76ECA6070EMBX01WFjnprn_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6V2luZ2RpbmdzOw0K
CXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250
LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAz
IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDEx
IDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30N
CmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcA0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFy
Z2luLXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVm
dDowaW47DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFu
Iiwic2VyaWYiO30NCnAuTXNvQWNldGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1zb0FjZXRhdGUN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQg
Q2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXpl
OjguMHB0Ow0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpwLk1zb0xpc3RQ
YXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdyYXBoDQoJe21z
by1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBpbjsNCgltYXJnaW4tcmlnaHQ6MGlu
Ow0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1hcmdpbi1sZWZ0Oi41aW47DQoJbWFyZ2luLWJvdHRv
bTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBS
b21hbiIsInNlcmlmIjt9DQpzcGFuLkJhbGxvb25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToi
QmFsbG9vbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUt
bGluazoiQmFsbG9vbiBUZXh0IjsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7
fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5N
c29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5O30NCkBwYWdlIFdvcmRT
ZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4g
MS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0
IERlZmluaXRpb25zICovDQpAbGlzdCBsMA0KCXttc28tbGlzdC1pZDoxMTIzMjMwOTI1Ow0KCW1z
by1saXN0LXR5cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczotMTA0MzY3MTc0MiAy
NDY5NDY0NTAgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTMgNjc2
OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTM7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC1z
dGFydC1hdDowOw0KCW1zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwt
dGV4dDotOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9z
aXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjsNCgltc28tZmFyZWFzdC1mb250LWZhbWlseTpDYWxpYnJpO30NCm9sDQoJ
e21hcmdpbi1ib3R0b206MGluO30NCnVsDQoJe21hcmdpbi1ib3R0b206MGluO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT48L2hlYWQ+
PGJvZHkgbGFuZz1FTi1VUyBsaW5rPWJsdWUgdmxpbms9cHVycGxlPjxkaXYgY2xhc3M9V29yZFNl
Y3Rpb24xPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPlFpb25nLDxv
OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0
OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu
IHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJp
ZiI7Y29sb3I6IzFGNDk3RCc+V2hpY2ggb2YgdGhlIGZvbGxvd2luZyBkbyB5b3UgdGhpbmsgd2ls
bCByZXF1aXJlIG1vcmUgbW9uZXkvZWZmb3J0OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFz
cz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNh
bGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+PHAgY2xhc3M9TXNvTGlzdFBhcmFncmFwaCBzdHlsZT0ndGV4dC1pbmRlbnQ6LS4yNWlu
O21zby1saXN0OmwwIGxldmVsMSBsZm8xJz48IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBzdHls
ZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2Nv
bG9yOiMxRjQ5N0QnPjxzcGFuIHN0eWxlPSdtc28tbGlzdDpJZ25vcmUnPi08c3BhbiBzdHlsZT0n
Zm9udDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlm
XT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNh
bnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPlRvIGRlcGxveSBJUHY2IG11bHRpY2FzdCB0aHJvdWdo
b3V0IHlvdXIgbmV0d29yazxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29MaXN0UGFy
YWdyYXBoIHN0eWxlPSd0ZXh0LWluZGVudDotLjI1aW47bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEn
PjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PHNwYW4gc3R5bGU9
J21zby1saXN0Oklnbm9yZSc+LTxzcGFuIHN0eWxlPSdmb250OjcuMHB0ICJUaW1lcyBOZXcgUm9t
YW4iJz4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxlPSdmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+
VG8gZGVwbG95IHRoZSBNTFRSQU5TIG1lY2hhbmlzbXMgdGhhdCB5b3Ugd2lsbCByZXF1aXJlIHRv
IGNvbXBlbnNhdGUgZm9yIHRoZSBsYWNrIHRoZSBhYm92ZSBtZW50aW9uZWQgY2FwYWJpbGl0eTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0
OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu
IHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJp
ZiI7Y29sb3I6IzFGNDk3RCc+SG93IG11Y2ggbW9yZSBtb25leS9lZmZvcnQ/IFdoeT88bzpwPjwv
bzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHls
ZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2Nv
bG9yOiMxRjQ5N0QnPsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg
wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBSb248
bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFG
NDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3Bh
biBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48ZGl2IHN0eWxl
PSdib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBp
biAwaW4gNC4wcHQnPjxkaXY+PGRpdiBzdHlsZT0nYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xp
ZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4nPjxwIGNsYXNzPU1zb05v
cm1hbD48Yj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21h
Iiwic2Fucy1zZXJpZiInPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPiBRaW9uZyBbbWFpbHRvOmJp
bmd4dWVyZUBnbWFpbC5jb21dIDxicj48Yj5TZW50OjwvYj4gTW9uZGF5LCBKdW5lIDE4LCAyMDEy
IDEwOjAzIFBNPGJyPjxiPlRvOjwvYj4gUm9uYWxkIEJvbmljYTxicj48Yj5DYzo8L2I+IExlbm55
IEdpdWxpYW5vOyBNQk9ORUQgV0c8YnI+PGI+U3ViamVjdDo8L2I+IFJlOiBbTUJPTkVEXSBNdWx0
aWNhc3QgdHJhbnNpdGlvbiB3b3JrIGluIE1CT05FRDxvOnA+PC9vOnA+PC9zcGFuPjwvcD48L2Rp
dj48L2Rpdj48cCBjbGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48L3A+PHAgY2xhc3M9
TXNvTm9ybWFsIHN0eWxlPSdtYXJnaW4tYm90dG9tOjEyLjBwdCc+SGkgUm9uYWxkLDxicj48YnI+
SSBhZ3JlZSB3ZSBkbyB3b3VsZCBsaWtlIHRvIGVuYWJsZSBJUHY2IG11bHRpY2FzdCBpbiBvdXIg
bmV0d29yay4gSG93ZXZlciwgYWxsIHRoZXNlIHRoaW5ncyBjYW4gbm90IGJlIGFjaGlldmVkIHdp
dGhpbiBvbmUgbmlnaHQuIFdlIHN0aWxsIGhhdmUgYSBsb3Qgb2Ygb2xkIGRldmljZXMgd2hpY2gg
Y2FuIG5vdCBzdXBwb3J0IElQdjYgbXVsdGljYXN0IGluIG91ciBuZXR3b3JrLCBidXQgd2UgYXJl
IHJ1bm5pbmcgb3V0IG9mIElQdjQgYWRkcmVzcyByaWdodCBub3cuIFNvIHdlIGNhbiBub3Qgd2Fp
dCB1bnRpbCB0aGUgd2hvbGUgbmV0d29yayBpcyByZWFkeSBmb3IgSVB2NiBtdWx0aWNhc3QuPGJy
Pjxicj5Ib3BlIGl0IGNsYXJpZmllcy48YnI+PGJyPkJlc3Qgd2lzaGVzPGJyPlFpb25nPG86cD48
L286cD48L3A+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWw+T24gTW9uLCBKdW4gMTgsIDIwMTIgYXQg
MTE6MDcgUE0sIFJvbmFsZCBCb25pY2EgJmx0OzxhIGhyZWY9Im1haWx0bzpyYm9uaWNhQGp1bmlw
ZXIubmV0IiB0YXJnZXQ9Il9ibGFuayI+cmJvbmljYUBqdW5pcGVyLm5ldDwvYT4mZ3Q7IHdyb3Rl
OjxvOnA+PC9vOnA+PC9wPjxkaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz48c3BhbiBzdHls
ZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2Nv
bG9yOiMxRjQ5N0QnPkhpIFFpb25nLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29O
b3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvJz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJy
aSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwv
cD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvJz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPklmIHlvdSB3ZXJl
IHRvIGVuYWJsZSBJUHY2IG11bHRpY2FzdCB0aHJvdWdob3V0IHlvdXIgbmV0d29yayBiZWZvcmUg
ZGVwbG95aW5nIElQdjYgb25seSByZWNlaXZlcnMsIHdvdWxkIHlvdSBub3QgZmFsbCBpbnRvIHVz
ZSBjYXNlcyAzLjQgYW5kIDMuNSAodGhlIGR1YWwgc3RhY2sgc2NlbmFyaW9zKS4gU2luY2UgeW91
IGFyZSBnb2luZyB0byBoYXZlIHRvIGVuYWJsZSBJUHY2IG11bHRpY2FzdCB0aHJvdWdob3V0IHlv
dXIgbmV0d29yayBhbnl3YXksIHdvdWxkbuKAmXQgaXQgYmUgYSBnb29kIGlkZWEgdG8gZG8gc28g
c29vbmVyIHRoYW4gbGF0ZXI/IDwvc3Bhbj48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3Jt
YWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvJz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD48
cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvJz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyBSb248L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtj
b2xvcjojMUY0OTdEJz4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+PGRpdiBzdHlsZT0nYm9y
ZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGlu
IDQuMHB0Jz48ZGl2PjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1
QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluJz48cCBjbGFzcz1Nc29Ob3JtYWwg
c3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Jz48Yj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwi
c2Fucy1zZXJpZiInPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPiBRaW9uZyBbbWFpbHRvOjxhIGhy
ZWY9Im1haWx0bzpiaW5neHVlcmVAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+YmluZ3h1ZXJl
QGdtYWlsLmNvbTwvYT5dIDxicj48Yj5TZW50OjwvYj4gVHVlc2RheSwgSnVuZSAxMiwgMjAxMiAx
MDoxMSBBTTxicj48Yj5Ubzo8L2I+IExlbm55IEdpdWxpYW5vPGJyPjxiPkNjOjwvYj4gTUJPTkVE
IFdHOyBSb25hbGQgQm9uaWNhPC9zcGFuPjxvOnA+PC9vOnA+PC9wPjxkaXY+PHAgY2xhc3M9TXNv
Tm9ybWFsPjxicj48Yj5TdWJqZWN0OjwvYj4gUmU6IFtNQk9ORURdIE11bHRpY2FzdCB0cmFuc2l0
aW9uIHdvcmsgaW4gTUJPTkVEPG86cD48L286cD48L3A+PC9kaXY+PC9kaXY+PC9kaXY+PHAgY2xh
c3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byc+Jm5ic3A7PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0
eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCc+RGVhciBh
bGwsPG86cD48L286cD48L3A+PGRpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48YnI+PGJyPjEu
IEluIG91ciBzaXR1YXRpb24sIHRoZSBzb3VyY2UgbWF5IHN0aWxsIHJlbWlhbiBpbiBJUHY0LCB3
aGlsZSB0aGUgcmVjZWl2ZXIgd2lsbCBiZSBJUHY2LW9ubHkgc2luY2UgdGhlcmUgaXMgbm8gbW9y
ZSBJUHY0IGFkZHJlc3MgYW55bW9yZS4gSG93ZXZlciwgdGhlIG5ldHdvcmsgbWlnaHQgYmUgSVB2
NC1vbmx5LCB3aGljaCBjYW4gbm90IHN1cHBvcnQgSVB2NiBtdWx0aWNhc3QgeWV0OyBvciB0aGUg
bmV0d29yayBjYW4gc3VwcG9ydCBJUHY2IG11bHRpY2FzdC4gVGhpcyBpcyB0aGUgY2FzZSBvZiA2
LTQuIDxicj5Bbm90aGVyIHNpdHVhdGlvbiBpczogdGhlIGFjY2VzcyBuZXR3b3JrIGlzIHN0aWxs
IElQdjQtb25seSwgYW5kIHRoZSBjb3JlIG5ldG93cmsgKG9yIGFwcGxpY2F0aW9uIHBsYXRmb3Jt
KSBpcyBJUHY2LCB0aGVuIHRoYXQgaXMgdGhlIGNhc2Ugb2YgNi00LTYtNC48YnI+PGJyPjIuIFVz
ZSBjYXNlOiAzLjIsIDMuNCw8YnI+PGJyPkJlc3Qgd2lzaGVzPGJyPlFpb25nPG86cD48L286cD48
L3A+PC9kaXY+PC9kaXY+PGRpdj48ZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+T24gRnJp
LCBKdW4gOCwgMjAxMiBhdCA0OjM0IEFNLCBMZW9uYXJkIEdpdWxpYW5vICZsdDs8YSBocmVmPSJt
YWlsdG86bGVubnlAanVuaXBlci5uZXQiIHRhcmdldD0iX2JsYW5rIj5sZW5ueUBqdW5pcGVyLm5l
dDwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0n
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8nPjxicj5U
aGUgbXVsdGljYXN0IHRyYW5zaXRpb24gd29yayB3aXRoaW4gTUJPTkVEIHdhcyBpbml0aWFsbHkg
aW50ZW5kZWQgdG8gY29uc2lzdCBvZiB+IDMgZG9jdW1lbnQgd2l0aCBsaW1pdGVkIHNjb3BlLiAm
bmJzcDtJbiBhIHZlcnkgc2hvcnQgYW1vdW50IG9mIHRpbWUsIHdlJ3ZlIHNlZW4gNyBkcmFmdHMg
KGFuZCBjb3VudGluZykgd2l0aCBzY29wZSB3aWRlbmluZy48YnI+PGJyPkluIG9yZGVyIHRvIG1h
a2Ugc3VyZSB3ZSBhcmUgZm9jdXNpbmcgb24gd29yayB0aGF0IGlzIG9mIGFjdHVhbCB2YWx1ZSB0
byB0aGUgY29tbXVuaXR5IGFuZCBwcmV2ZW50IGEgZmxvb2Qgb2YgaGlnaCB2b2x1bWUvbG93IHZh
bHVlIGRyYWZ0cywgd2Ugd291bGQgbGlrZSB0byByZXZpc2l0IHRoZSBiYXNpYyBxdWVzdGlvbnMg
b2YgbXVsdGljYXN0IHRyYW5zaXRpb24gd2l0aGluIE1CT05FRC4gJm5ic3A7V2Ugd291bGQgbGlr
ZSB0byBoZWFyIGFuc3dlcnMgZnJvbSB0aGUgV0cgdG8gdGhlIGZvbGxvd2luZyBxdWVzdGlvbnMg
YmVmb3JlIGNvbnRpbnVpbmcgYW55IHdvcmsgb24gbXVsdGljYXN0IHRyYW5zaXRpb24gaW4gTUJP
TkVEOjxicj48YnI+MSkgV2hpY2ggb3BlcmF0b3JzIGludGVuZCB0byBzb3VyY2UgbXVsdGljYXN0
IHRyYWZmaWMgZnJvbSBvbmUgSVAgdmVyc2lvbiBhbmQgcmVjZWl2ZSBpdCBvdmVyIGFub3RoZXIg
SVAgdmVyc2lvbj88YnI+PGJyPjIpIEZvciB0aG9zZSB3aG8gYW5zd2VyIDEpLCBwbGVhc2UgaWRl
bnRpZnkgdGhlIHVzZS1jYXNlcyBvZiBpbnRlcmVzdCBpbiBkcmFmdC1pZXRmLW1ib25lZC12NHY2
LW1jYXN0LXBzIHNvIHdlIGNhbiBsaW1pdCBkaXNjdXNzaW9uIHRvIHNvbHV0aW9ucyBmb3IgdGhv
c2UgdXNlIGNhc2VzLjxicj48YnI+PGJyPk1CT05FRCBDaGFpcnM8YnI+X19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+TUJPTkVEIG1haWxpbmcgbGlzdDxi
cj48YSBocmVmPSJtYWlsdG86TUJPTkVEQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+TUJPTkVE
QGlldGYub3JnPC9hPjxicj48YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL21ib25lZCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vbWJvbmVkPC9hPjxvOnA+PC9vOnA+PC9wPjwvZGl2PjxwIGNsYXNzPU1zb05v
cm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8nPiZuYnNwOzxvOnA+PC9vOnA+PC9wPjwvZGl2PjwvZGl2PjwvZGl2PjwvZGl2PjwvZGl2
PjwvZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD48L2Rpdj48L2Rp
dj48L2JvZHk+PC9odG1sPg==

--_000_13205C286662DE4387D9AF3AC30EF456D76ECA6070EMBX01WFjnprn_--

From bingxuere@gmail.com  Wed Jun 20 03:23:23 2012
Return-Path: <bingxuere@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F44A21F86E8 for <mboned@ietfa.amsl.com>; Wed, 20 Jun 2012 03:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.32
X-Spam-Level: 
X-Spam-Status: No, score=-3.32 tagged_above=-999 required=5 tests=[AWL=0.278,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 bZPaCbO2xvNU for <mboned@ietfa.amsl.com>; Wed, 20 Jun 2012 03:23:22 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1D6CF21F86CB for <mboned@ietf.org>; Wed, 20 Jun 2012 03:23:22 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so6041171ghb.31 for <mboned@ietf.org>; Wed, 20 Jun 2012 03:23:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=lN7K/4h1J/C2lAbflK/QjWw0o2XdNbW87JZ6lHZWGZE=; b=VCPrib4q23SuEFed1ARFlqsrMcpkWY8iKGMtwY92+bMii5RenRMOi17HCtNGl2twWL NR42vQkPg284iz/AHf9juRTglMTYXGlgusIOSd1pbhLo9zvX48DakzdBeb3oU8GifjRi UyulNuJi/61Uks3dK4MEa1A+9JmoOY/xSBgDbuVgoBfblbS5d4WueBBCIGGWSaYpHrVp VXG806x12Y7+06XroOggmlIThLLwx7rPqye6k77eI5SfKFtGC1u3diz64tgP2/RRiQp1 6K3KYqHaUXzFCbvb2PMPAaMH9H0hrIXXBq+GPiV0wi1ZJKl9afWo+qydHPRc1FR0+sff cVcA==
Received: by 10.50.192.199 with SMTP id hi7mr4005290igc.54.1340187801219; Wed, 20 Jun 2012 03:23:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.46.6 with HTTP; Wed, 20 Jun 2012 03:22:41 -0700 (PDT)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net>
From: Qiong <bingxuere@gmail.com>
Date: Wed, 20 Jun 2012 18:22:41 +0800
Message-ID: <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: multipart/alternative; boundary=14dae9340ffbd2f2b304c2e4c9d3
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 10:23:23 -0000

--14dae9340ffbd2f2b304c2e4c9d3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Ronald,

For your question, it would be too difficult to give you an acurate number
of money/effort, but I can tell you our situation of network upgradation.

In the transition period, it would be impossible to replace all the legacy
IPv4-only devices, especially a great many access network devices. So
actually, the process would be taken firstly towards our customers and new
region. For example, a new customer might get a new  STB with IPv6
functionality. However, this new customer might access some region only
with old devices, then at that time, it will be of great help to implement
some MLTRANS solutions in the new STB or deploy limited devices in the
network. I believe this will cost less than upgrading the whole network in
the first place.

For old customers, they will still use IPv4 as they already got address,
unless we upgrade their STB to support IPv6 remotely. But it is not the
first priority point.

Best wishes
Qiong

On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica <rbonica@juniper.net> wrote:

> Qiong,****
>
> ** **
>
> Which of the following do you think will require more money/effort:****
>
> ** **
>
> **-          **To deploy IPv6 multicast throughout your network****
>
> **-          **To deploy the MLTRANS mechanisms that you will require to
> compensate for the lack the above mentioned capability****
>
> ** **
>
> How much more money/effort? Why?****
>
> ** **
>
>                                                  Ron****
>
> ** **
>
> ** **
>
> *From:* Qiong [mailto:bingxuere@gmail.com]
> *Sent:* Monday, June 18, 2012 10:03 PM
> *To:* Ronald Bonica
> *Cc:* Lenny Giuliano; MBONED WG
>
> *Subject:* Re: [MBONED] Multicast transition work in MBONED****
>
> ** **
>
> Hi Ronald,
>
> I agree we do would like to enable IPv6 multicast in our network. However=
,
> all these things can not be achieved within one night. We still have a lo=
t
> of old devices which can not support IPv6 multicast in our network, but w=
e
> are running out of IPv4 address right now. So we can not wait until the
> whole network is ready for IPv6 multicast.
>
> Hope it clarifies.
>
> Best wishes
> Qiong****
>
> On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica <rbonica@juniper.net>
> wrote:****
>
> Hi Qiong,****
>
>  ****
>
> If you were to enable IPv6 multicast throughout your network before
> deploying IPv6 only receivers, would you not fall into use cases 3.4 and
> 3.5 (the dual stack scenarios). Since you are going to have to enable IPv=
6
> multicast throughout your network anyway, wouldn=E2=80=99t it be a good i=
dea to do
> so sooner than later? ****
>
>  ****
>
>                                                                       Ron=
*
> ***
>
>  ****
>
> *From:* Qiong [mailto:bingxuere@gmail.com]
> *Sent:* Tuesday, June 12, 2012 10:11 AM
> *To:* Lenny Giuliano
> *Cc:* MBONED WG; Ronald Bonica****
>
>
> *Subject:* Re: [MBONED] Multicast transition work in MBONED****
>
>  ****
>
> Dear all,****
>
>
>
> 1. In our situation, the source may still remian in IPv4, while the
> receiver will be IPv6-only since there is no more IPv4 address anymore.
> However, the network might be IPv4-only, which can not support IPv6
> multicast yet; or the network can support IPv6 multicast. This is the cas=
e
> of 6-4.
> Another situation is: the access network is still IPv4-only, and the core
> netowrk (or application platform) is IPv6, then that is the case of 6-4-6=
-4.
>
> 2. Use case: 3.2, 3.4,
>
> Best wishes
> Qiong****
>
> On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <lenny@juniper.net>
> wrote:****
>
>
> The multicast transition work within MBONED was initially intended to
> consist of ~ 3 document with limited scope.  In a very short amount of
> time, we've seen 7 drafts (and counting) with scope widening.
>
> In order to make sure we are focusing on work that is of actual value to
> the community and prevent a flood of high volume/low value drafts, we wou=
ld
> like to revisit the basic questions of multicast transition within MBONED=
.
>  We would like to hear answers from the WG to the following questions
> before continuing any work on multicast transition in MBONED:
>
> 1) Which operators intend to source multicast traffic from one IP version
> and receive it over another IP version?
>
> 2) For those who answer 1), please identify the use-cases of interest in
> draft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions f=
or
> those use cases.
>
>
> MBONED Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned****
>
>  ****
>
> ** **
>

--14dae9340ffbd2f2b304c2e4c9d3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Ronald,<br><br>For your question, it would be too difficult to give you =
an acurate number of money/effort, but I can tell you our situation of netw=
ork upgradation. <br><br>In the transition period, it would be impossible t=
o replace all the legacy IPv4-only devices, especially a great many access =
network devices. So actually, the process would be taken firstly towards ou=
r customers and new region. For example, a new customer might get a new=C2=
=A0 STB with IPv6 functionality. However, this new customer might access so=
me region only with old devices, then at that time, it will be of great hel=
p to implement some MLTRANS solutions in the new STB or deploy limited devi=
ces in the network. I believe this will cost less than upgrading the whole =
network in the first place. <br>

<br>For old customers, they will still use IPv4 as they already got address=
, unless we upgrade their STB to support IPv6 remotely. But it is not the f=
irst priority point.<br><br>Best wishes<br>Qiong<br><br><div class=3D"gmail=
_quote">

On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:rbonica@juniper.net" target=3D"_blank">rbonica@juniper.net</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d">Qiong,<u></u><u></u></span></p><p class=3D"M=
soNormal">

<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNo=
rmal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1f497d">Which of the following do you think will r=
equire more money/effort:<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:#1f497d"><span>-<span style=3D"font:7.0pt=
 &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 </span></span></span><u></u><span style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">To deploy =
IPv6 multicast throughout your network<u></u><u></u></span></p>

<p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><span>-<span style=3D"font:7.0pt &quot=
;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 </span></span></span><u></u><span style=3D"font-size:11.0pt;font-family=
:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">To deploy the ML=
TRANS mechanisms that you will require to compensate for the lack the above=
 mentioned capability<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">How much more money=
/effort? Why?<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Ron<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u=
></span></p>

<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b>=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"> Qiong [mailto:<a href=3D"mailto:bingxuere@gmail.com" target=3D=
"_blank">bingxuere@gmail.com</a>] <br>

<b>Sent:</b> Monday, June 18, 2012 10:03 PM<br><b>To:</b> Ronald Bonica<br>=
<b>Cc:</b> Lenny Giuliano; MBONED WG</span></p><div><div class=3D"h5"><br><=
b>Subject:</b> Re: [MBONED] Multicast transition work in MBONED<u></u><u></=
u></div>

</div><p></p></div></div><div><div class=3D"h5"><p class=3D"MsoNormal"><u><=
/u>=C2=A0<u></u></p><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">H=
i Ronald,<br><br>I agree we do would like to enable IPv6 multicast in our n=
etwork. However, all these things can not be achieved within one night. We =
still have a lot of old devices which can not support IPv6 multicast in our=
 network, but we are running out of IPv4 address right now. So we can not w=
ait until the whole network is ready for IPv6 multicast.<br>

<br>Hope it clarifies.<br><br>Best wishes<br>Qiong<u></u><u></u></p><div><p=
 class=3D"MsoNormal">On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica &lt;<a=
 href=3D"mailto:rbonica@juniper.net" target=3D"_blank">rbonica@juniper.net<=
/a>&gt; wrote:<u></u><u></u></p>

<div><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Qiong,</span=
><u></u><u></u></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=
</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If you were to enable IPv=
6 multicast throughout your network before deploying IPv6 only receivers, w=
ould you not fall into use cases 3.4 and 3.5 (the dual stack scenarios). Si=
nce you are going to have to enable IPv6 multicast throughout your network =
anyway, wouldn=E2=80=99t it be a good idea to do so sooner than later? </sp=
an><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Ron</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p><div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0i=
n 0in 4.0pt">

<div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt=
 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span s=
tyle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&qu=
ot;"> Qiong [mailto:<a href=3D"mailto:bingxuere@gmail.com" target=3D"_blank=
">bingxuere@gmail.com</a>] <br>

<b>Sent:</b> Tuesday, June 12, 2012 10:11 AM<br><b>To:</b> Lenny Giuliano<b=
r><b>Cc:</b> MBONED WG; Ronald Bonica</span><u></u><u></u></p><div><p class=
=3D"MsoNormal"><br><b>Subject:</b> Re: [MBONED] Multicast transition work i=
n MBONED<u></u><u></u></p>

</div></div></div><p class=3D"MsoNormal">=C2=A0<u></u><u></u></p><p class=
=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Dear all,<u></u><u></u></p><d=
iv><div><p class=3D"MsoNormal"><br><br>1. In our situation, the source may =
still remian in IPv4, while the receiver will be IPv6-only since there is n=
o more IPv4 address anymore. However, the network might be IPv4-only, which=
 can not support IPv6 multicast yet; or the network can support IPv6 multic=
ast. This is the case of 6-4. <br>

Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.=
<br><br>2. Use case: 3.2, 3.4,<br><br>Best wishes<br>Qiong<u></u><u></u></p=
>

</div></div><div><div><div><p class=3D"MsoNormal">On Fri, Jun 8, 2012 at 4:=
34 AM, Leonard Giuliano &lt;<a href=3D"mailto:lenny@juniper.net" target=3D"=
_blank">lenny@juniper.net</a>&gt; wrote:<u></u><u></u></p><p class=3D"MsoNo=
rmal">

<br>The multicast transition work within MBONED was initially intended to c=
onsist of ~ 3 document with limited scope. =C2=A0In a very short amount of =
time, we&#39;ve seen 7 drafts (and counting) with scope widening.<br><br>In=
 order to make sure we are focusing on work that is of actual value to the =
community and prevent a flood of high volume/low value drafts, we would lik=
e to revisit the basic questions of multicast transition within MBONED. =C2=
=A0We would like to hear answers from the WG to the following questions bef=
ore continuing any work on multicast transition in MBONED:<br>

<br>1) Which operators intend to source multicast traffic from one IP versi=
on and receive it over another IP version?<br><br>2) For those who answer 1=
), please identify the use-cases of interest in draft-ietf-mboned-v4v6-mcas=
t-ps so we can limit discussion to solutions for those use cases.<br>

<br><br>MBONED Chairs<br>_______________________________________________<br=
>MBONED mailing list<br><a href=3D"mailto:MBONED@ietf.org" target=3D"_blank=
">MBONED@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/m=
boned" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mboned</a><u=
></u><u></u></p>

</div><p class=3D"MsoNormal">=C2=A0<u></u><u></u></p></div></div></div></di=
v></div></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div></div></=
div></div></div></blockquote></div><br>

--14dae9340ffbd2f2b304c2e4c9d3--

From rbonica@juniper.net  Thu Jun 21 09:15:52 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49F9021F867E for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 09:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level: 
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 cI31Y1Mt35ho for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 09:15:51 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 4E1D221F8659 for <mboned@ietf.org>; Thu, 21 Jun 2012 09:15:50 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKT+NItC8Df0kIHz+65q0BGPzAKewEbSuK@postini.com; Thu, 21 Jun 2012 09:15:50 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 21 Jun 2012 09:14:57 -0700
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 21 Jun 2012 09:14:56 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Thu, 21 Jun 2012 12:14:52 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Qiong <bingxuere@gmail.com>
Date: Thu, 21 Jun 2012 12:14:50 -0400
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: Ac1OzrlyZvP6GwnYQH2TABgP0b2djgA+CjdQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net> <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com>
In-Reply-To: <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_13205C286662DE4387D9AF3AC30EF456D76EDCE3CAEMBX01WFjnprn_"
MIME-Version: 1.0
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 16:15:52 -0000

--_000_13205C286662DE4387D9AF3AC30EF456D76EDCE3CAEMBX01WFjnprn_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

Rm9sa3MsDQoNClNvIGl0IGxvb2tzIGxpa2UgdXNlLWNhc2VzIDMuMiwgMy40IGFuZCAzLjUgbWF5
IHNlZSBkZXBsb3ltZW50LiBUaGVyZSB3ZXJlIG5vIHRha2VycyBmb3IgdXNlLWNhc2VzIDMuMSBh
bmQgMy4zLg0KDQpJbiBodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvbWJvbmVk
L2N1cnJlbnQvbXNnMDE2MDcuaHRtbCwgU2ltb24gUGVycmF1bHQgc3VnZ2VzdHMgdHdvIHNvbHV0
aW9ucyBmb3IgMy40IGFuZCAzLjUuIERvZXMgdGhlIFdHIGFncmVlIHRoYXQgdGhvc2UgYXJlIHRo
ZSBzb2x1dGlvbnMgdGhhdCB3ZSBzaG91bGQgcnVuIHdpdGg/DQoNClNpbW9u4oCZcyBzb2x1dGlv
bnMgY2FuIGFsc28gYmUgYXBwbGllZCB0byB1c2UtY2FzZSAzLjIgaWYgd2UgdHVubmVsIG92ZXIg
bm9uLW11bHRpY2FzdCBlbmFibGVkIElQdjQgc2VnbWVudC4gRG9lcyBldmVyeW9uZSBhZ3JlZSB0
aGF0IHRoYXQgaXMgYSBnb29kIGlkZWE/DQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICBSb24NCg0KRnJvbTogUWlvbmcgW21haWx0bzpiaW5neHVl
cmVAZ21haWwuY29tXQ0KU2VudDogV2VkbmVzZGF5LCBKdW5lIDIwLCAyMDEyIDY6MjMgQU0NClRv
OiBSb25hbGQgQm9uaWNhDQpDYzogTGVubnkgR2l1bGlhbm87IE1CT05FRCBXRw0KU3ViamVjdDog
UmU6IFtNQk9ORURdIE11bHRpY2FzdCB0cmFuc2l0aW9uIHdvcmsgaW4gTUJPTkVEDQoNCkhpIFJv
bmFsZCwNCg0KRm9yIHlvdXIgcXVlc3Rpb24sIGl0IHdvdWxkIGJlIHRvbyBkaWZmaWN1bHQgdG8g
Z2l2ZSB5b3UgYW4gYWN1cmF0ZSBudW1iZXIgb2YgbW9uZXkvZWZmb3J0LCBidXQgSSBjYW4gdGVs
bCB5b3Ugb3VyIHNpdHVhdGlvbiBvZiBuZXR3b3JrIHVwZ3JhZGF0aW9uLg0KDQpJbiB0aGUgdHJh
bnNpdGlvbiBwZXJpb2QsIGl0IHdvdWxkIGJlIGltcG9zc2libGUgdG8gcmVwbGFjZSBhbGwgdGhl
IGxlZ2FjeSBJUHY0LW9ubHkgZGV2aWNlcywgZXNwZWNpYWxseSBhIGdyZWF0IG1hbnkgYWNjZXNz
IG5ldHdvcmsgZGV2aWNlcy4gU28gYWN0dWFsbHksIHRoZSBwcm9jZXNzIHdvdWxkIGJlIHRha2Vu
IGZpcnN0bHkgdG93YXJkcyBvdXIgY3VzdG9tZXJzIGFuZCBuZXcgcmVnaW9uLiBGb3IgZXhhbXBs
ZSwgYSBuZXcgY3VzdG9tZXIgbWlnaHQgZ2V0IGEgbmV3ICBTVEIgd2l0aCBJUHY2IGZ1bmN0aW9u
YWxpdHkuIEhvd2V2ZXIsIHRoaXMgbmV3IGN1c3RvbWVyIG1pZ2h0IGFjY2VzcyBzb21lIHJlZ2lv
biBvbmx5IHdpdGggb2xkIGRldmljZXMsIHRoZW4gYXQgdGhhdCB0aW1lLCBpdCB3aWxsIGJlIG9m
IGdyZWF0IGhlbHAgdG8gaW1wbGVtZW50IHNvbWUgTUxUUkFOUyBzb2x1dGlvbnMgaW4gdGhlIG5l
dyBTVEIgb3IgZGVwbG95IGxpbWl0ZWQgZGV2aWNlcyBpbiB0aGUgbmV0d29yay4gSSBiZWxpZXZl
IHRoaXMgd2lsbCBjb3N0IGxlc3MgdGhhbiB1cGdyYWRpbmcgdGhlIHdob2xlIG5ldHdvcmsgaW4g
dGhlIGZpcnN0IHBsYWNlLg0KDQpGb3Igb2xkIGN1c3RvbWVycywgdGhleSB3aWxsIHN0aWxsIHVz
ZSBJUHY0IGFzIHRoZXkgYWxyZWFkeSBnb3QgYWRkcmVzcywgdW5sZXNzIHdlIHVwZ3JhZGUgdGhl
aXIgU1RCIHRvIHN1cHBvcnQgSVB2NiByZW1vdGVseS4gQnV0IGl0IGlzIG5vdCB0aGUgZmlyc3Qg
cHJpb3JpdHkgcG9pbnQuDQoNCkJlc3Qgd2lzaGVzDQpRaW9uZw0KT24gV2VkLCBKdW4gMjAsIDIw
MTIgYXQgNDo0OCBQTSwgUm9uYWxkIEJvbmljYSA8cmJvbmljYUBqdW5pcGVyLm5ldDxtYWlsdG86
cmJvbmljYUBqdW5pcGVyLm5ldD4+IHdyb3RlOg0KUWlvbmcsDQoNCldoaWNoIG9mIHRoZSBmb2xs
b3dpbmcgZG8geW91IHRoaW5rIHdpbGwgcmVxdWlyZSBtb3JlIG1vbmV5L2VmZm9ydDoNCg0KDQot
ICAgICAgICAgIFRvIGRlcGxveSBJUHY2IG11bHRpY2FzdCB0aHJvdWdob3V0IHlvdXIgbmV0d29y
aw0KDQotICAgICAgICAgIFRvIGRlcGxveSB0aGUgTUxUUkFOUyBtZWNoYW5pc21zIHRoYXQgeW91
IHdpbGwgcmVxdWlyZSB0byBjb21wZW5zYXRlIGZvciB0aGUgbGFjayB0aGUgYWJvdmUgbWVudGlv
bmVkIGNhcGFiaWxpdHkNCg0KSG93IG11Y2ggbW9yZSBtb25leS9lZmZvcnQ/IFdoeT8NCg0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFJvbg0KDQoNCkZy
b206IFFpb25nIFttYWlsdG86YmluZ3h1ZXJlQGdtYWlsLmNvbTxtYWlsdG86YmluZ3h1ZXJlQGdt
YWlsLmNvbT5dDQpTZW50OiBNb25kYXksIEp1bmUgMTgsIDIwMTIgMTA6MDMgUE0NClRvOiBSb25h
bGQgQm9uaWNhDQpDYzogTGVubnkgR2l1bGlhbm87IE1CT05FRCBXRw0KDQpTdWJqZWN0OiBSZTog
W01CT05FRF0gTXVsdGljYXN0IHRyYW5zaXRpb24gd29yayBpbiBNQk9ORUQNCg0KSGkgUm9uYWxk
LA0KDQpJIGFncmVlIHdlIGRvIHdvdWxkIGxpa2UgdG8gZW5hYmxlIElQdjYgbXVsdGljYXN0IGlu
IG91ciBuZXR3b3JrLiBIb3dldmVyLCBhbGwgdGhlc2UgdGhpbmdzIGNhbiBub3QgYmUgYWNoaWV2
ZWQgd2l0aGluIG9uZSBuaWdodC4gV2Ugc3RpbGwgaGF2ZSBhIGxvdCBvZiBvbGQgZGV2aWNlcyB3
aGljaCBjYW4gbm90IHN1cHBvcnQgSVB2NiBtdWx0aWNhc3QgaW4gb3VyIG5ldHdvcmssIGJ1dCB3
ZSBhcmUgcnVubmluZyBvdXQgb2YgSVB2NCBhZGRyZXNzIHJpZ2h0IG5vdy4gU28gd2UgY2FuIG5v
dCB3YWl0IHVudGlsIHRoZSB3aG9sZSBuZXR3b3JrIGlzIHJlYWR5IGZvciBJUHY2IG11bHRpY2Fz
dC4NCg0KSG9wZSBpdCBjbGFyaWZpZXMuDQoNCkJlc3Qgd2lzaGVzDQpRaW9uZw0KT24gTW9uLCBK
dW4gMTgsIDIwMTIgYXQgMTE6MDcgUE0sIFJvbmFsZCBCb25pY2EgPHJib25pY2FAanVuaXBlci5u
ZXQ8bWFpbHRvOnJib25pY2FAanVuaXBlci5uZXQ+PiB3cm90ZToNCkhpIFFpb25nLA0KDQpJZiB5
b3Ugd2VyZSB0byBlbmFibGUgSVB2NiBtdWx0aWNhc3QgdGhyb3VnaG91dCB5b3VyIG5ldHdvcmsg
YmVmb3JlIGRlcGxveWluZyBJUHY2IG9ubHkgcmVjZWl2ZXJzLCB3b3VsZCB5b3Ugbm90IGZhbGwg
aW50byB1c2UgY2FzZXMgMy40IGFuZCAzLjUgKHRoZSBkdWFsIHN0YWNrIHNjZW5hcmlvcykuIFNp
bmNlIHlvdSBhcmUgZ29pbmcgdG8gaGF2ZSB0byBlbmFibGUgSVB2NiBtdWx0aWNhc3QgdGhyb3Vn
aG91dCB5b3VyIG5ldHdvcmsgYW55d2F5LCB3b3VsZG7igJl0IGl0IGJlIGEgZ29vZCBpZGVhIHRv
IGRvIHNvIHNvb25lciB0aGFuIGxhdGVyPw0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUm9uDQoNCkZyb206IFFp
b25nIFttYWlsdG86YmluZ3h1ZXJlQGdtYWlsLmNvbTxtYWlsdG86YmluZ3h1ZXJlQGdtYWlsLmNv
bT5dDQpTZW50OiBUdWVzZGF5LCBKdW5lIDEyLCAyMDEyIDEwOjExIEFNDQpUbzogTGVubnkgR2l1
bGlhbm8NCkNjOiBNQk9ORUQgV0c7IFJvbmFsZCBCb25pY2ENCg0KU3ViamVjdDogUmU6IFtNQk9O
RURdIE11bHRpY2FzdCB0cmFuc2l0aW9uIHdvcmsgaW4gTUJPTkVEDQoNCkRlYXIgYWxsLA0KDQoN
CjEuIEluIG91ciBzaXR1YXRpb24sIHRoZSBzb3VyY2UgbWF5IHN0aWxsIHJlbWlhbiBpbiBJUHY0
LCB3aGlsZSB0aGUgcmVjZWl2ZXIgd2lsbCBiZSBJUHY2LW9ubHkgc2luY2UgdGhlcmUgaXMgbm8g
bW9yZSBJUHY0IGFkZHJlc3MgYW55bW9yZS4gSG93ZXZlciwgdGhlIG5ldHdvcmsgbWlnaHQgYmUg
SVB2NC1vbmx5LCB3aGljaCBjYW4gbm90IHN1cHBvcnQgSVB2NiBtdWx0aWNhc3QgeWV0OyBvciB0
aGUgbmV0d29yayBjYW4gc3VwcG9ydCBJUHY2IG11bHRpY2FzdC4gVGhpcyBpcyB0aGUgY2FzZSBv
ZiA2LTQuDQpBbm90aGVyIHNpdHVhdGlvbiBpczogdGhlIGFjY2VzcyBuZXR3b3JrIGlzIHN0aWxs
IElQdjQtb25seSwgYW5kIHRoZSBjb3JlIG5ldG93cmsgKG9yIGFwcGxpY2F0aW9uIHBsYXRmb3Jt
KSBpcyBJUHY2LCB0aGVuIHRoYXQgaXMgdGhlIGNhc2Ugb2YgNi00LTYtNC4NCg0KMi4gVXNlIGNh
c2U6IDMuMiwgMy40LA0KDQpCZXN0IHdpc2hlcw0KUWlvbmcNCk9uIEZyaSwgSnVuIDgsIDIwMTIg
YXQgNDozNCBBTSwgTGVvbmFyZCBHaXVsaWFubyA8bGVubnlAanVuaXBlci5uZXQ8bWFpbHRvOmxl
bm55QGp1bmlwZXIubmV0Pj4gd3JvdGU6DQoNClRoZSBtdWx0aWNhc3QgdHJhbnNpdGlvbiB3b3Jr
IHdpdGhpbiBNQk9ORUQgd2FzIGluaXRpYWxseSBpbnRlbmRlZCB0byBjb25zaXN0IG9mIH4gMyBk
b2N1bWVudCB3aXRoIGxpbWl0ZWQgc2NvcGUuICBJbiBhIHZlcnkgc2hvcnQgYW1vdW50IG9mIHRp
bWUsIHdlJ3ZlIHNlZW4gNyBkcmFmdHMgKGFuZCBjb3VudGluZykgd2l0aCBzY29wZSB3aWRlbmlu
Zy4NCg0KSW4gb3JkZXIgdG8gbWFrZSBzdXJlIHdlIGFyZSBmb2N1c2luZyBvbiB3b3JrIHRoYXQg
aXMgb2YgYWN0dWFsIHZhbHVlIHRvIHRoZSBjb21tdW5pdHkgYW5kIHByZXZlbnQgYSBmbG9vZCBv
ZiBoaWdoIHZvbHVtZS9sb3cgdmFsdWUgZHJhZnRzLCB3ZSB3b3VsZCBsaWtlIHRvIHJldmlzaXQg
dGhlIGJhc2ljIHF1ZXN0aW9ucyBvZiBtdWx0aWNhc3QgdHJhbnNpdGlvbiB3aXRoaW4gTUJPTkVE
LiAgV2Ugd291bGQgbGlrZSB0byBoZWFyIGFuc3dlcnMgZnJvbSB0aGUgV0cgdG8gdGhlIGZvbGxv
d2luZyBxdWVzdGlvbnMgYmVmb3JlIGNvbnRpbnVpbmcgYW55IHdvcmsgb24gbXVsdGljYXN0IHRy
YW5zaXRpb24gaW4gTUJPTkVEOg0KDQoxKSBXaGljaCBvcGVyYXRvcnMgaW50ZW5kIHRvIHNvdXJj
ZSBtdWx0aWNhc3QgdHJhZmZpYyBmcm9tIG9uZSBJUCB2ZXJzaW9uIGFuZCByZWNlaXZlIGl0IG92
ZXIgYW5vdGhlciBJUCB2ZXJzaW9uPw0KDQoyKSBGb3IgdGhvc2Ugd2hvIGFuc3dlciAxKSwgcGxl
YXNlIGlkZW50aWZ5IHRoZSB1c2UtY2FzZXMgb2YgaW50ZXJlc3QgaW4gZHJhZnQtaWV0Zi1tYm9u
ZWQtdjR2Ni1tY2FzdC1wcyBzbyB3ZSBjYW4gbGltaXQgZGlzY3Vzc2lvbiB0byBzb2x1dGlvbnMg
Zm9yIHRob3NlIHVzZSBjYXNlcy4NCg0KDQpNQk9ORUQgQ2hhaXJzDQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KTUJPTkVEIG1haWxpbmcgbGlzdA0KTUJP
TkVEQGlldGYub3JnPG1haWx0bzpNQk9ORURAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL21ib25lZA0KDQoNCg0K

--_000_13205C286662DE4387D9AF3AC30EF456D76EDCE3CAEMBX01WFjnprn_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0
aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQt
ZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYi
O30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNw
YW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y
OnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnANCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQt
c2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpw
Lk1zb0FjZXRhdGUsIGxpLk1zb0FjZXRhdGUsIGRpdi5Nc29BY2V0YXRlDQoJe21zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1hcmdp
bjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTo4LjBwdDsNCglmb250
LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5CYWxsb29uVGV4dENoYXINCgl7
bXNvLXN0eWxlLW5hbWU6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4dCI7DQoJZm9udC1mYW1pbHk6IlRhaG9t
YSIsInNhbnMtc2VyaWYiO30NCnNwYW4uRW1haWxTdHlsZTIwDQoJe21zby1zdHlsZS10eXBlOnBl
cnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29s
b3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25s
eTt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEu
MGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2Vj
dGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVm
YXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxv
OmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwh
W2VuZGlmXS0tPjwvaGVhZD48Ym9keSBsYW5nPUVOLVVTIGxpbms9Ymx1ZSB2bGluaz1wdXJwbGU+
PGRpdiBjbGFzcz1Xb3JkU2VjdGlvbjE+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6
IzFGNDk3RCc+Rm9sa3MsPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48
c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt
c2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFz
cz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNh
bGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5TbyBpdCBsb29rcyBsaWtlIHVzZS1j
YXNlcyAzLjIsIDMuNCBhbmQgMy41IG1heSBzZWUgZGVwbG95bWVudC4gVGhlcmUgd2VyZSBubyB0
YWtlcnMgZm9yIHVzZS1jYXNlcyAzLjEgYW5kIDMuMy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAg
Y2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkluIDxh
IGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9tYm9uZWQvY3VycmVu
dC9tc2cwMTYwNy5odG1sIj5odHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvbWJv
bmVkL2N1cnJlbnQvbXNnMDE2MDcuaHRtbDwvYT4sIFNpbW9uIFBlcnJhdWx0IHN1Z2dlc3RzIHR3
byBzb2x1dGlvbnMgZm9yIDMuNCBhbmQgMy41LiBEb2VzIHRoZSBXRyBhZ3JlZSB0aGF0IHRob3Nl
IGFyZSB0aGUgc29sdXRpb25zIHRoYXQgd2Ugc2hvdWxkIHJ1biB3aXRoPzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFG
NDk3RCc+U2ltb27igJlzIHNvbHV0aW9ucyBjYW4gYWxzbyBiZSBhcHBsaWVkIHRvIHVzZS1jYXNl
IDMuMiBpZiB3ZSB0dW5uZWwgb3ZlciBub24tbXVsdGljYXN0IGVuYWJsZWQgSVB2NCBzZWdtZW50
LiBEb2VzIGV2ZXJ5b25lIGFncmVlIHRoYXQgdGhhdCBpcyBhIGdvb2QgaWRlYT88bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0n
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9y
OiMxRjQ5N0QnPsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqBS
b248bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6
IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxkaXYgc3R5bGU9J2JvcmRlcjpu
b25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBw
dCc+PGRpdj48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYg
MS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbic+PHAgY2xhc3M9TXNvTm9ybWFsPjxiPjxz
cGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNl
cmlmIic+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIic+IFFpb25nIFttYWlsdG86YmluZ3h1ZXJlQGdt
YWlsLmNvbV0gPGJyPjxiPlNlbnQ6PC9iPiBXZWRuZXNkYXksIEp1bmUgMjAsIDIwMTIgNjoyMyBB
TTxicj48Yj5Ubzo8L2I+IFJvbmFsZCBCb25pY2E8YnI+PGI+Q2M6PC9iPiBMZW5ueSBHaXVsaWFu
bzsgTUJPTkVEIFdHPGJyPjxiPlN1YmplY3Q6PC9iPiBSZTogW01CT05FRF0gTXVsdGljYXN0IHRy
YW5zaXRpb24gd29yayBpbiBNQk9ORUQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PC9kaXY+
PHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1h
bCBzdHlsZT0nbWFyZ2luLWJvdHRvbToxMi4wcHQnPkhpIFJvbmFsZCw8YnI+PGJyPkZvciB5b3Vy
IHF1ZXN0aW9uLCBpdCB3b3VsZCBiZSB0b28gZGlmZmljdWx0IHRvIGdpdmUgeW91IGFuIGFjdXJh
dGUgbnVtYmVyIG9mIG1vbmV5L2VmZm9ydCwgYnV0IEkgY2FuIHRlbGwgeW91IG91ciBzaXR1YXRp
b24gb2YgbmV0d29yayB1cGdyYWRhdGlvbi4gPGJyPjxicj5JbiB0aGUgdHJhbnNpdGlvbiBwZXJp
b2QsIGl0IHdvdWxkIGJlIGltcG9zc2libGUgdG8gcmVwbGFjZSBhbGwgdGhlIGxlZ2FjeSBJUHY0
LW9ubHkgZGV2aWNlcywgZXNwZWNpYWxseSBhIGdyZWF0IG1hbnkgYWNjZXNzIG5ldHdvcmsgZGV2
aWNlcy4gU28gYWN0dWFsbHksIHRoZSBwcm9jZXNzIHdvdWxkIGJlIHRha2VuIGZpcnN0bHkgdG93
YXJkcyBvdXIgY3VzdG9tZXJzIGFuZCBuZXcgcmVnaW9uLiBGb3IgZXhhbXBsZSwgYSBuZXcgY3Vz
dG9tZXIgbWlnaHQgZ2V0IGEgbmV3Jm5ic3A7IFNUQiB3aXRoIElQdjYgZnVuY3Rpb25hbGl0eS4g
SG93ZXZlciwgdGhpcyBuZXcgY3VzdG9tZXIgbWlnaHQgYWNjZXNzIHNvbWUgcmVnaW9uIG9ubHkg
d2l0aCBvbGQgZGV2aWNlcywgdGhlbiBhdCB0aGF0IHRpbWUsIGl0IHdpbGwgYmUgb2YgZ3JlYXQg
aGVscCB0byBpbXBsZW1lbnQgc29tZSBNTFRSQU5TIHNvbHV0aW9ucyBpbiB0aGUgbmV3IFNUQiBv
ciBkZXBsb3kgbGltaXRlZCBkZXZpY2VzIGluIHRoZSBuZXR3b3JrLiBJIGJlbGlldmUgdGhpcyB3
aWxsIGNvc3QgbGVzcyB0aGFuIHVwZ3JhZGluZyB0aGUgd2hvbGUgbmV0d29yayBpbiB0aGUgZmly
c3QgcGxhY2UuIDxicj48YnI+Rm9yIG9sZCBjdXN0b21lcnMsIHRoZXkgd2lsbCBzdGlsbCB1c2Ug
SVB2NCBhcyB0aGV5IGFscmVhZHkgZ290IGFkZHJlc3MsIHVubGVzcyB3ZSB1cGdyYWRlIHRoZWly
IFNUQiB0byBzdXBwb3J0IElQdjYgcmVtb3RlbHkuIEJ1dCBpdCBpcyBub3QgdGhlIGZpcnN0IHBy
aW9yaXR5IHBvaW50Ljxicj48YnI+QmVzdCB3aXNoZXM8YnI+UWlvbmc8bzpwPjwvbzpwPjwvcD48
ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD5PbiBXZWQsIEp1biAyMCwgMjAxMiBhdCA0OjQ4IFBNLCBS
b25hbGQgQm9uaWNhICZsdDs8YSBocmVmPSJtYWlsdG86cmJvbmljYUBqdW5pcGVyLm5ldCIgdGFy
Z2V0PSJfYmxhbmsiPnJib25pY2FAanVuaXBlci5uZXQ8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpw
PjwvcD48ZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdE
Jz5RaW9uZyw8L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4g
c3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
Ijtjb2xvcjojMUY0OTdEJz4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNv
Tm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5XaGljaCBvZiB0aGUgZm9sbG93aW5nIGRv
IHlvdSB0aGluayB3aWxsIHJlcXVpcmUgbW9yZSBtb25leS9lZmZvcnQ6PC9zcGFuPjxvOnA+PC9v
OnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8nPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+Jm5ic3A7
PC9zcGFuPjxvOnA+PC9vOnA+PC9wPjxwPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+LTwvc3Bhbj48
c3BhbiBzdHlsZT0nZm9udC1zaXplOjcuMHB0O2NvbG9yOiMxRjQ5N0QnPiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtj
b2xvcjojMUY0OTdEJz5UbyBkZXBsb3kgSVB2NiBtdWx0aWNhc3QgdGhyb3VnaG91dCB5b3VyIG5l
dHdvcms8L3NwYW4+PG86cD48L286cD48L3A+PHA+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4tPC9z
cGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6Ny4wcHQ7Y29sb3I6IzFGNDk3RCc+Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDwvc3Bhbj48c3Bh
biBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiO2NvbG9yOiMxRjQ5N0QnPlRvIGRlcGxveSB0aGUgTUxUUkFOUyBtZWNoYW5pc21zIHRoYXQg
eW91IHdpbGwgcmVxdWlyZSB0byBjb21wZW5zYXRlIGZvciB0aGUgbGFjayB0aGUgYWJvdmUgbWVu
dGlvbmVkIGNhcGFiaWxpdHk8L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFs
IHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJz
YW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+PHAg
Y2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5Ib3cgbXVjaCBtb3JlIG1v
bmV5L2VmZm9ydD8gV2h5Pzwvc3Bhbj48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwg
c3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Jz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNh
bnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD48cCBj
bGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvJz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBSb248L3NwYW4+PG86
cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4m
bmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtj
b2xvcjojMUY0OTdEJz4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+PGRpdiBzdHlsZT0nYm9y
ZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGlu
IDQuMHB0Jz48ZGl2PjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1
QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluJz48cCBjbGFzcz1Nc29Ob3JtYWwg
c3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Jz48Yj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwi
c2Fucy1zZXJpZiInPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPiBRaW9uZyBbbWFpbHRvOjxhIGhy
ZWY9Im1haWx0bzpiaW5neHVlcmVAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+YmluZ3h1ZXJl
QGdtYWlsLmNvbTwvYT5dIDxicj48Yj5TZW50OjwvYj4gTW9uZGF5LCBKdW5lIDE4LCAyMDEyIDEw
OjAzIFBNPGJyPjxiPlRvOjwvYj4gUm9uYWxkIEJvbmljYTxicj48Yj5DYzo8L2I+IExlbm55IEdp
dWxpYW5vOyBNQk9ORUQgV0c8L3NwYW4+PG86cD48L286cD48L3A+PGRpdj48ZGl2PjxwIGNsYXNz
PU1zb05vcm1hbD48YnI+PGI+U3ViamVjdDo8L2I+IFJlOiBbTUJPTkVEXSBNdWx0aWNhc3QgdHJh
bnNpdGlvbiB3b3JrIGluIE1CT05FRDxvOnA+PC9vOnA+PC9wPjwvZGl2PjwvZGl2PjwvZGl2Pjwv
ZGl2PjxkaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz4mbmJzcDs8bzpwPjwvbzpwPjwvcD48
cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1i
b3R0b206MTIuMHB0Jz5IaSBSb25hbGQsPGJyPjxicj5JIGFncmVlIHdlIGRvIHdvdWxkIGxpa2Ug
dG8gZW5hYmxlIElQdjYgbXVsdGljYXN0IGluIG91ciBuZXR3b3JrLiBIb3dldmVyLCBhbGwgdGhl
c2UgdGhpbmdzIGNhbiBub3QgYmUgYWNoaWV2ZWQgd2l0aGluIG9uZSBuaWdodC4gV2Ugc3RpbGwg
aGF2ZSBhIGxvdCBvZiBvbGQgZGV2aWNlcyB3aGljaCBjYW4gbm90IHN1cHBvcnQgSVB2NiBtdWx0
aWNhc3QgaW4gb3VyIG5ldHdvcmssIGJ1dCB3ZSBhcmUgcnVubmluZyBvdXQgb2YgSVB2NCBhZGRy
ZXNzIHJpZ2h0IG5vdy4gU28gd2UgY2FuIG5vdCB3YWl0IHVudGlsIHRoZSB3aG9sZSBuZXR3b3Jr
IGlzIHJlYWR5IGZvciBJUHY2IG11bHRpY2FzdC48YnI+PGJyPkhvcGUgaXQgY2xhcmlmaWVzLjxi
cj48YnI+QmVzdCB3aXNoZXM8YnI+UWlvbmc8bzpwPjwvbzpwPjwvcD48ZGl2PjxwIGNsYXNzPU1z
b05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8nPk9uIE1vbiwgSnVuIDE4LCAyMDEyIGF0IDExOjA3IFBNLCBSb25hbGQgQm9uaWNh
ICZsdDs8YSBocmVmPSJtYWlsdG86cmJvbmljYUBqdW5pcGVyLm5ldCIgdGFyZ2V0PSJfYmxhbmsi
PnJib25pY2FAanVuaXBlci5uZXQ8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD48ZGl2Pjxk
aXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5IaSBRaW9uZyw8
L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjoj
MUY0OTdEJz4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0
eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+
PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjtjb2xvcjojMUY0OTdEJz5JZiB5b3Ugd2VyZSB0byBlbmFibGUgSVB2NiBtdWx0aWNh
c3QgdGhyb3VnaG91dCB5b3VyIG5ldHdvcmsgYmVmb3JlIGRlcGxveWluZyBJUHY2IG9ubHkgcmVj
ZWl2ZXJzLCB3b3VsZCB5b3Ugbm90IGZhbGwgaW50byB1c2UgY2FzZXMgMy40IGFuZCAzLjUgKHRo
ZSBkdWFsIHN0YWNrIHNjZW5hcmlvcykuIFNpbmNlIHlvdSBhcmUgZ29pbmcgdG8gaGF2ZSB0byBl
bmFibGUgSVB2NiBtdWx0aWNhc3QgdGhyb3VnaG91dCB5b3VyIG5ldHdvcmsgYW55d2F5LCB3b3Vs
ZG7igJl0IGl0IGJlIGEgZ29vZCBpZGVhIHRvIGRvIHNvIHNvb25lciB0aGFuIGxhdGVyPyA8L3Nw
YW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNwYW4gc3R5bGU9J2ZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0
OTdEJz4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxl
PSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PHNw
YW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNl
cmlmIjtjb2xvcjojMUY0OTdEJz4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgUm9uPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8nPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+Jm5ic3A7PC9z
cGFuPjxvOnA+PC9vOnA+PC9wPjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCc+PGRpdj48ZGl2IHN0eWxl
PSdib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBw
dCAwaW4gMGluIDBpbic+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PGI+PHNwYW4gc3R5bGU9J2ZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiJz5Gcm9tOjwvc3Bh
bj48L2I+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIs
InNhbnMtc2VyaWYiJz4gUWlvbmcgW21haWx0bzo8YSBocmVmPSJtYWlsdG86YmluZ3h1ZXJlQGdt
YWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmJpbmd4dWVyZUBnbWFpbC5jb208L2E+XSA8YnI+PGI+
U2VudDo8L2I+IFR1ZXNkYXksIEp1bmUgMTIsIDIwMTIgMTA6MTEgQU08YnI+PGI+VG86PC9iPiBM
ZW5ueSBHaXVsaWFubzxicj48Yj5DYzo8L2I+IE1CT05FRCBXRzsgUm9uYWxkIEJvbmljYTwvc3Bh
bj48bzpwPjwvbzpwPjwvcD48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8nPjxicj48Yj5TdWJqZWN0
OjwvYj4gUmU6IFtNQk9ORURdIE11bHRpY2FzdCB0cmFuc2l0aW9uIHdvcmsgaW4gTUJPTkVEPG86
cD48L286cD48L3A+PC9kaXY+PC9kaXY+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+Jm5ic3A7
PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCc+RGVhciBhbGwsPG86cD48L286cD48L3A+PGRp
dj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8nPjxicj48YnI+MS4gSW4gb3VyIHNpdHVhdGlvbiwg
dGhlIHNvdXJjZSBtYXkgc3RpbGwgcmVtaWFuIGluIElQdjQsIHdoaWxlIHRoZSByZWNlaXZlciB3
aWxsIGJlIElQdjYtb25seSBzaW5jZSB0aGVyZSBpcyBubyBtb3JlIElQdjQgYWRkcmVzcyBhbnlt
b3JlLiBIb3dldmVyLCB0aGUgbmV0d29yayBtaWdodCBiZSBJUHY0LW9ubHksIHdoaWNoIGNhbiBu
b3Qgc3VwcG9ydCBJUHY2IG11bHRpY2FzdCB5ZXQ7IG9yIHRoZSBuZXR3b3JrIGNhbiBzdXBwb3J0
IElQdjYgbXVsdGljYXN0LiBUaGlzIGlzIHRoZSBjYXNlIG9mIDYtNC4gPGJyPkFub3RoZXIgc2l0
dWF0aW9uIGlzOiB0aGUgYWNjZXNzIG5ldHdvcmsgaXMgc3RpbGwgSVB2NC1vbmx5LCBhbmQgdGhl
IGNvcmUgbmV0b3dyayAob3IgYXBwbGljYXRpb24gcGxhdGZvcm0pIGlzIElQdjYsIHRoZW4gdGhh
dCBpcyB0aGUgY2FzZSBvZiA2LTQtNi00Ljxicj48YnI+Mi4gVXNlIGNhc2U6IDMuMiwgMy40LDxi
cj48YnI+QmVzdCB3aXNoZXM8YnI+UWlvbmc8bzpwPjwvbzpwPjwvcD48L2Rpdj48L2Rpdj48ZGl2
PjxkaXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvJz5PbiBGcmksIEp1biA4LCAyMDEyIGF0IDQ6
MzQgQU0sIExlb25hcmQgR2l1bGlhbm8gJmx0OzxhIGhyZWY9Im1haWx0bzpsZW5ueUBqdW5pcGVy
Lm5ldCIgdGFyZ2V0PSJfYmxhbmsiPmxlbm55QGp1bmlwZXIubmV0PC9hPiZndDsgd3JvdGU6PG86
cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+PGJyPlRoZSBtdWx0aWNhc3QgdHJhbnNp
dGlvbiB3b3JrIHdpdGhpbiBNQk9ORUQgd2FzIGluaXRpYWxseSBpbnRlbmRlZCB0byBjb25zaXN0
IG9mIH4gMyBkb2N1bWVudCB3aXRoIGxpbWl0ZWQgc2NvcGUuICZuYnNwO0luIGEgdmVyeSBzaG9y
dCBhbW91bnQgb2YgdGltZSwgd2UndmUgc2VlbiA3IGRyYWZ0cyAoYW5kIGNvdW50aW5nKSB3aXRo
IHNjb3BlIHdpZGVuaW5nLjxicj48YnI+SW4gb3JkZXIgdG8gbWFrZSBzdXJlIHdlIGFyZSBmb2N1
c2luZyBvbiB3b3JrIHRoYXQgaXMgb2YgYWN0dWFsIHZhbHVlIHRvIHRoZSBjb21tdW5pdHkgYW5k
IHByZXZlbnQgYSBmbG9vZCBvZiBoaWdoIHZvbHVtZS9sb3cgdmFsdWUgZHJhZnRzLCB3ZSB3b3Vs
ZCBsaWtlIHRvIHJldmlzaXQgdGhlIGJhc2ljIHF1ZXN0aW9ucyBvZiBtdWx0aWNhc3QgdHJhbnNp
dGlvbiB3aXRoaW4gTUJPTkVELiAmbmJzcDtXZSB3b3VsZCBsaWtlIHRvIGhlYXIgYW5zd2VycyBm
cm9tIHRoZSBXRyB0byB0aGUgZm9sbG93aW5nIHF1ZXN0aW9ucyBiZWZvcmUgY29udGludWluZyBh
bnkgd29yayBvbiBtdWx0aWNhc3QgdHJhbnNpdGlvbiBpbiBNQk9ORUQ6PGJyPjxicj4xKSBXaGlj
aCBvcGVyYXRvcnMgaW50ZW5kIHRvIHNvdXJjZSBtdWx0aWNhc3QgdHJhZmZpYyBmcm9tIG9uZSBJ
UCB2ZXJzaW9uIGFuZCByZWNlaXZlIGl0IG92ZXIgYW5vdGhlciBJUCB2ZXJzaW9uPzxicj48YnI+
MikgRm9yIHRob3NlIHdobyBhbnN3ZXIgMSksIHBsZWFzZSBpZGVudGlmeSB0aGUgdXNlLWNhc2Vz
IG9mIGludGVyZXN0IGluIGRyYWZ0LWlldGYtbWJvbmVkLXY0djYtbWNhc3QtcHMgc28gd2UgY2Fu
IGxpbWl0IGRpc2N1c3Npb24gdG8gc29sdXRpb25zIGZvciB0aG9zZSB1c2UgY2FzZXMuPGJyPjxi
cj48YnI+TUJPTkVEIENoYWlyczxicj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXzxicj5NQk9ORUQgbWFpbGluZyBsaXN0PGJyPjxhIGhyZWY9Im1haWx0bzpN
Qk9ORURAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5NQk9ORURAaWV0Zi5vcmc8L2E+PGJyPjxh
IGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWJvbmVkIiB0YXJn
ZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tYm9uZWQ8
L2E+PG86cD48L286cD48L3A+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byc+Jm5ic3A7PG86cD48
L286cD48L3A+PC9kaXY+PC9kaXY+PC9kaXY+PC9kaXY+PC9kaXY+PC9kaXY+PHAgY2xhc3M9TXNv
Tm9ybWFsIHN0eWxlPSdtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byc+Jm5ic3A7PG86cD48L286cD48L3A+PC9kaXY+PC9kaXY+PC9kaXY+PC9kaXY+PC9k
aXY+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjwvZGl2Pjwv
ZGl2PjwvYm9keT48L2h0bWw+

--_000_13205C286662DE4387D9AF3AC30EF456D76EDCE3CAEMBX01WFjnprn_--

From Tina.Tsou.Zouting@huawei.com  Thu Jun 21 09:27:22 2012
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC86021F8629 for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 09:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 gLCtet3iuVXa for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 09:27:21 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 7B87621F86F5 for <mboned@ietf.org>; Thu, 21 Jun 2012 09:27:21 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHC41234; Thu, 21 Jun 2012 12:27:21 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 21 Jun 2012 09:26:09 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.109]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.003; Thu, 21 Jun 2012 09:26:06 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: AQHNRO2IJbQ/FDofPUmTNMjuOmtYFZb3NfMAgAl9swCAALcMgIACA8EAgAAaSYCAAfS5AP//jc2v
Date: Thu, 21 Jun 2012 16:26:06 +0000
Message-ID: <3A85B6A1-9427-40C9-8D3A-307ACFECE13B@huawei.com>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net> <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com>, <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_3A85B6A1942740C98D3A307ACFECE13Bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 16:27:22 -0000

--_000_3A85B6A1942740C98D3A307ACFECE13Bhuaweicom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

The original question Lenny asked did not including 3.1 and 3.3.
Lenny asked
"1) Which operators intend to source multicast traffic from one IP version =
and receive it over another IP version?"
3.1 is 4-6-4
3.2 is 6-4-6.
So they r not In the scope of Lenny's question.

Tina

On Jun 21, 2012, at 9:16 AM, "Ronald Bonica" <rbonica@juniper.net<mailto:rb=
onica@juniper.net>> wrote:

Folks,

So it looks like use-cases 3.2, 3.4 and 3.5 may see deployment. There were =
no takers for use-cases 3.1 and 3.3.

In http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html, Simon=
 Perrault suggests two solutions for 3.4 and 3.5. Does the WG agree that th=
ose are the solutions that we should run with?

Simon=92s solutions can also be applied to use-case 3.2 if we tunnel over n=
on-multicast enabled IPv4 segment. Does everyone agree that that is a good =
idea?

                                                    Ron

From: Qiong [mailto:bingxuere@gmail.com]
Sent: Wednesday, June 20, 2012 6:23 AM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

For your question, it would be too difficult to give you an acurate number =
of money/effort, but I can tell you our situation of network upgradation.

In the transition period, it would be impossible to replace all the legacy =
IPv4-only devices, especially a great many access network devices. So actua=
lly, the process would be taken firstly towards our customers and new regio=
n. For example, a new customer might get a new  STB with IPv6 functionality=
. However, this new customer might access some region only with old devices=
, then at that time, it will be of great help to implement some MLTRANS sol=
utions in the new STB or deploy limited devices in the network. I believe t=
his will cost less than upgrading the whole network in the first place.

For old customers, they will still use IPv4 as they already got address, un=
less we upgrade their STB to support IPv6 remotely. But it is not the first=
 priority point.

Best wishes
Qiong
On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica <rbonica@juniper.net<mailto:=
rbonica@juniper.net>> wrote:
Qiong,

Which of the following do you think will require more money/effort:


-          To deploy IPv6 multicast throughout your network

-          To deploy the MLTRANS mechanisms that you will require to compen=
sate for the lack the above mentioned capability

How much more money/effort? Why?

                                                 Ron


From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Monday, June 18, 2012 10:03 PM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG

Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

I agree we do would like to enable IPv6 multicast in our network. However, =
all these things can not be achieved within one night. We still have a lot =
of old devices which can not support IPv6 multicast in our network, but we =
are running out of IPv4 address right now. So we can not wait until the who=
le network is ready for IPv6 multicast.

Hope it clarifies.

Best wishes
Qiong
On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica <rbonica@juniper.net<mailto=
:rbonica@juniper.net>> wrote:
Hi Qiong,

If you were to enable IPv6 multicast throughout your network before deployi=
ng IPv6 only receivers, would you not fall into use cases 3.4 and 3.5 (the =
dual stack scenarios). Since you are going to have to enable IPv6 multicast=
 throughout your network anyway, wouldn=92t it be a good idea to do so soon=
er than later?

                                                                      Ron

From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Tuesday, June 12, 2012 10:11 AM
To: Lenny Giuliano
Cc: MBONED WG; Ronald Bonica

Subject: Re: [MBONED] Multicast transition work in MBONED

Dear all,


1. In our situation, the source may still remian in IPv4, while the receive=
r will be IPv6-only since there is no more IPv4 address anymore. However, t=
he network might be IPv4-only, which can not support IPv6 multicast yet; or=
 the network can support IPv6 multicast. This is the case of 6-4.
Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.

2. Use case: 3.2, 3.4,

Best wishes
Qiong
On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <lenny@juniper.net<mailto:=
lenny@juniper.net>> wrote:

The multicast transition work within MBONED was initially intended to consi=
st of ~ 3 document with limited scope.  In a very short amount of time, we'=
ve seen 7 drafts (and counting) with scope widening.

In order to make sure we are focusing on work that is of actual value to th=
e community and prevent a flood of high volume/low value drafts, we would l=
ike to revisit the basic questions of multicast transition within MBONED.  =
We would like to hear answers from the WG to the following questions before=
 continuing any work on multicast transition in MBONED:

1) Which operators intend to source multicast traffic from one IP version a=
nd receive it over another IP version?

2) For those who answer 1), please identify the use-cases of interest in dr=
aft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions for t=
hose use cases.


MBONED Chairs
_______________________________________________
MBONED mailing list
MBONED@ietf.org<mailto:MBONED@ietf.org>
https://www.ietf.org/mailman/listinfo/mboned




--_000_3A85B6A1942740C98D3A307ACFECE13Bhuaweicom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body bgcolor=3D"#FFFFFF">
<div>The original question Lenny asked did not including 3.1 and 3.3.</div>
<div>Lenny asked</div>
<div>&quot;<font class=3D"Apple-style-span" face=3D"Helvetica"><tt>1) Which=
 operators intend to source multicast traffic from one IP version&nbsp;</tt=
></font><font class=3D"Apple-style-span" face=3D"Helvetica"><tt>and receive=
 it over another IP version?&quot;</tt></font></div>
<div><font class=3D"Apple-style-span" face=3D"monospace">3.1 is 4-6-4<br>
</font></div>
<div><font class=3D"Apple-style-span" face=3D"monospace">3.2 is 6-4-6.<br>
</font></div>
<div>So they r not In the scope of Lenny's question.</div>
<div><br>
</div>
<div>Tina</div>
<div><br>
On Jun 21, 2012, at 9:16 AM, &quot;Ronald Bonica&quot; &lt;<a href=3D"mailt=
o:rbonica@juniper.net">rbonica@juniper.net</a>&gt; wrote:<br>
<br>
</div>
<div></div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Folks,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">So it looks like use-case=
s 3.2, 3.4 and 3.5 may see deployment. There were no takers for use-cases 3=
.1 and 3.3.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In
<a href=3D"http://www.ietf.org/mail-archive/web/mboned/current/msg01607.htm=
l">http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html</a>, S=
imon Perrault suggests two solutions for 3.4 and 3.5. Does the WG agree tha=
t those are the solutions that we
 should run with?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Simon=92s solutions can a=
lso be applied to use-case 3.2 if we tunnel over non-multicast enabled IPv4=
 segment. Does everyone agree that that is a good idea?<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ron<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Qiong [m=
ailto:bingxuere@gmail.com]
<br>
<b>Sent:</b> Wednesday, June 20, 2012 6:23 AM<br>
<b>To:</b> Ronald Bonica<br>
<b>Cc:</b> Lenny Giuliano; MBONED WG<br>
<b>Subject:</b> Re: [MBONED] Multicast transition work in MBONED<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Hi Ronald,<br>
<br>
For your question, it would be too difficult to give you an acurate number =
of money/effort, but I can tell you our situation of network upgradation.
<br>
<br>
In the transition period, it would be impossible to replace all the legacy =
IPv4-only devices, especially a great many access network devices. So actua=
lly, the process would be taken firstly towards our customers and new regio=
n. For example, a new customer might
 get a new&nbsp; STB with IPv6 functionality. However, this new customer mi=
ght access some region only with old devices, then at that time, it will be=
 of great help to implement some MLTRANS solutions in the new STB or deploy=
 limited devices in the network. I believe
 this will cost less than upgrading the whole network in the first place. <=
br>
<br>
For old customers, they will still use IPv4 as they already got address, un=
less we upgrade their STB to support IPv6 remotely. But it is not the first=
 priority point.<br>
<br>
Best wishes<br>
Qiong<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica &lt;<=
a href=3D"mailto:rbonica@juniper.net" target=3D"_blank">rbonica@juniper.net=
</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Qiong,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Which of the following do you think wil=
l require more money/effort:</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">-</span><span style=3D"font-size:7.0pt;color:=
#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">To deploy IPv6 multicast throughout your =
network</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">-</span><span style=3D"font-size:7.0pt;color:=
#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">To deploy the MLTRANS mechanisms that you=
 will require to compensate for the lack the above mentioned capability</sp=
an><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">How much more money/effort? Why?</span>=
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; Ron</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Qiong [mailto:<a href=
=3D"mailto:bingxuere@gmail.com" target=3D"_blank">bingxuere@gmail.com</a>]
<br>
<b>Sent:</b> Monday, June 18, 2012 10:03 PM<br>
<b>To:</b> Ronald Bonica<br>
<b>Cc:</b> Lenny Giuliano; MBONED WG</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [MBONED] Multicast transition work in MBONED<o:p></o:p>=
</p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">Hi Ronald,<br>
<br>
I agree we do would like to enable IPv6 multicast in our network. However, =
all these things can not be achieved within one night. We still have a lot =
of old devices which can not support IPv6 multicast in our network, but we =
are running out of IPv4 address
 right now. So we can not wait until the whole network is ready for IPv6 mu=
lticast.<br>
<br>
Hope it clarifies.<br>
<br>
Best wishes<br>
Qiong<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica &lt;<a href=3D"mai=
lto:rbonica@juniper.net" target=3D"_blank">rbonica@juniper.net</a>&gt; wrot=
e:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Hi Qiong,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">If you were to enable IPv6 multicast th=
roughout your network before deploying IPv6 only receivers,
 would you not fall into use cases 3.4 and 3.5 (the dual stack scenarios). =
Since you are going to have to enable IPv6 multicast throughout your networ=
k anyway, wouldn=92t it be a good idea to do so sooner than later?
</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Ron</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Qiong [mailto:<a href=
=3D"mailto:bingxuere@gmail.com" target=3D"_blank">bingxuere@gmail.com</a>]
<br>
<b>Sent:</b> Tuesday, June 12, 2012 10:11 AM<br>
<b>To:</b> Lenny Giuliano<br>
<b>Cc:</b> MBONED WG; Ronald Bonica</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<b>Subject:</b> Re: [MBONED] Multicast transition work in MBONED<o:p></o:p>=
</p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">Dear all,<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<br>
1. In our situation, the source may still remian in IPv4, while the receive=
r will be IPv6-only since there is no more IPv4 address anymore. However, t=
he network might be IPv4-only, which can not support IPv6 multicast yet; or=
 the network can support IPv6 multicast.
 This is the case of 6-4. <br>
Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.=
<br>
<br>
2. Use case: 3.2, 3.4,<br>
<br>
Best wishes<br>
Qiong<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano &lt;<a href=3D"ma=
ilto:lenny@juniper.net" target=3D"_blank">lenny@juniper.net</a>&gt; wrote:<=
o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
The multicast transition work within MBONED was initially intended to consi=
st of ~ 3 document with limited scope. &nbsp;In a very short amount of time=
, we've seen 7 drafts (and counting) with scope widening.<br>
<br>
In order to make sure we are focusing on work that is of actual value to th=
e community and prevent a flood of high volume/low value drafts, we would l=
ike to revisit the basic questions of multicast transition within MBONED. &=
nbsp;We would like to hear answers from
 the WG to the following questions before continuing any work on multicast =
transition in MBONED:<br>
<br>
1) Which operators intend to source multicast traffic from one IP version a=
nd receive it over another IP version?<br>
<br>
2) For those who answer 1), please identify the use-cases of interest in dr=
aft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions for t=
hose use cases.<br>
<br>
<br>
MBONED Chairs<br>
_______________________________________________<br>
MBONED mailing list<br>
<a href=3D"mailto:MBONED@ietf.org" target=3D"_blank">MBONED@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mboned" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mboned</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div></div>
</blockquote>
</body>
</html>

--_000_3A85B6A1942740C98D3A307ACFECE13Bhuaweicom_--

From simon.perreault@viagenie.ca  Thu Jun 21 09:28:04 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 374B121F8733 for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 09:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 X2WXGjmkNQcC for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 09:28:03 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 8F23521F8679 for <mboned@ietf.org>; Thu, 21 Jun 2012 09:28:03 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c064:1435:1ef2:cef2:725e]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 06D8441581 for <mboned@ietf.org>; Thu, 21 Jun 2012 12:28:02 -0400 (EDT)
Message-ID: <4FE34B92.5090103@viagenie.ca>
Date: Thu, 21 Jun 2012 12:28:02 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
To: mboned@ietf.org
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net> <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 16:28:04 -0000

On 2012-06-21 12:14, Ronald Bonica wrote:
> In http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html,
> Simon Perrault suggests two solutions for 3.4 and 3.5. Does the WG agree
> that those are the solutions that we should run with?
>
> Simon’s solutions can also be applied to use-case 3.2 if we tunnel over
> non-multicast enabled IPv4 segment. Does everyone agree that that is a
> good idea?

Maybe it is the wrong URL or the wrong person, but I don't know what 
solutions you're talking about, sorry. Could you please summarize them?

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From rbonica@juniper.net  Thu Jun 21 09:40:28 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2683A21F86F8 for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 09:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.574
X-Spam-Level: 
X-Spam-Status: No, score=-106.574 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 RGH3jCmg+osS for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 09:40:22 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 60C2821F86E5 for <mboned@ietf.org>; Thu, 21 Jun 2012 09:40:22 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKT+NOdA0ehsFZgUymbCatA/SHdk/mDggs@postini.com; Thu, 21 Jun 2012 09:40:22 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 21 Jun 2012 09:39:45 -0700
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 21 Jun 2012 09:39:43 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Thu, 21 Jun 2012 12:38:39 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Date: Thu, 21 Jun 2012 12:38:37 -0400
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: AQHNRO2IJbQ/FDofPUmTNMjuOmtYFZb3NfMAgAl9swCAALcMgIACA8EAgAAaSYCAAfS5AP//jc2vgAACxgA=
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76EDCE440@EMBX01-WF.jnpr.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net> <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com>, <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net> <3A85B6A1-9427-40C9-8D3A-307ACFECE13B@huawei.com>
In-Reply-To: <3A85B6A1-9427-40C9-8D3A-307ACFECE13B@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_13205C286662DE4387D9AF3AC30EF456D76EDCE440EMBX01WFjnprn_"
MIME-Version: 1.0
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 16:40:28 -0000

--_000_13205C286662DE4387D9AF3AC30EF456D76EDCE440EMBX01WFjnprn_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Do we have anybody who is going to deploy 3.1 or 3.3?

                                     Ron


From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
Sent: Thursday, June 21, 2012 12:26 PM
To: Ronald Bonica
Cc: Qiong; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

The original question Lenny asked did not including 3.1 and 3.3.
Lenny asked
"1) Which operators intend to source multicast traffic from one IP version =
and receive it over another IP version?"
3.1 is 4-6-4
3.2 is 6-4-6.
So they r not In the scope of Lenny's question.

Tina

On Jun 21, 2012, at 9:16 AM, "Ronald Bonica" <rbonica@juniper.net<mailto:rb=
onica@juniper.net>> wrote:
Folks,

So it looks like use-cases 3.2, 3.4 and 3.5 may see deployment. There were =
no takers for use-cases 3.1 and 3.3.

In http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html, Simon=
 Perrault suggests two solutions for 3.4 and 3.5. Does the WG agree that th=
ose are the solutions that we should run with?

Simon's solutions can also be applied to use-case 3.2 if we tunnel over non=
-multicast enabled IPv4 segment. Does everyone agree that that is a good id=
ea?

                                                    Ron

From: Qiong [mailto:bingxuere@gmail.com]
Sent: Wednesday, June 20, 2012 6:23 AM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

For your question, it would be too difficult to give you an acurate number =
of money/effort, but I can tell you our situation of network upgradation.

In the transition period, it would be impossible to replace all the legacy =
IPv4-only devices, especially a great many access network devices. So actua=
lly, the process would be taken firstly towards our customers and new regio=
n. For example, a new customer might get a new  STB with IPv6 functionality=
. However, this new customer might access some region only with old devices=
, then at that time, it will be of great help to implement some MLTRANS sol=
utions in the new STB or deploy limited devices in the network. I believe t=
his will cost less than upgrading the whole network in the first place.

For old customers, they will still use IPv4 as they already got address, un=
less we upgrade their STB to support IPv6 remotely. But it is not the first=
 priority point.

Best wishes
Qiong
On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica <rbonica@juniper.net<mailto:=
rbonica@juniper.net>> wrote:
Qiong,

Which of the following do you think will require more money/effort:


-          To deploy IPv6 multicast throughout your network

-          To deploy the MLTRANS mechanisms that you will require to compen=
sate for the lack the above mentioned capability

How much more money/effort? Why?

                                                 Ron


From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Monday, June 18, 2012 10:03 PM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG

Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

I agree we do would like to enable IPv6 multicast in our network. However, =
all these things can not be achieved within one night. We still have a lot =
of old devices which can not support IPv6 multicast in our network, but we =
are running out of IPv4 address right now. So we can not wait until the who=
le network is ready for IPv6 multicast.

Hope it clarifies.

Best wishes
Qiong
On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica <rbonica@juniper.net<mailto=
:rbonica@juniper.net>> wrote:
Hi Qiong,

If you were to enable IPv6 multicast throughout your network before deployi=
ng IPv6 only receivers, would you not fall into use cases 3.4 and 3.5 (the =
dual stack scenarios). Since you are going to have to enable IPv6 multicast=
 throughout your network anyway, wouldn't it be a good idea to do so sooner=
 than later?

                                                                      Ron

From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Tuesday, June 12, 2012 10:11 AM
To: Lenny Giuliano
Cc: MBONED WG; Ronald Bonica

Subject: Re: [MBONED] Multicast transition work in MBONED

Dear all,


1. In our situation, the source may still remian in IPv4, while the receive=
r will be IPv6-only since there is no more IPv4 address anymore. However, t=
he network might be IPv4-only, which can not support IPv6 multicast yet; or=
 the network can support IPv6 multicast. This is the case of 6-4.
Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.

2. Use case: 3.2, 3.4,

Best wishes
Qiong
On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <lenny@juniper.net<mailto:=
lenny@juniper.net>> wrote:

The multicast transition work within MBONED was initially intended to consi=
st of ~ 3 document with limited scope.  In a very short amount of time, we'=
ve seen 7 drafts (and counting) with scope widening.

In order to make sure we are focusing on work that is of actual value to th=
e community and prevent a flood of high volume/low value drafts, we would l=
ike to revisit the basic questions of multicast transition within MBONED.  =
We would like to hear answers from the WG to the following questions before=
 continuing any work on multicast transition in MBONED:

1) Which operators intend to source multicast traffic from one IP version a=
nd receive it over another IP version?

2) For those who answer 1), please identify the use-cases of interest in dr=
aft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions for t=
hose use cases.


MBONED Chairs
_______________________________________________
MBONED mailing list
MBONED@ietf.org<mailto:MBONED@ietf.org>
https://www.ietf.org/mailman/listinfo/mboned




--_000_13205C286662DE4387D9AF3AC30EF456D76EDCE440EMBX01WFjnprn_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>Do we have anybody who is going to deploy 3.1 or 3.3? <o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"C=
alibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3D=
MsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif=
";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; Ron<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fa=
mily:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div=
 style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0p=
t'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.=
0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;fo=
nt-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:1=
0.0pt;font-family:"Tahoma","sans-serif"'> Tina TSOU [mailto:Tina.Tsou.Zouti=
ng@huawei.com] <br><b>Sent:</b> Thursday, June 21, 2012 12:26 PM<br><b>To:<=
/b> Ronald Bonica<br><b>Cc:</b> Qiong; MBONED WG<br><b>Subject:</b> Re: [MB=
ONED] Multicast transition work in MBONED<o:p></o:p></span></p></div></div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>The ori=
ginal question Lenny asked did not including 3.1 and 3.3.<o:p></o:p></p></d=
iv><div><p class=3DMsoNormal>Lenny asked<o:p></o:p></p></div><div><p class=
=3DMsoNormal>&quot;<tt><span style=3D'font-size:10.0pt'>1) Which operators =
intend to source multicast traffic from one IP version&nbsp;and receive it =
over another IP version?&quot;</span></tt><o:p></o:p></p></div><div><p clas=
s=3DMsoNormal><span style=3D'font-family:"Courier New"'>3.1 is 4-6-4</span>=
<o:p></o:p></p></div><div><p class=3DMsoNormal><span style=3D'font-family:"=
Courier New"'>3.2 is 6-4-6.</span><o:p></o:p></p></div><div><p class=3DMsoN=
ormal>So they r not In the scope of Lenny's question.<o:p></o:p></p></div><=
div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNorm=
al>Tina<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-botto=
m:12.0pt'><br>On Jun 21, 2012, at 9:16 AM, &quot;Ronald Bonica&quot; &lt;<a=
 href=3D"mailto:rbonica@juniper.net">rbonica@juniper.net</a>&gt; wrote:<o:p=
></o:p></p></div><blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'=
><div><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'>Folks,</span><o:p></o:p></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So i=
t looks like use-cases 3.2, 3.4 and 3.5 may see deployment. There were no t=
akers for use-cases 3.1 and 3.3.</span><o:p></o:p></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>In <a href=
=3D"http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html">http=
://www.ietf.org/mail-archive/web/mboned/current/msg01607.html</a>, Simon Pe=
rrault suggests two solutions for 3.4 and 3.5. Does the WG agree that those=
 are the solutions that we should run with?</span><o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
>Simon&#8217;s solutions can also be applied to use-case 3.2 if we tunnel o=
ver non-multicast enabled IPv4 segment. Does everyone agree that that is a =
good idea?</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-si=
ze:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o=
:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ron</span><o:p></o:p></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><div style=3D'border:=
none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div styl=
e=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>=
<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family=
:"Tahoma","sans-serif"'> Qiong [<a href=3D"mailto:bingxuere@gmail.com">mail=
to:bingxuere@gmail.com</a>] <br><b>Sent:</b> Wednesday, June 20, 2012 6:23 =
AM<br><b>To:</b> Ronald Bonica<br><b>Cc:</b> Lenny Giuliano; MBONED WG<br><=
b>Subject:</b> Re: [MBONED] Multicast transition work in MBONED</span><o:p>=
</o:p></p></div></div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3D=
MsoNormal style=3D'margin-bottom:12.0pt'>Hi Ronald,<br><br>For your questio=
n, it would be too difficult to give you an acurate number of money/effort,=
 but I can tell you our situation of network upgradation. <br><br>In the tr=
ansition period, it would be impossible to replace all the legacy IPv4-only=
 devices, especially a great many access network devices. So actually, the =
process would be taken firstly towards our customers and new region. For ex=
ample, a new customer might get a new&nbsp; STB with IPv6 functionality. Ho=
wever, this new customer might access some region only with old devices, th=
en at that time, it will be of great help to implement some MLTRANS solutio=
ns in the new STB or deploy limited devices in the network. I believe this =
will cost less than upgrading the whole network in the first place. <br><br=
>For old customers, they will still use IPv4 as they already got address, u=
nless we upgrade their STB to support IPv6 remotely. But it is not the firs=
t priority point.<br><br>Best wishes<br>Qiong<o:p></o:p></p><div><p class=
=3DMsoNormal>On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica &lt;<a href=3D"=
mailto:rbonica@juniper.net" target=3D"_blank">rbonica@juniper.net</a>&gt; w=
rote:<o:p></o:p></p><div><div><p class=3DMsoNormal style=3D'mso-margin-top-=
alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>Qiong,</span><o:p></o:p></p><p =
class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:au=
to'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";colo=
r:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-ma=
rgin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>Which of the following=
 do you think will require more money/effort:</span><o:p></o:p></p><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'>&nbsp;</span><o:p></o:p></p><p><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>-</span><span style=3D'font-siz=
e:7.0pt;color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; </span><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif=
";color:#1F497D'>To deploy IPv6 multicast throughout your network</span><o:=
p></o:p></p><p><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-=
serif";color:#1F497D'>-</span><span style=3D'font-size:7.0pt;color:#1F497D'=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>To d=
eploy the MLTRANS mechanisms that you will require to compensate for the la=
ck the above mentioned capability</span><o:p></o:p></p><p class=3DMsoNormal=
 style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbs=
p;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:au=
to;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:=
"Calibri","sans-serif";color:#1F497D'>How much more money/effort? Why?</spa=
n><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNo=
rmal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ron</span><o:=
p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margi=
n-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;<=
/span><o:p></o:p></p><div style=3D'border:none;border-left:solid blue 1.5pt=
;padding:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:solid=
 #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'mso=
-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style=3D'font-siz=
e:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'=
font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Qiong [mailto:<a href=
=3D"mailto:bingxuere@gmail.com" target=3D"_blank">bingxuere@gmail.com</a>] =
<br><b>Sent:</b> Monday, June 18, 2012 10:03 PM<br><b>To:</b> Ronald Bonica=
<br><b>Cc:</b> Lenny Giuliano; MBONED WG</span><o:p></o:p></p><div><div><p =
class=3DMsoNormal><br><b>Subject:</b> Re: [MBONED] Multicast transition wor=
k in MBONED<o:p></o:p></p></div></div></div></div><div><div><p class=3DMsoN=
ormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o=
:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;margin-b=
ottom:12.0pt'>Hi Ronald,<br><br>I agree we do would like to enable IPv6 mul=
ticast in our network. However, all these things can not be achieved within=
 one night. We still have a lot of old devices which can not support IPv6 m=
ulticast in our network, but we are running out of IPv4 address right now. =
So we can not wait until the whole network is ready for IPv6 multicast.<br>=
<br>Hope it clarifies.<br><br>Best wishes<br>Qiong<o:p></o:p></p><div><p cl=
ass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
'>On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica &lt;<a href=3D"mailto:rbo=
nica@juniper.net" target=3D"_blank">rbonica@juniper.net</a>&gt; wrote:<o:p>=
</o:p></p><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;m=
so-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'>Hi Qiong,</span><o:p></o:p></p><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-=
top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'>If you were to enable IPv6 =
multicast throughout your network before deploying IPv6 only receivers, wou=
ld you not fall into use cases 3.4 and 3.5 (the dual stack scenarios). Sinc=
e you are going to have to enable IPv6 multicast throughout your network an=
yway, wouldn&#8217;t it be a good idea to do so sooner than later? </span><=
o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-mar=
gin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNorma=
l style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ron</span><o:p></o:p></p><p class=3DMso=
Normal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>=
&nbsp;</span><o:p></o:p></p><div style=3D'border:none;border-left:solid blu=
e 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-to=
p:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Qiong [mailto:<=
a href=3D"mailto:bingxuere@gmail.com" target=3D"_blank">bingxuere@gmail.com=
</a>] <br><b>Sent:</b> Tuesday, June 12, 2012 10:11 AM<br><b>To:</b> Lenny =
Giuliano<br><b>Cc:</b> MBONED WG; Ronald Bonica</span><o:p></o:p></p><div><=
p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:=
auto'><br><b>Subject:</b> Re: [MBONED] Multicast transition work in MBONED<=
o:p></o:p></p></div></div></div><p class=3DMsoNormal style=3D'mso-margin-to=
p-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><p class=3DMsoN=
ormal style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>Dear all,<o:p>=
</o:p></p><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;m=
so-margin-bottom-alt:auto'><br><br>1. In our situation, the source may stil=
l remian in IPv4, while the receiver will be IPv6-only since there is no mo=
re IPv4 address anymore. However, the network might be IPv4-only, which can=
 not support IPv6 multicast yet; or the network can support IPv6 multicast.=
 This is the case of 6-4. <br>Another situation is: the access network is s=
till IPv4-only, and the core netowrk (or application platform) is IPv6, the=
n that is the case of 6-4-6-4.<br><br>2. Use case: 3.2, 3.4,<br><br>Best wi=
shes<br>Qiong<o:p></o:p></p></div></div><div><div><div><p class=3DMsoNormal=
 style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Fri, Jun 8=
, 2012 at 4:34 AM, Leonard Giuliano &lt;<a href=3D"mailto:lenny@juniper.net=
" target=3D"_blank">lenny@juniper.net</a>&gt; wrote:<o:p></o:p></p><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><=
br>The multicast transition work within MBONED was initially intended to co=
nsist of ~ 3 document with limited scope. &nbsp;In a very short amount of t=
ime, we've seen 7 drafts (and counting) with scope widening.<br><br>In orde=
r to make sure we are focusing on work that is of actual value to the commu=
nity and prevent a flood of high volume/low value drafts, we would like to =
revisit the basic questions of multicast transition within MBONED. &nbsp;We=
 would like to hear answers from the WG to the following questions before c=
ontinuing any work on multicast transition in MBONED:<br><br>1) Which opera=
tors intend to source multicast traffic from one IP version and receive it =
over another IP version?<br><br>2) For those who answer 1), please identify=
 the use-cases of interest in draft-ietf-mboned-v4v6-mcast-ps so we can lim=
it discussion to solutions for those use cases.<br><br><br>MBONED Chairs<br=
>_______________________________________________<br>MBONED mailing list<br>=
<a href=3D"mailto:MBONED@ietf.org" target=3D"_blank">MBONED@ietf.org</a><br=
><a href=3D"https://www.ietf.org/mailman/listinfo/mboned" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/mboned</a><o:p></o:p></p></div><p cl=
ass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
'>&nbsp;<o:p></o:p></p></div></div></div></div></div></div><p class=3DMsoNo=
rmal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:=
p></o:p></p></div></div></div></div></div></div><p class=3DMsoNormal>&nbsp;=
<o:p></o:p></p></div></div></blockquote></div></div></body></html>=

--_000_13205C286662DE4387D9AF3AC30EF456D76EDCE440EMBX01WFjnprn_--

From Tina.Tsou.Zouting@huawei.com  Thu Jun 21 09:46:59 2012
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4936721F860F for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 09:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 gl4cafITXIBh for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 09:46:58 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id DB9B621F85EA for <mboned@ietf.org>; Thu, 21 Jun 2012 09:46:57 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHJ71699; Thu, 21 Jun 2012 12:46:57 -0400 (EDT)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 21 Jun 2012 09:45:48 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.109]) by dfweml404-hub.china.huawei.com ([10.193.5.203]) with mapi id 14.01.0323.003; Thu, 21 Jun 2012 09:45:44 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: AQHNRO2IJbQ/FDofPUmTNMjuOmtYFZb3NfMAgAl9swCAALcMgIACA8EAgAAaSYCAAfS5AP//jc2vgAACxgCAAAK2XQ==
Date: Thu, 21 Jun 2012 16:45:44 +0000
Message-ID: <5A041654-83A8-46D7-8149-6286F05297F5@huawei.com>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net> <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com>, <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net> <3A85B6A1-9427-40C9-8D3A-307ACFECE13B@huawei.com>, <13205C286662DE4387D9AF3AC30EF456D76EDCE440@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76EDCE440@EMBX01-WF.jnpr.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_5A04165483A846D781496286F05297F5huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 16:46:59 -0000

--_000_5A04165483A846D781496286F05297F5huaweicom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

I remember Christian, Med and Nic are going to deployed 3.1. Roberta asked =
about 3.3.
Med is out of office these days. Hope the whole Europe is not all in vacati=
on.

Tina

On Jun 21, 2012, at 9:40 AM, "Ronald Bonica" <rbonica@juniper.net<mailto:rb=
onica@juniper.net>> wrote:

Do we have anybody who is going to deploy 3.1 or 3.3?

                                     Ron


From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
Sent: Thursday, June 21, 2012 12:26 PM
To: Ronald Bonica
Cc: Qiong; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

The original question Lenny asked did not including 3.1 and 3.3.
Lenny asked
"1) Which operators intend to source multicast traffic from one IP version =
and receive it over another IP version?"
3.1 is 4-6-4
3.2 is 6-4-6.
So they r not In the scope of Lenny's question.

Tina

On Jun 21, 2012, at 9:16 AM, "Ronald Bonica" <rbonica@juniper.net<mailto:rb=
onica@juniper.net>> wrote:
Folks,

So it looks like use-cases 3.2, 3.4 and 3.5 may see deployment. There were =
no takers for use-cases 3.1 and 3.3.

In http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html, Simon=
 Perrault suggests two solutions for 3.4 and 3.5. Does the WG agree that th=
ose are the solutions that we should run with?

Simon=92s solutions can also be applied to use-case 3.2 if we tunnel over n=
on-multicast enabled IPv4 segment. Does everyone agree that that is a good =
idea?

                                                    Ron

From: Qiong [mailto:bingxuere@gmail.com]
Sent: Wednesday, June 20, 2012 6:23 AM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

For your question, it would be too difficult to give you an acurate number =
of money/effort, but I can tell you our situation of network upgradation.

In the transition period, it would be impossible to replace all the legacy =
IPv4-only devices, especially a great many access network devices. So actua=
lly, the process would be taken firstly towards our customers and new regio=
n. For example, a new customer might get a new  STB with IPv6 functionality=
. However, this new customer might access some region only with old devices=
, then at that time, it will be of great help to implement some MLTRANS sol=
utions in the new STB or deploy limited devices in the network. I believe t=
his will cost less than upgrading the whole network in the first place.

For old customers, they will still use IPv4 as they already got address, un=
less we upgrade their STB to support IPv6 remotely. But it is not the first=
 priority point.

Best wishes
Qiong
On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica <rbonica@juniper.net<mailto:=
rbonica@juniper.net>> wrote:
Qiong,

Which of the following do you think will require more money/effort:


-          To deploy IPv6 multicast throughout your network

-          To deploy the MLTRANS mechanisms that you will require to compen=
sate for the lack the above mentioned capability

How much more money/effort? Why?

                                                 Ron


From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Monday, June 18, 2012 10:03 PM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG

Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

I agree we do would like to enable IPv6 multicast in our network. However, =
all these things can not be achieved within one night. We still have a lot =
of old devices which can not support IPv6 multicast in our network, but we =
are running out of IPv4 address right now. So we can not wait until the who=
le network is ready for IPv6 multicast.

Hope it clarifies.

Best wishes
Qiong
On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica <rbonica@juniper.net<mailto=
:rbonica@juniper.net>> wrote:
Hi Qiong,

If you were to enable IPv6 multicast throughout your network before deployi=
ng IPv6 only receivers, would you not fall into use cases 3.4 and 3.5 (the =
dual stack scenarios). Since you are going to have to enable IPv6 multicast=
 throughout your network anyway, wouldn=92t it be a good idea to do so soon=
er than later?

                                                                      Ron

From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Tuesday, June 12, 2012 10:11 AM
To: Lenny Giuliano
Cc: MBONED WG; Ronald Bonica

Subject: Re: [MBONED] Multicast transition work in MBONED

Dear all,


1. In our situation, the source may still remian in IPv4, while the receive=
r will be IPv6-only since there is no more IPv4 address anymore. However, t=
he network might be IPv4-only, which can not support IPv6 multicast yet; or=
 the network can support IPv6 multicast. This is the case of 6-4.
Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.

2. Use case: 3.2, 3.4,

Best wishes
Qiong
On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <lenny@juniper.net<mailto:=
lenny@juniper.net>> wrote:

The multicast transition work within MBONED was initially intended to consi=
st of ~ 3 document with limited scope.  In a very short amount of time, we'=
ve seen 7 drafts (and counting) with scope widening.

In order to make sure we are focusing on work that is of actual value to th=
e community and prevent a flood of high volume/low value drafts, we would l=
ike to revisit the basic questions of multicast transition within MBONED.  =
We would like to hear answers from the WG to the following questions before=
 continuing any work on multicast transition in MBONED:

1) Which operators intend to source multicast traffic from one IP version a=
nd receive it over another IP version?

2) For those who answer 1), please identify the use-cases of interest in dr=
aft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions for t=
hose use cases.


MBONED Chairs
_______________________________________________
MBONED mailing list
MBONED@ietf.org<mailto:MBONED@ietf.org>
https://www.ietf.org/mailman/listinfo/mboned




--_000_5A04165483A846D781496286F05297F5huaweicom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body bgcolor=3D"#FFFFFF">
<div>I remember Christian, Med and Nic are going to deployed 3.1. Roberta a=
sked about 3.3.</div>
<div>Med is out of office these days. Hope the whole Europe is not all in v=
acation.<br>
<br>
Tina</div>
<div><br>
On Jun 21, 2012, at 9:40 AM, &quot;Ronald Bonica&quot; &lt;<a href=3D"mailt=
o:rbonica@juniper.net">rbonica@juniper.net</a>&gt; wrote:<br>
<br>
</div>
<div></div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Do we have anybody who is=
 going to deploy 3.1 or 3.3?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ron<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tina TSO=
U [mailto:Tina.Tsou.Zouting@huawei.com]
<br>
<b>Sent:</b> Thursday, June 21, 2012 12:26 PM<br>
<b>To:</b> Ronald Bonica<br>
<b>Cc:</b> Qiong; MBONED WG<br>
<b>Subject:</b> Re: [MBONED] Multicast transition work in MBONED<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">The original question Lenny asked did not including =
3.1 and 3.3.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Lenny asked<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;<tt><span style=3D"font-size:10.0pt">1) Which =
operators intend to source multicast traffic from one IP version&nbsp;and r=
eceive it over another IP version?&quot;</span></tt><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
3.1 is 4-6-4</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
3.2 is 6-4-6.</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">So they r not In the scope of Lenny's question.<o:p>=
</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Tina<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 21, 2012, at 9:16 AM, &quot;Ronald Bonica&quot; &lt;<a href=3D"mailt=
o:rbonica@juniper.net">rbonica@juniper.net</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Folks,</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">So it looks like use-case=
s 3.2, 3.4 and 3.5 may see deployment. There were no takers for use-cases 3=
.1 and 3.3.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In
<a href=3D"http://www.ietf.org/mail-archive/web/mboned/current/msg01607.htm=
l">http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html</a>, S=
imon Perrault suggests two solutions for 3.4 and 3.5. Does the WG agree tha=
t those are the solutions that we
 should run with?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Simon=92s solutions can a=
lso be applied to use-case 3.2 if we tunnel over non-multicast enabled IPv4=
 segment. Does everyone agree that that is a good idea?</span><o:p></o:p></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ron</span><o:p></o=
:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Qiong [<=
a href=3D"mailto:bingxuere@gmail.com">mailto:bingxuere@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, June 20, 2012 6:23 AM<br>
<b>To:</b> Ronald Bonica<br>
<b>Cc:</b> Lenny Giuliano; MBONED WG<br>
<b>Subject:</b> Re: [MBONED] Multicast transition work in MBONED</span><o:p=
></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Hi Ronald,<br>
<br>
For your question, it would be too difficult to give you an acurate number =
of money/effort, but I can tell you our situation of network upgradation.
<br>
<br>
In the transition period, it would be impossible to replace all the legacy =
IPv4-only devices, especially a great many access network devices. So actua=
lly, the process would be taken firstly towards our customers and new regio=
n. For example, a new customer might
 get a new&nbsp; STB with IPv6 functionality. However, this new customer mi=
ght access some region only with old devices, then at that time, it will be=
 of great help to implement some MLTRANS solutions in the new STB or deploy=
 limited devices in the network. I believe
 this will cost less than upgrading the whole network in the first place. <=
br>
<br>
For old customers, they will still use IPv4 as they already got address, un=
less we upgrade their STB to support IPv6 remotely. But it is not the first=
 priority point.<br>
<br>
Best wishes<br>
Qiong<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica &lt;<=
a href=3D"mailto:rbonica@juniper.net" target=3D"_blank">rbonica@juniper.net=
</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Qiong,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Which of the following do you think wil=
l require more money/effort:</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">-</span><span style=3D"font-size:7.0pt;color:=
#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">To deploy IPv6 multicast throughout your =
network</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">-</span><span style=3D"font-size:7.0pt;color:=
#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">To deploy the MLTRANS mechanisms that you=
 will require to compensate for the lack the above mentioned capability</sp=
an><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">How much more money/effort? Why?</span>=
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; Ron</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Qiong [mailto:<a href=
=3D"mailto:bingxuere@gmail.com" target=3D"_blank">bingxuere@gmail.com</a>]
<br>
<b>Sent:</b> Monday, June 18, 2012 10:03 PM<br>
<b>To:</b> Ronald Bonica<br>
<b>Cc:</b> Lenny Giuliano; MBONED WG</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [MBONED] Multicast transition work in MBONED<o:p></o:p>=
</p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">Hi Ronald,<br>
<br>
I agree we do would like to enable IPv6 multicast in our network. However, =
all these things can not be achieved within one night. We still have a lot =
of old devices which can not support IPv6 multicast in our network, but we =
are running out of IPv4 address
 right now. So we can not wait until the whole network is ready for IPv6 mu=
lticast.<br>
<br>
Hope it clarifies.<br>
<br>
Best wishes<br>
Qiong<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica &lt;<a href=3D"mai=
lto:rbonica@juniper.net" target=3D"_blank">rbonica@juniper.net</a>&gt; wrot=
e:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Hi Qiong,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">If you were to enable IPv6 multicast th=
roughout your network before deploying IPv6 only receivers,
 would you not fall into use cases 3.4 and 3.5 (the dual stack scenarios). =
Since you are going to have to enable IPv6 multicast throughout your networ=
k anyway, wouldn=92t it be a good idea to do so sooner than later?
</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Ron</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Qiong [mailto:<a href=
=3D"mailto:bingxuere@gmail.com" target=3D"_blank">bingxuere@gmail.com</a>]
<br>
<b>Sent:</b> Tuesday, June 12, 2012 10:11 AM<br>
<b>To:</b> Lenny Giuliano<br>
<b>Cc:</b> MBONED WG; Ronald Bonica</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<b>Subject:</b> Re: [MBONED] Multicast transition work in MBONED<o:p></o:p>=
</p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">Dear all,<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<br>
1. In our situation, the source may still remian in IPv4, while the receive=
r will be IPv6-only since there is no more IPv4 address anymore. However, t=
he network might be IPv4-only, which can not support IPv6 multicast yet; or=
 the network can support IPv6 multicast.
 This is the case of 6-4. <br>
Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.=
<br>
<br>
2. Use case: 3.2, 3.4,<br>
<br>
Best wishes<br>
Qiong<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano &lt;<a href=3D"ma=
ilto:lenny@juniper.net" target=3D"_blank">lenny@juniper.net</a>&gt; wrote:<=
o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
The multicast transition work within MBONED was initially intended to consi=
st of ~ 3 document with limited scope. &nbsp;In a very short amount of time=
, we've seen 7 drafts (and counting) with scope widening.<br>
<br>
In order to make sure we are focusing on work that is of actual value to th=
e community and prevent a flood of high volume/low value drafts, we would l=
ike to revisit the basic questions of multicast transition within MBONED. &=
nbsp;We would like to hear answers from
 the WG to the following questions before continuing any work on multicast =
transition in MBONED:<br>
<br>
1) Which operators intend to source multicast traffic from one IP version a=
nd receive it over another IP version?<br>
<br>
2) For those who answer 1), please identify the use-cases of interest in dr=
aft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions for t=
hose use cases.<br>
<br>
<br>
MBONED Chairs<br>
_______________________________________________<br>
MBONED mailing list<br>
<a href=3D"mailto:MBONED@ietf.org" target=3D"_blank">MBONED@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mboned" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mboned</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</body>
</html>

--_000_5A04165483A846D781496286F05297F5huaweicom_--

From rbonica@juniper.net  Thu Jun 21 10:01:51 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3302721F858E for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 10:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.275
X-Spam-Level: 
X-Spam-Status: No, score=-106.275 tagged_above=-999 required=5 tests=[AWL=-0.276, BAYES_00=-2.599, J_CHICKENPOX_51=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 CEdQbbsB+Olu for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 10:01:50 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB2A21F8589 for <mboned@ietf.org>; Thu, 21 Jun 2012 10:01:50 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKT+NTfVBwUyC18eOWJrEPCojLf85fMag4@postini.com; Thu, 21 Jun 2012 10:01:50 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 21 Jun 2012 09:59:49 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 21 Jun 2012 12:59:29 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Thu, 21 Jun 2012 12:59:28 -0400
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: Ac1PytjX8js/0igMTaO85KIXl+mVdwAA6oWA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76EDCE4B7@EMBX01-WF.jnpr.net>
References: <mailman.2415.1340296084.3336.mboned@ietf.org>
In-Reply-To: <mailman.2415.1340296084.3336.mboned@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 17:01:51 -0000

Simon,

Sorry. The email that I reference was to you and from Bert Manfredi. The tw=
o solutions were:

- source the traffic twice, once in IPv4 and again in IPv6
- allow sources to transmit either v4 or v6, and then to do the translation=
 at the destination edge routers, based on whether these edge routers recei=
ve IGMP or MLD join reports.

The advantage of the former is that it is simple. The disadvantage is that =
some streams will traverse some links twice (once in IPv4 and again in IPv6=
).

The advantage of the later is that it conserves bandwidth. The disadvantage=
, in Bert's words is "that it is messier".

                                              Ron

>=20
> Message: 1
> Date: Thu, 21 Jun 2012 12:28:02 -0400
> From: Simon Perreault <simon.perreault@viagenie.ca>
> To: mboned@ietf.org
> Subject: Re: [MBONED] Multicast transition work in MBONED
> Message-ID: <4FE34B92.5090103@viagenie.ca>
> Content-Type: text/plain; charset=3Dwindows-1252; format=3Dflowed
>=20
> On 2012-06-21 12:14, Ronald Bonica wrote:
> > In http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html,
> > Simon Perrault suggests two solutions for 3.4 and 3.5. Does the WG
> > agree that those are the solutions that we should run with?
> >
> > Simon?s solutions can also be applied to use-case 3.2 if we tunnel
> > over non-multicast enabled IPv4 segment. Does everyone agree that
> that
> > is a good idea?
>=20
> Maybe it is the wrong URL or the wrong person, but I don't know what
> solutions you're talking about, sorry. Could you please summarize them?
>=20
> Thanks,
> Simon
> --

From rbonica@juniper.net  Thu Jun 21 10:13:14 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04FD421F873C for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 10:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.569
X-Spam-Level: 
X-Spam-Status: No, score=-106.569 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 fSfRhLiiavTa for <mboned@ietfa.amsl.com>; Thu, 21 Jun 2012 10:13:10 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 528DA21F8723 for <mboned@ietf.org>; Thu, 21 Jun 2012 10:13:08 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKT+NWI1jFSPdxex0B4uSXi+28aBxD8DLY@postini.com; Thu, 21 Jun 2012 10:13:09 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 21 Jun 2012 10:12:34 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 21 Jun 2012 13:12:22 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Date: Thu, 21 Jun 2012 13:12:20 -0400
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: AQHNRO2IJbQ/FDofPUmTNMjuOmtYFZb3NfMAgAl9swCAALcMgIACA8EAgAAaSYCAAfS5AP//jc2vgAACxgCAAAK2XYAABGhA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76EDCE4FE@EMBX01-WF.jnpr.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net> <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com>, <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net> <3A85B6A1-9427-40C9-8D3A-307ACFECE13B@huawei.com>, <13205C286662DE4387D9AF3AC30EF456D76EDCE440@EMBX01-WF.jnpr.net> <5A041654-83A8-46D7-8149-6286F05297F5@huawei.com>
In-Reply-To: <5A041654-83A8-46D7-8149-6286F05297F5@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_13205C286662DE4387D9AF3AC30EF456D76EDCE4FEEMBX01WFjnprn_"
MIME-Version: 1.0
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 17:13:14 -0000

--_000_13205C286662DE4387D9AF3AC30EF456D76EDCE4FEEMBX01WFjnprn_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Tina,

It seems that the simplest solution in uses case 3.1  would be to deploy du=
al-stack in the network. Maybe Chris and Med, Nic  could explain why this i=
s not the case?

                                                     Ron

From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
Sent: Thursday, June 21, 2012 12:46 PM
To: Ronald Bonica
Cc: Qiong; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

I remember Christian, Med and Nic are going to deployed 3.1. Roberta asked =
about 3.3.
Med is out of office these days. Hope the whole Europe is not all in vacati=
on.

Tina

On Jun 21, 2012, at 9:40 AM, "Ronald Bonica" <rbonica@juniper.net<mailto:rb=
onica@juniper.net>> wrote:
Do we have anybody who is going to deploy 3.1 or 3.3?

                                     Ron


From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
Sent: Thursday, June 21, 2012 12:26 PM
To: Ronald Bonica
Cc: Qiong; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

The original question Lenny asked did not including 3.1 and 3.3.
Lenny asked
"1) Which operators intend to source multicast traffic from one IP version =
and receive it over another IP version?"
3.1 is 4-6-4
3.2 is 6-4-6.
So they r not In the scope of Lenny's question.

Tina

On Jun 21, 2012, at 9:16 AM, "Ronald Bonica" <rbonica@juniper.net<mailto:rb=
onica@juniper.net>> wrote:
Folks,

So it looks like use-cases 3.2, 3.4 and 3.5 may see deployment. There were =
no takers for use-cases 3.1 and 3.3.

In http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html, Simon=
 Perrault suggests two solutions for 3.4 and 3.5. Does the WG agree that th=
ose are the solutions that we should run with?

Simon's solutions can also be applied to use-case 3.2 if we tunnel over non=
-multicast enabled IPv4 segment. Does everyone agree that that is a good id=
ea?

                                                    Ron

From: Qiong [mailto:bingxuere@gmail.com]
Sent: Wednesday, June 20, 2012 6:23 AM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

For your question, it would be too difficult to give you an acurate number =
of money/effort, but I can tell you our situation of network upgradation.

In the transition period, it would be impossible to replace all the legacy =
IPv4-only devices, especially a great many access network devices. So actua=
lly, the process would be taken firstly towards our customers and new regio=
n. For example, a new customer might get a new  STB with IPv6 functionality=
. However, this new customer might access some region only with old devices=
, then at that time, it will be of great help to implement some MLTRANS sol=
utions in the new STB or deploy limited devices in the network. I believe t=
his will cost less than upgrading the whole network in the first place.

For old customers, they will still use IPv4 as they already got address, un=
less we upgrade their STB to support IPv6 remotely. But it is not the first=
 priority point.

Best wishes
Qiong
On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica <rbonica@juniper.net<mailto:=
rbonica@juniper.net>> wrote:
Qiong,

Which of the following do you think will require more money/effort:


-          To deploy IPv6 multicast throughout your network

-          To deploy the MLTRANS mechanisms that you will require to compen=
sate for the lack the above mentioned capability

How much more money/effort? Why?

                                                 Ron


From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Monday, June 18, 2012 10:03 PM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG

Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

I agree we do would like to enable IPv6 multicast in our network. However, =
all these things can not be achieved within one night. We still have a lot =
of old devices which can not support IPv6 multicast in our network, but we =
are running out of IPv4 address right now. So we can not wait until the who=
le network is ready for IPv6 multicast.

Hope it clarifies.

Best wishes
Qiong
On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica <rbonica@juniper.net<mailto=
:rbonica@juniper.net>> wrote:
Hi Qiong,

If you were to enable IPv6 multicast throughout your network before deployi=
ng IPv6 only receivers, would you not fall into use cases 3.4 and 3.5 (the =
dual stack scenarios). Since you are going to have to enable IPv6 multicast=
 throughout your network anyway, wouldn't it be a good idea to do so sooner=
 than later?

                                                                      Ron

From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Tuesday, June 12, 2012 10:11 AM
To: Lenny Giuliano
Cc: MBONED WG; Ronald Bonica

Subject: Re: [MBONED] Multicast transition work in MBONED

Dear all,


1. In our situation, the source may still remian in IPv4, while the receive=
r will be IPv6-only since there is no more IPv4 address anymore. However, t=
he network might be IPv4-only, which can not support IPv6 multicast yet; or=
 the network can support IPv6 multicast. This is the case of 6-4.
Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.

2. Use case: 3.2, 3.4,

Best wishes
Qiong
On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <lenny@juniper.net<mailto:=
lenny@juniper.net>> wrote:

The multicast transition work within MBONED was initially intended to consi=
st of ~ 3 document with limited scope.  In a very short amount of time, we'=
ve seen 7 drafts (and counting) with scope widening.

In order to make sure we are focusing on work that is of actual value to th=
e community and prevent a flood of high volume/low value drafts, we would l=
ike to revisit the basic questions of multicast transition within MBONED.  =
We would like to hear answers from the WG to the following questions before=
 continuing any work on multicast transition in MBONED:

1) Which operators intend to source multicast traffic from one IP version a=
nd receive it over another IP version?

2) For those who answer 1), please identify the use-cases of interest in dr=
aft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions for t=
hose use cases.


MBONED Chairs
_______________________________________________
MBONED mailing list
MBONED@ietf.org<mailto:MBONED@ietf.org>
https://www.ietf.org/mailman/listinfo/mboned




--_000_13205C286662DE4387D9AF3AC30EF456D76EDCE4FEEMBX01WFjnprn_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>Tina,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fa=
mily:"Calibri","sans-serif";color:#1F497D'>It seems that the simplest solut=
ion in uses case 3.1 &nbsp;would be to deploy dual-stack in the network. Ma=
ybe Chris and Med, Nic &nbsp;could explain why this is not the case?<o:p></=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fa=
mily:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ron<o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border=
-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'border=
:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3D=
MsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-ser=
if"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'> Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com] <br><b>Sent:<=
/b> Thursday, June 21, 2012 12:46 PM<br><b>To:</b> Ronald Bonica<br><b>Cc:<=
/b> Qiong; MBONED WG<br><b>Subject:</b> Re: [MBONED] Multicast transition w=
ork in MBONED<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p><div><p class=3DMsoNormal>I remember Christian, Med and Nic a=
re going to deployed 3.1. Roberta asked about 3.3.<o:p></o:p></p></div><div=
><p class=3DMsoNormal>Med is out of office these days. Hope the whole Europ=
e is not all in vacation.<br><br>Tina<o:p></o:p></p></div><div><p class=3DM=
soNormal style=3D'margin-bottom:12.0pt'><br>On Jun 21, 2012, at 9:40 AM, &q=
uot;Ronald Bonica&quot; &lt;<a href=3D"mailto:rbonica@juniper.net">rbonica@=
juniper.net</a>&gt; wrote:<o:p></o:p></p></div><blockquote style=3D'margin-=
top:5.0pt;margin-bottom:5.0pt'><div><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Do we have =
anybody who is going to deploy 3.1 or 3.3? </span><o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ron</sp=
an><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font=
-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><=
p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","=
sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><div style=3D'border=
:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div sty=
le=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'=
><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-famil=
y:"Tahoma","sans-serif"'> Tina TSOU [<a href=3D"mailto:Tina.Tsou.Zouting@hu=
awei.com">mailto:Tina.Tsou.Zouting@huawei.com</a>] <br><b>Sent:</b> Thursda=
y, June 21, 2012 12:26 PM<br><b>To:</b> Ronald Bonica<br><b>Cc:</b> Qiong; =
MBONED WG<br><b>Subject:</b> Re: [MBONED] Multicast transition work in MBON=
ED</span><o:p></o:p></p></div></div><p class=3DMsoNormal>&nbsp;<o:p></o:p><=
/p><div><p class=3DMsoNormal>The original question Lenny asked did not incl=
uding 3.1 and 3.3.<o:p></o:p></p></div><div><p class=3DMsoNormal>Lenny aske=
d<o:p></o:p></p></div><div><p class=3DMsoNormal>&quot;<tt><span style=3D'fo=
nt-size:10.0pt'>1) Which operators intend to source multicast traffic from =
one IP version&nbsp;and receive it over another IP version?&quot;</span></t=
t><o:p></o:p></p></div><div><p class=3DMsoNormal><span style=3D'font-family=
:"Courier New"'>3.1 is 4-6-4</span><o:p></o:p></p></div><div><p class=3DMso=
Normal><span style=3D'font-family:"Courier New"'>3.2 is 6-4-6.</span><o:p><=
/o:p></p></div><div><p class=3DMsoNormal>So they r not In the scope of Lenn=
y's question.<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp;<o:p></o:=
p></p></div><div><p class=3DMsoNormal>Tina<o:p></o:p></p></div><div><p clas=
s=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>On Jun 21, 2012, at 9:16 A=
M, &quot;Ronald Bonica&quot; &lt;<a href=3D"mailto:rbonica@juniper.net">rbo=
nica@juniper.net</a>&gt; wrote:<o:p></o:p></p></div><blockquote style=3D'ma=
rgin-top:5.0pt;margin-bottom:5.0pt'><div><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Folk=
s,</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p=
></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'>So it looks like use-cases 3.2, 3.4 and 3.=
5 may see deployment. There were no takers for use-cases 3.1 and 3.3.</span=
><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'>In <a href=3D"http://www.ietf.org/mail-archive/web=
/mboned/current/msg01607.html">http://www.ietf.org/mail-archive/web/mboned/=
current/msg01607.html</a>, Simon Perrault suggests two solutions for 3.4 an=
d 3.5. Does the WG agree that those are the solutions that we should run wi=
th?</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:=
p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'>Simon&#8217;s solutions can also be appli=
ed to use-case 3.2 if we tunnel over non-multicast enabled IPv4 segment. Do=
es everyone agree that that is a good idea?</span><o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;Ron</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-s=
ize:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><=
o:p></o:p></p><div style=3D'border:none;border-left:solid blue 1.5pt;paddin=
g:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4D=
F 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Qiong [<a href=
=3D"mailto:bingxuere@gmail.com">mailto:bingxuere@gmail.com</a>] <br><b>Sent=
:</b> Wednesday, June 20, 2012 6:23 AM<br><b>To:</b> Ronald Bonica<br><b>Cc=
:</b> Lenny Giuliano; MBONED WG<br><b>Subject:</b> Re: [MBONED] Multicast t=
ransition work in MBONED</span><o:p></o:p></p></div></div><p class=3DMsoNor=
mal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt=
'>Hi Ronald,<br><br>For your question, it would be too difficult to give yo=
u an acurate number of money/effort, but I can tell you our situation of ne=
twork upgradation. <br><br>In the transition period, it would be impossible=
 to replace all the legacy IPv4-only devices, especially a great many acces=
s network devices. So actually, the process would be taken firstly towards =
our customers and new region. For example, a new customer might get a new&n=
bsp; STB with IPv6 functionality. However, this new customer might access s=
ome region only with old devices, then at that time, it will be of great he=
lp to implement some MLTRANS solutions in the new STB or deploy limited dev=
ices in the network. I believe this will cost less than upgrading the whole=
 network in the first place. <br><br>For old customers, they will still use=
 IPv4 as they already got address, unless we upgrade their STB to support I=
Pv6 remotely. But it is not the first priority point.<br><br>Best wishes<br=
>Qiong<o:p></o:p></p><div><p class=3DMsoNormal>On Wed, Jun 20, 2012 at 4:48=
 PM, Ronald Bonica &lt;<a href=3D"mailto:rbonica@juniper.net" target=3D"_bl=
ank">rbonica@juniper.net</a>&gt; wrote:<o:p></o:p></p><div><div><p class=3D=
MsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Qiong,</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p=
 class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:a=
uto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";col=
or:#1F497D'>Which of the following do you think will require more money/eff=
ort:</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:=
auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-famil=
y:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>-</span><span style=3D'font-size:7.0pt;color:#1F497D'>&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'>To deploy IPv6 multicast=
 throughout your network</span><o:p></o:p></p><p><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span style=
=3D'font-size:7.0pt;color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; </span><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'>To deploy the MLTRANS mechanisms that you will=
 require to compensate for the lack the above mentioned capability</span><o=
:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-marg=
in-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","=
sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal=
 style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>How =
much more money/effort? Why?</span><o:p></o:p></p><p class=3DMsoNormal styl=
e=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Ron</span><o:p></o:p></p><p class=3DMsoNormal style=3D'=
mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:=
p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margi=
n-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><div style=3D'border:=
none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div styl=
e=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>=
<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","san=
s-serif"'> Qiong [mailto:<a href=3D"mailto:bingxuere@gmail.com" target=3D"_=
blank">bingxuere@gmail.com</a>] <br><b>Sent:</b> Monday, June 18, 2012 10:0=
3 PM<br><b>To:</b> Ronald Bonica<br><b>Cc:</b> Lenny Giuliano; MBONED WG</s=
pan><o:p></o:p></p><div><div><p class=3DMsoNormal><br><b>Subject:</b> Re: [=
MBONED] Multicast transition work in MBONED<o:p></o:p></p></div></div></div=
></div><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><p class=3DMsoNormal style=3D'=
mso-margin-top-alt:auto;margin-bottom:12.0pt'>Hi Ronald,<br><br>I agree we =
do would like to enable IPv6 multicast in our network. However, all these t=
hings can not be achieved within one night. We still have a lot of old devi=
ces which can not support IPv6 multicast in our network, but we are running=
 out of IPv4 address right now. So we can not wait until the whole network =
is ready for IPv6 multicast.<br><br>Hope it clarifies.<br><br>Best wishes<b=
r>Qiong<o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso-margin-top-alt=
:auto;mso-margin-bottom-alt:auto'>On Mon, Jun 18, 2012 at 11:07 PM, Ronald =
Bonica &lt;<a href=3D"mailto:rbonica@juniper.net" target=3D"_blank">rbonica=
@juniper.net</a>&gt; wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal st=
yle=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Qiong,=
</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto=
;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"C=
alibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3D=
MsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>If you were to enable IPv6 multicast throughout your network before depl=
oying IPv6 only receivers, would you not fall into use cases 3.4 and 3.5 (t=
he dual stack scenarios). Since you are going to have to enable IPv6 multic=
ast throughout your network anyway, wouldn&#8217;t it be a good idea to do =
so sooner than later? </span><o:p></o:p></p><p class=3DMsoNormal style=3D'm=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p=
></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin=
-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ron</span>=
<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><div style=3D'bord=
er:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div s=
tyle=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0i=
n'><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-ser=
if"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'> Qiong [mailto:<a href=3D"mailto:bingxuere@gmail.com" target=
=3D"_blank">bingxuere@gmail.com</a>] <br><b>Sent:</b> Tuesday, June 12, 201=
2 10:11 AM<br><b>To:</b> Lenny Giuliano<br><b>Cc:</b> MBONED WG; Ronald Bon=
ica</span><o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso-margin-top-=
alt:auto;mso-margin-bottom-alt:auto'><br><b>Subject:</b> Re: [MBONED] Multi=
cast transition work in MBONED<o:p></o:p></p></div></div></div><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp=
;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;margi=
n-bottom:12.0pt'>Dear all,<o:p></o:p></p><div><div><p class=3DMsoNormal sty=
le=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><br>1. In our=
 situation, the source may still remian in IPv4, while the receiver will be=
 IPv6-only since there is no more IPv4 address anymore. However, the networ=
k might be IPv4-only, which can not support IPv6 multicast yet; or the netw=
ork can support IPv6 multicast. This is the case of 6-4. <br>Another situat=
ion is: the access network is still IPv4-only, and the core netowrk (or app=
lication platform) is IPv6, then that is the case of 6-4-6-4.<br><br>2. Use=
 case: 3.2, 3.4,<br><br>Best wishes<br>Qiong<o:p></o:p></p></div></div><div=
><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin=
-bottom-alt:auto'>On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano &lt;<a h=
ref=3D"mailto:lenny@juniper.net" target=3D"_blank">lenny@juniper.net</a>&gt=
; wrote:<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:aut=
o;mso-margin-bottom-alt:auto'><br>The multicast transition work within MBON=
ED was initially intended to consist of ~ 3 document with limited scope. &n=
bsp;In a very short amount of time, we've seen 7 drafts (and counting) with=
 scope widening.<br><br>In order to make sure we are focusing on work that =
is of actual value to the community and prevent a flood of high volume/low =
value drafts, we would like to revisit the basic questions of multicast tra=
nsition within MBONED. &nbsp;We would like to hear answers from the WG to t=
he following questions before continuing any work on multicast transition i=
n MBONED:<br><br>1) Which operators intend to source multicast traffic from=
 one IP version and receive it over another IP version?<br><br>2) For those=
 who answer 1), please identify the use-cases of interest in draft-ietf-mbo=
ned-v4v6-mcast-ps so we can limit discussion to solutions for those use cas=
es.<br><br><br>MBONED Chairs<br>___________________________________________=
____<br>MBONED mailing list<br><a href=3D"mailto:MBONED@ietf.org" target=3D=
"_blank">MBONED@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/lis=
tinfo/mboned" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mbone=
d</a><o:p></o:p></p></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:=
auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div></div></div></d=
iv></div></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div></div></div></div></div></=
div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div></blockquote></di=
v></div></blockquote></div></div></body></html>=

--_000_13205C286662DE4387D9AF3AC30EF456D76EDCE4FEEMBX01WFjnprn_--

From christian.jacquenet@orange.com  Fri Jun 22 01:34:20 2012
Return-Path: <christian.jacquenet@orange.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 938A921F867B for <mboned@ietfa.amsl.com>; Fri, 22 Jun 2012 01:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.247
X-Spam-Level: 
X-Spam-Status: No, score=-2.247 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
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 g6u93-nRizgO for <mboned@ietfa.amsl.com>; Fri, 22 Jun 2012 01:34:19 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 40B1221F8600 for <mboned@ietf.org>; Fri, 22 Jun 2012 01:34:18 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 6D0E22DC253; Fri, 22 Jun 2012 10:34:17 +0200 (CEST)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 527C44C015; Fri, 22 Jun 2012 10:34:17 +0200 (CEST)
Received: from PUEXCB1C.nanterre.francetelecom.fr ([10.101.44.11]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Fri, 22 Jun 2012 10:34:17 +0200
From: <christian.jacquenet@orange.com>
To: Ronald Bonica <rbonica@juniper.net>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Date: Fri, 22 Jun 2012 10:34:15 +0200
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: AQHNRO2IJbQ/FDofPUmTNMjuOmtYFZb3NfMAgAl9swCAALcMgIACA8EAgAAaSYCAAfS5AP//jc2vgAACxgCAAAK2XYAABGhAgAD9WXA=
Message-ID: <17386_1340354057_4FE42E09_17386_8210_1_983A1D8DA0DA5F4EB747BF34CBEE5CD15A0EF4E7E0@PUEXCB1C.nanterre.francetelecom.fr>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net> <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com>, <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net> <3A85B6A1-9427-40C9-8D3A-307ACFECE13B@huawei.com>, <13205C286662DE4387D9AF3AC30EF456D76EDCE440@EMBX01-WF.jnpr.net> <5A041654-83A8-46D7-8149-6286F05297F5@huawei.com> <13205C286662DE4387D9AF3AC30EF456D76EDCE4FE@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76EDCE4FE@EMBX01-WF.jnpr.net>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_983A1D8DA0DA5F4EB747BF34CBEE5CD15A0EF4E7E0PUEXCB1Cnante_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.6.22.65415
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 08:34:20 -0000

--_000_983A1D8DA0DA5F4EB747BF34CBEE5CD15A0EF4E7E0PUEXCB1Cnante_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Ron, all,

I have to admit I don't understand why this question about use cases is rai=
sed again and again, to second one of the comments that were made by Simon =
some time ago.

This effort initially started with the softwire http://datatracker.ietf.org=
/doc/draft-ietf-softwire-dslite-multicast/ draft, according to the section =
3 of the softwire WG charter (http://datatracker.ietf.org/wg/softwire/chart=
er/).

As per an initial request from the softwire WG chairs, several operators go=
t together to document the accompanying problem statement draft that has be=
en further elaborated with the integration of use cases in addition to the =
4-6-4 use case, and which has now become a mboned WG document, as per the p=
oll results that were confirmed some time ago.

I'm still wondering why the 4-6-4 use case should be ruled out, as it can b=
e seen as a consequence of the enforcement of a global IPv6 strategy that i=
ncludes (but is not limited to) the deployment of IPv6 multicast-enabled in=
frastructures combined with the introduction of techniques that are meant t=
o address the need to access IPv4 contents during the transition period whe=
re end customers will not be assigned a global IPv4 address anymore.

Such techniques include DS-Lite.

I'm not convinced that deploying DS multicast architectures would be simple=
r, but I'm sure such design will certainly not optimize bandwidth usage in =
(at least) the access infrastructures.

As for the use of an IPv6-only, multicast-enabled, access infrastructure, t=
his is something that has been slightly elaborated in the first bullet para=
graph of section 1 of http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mca=
st-ps-00#page-6, whereas some operators are currently moving from a service=
-specific, multi-PVC design scheme towards a service-agnostic, single PVC d=
esign scheme.

A service-agnostic, single PVC design scheme has the inevitable effect of i=
mporting global IPv4 address depletion issues into service environments whi=
ch used to rely upon a walled garden, RFC1918-based, design.

Combined with the introduction of DS-Lite, this leads to the 4-6-4 use case.

Note that the technical feasibility of what is documented in http://datatra=
cker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/ has already been de=
monstrated, thanks to a collaboration with a couple of vendors.

Is this 4-6-4 use case more complicated than a DS multicast design? Yes.

Is this messier? I don't think so, as it primarily depends on service provi=
der-specific operational procedures.

Besides, I'm not convinced that there is room for such hasty qualitative ap=
preciation at this stage of the effort.

I hope this will help closing the debate on the multicast transition use ca=
ses and that we will all move on. Finally.

Cheers,

Christian.




________________________________
De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] De la part de=
 Ronald Bonica
Envoy=E9 : jeudi 21 juin 2012 19:12
=C0 : Tina TSOU
Cc : MBONED WG
Objet : Re: [MBONED] Multicast transition work in MBONED

Tina,

It seems that the simplest solution in uses case 3.1  would be to deploy du=
al-stack in the network. Maybe Chris and Med, Nic  could explain why this i=
s not the case?

                                                     Ron

From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
Sent: Thursday, June 21, 2012 12:46 PM
To: Ronald Bonica
Cc: Qiong; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

I remember Christian, Med and Nic are going to deployed 3.1. Roberta asked =
about 3.3.
Med is out of office these days. Hope the whole Europe is not all in vacati=
on.

Tina

On Jun 21, 2012, at 9:40 AM, "Ronald Bonica" <rbonica@juniper.net<mailto:rb=
onica@juniper.net>> wrote:
Do we have anybody who is going to deploy 3.1 or 3.3?

                                     Ron


From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
Sent: Thursday, June 21, 2012 12:26 PM
To: Ronald Bonica
Cc: Qiong; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

The original question Lenny asked did not including 3.1 and 3.3.
Lenny asked
"1) Which operators intend to source multicast traffic from one IP version =
and receive it over another IP version?"
3.1 is 4-6-4
3.2 is 6-4-6.
So they r not In the scope of Lenny's question.

Tina

On Jun 21, 2012, at 9:16 AM, "Ronald Bonica" <rbonica@juniper.net<mailto:rb=
onica@juniper.net>> wrote:
Folks,

So it looks like use-cases 3.2, 3.4 and 3.5 may see deployment. There were =
no takers for use-cases 3.1 and 3.3.

In http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html, Simon=
 Perrault suggests two solutions for 3.4 and 3.5. Does the WG agree that th=
ose are the solutions that we should run with?

Simon's solutions can also be applied to use-case 3.2 if we tunnel over non=
-multicast enabled IPv4 segment. Does everyone agree that that is a good id=
ea?

                                                    Ron

From: Qiong [mailto:bingxuere@gmail.com]
Sent: Wednesday, June 20, 2012 6:23 AM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

For your question, it would be too difficult to give you an acurate number =
of money/effort, but I can tell you our situation of network upgradation.

In the transition period, it would be impossible to replace all the legacy =
IPv4-only devices, especially a great many access network devices. So actua=
lly, the process would be taken firstly towards our customers and new regio=
n. For example, a new customer might get a new  STB with IPv6 functionality=
. However, this new customer might access some region only with old devices=
, then at that time, it will be of great help to implement some MLTRANS sol=
utions in the new STB or deploy limited devices in the network. I believe t=
his will cost less than upgrading the whole network in the first place.

For old customers, they will still use IPv4 as they already got address, un=
less we upgrade their STB to support IPv6 remotely. But it is not the first=
 priority point.

Best wishes
Qiong
On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica <rbonica@juniper.net<mailto:=
rbonica@juniper.net>> wrote:
Qiong,

Which of the following do you think will require more money/effort:


-          To deploy IPv6 multicast throughout your network

-          To deploy the MLTRANS mechanisms that you will require to compen=
sate for the lack the above mentioned capability

How much more money/effort? Why?

                                                 Ron


From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Monday, June 18, 2012 10:03 PM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG

Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

I agree we do would like to enable IPv6 multicast in our network. However, =
all these things can not be achieved within one night. We still have a lot =
of old devices which can not support IPv6 multicast in our network, but we =
are running out of IPv4 address right now. So we can not wait until the who=
le network is ready for IPv6 multicast.

Hope it clarifies.

Best wishes
Qiong
On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica <rbonica@juniper.net<mailto=
:rbonica@juniper.net>> wrote:
Hi Qiong,

If you were to enable IPv6 multicast throughout your network before deployi=
ng IPv6 only receivers, would you not fall into use cases 3.4 and 3.5 (the =
dual stack scenarios). Since you are going to have to enable IPv6 multicast=
 throughout your network anyway, wouldn't it be a good idea to do so sooner=
 than later?

                                                                      Ron

From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Tuesday, June 12, 2012 10:11 AM
To: Lenny Giuliano
Cc: MBONED WG; Ronald Bonica

Subject: Re: [MBONED] Multicast transition work in MBONED

Dear all,


1. In our situation, the source may still remian in IPv4, while the receive=
r will be IPv6-only since there is no more IPv4 address anymore. However, t=
he network might be IPv4-only, which can not support IPv6 multicast yet; or=
 the network can support IPv6 multicast. This is the case of 6-4.
Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.

2. Use case: 3.2, 3.4,

Best wishes
Qiong
On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <lenny@juniper.net<mailto:=
lenny@juniper.net>> wrote:

The multicast transition work within MBONED was initially intended to consi=
st of ~ 3 document with limited scope.  In a very short amount of time, we'=
ve seen 7 drafts (and counting) with scope widening.

In order to make sure we are focusing on work that is of actual value to th=
e community and prevent a flood of high volume/low value drafts, we would l=
ike to revisit the basic questions of multicast transition within MBONED.  =
We would like to hear answers from the WG to the following questions before=
 continuing any work on multicast transition in MBONED:

1) Which operators intend to source multicast traffic from one IP version a=
nd receive it over another IP version?

2) For those who answer 1), please identify the use-cases of interest in dr=
aft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions for t=
hose use cases.


MBONED Chairs
_______________________________________________
MBONED mailing list
MBONED@ietf.org<mailto:MBONED@ietf.org>
https://www.ietf.org/mailman/listinfo/mboned




___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


--_000_983A1D8DA0DA5F4EB747BF34CBEE5CD15A0EF4E7E0PUEXCB1Cnante_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.21311" name=3DGENERATOR>
<STYLE><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue bgColor=3Dwhite>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>Ron, all,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>I have to admit I don't understand why this questi=
on about=20
use cases is raised again and again, to second one of the comments that wer=
e=20
made by Simon some time ago.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>This effort initially started with the softwire <A=
=20
href=3D"http://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicas=
t/">http://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/</=
A>&nbsp;draft,=20
according to the section 3 of the softwire WG charter (<A=20
href=3D"http://datatracker.ietf.org/wg/softwire/charter/).">http://datatrac=
ker.ietf.org/wg/softwire/charter/).</A></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>As per an initial request from the softwire WG cha=
irs,=20
several operators got together to document the accompanying problem stateme=
nt=20
draft that has been further elaborated with the integration of use cases in=
=20
addition to the 4-6-4 use case, and which has now become a mboned WG docume=
nt,=20
as per the poll results that were confirmed some time ago.</FONT></SPAN></D=
IV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>I'm still wondering why the 4-6-4 use case should =
be ruled=20
out, as it can be seen as a consequence of the enforcement of a global IPv6=
=20
strategy that includes (but is not limited to)&nbsp;the deployment of IPv6=
=20
multicast-enabled infrastructures combined with the introduction of techniq=
ues=20
that are meant to address the need to access IPv4 contents during the trans=
ition=20
period where end customers will not be assigned a global IPv4 address anymo=
re.=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>Such techniques include DS-Lite.</FONT></SPAN></DI=
V>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>I'm not convinced that deploying DS multicast arch=
itectures=20
would be simpler, but I'm sure such design will certainly not optimize band=
width=20
usage&nbsp;in (at least)&nbsp;the access infrastructures.</FONT></SPAN></DI=
V>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>As for the use of an IPv6-only, multicast-enabled,=
 access=20
infrastructure, this is something that has been slightly elaborated in the =
first=20
bullet paragraph of section 1 of <A=20
href=3D"http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00#page-=
6">http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00#page-6</A>=
,=20
whereas some operators are currently moving from a service-specific, multi-=
PVC=20
design scheme towards a service-agnostic, single PVC design=20
scheme.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012></SPAN>&nbsp;<=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>A service-agnostic, single PVC design scheme has t=
he=20
inevitable effect of importing global IPv4 address depletion issues=20
into&nbsp;service environments which used to rely upon a walled garden,=20
RFC1918-based, design.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012></SPAN>&nbsp;<=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>Combined with the introduction of DS-Lite, this le=
ads to=20
the 4-6-4 use case.&nbsp;</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>Note that the technical feasibility of what is doc=
umented=20
in <A=20
href=3D"http://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicas=
t/">http://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/</=
A>&nbsp;has=20
already been demonstrated, thanks to a collaboration with a couple of=20
vendors.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012></SPAN>&nbsp;<=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>Is this 4-6-4 use case more complicated than a DS =
multicast=20
design? Yes.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>Is this messier? I don't think so, as it primarily=
 depends=20
on service provider-specific operational procedures. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>Besides, I'm not convinced that there is room for =
such=20
hasty qualitative appreciation at this stage of the effort.</FONT></SPAN></=
DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>I hope this will help closing the debate on the mu=
lticast=20
transition use cases and that we will all move on. Finally.</FONT></SPAN></=
DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>Cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2>Christian.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012></SPAN>&nbsp;<=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN=20
class=3D979150808-22062012>&nbsp;&nbsp;&nbsp;</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979150808-22062012><FONT face=3D"=
Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma size=3D2><B>De&nbsp;:</B>=
=20
mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] <B>De la part de</=
B>=20
Ronald Bonica<BR><B>Envoy=E9&nbsp;:</B> jeudi 21 juin 2012=20
19:12<BR><B>=C0&nbsp;:</B> Tina TSOU<BR><B>Cc&nbsp;:</B> MBONED=20
WG<BR><B>Objet&nbsp;:</B> Re: [MBONED] Multicast transition work in=20
MBONED<BR></FONT><BR></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DWordSection1>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-se=
rif'">Tina,<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-se=
rif'"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-se=
rif'">It=20
  seems that the simplest solution in uses case 3.1 &nbsp;would be to deplo=
y=20
  dual-stack in the network. Maybe Chris and Med, Nic &nbsp;could explain w=
hy=20
  this is not the case?<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-se=
rif'"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-se=
rif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;Ron<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-se=
rif'"><o:p>&nbsp;</o:p></SPAN></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: mediu=
m none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt sol=
id; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <DIV>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4=
df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium n=
one; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal><B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN=
></B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Tina TSOU=
=20
  [mailto:Tina.Tsou.Zouting@huawei.com] <BR><B>Sent:</B> Thursday, June 21,=
 2012=20
  12:46 PM<BR><B>To:</B> Ronald Bonica<BR><B>Cc:</B> Qiong; MBONED=20
  WG<BR><B>Subject:</B> Re: [MBONED] Multicast transition work in=20
  MBONED<o:p></o:p></SPAN></P></DIV></DIV>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <DIV>
  <P class=3DMsoNormal>I remember Christian, Med and Nic are going to deplo=
yed=20
  3.1. Roberta asked about 3.3.<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>Med is out of office these days. Hope the whole Euro=
pe is=20
  not all in vacation.<BR><BR>Tina<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><BR>On Jun 21, 2012, a=
t 9:40=20
  AM, "Ronald Bonica" &lt;<A=20
  href=3D"mailto:rbonica@juniper.net">rbonica@juniper.net</A>&gt;=20
  wrote:<o:p></o:p></P></DIV>
  <BLOCKQUOTE style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt">
    <DIV>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-=
serif'">Do=20
    we have anybody who is going to deploy 3.1 or 3.3? </SPAN><o:p></o:p></=
P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-=
serif'">&nbsp;</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-=
serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
    Ron</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-=
serif'">&nbsp;</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-=
serif'">&nbsp;</SPAN><o:p></o:p></P>
    <DIV=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: med=
ium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt s=
olid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
    <DIV>
    <DIV=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5=
c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium=
 none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
    <P class=3DMsoNormal><B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SP=
AN></B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Tina TSO=
U [<A=20
    href=3D"mailto:Tina.Tsou.Zouting@huawei.com">mailto:Tina.Tsou.Zouting@h=
uawei.com</A>]=20
    <BR><B>Sent:</B> Thursday, June 21, 2012 12:26 PM<BR><B>To:</B> Ronald=
=20
    Bonica<BR><B>Cc:</B> Qiong; MBONED WG<BR><B>Subject:</B> Re: [MBONED]=
=20
    Multicast transition work in MBONED</SPAN><o:p></o:p></P></DIV></DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
    <DIV>
    <P class=3DMsoNormal>The original question Lenny asked did not includin=
g 3.1=20
    and 3.3.<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>Lenny asked<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>"<TT><SPAN style=3D"FONT-SIZE: 10pt">1) Which oper=
ators=20
    intend to source multicast traffic from one IP version&nbsp;and receive=
 it=20
    over another IP version?"</SPAN></TT><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Courier New'">3.1 is=
=20
    4-6-4</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Courier New'">3.2 is=
=20
    6-4-6.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>So they r not In the scope of Lenny's=20
    question.<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>Tina<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><BR>On Jun 21, 2012,=
 at 9:16=20
    AM, "Ronald Bonica" &lt;<A=20
    href=3D"mailto:rbonica@juniper.net">rbonica@juniper.net</A>&gt;=20
    wrote:<o:p></o:p></P></DIV>
    <BLOCKQUOTE style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt">
      <DIV>
      <P class=3DMsoNormal><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">Folks,</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">So=20
      it looks like use-cases 3.2, 3.4 and 3.5 may see deployment. There we=
re no=20
      takers for use-cases 3.1 and 3.3.</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">In=20
      <A=20
      href=3D"http://www.ietf.org/mail-archive/web/mboned/current/msg01607.=
html">http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html</A>=
,=20
      Simon Perrault suggests two solutions for 3.4 and 3.5. Does the WG ag=
ree=20
      that those are the solutions that we should run=20
with?</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">Simon=92s=20
      solutions can also be applied to use-case 3.2 if we tunnel over=20
      non-multicast enabled IPv4 segment. Does everyone agree that that is =
a=20
      good idea?</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;Ron</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <DIV=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: m=
edium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt=
 solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
      <DIV>
      <DIV=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #=
b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medi=
um none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
      <P class=3DMsoNormal><B><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</=
SPAN></B><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Qiong =
[<A=20
      href=3D"mailto:bingxuere@gmail.com">mailto:bingxuere@gmail.com</A>]=
=20
      <BR><B>Sent:</B> Wednesday, June 20, 2012 6:23 AM<BR><B>To:</B> Ronal=
d=20
      Bonica<BR><B>Cc:</B> Lenny Giuliano; MBONED WG<BR><B>Subject:</B> Re:=
=20
      [MBONED] Multicast transition work in=20
      MBONED</SPAN><o:p></o:p></P></DIV></DIV>
      <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt">Hi Ronald,<BR><BR>=
For your=20
      question, it would be too difficult to give you an acurate number of=
=20
      money/effort, but I can tell you our situation of network upgradation=
.=20
      <BR><BR>In the transition period, it would be impossible to replace a=
ll=20
      the legacy IPv4-only devices, especially a great many access network=
=20
      devices. So actually, the process would be taken firstly towards our=
=20
      customers and new region. For example, a new customer might get a=20
      new&nbsp; STB with IPv6 functionality. However, this new customer mig=
ht=20
      access some region only with old devices, then at that time, it will =
be of=20
      great help to implement some MLTRANS solutions in the new STB or depl=
oy=20
      limited devices in the network. I believe this will cost less than=20
      upgrading the whole network in the first place. <BR><BR>For old custo=
mers,=20
      they will still use IPv4 as they already got address, unless we upgra=
de=20
      their STB to support IPv6 remotely. But it is not the first priority=
=20
      point.<BR><BR>Best wishes<BR>Qiong<o:p></o:p></P>
      <DIV>
      <P class=3DMsoNormal>On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica &=
lt;<A=20
      href=3D"mailto:rbonica@juniper.net"=20
      target=3D_blank>rbonica@juniper.net</A>&gt; wrote:<o:p></o:p></P>
      <DIV>
      <DIV>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">Qiong,</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">Which=20
      of the following do you think will require more=20
      money/effort:</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">-</SPAN><SPAN=20
      style=3D"FONT-SIZE: 7pt; COLOR: #1f497d">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      </SPAN><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">To=20
      deploy IPv6 multicast throughout your network</SPAN><o:p></o:p></P>
      <P><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">-</SPAN><SPAN=20
      style=3D"FONT-SIZE: 7pt; COLOR: #1f497d">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      </SPAN><SPAN=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">To=20
      deploy the MLTRANS mechanisms that you will require to compensate for=
 the=20
      lack the above mentioned capability</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">How=20
      much more money/effort? Why?</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
      Ron</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <DIV=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: m=
edium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt=
 solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
      <DIV>
      <DIV=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #=
b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medi=
um none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><B><S=
PAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</=
SPAN></B><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Qiong=
=20
      [mailto:<A href=3D"mailto:bingxuere@gmail.com"=20
      target=3D_blank>bingxuere@gmail.com</A>] <BR><B>Sent:</B> Monday, Jun=
e 18,=20
      2012 10:03 PM<BR><B>To:</B> Ronald Bonica<BR><B>Cc:</B> Lenny Giulian=
o;=20
      MBONED WG</SPAN><o:p></o:p></P>
      <DIV>
      <DIV>
      <P class=3DMsoNormal><BR><B>Subject:</B> Re: [MBONED] Multicast trans=
ition=20
      work in MBONED<o:p></o:p></P></DIV></DIV></DIV></DIV>
      <DIV>
      <DIV>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">&nbsp=
;<o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"MARGIN-BOTTOM: 12pt; mso-margin-top-alt: auto">Hi Ronald,<BR=
><BR>I=20
      agree we do would like to enable IPv6 multicast in our network. Howev=
er,=20
      all these things can not be achieved within one night. We still have =
a lot=20
      of old devices which can not support IPv6 multicast in our network, b=
ut we=20
      are running out of IPv4 address right now. So we can not wait until t=
he=20
      whole network is ready for IPv6 multicast.<BR><BR>Hope it=20
      clarifies.<BR><BR>Best wishes<BR>Qiong<o:p></o:p></P>
      <DIV>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">On Mo=
n, Jun=20
      18, 2012 at 11:07 PM, Ronald Bonica &lt;<A=20
      href=3D"mailto:rbonica@juniper.net"=20
      target=3D_blank>rbonica@juniper.net</A>&gt; wrote:<o:p></o:p></P>
      <DIV>
      <DIV>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">Hi=20
      Qiong,</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">If=20
      you were to enable IPv6 multicast throughout your network before depl=
oying=20
      IPv6 only receivers, would you not fall into use cases 3.4 and 3.5 (t=
he=20
      dual stack scenarios). Since you are going to have to enable IPv6=20
      multicast throughout your network anyway, wouldn=92t it be a good ide=
a to do=20
      so sooner than later? </SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Ron</SPAN><o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN=
=20
      style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','san=
s-serif'">&nbsp;</SPAN><o:p></o:p></P>
      <DIV=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: m=
edium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt=
 solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
      <DIV>
      <DIV=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #=
b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medi=
um none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><B><S=
PAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</=
SPAN></B><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Qiong=
=20
      [mailto:<A href=3D"mailto:bingxuere@gmail.com"=20
      target=3D_blank>bingxuere@gmail.com</A>] <BR><B>Sent:</B> Tuesday, Ju=
ne 12,=20
      2012 10:11 AM<BR><B>To:</B> Lenny Giuliano<BR><B>Cc:</B> MBONED WG; R=
onald=20
      Bonica</SPAN><o:p></o:p></P>
      <DIV>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><BR><=
B>Subject:</B>=20
      Re: [MBONED] Multicast transition work in=20
      MBONED<o:p></o:p></P></DIV></DIV></DIV>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">&nbsp=
;<o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"MARGIN-BOTTOM: 12pt; mso-margin-top-alt: auto">Dear=20
      all,<o:p></o:p></P>
      <DIV>
      <DIV>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><BR><=
BR>1.=20
      In our situation, the source may still remian in IPv4, while the rece=
iver=20
      will be IPv6-only since there is no more IPv4 address anymore. Howeve=
r,=20
      the network might be IPv4-only, which can not support IPv6 multicast =
yet;=20
      or the network can support IPv6 multicast. This is the case of 6-4.=
=20
      <BR>Another situation is: the access network is still IPv4-only, and =
the=20
      core netowrk (or application platform) is IPv6, then that is the case=
 of=20
      6-4-6-4.<BR><BR>2. Use case: 3.2, 3.4,<BR><BR>Best=20
      wishes<BR>Qiong<o:p></o:p></P></DIV></DIV>
      <DIV>
      <DIV>
      <DIV>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">On Fr=
i, Jun=20
      8, 2012 at 4:34 AM, Leonard Giuliano &lt;<A=20
      href=3D"mailto:lenny@juniper.net" target=3D_blank>lenny@juniper.net</=
A>&gt;=20
      wrote:<o:p></o:p></P>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><BR>T=
he=20
      multicast transition work within MBONED was initially intended to con=
sist=20
      of ~ 3 document with limited scope. &nbsp;In a very short amount of t=
ime,=20
      we've seen 7 drafts (and counting) with scope widening.<BR><BR>In ord=
er to=20
      make sure we are focusing on work that is of actual value to the comm=
unity=20
      and prevent a flood of high volume/low value drafts, we would like to=
=20
      revisit the basic questions of multicast transition within MBONED.=20
      &nbsp;We would like to hear answers from the WG to the following ques=
tions=20
      before continuing any work on multicast transition in MBONED:<BR><BR>=
1)=20
      Which operators intend to source multicast traffic from one IP versio=
n and=20
      receive it over another IP version?<BR><BR>2) For those who answer 1)=
,=20
      please identify the use-cases of interest in=20
      draft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutio=
ns=20
      for those use cases.<BR><BR><BR>MBONED=20
      Chairs<BR>_______________________________________________<BR>MBONED=
=20
      mailing list<BR><A href=3D"mailto:MBONED@ietf.org"=20
      target=3D_blank>MBONED@ietf.org</A><BR><A=20
      href=3D"https://www.ietf.org/mailman/listinfo/mboned"=20
      target=3D_blank>https://www.ietf.org/mailman/listinfo/mboned</A><o:p>=
</o:p></P></DIV>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">&nbsp=
;<o:p></o:p></P></DIV></DIV></DIV></DIV></DIV></DIV>
      <P class=3DMsoNormal=20
      style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">&nbsp=
;<o:p></o:p></P></DIV></DIV></DIV></DIV></DIV></DIV>
      <P=20
  class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV></DIV></BLOCKQUOTE></DIV></D=
IV></BLOCKQUOTE></DIV></DIV></BLOCKQUOTE><PRE>_____________________________=
___________________________________________________________________________=
_________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.
</PRE></BODY></HTML>

--_000_983A1D8DA0DA5F4EB747BF34CBEE5CD15A0EF4E7E0PUEXCB1Cnante_--

From stig@venaas.com  Fri Jun 22 13:21:44 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F86F21F85D4 for <mboned@ietfa.amsl.com>; Fri, 22 Jun 2012 13:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 RpmO4v8FYmgj for <mboned@ietfa.amsl.com>; Fri, 22 Jun 2012 13:21:44 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 41A0421F8564 for <mboned@ietf.org>; Fri, 22 Jun 2012 13:21:44 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id DC8388023 for <mboned@ietf.org>; Fri, 22 Jun 2012 22:21:42 +0200 (CEST)
Message-ID: <4FE4D3D5.2000900@venaas.com>
Date: Fri, 22 Jun 2012 13:21:41 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: MBONED WG <mboned@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [MBONED] PIM survey for operators
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 20:21:44 -0000

The IETF pim working group is conducting a survey in order to advance
the PIM Sparse Mode spec on the IETF Standards Track, and would like
input from operators. The survey ends July 20th. Please see below for
more information.

thank you,
pim chairs Mike & Stig


Introduction:

PIM-SM was first published as RFC 2117 in 1997 and then again as
RFC 2362 in 1998.  The protocol was classified as Experimental in
both of these documents.  The PIM-SM protocol specification was
then rewritten in whole and advanced to Proposed Standard as
RFC 4601 in 2006. Considering the multiple independent
implementations developed and the successful operational
experience gained, the IETF has decided to advance the PIM-SM
routing protocol to Draft Standard.  This survey intends to
provide supporting documentation to advance the Protocol
Independent Multicast - Sparse Mode (PIM-SM) routing protocol
from IETF Proposed Standard to Draft Standard. (Due to RFC 6410,
now the intention is to progress it to Internet Standard.  Draft Standard
is no longer used.)

This survey is issued on behalf of the IETF PIM Working Group.

The responses will be collected by a neutral third-party and kept
strictly confidential; only the final combined results will be
published.  Marshall Eubanks has agreed to anonymize the response
to this Questionnaire.  Marshall has a long experience with
Multicast but has no direct financial interest in this matter,
nor ties to any of the vendors involved.  He is also a member of
the IAOC, Chair of the IETF Trust and co-chair of the IETF
Layer 3 VPN Working Group.  Please send Questionnaire responses
to his email address, marshall.eubanks@gmail.com.  He requests
that such responses include the string "RFC 4601 bis Questionnaire" in
the subject field.

Before answering the questions, please comple the following background
information.

Name of the Respondent:
Affliation/Organization:
Contact Email:
Provide description of PIM deployment:
Do you wish to keep the information provided confidential:

Questions:

1       Have you deployed PIM-SM in your network?

2       How long have you had PIM-SM deployed in your network?
        Do you know if your deployment is based on the most recent
        RFC4601?

3       Have you deployed PIM-SM for IPv6 in your network?

4       Are you using equipment with different (multi-vendor) PIM-SM
        implementations for your deployment?

5       Have you encountered any inter-operability or backward-
        compatibility issues amongst differing implementations?
        If yes, what are your concerns about these issues?

6       Have you deployed both dense mode and sparse mode in your
        network?

        If yes, do you route between these modes using features such
        as *,*,RP or PMBR?

7       To what extent have you deployed PIM functionality, like BSR,
        SSM, and Explicit Tracking?

8       Which RP mapping mechanism do you use: Static, AutoRP, or BSR?

9       How many RPs have you deployed in your network?

10      If you use Anycast-RP, is it Anycast-RP using MSDP (RFC 3446)
        or Anycast-RP using PIM (RFC 4610)?

11      Do you have any other comments on PIM-SM deployment in your
        network?

From stig@venaas.com  Fri Jun 22 13:29:35 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11E1611E8079 for <mboned@ietfa.amsl.com>; Fri, 22 Jun 2012 13:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 iNr2UAMSzCz9 for <mboned@ietfa.amsl.com>; Fri, 22 Jun 2012 13:29:34 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id BD76D21F8627 for <mboned@ietf.org>; Fri, 22 Jun 2012 13:29:34 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 7C12F8020 for <mboned@ietf.org>; Fri, 22 Jun 2012 22:29:33 +0200 (CEST)
Message-ID: <4FE4D5AB.5050707@venaas.com>
Date: Fri, 22 Jun 2012 13:29:31 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: MBONED WG <mboned@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [MBONED] PIM survey for implementors
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 20:29:35 -0000

The IETF pim working group is conducting a survey in order to advance
the PIM Sparse Mode spec on the IETF Standards Track, and would like
input from implementors. The survey ends July 20th. Please see below
for more information.

thank you,
pim chairs Mike & Stig


Introduction:

PIM-SM was first published as RFC 2117 in 1997 and then again as RFC
2362 in 1998.  The protocol was classified as Experimental in both of
these documents.  The PIM-SM protocol specification was then rewritten
in whole and advanced to Proposed Standard as RFC 4601 in 2006.
Considering the multiple independent implementations developed and the
successful operational experience gained, the IETF has decided to
advance the PIM-SM routing protocol to Draft Standard.  This survey
intends to provide supporting documentation to advance the Protocol
Independent Multicast - Sparse Mode (PIM-SM) routing protocol from IETF
Proposed Standard to Draft Standard. (Due to RFC 6410, now the
intention is to progress it to Internet Standard.  Draft Standard is
not used anymore.)

This survey is issued on behalf of the IETF PIM Working Group.

The responses will be collected by neutral third-party and kept
strictly confidential; only the final combined results will be
published.  Marshall Eubanks has agreed to anonymize the response to
this Questionnaire.  Marshall has a long experience with Multicast but
has no direct financial interest in this matter, nor ties to any of the
vendors involved.  He is also a member of the IAOC, Chair of the IETF
Trust and co-chair of the IETF Layer 3 VPN Working Group.  Please send
Questionnaire responses to his email address,
marshall.eubanks@gmail.com.  He requests that such responses include
the string "RFC 4601 bis Questionnaire" in the subject field.

Before answer the questions, please fill the following background 
information.

Name of the Respondent:
Affliation/Organization:
Contact Email:
Provide description of PIM implementation:
Do you wish to keep the information provided confidential:

Questions:

1       Have you implemented PIM-SM?

2       Is the PIM-SM implementation based on RFC 2632 or RFC 4601?

3       Have you implemented (*,*, RP) state of RFC 4601? What is the
         rationale behind implementing or omitting (*,*,RP)?

4       Have you implemented the PMBR as specified in RFC 4601 and
         RFC 2715?
         What is the rationale behind implementing or omitting PMBR?

5       Have you implemented other features and functions of RFC 4601:
                 - SSM
                 - Join Suppression
                 - Explicit tracking
                 - Register mechanism
                 - SPT switchover at last-hop router
                 - Assert mechanism
                 - Hashing of group to RP mappings

6       Does your PIM-SM implementation support IPv6?

7       Have you encountered any inter-operability issues with other
         PIM implementations in trials or in the field?

8       Do you have any other comments or concerns about PIM-SM as
         specified in RFC4601?

From rbonica@juniper.net  Fri Jun 22 18:33:18 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B4F521F853E for <mboned@ietfa.amsl.com>; Fri, 22 Jun 2012 18:33:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.57
X-Spam-Level: 
X-Spam-Status: No, score=-106.57 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 zgKIV-iBlRuU for <mboned@ietfa.amsl.com>; Fri, 22 Jun 2012 18:33:11 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 3277F21F853C for <mboned@ietf.org>; Fri, 22 Jun 2012 18:33:08 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKT+Uc00UCAw4LmNxJE6hynduo02itDBMd@postini.com; Fri, 22 Jun 2012 18:33:11 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 22 Jun 2012 18:30:04 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 22 Jun 2012 21:30:03 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Date: Fri, 22 Jun 2012 21:30:01 -0400
Thread-Topic: [MBONED] Multicast transition work in MBONED
Thread-Index: AQHNRO2IJbQ/FDofPUmTNMjuOmtYFZb3NfMAgAl9swCAALcMgIACA8EAgAAaSYCAAfS5AP//jc2vgAACxgCAAAK2XYAABGhAgAD9WXCAARqe0A==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76EFC667E@EMBX01-WF.jnpr.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net> <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com>, <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net> <3A85B6A1-9427-40C9-8D3A-307ACFECE13B@huawei.com>, <13205C286662DE4387D9AF3AC30EF456D76EDCE440@EMBX01-WF.jnpr.net> <5A041654-83A8-46D7-8149-6286F05297F5@huawei.com> <13205C286662DE4387D9AF3AC30EF456D76EDCE4FE@EMBX01-WF.jnpr.net> <17386_1340354057_4FE42E09_17386_8210_1_983A1D8DA0DA5F4EB747BF34CBEE5CD15A0EF4E7E0@PUEXCB1C.nanterre.francetelecom.fr>
In-Reply-To: <17386_1340354057_4FE42E09_17386_8210_1_983A1D8DA0DA5F4EB747BF34CBEE5CD15A0EF4E7E0@PUEXCB1C.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_13205C286662DE4387D9AF3AC30EF456D76EFC667EEMBX01WFjnprn_"
MIME-Version: 1.0
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jun 2012 01:33:18 -0000

--_000_13205C286662DE4387D9AF3AC30EF456D76EFC667EEMBX01WFjnprn_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Christian,

In both the 6-4-6 and 4-6-4 cases, it is architecturally cleaner to deploy =
dual stack in the core than it is to deploy the required adaptation functio=
ns. If a few operators step forward to say that they are deploying in the a=
bove mentioned scenarios, it might make sense to develop the required adapt=
ation functions. However, lacking those operator statements, it makes littl=
e sense for the IETF to specify what may never be deployed.

I am particularly interested in understanding why an operator would chose a=
daptation over native dual stack. It seems that operational cost and comple=
xity associate with adaptation will be greater than that associated with ru=
nning dual stack.

                                                                   Ron


From: christian.jacquenet@orange.com [mailto:christian.jacquenet@orange.com=
]
Sent: Friday, June 22, 2012 4:34 AM
To: Ronald Bonica; Tina TSOU
Cc: MBONED WG
Subject: RE: [MBONED] Multicast transition work in MBONED

Ron, all,

I have to admit I don't understand why this question about use cases is rai=
sed again and again, to second one of the comments that were made by Simon =
some time ago.

This effort initially started with the softwire http://datatracker.ietf.org=
/doc/draft-ietf-softwire-dslite-multicast/ draft, according to the section =
3 of the softwire WG charter (http://datatracker.ietf.org/wg/softwire/chart=
er/).

As per an initial request from the softwire WG chairs, several operators go=
t together to document the accompanying problem statement draft that has be=
en further elaborated with the integration of use cases in addition to the =
4-6-4 use case, and which has now become a mboned WG document, as per the p=
oll results that were confirmed some time ago.

I'm still wondering why the 4-6-4 use case should be ruled out, as it can b=
e seen as a consequence of the enforcement of a global IPv6 strategy that i=
ncludes (but is not limited to) the deployment of IPv6 multicast-enabled in=
frastructures combined with the introduction of techniques that are meant t=
o address the need to access IPv4 contents during the transition period whe=
re end customers will not be assigned a global IPv4 address anymore.

Such techniques include DS-Lite.

I'm not convinced that deploying DS multicast architectures would be simple=
r, but I'm sure such design will certainly not optimize bandwidth usage in =
(at least) the access infrastructures.

As for the use of an IPv6-only, multicast-enabled, access infrastructure, t=
his is something that has been slightly elaborated in the first bullet para=
graph of section 1 of http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mca=
st-ps-00#page-6, whereas some operators are currently moving from a service=
-specific, multi-PVC design scheme towards a service-agnostic, single PVC d=
esign scheme.

A service-agnostic, single PVC design scheme has the inevitable effect of i=
mporting global IPv4 address depletion issues into service environments whi=
ch used to rely upon a walled garden, RFC1918-based, design.

Combined with the introduction of DS-Lite, this leads to the 4-6-4 use case=
.

Note that the technical feasibility of what is documented in http://datatra=
cker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/ has already been de=
monstrated, thanks to a collaboration with a couple of vendors.

Is this 4-6-4 use case more complicated than a DS multicast design? Yes.

Is this messier? I don't think so, as it primarily depends on service provi=
der-specific operational procedures.

Besides, I'm not convinced that there is room for such hasty qualitative ap=
preciation at this stage of the effort.

I hope this will help closing the debate on the multicast transition use ca=
ses and that we will all move on. Finally.

Cheers,

Christian.




________________________________
De : mboned-bounces@ietf.org<mailto:mboned-bounces@ietf.org> [mailto:mboned=
-bounces@ietf.org] De la part de Ronald Bonica
Envoy=E9 : jeudi 21 juin 2012 19:12
=C0 : Tina TSOU
Cc : MBONED WG
Objet : Re: [MBONED] Multicast transition work in MBONED
Tina,

It seems that the simplest solution in uses case 3.1  would be to deploy du=
al-stack in the network. Maybe Chris and Med, Nic  could explain why this i=
s not the case?

                                                     Ron

From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
Sent: Thursday, June 21, 2012 12:46 PM
To: Ronald Bonica
Cc: Qiong; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

I remember Christian, Med and Nic are going to deployed 3.1. Roberta asked =
about 3.3.
Med is out of office these days. Hope the whole Europe is not all in vacati=
on.

Tina

On Jun 21, 2012, at 9:40 AM, "Ronald Bonica" <rbonica@juniper.net<mailto:rb=
onica@juniper.net>> wrote:
Do we have anybody who is going to deploy 3.1 or 3.3?

                                     Ron


From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
Sent: Thursday, June 21, 2012 12:26 PM
To: Ronald Bonica
Cc: Qiong; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

The original question Lenny asked did not including 3.1 and 3.3.
Lenny asked
"1) Which operators intend to source multicast traffic from one IP version =
and receive it over another IP version?"
3.1 is 4-6-4
3.2 is 6-4-6.
So they r not In the scope of Lenny's question.

Tina

On Jun 21, 2012, at 9:16 AM, "Ronald Bonica" <rbonica@juniper.net<mailto:rb=
onica@juniper.net>> wrote:
Folks,

So it looks like use-cases 3.2, 3.4 and 3.5 may see deployment. There were =
no takers for use-cases 3.1 and 3.3.

In http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html, Simon=
 Perrault suggests two solutions for 3.4 and 3.5. Does the WG agree that th=
ose are the solutions that we should run with?

Simon's solutions can also be applied to use-case 3.2 if we tunnel over non=
-multicast enabled IPv4 segment. Does everyone agree that that is a good id=
ea?

                                                    Ron

From: Qiong [mailto:bingxuere@gmail.com]
Sent: Wednesday, June 20, 2012 6:23 AM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG
Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

For your question, it would be too difficult to give you an acurate number =
of money/effort, but I can tell you our situation of network upgradation.

In the transition period, it would be impossible to replace all the legacy =
IPv4-only devices, especially a great many access network devices. So actua=
lly, the process would be taken firstly towards our customers and new regio=
n. For example, a new customer might get a new  STB with IPv6 functionality=
. However, this new customer might access some region only with old devices=
, then at that time, it will be of great help to implement some MLTRANS sol=
utions in the new STB or deploy limited devices in the network. I believe t=
his will cost less than upgrading the whole network in the first place.

For old customers, they will still use IPv4 as they already got address, un=
less we upgrade their STB to support IPv6 remotely. But it is not the first=
 priority point.

Best wishes
Qiong
On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica <rbonica@juniper.net<mailto:=
rbonica@juniper.net>> wrote:
Qiong,

Which of the following do you think will require more money/effort:


-          To deploy IPv6 multicast throughout your network

-          To deploy the MLTRANS mechanisms that you will require to compen=
sate for the lack the above mentioned capability

How much more money/effort? Why?

                                                 Ron


From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Monday, June 18, 2012 10:03 PM
To: Ronald Bonica
Cc: Lenny Giuliano; MBONED WG

Subject: Re: [MBONED] Multicast transition work in MBONED

Hi Ronald,

I agree we do would like to enable IPv6 multicast in our network. However, =
all these things can not be achieved within one night. We still have a lot =
of old devices which can not support IPv6 multicast in our network, but we =
are running out of IPv4 address right now. So we can not wait until the who=
le network is ready for IPv6 multicast.

Hope it clarifies.

Best wishes
Qiong
On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica <rbonica@juniper.net<mailto=
:rbonica@juniper.net>> wrote:
Hi Qiong,

If you were to enable IPv6 multicast throughout your network before deployi=
ng IPv6 only receivers, would you not fall into use cases 3.4 and 3.5 (the =
dual stack scenarios). Since you are going to have to enable IPv6 multicast=
 throughout your network anyway, wouldn't it be a good idea to do so sooner=
 than later?

                                                                      Ron

From: Qiong [mailto:bingxuere@gmail.com<mailto:bingxuere@gmail.com>]
Sent: Tuesday, June 12, 2012 10:11 AM
To: Lenny Giuliano
Cc: MBONED WG; Ronald Bonica

Subject: Re: [MBONED] Multicast transition work in MBONED

Dear all,


1. In our situation, the source may still remian in IPv4, while the receive=
r will be IPv6-only since there is no more IPv4 address anymore. However, t=
he network might be IPv4-only, which can not support IPv6 multicast yet; or=
 the network can support IPv6 multicast. This is the case of 6-4.
Another situation is: the access network is still IPv4-only, and the core n=
etowrk (or application platform) is IPv6, then that is the case of 6-4-6-4.

2. Use case: 3.2, 3.4,

Best wishes
Qiong
On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <lenny@juniper.net<mailto:=
lenny@juniper.net>> wrote:

The multicast transition work within MBONED was initially intended to consi=
st of ~ 3 document with limited scope.  In a very short amount of time, we'=
ve seen 7 drafts (and counting) with scope widening.

In order to make sure we are focusing on work that is of actual value to th=
e community and prevent a flood of high volume/low value drafts, we would l=
ike to revisit the basic questions of multicast transition within MBONED.  =
We would like to hear answers from the WG to the following questions before=
 continuing any work on multicast transition in MBONED:

1) Which operators intend to source multicast traffic from one IP version a=
nd receive it over another IP version?

2) For those who answer 1), please identify the use-cases of interest in dr=
aft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions for t=
hose use cases.


MBONED Chairs
_______________________________________________
MBONED mailing list
MBONED@ietf.org<mailto:MBONED@ietf.org>
https://www.ietf.org/mailman/listinfo/mboned




___________________________________________________________________________=
______________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,

France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and dele=
te this message and its attachments.

As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.

Thank you.

--_000_13205C286662DE4387D9AF3AC30EF456D76EFC667EEMBX01WFjnprn_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Micr=
osoft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#d=
efault#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>Christian,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'>In both the 6-4-6 and 4-6-4=
 cases, it is architecturally cleaner to deploy dual stack in the core than=
 it is to deploy the required adaptation functions. If a few operators step=
 forward to say that they are deploying in the above mentioned scenarios, i=
t might make sense to develop the required adaptation functions. However, l=
acking those operator statements, it makes little sense for the IETF to spe=
cify what may never be deployed.<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I am particu=
larly interested in understanding why an operator would chose adaptation ov=
er native dual stack. It seems that operational cost and complexity associa=
te with adaptation will be greater than that associated with running dual s=
tack.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11=
.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"C=
alibri","sans-serif";color:#1F497D'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 Ron<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'> <o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;b=
order-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'b=
order:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p cla=
ss=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","san=
s-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Taho=
ma","sans-serif"'> christian.jacquenet@orange.com [mailto:christian.jacquen=
et@orange.com] <br><b>Sent:</b> Friday, June 22, 2012 4:34 AM<br><b>To:</b>=
 Ronald Bonica; Tina TSOU<br><b>Cc:</b> MBONED WG<br><b>Subject:</b> RE: [M=
BONED] Multicast transition work in MBONED<o:p></o:p></span></p></div></div=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:blue'>Ron, all,</span>=
<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNorm=
al><span style=3D'font-size:10.0pt;font-family:"Courier New";color:blue'>I =
have to admit I don't understand why this question about use cases is raise=
d again and again, to second one of the comments that were made by Simon so=
me time ago.</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New";color:blue'>This effort initially started with the softwire <a href=3D=
"http://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/">htt=
p://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/</a>&nbsp=
;draft, according to the section 3 of the softwire WG charter (<a href=3D"h=
ttp://datatracker.ietf.org/wg/softwire/charter/).">http://datatracker.ietf.=
org/wg/softwire/charter/).</a></span><o:p></o:p></p><p class=3DMsoNormal>&n=
bsp;<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Courier New";color:blue'>As per an initial request from the softw=
ire WG chairs, several operators got together to document the accompanying =
problem statement draft that has been further elaborated with the integrati=
on of use cases in addition to the 4-6-4 use case, and which has now become=
 a mboned WG document, as per the poll results that were confirmed some tim=
e ago.</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";c=
olor:blue'>I'm still wondering why the 4-6-4 use case should be ruled out, =
as it can be seen as a consequence of the enforcement of a global IPv6 stra=
tegy that includes (but is not limited to)&nbsp;the deployment of IPv6 mult=
icast-enabled infrastructures combined with the introduction of techniques =
that are meant to address the need to access IPv4 contents during the trans=
ition period where end customers will not be assigned a global IPv4 address=
 anymore. </span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><=
p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier Ne=
w";color:blue'>Such techniques include DS-Lite.</span><o:p></o:p></p><p cla=
ss=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span style=3D'fon=
t-size:10.0pt;font-family:"Courier New";color:blue'>I'm not convinced that =
deploying DS multicast architectures would be simpler, but I'm sure such de=
sign will certainly not optimize bandwidth usage&nbsp;in (at least)&nbsp;th=
e access infrastructures.</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<=
o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fam=
ily:"Courier New";color:blue'>As for the use of an IPv6-only, multicast-ena=
bled, access infrastructure, this is something that has been slightly elabo=
rated in the first bullet paragraph of section 1 of <a href=3D"http://tools=
.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00#page-6">http://tools.ietf=
.org/html/draft-ietf-mboned-v4v6-mcast-ps-00#page-6</a>, whereas some opera=
tors are currently moving from a service-specific, multi-PVC design scheme =
towards a service-agnostic, single PVC design scheme.</span><o:p></o:p></p>=
<p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:blue'>A service-agnost=
ic, single PVC design scheme has the inevitable effect of importing global =
IPv4 address depletion issues into&nbsp;service environments which used to =
rely upon a walled garden, RFC1918-based, design.</span><o:p></o:p></p><p c=
lass=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:blue'>Combined with the int=
roduction of DS-Lite, this leads to the 4-6-4 use case.&nbsp;</span><o:p></=
o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New";color:blue'>Note that=
 the technical feasibility of what is documented in <a href=3D"http://datat=
racker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/">http://datatrack=
er.ietf.org/doc/draft-ietf-softwire-dslite-multicast/</a>&nbsp;has already =
been demonstrated, thanks to a collaboration with a couple of vendors.</spa=
n><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNo=
rmal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:blue'>=
Is this 4-6-4 use case more complicated than a DS multicast design? Yes.</s=
pan><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMso=
Normal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:blue=
'>Is this messier? I don't think so, as it primarily depends on service pro=
vider-specific operational procedures. </span><o:p></o:p></p><p class=3DMso=
Normal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:1=
0.0pt;font-family:"Courier New";color:blue'>Besides, I'm not convinced that=
 there is room for such hasty qualitative appreciation at this stage of the=
 effort.</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New"=
;color:blue'>I hope this will help closing the debate on the multicast tran=
sition use cases and that we will all move on. Finally.</span><o:p></o:p></=
p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span styl=
e=3D'font-size:10.0pt;font-family:"Courier New";color:blue'>Cheers,</span><=
o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNorma=
l><span style=3D'font-size:10.0pt;font-family:"Courier New";color:blue'>Chr=
istian.</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p c=
lass=3DMsoNormal>&nbsp;&nbsp;&nbsp;<o:p></o:p></p><p class=3DMsoNormal>&nbs=
p;<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><div class=3DMso=
Normal align=3Dcenter style=3D'text-align:center'><hr size=3D2 width=3D"100=
%" align=3Dcenter></div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'=
><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&n=
bsp;:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-=
serif"'> <a href=3D"mailto:mboned-bounces@ietf.org">mboned-bounces@ietf.org=
</a> [<a href=3D"mailto:mboned-bounces@ietf.org">mailto:mboned-bounces@ietf=
.org</a>] <b>De la part de</b> Ronald Bonica<br><b>Envoy=E9&nbsp;:</b> jeud=
i 21 juin 2012 19:12<br><b>=C0&nbsp;:</b> Tina TSOU<br><b>Cc&nbsp;:</b> MBO=
NED WG<br><b>Objet&nbsp;:</b> Re: [MBONED] Multicast transition work in MBO=
NED</span><o:p></o:p></p><blockquote style=3D'margin-top:5.0pt;margin-right=
:0in;margin-bottom:5.0pt'><p class=3DMsoNormal><span style=3D'font-size:11.=
0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Tina,<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'>It seems that the simplest solution in uses case 3.1 &nbsp;w=
ould be to deploy dual-stack in the network. Maybe Chris and Med, Nic &nbsp=
;could explain why this is not the case?<o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;Ron<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</=
o:p></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;paddi=
ng:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4=
DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'=
font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Tina TSOU [<a =
href=3D"mailto:Tina.Tsou.Zouting@huawei.com">mailto:Tina.Tsou.Zouting@huawe=
i.com</a>] <br><b>Sent:</b> Thursday, June 21, 2012 12:46 PM<br><b>To:</b> =
Ronald Bonica<br><b>Cc:</b> Qiong; MBONED WG<br><b>Subject:</b> Re: [MBONED=
] Multicast transition work in MBONED<o:p></o:p></span></p></div></div><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>I remember =
Christian, Med and Nic are going to deployed 3.1. Roberta asked about 3.3.<=
o:p></o:p></p></div><div><p class=3DMsoNormal>Med is out of office these da=
ys. Hope the whole Europe is not all in vacation.<br><br>Tina<o:p></o:p></p=
></div><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>On Jun =
21, 2012, at 9:40 AM, &quot;Ronald Bonica&quot; &lt;<a href=3D"mailto:rboni=
ca@juniper.net">rbonica@juniper.net</a>&gt; wrote:<o:p></o:p></p></div><blo=
ckquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=3DMsoN=
ormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";co=
lor:#1F497D'>Do we have anybody who is going to deploy 3.1 or 3.3? </span><=
o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Ron</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;<=
/span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></=
p><div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0i=
n 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padd=
ing:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.=
0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-=
size:10.0pt;font-family:"Tahoma","sans-serif"'> Tina TSOU [<a href=3D"mailt=
o:Tina.Tsou.Zouting@huawei.com">mailto:Tina.Tsou.Zouting@huawei.com</a>] <b=
r><b>Sent:</b> Thursday, June 21, 2012 12:26 PM<br><b>To:</b> Ronald Bonica=
<br><b>Cc:</b> Qiong; MBONED WG<br><b>Subject:</b> Re: [MBONED] Multicast t=
ransition work in MBONED</span><o:p></o:p></p></div></div><p class=3DMsoNor=
mal>&nbsp;<o:p></o:p></p><div><p class=3DMsoNormal>The original question Le=
nny asked did not including 3.1 and 3.3.<o:p></o:p></p></div><div><p class=
=3DMsoNormal>Lenny asked<o:p></o:p></p></div><div><p class=3DMsoNormal>&quo=
t;<tt><span style=3D'font-size:10.0pt'>1) Which operators intend to source =
multicast traffic from one IP version&nbsp;and receive it over another IP v=
ersion?&quot;</span></tt><o:p></o:p></p></div><div><p class=3DMsoNormal><sp=
an style=3D'font-family:"Courier New"'>3.1 is 4-6-4</span><o:p></o:p></p></=
div><div><p class=3DMsoNormal><span style=3D'font-family:"Courier New"'>3.2=
 is 6-4-6.</span><o:p></o:p></p></div><div><p class=3DMsoNormal>So they r n=
ot In the scope of Lenny's question.<o:p></o:p></p></div><div><p class=3DMs=
oNormal>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal>Tina<o:p></o:p=
></p></div><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>On =
Jun 21, 2012, at 9:16 AM, &quot;Ronald Bonica&quot; &lt;<a href=3D"mailto:r=
bonica@juniper.net">rbonica@juniper.net</a>&gt; wrote:<o:p></o:p></p></div>=
<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=3D=
MsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif=
";color:#1F497D'>Folks,</span><o:p></o:p></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&n=
bsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.=
0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So it looks like use-=
cases 3.2, 3.4 and 3.5 may see deployment. There were no takers for use-cas=
es 3.1 and 3.3.</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</sp=
an><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font=
-family:"Calibri","sans-serif";color:#1F497D'>In <a href=3D"http://www.ietf=
.org/mail-archive/web/mboned/current/msg01607.html">http://www.ietf.org/mai=
l-archive/web/mboned/current/msg01607.html</a>, Simon Perrault suggests two=
 solutions for 3.4 and 3.5. Does the WG agree that those are the solutions =
that we should run with?</span><o:p></o:p></p><p class=3DMsoNormal><span st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&=
nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11=
.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Simon&#8217;s soluti=
ons can also be applied to use-case 3.2 if we tunnel over non-multicast ena=
bled IPv4 segment. Does everyone agree that that is a good idea?</span><o:p=
></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family=
:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;Ron</span><o:p></o:p></p><p class=3DMsoNormal><s=
pan style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F4=
97D'>&nbsp;</span><o:p></o:p></p><div style=3D'border:none;border-left:soli=
d blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'border:none;bord=
er-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal>=
<b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:=
</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
"'> Qiong [<a href=3D"mailto:bingxuere@gmail.com">mailto:bingxuere@gmail.co=
m</a>] <br><b>Sent:</b> Wednesday, June 20, 2012 6:23 AM<br><b>To:</b> Rona=
ld Bonica<br><b>Cc:</b> Lenny Giuliano; MBONED WG<br><b>Subject:</b> Re: [M=
BONED] Multicast transition work in MBONED</span><o:p></o:p></p></div></div=
><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal style=3D'ma=
rgin-bottom:12.0pt'>Hi Ronald,<br><br>For your question, it would be too di=
fficult to give you an acurate number of money/effort, but I can tell you o=
ur situation of network upgradation. <br><br>In the transition period, it w=
ould be impossible to replace all the legacy IPv4-only devices, especially =
a great many access network devices. So actually, the process would be take=
n firstly towards our customers and new region. For example, a new customer=
 might get a new&nbsp; STB with IPv6 functionality. However, this new custo=
mer might access some region only with old devices, then at that time, it w=
ill be of great help to implement some MLTRANS solutions in the new STB or =
deploy limited devices in the network. I believe this will cost less than u=
pgrading the whole network in the first place. <br><br>For old customers, t=
hey will still use IPv4 as they already got address, unless we upgrade thei=
r STB to support IPv6 remotely. But it is not the first priority point.<br>=
<br>Best wishes<br>Qiong<o:p></o:p></p><div><p class=3DMsoNormal>On Wed, Ju=
n 20, 2012 at 4:48 PM, Ronald Bonica &lt;<a href=3D"mailto:rbonica@juniper.=
net" target=3D"_blank">rbonica@juniper.net</a>&gt; wrote:<o:p></o:p></p><di=
v><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bot=
tom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D'>Qiong,</span><o:p></o:p></p><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span=
><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";color:#1F497D'>Which of the following do you think will requ=
ire more money/effort:</span><o:p></o:p></p><p class=3DMsoNormal style=3D'm=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p=
></o:p></p><p><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D'>-</span><span style=3D'font-size:7.0pt;color:#1F497D'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>To d=
eploy IPv6 multicast throughout your network</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
>-</span><span style=3D'font-size:7.0pt;color:#1F497D'>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'>To deploy the MLTRANS mech=
anisms that you will require to compensate for the lack the above mentioned=
 capability</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p>=
<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#1F497D'>How much more money/effort? Why?</span><o:p></o:p></p><p clas=
s=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ron</span><o:p></o:p></p><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-=
alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><di=
v style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0=
pt'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3=
.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso=
-margin-bottom-alt:auto'><b><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-fa=
mily:"Tahoma","sans-serif"'> Qiong [mailto:<a href=3D"mailto:bingxuere@gmai=
l.com" target=3D"_blank">bingxuere@gmail.com</a>] <br><b>Sent:</b> Monday, =
June 18, 2012 10:03 PM<br><b>To:</b> Ronald Bonica<br><b>Cc:</b> Lenny Giul=
iano; MBONED WG</span><o:p></o:p></p><div><div><p class=3DMsoNormal><br><b>=
Subject:</b> Re: [MBONED] Multicast transition work in MBONED<o:p></o:p></p=
></div></div></div></div><div><div><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>Hi Ronald,<=
br><br>I agree we do would like to enable IPv6 multicast in our network. Ho=
wever, all these things can not be achieved within one night. We still have=
 a lot of old devices which can not support IPv6 multicast in our network, =
but we are running out of IPv4 address right now. So we can not wait until =
the whole network is ready for IPv6 multicast.<br><br>Hope it clarifies.<br=
><br>Best wishes<br>Qiong<o:p></o:p></p><div><p class=3DMsoNormal style=3D'=
mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Mon, Jun 18, 2012 at=
 11:07 PM, Ronald Bonica &lt;<a href=3D"mailto:rbonica@juniper.net" target=
=3D"_blank">rbonica@juniper.net</a>&gt; wrote:<o:p></o:p></p><div><div><p c=
lass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:aut=
o'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color=
:#1F497D'>Hi Qiong,</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-=
margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11=
.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></=
o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-=
serif";color:#1F497D'>If you were to enable IPv6 multicast throughout your =
network before deploying IPv6 only receivers, would you not fall into use c=
ases 3.4 and 3.5 (the dual stack scenarios). Since you are going to have to=
 enable IPv6 multicast throughout your network anyway, wouldn&#8217;t it be=
 a good idea to do so sooner than later? </span><o:p></o:p></p><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-=
alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; Ron</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-=
top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p=
><div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in=
 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;paddi=
ng:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto=
;mso-margin-bottom-alt:auto'><b><span style=3D'font-size:10.0pt;font-family=
:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;fon=
t-family:"Tahoma","sans-serif"'> Qiong [mailto:<a href=3D"mailto:bingxuere@=
gmail.com" target=3D"_blank">bingxuere@gmail.com</a>] <br><b>Sent:</b> Tues=
day, June 12, 2012 10:11 AM<br><b>To:</b> Lenny Giuliano<br><b>Cc:</b> MBON=
ED WG; Ronald Bonica</span><o:p></o:p></p><div><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><b>Subject:</b>=
 Re: [MBONED] Multicast transition work in MBONED<o:p></o:p></p></div></div=
></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bot=
tom-alt:auto'>&nbsp;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;margin-bottom:12.0pt'>Dear all,<o:p></o:p></p><div><div><p cl=
ass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
'><br><br>1. In our situation, the source may still remian in IPv4, while t=
he receiver will be IPv6-only since there is no more IPv4 address anymore. =
However, the network might be IPv4-only, which can not support IPv6 multica=
st yet; or the network can support IPv6 multicast. This is the case of 6-4.=
 <br>Another situation is: the access network is still IPv4-only, and the c=
ore netowrk (or application platform) is IPv6, then that is the case of 6-4=
-6-4.<br><br>2. Use case: 3.2, 3.4,<br><br>Best wishes<br>Qiong<o:p></o:p><=
/p></div></div><div><div><div><p class=3DMsoNormal style=3D'mso-margin-top-=
alt:auto;mso-margin-bottom-alt:auto'>On Fri, Jun 8, 2012 at 4:34 AM, Leonar=
d Giuliano &lt;<a href=3D"mailto:lenny@juniper.net" target=3D"_blank">lenny=
@juniper.net</a>&gt; wrote:<o:p></o:p></p><p class=3DMsoNormal style=3D'mso=
-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>The multicast transiti=
on work within MBONED was initially intended to consist of ~ 3 document wit=
h limited scope. &nbsp;In a very short amount of time, we've seen 7 drafts =
(and counting) with scope widening.<br><br>In order to make sure we are foc=
using on work that is of actual value to the community and prevent a flood =
of high volume/low value drafts, we would like to revisit the basic questio=
ns of multicast transition within MBONED. &nbsp;We would like to hear answe=
rs from the WG to the following questions before continuing any work on mul=
ticast transition in MBONED:<br><br>1) Which operators intend to source mul=
ticast traffic from one IP version and receive it over another IP version?<=
br><br>2) For those who answer 1), please identify the use-cases of interes=
t in draft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solution=
s for those use cases.<br><br><br>MBONED Chairs<br>________________________=
_______________________<br>MBONED mailing list<br><a href=3D"mailto:MBONED@=
ietf.org" target=3D"_blank">MBONED@ietf.org</a><br><a href=3D"https://www.i=
etf.org/mailman/listinfo/mboned" target=3D"_blank">https://www.ietf.org/mai=
lman/listinfo/mboned</a><o:p></o:p></p></div><p class=3DMsoNormal style=3D'=
mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></=
div></div></div></div></div></div><p class=3DMsoNormal style=3D'mso-margin-=
top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div></div><=
/div></div></div></div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></di=
v></blockquote></div></div></blockquote></div></blockquote><pre>___________=
___________________________________________________________________________=
___________________________________<o:p></o:p></pre><pre><o:p>&nbsp;</o:p><=
/pre><pre>Ce message et ses pieces jointes peuvent contenir des information=
s confidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre><pre>p=
as etre diffuses, exploites ou copies sans autorisation. Si vous avez recu =
ce message par erreur, veuillez le signaler<o:p></o:p></pre><pre>a l'expedi=
teur et le detruire ainsi que les pieces jointes. Les messages electronique=
s etant susceptibles d'alteration,<o:p></o:p></pre><pre>France Telecom - Or=
ange decline toute responsabilite si ce message a ete altere, deforme ou fa=
lsifie. Merci.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>This messag=
e and its attachments may contain confidential or privileged information th=
at may be protected by law;<o:p></o:p></pre><pre>they should not be distrib=
uted, used or copied without authorisation.<o:p></o:p></pre><pre>If you hav=
e received this email in error, please notify the sender and delete this me=
ssage and its attachments.<o:p></o:p></pre><pre>As emails may be altered, F=
rance Telecom - Orange is not liable for messages that have been modified, =
changed or falsified.<o:p></o:p></pre><pre>Thank you.<o:p></o:p></pre></div=
></div></body></html>=

--_000_13205C286662DE4387D9AF3AC30EF456D76EFC667EEMBX01WFjnprn_--

From mmcbride7@gmail.com  Tue Jun 26 17:34:42 2012
Return-Path: <mmcbride7@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C30711E80C1 for <mboned@ietfa.amsl.com>; Tue, 26 Jun 2012 17:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 pzZOP64EjLIF for <mboned@ietfa.amsl.com>; Tue, 26 Jun 2012 17:34:40 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8314B11E80C0 for <mboned@ietf.org>; Tue, 26 Jun 2012 17:34:40 -0700 (PDT)
Received: by yenq13 with SMTP id q13so530651yen.31 for <mboned@ietf.org>; Tue, 26 Jun 2012 17:34:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=LWTcyKAe+AV7Y+9EqM3hI7gHr/m2v6bfGhAnJKUrG/k=; b=hQ7QmWpf7C5YOHIUKVLtIgAssG2ZEtvsxZguZUzm/lgpF+vYUOsmXgT5vfHTRH68wz t0ib16rkvzJkr4jihusl8DD49JenYquUw77s06setm2SUuY79Z106AgXp0eMwmZx+HXq p4HEiZFKyDh2OzuEyTmL91Xnb4nNjQ0a6VgLfzn49Oekc2DfXoBUkhpSxq/6+3K5WYaC LPqA5dYSKJQvrLKW43f+/DzBNDf7aPKzqTv5iJQWD8GZVuVPSPjxRhQips1EBkpsmw7x UV0pRijPyWJ6RlXHSdmVPY21xQ5kdHJHmN2EOvD1L5FtUa+nN4JYnTIjgUq/a+WH6143 1xpw==
MIME-Version: 1.0
Received: by 10.43.106.1 with SMTP id ds1mr9790507icc.24.1340757275952; Tue, 26 Jun 2012 17:34:35 -0700 (PDT)
Received: by 10.64.62.133 with HTTP; Tue, 26 Jun 2012 17:34:35 -0700 (PDT)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76EFC667E@EMBX01-WF.jnpr.net>
References: <20120607132832.I69151@eng-mail01.juniper.net> <CAH3bfAByeQGVCsr1p=Jp456vKn=sw_e945we8r4DmdK8HS+qXA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76E909B8E@EMBX01-WF.jnpr.net> <CAH3bfADtn0q4hN342rLV8QACBP=3pJmqppQwH0xfyoBFtu9BwA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76ECA6070@EMBX01-WF.jnpr.net> <CAH3bfACAzm5v1bzBzc8as4LzRV5J+7DvEdWJCG+4ZgwopiZhjQ@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D76EDCE3CA@EMBX01-WF.jnpr.net> <3A85B6A1-9427-40C9-8D3A-307ACFECE13B@huawei.com> <13205C286662DE4387D9AF3AC30EF456D76EDCE440@EMBX01-WF.jnpr.net> <5A041654-83A8-46D7-8149-6286F05297F5@huawei.com> <13205C286662DE4387D9AF3AC30EF456D76EDCE4FE@EMBX01-WF.jnpr.net> <17386_1340354057_4FE42E09_17386_8210_1_983A1D8DA0DA5F4EB747BF34CBEE5CD15A0EF4E7E0@PUEXCB1C.nanterre.francetelecom.fr> <13205C286662DE4387D9AF3AC30EF456D76EFC667E@EMBX01-WF.jnpr.net>
Date: Tue, 26 Jun 2012 17:34:35 -0700
Message-ID: <CAL3FGfz+FCzXyL5mmR_Es0j3_mc4rcxfXd=wAH4NeSyCeNYO7A@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Multicast transition work in MBONED
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2012 00:34:42 -0000

Ron,

I'd suggest having your "architecturally cleaner" comment added to the
framework draft. And perhaps state that it is the recommendation of
mboned to deploy dual stack in the core whenever possible.

And then further explain the need, of some like Christian, to provide
the adaptation functions. The adaptation work can then proceed even if
its not the mboned preference. The good position we are in is that
there are people/drafts and a wg queued up and ready to go. Its not
like there is no interest in working on the adaptation solutions.

mike

On Fri, Jun 22, 2012 at 6:30 PM, Ronald Bonica <rbonica@juniper.net> wrote:
> Christian,
>
>
>
> In both the 6-4-6 and 4-6-4 cases, it is architecturally cleaner to deplo=
y
> dual stack in the core than it is to deploy the required adaptation
> functions. If a few operators step forward to say that they are deploying=
 in
> the above mentioned scenarios, it might make sense to develop the require=
d
> adaptation functions. However, lacking those operator statements, it make=
s
> little sense for the IETF to specify what may never be deployed.
>
>
>
> I am particularly interested in understanding why an operator would chose
> adaptation over native dual stack. It seems that operational cost and
> complexity associate with adaptation will be greater than that associated
> with running dual stack.
>
>
>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Ron
>
>
>
>
>
> From: christian.jacquenet@orange.com [mailto:christian.jacquenet@orange.c=
om]
> Sent: Friday, June 22, 2012 4:34 AM
> To: Ronald Bonica; Tina TSOU
> Cc: MBONED WG
> Subject: RE: [MBONED] Multicast transition work in MBONED
>
>
>
> Ron, all,
>
>
>
> I have to admit I don't understand why this question about use cases is
> raised again and again, to second one of the comments that were made by
> Simon some time ago.
>
>
>
> This effort initially started with the softwire
> http://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/=A0d=
raft,
> according to the section 3 of the softwire WG charter
> (http://datatracker.ietf.org/wg/softwire/charter/).
>
>
>
> As per an initial request from the softwire WG chairs, several operators =
got
> together to document the accompanying problem statement draft that has be=
en
> further elaborated with the integration of use cases in addition to the
> 4-6-4 use case, and which has now become a mboned WG document, as per the
> poll results that were confirmed some time ago.
>
>
>
> I'm still wondering why the 4-6-4 use case should be ruled out, as it can=
 be
> seen as a consequence of the enforcement of a global IPv6 strategy that
> includes (but is not limited to)=A0the deployment of IPv6 multicast-enabl=
ed
> infrastructures combined with the introduction of techniques that are mea=
nt
> to address the need to access IPv4 contents during the transition period
> where end customers will not be assigned a global IPv4 address anymore.
>
>
>
> Such techniques include DS-Lite.
>
>
>
> I'm not convinced that deploying DS multicast architectures would be
> simpler, but I'm sure such design will certainly not optimize bandwidth
> usage=A0in (at least)=A0the access infrastructures.
>
>
>
> As for the use of an IPv6-only, multicast-enabled, access infrastructure,
> this is something that has been slightly elaborated in the first bullet
> paragraph of section 1 of
> http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00#page-6,
> whereas some operators are currently moving from a service-specific,
> multi-PVC design scheme towards a service-agnostic, single PVC design
> scheme.
>
>
>
> A service-agnostic, single PVC design scheme has the inevitable effect of
> importing global IPv4 address depletion issues into=A0service environment=
s
> which used to rely upon a walled garden, RFC1918-based, design.
>
>
>
> Combined with the introduction of DS-Lite, this leads to the 4-6-4 use
> case.
>
>
>
> Note that the technical feasibility of what is documented in
> http://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicast/=A0h=
as
> already been demonstrated, thanks to a collaboration with a couple of
> vendors.
>
>
>
> Is this 4-6-4 use case more complicated than a DS multicast design? Yes.
>
>
>
> Is this messier? I don't think so, as it primarily depends on service
> provider-specific operational procedures.
>
>
>
> Besides, I'm not convinced that there is room for such hasty qualitative
> appreciation at this stage of the effort.
>
>
>
> I hope this will help closing the debate on the multicast transition use
> cases and that we will all move on. Finally.
>
>
>
> Cheers,
>
>
>
> Christian.
>
>
>
>
>
>
>
>
>
> ________________________________
>
> De=A0: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] De la par=
t de
> Ronald Bonica
> Envoy=E9=A0: jeudi 21 juin 2012 19:12
> =C0=A0: Tina TSOU
> Cc=A0: MBONED WG
> Objet=A0: Re: [MBONED] Multicast transition work in MBONED
>
> Tina,
>
>
>
> It seems that the simplest solution in uses case 3.1 =A0would be to deplo=
y
> dual-stack in the network. Maybe Chris and Med, Nic =A0could explain why =
this
> is not the case?
>
>
>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0Ron
>
>
>
> From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
> Sent: Thursday, June 21, 2012 12:46 PM
> To: Ronald Bonica
> Cc: Qiong; MBONED WG
> Subject: Re: [MBONED] Multicast transition work in MBONED
>
>
>
> I remember Christian, Med and Nic are going to deployed 3.1. Roberta aske=
d
> about 3.3.
>
> Med is out of office these days. Hope the whole Europe is not all in
> vacation.
>
> Tina
>
>
> On Jun 21, 2012, at 9:40 AM, "Ronald Bonica" <rbonica@juniper.net> wrote:
>
> Do we have anybody who is going to deploy 3.1 or 3.3?
>
>
>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Ron
>
>
>
>
>
> From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
> Sent: Thursday, June 21, 2012 12:26 PM
> To: Ronald Bonica
> Cc: Qiong; MBONED WG
> Subject: Re: [MBONED] Multicast transition work in MBONED
>
>
>
> The original question Lenny asked did not including 3.1 and 3.3.
>
> Lenny asked
>
> "1) Which operators intend to source multicast traffic from one IP
> version=A0and receive it over another IP version?"
>
> 3.1 is 4-6-4
>
> 3.2 is 6-4-6.
>
> So they r not In the scope of Lenny's question.
>
>
>
> Tina
>
>
> On Jun 21, 2012, at 9:16 AM, "Ronald Bonica" <rbonica@juniper.net> wrote:
>
> Folks,
>
>
>
> So it looks like use-cases 3.2, 3.4 and 3.5 may see deployment. There wer=
e
> no takers for use-cases 3.1 and 3.3.
>
>
>
> In http://www.ietf.org/mail-archive/web/mboned/current/msg01607.html, Sim=
on
> Perrault suggests two solutions for 3.4 and 3.5. Does the WG agree that
> those are the solutions that we should run with?
>
>
>
> Simon=92s solutions can also be applied to use-case 3.2 if we tunnel over
> non-multicast enabled IPv4 segment. Does everyone agree that that is a go=
od
> idea?
>
>
>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0Ron
>
>
>
> From: Qiong [mailto:bingxuere@gmail.com]
> Sent: Wednesday, June 20, 2012 6:23 AM
> To: Ronald Bonica
> Cc: Lenny Giuliano; MBONED WG
> Subject: Re: [MBONED] Multicast transition work in MBONED
>
>
>
> Hi Ronald,
>
> For your question, it would be too difficult to give you an acurate numbe=
r
> of money/effort, but I can tell you our situation of network upgradation.
>
> In the transition period, it would be impossible to replace all the legac=
y
> IPv4-only devices, especially a great many access network devices. So
> actually, the process would be taken firstly towards our customers and ne=
w
> region. For example, a new customer might get a new=A0 STB with IPv6
> functionality. However, this new customer might access some region only w=
ith
> old devices, then at that time, it will be of great help to implement som=
e
> MLTRANS solutions in the new STB or deploy limited devices in the network=
. I
> believe this will cost less than upgrading the whole network in the first
> place.
>
> For old customers, they will still use IPv4 as they already got address,
> unless we upgrade their STB to support IPv6 remotely. But it is not the
> first priority point.
>
> Best wishes
> Qiong
>
> On Wed, Jun 20, 2012 at 4:48 PM, Ronald Bonica <rbonica@juniper.net> wrot=
e:
>
> Qiong,
>
>
>
> Which of the following do you think will require more money/effort:
>
>
>
> -=A0=A0=A0=A0=A0=A0=A0=A0=A0 To deploy IPv6 multicast throughout your net=
work
>
> -=A0=A0=A0=A0=A0=A0=A0=A0=A0 To deploy the MLTRANS mechanisms that you wi=
ll require to
> compensate for the lack the above mentioned capability
>
>
>
> How much more money/effort? Why?
>
>
>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Ro=
n
>
>
>
>
>
> From: Qiong [mailto:bingxuere@gmail.com]
> Sent: Monday, June 18, 2012 10:03 PM
> To: Ronald Bonica
> Cc: Lenny Giuliano; MBONED WG
>
>
> Subject: Re: [MBONED] Multicast transition work in MBONED
>
>
>
> Hi Ronald,
>
> I agree we do would like to enable IPv6 multicast in our network. However=
,
> all these things can not be achieved within one night. We still have a lo=
t
> of old devices which can not support IPv6 multicast in our network, but w=
e
> are running out of IPv4 address right now. So we can not wait until the
> whole network is ready for IPv6 multicast.
>
> Hope it clarifies.
>
> Best wishes
> Qiong
>
> On Mon, Jun 18, 2012 at 11:07 PM, Ronald Bonica <rbonica@juniper.net> wro=
te:
>
> Hi Qiong,
>
>
>
> If you were to enable IPv6 multicast throughout your network before
> deploying IPv6 only receivers, would you not fall into use cases 3.4 and =
3.5
> (the dual stack scenarios). Since you are going to have to enable IPv6
> multicast throughout your network anyway, wouldn=92t it be a good idea to=
 do
> so sooner than later?
>
>
>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Ron
>
>
>
> From: Qiong [mailto:bingxuere@gmail.com]
> Sent: Tuesday, June 12, 2012 10:11 AM
> To: Lenny Giuliano
> Cc: MBONED WG; Ronald Bonica
>
>
> Subject: Re: [MBONED] Multicast transition work in MBONED
>
>
>
> Dear all,
>
>
>
> 1. In our situation, the source may still remian in IPv4, while the recei=
ver
> will be IPv6-only since there is no more IPv4 address anymore. However, t=
he
> network might be IPv4-only, which can not support IPv6 multicast yet; or =
the
> network can support IPv6 multicast. This is the case of 6-4.
> Another situation is: the access network is still IPv4-only, and the core
> netowrk (or application platform) is IPv6, then that is the case of 6-4-6=
-4.
>
> 2. Use case: 3.2, 3.4,
>
> Best wishes
> Qiong
>
> On Fri, Jun 8, 2012 at 4:34 AM, Leonard Giuliano <lenny@juniper.net> wrot=
e:
>
>
> The multicast transition work within MBONED was initially intended to
> consist of ~ 3 document with limited scope. =A0In a very short amount of =
time,
> we've seen 7 drafts (and counting) with scope widening.
>
> In order to make sure we are focusing on work that is of actual value to =
the
> community and prevent a flood of high volume/low value drafts, we would l=
ike
> to revisit the basic questions of multicast transition within MBONED. =A0=
We
> would like to hear answers from the WG to the following questions before
> continuing any work on multicast transition in MBONED:
>
> 1) Which operators intend to source multicast traffic from one IP version
> and receive it over another IP version?
>
> 2) For those who answer 1), please identify the use-cases of interest in
> draft-ietf-mboned-v4v6-mcast-ps so we can limit discussion to solutions f=
or
> those use cases.
>
>
> MBONED Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>
>
>
>
>
>
>
> _________________________________________________________________________=
________________________________________________
>
>
>
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu
> ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
>
> France Telecom - Orange decline toute responsabilite si ce message a ete
> altere, deforme ou falsifie. Merci.
>
>
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
>
> As emails may be altered, France Telecom - Orange is not liable for messa=
ges
> that have been modified, changed or falsified.
>
> Thank you.
>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>

From stig@venaas.com  Thu Jun 28 14:57:06 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53E8411E80D0 for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 14:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 DJXTvxAYUVis for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 14:57:05 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id A7BF511E80C6 for <mboned@ietf.org>; Thu, 28 Jun 2012 14:57:05 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 87E047FF0 for <mboned@ietf.org>; Thu, 28 Jun 2012 23:57:04 +0200 (CEST)
Message-ID: <4FECD32D.30403@venaas.com>
Date: Thu, 28 Jun 2012 14:57:01 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "mboned@ietf.org" <mboned@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 21:57:06 -0000

The draft draft-ietf-mboned-64-multicast-address-format specifies as you
know, a new flag to indicate that an IPv4 multicast address is embedded.
This is useful for translators (and maybe other devices) that can then
extract the IPv4 address and doing operations as needed on that address.

I would like to present a possible alternative, and hear your thoughts.
What if instead, when the group address is specified in a PIM join, or
an MLD report, there was a flag as part of the PIM/MLD message that
indicated that an IPv4 address is embedded?

A new draft describing this is available at
http://tools.ietf.org/html/draft-kumar-mboned-64mcast-embedded-address-00

What do you think? Might this be an alternative? Are there other
cases (apart from receiving a PIM join or an MLD report), where we
need to know that an IPv4 address is embedded in the group address?

Stig

From Tina.Tsou.Zouting@huawei.com  Thu Jun 28 15:13:14 2012
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8ECE11E80D7 for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 15:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.582
X-Spam-Level: 
X-Spam-Status: No, score=-5.582 tagged_above=-999 required=5 tests=[AWL=1.017,  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 JIH12sDF9mXT for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 15:13:13 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 3C21E11E80D0 for <mboned@ietf.org>; Thu, 28 Jun 2012 15:13:13 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHO51098; Thu, 28 Jun 2012 18:13:13 -0400 (EDT)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 28 Jun 2012 15:11:33 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.109]) by dfweml407-hub.china.huawei.com ([10.193.5.132]) with mapi id 14.01.0323.003; Thu, 28 Jun 2012 15:11:27 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Stig Venaas <stig@venaas.com>
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: AQHNVXr1k0y8HoxuUUiW5KokUsP+cw==
Date: Thu, 28 Jun 2012 22:11:26 +0000
Message-ID: <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com>
References: <4FECD32D.30403@venaas.com>
In-Reply-To: <4FECD32D.30403@venaas.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 22:13:14 -0000

The AD said draft-ietf-mboned-64-multicast-address-format has been moved to=
 WG 6man.

Tina

On Jun 28, 2012, at 2:58 PM, "Stig Venaas" <stig@venaas.com> wrote:

> The draft draft-ietf-mboned-64-multicast-address-format specifies as you
> know, a new flag to indicate that an IPv4 multicast address is embedded.
> This is useful for translators (and maybe other devices) that can then
> extract the IPv4 address and doing operations as needed on that address.
>=20
> I would like to present a possible alternative, and hear your thoughts.
> What if instead, when the group address is specified in a PIM join, or
> an MLD report, there was a flag as part of the PIM/MLD message that
> indicated that an IPv4 address is embedded?
>=20
> A new draft describing this is available at
> http://tools.ietf.org/html/draft-kumar-mboned-64mcast-embedded-address-00
>=20
> What do you think? Might this be an alternative? Are there other
> cases (apart from receiving a PIM join or an MLD report), where we
> need to know that an IPv4 address is embedded in the group address?
>=20
> Stig
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From stig@venaas.com  Thu Jun 28 15:23:34 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C73B11E80E6 for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 15:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 gWCB+oLGDJxa for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 15:23:33 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 7522211E80EA for <mboned@ietf.org>; Thu, 28 Jun 2012 15:23:32 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 2E9517FF0; Fri, 29 Jun 2012 00:23:30 +0200 (CEST)
Message-ID: <4FECD960.8070407@venaas.com>
Date: Thu, 28 Jun 2012 15:23:28 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
References: <4FECD32D.30403@venaas.com> <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com>
In-Reply-To: <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 22:23:34 -0000

On 6/28/2012 3:11 PM, Tina TSOU wrote:
> The AD said draft-ietf-mboned-64-multicast-address-format has been moved to WG 6man.

I know. But I think whether this alternative approach can work is
something we probably need to consider here in mboned. We are the
ones that are looking at translation mechanisms and need some kind
of mechanism to show that an IPv4 address is embedded.

Stig

> Tina
>
> On Jun 28, 2012, at 2:58 PM, "Stig Venaas" <stig@venaas.com> wrote:
>
>> The draft draft-ietf-mboned-64-multicast-address-format specifies as you
>> know, a new flag to indicate that an IPv4 multicast address is embedded.
>> This is useful for translators (and maybe other devices) that can then
>> extract the IPv4 address and doing operations as needed on that address.
>>
>> I would like to present a possible alternative, and hear your thoughts.
>> What if instead, when the group address is specified in a PIM join, or
>> an MLD report, there was a flag as part of the PIM/MLD message that
>> indicated that an IPv4 address is embedded?
>>
>> A new draft describing this is available at
>> http://tools.ietf.org/html/draft-kumar-mboned-64mcast-embedded-address-00
>>
>> What do you think? Might this be an alternative? Are there other
>> cases (apart from receiving a PIM join or an MLD report), where we
>> need to know that an IPv4 address is embedded in the group address?
>>
>> Stig
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned



From albert.e.manfredi@boeing.com  Thu Jun 28 15:26:09 2012
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A22711E80EE for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 15:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Vk6lWb+NvSKF for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 15:26:08 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id F3C4811E80E1 for <mboned@ietf.org>; Thu, 28 Jun 2012 15:26:07 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q5SMQ8oN017705 for <mboned@ietf.org>; Thu, 28 Jun 2012 15:26:08 -0700
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.16.37]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q5SMQ8in017702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 28 Jun 2012 15:26:08 -0700
Received: from blv-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q5SMQ6rq025295; Thu, 28 Jun 2012 15:26:06 -0700
Received: from XCH-MWHT-05.mw.nos.boeing.com (xch-mwht-05.mw.nos.boeing.com [134.57.119.160]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q5SMQ6UF025284 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 28 Jun 2012 15:26:06 -0700
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.118.180]) by XCH-MWHT-05.mw.nos.boeing.com ([134.57.119.160]) with mapi; Thu, 28 Jun 2012 17:26:06 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Stig Venaas <stig@venaas.com>
Date: Thu, 28 Jun 2012 17:26:04 -0500
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: Ac1VfKvCX/xLwhMORFmgWlSCFUIbkQAADIuQ
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02BC4A5ADC@XCH-MW-08V.mw.nos.boeing.com>
References: <4FECD32D.30403@venaas.com> <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com> <4FECD960.8070407@venaas.com>
In-Reply-To: <4FECD960.8070407@venaas.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] An alternative to	draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 22:26:09 -0000

Wait, is there any reason to require anything more than a predictable IPv6 =
multicast address prefix for this?

Bert

-----Original Message-----
From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of=
 Stig Venaas
Sent: Thursday, June 28, 2012 6:23 PM
To: Tina TSOU
Cc: mboned@ietf.org
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-addr=
ess-format?

On 6/28/2012 3:11 PM, Tina TSOU wrote:
> The AD said draft-ietf-mboned-64-multicast-address-format has been moved =
to WG 6man.

I know. But I think whether this alternative approach can work is
something we probably need to consider here in mboned. We are the
ones that are looking at translation mechanisms and need some kind
of mechanism to show that an IPv4 address is embedded.

Stig

> Tina
>
> On Jun 28, 2012, at 2:58 PM, "Stig Venaas" <stig@venaas.com> wrote:
>
>> The draft draft-ietf-mboned-64-multicast-address-format specifies as you
>> know, a new flag to indicate that an IPv4 multicast address is embedded.
>> This is useful for translators (and maybe other devices) that can then
>> extract the IPv4 address and doing operations as needed on that address.
>>
>> I would like to present a possible alternative, and hear your thoughts.
>> What if instead, when the group address is specified in a PIM join, or
>> an MLD report, there was a flag as part of the PIM/MLD message that
>> indicated that an IPv4 address is embedded?
>>
>> A new draft describing this is available at
>> http://tools.ietf.org/html/draft-kumar-mboned-64mcast-embedded-address-0=
0
>>
>> What do you think? Might this be an alternative? Are there other
>> cases (apart from receiving a PIM join or an MLD report), where we
>> need to know that an IPv4 address is embedded in the group address?
>>
>> Stig
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned


_______________________________________________
MBONED mailing list
MBONED@ietf.org
https://www.ietf.org/mailman/listinfo/mboned

From stig@venaas.com  Thu Jun 28 15:33:08 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59C7211E80E1 for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 15:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2SnlN16g9ro3 for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 15:33:07 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 6EA2E11E80D7 for <mboned@ietf.org>; Thu, 28 Jun 2012 15:33:07 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id E92047FF0; Fri, 29 Jun 2012 00:33:05 +0200 (CEST)
Message-ID: <4FECDBA0.3090405@venaas.com>
Date: Thu, 28 Jun 2012 15:33:04 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
References: <4FECD32D.30403@venaas.com> <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com> <4FECD960.8070407@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5ADC@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BC4A5ADC@XCH-MW-08V.mw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 22:33:08 -0000

On 6/28/2012 3:26 PM, Manfredi, Albert E wrote:
> Wait, is there any reason to require anything more than a predictable IPv6 multicast address prefix for this?

This would be instead of a predictable prefix.

Regarding predictable prefix. As in
draft-ietf-mboned-64-multicast-address-format

I don't think you can have just 96 fixed bits though. I'm not quite sure
what you mean by predictable.

If there is nothing in say a PIM (S,G)-join (in the group address or in
the PIM message) to say that G has a 32-bits IPv4 multicast address
embedded, then the best I can think of is to configure the devices so
that they know that a specific IPv6 prefix has an address embedded. But
I don't think it can be a fixed well-known hardcoded address.

Stig

> Bert
>
> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of Stig Venaas
> Sent: Thursday, June 28, 2012 6:23 PM
> To: Tina TSOU
> Cc: mboned@ietf.org
> Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
>
> On 6/28/2012 3:11 PM, Tina TSOU wrote:
>> The AD said draft-ietf-mboned-64-multicast-address-format has been moved to WG 6man.
>
> I know. But I think whether this alternative approach can work is
> something we probably need to consider here in mboned. We are the
> ones that are looking at translation mechanisms and need some kind
> of mechanism to show that an IPv4 address is embedded.
>
> Stig
>
>> Tina
>>
>> On Jun 28, 2012, at 2:58 PM, "Stig Venaas" <stig@venaas.com> wrote:
>>
>>> The draft draft-ietf-mboned-64-multicast-address-format specifies as you
>>> know, a new flag to indicate that an IPv4 multicast address is embedded.
>>> This is useful for translators (and maybe other devices) that can then
>>> extract the IPv4 address and doing operations as needed on that address.
>>>
>>> I would like to present a possible alternative, and hear your thoughts.
>>> What if instead, when the group address is specified in a PIM join, or
>>> an MLD report, there was a flag as part of the PIM/MLD message that
>>> indicated that an IPv4 address is embedded?
>>>
>>> A new draft describing this is available at
>>> http://tools.ietf.org/html/draft-kumar-mboned-64mcast-embedded-address-00
>>>
>>> What do you think? Might this be an alternative? Are there other
>>> cases (apart from receiving a PIM join or an MLD report), where we
>>> need to know that an IPv4 address is embedded in the group address?
>>>
>>> Stig
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>



From albert.e.manfredi@boeing.com  Thu Jun 28 16:06:13 2012
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F27B111E80D3 for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 16:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 PweNPOLB1m9H for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 16:06:11 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id D324111E8088 for <mboned@ietf.org>; Thu, 28 Jun 2012 16:06:11 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q5SN6A7H024087 for <mboned@ietf.org>; Thu, 28 Jun 2012 16:06:10 -0700
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [130.247.228.54]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q5SN69Fs024069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 28 Jun 2012 16:06:10 -0700
Received: from stl-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q5SN696K022501; Thu, 28 Jun 2012 18:06:09 -0500
Received: from XCH-MWHT-03.mw.nos.boeing.com (xch-mwht-03.mw.nos.boeing.com [134.57.119.161]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q5SN69kH022490 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 28 Jun 2012 18:06:09 -0500
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.118.180]) by XCH-MWHT-03.mw.nos.boeing.com ([134.57.119.161]) with mapi; Thu, 28 Jun 2012 18:06:09 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Stig Venaas <stig@venaas.com>
Date: Thu, 28 Jun 2012 18:06:08 -0500
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: Ac1VfgGXXue0HAS8QL6Ib7mmjpRyqgAA3/Pg
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02BC4A5AE1@XCH-MW-08V.mw.nos.boeing.com>
References: <4FECD32D.30403@venaas.com> <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com> <4FECD960.8070407@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5ADC@XCH-MW-08V.mw.nos.boeing.com> <4FECDBA0.3090405@venaas.com>
In-Reply-To: <4FECDBA0.3090405@venaas.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 23:06:13 -0000

> -----Original Message-----
> From: Stig Venaas [mailto:stig@venaas.com]

> I don't think you can have just 96 fixed bits though. I'm not quite
> sure
> what you mean by predictable.
>=20
> If there is nothing in say a PIM (S,G)-join (in the group address or in
> the PIM message) to say that G has a 32-bits IPv4 multicast address
> embedded, then the best I can think of is to configure the devices so
> that they know that a specific IPv6 prefix has an address embedded. But
> I don't think it can be a fixed well-known hardcoded address.

For networks that are NOT dual stack, the scheme has to work for 6 to 4 and=
 4 to 6.

So, the way I see it working, the easiest solution is to have a single, fix=
ed, 96-bit IPv6 multicast prefix, for multicasts that have to do this trave=
rsing back and forth.

1. The ingress router to an IPv4-only network can detect that the IPv4 addr=
ess is embedded.

2. The egress router from the IPv4 network to the IPv6 network can know wha=
t IPv6 prefix to add.

I don't see how a flag in the IPv6 multicast address can solve both problem=
s, UNLESS we also create a new subgroup of IPv4 multicast addresses?

Bert


From stig@venaas.com  Thu Jun 28 21:03:38 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED7E311E80DC for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 21:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 qbQuCrLcH4WG for <mboned@ietfa.amsl.com>; Thu, 28 Jun 2012 21:03:37 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 4844D11E80A4 for <mboned@ietf.org>; Thu, 28 Jun 2012 21:03:37 -0700 (PDT)
Received: from [10.21.80.199] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 650717FF0; Fri, 29 Jun 2012 06:03:32 +0200 (CEST)
Message-ID: <4FED2926.60300@venaas.com>
Date: Thu, 28 Jun 2012 21:03:50 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
References: <4FECD32D.30403@venaas.com> <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com> <4FECD960.8070407@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5ADC@XCH-MW-08V.mw.nos.boeing.com> <4FECDBA0.3090405@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5AE1@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BC4A5AE1@XCH-MW-08V.mw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 04:03:38 -0000

On 28.06.2012 16:06, Manfredi, Albert E wrote:
>> -----Original Message-----
>> From: Stig Venaas [mailto:stig@venaas.com]
>
>> I don't think you can have just 96 fixed bits though. I'm not quite
>> sure
>> what you mean by predictable.
>>
>> If there is nothing in say a PIM (S,G)-join (in the group address or in
>> the PIM message) to say that G has a 32-bits IPv4 multicast address
>> embedded, then the best I can think of is to configure the devices so
>> that they know that a specific IPv6 prefix has an address embedded. But
>> I don't think it can be a fixed well-known hardcoded address.
>
> For networks that are NOT dual stack, the scheme has to work for 6 to 4 and 4 to 6.
>
> So, the way I see it working, the easiest solution is to have a single, fixed, 96-bit IPv6 multicast prefix, for multicasts that have to do this traversing back and forth.

Yes, this can work. And is also what I've been assuming in a couple
of drafts a wrote some years ago.

This can be a well-known prefix (say specified in an RFC), but I think
I might prefer implementations to rather be configured. But that means
I think, that there need to be some coordination between different
devices.

To solve this, there is draft-ietf-mboned-64-multicast-address-format.
Now I'm saying that this draft may be an alternative way of
accomplishing this.

I think we may need to further consider solutions to see what is needed.
There is a draft in WGLC in softwire though that makes use of the
address-format draft.

> 1. The ingress router to an IPv4-only network can detect that the IPv4 address is embedded.
>
> 2. The egress router from the IPv4 network to the IPv6 network can know what IPv6 prefix to add.
>
> I don't see how a flag in the IPv6 multicast address can solve both problems, UNLESS we also create a new subgroup of IPv4 multicast addresses?

For multicast things are kind of reversed. From say PIM perspective, you
can start out with someone joining an IPv6 group where the last 32 bits
form an IPv4 group address. When this IPv6 join reaches say a device on
the edge of the IPv4 network, it can based on configuration (or
hard-coded if a standardized prefix), or a flag in the group address,
or a join attribute (these are the solutions I think we have on the
table), know that it should extract those 32 bits, and join the IPv4
source. When it receives IPv4 data packets, it can based on its PIM
state know what IPv6 address to translate them to.

There are other use-cases, this is maybe the easiest one.

Stig

> Bert


From albert.e.manfredi@boeing.com  Fri Jun 29 12:35:20 2012
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56E8321F88B9 for <mboned@ietfa.amsl.com>; Fri, 29 Jun 2012 12:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 tm4gsjXCMSpX for <mboned@ietfa.amsl.com>; Fri, 29 Jun 2012 12:35:19 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id C251A21F88B3 for <mboned@ietf.org>; Fri, 29 Jun 2012 12:35:19 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q5TJZI1I012878 for <mboned@ietf.org>; Fri, 29 Jun 2012 12:35:18 -0700
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [130.247.228.54]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q5TJZGpE012800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 29 Jun 2012 12:35:18 -0700
Received: from stl-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q5TJZHSj023404; Fri, 29 Jun 2012 14:35:17 -0500
Received: from XCH-MWHT-02.mw.nos.boeing.com (xch-mwht-02.mw.nos.boeing.com [134.57.113.20]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q5TJZHxv023384 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 29 Jun 2012 14:35:17 -0500
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.118.180]) by XCH-MWHT-02.mw.nos.boeing.com ([134.57.113.20]) with mapi; Fri, 29 Jun 2012 14:35:17 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Stig Venaas <stig@venaas.com>
Date: Fri, 29 Jun 2012 14:35:09 -0500
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: Ac1VrC3M+3C5NZcfREmVwLy7VF0LJAAgWhmQ
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02BC4A5D35@XCH-MW-08V.mw.nos.boeing.com>
References: <4FECD32D.30403@venaas.com> <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com> <4FECD960.8070407@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5ADC@XCH-MW-08V.mw.nos.boeing.com> <4FECDBA0.3090405@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5AE1@XCH-MW-08V.mw.nos.boeing.com> <4FED2926.60300@venaas.com>
In-Reply-To: <4FED2926.60300@venaas.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 19:35:20 -0000

> -----Original Message-----


> For multicast things are kind of reversed. From say PIM perspective,
> you
> can start out with someone joining an IPv6 group where the last 32 bits
> form an IPv4 group address. When this IPv6 join reaches say a device on
> the edge of the IPv4 network, it can based on configuration (or
> hard-coded if a standardized prefix), or a flag in the group address,
> or a join attribute (these are the solutions I think we have on the
> table), know that it should extract those 32 bits, and join the IPv4
> source. When it receives IPv4 data packets, it can based on its PIM
> state know what IPv6 address to translate them to.
>=20
> There are other use-cases, this is maybe the easiest one.

This seems similar yo what I had described, except that the 96-bit prefix i=
s configurable (presumably there will be an OOB mechanism to indicate what =
the prefix should be), AND it also seems to depend on PIM.

What about cases in which PIM isn't used? For example, where proxy IGMP or =
proxy MLD is used, to make multicasts traversing a network available to an =
egress router? Or are we saying that it's okay to have incompatible solutio=
ns depending on each use case?

Bert


From stig@venaas.com  Fri Jun 29 14:32:46 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D14B21F859B for <mboned@ietfa.amsl.com>; Fri, 29 Jun 2012 14:32:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 uiWM8wPVUEnn for <mboned@ietfa.amsl.com>; Fri, 29 Jun 2012 14:32:46 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id C8BE521F8594 for <mboned@ietf.org>; Fri, 29 Jun 2012 14:32:45 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 7ABBB7FEB; Fri, 29 Jun 2012 23:32:43 +0200 (CEST)
Message-ID: <4FEE1EDF.7010907@venaas.com>
Date: Fri, 29 Jun 2012 14:32:15 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
References: <4FECD32D.30403@venaas.com> <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com> <4FECD960.8070407@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5ADC@XCH-MW-08V.mw.nos.boeing.com> <4FECDBA0.3090405@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5AE1@XCH-MW-08V.mw.nos.boeing.com> <4FED2926.60300@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5D35@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BC4A5D35@XCH-MW-08V.mw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 21:32:46 -0000

On 6/29/2012 12:35 PM, Manfredi, Albert E wrote:
>> -----Original Message-----
>
>
>> For multicast things are kind of reversed. From say PIM perspective,
>> you
>> can start out with someone joining an IPv6 group where the last 32 bits
>> form an IPv4 group address. When this IPv6 join reaches say a device on
>> the edge of the IPv4 network, it can based on configuration (or
>> hard-coded if a standardized prefix), or a flag in the group address,
>> or a join attribute (these are the solutions I think we have on the
>> table), know that it should extract those 32 bits, and join the IPv4
>> source. When it receives IPv4 data packets, it can based on its PIM
>> state know what IPv6 address to translate them to.
>>
>> There are other use-cases, this is maybe the easiest one.
>
> This seems similar yo what I had described, except that the 96-bit prefix is configurable (presumably there will be an OOB mechanism to indicate what the prefix should be), AND it also seems to depend on PIM.

I guess I could try to explain why I think a fixed well-defined prefix
is a bit too limiting. It could work in some cases though. When I say
configurable, it could in theory be passed via some other protocol.

> What about cases in which PIM isn't used? For example, where proxy IGMP or proxy MLD is used, to make multicasts traversing a network available to an egress router? Or are we saying that it's okay to have incompatible solutions depending on each use case?

For this new proposal, we're describing a flag that can be used in
IGMP/MLD messages, so not just PIM. Using a bit in the group address
also obviously works for IGMP/MLD.

Do you think we should have some discussion along these lines in the
next mboned meeting? I would be happy to try to present all the
alternatives.

Stig

> Bert
>



From Tina.Tsou.Zouting@huawei.com  Fri Jun 29 18:42:43 2012
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BCE021F8421 for <mboned@ietfa.amsl.com>; Fri, 29 Jun 2012 18:42:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.674
X-Spam-Level: 
X-Spam-Status: No, score=-5.674 tagged_above=-999 required=5 tests=[AWL=0.925,  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 N0rq7wfTKRTr for <mboned@ietfa.amsl.com>; Fri, 29 Jun 2012 18:42:41 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id C115E21F841D for <mboned@ietf.org>; Fri, 29 Jun 2012 18:42:41 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHI05135; Fri, 29 Jun 2012 21:42:38 -0400 (EDT)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 29 Jun 2012 18:41:29 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.109]) by dfweml407-hub.china.huawei.com ([10.193.5.132]) with mapi id 14.01.0323.003; Fri, 29 Jun 2012 18:41:23 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Stig Venaas <stig@venaas.com>
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: AQHNVi5bmeS2biyti0iWC24nf7E7XJcSFkcQ
Date: Sat, 30 Jun 2012 01:41:22 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A80D447A49@dfweml513-mbx.china.huawei.com>
References: <4FECD32D.30403@venaas.com> <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com> <4FECD960.8070407@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5ADC@XCH-MW-08V.mw.nos.boeing.com> <4FECDBA0.3090405@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5AE1@XCH-MW-08V.mw.nos.boeing.com> <4FED2926.60300@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5D35@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BC4A5D35@XCH-MW-08V.mw.nos.boeing.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.212.245.114]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jun 2012 01:42:43 -0000

The fixed 96 bits and then 32 bits of the IPv4 address is a simpler and bet=
ter approach according to me, as described in http://tools.ietf.org/html/dr=
aft-ietf-mboned-64-multicast-address-format-02. However, this http://tools.=
ietf.org/html/draft-kumar-mboned-64mcast-embedded-address-00 document has i=
ts advantages of 6-4-6-4 scenario which is missing in the alternative docum=
ent. The only point I would like to stress upon is if it covers the scenari=
o of 6-4-6, as IPv6 multicast address expressed in terms of IPv4 is somethi=
ng I didn't find in the document. I am only concerned about the validity of=
 the attributes in an IPv4 only multicast network. Would tunnels be used to=
 route the IPv6 packets with the end routers being dual stack?

Tina


> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf
> Of Manfredi, Albert E
> Sent: Friday, June 29, 2012 12:35 PM
> To: Stig Venaas
> Cc: mboned@ietf.org
> Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-
> address-format?
>=20
> > -----Original Message-----
>=20
>=20
> > For multicast things are kind of reversed. From say PIM perspective,
> > you
> > can start out with someone joining an IPv6 group where the last 32 bits
> > form an IPv4 group address. When this IPv6 join reaches say a device on
> > the edge of the IPv4 network, it can based on configuration (or
> > hard-coded if a standardized prefix), or a flag in the group address,
> > or a join attribute (these are the solutions I think we have on the
> > table), know that it should extract those 32 bits, and join the IPv4
> > source. When it receives IPv4 data packets, it can based on its PIM
> > state know what IPv6 address to translate them to.
> >
> > There are other use-cases, this is maybe the easiest one.
>=20
> This seems similar yo what I had described, except that the 96-bit prefix
> is configurable (presumably there will be an OOB mechanism to indicate
> what the prefix should be), AND it also seems to depend on PIM.
>=20
> What about cases in which PIM isn't used? For example, where proxy IGMP o=
r
> proxy MLD is used, to make multicasts traversing a network available to a=
n
> egress router? Or are we saying that it's okay to have incompatible
> solutions depending on each use case?
>=20
> Bert
>=20
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From tom.taylor.stds@gmail.com  Sat Jun 30 09:47:57 2012
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F73021F8503 for <mboned@ietfa.amsl.com>; Sat, 30 Jun 2012 09:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 6jycBWr1Qksz for <mboned@ietfa.amsl.com>; Sat, 30 Jun 2012 09:47:56 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id BA1EB21F8427 for <mboned@ietf.org>; Sat, 30 Jun 2012 09:47:56 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so6182366obb.31 for <mboned@ietf.org>; Sat, 30 Jun 2012 09:47:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=n9+MKArGN34BVK7AsP5EFpr2EDfh5kxwLPBVY0So1Bg=; b=TnrE14Cb1bDrrlXl/YPZhOCYYEEcVPfpBDdfvu/t4KN9Qa6F1QqTXgT9bEw/fdu/q9 l9dm89LDXW5Ca3/SscRL7FhUj1+CgPV/qeM7Vq9QuA7HQiGyV9N+Eb8bu7+w31Y21tiZ BRzGugvGKe8Rr1ruYGyUj63Wl1R2qcBkCFkIls2uOe24/yHU4lCo5bMsR2gnThgSJpTt jfnG2eJ3TbFduEht/SShxOsHfw+rpjD/cXNhP9RVM/wu3hm4mVDiUFQaqV795TM7+aGh bZaDIN8BsQZwSNhKlBBv8drC7xSYDpwYGWUOzhtbVhWfLMLZigyGzpji9R1Moowb8nV4 CWVA==
Received: by 10.182.207.39 with SMTP id lt7mr986023obc.67.1341074877107; Sat, 30 Jun 2012 09:47:57 -0700 (PDT)
Received: from [127.0.0.1] ([207.112.119.108]) by mx.google.com with ESMTPS id k8sm5434601oeh.9.2012.06.30.09.47.55 (version=SSLv3 cipher=OTHER); Sat, 30 Jun 2012 09:47:56 -0700 (PDT)
Message-ID: <4FEF2DB9.2030809@gmail.com>
Date: Sat, 30 Jun 2012 12:47:53 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Stig Venaas <stig@venaas.com>
References: <4FECD32D.30403@venaas.com> <EE15DDE8-F921-4F9F-B0B4-704A8BD10045@huawei.com> <4FECD960.8070407@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5ADC@XCH-MW-08V.mw.nos.boeing.com> <4FECDBA0.3090405@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5AE1@XCH-MW-08V.mw.nos.boeing.com> <4FED2926.60300@venaas.com> <B0147C3DD45E42478038FC347CCB65FE02BC4A5D35@XCH-MW-08V.mw.nos.boeing.com> <4FEE1EDF.7010907@venaas.com>
In-Reply-To: <4FEE1EDF.7010907@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120630-0, 30/06/2012), Outbound message
X-Antivirus-Status: Clean
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jun 2012 16:47:57 -0000

I think such a discussion would be a great idea. As usual we need use 
cases to measure the proposals against. You seem to have some in mind 
when you refer to "some cases". We also need criteria. One of them is 
the amount of administration required.

It would be good to preserve the advantages of embedded RP. You 
certainly can't have a well-known /96 and use embedded RP. RFC 3956 
seems to leave four bits open (aside from the unused flag) -- the four 
bits between scop and RIID. One could contemplate using one of those to 
indicate that an embedded IPv4 address is present as well as an embedded 
RP address. That still leaves the need for an equivalent representation 
when not using embedded RP.

On 29/06/2012 5:32 PM, Stig Venaas wrote:
> On 6/29/2012 12:35 PM, Manfredi, Albert E wrote:
>>> -----Original Message-----
>>
>>
...
>
> I guess I could try to explain why I think a fixed well-defined prefix
> is a bit too limiting. It could work in some cases though. When I say
> configurable, it could in theory be passed via some other protocol.
>
>> What about cases in which PIM isn't used? For example, where proxy
>> IGMP or proxy MLD is used, to make multicasts traversing a network
>> available to an egress router? Or are we saying that it's okay to have
>> incompatible solutions depending on each use case?
>
> For this new proposal, we're describing a flag that can be used in
> IGMP/MLD messages, so not just PIM. Using a bit in the group address
> also obviously works for IGMP/MLD.
>
> Do you think we should have some discussion along these lines in the
> next mboned meeting? I would be happy to try to present all the
> alternatives.
>
> Stig
>
>> Bert
>>
>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>

