
From albert.e.manfredi@boeing.com  Sun Jul  1 15:12:37 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 56CC721F88F3 for <mboned@ietfa.amsl.com>; Sun,  1 Jul 2012 15:12:37 -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 DezdCOcZXAzm for <mboned@ietfa.amsl.com>; Sun,  1 Jul 2012 15:12:36 -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 A715321F88AB for <mboned@ietf.org>; Sun,  1 Jul 2012 15:12:36 -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 q61MCdAP030137 for <mboned@ietf.org>; Sun, 1 Jul 2012 15:12:39 -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 q61MCaTt030124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 1 Jul 2012 15:12:37 -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 q61MCakc027468; Sun, 1 Jul 2012 15:12:36 -0700
Received: from XCH-MWHT-03.mw.nos.boeing.com (xch-mwht-03.mw.nos.boeing.com [134.57.119.161]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q61MCape027174 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Sun, 1 Jul 2012 15:12:36 -0700
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; Sun, 1 Jul 2012 17:12:35 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Date: Sun, 1 Jul 2012 17:12:32 -0500
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: AQHNVi5bmeS2biyti0iWC24nf7E7XJcSFkcQgALnICA=
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02BC4A5DB5@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> <B0147C3DD45E42478038FC347CCB65FE02BC4A5D35@XCH-MW-08V.mw.nos.boeing.com> <C0E0A32284495243BDE0AC8A066631A80D447A49@dfweml513-mbx.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80D447A49@dfweml513-mbx.china.huawei.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: Sun, 01 Jul 2012 22:12:37 -0000

I'm always in favor of simple solutions that don't have a lot of prerequisi=
tes. But I do get the complaint that a fixed 96-bit multicast prefix invali=
dates the embedded RP technique.

So for example, let's say we have an IPv4-only transit network, surrounded =
by IPv6 networks. And multicasts that want to be receivable by hosts on eit=
her 6 or 4 networks.

The edge routers to IPv6 networks, from this IPv4-only network, are presuma=
bly all smart enough to speak IPv6 on the outside interfaces. So we create =
an "all routers" multicast, inside the IPv4-only network, that periodically=
 transmits a static table showing the mapping of IPv4 address to IPv6 multi=
cast prefix. That way, all egress routers can reformulate the IPv6 header.

This would seem to make tunneling, dependence on PIM-SM, and multicast dupl=
icating unnecessary in the IPv4 network, no?

This is not my use case, as we have dual stacked networks. However if faced=
 with such a problem, I would not hesitate to cook my own solution along th=
ese lines. Did I miss some fundamental problem?

Bert

> -----Original Message-----
> From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
> Sent: Friday, June 29, 2012 9:41 PM
> To: Manfredi, Albert E; Stig Venaas
> Cc: mboned@ietf.org
> Subject: RE: [MBONED] An alternative to draft-ietf-mboned-64-multicast-
> address-format?
>=20
> The fixed 96 bits and then 32 bits of the IPv4 address is a simpler and
> better approach according to me, as described in
> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-
> format-02. However, this http://tools.ietf.org/html/draft-kumar-mboned-
> 64mcast-embedded-address-00 document has its advantages of 6-4-6-4
> scenario which is missing in the alternative document. The only point I
> would like to stress upon is if it covers the scenario of 6-4-6, as
> IPv6 multicast address expressed in terms of IPv4 is something 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?
>=20
> Tina
>=20
>=20
> > -----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?
> >
> > > -----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.
> >
> > 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?
> >
> > Bert
> >
> > _______________________________________________
> > MBONED mailing list
> > MBONED@ietf.org
> > https://www.ietf.org/mailman/listinfo/mboned

From rbonica@juniper.net  Mon Jul  2 07:27:46 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 46F7D21F84DE for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 07:27:46 -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.025, 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 iyX-CKZEDhXP for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 07:27:45 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 6C96D21F84B9 for <mboned@ietf.org>; Mon,  2 Jul 2012 07:27:45 -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/Gv5gTVrP4xGxvRH8io4KwsoerG8KxH@postini.com; Mon, 02 Jul 2012 07:27: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; Mon, 2 Jul 2012 07:27:30 -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, 2 Jul 2012 10:27:29 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Mon, 2 Jul 2012 10:27:27 -0400
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: Ac1WYemRo9GBBAIsT6O34PFLgQvYLQB+sRIQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76F687E26@EMBX01-WF.jnpr.net>
References: <mailman.4264.1341020564.3336.mboned@ietf.org>
In-Reply-To: <mailman.4264.1341020564.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] 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: Mon, 02 Jul 2012 14:27:46 -0000

Tina,

We should be remember two things wrt address formats:

- the MLTRANS problem will be with us only for a short time (until walled-g=
arden IPTV providers upgrade to IPv6)
- changes that we make to the IPv6 addressing scheme will be with us foreve=
r

So, in the interest of keeping the IPv6 addressing scheme simple, we should=
 try our best to limit the number of uses cases that we support and make th=
e smallest possible change to the IPv6 addressing scheme. It doesn't make s=
ense to complicate the IPv6 addressing scheme in order to support a use-cas=
e that will rarely or never be deployed.

                                       Ron
                                       /speaking as AD


> Date: Sat, 30 Jun 2012 01:41:22 +0000
> From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
> To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Stig Venaas
> 	<stig@venaas.com>
> Cc: "mboned@ietf.org" <mboned@ietf.org>
> Subject: Re: [MBONED] An alternative to
> 	draft-ietf-mboned-64-multicast-address-format?
>=20
> The fixed 96 bits and then 32 bits of the IPv4 address is a simpler and
> better approach according to me, as described in
> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-
> format-02. However, this http://tools.ietf.org/html/draft-kumar-mboned-
> 64mcast-embedded-address-00 document has its advantages of 6-4-6-4
> scenario which is missing in the alternative document. The only point I
> would like to stress upon is if it covers the scenario of 6-4-6, as
> IPv6 multicast address expressed in terms of IPv4 is something 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?
>=20
> Tina
>=20
>=20
**********

From naikumar@cisco.com  Sun Jul  1 01:58:03 2012
Return-Path: <naikumar@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 9991F21F8493 for <mboned@ietfa.amsl.com>; Sun,  1 Jul 2012 01:58:03 -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 yqloyC6ZN-cB for <mboned@ietfa.amsl.com>; Sun,  1 Jul 2012 01:58:02 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 68B4221F8491 for <mboned@ietf.org>; Sun,  1 Jul 2012 01:58:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=naikumar@cisco.com; l=3567; q=dns/txt; s=iport; t=1341133084; x=1342342684; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=vj7X9AsYcFgwMOhpGw387ny/k3BjQwqci8Kv9qCJssw=; b=A0GNWsF5stuE5VoOX9LWcNyVZMsB8hnxsu5tOxzJrEUwB1xMggsK3XvK pUKz/z72xqTMHZfpyQMs3AJAQ7EO57jpem+kaHqhNUpwXWO9KzNnna5p1 7NLSQuXUTVHMmKD426Hy3/MNV93IY9YVMV60BGfCpJHsMZDJk//JXzxIE U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAIoQ8E+tJV2b/2dsb2JhbABFtliBB4IYAQEBBAEBAQ8BJzQLDAQCAQgRBAEBCxQJBycLFAkIAgQBCQQFCBMHh2kLm2OfFIs7hTpgA5ZGjQuBZoJf
X-IronPort-AV: E=Sophos;i="4.77,504,1336348800"; d="scan'208";a="97684410"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP; 01 Jul 2012 08:58:03 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q618w2p5000919 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 1 Jul 2012 08:58:02 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.154]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0298.004; Sun, 1 Jul 2012 03:58:02 -0500
From: "Nagendra Kumar (naikumar)" <naikumar@cisco.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "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: AQHNVi5VQ5Smo6vw00OI2MHPt8AL2pcSalwAgAGfJ9A=
Date: Sun, 1 Jul 2012 08:58:01 +0000
Message-ID: <47E76F08F1BCF5458111C1939C7B9C460450C5@xmb-rcd-x03.cisco.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> <C0E0A32284495243BDE0AC8A066631A80D447A49@dfweml513-mbx.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80D447A49@dfweml513-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.95.213]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19010.004
x-tm-as-result: No--53.841900-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 02 Jul 2012 08:50:34 -0700
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: Sun, 01 Jul 2012 08:58:03 -0000

Hi Tina,

Thanks for your thoughts. For 6-4-6 scenarios, I think it may not require t=
o signal if or not v4 address is embedded as IPv4 cloud will be transit her=
e. I guess Tunneling, AMT or MVPN kind of solution might be apt here.

Regarding the attribute in IPv4 only network, even if there is a requiremen=
t to transparently transfer attribute via v4 cloud, per my understanding, i=
t still can be done by setting the F bit. So just the ingress and egress de=
vices are required to understand the content of attribute.

Regards,
Nagendra

-----Original Message-----
From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of=
 Tina TSOU
Sent: Saturday, June 30, 2012 7:11 AM
To: Manfredi, Albert E; Stig Venaas
Cc: mboned@ietf.org
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-addr=
ess-format?

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=20
> 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=20
> draft-ietf-mboned-64-multicast- address-format?
>=20
> > -----Original Message-----
>=20
>=20
> > For multicast things are kind of reversed. From say PIM perspective,=20
> > you can start out with someone joining an IPv6 group where the last=20
> > 32 bits form an IPv4 group address. When this IPv6 join reaches say=20
> > a device on the edge of the IPv4 network, it can based on=20
> > configuration (or hard-coded if a standardized prefix), or a flag in=20
> > the group address, or a join attribute (these are the solutions I=20
> > think we have on the table), know that it should extract those 32=20
> > bits, and join the IPv4 source. When it receives IPv4 data packets,=20
> > it can based on its PIM state know what IPv6 address to translate=20
> > 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=20
> prefix is configurable (presumably there will be an OOB mechanism to=20
> 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=20
> IGMP or proxy MLD is used, to make multicasts traversing a network=20
> available to an egress router? Or are we saying that it's okay to have=20
> incompatible solutions depending on each use case?
>=20
> Bert
>=20
> _______________________________________________
> 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 Tina.Tsou.Zouting@huawei.com  Mon Jul  2 09:27:16 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 29F7A21F875B for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 09:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.704
X-Spam-Level: 
X-Spam-Status: No, score=-5.704 tagged_above=-999 required=5 tests=[AWL=0.895,  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 ojn3B-xO7unF for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 09:27:15 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 81A4321F8716 for <mboned@ietf.org>; Mon,  2 Jul 2012 09:27:15 -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 AHJ47725; Mon, 02 Jul 2012 12:27:20 -0400 (EDT)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 2 Jul 2012 09:25:14 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.208]) by dfweml405-hub.china.huawei.com ([10.193.5.102]) with mapi id 14.01.0323.003; Mon, 2 Jul 2012 09:25:13 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: Ac1WYemRmeS2biyti0iWC24nf7E7XAB+sRIQABJLuQA=
Date: Mon, 2 Jul 2012 16:25:13 +0000
Message-ID: <1E46ADFC-0D12-4C21-A9F3-922A70C739D5@huawei.com>
References: <mailman.4264.1341020564.3336.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D76F687E26@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76F687E26@EMBX01-WF.jnpr.net>
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-ID: <AE6FEDAFE3CBE04C8E6144F0FE86E453@huawei.com>
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: Mon, 02 Jul 2012 16:27:16 -0000

Dear Ron,
They are simply comments on a new draft, nothing more than this. Sorry for =
making u thinking about Multrans related to these comments.

The call for=20
http://datatracker.ietf.org/doc/draft-tsou-mboned-multrans-addr-acquisition=
/
has ended in May 29th.

It is July 2nd.=20
Can the chairs say what the result of this call is?

Tina

On Jul 2, 2012, at 7:28 AM, "Ronald Bonica" <rbonica@juniper.net> wrote:

> Tina,
>=20
> We should be remember two things wrt address formats:
>=20
> - the MLTRANS problem will be with us only for a short time (until walled=
-garden IPTV providers upgrade to IPv6)
> - changes that we make to the IPv6 addressing scheme will be with us fore=
ver
>=20
> So, in the interest of keeping the IPv6 addressing scheme simple, we shou=
ld try our best to limit the number of uses cases that we support and make =
the smallest possible change to the IPv6 addressing scheme. It doesn't make=
 sense to complicate the IPv6 addressing scheme in order to support a use-c=
ase that will rarely or never be deployed.
>=20
>                                       Ron
>                                       /speaking as AD
>=20
>=20
>> Date: Sat, 30 Jun 2012 01:41:22 +0000
>> From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
>> To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Stig Venaas
>>    <stig@venaas.com>
>> Cc: "mboned@ietf.org" <mboned@ietf.org>
>> Subject: Re: [MBONED] An alternative to
>>    draft-ietf-mboned-64-multicast-address-format?
>>=20
>> The fixed 96 bits and then 32 bits of the IPv4 address is a simpler and
>> better approach according to me, as described in
>> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-
>> format-02. However, this http://tools.ietf.org/html/draft-kumar-mboned-
>> 64mcast-embedded-address-00 document has its advantages of 6-4-6-4
>> scenario which is missing in the alternative document. The only point I
>> would like to stress upon is if it covers the scenario of 6-4-6, as
>> IPv6 multicast address expressed in terms of IPv4 is something 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?
>>=20
>> Tina
>>=20
>>=20
> **********
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From stig@venaas.com  Mon Jul  2 09:59:14 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 412D821F861B for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 09:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 4W2HYZw-gmyd for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 09:59:13 -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 402D421F85AF for <mboned@ietf.org>; Mon,  2 Jul 2012 09:59:13 -0700 (PDT)
Received: from [IPv6:2001:420:301:1004:9899:7794:59d7:7669] (unknown [IPv6:2001:420:301:1004:9899:7794:59d7:7669]) by ufisa.uninett.no (Postfix) with ESMTPSA id 9983F7FD4; Mon,  2 Jul 2012 18:59:15 +0200 (CEST)
Message-ID: <4FF1D35D.8010802@venaas.com>
Date: Mon, 02 Jul 2012 09:59:09 -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: "Nagendra Kumar (naikumar)" <naikumar@cisco.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> <C0E0A32284495243BDE0AC8A066631A80D447A49@dfweml513-mbx.china.huawei.com> <47E76F08F1BCF5458111C1939C7B9C460450C5@xmb-rcd-x03.cisco.com>
In-Reply-To: <47E76F08F1BCF5458111C1939C7B9C460450C5@xmb-rcd-x03.cisco.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: Mon, 02 Jul 2012 16:59:14 -0000

Hi, a few comments here on the responses below.

On 7/1/2012 1:58 AM, Nagendra Kumar (naikumar) wrote:
> Hi Tina,
>
> Thanks for your thoughts. For 6-4-6 scenarios, I think it may not require to signal if or not v4 address is embedded as IPv4 cloud will be transit here. I guess Tunneling, AMT or MVPN kind of solution might be apt here.
>
> Regarding the attribute in IPv4 only network, even if there is a requirement to transparently transfer attribute via v4 cloud, per my understanding, it still can be done by setting the F bit. So just the ingress and egress devices are required to understand the content of attribute.

Just one thought here. I'm not aware of scenarios where we need to mark
an IPv4 address now (to somehow get some particular behavior for
transition), but I want to point out that the technique of using PIM
join attributes (or IGMP aux data) as specified in this draft, could
in theory be used for some kind of marking of IPv4 groups too. While
we of course never could reserve a bit in the IPv4 address. I can't
think of any uses right now though.

More below.

> Regards,
> Nagendra
>
> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of Tina TSOU
> Sent: Saturday, June 30, 2012 7:11 AM
> To: Manfredi, Albert E; Stig Venaas
> Cc: mboned@ietf.org
> Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
>
> The fixed 96 bits and then 32 bits of the IPv4 address is a simpler and better approach according to me, as described in http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-02. However, this http://tools.ietf.org/html/draft-kumar-mboned-64mcast-embedded-address-00 document has its advantages of 6-4-6-4 scenario which is missing in the alternative document. The only point I would like to stress upon is if it covers the scenario of 6-4-6, as IPv6 multicast address expressed in terms of IPv4 is something 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?

I think we're all talking about that last 32 bits being the IPv4 address
at least. Right? The only question is how a router (and maybe other
entities) can know that a particular IPv6 group address has an IPv4
address in the last 32 bits.

It can be done by a reserved well-known prefix, or a reserved flag.
Or it can be a non-defined prefix where devices need to be configured
or dynamically learn which prefixes are used. Or it can be some marking
in a PIM join or other places where the group address is used, without
putting it in the group address itself. As in this latest draft.

Stig

> 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?
>>
>>> -----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.
>>
>> 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?
>>
>> Bert
>>
>> _______________________________________________
>> 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 Tina.Tsou.Zouting@huawei.com  Mon Jul  2 11:35:41 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 0756811E8105 for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 11:35:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.732
X-Spam-Level: 
X-Spam-Status: No, score=-5.732 tagged_above=-999 required=5 tests=[AWL=0.867,  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 jz8Gq3MFoDCx for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 11:35:40 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2F03211E8106 for <mboned@ietf.org>; Mon,  2 Jul 2012 11:35:40 -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 AHQ78386; Mon, 02 Jul 2012 14:35:45 -0400 (EDT)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 2 Jul 2012 11:33:35 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.208]) by dfweml403-hub.china.huawei.com ([10.193.5.151]) with mapi id 14.01.0323.003; Mon, 2 Jul 2012 11:33:34 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: "Nagendra Kumar (naikumar)" <naikumar@cisco.com>, "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: AQHNVi5bmeS2biyti0iWC24nf7E7XJcSFkcQgAKB8YCAAb2TcA==
Date: Mon, 2 Jul 2012 18:33:33 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A80D463619@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> <C0E0A32284495243BDE0AC8A066631A80D447A49@dfweml513-mbx.china.huawei.com> <47E76F08F1BCF5458111C1939C7B9C460450C5@xmb-rcd-x03.cisco.com>
In-Reply-To: <47E76F08F1BCF5458111C1939C7B9C460450C5@xmb-rcd-x03.cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.212.244.162]
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: Mon, 02 Jul 2012 18:35:41 -0000

Hi Nagendra,
Thank you. I agree with you that the most apt solution for IPv4 transit wou=
ld be tunneling, AMT or MVPN. As that scenario is not to be considered, do =
you think complicating the addressing scheme with additional attributes is =
worth the effort put in implementing it? Though the solution is thoughtful =
and a good one, I am seeing from the implementation point of view.

Tina

> -----Original Message-----
> From: Nagendra Kumar (naikumar) [mailto:naikumar@cisco.com]
> Sent: Sunday, July 01, 2012 1:58 AM
> To: Tina TSOU; Manfredi, Albert E; Stig Venaas
> Cc: mboned@ietf.org
> Subject: RE: [MBONED] An alternative to draft-ietf-mboned-64-multicast-
> address-format?
>=20
> Hi Tina,
>=20
> Thanks for your thoughts. For 6-4-6 scenarios, I think it may not require
> to signal if or not v4 address is embedded as IPv4 cloud will be transit
> here. I guess Tunneling, AMT or MVPN kind of solution might be apt here.
>=20
> Regarding the attribute in IPv4 only network, even if there is a
> requirement to transparently transfer attribute via v4 cloud, per my
> understanding, it still can be done by setting the F bit. So just the
> ingress and egress devices are required to understand the content of
> attribute.
>=20
> Regards,
> Nagendra
>=20
> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf
> Of Tina TSOU
> Sent: Saturday, June 30, 2012 7:11 AM
> To: Manfredi, Albert E; Stig Venaas
> Cc: mboned@ietf.org
> Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-
> address-format?
>=20
> The fixed 96 bits and then 32 bits of the IPv4 address is a simpler and
> better approach according to me, as described in
> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-
> 02. However, this http://tools.ietf.org/html/draft-kumar-mboned-64mcast-
> embedded-address-00 document has its advantages of 6-4-6-4 scenario which
> is missing in the alternative document. The only point I would like to
> stress upon is if it covers the scenario of 6-4-6, as IPv6 multicast
> address expressed in terms of IPv4 is something 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?
>=20
> Tina
>=20
>=20
> > -----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?
> >
> > > -----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=
.
> >
> > 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?
> >
> > Bert
> >
> > _______________________________________________
> > 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 Tina.Tsou.Zouting@huawei.com  Mon Jul  2 11:48:33 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 54B7F11E80C8 for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 11:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.758
X-Spam-Level: 
X-Spam-Status: No, score=-5.758 tagged_above=-999 required=5 tests=[AWL=0.841,  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 wvZUoRxoBWtL for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 11:48:32 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5E17511E8083 for <mboned@ietf.org>; Mon,  2 Jul 2012 11:48:32 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHQ79098; Mon, 02 Jul 2012 14:48:37 -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, 2 Jul 2012 11:47:30 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.208]) by dfweml404-hub.china.huawei.com ([10.193.5.203]) with mapi id 14.01.0323.003; Mon, 2 Jul 2012 11:47:30 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: Ac1WYemRmeS2biyti0iWC24nf7E7XAB+sRIQAAmb9+A=
Date: Mon, 2 Jul 2012 18:47:29 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A80D463831@dfweml513-mbx.china.huawei.com>
References: <mailman.4264.1341020564.3336.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D76F687E26@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76F687E26@EMBX01-WF.jnpr.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.212.244.162]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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: Mon, 02 Jul 2012 18:48:33 -0000

Dear Ron,
I agree with you that if the addressing scheme is kept simple, it is defini=
tely better. However, since the Internet at present is more IPv4 rather tha=
n IPv6, should we consider keeping more IPv4 only transit networks in mind?=
 On the other hand, if IPv6 addressing scheme supports more IPv4 only netwo=
rks, according to me, people will be more reluctant to deploy IPv6 in their=
 IPv4 only network. So, for deployment and adoption of IPv6, the use cases =
should be limited, right? I look forward hearing from you.

Tina


> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf
> Of Ronald Bonica
> Sent: Monday, July 02, 2012 7:27 AM
> To: mboned@ietf.org
> Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-
> address-format?
>=20
> Tina,
>=20
> We should be remember two things wrt address formats:
>=20
> - the MLTRANS problem will be with us only for a short time (until walled=
-
> garden IPTV providers upgrade to IPv6)
> - changes that we make to the IPv6 addressing scheme will be with us
> forever
>=20
> So, in the interest of keeping the IPv6 addressing scheme simple, we
> should try our best to limit the number of uses cases that we support and
> make the smallest possible change to the IPv6 addressing scheme. It
> doesn't make sense to complicate the IPv6 addressing scheme in order to
> support a use-case that will rarely or never be deployed.
>=20
>                                        Ron
>                                        /speaking as AD
>=20
>=20
> > Date: Sat, 30 Jun 2012 01:41:22 +0000
> > From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
> > To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Stig Venaas
> > 	<stig@venaas.com>
> > Cc: "mboned@ietf.org" <mboned@ietf.org>
> > Subject: Re: [MBONED] An alternative to
> > 	draft-ietf-mboned-64-multicast-address-format?
> >
> > The fixed 96 bits and then 32 bits of the IPv4 address is a simpler and
> > better approach according to me, as described in
> > http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-
> > format-02. However, this http://tools.ietf.org/html/draft-kumar-mboned-
> > 64mcast-embedded-address-00 document has its advantages of 6-4-6-4
> > scenario which is missing in the alternative document. The only point I
> > would like to stress upon is if it covers the scenario of 6-4-6, as
> > IPv6 multicast address expressed in terms of IPv4 is something 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
> >
> >
> **********
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From rbonica@juniper.net  Mon Jul  2 12:28:02 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 D095A21F8525 for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 12:28:02 -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.025, 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 nl0CbYf0QfLz for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 12:28:02 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id E4F4421F8517 for <mboned@ietf.org>; Mon,  2 Jul 2012 12:28:01 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKT/H2Rhd97ckT64VG/Q/VMfQ01QaP74Fy@postini.com; Mon, 02 Jul 2012 12:28:07 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, 2 Jul 2012 12:28:02 -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, 2 Jul 2012 12:28:02 -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, 2 Jul 2012 15:28:00 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "mboned@ietf.org" <mboned@ietf.org>
Date: Mon, 2 Jul 2012 15:27:58 -0400
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: Ac1WYemRmeS2biyti0iWC24nf7E7XAB+sRIQAAmb9+AAAL6wQA==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76F6883EE@EMBX01-WF.jnpr.net>
References: <mailman.4264.1341020564.3336.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D76F687E26@EMBX01-WF.jnpr.net> <C0E0A32284495243BDE0AC8A066631A80D463831@dfweml513-mbx.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80D463831@dfweml513-mbx.china.huawei.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
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: Mon, 02 Jul 2012 19:28:02 -0000

Tina (et al),

First, please accept my apologies for the rather confused email that I sent=
 this morning. For the last few days, we have been without electricity in N=
orthern Virginia, recovering from a severe storm. I have only caught up wit=
h this email thread in the last hour.

That said, I would like to restate a few architectural principles. The MLTR=
ANS problem will only be with us for a short time (until walled-garden IPTV=
 operators have converted to IPv6). Therefore, we want to minimize our inve=
stment in MLTRANS.

In my mind, the best way to do this is to solve only for use-cases that wil=
l see significant deployment. One or two deployments isn't enough to justif=
y a solution. Beyond that, we want to limit the scope of our solutions. If =
we can avoid changing the IPv6 addressing scheme, that would be a win. Also=
, restricting our solution to a few optional TLVs in routing and signaling =
protocols would also be a win.

                                                  Ron



> -----Original Message-----
> From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
> Sent: Monday, July 02, 2012 2:47 PM
> To: Ronald Bonica; mboned@ietf.org
> Subject: RE: [MBONED] An alternative to draft-ietf-mboned-64-multicast-
> address-format?
>=20
> Dear Ron,
> I agree with you that if the addressing scheme is kept simple, it is
> definitely better. However, since the Internet at present is more IPv4
> rather than IPv6, should we consider keeping more IPv4 only transit
> networks in mind? On the other hand, if IPv6 addressing scheme supports
> more IPv4 only networks, according to me, people will be more reluctant
> to deploy IPv6 in their IPv4 only network. So, for deployment and
> adoption of IPv6, the use cases should be limited, right? I look
> forward hearing from you.
>=20
> Tina
>=20
>=20
> > -----Original Message-----
> > From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On
> > Behalf Of Ronald Bonica
> > Sent: Monday, July 02, 2012 7:27 AM
> > To: mboned@ietf.org
> > Subject: Re: [MBONED] An alternative to
> > draft-ietf-mboned-64-multicast- address-format?
> >
> > Tina,
> >
> > We should be remember two things wrt address formats:
> >
> > - the MLTRANS problem will be with us only for a short time (until
> > walled- garden IPTV providers upgrade to IPv6)
> > - changes that we make to the IPv6 addressing scheme will be with us
> > forever
> >
> > So, in the interest of keeping the IPv6 addressing scheme simple, we
> > should try our best to limit the number of uses cases that we support
> > and make the smallest possible change to the IPv6 addressing scheme.
> > It doesn't make sense to complicate the IPv6 addressing scheme in
> > order to support a use-case that will rarely or never be deployed.
> >
> >                                        Ron
> >                                        /speaking as AD
> >
> >
> > > Date: Sat, 30 Jun 2012 01:41:22 +0000
> > > From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
> > > To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Stig
> Venaas
> > > 	<stig@venaas.com>
> > > Cc: "mboned@ietf.org" <mboned@ietf.org>
> > > Subject: Re: [MBONED] An alternative to
> > > 	draft-ietf-mboned-64-multicast-address-format?
> > >
> > > The fixed 96 bits and then 32 bits of the IPv4 address is a simpler
> > > and better approach according to me, as described in
> > > http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-
> > > format-02. However, this
> > > http://tools.ietf.org/html/draft-kumar-mboned-
> > > 64mcast-embedded-address-00 document has its advantages of 6-4-6-4
> > > scenario which is missing in the alternative document. The only
> > > point I would like to stress upon is if it covers the scenario of
> > > 6-4-6, as
> > > IPv6 multicast address expressed in terms of IPv4 is something 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
> > >
> > >
> > **********
> > _______________________________________________
> > MBONED mailing list
> > MBONED@ietf.org
> > https://www.ietf.org/mailman/listinfo/mboned

From sarikaya2012@gmail.com  Mon Jul  2 13:17:10 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 A7AE021F8601 for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 13:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.471
X-Spam-Level: 
X-Spam-Status: No, score=-3.471 tagged_above=-999 required=5 tests=[AWL=0.128,  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 B3WRPgdLveRC for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 13:17:10 -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 2807A21F8600 for <mboned@ietf.org>; Mon,  2 Jul 2012 13:17:10 -0700 (PDT)
Received: by yenq13 with SMTP id q13so5030661yen.31 for <mboned@ietf.org>; Mon, 02 Jul 2012 13:17:15 -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; bh=X1nwwvlW7IM5Cx35SgxsDqR4raUp4VRgygkkfHmIbXE=; b=k805/VvdsZuCOn29kEDSlKUeT2IfPkKq5Ox5yIAkuoxSN/xSNF14CccumeRZaZUevD Eo7MYwO8v65Gi/n8aOsasha7ASqXySRAkNQp2T47eoQqFwrRLlZZfW4ND9lGy/mMWhG6 r5dcwX3FeryxTQXBwT2nbq/tAPT5+adkGx5hwl4StJJteQoP4Ajg2GA9325xYisTy8Rv S/diWf0k6aMz6VtaaRrmI5fkTQ7VkNLnV6vnWQn1tBrXVdC4zv4e/tCXKScwvhW0R1EV 7xSFNQ2BDcwgUXW0SEW0BO+FZZVY4M+iALLf1ezMGswkm9w0t3Y+5grk6n2adJX5ED5v /a8g==
MIME-Version: 1.0
Received: by 10.50.160.198 with SMTP id xm6mr6496007igb.0.1341260235725; Mon, 02 Jul 2012 13:17:15 -0700 (PDT)
Received: by 10.231.118.210 with HTTP; Mon, 2 Jul 2012 13:17:15 -0700 (PDT)
In-Reply-To: <4FEF2DB9.2030809@gmail.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> <4FEF2DB9.2030809@gmail.com>
Date: Mon, 2 Jul 2012 15:17:15 -0500
Message-ID: <CAC8QAccGDUJx7DbFS8Bwgr4+4jF6FVE2=t7zAQfGkzy=3-vaZg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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
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: Mon, 02 Jul 2012 20:17:10 -0000

On Sat, Jun 30, 2012 at 11:47 AM, Tom Taylor <tom.taylor.stds@gmail.com> wrote:

>
> It would be good to preserve the advantages of embedded RP. You certainly
> can't have a well-known /96 and use embedded RP.


Why not?

If the translator is able to use an IPv6 Embedded-
RP prefix to represent IPv4 ASM groups on the IPv6 network, no
modifications are required
to the configuration of other PIM routers.

(From Teemu's thesis).

Behcet

From tom.taylor.stds@gmail.com  Mon Jul  2 13:35:31 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 79BFA11E80E7 for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 13:35:31 -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 V0AlnpLJyUHN for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 13:35:31 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id AFE8521F8617 for <mboned@ietf.org>; Mon,  2 Jul 2012 13:35:30 -0700 (PDT)
Received: by werp11 with SMTP id p11so989165wer.31 for <mboned@ietf.org>; Mon, 02 Jul 2012 13:35:36 -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=d0BxnmnnHEhQ1fIWP7VdS6oGY0UT12pFNfUP9vDYMJw=; b=L/XaP1DwSOWmAsShpUa8dQzEUsUkmGYcETAalV6l2goKGXlSdQ9a53Qck7jcJbNtCU VTLBP+Vy/3PLqjtObwwIS7w5D+VeT1eraJAc20YX/fILQhhKCDlW19BYnBHUgR/YwAfP I++56uhm5ISQ/Q7S5uVZS27b/xwm9RJ6GFr1sh0Kd+LByQUa2ToJlaQEh899f+d7CuFY 7JIQ4xudx4xccUrz/SsE6omL7hu4QQuQBn+m1viK60Jb0BqDpBpsgEC3j2CMwUA4hbVb M/slEjkcZ0hzD4gQku/4p/GLMtN5Biuy+uTn/rVnku7iJ9mHNJOAR6XNHgcFPnYiXTBa 1XUg==
Received: by 10.216.218.200 with SMTP id k50mr2616587wep.212.1341261335892; Mon, 02 Jul 2012 13:35:35 -0700 (PDT)
Received: from [127.0.0.1] ([207.112.119.108]) by mx.google.com with ESMTPS id m4sm26802463wie.1.2012.07.02.13.35.34 (version=SSLv3 cipher=OTHER); Mon, 02 Jul 2012 13:35:35 -0700 (PDT)
Message-ID: <4FF20613.5050107@gmail.com>
Date: Mon, 02 Jul 2012 16:35:31 -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: sarikaya@ieee.org
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> <4FEF2DB9.2030809@gmail.com> <CAC8QAccGDUJx7DbFS8Bwgr4+4jF6FVE2=t7zAQfGkzy=3-vaZg@mail.gmail.com>
In-Reply-To: <CAC8QAccGDUJx7DbFS8Bwgr4+4jF6FVE2=t7zAQfGkzy=3-vaZg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120702-1, 02/07/2012), Outbound message
X-Antivirus-Status: Clean
Cc: "mboned@ietf.org" <mboned@ietf.org>, Behcet Sarikaya <sarikaya2012@gmail.com>
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: Mon, 02 Jul 2012 20:35:31 -0000

Your statement is correct, but has nothing to do with a well-known /96. 
That's why I was ruminating on the possible use of a reserved bit to 
indicate the presence of an embedded IPv4 address.

On 02/07/2012 4:17 PM, Behcet Sarikaya wrote:
> On Sat, Jun 30, 2012 at 11:47 AM, Tom Taylor <tom.taylor.stds@gmail.com> wrote:
>
>>
>> It would be good to preserve the advantages of embedded RP. You certainly
>> can't have a well-known /96 and use embedded RP.
>
>
> Why not?
>
> If the translator is able to use an IPv6 Embedded-
> RP prefix to represent IPv4 ASM groups on the IPv6 network, no
> modifications are required
> to the configuration of other PIM routers.
>
> (From Teemu's thesis).
>
> Behcet
>


From brian@innovationslab.net  Mon Jul  2 15:01:20 2012
Return-Path: <brian@innovationslab.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 8A90B21F854F for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 15:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 0qX-ExiYZE22 for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 15:01:20 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 06A2C21F854E for <mboned@ietf.org>; Mon,  2 Jul 2012 15:01:20 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 31A53880CF for <mboned@ietf.org>; Mon,  2 Jul 2012 15:01:26 -0700 (PDT)
Received: from clemson.local (c-68-33-164-105.hsd1.dc.comcast.net [68.33.164.105]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id E1AFB130017 for <mboned@ietf.org>; Mon,  2 Jul 2012 15:01:25 -0700 (PDT)
Message-ID: <4FF21A32.7030304@innovationslab.net>
Date: Mon, 02 Jul 2012 18:01:22 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: mboned@ietf.org
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> <4FEF2DB9.2030809@gmail.com> <CAC8QAccGDUJx7DbFS8Bwgr4+4jF6FVE2=t7zAQfGkzy=3-vaZg@mail.gmail.com>
In-Reply-To: <CAC8QAccGDUJx7DbFS8Bwgr4+4jF6FVE2=t7zAQfGkzy=3-vaZg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Mon, 02 Jul 2012 22:01:20 -0000

On 7/2/12 4:17 PM, Behcet Sarikaya wrote:
> On Sat, Jun 30, 2012 at 11:47 AM, Tom Taylor <tom.taylor.stds@gmail.com> wrote:
>
>>
>> It would be good to preserve the advantages of embedded RP. You certainly
>> can't have a well-known /96 and use embedded RP.
>
>
> Why not?
>
> If the translator is able to use an IPv6 Embedded-
> RP prefix to represent IPv4 ASM groups on the IPv6 network, no
> modifications are required
> to the configuration of other PIM routers.

This would not be a well-known 96-bit prefix.  The information 
describing the RP address (within that /96) would change based on which 
network is maintaining the RP.

Regards,
Brian

From stig@venaas.com  Mon Jul  2 18:47:20 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 5866421F85C0 for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 18:47:20 -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 YNV7wWAiffDg for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 18:47:19 -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 A6DC621F85B5 for <mboned@ietf.org>; Mon,  2 Jul 2012 18:47:19 -0700 (PDT)
Received: from [10.21.79.223] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 0E5EF7FE2; Tue,  3 Jul 2012 03:47:20 +0200 (CEST)
Message-ID: <4FF24F3F.3020505@venaas.com>
Date: Mon, 02 Jul 2012 18:47:43 -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: Brian Haberman <brian@innovationslab.net>
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> <4FEF2DB9.2030809@gmail.com> <CAC8QAccGDUJx7DbFS8Bwgr4+4jF6FVE2=t7zAQfGkzy=3-vaZg@mail.gmail.com> <4FF21A32.7030304@innovationslab.net>
In-Reply-To: <4FF21A32.7030304@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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: Tue, 03 Jul 2012 01:47:20 -0000

On 02.07.2012 15:01, Brian Haberman wrote:
> On 7/2/12 4:17 PM, Behcet Sarikaya wrote:
>> On Sat, Jun 30, 2012 at 11:47 AM, Tom Taylor
>> <tom.taylor.stds@gmail.com> wrote:
>>
>>>
>>> It would be good to preserve the advantages of embedded RP. You
>>> certainly
>>> can't have a well-known /96 and use embedded RP.
>>
>>
>> Why not?
>>
>> If the translator is able to use an IPv6 Embedded-
>> RP prefix to represent IPv4 ASM groups on the IPv6 network, no
>> modifications are required
>> to the configuration of other PIM routers.
>
> This would not be a well-known 96-bit prefix. The information describing
> the RP address (within that /96) would change based on which network is
> maintaining the RP.

It could work if everyone used the same RP address ;) Sort of an
anycast RP address. It would probably not be a good idea though.

Of course we could argue whether we need to support embedded-RP.
It is very useful, especially inter-domain, but if that is not a
requirement, we may not need to support it.

Stig

>
> Regards,
> Brian
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From naikumar@cisco.com  Mon Jul  2 22:34:31 2012
Return-Path: <naikumar@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 580E421F8713 for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 22:34:31 -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 HnQl+J-OjCDu for <mboned@ietfa.amsl.com>; Mon,  2 Jul 2012 22:34:30 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 35BD121F855A for <mboned@ietf.org>; Mon,  2 Jul 2012 22:34:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=naikumar@cisco.com; l=5510; q=dns/txt; s=iport; t=1341293677; x=1342503277; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=YlGKEwrkqYDA4tvnlK6xZp0lHeqR9X80Zdlw6zLkQ/Y=; b=fdxL4B4wEJid4+Ywlll6Bojg5+P6eI9rjB8UZwcwZj/PoJ4xICSDaaLG WVGQmLBNYHbntW9rwSMnUjfXrOgIZ0FTIxPRV6AHChum4CsvoRs0187Uo rvh9CH+kmkG2XcnuH2f4m8iKkLWfGeJX5cCIzcm2iv88D0YhKi4kamirE 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAPSD8k+tJV2Z/2dsb2JhbABFtmiBB4IYAQEBAwEBAQEPASc0CwwEAgEIEQQBAQsUCQcnCxQJCAIEAQkEBQgTB4dkBQuaZKBEizmFOmADlkaNC4Fmgl8
X-IronPort-AV: E=Sophos;i="4.77,514,1336348800"; d="scan'208";a="98188809"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP; 03 Jul 2012 05:34:37 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q635YaDj006347 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Jul 2012 05:34:36 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.154]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0298.004; Tue, 3 Jul 2012 00:34:36 -0500
From: "Nagendra Kumar (naikumar)" <naikumar@cisco.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "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: AQHNVi5VQ5Smo6vw00OI2MHPt8AL2pcSalwAgAGfJ9CAAqBQgIAAYOXA
Date: Tue, 3 Jul 2012 05:34:35 +0000
Message-ID: <47E76F08F1BCF5458111C1939C7B9C46048D35@xmb-rcd-x03.cisco.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> <C0E0A32284495243BDE0AC8A066631A80D447A49@dfweml513-mbx.china.huawei.com> <47E76F08F1BCF5458111C1939C7B9C460450C5@xmb-rcd-x03.cisco.com> <C0E0A32284495243BDE0AC8A066631A80D463619@dfweml513-mbx.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80D463619@dfweml513-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.103.228.140]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19014.003
x-tm-as-result: No--65.781900-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
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] 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: Tue, 03 Jul 2012 05:34:31 -0000

Hi Tina,

Thanks for the comments. With IPv6 source based scenarios, per my understan=
ding, current proposals (embedded bit or flag in PIM/MLD) may not be suffic=
ient (atleast in current state) to build the tree. But as Stig mentioned, w=
e could use some kind of marking (or that sort) in join attribute for IPv4 =
groups too.=20

I agree with your comment that both idea got its own pros and cons. So we w=
ould like to put it on table to discuss and understand others view on the s=
ame :)

Thanks again for your comments.

Thanks,
Nagendra

-----Original Message-----
From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of=
 Tina TSOU
Sent: Tuesday, July 03, 2012 12:04 AM
To: Nagendra Kumar (naikumar); Manfredi, Albert E; Stig Venaas
Cc: mboned@ietf.org
Subject: Re: [MBONED] An alternative to draft-ietf-mboned-64-multicast-addr=
ess-format?

Hi Nagendra,
Thank you. I agree with you that the most apt solution for IPv4 transit wou=
ld be tunneling, AMT or MVPN. As that scenario is not to be considered, do =
you think complicating the addressing scheme with additional attributes is =
worth the effort put in implementing it? Though the solution is thoughtful =
and a good one, I am seeing from the implementation point of view.

Tina

> -----Original Message-----
> From: Nagendra Kumar (naikumar) [mailto:naikumar@cisco.com]
> Sent: Sunday, July 01, 2012 1:58 AM
> To: Tina TSOU; Manfredi, Albert E; Stig Venaas
> Cc: mboned@ietf.org
> Subject: RE: [MBONED] An alternative to=20
> draft-ietf-mboned-64-multicast- address-format?
>=20
> Hi Tina,
>=20
> Thanks for your thoughts. For 6-4-6 scenarios, I think it may not=20
> require to signal if or not v4 address is embedded as IPv4 cloud will=20
> be transit here. I guess Tunneling, AMT or MVPN kind of solution might be=
 apt here.
>=20
> Regarding the attribute in IPv4 only network, even if there is a=20
> requirement to transparently transfer attribute via v4 cloud, per my=20
> understanding, it still can be done by setting the F bit. So just the=20
> ingress and egress devices are required to understand the content of=20
> attribute.
>=20
> Regards,
> Nagendra
>=20
> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On=20
> Behalf Of Tina TSOU
> Sent: Saturday, June 30, 2012 7:11 AM
> To: Manfredi, Albert E; Stig Venaas
> Cc: mboned@ietf.org
> Subject: Re: [MBONED] An alternative to=20
> draft-ietf-mboned-64-multicast- address-format?
>=20
> The fixed 96 bits and then 32 bits of the IPv4 address is a simpler=20
> and better approach according to me, as described in
> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-form
> at- 02. However, this=20
> http://tools.ietf.org/html/draft-kumar-mboned-64mcast-
> embedded-address-00 document has its advantages of 6-4-6-4 scenario=20
> which is missing in the alternative document. The only point I would=20
> like to stress upon is if it covers the scenario of 6-4-6, as IPv6=20
> multicast address expressed in terms of IPv4 is something I didn't=20
> find in the document. I am only concerned about the validity of the=20
> attributes in an
> IPv4 only multicast network. Would tunnels be used to route the IPv6=20
> packets with the end routers being dual stack?
>=20
> Tina
>=20
>=20
> > -----Original Message-----
> > From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On=20
> > 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?
> >
> > > -----Original Message-----
> >
> >
> > > For multicast things are kind of reversed. From say PIM=20
> > > perspective, you can start out with someone joining an IPv6 group=20
> > > where the last
> > > 32 bits form an IPv4 group address. When this IPv6 join reaches=20
> > > say a device on the edge of the IPv4 network, it can based on=20
> > > configuration (or hard-coded if a standardized prefix), or a flag=20
> > > in the group address, or a join attribute (these are the solutions=20
> > > I think we have on the table), know that it should extract those=20
> > > 32 bits, and join the IPv4 source. When it receives IPv4 data=20
> > > packets, it can based on its PIM state know what IPv6 address to=20
> > > 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=20
> > prefix is configurable (presumably there will be an OOB mechanism to=20
> > 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=20
> > IGMP or proxy MLD is used, to make multicasts traversing a network=20
> > available to an egress router? Or are we saying that it's okay to=20
> > have incompatible solutions depending on each use case?
> >
> > Bert
> >
> > _______________________________________________
> > 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
_______________________________________________
MBONED mailing list
MBONED@ietf.org
https://www.ietf.org/mailman/listinfo/mboned

From lenny@juniper.net  Thu Jul  5 08:44:27 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 717A721F8787 for <mboned@ietfa.amsl.com>; Thu,  5 Jul 2012 08:44: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.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 NRr3Hmrq7-i5 for <mboned@ietfa.amsl.com>; Thu,  5 Jul 2012 08:44:27 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id BD2D621F86D5 for <mboned@ietf.org>; Thu,  5 Jul 2012 08:44:26 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKT/W2aEfnNU5tDI1VRTIrES+addpkj8YK@postini.com; Thu, 05 Jul 2012 08:44:40 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, 5 Jul 2012 08:36:30 -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 q65FaDh20930	for <mboned@ietf.org>; Thu, 5 Jul 2012 08:36:28 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 1152E1141B;  Thu,  5 Jul 2012 08:36:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 05FFD1144F	for <mboned@ietf.org>; Thu,  5 Jul 2012 08:36:13 -0700 (PDT)
Date: Thu, 5 Jul 2012 08:36:12 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
Message-ID: <20120705082719.Q95800@eng-mail01.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Subject: [MBONED] draft-tsou-mboned-multrans-addr-acquisition
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, 05 Jul 2012 15:44:27 -0000

Regarding the question of adopting 
draft-tsou-mboned-multrans-addr-acquisition as a WG document, and with 
respect to the larger questions about Multrans work in Mboned, we have 
reached the following conclusion:

- The WG's goal is to standardize only technologies that will see 
significant deployment

- The WG is currently engaged in a discussion regarding the uses-cases 
enumerated in draft-ietf-mboned-v4v6-mcast-ps. WG participants agreed that 
both of the "dual-stack" use cases are likely to see deployment. However, 
the WG has yet to demonstrate sufficient motivation for any solution other 
than "unicast tunneling" in scenarios when the problem network or network 
segment is not both dual stack and multicast enabled. In order to 
demonstrate sufficient motivation, the proponents should explain why 
unicast tunneling until dual stack can be deployed is not a viable 
solution.

- Until the discussion mentioned above is resolved, 
draft-ietf-mboned-v4v6-mcast-ps cannot progress to WG last call

- Because all MULTRANS documents should normatively reference 
draft-ietf-mboned-v4v6-mcast-ps, they cannot progress to WG last call 
until draft-ietf-mboned-v4v6-mcast-ps progresses to WG last call

- However, the WG may accept other MULTRANS work, with the understanding 
that it may have to change pending the outcome of discussions mentioned 
above.

- Therefore, draft-tsou-mboned-multrans-addr-acquisition can be accepted 
as a WG document, given the above-mentioned caveats and the support 
expressed by the WG to adopt.  The authors may resubmit this doc as 
draft-mboned -...

MBONED Chairs

From tom.taylor.stds@gmail.com  Thu Jul  5 09:15:11 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 3DE6421F8732 for <mboned@ietfa.amsl.com>; Thu,  5 Jul 2012 09:15:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.514
X-Spam-Level: 
X-Spam-Status: No, score=-3.514 tagged_above=-999 required=5 tests=[AWL=0.085,  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 qIEYE8iLP+KU for <mboned@ietfa.amsl.com>; Thu,  5 Jul 2012 09:15:10 -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 40AA621F864B for <mboned@ietf.org>; Thu,  5 Jul 2012 09:15:10 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id y7so610150bkt.31 for <mboned@ietf.org>; Thu, 05 Jul 2012 09:15:24 -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=ny4S9unGE0e4xtwtObaL2AlpqHxR5BfVf1Gr4uJM42Y=; b=wSch3dKhx/a41mXjIUDQvXpDZOOt6uHW0MELCFOmM1bewo4Gg6lG1GCLGitm7gffZE svGvbm1pi8uqG64XcFCmBxT+qzxJVzX+wrLu8JpdX85OdUwkqG4QAYGcfQpb/wbvPVSD obqAw4BcO1FNVgrYmlySfp3E4tsjDO68Em0ymVoFPTDhsS3YyRYDjFv7jVuPAO82R5vD rHLW3tVavaIGW3LlFo7jfdQIy5T6I+As1cGhiTf6iDgVV2qOf/psoJiBcKEbvrdtOjwo z0O7GxIVReVhp6pNKhR3WvzTHpsIu4wYv6NgEzen2q4bkcW9s2ubv02b5McKNOZmweVF /XUg==
Received: by 10.205.125.7 with SMTP id gq7mr11766377bkc.98.1341504923887; Thu, 05 Jul 2012 09:15:23 -0700 (PDT)
Received: from [127.0.0.1] (dsl-173-206-67-81.tor.primus.ca. [173.206.67.81]) by mx.google.com with ESMTPS id b18sm6665242bkx.11.2012.07.05.09.15.22 (version=SSLv3 cipher=OTHER); Thu, 05 Jul 2012 09:15:23 -0700 (PDT)
Message-ID: <4FF5BD99.6080105@gmail.com>
Date: Thu, 05 Jul 2012 12:15:21 -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: Leonard Giuliano <lenny@juniper.net>
References: <20120705082719.Q95800@eng-mail01.juniper.net>
In-Reply-To: <20120705082719.Q95800@eng-mail01.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120705-0, 05/07/2012), Outbound message
X-Antivirus-Status: Clean
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition
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, 05 Jul 2012 16:15:11 -0000

You are taking a rather old-fashioned view of IPv6 transition. The IETF 
held for at least 15 years that dual stack was the way to achieve it, 
but dual stack didn't happen. Behave and Softwires have developed 
alternatives, which operators are deploying. You are ignoring reality 
with your present position.

On 05/07/2012 11:36 AM, Leonard Giuliano wrote:
>
> Regarding the question of adopting
> draft-tsou-mboned-multrans-addr-acquisition as a WG document, and with
> respect to the larger questions about Multrans work in Mboned, we have
> reached the following conclusion:
>
> - The WG's goal is to standardize only technologies that will see
> significant deployment
>
> - The WG is currently engaged in a discussion regarding the uses-cases
> enumerated in draft-ietf-mboned-v4v6-mcast-ps. WG participants agreed
> that both of the "dual-stack" use cases are likely to see deployment.
> However, the WG has yet to demonstrate sufficient motivation for any
> solution other than "unicast tunneling" in scenarios when the problem
> network or network segment is not both dual stack and multicast enabled.
> In order to demonstrate sufficient motivation, the proponents should
> explain why unicast tunneling until dual stack can be deployed is not a
> viable solution.
>
> - Until the discussion mentioned above is resolved,
> draft-ietf-mboned-v4v6-mcast-ps cannot progress to WG last call
>
> - Because all MULTRANS documents should normatively reference
> draft-ietf-mboned-v4v6-mcast-ps, they cannot progress to WG last call
> until draft-ietf-mboned-v4v6-mcast-ps progresses to WG last call
>
> - However, the WG may accept other MULTRANS work, with the understanding
> that it may have to change pending the outcome of discussions mentioned
> above.
>
> - Therefore, draft-tsou-mboned-multrans-addr-acquisition can be accepted
> as a WG document, given the above-mentioned caveats and the support
> expressed by the WG to adopt.  The authors may resubmit this doc as
> draft-mboned -...
>
> MBONED Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>


From lenny@juniper.net  Mon Jul  9 13:24:28 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 2F45F11E80FE for <mboned@ietfa.amsl.com>; Mon,  9 Jul 2012 13:24:28 -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 IYW4DvhKRX8z for <mboned@ietfa.amsl.com>; Mon,  9 Jul 2012 13:24:27 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE7711E80FC for <mboned@ietf.org>; Mon,  9 Jul 2012 13:24:27 -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 DSNKT/s+E9XgnioVMkfoezjSKM5JvdiKrsTn@postini.com; Mon, 09 Jul 2012 13:24:53 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, 9 Jul 2012 13:24:05 -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 q69KO4h70107; Mon, 9 Jul 2012 13:24:05 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id CA2321144F;  Mon,  9 Jul 2012 13:24:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id BEDEF11446; Mon,  9 Jul 2012 13:24:04 -0700 (PDT)
Date: Mon, 9 Jul 2012 13:24:04 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Tom Taylor <tom.taylor.stds@gmail.com>
In-Reply-To: <4FF5BD99.6080105@gmail.com>
Message-ID: <20120709131631.W63595@eng-mail01.juniper.net>
References: <20120705082719.Q95800@eng-mail01.juniper.net> <4FF5BD99.6080105@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition
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, 09 Jul 2012 20:24:28 -0000

If it is demonstrated that other use cases are likely to be deployed for 
mcast, then the WG will consider those.  

We simply want to focus our efforts on those use cases that are likely to 
deployed for mcast, not every theoretical permutation of cases.

On Thu, 5 Jul 2012, Tom Taylor wrote:

-) You are taking a rather old-fashioned view of IPv6 transition. The IETF held
-) for at least 15 years that dual stack was the way to achieve it, but dual
-) stack didn't happen. Behave and Softwires have developed alternatives, which
-) operators are deploying. You are ignoring reality with your present position.
-) 
-) On 05/07/2012 11:36 AM, Leonard Giuliano wrote:
-) > 
-) > Regarding the question of adopting
-) > draft-tsou-mboned-multrans-addr-acquisition as a WG document, and with
-) > respect to the larger questions about Multrans work in Mboned, we have
-) > reached the following conclusion:
-) > 
-) > - The WG's goal is to standardize only technologies that will see
-) > significant deployment
-) > 
-) > - The WG is currently engaged in a discussion regarding the uses-cases
-) > enumerated in draft-ietf-mboned-v4v6-mcast-ps. WG participants agreed
-) > that both of the "dual-stack" use cases are likely to see deployment.
-) > However, the WG has yet to demonstrate sufficient motivation for any
-) > solution other than "unicast tunneling" in scenarios when the problem
-) > network or network segment is not both dual stack and multicast enabled.
-) > In order to demonstrate sufficient motivation, the proponents should
-) > explain why unicast tunneling until dual stack can be deployed is not a
-) > viable solution.
-) > 
-) > - Until the discussion mentioned above is resolved,
-) > draft-ietf-mboned-v4v6-mcast-ps cannot progress to WG last call
-) > 
-) > - Because all MULTRANS documents should normatively reference
-) > draft-ietf-mboned-v4v6-mcast-ps, they cannot progress to WG last call
-) > until draft-ietf-mboned-v4v6-mcast-ps progresses to WG last call
-) > 
-) > - However, the WG may accept other MULTRANS work, with the understanding
-) > that it may have to change pending the outcome of discussions mentioned
-) > above.
-) > 
-) > - Therefore, draft-tsou-mboned-multrans-addr-acquisition can be accepted
-) > as a WG document, given the above-mentioned caveats and the support
-) > expressed by the WG to adopt.  The authors may resubmit this doc as
-) > draft-mboned -...
-) > 
-) > MBONED Chairs
-) > _______________________________________________
-) > MBONED mailing list
-) > MBONED@ietf.org
-) > https://www.ietf.org/mailman/listinfo/mboned
-) > 
-) 

From internet-drafts@ietf.org  Tue Jul 10 08:47:48 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 C1A3A11E8121; Tue, 10 Jul 2012 08:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.317
X-Spam-Level: 
X-Spam-Status: No, score=-102.317 tagged_above=-999 required=5 tests=[AWL=0.282, 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 VSgOVIAstc9S; Tue, 10 Jul 2012 08:47:48 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44FD811E8091; Tue, 10 Jul 2012 08:47:48 -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.30p3
Message-ID: <20120710154748.13110.97620.idtracker@ietfa.amsl.com>
Date: Tue, 10 Jul 2012 08:47:48 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-multrans-addr-acquisition-00.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, 10 Jul 2012 15:47:48 -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           : Address Acquisition For Multicast Content When Source an=
d Receiver Support Differing IP Versions
	Author(s)       : Tina Tsou
                          Axel Clauberg
                          Mohamed Boucadair
                          Stig Venaas
                          Qiong Sun
	Filename        : draft-ietf-mboned-multrans-addr-acquisition-00.txt
	Pages           : 10
	Date            : 2012-07-09

Abstract:
   Each IPTV operator has their own arrangements for pre-provisioning
   program information including addresses of the multicast groups
   corresponding to broadcast programs on the subscriber receiver.
   During the transition from IPv4 to IPv6, scenarios can occur where
   the IP version supported by the receiver differs from that supported
   by the source.  This memo examines what has to be done to allow the
   receiver to acquire multicast address information in the version it
   supports in such scenarios.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-multrans-addr-acquisition

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mboned-multrans-addr-acquisition-00


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


From lenny@juniper.net  Tue Jul 10 09:19:22 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 B8BE911E8140 for <mboned@ietfa.amsl.com>; Tue, 10 Jul 2012 09:19:22 -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 6-ew5OgD-SZN for <mboned@ietfa.amsl.com>; Tue, 10 Jul 2012 09:19:22 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 12FAB11E810B for <mboned@ietf.org>; Tue, 10 Jul 2012 09:19:22 -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/xWJJUL801hCvN0ye9dQh6ygfLh9o7V@postini.com; Tue, 10 Jul 2012 09:19:50 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; Tue, 10 Jul 2012 09:15: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 q6AGFoh15029; Tue, 10 Jul 2012 09:15:50 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 2382B11446;  Tue, 10 Jul 2012 09:15:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 170371141B; Tue, 10 Jul 2012 09:15:50 -0700 (PDT)
Date: Tue, 10 Jul 2012 09:15:50 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
Message-ID: <20120710091341.M7695@eng-mail01.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Subject: [MBONED] Call for agenda items 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, 10 Jul 2012 16:19:22 -0000

If you would like to present anything at MBONED in Vancouver, please let 
Greg and me know what you'd like to cover and how much time you'd like.

Thanks,
MBoned Chairs

From cathy.zhou@huawei.com  Thu Jul 19 20:07:00 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 5A0EB11E80EA for <mboned@ietfa.amsl.com>; Thu, 19 Jul 2012 20:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.477
X-Spam-Level: 
X-Spam-Status: No, score=-6.477 tagged_above=-999 required=5 tests=[AWL=0.122,  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 x-abGLUVh-ON for <mboned@ietfa.amsl.com>; Thu, 19 Jul 2012 20:06:59 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE5311E80E4 for <mboned@ietf.org>; Thu, 19 Jul 2012 20:06:59 -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 AHX42077; Thu, 19 Jul 2012 23:07:54 -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, 19 Jul 2012 20:05:27 -0700
Received: from SZXEML435-HUB.china.huawei.com (10.72.61.63) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 19 Jul 2012 20:05:24 -0700
Received: from SZXEML527-MBX.china.huawei.com ([169.254.3.194]) by szxeml435-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Fri, 20 Jul 2012 11:04:44 +0800
From: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>
To: Leonard Giuliano <lenny@juniper.net>, MBONED WG <mboned@ietf.org>
Thread-Topic: [MBONED] Call for agenda items in MBONED
Thread-Index: AQHNXrfep753TKZJQ0aMMtYVQ+ZD/5cxirSw
Date: Fri, 20 Jul 2012 03:04:42 +0000
Message-ID: <A6A061BEE5DDC94A9692D9D81AF776DF2D486C90@szxeml527-mbx.china.huawei.com>
References: <20120710091341.M7695@eng-mail01.juniper.net>
In-Reply-To: <20120710091341.M7695@eng-mail01.juniper.net>
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [MBONED] Call for agenda items 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, 20 Jul 2012 03:07:00 -0000

Hi chairs,
I'd like a 10 minutes slot for http://tools.ietf.org/html/draft-zhou-mboned=
-multrans-path-optimization-02.

Thanks,
Cathy Zhou

> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On
> Behalf Of Leonard Giuliano
> Sent: Wednesday, July 11, 2012 12:16 AM
> To: MBONED WG
> Subject: [MBONED] Call for agenda items in MBONED
>=20
>=20
> If you would like to present anything at MBONED in Vancouver, please let
> Greg and me know what you'd like to cover and how much time you'd like.
>=20
> Thanks,
> MBoned Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From lenny@juniper.net  Mon Jul 23 13:02:57 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 ADB9E11E807F for <mboned@ietfa.amsl.com>; Mon, 23 Jul 2012 13:02:57 -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 A1Guvl8wL4wg for <mboned@ietfa.amsl.com>; Mon, 23 Jul 2012 13:02:57 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 63A0311E8072 for <mboned@ietf.org>; Mon, 23 Jul 2012 13:02:56 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUA2t7/Dhk6iPgTSTfqqwKjWptJwknmh0@postini.com; Mon, 23 Jul 2012 13:02:56 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, 23 Jul 2012 13:01:27 -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 q6NK1Qh31488	for <mboned@ietf.org>; Mon, 23 Jul 2012 13:01:27 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id CAB6E11446;  Mon, 23 Jul 2012 13:01:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id BEDFB1141B	for <mboned@ietf.org>; Mon, 23 Jul 2012 13:01:26 -0700 (PDT)
Date: Mon, 23 Jul 2012 13:01:26 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
Message-ID: <20120723124102.M27861@eng-mail01.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Subject: [MBONED] recharter text
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, 23 Jul 2012 20:02:57 -0000

Here is the proposed recharter verbage based on feedback from the mtg in 
Paris.  Once again, only the last bullet is new (plus a few completed 
items are removed).

Please send comments by Aug 6.

Thanks,
MBONED Chairs

****

The MBONE Deployment Working Group is a forum for coordinating
the deployment, engineering, and operation of multicast routing
protocols and procedures in the global Internet. This activity will
include, but not be limited to:

- Documenting deployment of multicast routing in the global Internet.

- Receive regular reports on the current state of the deployment of
multicast technology. Create "practice and experience" documents that
capture the experience of those who have deployed and are deploying
various multicast technologies.

- Based on reports and other information, provide feedback to other
relevant working groups.

- Develop mechanisms and procedures for sharing operational
information to aid in operation of the multicast backbones and
interconnects.

- Develop tools and protocols that assist in multicast administration, 
diagnostics, troubleshooting and deployment in native and non-native 
environments. While development of routing and group membership protocols 
is out of scope, this working group may develop requirements and assist in 
review and feedback of documents in other working groups responsible for 
such protocols.


From mmcbride7@gmail.com  Mon Jul 23 16:23:08 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 4B2C811E80F0 for <mboned@ietfa.amsl.com>; Mon, 23 Jul 2012 16:23:08 -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 HFdEvfV0EIDO for <mboned@ietfa.amsl.com>; Mon, 23 Jul 2012 16:23:07 -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 AB80D11E80E7 for <mboned@ietf.org>; Mon, 23 Jul 2012 16:23:07 -0700 (PDT)
Received: by yenq13 with SMTP id q13so6639376yen.31 for <mboned@ietf.org>; Mon, 23 Jul 2012 16:23:07 -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; bh=nHqvIC+dch0ZEE73EgRy2WgnkRoMLEYACjgPPjCCjTo=; b=a69s4hgj8Gz74BNGOybZ00w7elO1IVCeNUYuiv5iU9xkhOBT9YlW9tSlYTyWZRmrEi NkbAWULqHDITpCBMsq8u+QqsT4sSiS+NmZybfNH/70eQ+/RRuqMq+6RhZvTid/kg734j PxhP3GemcD48fahdNs7GfB6HakCk9dakr2/JoFb31i8FDBDb1YkzcKg9kuMW6G+2VdYx h+JQjCzQKzz3meWZ7MJvqYJr1dJloy2qLuxQl7mLqn5Y3d7VTqQgGer6QZfU+LK6fgFY sysX0Pr46uTHKd4sAVuSHxFEFO2Y4Ve4+oOQv8cJb04yKls8thHbqb18TSYG1bBut6+H CivQ==
MIME-Version: 1.0
Received: by 10.43.85.69 with SMTP id an5mr10081105icc.37.1343085786944; Mon, 23 Jul 2012 16:23:06 -0700 (PDT)
Received: by 10.64.63.13 with HTTP; Mon, 23 Jul 2012 16:23:06 -0700 (PDT)
In-Reply-To: <20120723124102.M27861@eng-mail01.juniper.net>
References: <20120723124102.M27861@eng-mail01.juniper.net>
Date: Mon, 23 Jul 2012 16:23:06 -0700
Message-ID: <CAL3FGfzpxd959+3sXaaR3eTDxvoszA4fc8P83y2xXjTcdvAnHQ@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: Leonard Giuliano <lenny@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] recharter text
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, 23 Jul 2012 23:23:08 -0000

Lenny, Greg,

MBONED is *the* multicast operations forum. And, since there is a fair
amount of activity in the data center, I'd like to see the MBONED
charter expanding to specifically include DC deployment, engineering
and operation of multicast.

thanks,
mike

On Mon, Jul 23, 2012 at 1:01 PM, Leonard Giuliano <lenny@juniper.net> wrote:
>
> Here is the proposed recharter verbage based on feedback from the mtg in
> Paris.  Once again, only the last bullet is new (plus a few completed items
> are removed).
>
> Please send comments by Aug 6.
>
> Thanks,
> MBONED Chairs
>
> ****
>
> The MBONE Deployment Working Group is a forum for coordinating
> the deployment, engineering, and operation of multicast routing
> protocols and procedures in the global Internet. This activity will
> include, but not be limited to:
>
> - Documenting deployment of multicast routing in the global Internet.
>
> - Receive regular reports on the current state of the deployment of
> multicast technology. Create "practice and experience" documents that
> capture the experience of those who have deployed and are deploying
> various multicast technologies.
>
> - Based on reports and other information, provide feedback to other
> relevant working groups.
>
> - Develop mechanisms and procedures for sharing operational
> information to aid in operation of the multicast backbones and
> interconnects.
>
> - Develop tools and protocols that assist in multicast administration,
> diagnostics, troubleshooting and deployment in native and non-native
> environments. While development of routing and group membership protocols is
> out of scope, this working group may develop requirements and assist in
> review and feedback of documents in other working groups responsible for
> such protocols.
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From tom.taylor.stds@gmail.com  Mon Jul 23 18:03:26 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 8D16711E80BF for <mboned@ietfa.amsl.com>; Mon, 23 Jul 2012 18:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.544
X-Spam-Level: 
X-Spam-Status: No, score=-3.544 tagged_above=-999 required=5 tests=[AWL=0.055,  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 2MJhT+qMbZD6 for <mboned@ietfa.amsl.com>; Mon, 23 Jul 2012 18:03:24 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id EF31311E8085 for <mboned@ietf.org>; Mon, 23 Jul 2012 18:03:23 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so4475740wgb.13 for <mboned@ietf.org>; Mon, 23 Jul 2012 18:03:13 -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=SA5Bg0rzPsvt3G30W2Ty+2jB3859RNEx+czN/B8tMw8=; b=j53h+c2kcdynHxcmlG7pRZlYFGWBgk1NeUvdjvgggU+ffdkZL0J0CWJwtBXK13YiWi +Rz6JlKViHru1rmLdj4WGRYFJLZVVGG9HpNkq7A31eVSQ4Z4BfElJ9ubJwKR7Qv7E3J3 pw4uoIvFdC49kvJMCoEtECyAIibgQmQL9A+AJMeHqh2X6O2HvgIRh8/wJ61TIkV+VgCB rV6zgeTYIgGQlqdbDwWpaIenxC16x9LXk9sKvjlVviBjgkwKlN4rBzmQK6+U1ngDnanZ KWz1fFBhpHKxKTOKrBuTTPVtLD0VvpZQdKDfYFpevDj2TRHPKoAsqP9uUofV3uFUro6T sBUA==
Received: by 10.180.81.138 with SMTP id a10mr2115642wiy.7.1343091793433; Mon, 23 Jul 2012 18:03:13 -0700 (PDT)
Received: from [127.0.0.1] (dsl-173-206-32-179.tor.primus.ca. [173.206.32.179]) by mx.google.com with ESMTPS id cu1sm1602987wib.6.2012.07.23.18.03.11 (version=SSLv3 cipher=OTHER); Mon, 23 Jul 2012 18:03:12 -0700 (PDT)
Message-ID: <500DF44C.7070006@gmail.com>
Date: Mon, 23 Jul 2012 21:03:08 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Leonard Giuliano <lenny@juniper.net>
References: <20120723124102.M27861@eng-mail01.juniper.net>
In-Reply-To: <20120723124102.M27861@eng-mail01.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120723-2, 23/07/2012), Outbound message
X-Antivirus-Status: Clean
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] recharter text
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, 24 Jul 2012 01:03:27 -0000

So I see Ron deleted the word "transition" from the last bullet after 
all. In Paris we had wordsmithed the bullet without doing that.

On 23/07/2012 4:01 PM, Leonard Giuliano wrote:
>
> Here is the proposed recharter verbage based on feedback from the mtg in
> Paris.  Once again, only the last bullet is new (plus a few completed
> items are removed).
>
> Please send comments by Aug 6.
>
> Thanks,
> MBONED Chairs
>
> ****
>
> The MBONE Deployment Working Group is a forum for coordinating
> the deployment, engineering, and operation of multicast routing
> protocols and procedures in the global Internet. This activity will
> include, but not be limited to:
>
> - Documenting deployment of multicast routing in the global Internet.
>
> - Receive regular reports on the current state of the deployment of
> multicast technology. Create "practice and experience" documents that
> capture the experience of those who have deployed and are deploying
> various multicast technologies.
>
> - Based on reports and other information, provide feedback to other
> relevant working groups.
>
> - Develop mechanisms and procedures for sharing operational
> information to aid in operation of the multicast backbones and
> interconnects.
>
> - Develop tools and protocols that assist in multicast administration,
> diagnostics, troubleshooting and deployment in native and non-native
> environments. While development of routing and group membership
> protocols is out of scope, this working group may develop requirements
> and assist in review and feedback of documents in other working groups
> responsible for such protocols.
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>

From rbonica@juniper.net  Tue Jul 24 07:23:37 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 4A53721F8697 for <mboned@ietfa.amsl.com>; Tue, 24 Jul 2012 07:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level: 
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 k1jqx2bxY2J9 for <mboned@ietfa.amsl.com>; Tue, 24 Jul 2012 07:23:36 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id A150021F8694 for <mboned@ietf.org>; Tue, 24 Jul 2012 07:23:36 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKUA6v5/5i1zerCA1iX8dUkj1PzCX5XYXA@postini.com; Tue, 24 Jul 2012 07:23:36 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; Tue, 24 Jul 2012 07:21:58 -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; Tue, 24 Jul 2012 07:21:58 -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, 24 Jul 2012 10:21:57 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Tue, 24 Jul 2012 10:21:56 -0400
Thread-Topic: [MBONED] recharter text
Thread-Index: Ac1pOCUtpMhg5xvlQf+c+JsIDuSy4QAb0fuQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D770B96D6A@EMBX01-WF.jnpr.net>
References: <mailman.309.1343091808.3364.mboned@ietf.org>
In-Reply-To: <mailman.309.1343091808.3364.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] recharter text
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, 24 Jul 2012 14:23:37 -0000

Tom,

Do you have alternative text that you prefer? While I am not promising to a=
dopt it, we can at least discuss the differences.

                                                 Ron



>=20
> So I see Ron deleted the word "transition" from the last bullet after
> all. In Paris we had wordsmithed the bullet without doing that.
>=20



From lenny@juniper.net  Tue Jul 24 07:48:12 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 4EABC21F85DD for <mboned@ietfa.amsl.com>; Tue, 24 Jul 2012 07:48:12 -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 WT46XKnUmPHD for <mboned@ietfa.amsl.com>; Tue, 24 Jul 2012 07:48:11 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD9E21F85DB for <mboned@ietf.org>; Tue, 24 Jul 2012 07:48:11 -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 DSNKUA61qXgeIC5zlWv9tAtBGg4rn7z/kXXr@postini.com; Tue, 24 Jul 2012 07:48:11 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; Tue, 24 Jul 2012 07:45:08 -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 q6OEj5h58192; Tue, 24 Jul 2012 07:45:07 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 55A341144F;  Tue, 24 Jul 2012 07:45:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 4BA2511446; Tue, 24 Jul 2012 07:45:05 -0700 (PDT)
Date: Tue, 24 Jul 2012 07:45:05 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Tom Taylor <tom.taylor.stds@gmail.com>
In-Reply-To: <500DF44C.7070006@gmail.com>
Message-ID: <20120724074114.E67488@eng-mail01.juniper.net>
References: <20120723124102.M27861@eng-mail01.juniper.net> <500DF44C.7070006@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] recharter text
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, 24 Jul 2012 14:48:12 -0000

Keep in mind "transition" was only in there in the first place to cover 
AMT, that is the transition from unicast-only to multicast.  So it was 
changed to "... native and non-native environments..." to clarify original 
intent.


On Mon, 23 Jul 2012, Tom Taylor wrote:

-) So I see Ron deleted the word "transition" from the last bullet after all. In
-) Paris we had wordsmithed the bullet without doing that.
-) 
-) On 23/07/2012 4:01 PM, Leonard Giuliano wrote:
-) > 
-) > Here is the proposed recharter verbage based on feedback from the mtg in
-) > Paris.  Once again, only the last bullet is new (plus a few completed
-) > items are removed).
-) > 
-) > Please send comments by Aug 6.
-) > 
-) > Thanks,
-) > MBONED Chairs
-) > 
-) > ****
-) > 
-) > The MBONE Deployment Working Group is a forum for coordinating
-) > the deployment, engineering, and operation of multicast routing
-) > protocols and procedures in the global Internet. This activity will
-) > include, but not be limited to:
-) > 
-) > - Documenting deployment of multicast routing in the global Internet.
-) > 
-) > - Receive regular reports on the current state of the deployment of
-) > multicast technology. Create "practice and experience" documents that
-) > capture the experience of those who have deployed and are deploying
-) > various multicast technologies.
-) > 
-) > - Based on reports and other information, provide feedback to other
-) > relevant working groups.
-) > 
-) > - Develop mechanisms and procedures for sharing operational
-) > information to aid in operation of the multicast backbones and
-) > interconnects.
-) > 
-) > - Develop tools and protocols that assist in multicast administration,
-) > diagnostics, troubleshooting and deployment in native and non-native
-) > environments. While development of routing and group membership
-) > protocols is out of scope, this working group may develop requirements
-) > and assist in review and feedback of documents in other working groups
-) > responsible for such protocols.
-) > 
-) > _______________________________________________
-) > MBONED mailing list
-) > MBONED@ietf.org
-) > https://www.ietf.org/mailman/listinfo/mboned
-) > 
-) 

From stig@venaas.com  Tue Jul 24 12:20:54 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 861BC21F8463 for <mboned@ietfa.amsl.com>; Tue, 24 Jul 2012 12:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 M6OQ100j3iy2 for <mboned@ietfa.amsl.com>; Tue, 24 Jul 2012 12:20:53 -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 B2A3E21F8462 for <mboned@ietf.org>; Tue, 24 Jul 2012 12:20:53 -0700 (PDT)
Received: from [IPv6:2001:420:301:1004:459a:d645:29ff:f879] (unknown [IPv6:2001:420:301:1004:459a:d645:29ff:f879]) by ufisa.uninett.no (Postfix) with ESMTPSA id 9194B7FC8; Tue, 24 Jul 2012 21:20:50 +0200 (CEST)
Message-ID: <500EF58F.8050000@venaas.com>
Date: Tue, 24 Jul 2012 12:20:47 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Leonard Giuliano <lenny@juniper.net>
References: <20120723124102.M27861@eng-mail01.juniper.net> <500DF44C.7070006@gmail.com> <20120724074114.E67488@eng-mail01.juniper.net>
In-Reply-To: <20120724074114.E67488@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] recharter text
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, 24 Jul 2012 19:20:54 -0000

On 7/24/2012 7:45 AM, Leonard Giuliano wrote:
>
> Keep in mind "transition" was only in there in the first place to cover
> AMT, that is the transition from unicast-only to multicast.  So it was
> changed to "... native and non-native environments..." to clarify original
> intent.

With the proposed charter text, does it include these WG documents?

draft-ietf-mboned-multrans-addr-acquisition
draft-ietf-mboned-v4v6-mcast-ps

Maybe it does, but it's not clear to me.

We should make sure they are somehow covered by the new text.

Stig

>
>
> On Mon, 23 Jul 2012, Tom Taylor wrote:
>
> -) So I see Ron deleted the word "transition" from the last bullet after all. In
> -) Paris we had wordsmithed the bullet without doing that.
> -)
> -) On 23/07/2012 4:01 PM, Leonard Giuliano wrote:
> -) >
> -) > Here is the proposed recharter verbage based on feedback from the mtg in
> -) > Paris.  Once again, only the last bullet is new (plus a few completed
> -) > items are removed).
> -) >
> -) > Please send comments by Aug 6.
> -) >
> -) > Thanks,
> -) > MBONED Chairs
> -) >
> -) > ****
> -) >
> -) > The MBONE Deployment Working Group is a forum for coordinating
> -) > the deployment, engineering, and operation of multicast routing
> -) > protocols and procedures in the global Internet. This activity will
> -) > include, but not be limited to:
> -) >
> -) > - Documenting deployment of multicast routing in the global Internet.
> -) >
> -) > - Receive regular reports on the current state of the deployment of
> -) > multicast technology. Create "practice and experience" documents that
> -) > capture the experience of those who have deployed and are deploying
> -) > various multicast technologies.
> -) >
> -) > - Based on reports and other information, provide feedback to other
> -) > relevant working groups.
> -) >
> -) > - Develop mechanisms and procedures for sharing operational
> -) > information to aid in operation of the multicast backbones and
> -) > interconnects.
> -) >
> -) > - Develop tools and protocols that assist in multicast administration,
> -) > diagnostics, troubleshooting and deployment in native and non-native
> -) > environments. While development of routing and group membership
> -) > protocols is out of scope, this working group may develop requirements
> -) > and assist in review and feedback of documents in other working groups
> -) > responsible for such protocols.
> -) >
> -) > _______________________________________________
> -) > 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 tom.taylor.stds@gmail.com  Tue Jul 24 17:01:04 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 8A17C11E8088 for <mboned@ietfa.amsl.com>; Tue, 24 Jul 2012 17:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.547
X-Spam-Level: 
X-Spam-Status: No, score=-3.547 tagged_above=-999 required=5 tests=[AWL=0.052,  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 0m1FbQ4bN9Ur for <mboned@ietfa.amsl.com>; Tue, 24 Jul 2012 17:01:03 -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 3D79A21F84FF for <mboned@ietf.org>; Tue, 24 Jul 2012 17:01:03 -0700 (PDT)
Received: by bkty7 with SMTP id y7so78917bkt.31 for <mboned@ietf.org>; Tue, 24 Jul 2012 17:01:02 -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=rOnZrRHtQIdPOHl0bl8YWxNYszlZ8hBntnU6Kq36hL8=; b=eo6/Fwe8PDTcNlkUSkZIPO3Ncfmpv+fj322F9s3uVGzH/TGnVYWSOhncjhXd2CcAmG TyofJCL0Y3xIShD4BW1fJ+PgXZAmnKDigVlpiAymsTieeYsngNruEk70LH9OP2HJaaB3 qPqeuYSMmVlnAwrZh5fngfHhrEkNNIK2njG7spgYUQDSDihScjtgYVTagaIzXA2kJRXJ roMojCGubsHrid6+b4pft1YewwncSofvx+JsEiOEGIH7cYsbLeEhTbGkjDwRcpHBgSu6 B2X/RlmJ1CJnMKDkIP29Q4awOiOYklBTrSkDTUtU1x/9qFE3jyUG/71ijRpdjwN22hTo 2AUQ==
Received: by 10.204.130.216 with SMTP id u24mr11328953bks.119.1343174462033; Tue, 24 Jul 2012 17:01:02 -0700 (PDT)
Received: from [127.0.0.1] (dsl-173-206-32-179.tor.primus.ca. [173.206.32.179]) by mx.google.com with ESMTPS id n17sm11744650bks.6.2012.07.24.17.01.00 (version=SSLv3 cipher=OTHER); Tue, 24 Jul 2012 17:01:01 -0700 (PDT)
Message-ID: <500F373A.3060206@gmail.com>
Date: Tue, 24 Jul 2012 20:00:58 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Stig Venaas <stig@venaas.com>
References: <20120723124102.M27861@eng-mail01.juniper.net> <500DF44C.7070006@gmail.com> <20120724074114.E67488@eng-mail01.juniper.net> <500EF58F.8050000@venaas.com>
In-Reply-To: <500EF58F.8050000@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120724-1, 24/07/2012), Outbound message
X-Antivirus-Status: Clean
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] recharter text
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, 25 Jul 2012 00:01:04 -0000

That's my concern too. Leonard's interpretation of "transition" doesn't 
match our understanding in Paris. Until we get that settled there's no 
point in adding it back to the charter.

On 24/07/2012 3:20 PM, Stig Venaas wrote:
> On 7/24/2012 7:45 AM, Leonard Giuliano wrote:
>>
>> Keep in mind "transition" was only in there in the first place to cover
>> AMT, that is the transition from unicast-only to multicast.  So it was
>> changed to "... native and non-native environments..." to clarify
>> original
>> intent.
>
> With the proposed charter text, does it include these WG documents?
>
> draft-ietf-mboned-multrans-addr-acquisition
> draft-ietf-mboned-v4v6-mcast-ps
>
> Maybe it does, but it's not clear to me.
>
> We should make sure they are somehow covered by the new text.
>
> Stig
>
>>
>>
>> On Mon, 23 Jul 2012, Tom Taylor wrote:
>>
>> -) So I see Ron deleted the word "transition" from the last bullet
>> after all. In
>> -) Paris we had wordsmithed the bullet without doing that.
>> -)
>> -) On 23/07/2012 4:01 PM, Leonard Giuliano wrote:
>> -) >
>> -) > Here is the proposed recharter verbage based on feedback from the
>> mtg in
>> -) > Paris.  Once again, only the last bullet is new (plus a few
>> completed
>> -) > items are removed).
>> -) >
>> -) > Please send comments by Aug 6.
>> -) >
>> -) > Thanks,
>> -) > MBONED Chairs
>> -) >
>> -) > ****
>> -) >
>> -) > The MBONE Deployment Working Group is a forum for coordinating
>> -) > the deployment, engineering, and operation of multicast routing
>> -) > protocols and procedures in the global Internet. This activity will
>> -) > include, but not be limited to:
>> -) >
>> -) > - Documenting deployment of multicast routing in the global
>> Internet.
>> -) >
>> -) > - Receive regular reports on the current state of the deployment of
>> -) > multicast technology. Create "practice and experience" documents
>> that
>> -) > capture the experience of those who have deployed and are deploying
>> -) > various multicast technologies.
>> -) >
>> -) > - Based on reports and other information, provide feedback to other
>> -) > relevant working groups.
>> -) >
>> -) > - Develop mechanisms and procedures for sharing operational
>> -) > information to aid in operation of the multicast backbones and
>> -) > interconnects.
>> -) >
>> -) > - Develop tools and protocols that assist in multicast
>> administration,
>> -) > diagnostics, troubleshooting and deployment in native and non-native
>> -) > environments. While development of routing and group membership
>> -) > protocols is out of scope, this working group may develop
>> requirements
>> -) > and assist in review and feedback of documents in other working
>> groups
>> -) > responsible for such protocols.
>> -) >
>> -) > _______________________________________________
>> -) > 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 lenny@juniper.net  Tue Jul 24 18:03:54 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 8505D11E8080 for <mboned@ietfa.amsl.com>; Tue, 24 Jul 2012 18:03:54 -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 6PrFVnolYz+p for <mboned@ietfa.amsl.com>; Tue, 24 Jul 2012 18:03:54 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id C47E411E80A4 for <mboned@ietf.org>; Tue, 24 Jul 2012 18:03:53 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKUA9F9zKQ9X5pjfpwKyVbXA4oos9HLuEL@postini.com; Tue, 24 Jul 2012 18:03:53 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; Tue, 24 Jul 2012 17:58: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 q6P0wnh17530; Tue, 24 Jul 2012 17:58:49 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id D8E811144E;  Tue, 24 Jul 2012 17:58:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id CE8CB11446; Tue, 24 Jul 2012 17:58:49 -0700 (PDT)
Date: Tue, 24 Jul 2012 17:58:49 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Mike McBride <mmcbride7@gmail.com>
In-Reply-To: <CAL3FGfzpxd959+3sXaaR3eTDxvoszA4fc8P83y2xXjTcdvAnHQ@mail.gmail.com>
Message-ID: <20120724175109.T19170@eng-mail01.juniper.net>
References: <20120723124102.M27861@eng-mail01.juniper.net> <CAL3FGfzpxd959+3sXaaR3eTDxvoszA4fc8P83y2xXjTcdvAnHQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] recharter text
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, 25 Jul 2012 01:03:54 -0000

Mike- I see nothing in the current charter that would preclude MBONED from 
taking on work related to data centers.  Also, I think there is a risk in 
overly specific enumeration of networking components, where some could 
imply that if it isn't specifically mentioned in the charter it is 
explictly excluded.  

If there are drafts related to data centers that you think should be 
adopted, let's have them presented.  If the charter presents a barrier, we 
can always address later.


On Mon, 23 Jul 2012, Mike McBride wrote:

-) Lenny, Greg,
-) 
-) MBONED is *the* multicast operations forum. And, since there is a fair
-) amount of activity in the data center, I'd like to see the MBONED
-) charter expanding to specifically include DC deployment, engineering
-) and operation of multicast.
-) 
-) thanks,
-) mike
-) 
-) On Mon, Jul 23, 2012 at 1:01 PM, Leonard Giuliano <lenny@juniper.net> wrote:
-) >
-) > Here is the proposed recharter verbage based on feedback from the mtg in
-) > Paris.  Once again, only the last bullet is new (plus a few completed items
-) > are removed).
-) >
-) > Please send comments by Aug 6.
-) >
-) > Thanks,
-) > MBONED Chairs
-) >
-) > ****
-) >
-) > The MBONE Deployment Working Group is a forum for coordinating
-) > the deployment, engineering, and operation of multicast routing
-) > protocols and procedures in the global Internet. This activity will
-) > include, but not be limited to:
-) >
-) > - Documenting deployment of multicast routing in the global Internet.
-) >
-) > - Receive regular reports on the current state of the deployment of
-) > multicast technology. Create "practice and experience" documents that
-) > capture the experience of those who have deployed and are deploying
-) > various multicast technologies.
-) >
-) > - Based on reports and other information, provide feedback to other
-) > relevant working groups.
-) >
-) > - Develop mechanisms and procedures for sharing operational
-) > information to aid in operation of the multicast backbones and
-) > interconnects.
-) >
-) > - Develop tools and protocols that assist in multicast administration,
-) > diagnostics, troubleshooting and deployment in native and non-native
-) > environments. While development of routing and group membership protocols is
-) > out of scope, this working group may develop requirements and assist in
-) > review and feedback of documents in other working groups responsible for
-) > such protocols.
-) >
-) > _______________________________________________
-) > MBONED mailing list
-) > MBONED@ietf.org
-) > https://www.ietf.org/mailman/listinfo/mboned
-) 

From rbonica@juniper.net  Wed Jul 25 07:14:19 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 432D621F85E3 for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 07:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level: 
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 vEcQZQ0PZA3z for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 07:14:18 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 94BBD21F85C7 for <mboned@ietf.org>; Wed, 25 Jul 2012 07:14:18 -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 DSNKUA//Om76qNXtFku/pZjGvK6xPme73oYM@postini.com; Wed, 25 Jul 2012 07:14:18 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, 25 Jul 2012 07:12:56 -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; Wed, 25 Jul 2012 07:12:56 -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; Wed, 25 Jul 2012 10:12:54 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Wed, 25 Jul 2012 10:12:53 -0400
Thread-Topic: [MBONED] recharter text
Thread-Index: Ac1p0XvlCb49LErWRrGql+0gVBPg4gAna1Kg
Message-ID: <13205C286662DE4387D9AF3AC30EF456D770C81AE2@EMBX01-WF.jnpr.net>
References: <mailman.584.1343157655.3364.mboned@ietf.org>
In-Reply-To: <mailman.584.1343157655.3364.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] recharter text
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, 25 Jul 2012 14:14:19 -0000

Stig,

I would be reluctant to add any of the MLTRANS work to the charter until th=
e use-case issues surrounding draft-ietf-mboned-v4v6-mcast-ps are resolved.=
 Otherwise, we might be chartering work that will never be deployed.

                                               Ron
                                         =20

>=20
> With the proposed charter text, does it include these WG documents?
>=20
> draft-ietf-mboned-multrans-addr-acquisition
> draft-ietf-mboned-v4v6-mcast-ps
>=20
> Maybe it does, but it's not clear to me.
>=20
> We should make sure they are somehow covered by the new text.
>=20
> Stig
>=20


From mmcbride7@gmail.com  Wed Jul 25 09:55:45 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 E553321F867B for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 09:55:45 -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 QW2ts3P1tgPL for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 09:55:45 -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 1D59821F864F for <mboned@ietf.org>; Wed, 25 Jul 2012 09:55:45 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so1542308obb.31 for <mboned@ietf.org>; Wed, 25 Jul 2012 09:55:44 -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; bh=C6M0jSt+kzB/HIXbeYjUhtTUVd9apTayMY/awQHiGW0=; b=Zt8u9i9QZetJg3f9V5yJHF206elLgr224Q5iqye8W+Lh4GViyaRGc5zHMwUOhaHnbz QzLEKvC2Jq7Y9+MD8xD1m/wpRjCjyt2iFbtMCbrfEPwbdanrFPLdq2gHM7LNRLJyHZfF 9Wje7jRSWvg55Iqgn59ZuXAyN4zlTq4pdVoannx1CzynZfL5RVb47Ltq69pJSNRzmiHk sORmbDBnO7EfSaZurAcIHob4bTYsa5i9BGJp0EqfPPhhE9Xci+l1rWGE4oGEEeJRWBDL CzRZBTjoBYJ8zTQkuiPFLdgdSVzHYjx78T/y8FhV9RVlUQ2aT7AF5Y6zVNL7HLKhfy90 T6rQ==
MIME-Version: 1.0
Received: by 10.182.119.72 with SMTP id ks8mr36403607obb.10.1343235344658; Wed, 25 Jul 2012 09:55:44 -0700 (PDT)
Received: by 10.60.23.70 with HTTP; Wed, 25 Jul 2012 09:55:44 -0700 (PDT)
In-Reply-To: <20120724175109.T19170@eng-mail01.juniper.net>
References: <20120723124102.M27861@eng-mail01.juniper.net> <CAL3FGfzpxd959+3sXaaR3eTDxvoszA4fc8P83y2xXjTcdvAnHQ@mail.gmail.com> <20120724175109.T19170@eng-mail01.juniper.net>
Date: Wed, 25 Jul 2012 09:55:44 -0700
Message-ID: <CAL3FGfx==rebzjv038CZWM5FJN6DUh00Bbjx9NU4NUoCFx7NyQ@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: Leonard Giuliano <lenny@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] recharter text
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, 25 Jul 2012 16:55:46 -0000

Lenny,

If "global internet" includes data centers, sdn's, and other areas of
potential multicast work then I suppose I agree, we should be good.

But I still think it would be helpful to call these areas out. Much
has changed since the mbone of the 90s. If this wg doesn't update its
charter with new work, that work will be done somewhere else and
mboned is at risk of becoming obsolete. I don't want that.

mike

On Tue, Jul 24, 2012 at 5:58 PM, Leonard Giuliano <lenny@juniper.net> wrote:
>
> Mike- I see nothing in the current charter that would preclude MBONED from
> taking on work related to data centers.  Also, I think there is a risk in
> overly specific enumeration of networking components, where some could
> imply that if it isn't specifically mentioned in the charter it is
> explictly excluded.
>
> If there are drafts related to data centers that you think should be
> adopted, let's have them presented.  If the charter presents a barrier, we
> can always address later.
>
>
> On Mon, 23 Jul 2012, Mike McBride wrote:
>
> -) Lenny, Greg,
> -)
> -) MBONED is *the* multicast operations forum. And, since there is a fair
> -) amount of activity in the data center, I'd like to see the MBONED
> -) charter expanding to specifically include DC deployment, engineering
> -) and operation of multicast.
> -)
> -) thanks,
> -) mike
> -)
> -) On Mon, Jul 23, 2012 at 1:01 PM, Leonard Giuliano <lenny@juniper.net> wrote:
> -) >
> -) > Here is the proposed recharter verbage based on feedback from the mtg in
> -) > Paris.  Once again, only the last bullet is new (plus a few completed items
> -) > are removed).
> -) >
> -) > Please send comments by Aug 6.
> -) >
> -) > Thanks,
> -) > MBONED Chairs
> -) >
> -) > ****
> -) >
> -) > The MBONE Deployment Working Group is a forum for coordinating
> -) > the deployment, engineering, and operation of multicast routing
> -) > protocols and procedures in the global Internet. This activity will
> -) > include, but not be limited to:
> -) >
> -) > - Documenting deployment of multicast routing in the global Internet.
> -) >
> -) > - Receive regular reports on the current state of the deployment of
> -) > multicast technology. Create "practice and experience" documents that
> -) > capture the experience of those who have deployed and are deploying
> -) > various multicast technologies.
> -) >
> -) > - Based on reports and other information, provide feedback to other
> -) > relevant working groups.
> -) >
> -) > - Develop mechanisms and procedures for sharing operational
> -) > information to aid in operation of the multicast backbones and
> -) > interconnects.
> -) >
> -) > - Develop tools and protocols that assist in multicast administration,
> -) > diagnostics, troubleshooting and deployment in native and non-native
> -) > environments. While development of routing and group membership protocols is
> -) > out of scope, this working group may develop requirements and assist in
> -) > review and feedback of documents in other working groups responsible for
> -) > such protocols.
> -) >
> -) > _______________________________________________
> -) > MBONED mailing list
> -) > MBONED@ietf.org
> -) > https://www.ietf.org/mailman/listinfo/mboned
> -)

From stig@venaas.com  Wed Jul 25 10:43:19 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 AC10E21F86F3 for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 10:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 cxrscotbKE5h for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 10:43:19 -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 093A621F86A8 for <mboned@ietf.org>; Wed, 25 Jul 2012 10:43:19 -0700 (PDT)
Received: from [IPv6:2001:420:301:1004:48fd:6ab5:b50b:91cd] (unknown [IPv6:2001:420:301:1004:48fd:6ab5:b50b:91cd]) by ufisa.uninett.no (Postfix) with ESMTPSA id 08F427FB7; Wed, 25 Jul 2012 19:43:16 +0200 (CEST)
Message-ID: <50103032.9060900@venaas.com>
Date: Wed, 25 Jul 2012 10:43:14 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <mailman.584.1343157655.3364.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D770C81AE2@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D770C81AE2@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] recharter text
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, 25 Jul 2012 17:43:19 -0000

On 7/25/2012 7:12 AM, Ronald Bonica wrote:
> Stig,
>
> I would be reluctant to add any of the MLTRANS work to the charter until the use-case issues surrounding draft-ietf-mboned-v4v6-mcast-ps are resolved. Otherwise, we might be chartering work that will never be deployed.

Agree, but shouldn't it at least include what is already adopted?
E.g. something like:

- Analyze the need for IPv4 - IPv6 multicast transition solutions

I'm not saying that it need to have the full MULTRANS work in there, just
sufficient text to at least include the work that the group already has
agreed to work on (the adopted drafts).

Stig

>                                                 Ron
>
>
>>
>> With the proposed charter text, does it include these WG documents?
>>
>> draft-ietf-mboned-multrans-addr-acquisition
>> draft-ietf-mboned-v4v6-mcast-ps
>>
>> Maybe it does, but it's not clear to me.
>>
>> We should make sure they are somehow covered by the new text.
>>
>> Stig
>>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>


From rbonica@juniper.net  Wed Jul 25 11:35: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 0F06C21F866B for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 11:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.572
X-Spam-Level: 
X-Spam-Status: No, score=-106.572 tagged_above=-999 required=5 tests=[AWL=0.027, 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 X5bZxtYIQeyT for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 11:35:56 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3388321F864C for <mboned@ietf.org>; Wed, 25 Jul 2012 11:35:55 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKUBA8iJKjaPK11bOoV72urPvdB9Z5h/fX@postini.com; Wed, 25 Jul 2012 11:35:55 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 25 Jul 2012 11:35:40 -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; Wed, 25 Jul 2012 11:35:40 -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; Wed, 25 Jul 2012 14:35:39 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Stig Venaas <stig@venaas.com>
Date: Wed, 25 Jul 2012 14:35:38 -0400
Thread-Topic: [MBONED] recharter text
Thread-Index: Ac1qjPvvMN+oqSsKTM+YWBNuNlCNUwABmjdg
Message-ID: <13205C286662DE4387D9AF3AC30EF456D770C8209C@EMBX01-WF.jnpr.net>
References: <mailman.584.1343157655.3364.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D770C81AE2@EMBX01-WF.jnpr.net> <50103032.9060900@venaas.com>
In-Reply-To: <50103032.9060900@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
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] recharter text
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, 25 Jul 2012 18:35:57 -0000

>=20
> - Analyze the need for IPv4 - IPv6 multicast transition solutions
>=20

Stig,

I would be happy with this text, but nothing more. AFAIKS, an thorough anal=
ysis of the need for IPv4 - IPv6 multicast transition solutions may reveal =
that:

- there is an need to solve the IPvX-DualStack-IPvY use cases
- all other use cases are best addressed by caching content on strategicall=
y located, dual-stack devices or, even better, by deploying dual stack

If we were to put anything about MLTRANS solutions into the document, we mi=
ght be committing to do work that will never see deployment.

                                                     Ron


From lenny@juniper.net  Wed Jul 25 12:10:13 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 8EB2921F85F7 for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 12:10:13 -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 PCSgzNmCwoRi for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 12:10:12 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 54A1D21F8644 for <mboned@ietf.org>; Wed, 25 Jul 2012 12:10:12 -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 DSNKUBBEk0fNHt8FLDmCo6Mv7q1Nu0mf68/o@postini.com; Wed, 25 Jul 2012 12:10:12 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; Wed, 25 Jul 2012 12:06: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 q6PJ6nh35859	for <mboned@ietf.org>; Wed, 25 Jul 2012 12:06:49 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id C604011446;  Wed, 25 Jul 2012 12:06:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id BA1451141B	for <mboned@ietf.org>; Wed, 25 Jul 2012 12:06:49 -0700 (PDT)
Date: Wed, 25 Jul 2012 12:06:49 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
Message-ID: <20120725120437.P55680@eng-mail01.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Subject: [MBONED] Vancouver Agenda
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, 25 Jul 2012 19:10:13 -0000

Here's what we have so far in terms of presenters.  Please let me know if 
I missed anyone.  Those of you presenting please send the chairs your 
slides by this Fri so we have ample time to upload for remote viewers.


draft-kumar-mboned-64mcast-embedded-address-00	Stig		20 min
draft-tarapore-mboned-multicast-cdni-00		Sayko		10 min
AMT deployment experience			Sayko		10 min
draft-mcbride-armd-mcast-overview-02		McBride		10 min
draft-zhou-mboned-multrans-path-optimization-02	Zhou		10 min
draft-ietf-mboned-auto-multicast-14		Bumgardner	20 min

From tom.taylor.stds@gmail.com  Wed Jul 25 13:44:52 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 924AC21F86E5 for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 13:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.55
X-Spam-Level: 
X-Spam-Status: No, score=-3.55 tagged_above=-999 required=5 tests=[AWL=0.049,  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 05Nxv0fJaXT6 for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 13:44:51 -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 8531421F86E4 for <mboned@ietf.org>; Wed, 25 Jul 2012 13:44:51 -0700 (PDT)
Received: by bkty7 with SMTP id y7so773130bkt.31 for <mboned@ietf.org>; Wed, 25 Jul 2012 13:44:50 -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=+Eo7CV6PCLnnVxv4Ds5qhILEa2qD3MSPTIfL7hB/wKE=; b=p5gp50zttUBWwVglvH16aFfSKqcGxBLonc33YZoE4uWOcFx3BFzbuas87YI3B5yfVy 9UAuFCbeLg4SWwWGnQZ8OJRSiroGYvRPIFARU5QPxAhplIlqf7GFRCTY6qglSuSZP742 bkbjUTI1tytqYXCFmVqCD9JNhiP0NqEjMnSVvMEfWVNIaY35my2DQ3Unxf+E0pbLZ4Dn KH8qOX+zVTXdyP4KlXuwcQA2PhDFk8joqWSBwMAb+IRpdqHnBZ4pLCxn1s9bNhzRftoA b/vrEqLgerAXURM2f6zzDc1hTsN2EDhItCWDpE8U//o+yfaHfyPRCJWvE5XJtkU6P+l1 lkJg==
Received: by 10.205.119.208 with SMTP id fv16mr13049169bkc.100.1343249090592;  Wed, 25 Jul 2012 13:44:50 -0700 (PDT)
Received: from [127.0.0.1] (dsl-173-206-32-179.tor.primus.ca. [173.206.32.179]) by mx.google.com with ESMTPS id hg13sm13540871bkc.7.2012.07.25.13.44.48 (version=SSLv3 cipher=OTHER); Wed, 25 Jul 2012 13:44:50 -0700 (PDT)
Message-ID: <50105ABC.6080204@gmail.com>
Date: Wed, 25 Jul 2012 16:44:44 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Leonard Giuliano <lenny@juniper.net>
References: <20120725120437.P55680@eng-mail01.juniper.net>
In-Reply-To: <20120725120437.P55680@eng-mail01.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120725-0, 25/07/2012), Outbound message
X-Antivirus-Status: Clean
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] Vancouver Agenda
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, 25 Jul 2012 20:44:52 -0000

I trust Stig's presentation is the one he proposed regarding how to 
handle address mapping. If not, I'll be glad to work one up.

Could I have 10 minutes to point out the need for adaptation even with a 
dual stack network?\

Tom Taylor

On 25/07/2012 3:06 PM, Leonard Giuliano wrote:
>
> Here's what we have so far in terms of presenters.  Please let me know
> if I missed anyone.  Those of you presenting please send the chairs your
> slides by this Fri so we have ample time to upload for remote viewers.
>
>
> draft-kumar-mboned-64mcast-embedded-address-00    Stig        20 min
> draft-tarapore-mboned-multicast-cdni-00        Sayko        10 min
> AMT deployment experience            Sayko        10 min
> draft-mcbride-armd-mcast-overview-02        McBride        10 min
> draft-zhou-mboned-multrans-path-optimization-02    Zhou        10 min
> draft-ietf-mboned-auto-multicast-14        Bumgardner    20 min
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>

From stig@venaas.com  Wed Jul 25 15:01:57 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 A6ED921F86AA for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 15:01:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 AXWGV+3yxbdE for <mboned@ietfa.amsl.com>; Wed, 25 Jul 2012 15:01:56 -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 7FF6821F86A5 for <mboned@ietf.org>; Wed, 25 Jul 2012 15:01:56 -0700 (PDT)
Received: from [IPv6:2001:420:301:1004:48fd:6ab5:b50b:91cd] (unknown [IPv6:2001:420:301:1004:48fd:6ab5:b50b:91cd]) by ufisa.uninett.no (Postfix) with ESMTPSA id 512C87FB7 for <mboned@ietf.org>; Thu, 26 Jul 2012 00:01:53 +0200 (CEST)
Message-ID: <50106CCE.7000508@venaas.com>
Date: Wed, 25 Jul 2012 15:01:50 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: mboned@ietf.org
References: <20120725120437.P55680@eng-mail01.juniper.net> <50105ABC.6080204@gmail.com>
In-Reply-To: <50105ABC.6080204@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [MBONED] Vancouver Agenda
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, 25 Jul 2012 22:01:58 -0000

On 7/25/2012 1:44 PM, Tom Taylor wrote:
> I trust Stig's presentation is the one he proposed regarding how to
> handle address mapping. If not, I'll be glad to work one up.

Yes. I will try to talk about the different possible ways we can make
sure a translator (or other device) can know that an IPv4 address is
embedded, and the pros and cons of the different alternatives.

Including using a flag in the IP address, using a PIM join attribute,
using a well-known prefix, static configuration, out-of-band signaling.

Stig

> Could I have 10 minutes to point out the need for adaptation even with a
> dual stack network?\
>
> Tom Taylor
>
> On 25/07/2012 3:06 PM, Leonard Giuliano wrote:
>>
>> Here's what we have so far in terms of presenters.  Please let me know
>> if I missed anyone.  Those of you presenting please send the chairs your
>> slides by this Fri so we have ample time to upload for remote viewers.
>>
>>
>> draft-kumar-mboned-64mcast-embedded-address-00    Stig        20 min
>> draft-tarapore-mboned-multicast-cdni-00        Sayko        10 min
>> AMT deployment experience            Sayko        10 min
>> draft-mcbride-armd-mcast-overview-02        McBride        10 min
>> draft-zhou-mboned-multrans-path-optimization-02    Zhou        10 min
>> draft-ietf-mboned-auto-multicast-14        Bumgardner    20 min
>> _______________________________________________
>> 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 mohamed.boucadair@orange.com  Thu Jul 26 01:57:28 2012
Return-Path: <mohamed.boucadair@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 45E7F21F8732 for <mboned@ietfa.amsl.com>; Thu, 26 Jul 2012 01:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.228
X-Spam-Level: 
X-Spam-Status: No, score=-2.228 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 IiH2ivIzlg5k for <mboned@ietfa.amsl.com>; Thu, 26 Jul 2012 01:57:27 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC9321F870B for <mboned@ietf.org>; Thu, 26 Jul 2012 01:57:20 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id B82112DC11E; Thu, 26 Jul 2012 10:57:19 +0200 (CEST)
Received: from PUEXCH11.nanterre.francetelecom.fr (unknown [10.101.44.27]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 9EB9C4C06D; Thu, 26 Jul 2012 10:57:19 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.11]) by PUEXCH11.nanterre.francetelecom.fr ([10.101.44.27]) with mapi; Thu, 26 Jul 2012 10:57:13 +0200
From: <mohamed.boucadair@orange.com>
To: Stig Venaas <stig@venaas.com>, "mboned@ietf.org" <mboned@ietf.org>
Date: Thu, 26 Jul 2012 10:57:12 +0200
Thread-Topic: [MBONED] An alternative to draft-ietf-mboned-64-multicast-address-format?
Thread-Index: Ac1VePflMRgTWYABSG+RrQiH+Kir4AVkfKPg
Message-ID: <94C682931C08B048B7A8645303FDC9F36E4A17E2F7@PUEXCB1B.nanterre.francetelecom.fr>
References: <4FECD32D.30403@venaas.com>
In-Reply-To: <4FECD32D.30403@venaas.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.6.19.115414
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, 26 Jul 2012 08:57:28 -0000

Hi Stig, all,

The main purpose of draft-ietf-mboned-64-multicast-address-format is to spe=
cify the following:=20

* an address format to embed an IPv4 address into an IPv6 address
* how to extract an IPv4 address from an IPv4-embedded IPv6 multicast addre=
ss
=20
draft-ietf-mboned-64-multicast-address-format concludes that it is useful t=
o identify an IPv4-embedded IPv6 multicast address compared to a native IPv=
6 multicast address for the reasons listed in http://tools.ietf.org/html/dr=
aft-ietf-mboned-64-multicast-address-format-02#page-11.

Cheers,
Med

>-----Message d'origine-----
>De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org]=20
>De la part de Stig Venaas
>Envoy=E9 : jeudi 28 juin 2012 23:57
>=C0 : mboned@ietf.org
>Objet : [MBONED] An alternative to=20
>draft-ietf-mboned-64-multicast-address-format?
>
>The draft draft-ietf-mboned-64-multicast-address-format=20
>specifies as you
>know, a new flag to indicate that an IPv4 multicast address is=20
>embedded.
>This is useful for translators (and maybe other devices) that can then
>extract the IPv4 address and doing operations as needed on=20
>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 gjshep@gmail.com  Sun Jul 29 15:50:56 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 D667621F8628 for <mboned@ietfa.amsl.com>; Sun, 29 Jul 2012 15:50:55 -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 WKJm9iQ-Y-xQ for <mboned@ietfa.amsl.com>; Sun, 29 Jul 2012 15:50:55 -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 B75C321F8622 for <mboned@ietf.org>; Sun, 29 Jul 2012 15:50:54 -0700 (PDT)
Received: by bkty7 with SMTP id y7so2606742bkt.31 for <mboned@ietf.org>; Sun, 29 Jul 2012 15:50:53 -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; bh=wKY/2Y9hAfTln5/4lRBPq9l0oS8RjEbmB1WVIOvYU78=; b=OFH6IEIaEw7kLxCC2Qyn0Ct9BcMiIToUx6+mgTc8U89LKhmG99Ch6L846J2RoVcAmM DDUBEVH2WyNL2ZyCnO/XPLuezArrZS3mrjQxO92aYbWDxYYJxq+QNvYUKeu8MPbN7lZL Xr+d8YNz3O6fjktk6klieXNqYJdP118DqGXewj/HKffssy2/e9tDjlT2TqpRGGGo6yet I10Q5EPkvNB10UGKH70I/vnQm2AR+QMh/DevkyWoJ9rjaua+LX9XFNdLvGP7Ky/bpUia Xo7vlfIvZVfTL/BosM7DmiS+D30c20qJa5W1kDnpkSY7Hk9jr2FhimgTUs0/4Jtdr6PX wxBg==
MIME-Version: 1.0
Received: by 10.204.143.138 with SMTP id v10mr3237844bku.114.1343602253676; Sun, 29 Jul 2012 15:50:53 -0700 (PDT)
Received: by 10.204.170.76 with HTTP; Sun, 29 Jul 2012 15:50:53 -0700 (PDT)
Date: Sun, 29 Jul 2012 15:50:53 -0700
Message-ID: <CABFReBq++DeCMaTZzjjQjTsHnGi_7fXoeeRBDgQVFomyJMdADA@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
To: mboned@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [MBONED] FREE BEER at MBONED!
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: Sun, 29 Jul 2012 22:50:56 -0000

I'd like to ask now for a scribe. This is always a more difficult
process than it needs to be but if we can get a volunteer early then
we'll move right into the agenda in the morning.

Thanks,
Greg

From rbonica@juniper.net  Sun Jul 29 19:07:53 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 8B84B11E80F6 for <mboned@ietfa.amsl.com>; Sun, 29 Jul 2012 19:07:53 -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.026, 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 k9UxeItYmy+B for <mboned@ietfa.amsl.com>; Sun, 29 Jul 2012 19:07:53 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id ED4B711E8088 for <mboned@ietf.org>; Sun, 29 Jul 2012 19:07:52 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKUBXseOFi4s/w6YE0ZWYXOVkQSyVKhJaR@postini.com; Sun, 29 Jul 2012 19:07:52 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; Sun, 29 Jul 2012 19:07:42 -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; Sun, 29 Jul 2012 19:07:41 -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; Sun, 29 Jul 2012 22:07:40 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Sun, 29 Jul 2012 22:07:39 -0400
Thread-Topic: MBONED] FREE BEER at MBONED!
Thread-Index: Ac1t3KYyF/0l5gyRSF+Z0jZeUkZOSgAGy5Sg
Message-ID: <13205C286662DE4387D9AF3AC30EF456D770E60134@EMBX01-WF.jnpr.net>
References: <mailman.1457.1343602266.3364.mboned@ietf.org>
In-Reply-To: <mailman.1457.1343602266.3364.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] MBONED] FREE BEER at 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, 30 Jul 2012 02:07:53 -0000

Just to clarify, only the scribe gets free beer. Everybody else has to pay.

                                                      Ron


> Date: Sun, 29 Jul 2012 15:50:53 -0700
> From: Greg Shepherd <gjshep@gmail.com>
> To: mboned@ietf.org
> Subject: [MBONED] FREE BEER at MBONED!
> Message-ID:
> 	<CABFReBq++DeCMaTZzjjQjTsHnGi_7fXoeeRBDgQVFomyJMdADA@mail.gmail.c
> om>
> Content-Type: text/plain; charset=3DISO-8859-1
>=20
> I'd like to ask now for a scribe. This is always a more difficult
> process than it needs to be but if we can get a volunteer early then
> we'll move right into the agenda in the morning.
>=20
> Thanks,
> Greg
>=20


From lenny@juniper.net  Tue Jul 31 16:28:20 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 29BFF11E8165 for <mboned@ietfa.amsl.com>; Tue, 31 Jul 2012 16:28:20 -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 l7LK3MZQxR4X for <mboned@ietfa.amsl.com>; Tue, 31 Jul 2012 16:28:19 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 4B16311E8162 for <mboned@ietf.org>; Tue, 31 Jul 2012 16:28:19 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKUBhqEhprddhNpxZmo2dFAN4N0pHV6Jst@postini.com; Tue, 31 Jul 2012 16:28:19 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; Tue, 31 Jul 2012 16:27:31 -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 q6VNRVh38447	for <mboned@ietf.org>; Tue, 31 Jul 2012 16:27:31 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 4F1E011489;  Tue, 31 Jul 2012 16:27:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 43EE41144F	for <mboned@ietf.org>; Tue, 31 Jul 2012 16:27:31 -0700 (PDT)
Date: Tue, 31 Jul 2012 16:27:31 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
Message-ID: <20120731161725.D33047@eng-mail01.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Subject: [MBONED] Draft MBONED minutes
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, 31 Jul 2012 23:28:20 -0000

Thanks Tom T for taking minutes yesterday.  Please take a look and let us 
know if you see anything that should be added/subtracted/modified.



IETF 84 Vancouver
MBONED Agenda
Mon, July 30, 2012
9:00-11:30AM PT
Regency B

Status of WG items, recharter                    Chairs    15
draft-ietf-mboned-auto-multicast-14                Bumgardner    20
AMT deployment experience                    Sayko        10
draft-tarapore-mboned-multicast-cdni-00            Sayko        10
draft-mcbride-armd-mcast-overview-02            McBride    10
Need for Adaptation                        Taylor    10
draft-kumar-mboned-64mcast-embedded-address-00        Venaas    20
draft-zhou-mboned-multrans-path-optimization-02        Zhou  10

Meeting began at 9:00 am, Greg Shepherd and Lenny Giuliano presiding

Status
======

Lenny presented. Chart.
Small clarification on mcaddrdoc.

Recharter
---------

Transition: text proposed by Stig (chart) "Analyze the need for IPv4-IPv6 
multicast transitions solutions."

Will be posted on the list for comment.


draft-ietf-mboned-auto-multicast-14
===================================

Greg Bumgardner. Chart on status.

Status: WGLC completed, ready for submission to IESG.


AMT deployment experience (AT&T)
=========================

Bob Sayko. Charts.

Status since initial trial with on-line gaming. Have deployed to 12 sites 
(based on -09 version, will update).

Operational issue -- routing.

Lenny: have they begun MC peering with other ISPs? Not yet -- informal 
discussions in standards venues. Anyone interested send Bob an E-mail.

Interdomain multicast BCP draft
(draft-tarapore-mboned-multicast-cdni-00)
==========================

Bob Sayko again. Charts.

Greg Shepherd concerned that CDN-i Federation is passing up work central to 
their mandate. We'll see what the IESG says about this as a charter item, but 
there seems to be a failure of process.

Joel Jaeggli: CDNI has charter mandate for multicast, meaning it wouldn't be an 
IESG issue to do it in the IETF.

Two other comments in favour of MBoneD taking the work on.


draft-mcbride-armd-mcast-overview-02
=========================

Michael McBride. Charts.

Conflicting views on use of multicast in data centers in ARMD. Draft hopes 
to describe current uses and provide a taxonomy.

Comments: local multicast such as VRRP may or may not be suitable for scope. 
Tied into L2 domain size and capability.

Looking for mboned people to identify additional applications of multicast in 
data center. Would like draft to be work item.

Lenny: work does fall in charter.

Ron Bonica as individual. Really three questions to address. Took sense of room

-- not many readers, Mike to update the draft based on comments and take 
to list.


Need for Adaptation
=============

Tom Taylor. Charts.

Extensive discussion. Conclusion that Mboned is not in a position to support 
the related work in PIM but could be convinced if evidence appears that this is 
a real use case.


draft-kumar-mboned-64mcast-embedded-address-00
=================================

Stig Venaas. Charts.

Comment: Ron B as individual. Solved in unicast case by embedding in well-known 
prefix. Why not in multicast case? Stig: problems in inter-domain case.

Don't need to worry about this unless concerned with dynamic translation of 
ASM, either intra- or inter-domain.

Ron as AD: still needs to see people intending to use this before doing the 
work.

Greg: no use case for inter-domain ASM. Need to remember that source address 
also needs translation. Basically misleading the IETF as a whole if we continue 
to work on ASM solutions. Greg put question to the group. Some hands supporting 
statement that only SSM to be worked on in future. No hands for ASM, but 
qualified comment: will use what works.

Point made that home network will be locus for new multicast applications.


draft-zhou-mboned-multrans-path-optimization-02
===============================

Cathy Zhou. Charts.

Ron: part of the whole question of whether we want to work on the second 
scenario presented by Tom Taylor. Lenny agrees- this is an optimization 
for use cases that we have not yet agreed to work on.

Stig: usefulness depends on scenario -- scale a consideration.

Reprise from Tom Taylor presentation: multicast data packet translation. Note 
taken that this is work to be done, but need to refine the problem statement to 
determine exactly how the work items fall out.

Adjourned at 11:05.
