
From internet-drafts@ietf.org  Wed Jun  5 07:38:03 2013
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 5AD6421F9ABF; Wed,  5 Jun 2013 07:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=0.159, 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 TgSpQeqzPI40; Wed,  5 Jun 2013 07:38:02 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E3E21F9AB6; Wed,  5 Jun 2013 07:38:02 -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.50
Message-ID: <20130605143802.18895.13005.idtracker@ietfa.amsl.com>
Date: Wed, 05 Jun 2013 07:38:02 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-v4v6-mcast-ps-03.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: Wed, 05 Jun 2013 14:38:03 -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           : IPv4-IPv6 Multicast: Problem Statement and Use Cases
	Author(s)       : Christian Jacquenet
                          Mohamed Boucadair
                          Yiu Lee
                          Jacni Qin
                          Tina Tsou
                          Qiong Sun
	Filename        : draft-ietf-mboned-v4v6-mcast-ps-03.txt
	Pages           : 20
	Date            : 2013-06-05

Abstract:
   This document discusses issues and requirements raised by IPv4-IPv6
   multicast interconnection and co-existence scenarios.  It also
   discusses various multicast use cases which may occur during IPv6
   transitioning.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-v4v6-mcast-ps

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-v4v6-mcast-ps-03


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


From christian.jacquenet@orange.com  Wed Jun  5 07:39:54 2013
Return-Path: <christian.jacquenet@orange.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1BE21F89C3 for <mboned@ietfa.amsl.com>; Wed,  5 Jun 2013 07:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[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 7NIL4rE6GiAo for <mboned@ietfa.amsl.com>; Wed,  5 Jun 2013 07:39:50 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id C01EE21F9AB8 for <mboned@ietf.org>; Wed,  5 Jun 2013 07:39:49 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 70E6826491F for <mboned@ietf.org>; Wed,  5 Jun 2013 16:39:48 +0200 (CEST)
Received: from PUEXCH11.nanterre.francetelecom.fr (unknown [10.101.44.27]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 5373B35C045 for <mboned@ietf.org>; Wed,  5 Jun 2013 16:39:48 +0200 (CEST)
Received: from PUEXCB1C.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH11.nanterre.francetelecom.fr ([10.101.44.27]) with mapi; Wed, 5 Jun 2013 16:39:48 +0200
From: <christian.jacquenet@orange.com>
To: "MBONED WG (mboned@ietf.org)" <mboned@ietf.org>
Date: Wed, 5 Jun 2013 16:39:47 +0200
Thread-Topic: New Version Notification for draft-ietf-mboned-v4v6-mcast-ps-03.txt
Thread-Index: Ac5h+ks71G3Vp4sfR9OyIofSYqM5pQAABd4g
Message-ID: <5059_1370443188_51AF4DB4_5059_2547_1_983A1D8DA0DA5F4EB747BF34CBEE5CD15C3DA2DB9A@PUEXCB1C.nanterre.francetelecom.fr>
References: <20130605143803.18895.62211.idtracker@ietfa.amsl.com>
In-Reply-To: <20130605143803.18895.62211.idtracker@ietfa.amsl.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.6.5.34520
Subject: [MBONED] TR: New Version Notification for draft-ietf-mboned-v4v6-mcast-ps-03.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: Wed, 05 Jun 2013 14:39:54 -0000

V0csDQoNClRoaXMgdmVyc2lvbiBpbnRlZ3JhdGVzIFN0aWcncyBjb21tZW50cyBvZiBsYXRlIE1h
cmNoLg0KDQpDaGVlcnMsDQoNCkNocmlzdGlhbi4NCg0KLS0tLS1NZXNzYWdlIGQnb3JpZ2luZS0t
LS0tDQpEZcKgOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFm
dHNAaWV0Zi5vcmddIA0KRW52b3nDqcKgOiBtZXJjcmVkaSA1IGp1aW4gMjAxMyAxNjozOA0Kw4DC
oDogVGluYSBUc291OyBRaW9uZyBTdW47IEJPVUNBREFJUiBNb2hhbWVkIE9MTkMvT0xOOyBKQUNR
VUVORVQgQ2hyaXN0aWFuIE9MTkMvT0xOOyBUaW5hIFRzb3U7IFlpdSBMZWU7IEphY25pIFFpbg0K
T2JqZXTCoDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1pZXRmLW1ib25lZC12
NHY2LW1jYXN0LXBzLTAzLnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1pZXRm
LW1ib25lZC12NHY2LW1jYXN0LXBzLTAzLnR4dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1p
dHRlZCBieSBDaHJpc3RpYW4gSmFjcXVlbmV0IGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3Np
dG9yeS4NCg0KRmlsZW5hbWU6CSBkcmFmdC1pZXRmLW1ib25lZC12NHY2LW1jYXN0LXBzDQpSZXZp
c2lvbjoJIDAzDQpUaXRsZToJCSBJUHY0LUlQdjYgTXVsdGljYXN0OiBQcm9ibGVtIFN0YXRlbWVu
dCBhbmQgVXNlIENhc2VzDQpDcmVhdGlvbiBkYXRlOgkgMjAxMy0wNi0wNQ0KR3JvdXA6CQkgbWJv
bmVkDQpOdW1iZXIgb2YgcGFnZXM6IDIwDQpVUkw6ICAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0
Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtbWJvbmVkLXY0djYtbWNhc3QtcHMtMDMu
dHh0DQpTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQtaWV0Zi1tYm9uZWQtdjR2Ni1tY2FzdC1wcw0KSHRtbGl6ZWQ6ICAgICAgICBodHRwOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW1ib25lZC12NHY2LW1jYXN0LXBzLTAzDQpEaWZm
OiAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYt
bWJvbmVkLXY0djYtbWNhc3QtcHMtMDMNCg0KQWJzdHJhY3Q6DQogICBUaGlzIGRvY3VtZW50IGRp
c2N1c3NlcyBpc3N1ZXMgYW5kIHJlcXVpcmVtZW50cyByYWlzZWQgYnkgSVB2NC1JUHY2DQogICBt
dWx0aWNhc3QgaW50ZXJjb25uZWN0aW9uIGFuZCBjby1leGlzdGVuY2Ugc2NlbmFyaW9zLiAgSXQg
YWxzbw0KICAgZGlzY3Vzc2VzIHZhcmlvdXMgbXVsdGljYXN0IHVzZSBjYXNlcyB3aGljaCBtYXkg
b2NjdXIgZHVyaW5nIElQdjYNCiAgIHRyYW5zaXRpb25pbmcuDQoNCiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICANCg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQoKX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKQ2UgbWVzc2Fn
ZSBldCBzZXMgcGllY2VzIGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25z
IGNvbmZpZGVudGllbGxlcyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBl
dHJlIGRpZmZ1c2VzLCBleHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2
b3VzIGF2ZXogcmVjdSBjZSBtZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVy
CmEgbCdleHBlZGl0ZXVyIGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50
ZXMuIExlcyBtZXNzYWdlcyBlbGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVy
YXRpb24sCkZyYW5jZSBUZWxlY29tIC0gT3JhbmdlIGRlY2xpbmUgdG91dGUgcmVzcG9uc2FiaWxp
dGUgc2kgY2UgbWVzc2FnZSBhIGV0ZSBhbHRlcmUsIGRlZm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNp
LgoKVGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMgbWF5IGNvbnRhaW4gY29uZmlkZW50
aWFsIG9yIHByaXZpbGVnZWQgaW5mb3JtYXRpb24gdGhhdCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxh
dzsKdGhleSBzaG91bGQgbm90IGJlIGRpc3RyaWJ1dGVkLCB1c2VkIG9yIGNvcGllZCB3aXRob3V0
IGF1dGhvcmlzYXRpb24uCklmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3Is
IHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRz
IGF0dGFjaG1lbnRzLgpBcyBlbWFpbHMgbWF5IGJlIGFsdGVyZWQsIEZyYW5jZSBUZWxlY29tIC0g
T3JhbmdlIGlzIG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVk
LCBjaGFuZ2VkIG9yIGZhbHNpZmllZC4KVGhhbmsgeW91LgoK

From stig@venaas.com  Wed Jun  5 11:11:33 2013
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 2CDBF21F9A69; Wed,  5 Jun 2013 11:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  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 Dlt3XMIa+tF8; Wed,  5 Jun 2013 11:11:32 -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 06F0821F9A30; Wed,  5 Jun 2013 11:11:32 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 38A0F84BB; Wed,  5 Jun 2013 20:11:28 +0200 (CEST)
Message-ID: <51AF7F4E.605@venaas.com>
Date: Wed, 05 Jun 2013 11:11:26 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Toerless Eckert <eckert@cisco.com>
References: <20130511182540.GV12184@cisco.com> <51912101.1090002@venaas.com>
In-Reply-To: <51912101.1090002@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ah@TR-Sys.de, bcain99@gmail.com, holbrook@arastra.com, mboned@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pim@ietf.org
Subject: Re: [MBONED] [pim] Trying to clean-up an SSM Errata Report
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, 05 Jun 2013 18:11:33 -0000

On 5/13/2013 10:21 AM, Stig Venaas wrote:
> Hi
>
> On 5/11/2013 11:25 AM, Toerless Eckert wrote:
>> Let me add mboned and the author of said errata.
>>
>> The author of this errata seems to claim inconsistency between 4607 and
>> prior addressing standards (RFC3307, RFC4291). He also states: "I'm
>> sure that
>> RFC 4291 should NOT be called in question.". This to me implies that
>> he is asking
>> to have RFC4607 updated to remove these conflicts in RFC4607bis.
>
> Med (copied) and I are trying to get some of these issues resolved, we
> have one draft (draft-ietf-6man-multicast-addr-arch-update) that will
> try to clarify and resolve some conflicts. We intent to discuss some of
> these SSM issues mentioned here as well. We will probably both on the
> list and in the next IETF meeting try to discuss some of these issues.
>
> We've been focusing on how the flag bits are used, and one of the cases
> is the use of the transient flag and SSM.

We now have a new version of the draft that suggests some major changes,
e.g. what is an SSM address (including ff2x::/32 for IANA allocations).
It would be great if you can see if this addresses the errata, and also
whether it makes sense in general.

The latest version is at
http://tools.ietf.org/html/draft-ietf-6man-multicast-addr-arch-update-01

Stig

> Perhaps this thread is a good opportunity to move forward on this topic.
> One question in particular, is whether the T bit should be allowed to be
> 0 for SSM, and whether the IANA SSM assignments (non-yet) should have
> T=0.
>
> Stig
>
>> IMHO:
>>
>> I have not been able to (in)validate the erratas author claims wrt. to
>> the interpretation of the prior RFCs. I hope others on the lists can
>> chime
>> in. Assuming he is right on one or the other accounts:
>>
>> I would like to see a resolution that minimizes actual
>> deployment/interoperability
>> problems.
>>
>> Withdrawing address ranges deemed to be useable according to existing
>> RFC4607
>> in an upcoming RFC4607bis definitely has the potentialy to create mayor
>> disturbances in deployments relying on those addresses. If MBoned can
>> clearly
>> identify affected ranges known not to be deployed at all, then they
>> could be
>> redesignated, otherwise IMHO not.
>>
>> I have not seen any example of actual deployment/interoperability issues
>> from the incompatibility of existing RFC4607 and its claimed conflicts
>> with prior address architectures. It would be good if the author of
>> the errata
>> (or someone else) could provide some example of such breakage.
>>
>> If no real breakage could reasonably be claimed, i think RFC4607bis
>> should
>> grandfather in the ranges from RFC4607 and explain how we derived at
>> them,
>> and that they constitute unfortunate, but not caught violations of
>> principle due to the a) human nature, b) IETF process or c) the
>> complexity
>> of the IPv6 address architecture. And grandfathering is not the same as
>> questioning RFC4291.
>>
>> Cheers
>>      Toerless
>>
>> On Sat, May 11, 2013 at 05:36:53PM +0100, Adrian Farrel wrote:
>>> Hi,
>>>
>>> Take a look at http://www.rfc-editor.org/errata_search.php?eid=905
>>>
>>> I can't make head or tail of what the appropriate resolution is.
>>> Advice please.
>>>
>>> And any ideas if there is a better place to discuss this.
>>>
>>> Thanks,
>>> Adrian
>>>
>>> _______________________________________________
>>> pim mailing list
>>> pim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pim
>> _______________________________________________
>> pim mailing list
>> pim@ietf.org
>> https://www.ietf.org/mailman/listinfo/pim
>>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From lenny@juniper.net  Fri Jun 28 13:47:27 2013
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 624C721F9CD8 for <mboned@ietfa.amsl.com>; Fri, 28 Jun 2013 13:47: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=[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 e28dAsmMa-2S for <mboned@ietfa.amsl.com>; Fri, 28 Jun 2013 13:47:21 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe002.messaging.microsoft.com [65.55.88.12]) by ietfa.amsl.com (Postfix) with ESMTP id 8F03C21F9CD7 for <mboned@ietf.org>; Fri, 28 Jun 2013 13:47:21 -0700 (PDT)
Received: from mail82-tx2-R.bigfish.com (10.9.14.254) by TX2EHSOBE009.bigfish.com (10.9.40.29) with Microsoft SMTP Server id 14.1.225.23; Fri, 28 Jun 2013 20:47:20 +0000
Received: from mail82-tx2 (localhost [127.0.0.1])	by mail82-tx2-R.bigfish.com (Postfix) with ESMTP id AA822440277	for <mboned@ietf.org>; Fri, 28 Jun 2013 20:47:20 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.50; KIP:(null); UIP:(null); IPV:NLI; H:P-EMHUB01-HQ.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: 1
X-BigFish: VPS1(zzc430I4015Izz1f42h1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kzzz2fh2a8h668h839h944hd25hf0ah11b5h121eh1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1d0ch1d2eh1d3fh1dc1h1de2h1dfeh1dffh1155h)
Received-SPF: pass (mail82-tx2: domain of juniper.net designates 66.129.224.50 as permitted sender) client-ip=66.129.224.50; envelope-from=lenny@juniper.net; helo=P-EMHUB01-HQ.jnpr.net ; -HQ.jnpr.net ; 
Received: from mail82-tx2 (localhost.localdomain [127.0.0.1]) by mail82-tx2 (MessageSwitch) id 1372452438416265_18274; Fri, 28 Jun 2013 20:47:18 +0000 (UTC)
Received: from TX2EHSMHS041.bigfish.com (unknown [10.9.14.244])	by mail82-tx2.bigfish.com (Postfix) with ESMTP id 5846D400076	for <mboned@ietf.org>; Fri, 28 Jun 2013 20:47:18 +0000 (UTC)
Received: from P-EMHUB01-HQ.jnpr.net (66.129.224.50) by TX2EHSMHS041.bigfish.com (10.9.99.141) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 28 Jun 2013 20:47:18 +0000
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; Fri, 28 Jun 2013 13:47:17 -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 r5SKlFL23486	for <mboned@ietf.org>; Fri, 28 Jun 2013 13:47:16 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id D499D11446;  Fri, 28 Jun 2013 13:47:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id C45771141B	for <mboned@ietf.org>; Fri, 28 Jun 2013 13:47:14 -0700 (PDT)
Date: Fri, 28 Jun 2013 13:47:14 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
Message-ID: <20130628134438.M87709@eng-mail01.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
X-OriginatorOrg: juniper.net
Subject: [MBONED] Call for agenda items in MBONED in Berlin
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, 28 Jun 2013 20:47:27 -0000

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

The preliminary WG agenda has been posted and we are currently scheduled 
for Tues, 1700-1830.  This is of course subject to change at this point.


Thanks,
MBoned Chairs


From adurand@juniper.net  Fri Jun 28 14:54:18 2013
Return-Path: <adurand@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 8852C21F9D19 for <mboned@ietfa.amsl.com>; Fri, 28 Jun 2013 14:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.466
X-Spam-Level: 
X-Spam-Status: No, score=-99.466 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, UNRESOLVED_TEMPLATE=3.132,  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 LUHG5sdWSPG9 for <mboned@ietfa.amsl.com>; Fri, 28 Jun 2013 14:53:55 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0184.outbound.messaging.microsoft.com [213.199.154.184]) by ietfa.amsl.com (Postfix) with ESMTP id 567ED21F9CF2 for <mboned@ietf.org>; Fri, 28 Jun 2013 14:53:54 -0700 (PDT)
Received: from mail192-db8-R.bigfish.com (10.174.8.242) by DB8EHSOBE037.bigfish.com (10.174.4.100) with Microsoft SMTP Server id 14.1.225.23; Fri, 28 Jun 2013 21:53:53 +0000
Received: from mail192-db8 (localhost [127.0.0.1])	by mail192-db8-R.bigfish.com (Postfix) with ESMTP id 0F88AC02F5	for <mboned@ietf.org>; Fri, 28 Jun 2013 21:53:53 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.51; KIP:(null); UIP:(null); IPV:NLI; H:P-EMHUB01-HQ.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: 0
X-BigFish: VPS0(zzc85fhzz1f42h1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz18c673h8275bhz2fh2a8h683h839hbe3hd25he5bhf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1bceh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1155h)
Received-SPF: pass (mail192-db8: domain of juniper.net designates 66.129.224.51 as permitted sender) client-ip=66.129.224.51; envelope-from=adurand@juniper.net; helo=P-EMHUB01-HQ.jnpr.net ; -HQ.jnpr.net ; 
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT003.namprd05.prod.outlook.com; R:internal; EFV:INT
Received: from mail192-db8 (localhost.localdomain [127.0.0.1]) by mail192-db8 (MessageSwitch) id 1372456429766492_28022; Fri, 28 Jun 2013 21:53:49 +0000 (UTC)
Received: from DB8EHSMHS004.bigfish.com (unknown [10.174.8.225])	by mail192-db8.bigfish.com (Postfix) with ESMTP id B6C58400046	for <mboned@ietf.org>; Fri, 28 Jun 2013 21:53:49 +0000 (UTC)
Received: from P-EMHUB01-HQ.jnpr.net (66.129.224.51) by DB8EHSMHS004.bigfish.com (10.174.4.14) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 28 Jun 2013 21:53:49 +0000
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 28 Jun 2013 14:53:47 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Fri, 28 Jun 2013 14:53:46 -0700
Received: from co1outboundpool.messaging.microsoft.com (216.32.180.188) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 28 Jun 2013 14:57:56 -0700
Received: from mail70-co1-R.bigfish.com (10.243.78.229) by CO1EHSOBE010.bigfish.com (10.243.66.73) with Microsoft SMTP Server id 14.1.225.23; Fri, 28 Jun 2013 21:53:45 +0000
Received: from mail70-co1 (localhost [127.0.0.1])	by mail70-co1-R.bigfish.com (Postfix) with ESMTP id 35C3B240272	for <mboned@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 28 Jun 2013 21:53:45 +0000 (UTC)
Received: from mail70-co1 (localhost.localdomain [127.0.0.1]) by mail70-co1 (MessageSwitch) id 1372456422248761_11282; Fri, 28 Jun 2013 21:53:42 +0000 (UTC)
Received: from CO1EHSMHS015.bigfish.com (unknown [10.243.78.250])	by mail70-co1.bigfish.com (Postfix) with ESMTP id 314B24C004D	for <mboned@ietf.org>; Fri, 28 Jun 2013 21:53:42 +0000 (UTC)
Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by CO1EHSMHS015.bigfish.com (10.243.66.25) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 28 Jun 2013 21:53:42 +0000
Received: from BL2PRD0510MB386.namprd05.prod.outlook.com ([169.254.11.77]) by BL2PRD0510HT003.namprd05.prod.outlook.com ([10.255.100.38]) with mapi id 14.16.0324.000; Fri, 28 Jun 2013 21:53:35 +0000
From: Alain Durand <adurand@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: Comments on draft-ietf-mboned-v4v6-mcast-ps-02
Thread-Index: AQHOdEnwmm5PwAzUkkKjRu27N+iNfw==
Date: Fri, 28 Jun 2013 21:53:35 +0000
Message-ID: <A7AA8F6D-4AB1-400A-A27B-6F04A26A08EA@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.100.4]
Content-Type: multipart/alternative; boundary="_000_A7AA8F6D4AB1400AA27B6F04A26A08EAjunipernet_"
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: [MBONED] Comments on draft-ietf-mboned-v4v6-mcast-ps-02
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jun 2013 21:54:18 -0000

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

Dear wg,

Here are comments on draft-ietf-mboned-v4v6-mcast-ps-02

Alain.


1. Introduction


   The rarefaction of global IPv4 addresses may indeed affect the
   multicast delivery of IPv4-formatted contents to IPv4 receivers.  For
   example, the observed evolution of ADSL broadband access
   infrastructures from a service-specific, multi-PVC (Permanent Virtual
   Circuit) scheme towards a "service-agnostic", single PVC scheme,
   assumes the allocation of a globally unique IPv4 address on the WAN
   (Wide Area Network) interface of the CPE (Customer Premises
   Equipment), or to a mobile terminal), whatever the number and the
   nature of the services the customer has subscribed to.


=3D=3D> In many cases, multicast is used solely for IP-TV class solutions a=
nd its scope is limited to the service provider network.
        Hence, global IPv4 addresses on the CPE are not necessary, private =
IPv4 addresses can be used to deliver this service.


  Likewise, the global IPv4 address depletion encourages the
   development of IPv6 receivers while contents may very well remain
   IPv4-formatted

=3D=3D> I do not understand what IPv4 formatted means. Does it mean sourced=
 by an IPv4-only application? If so, say it.


   o  The current design of some multicast-based services like TV
      broadcasting often relies upon the use of a private IPv4
      addressing scheme because of a walled garden approach.  Privately-
      addressed IGMP [RFC2236][RFC3376] traffic sent by IPv4 receivers
      is generally forwarded over a specific (e.g., "IPTV") PVC towards
      an IGMP Querier located in the access infrastructure, e.g., in
      some deployments it is hosted by a BRAS (BRoadband Access Server)
      device that is the PPP (Point-to-Point Protocol) session endpoint
      and which may also act as a PIM DR (Protocol Independent Multicast
      Designated Router)[RFC4601].  This design does not suffer from
      global IPv4 address depletion by definition (since multicast
      traffic relies upon the use of a private IPv4 addressing scheme),
      but it is inconsistent with migrating the access infrastructure
      towards a publicly-addressed single PVC design scheme.


=3D=3D> This is somehow echoing the point I made earlier: technically, you =
can
        do this with private IPv4 addresses. If you choose not too for othe=
r reasons,
        this is another story.  So this all section should be rewritten to =
explain
        that the problem statement ONLY applies to cases where the ISP has =
decided
        for whatever reasons to NOT deploy private IPv4 addresses.


   o  Likewise, other deployments (e.g., cable operators' environments)
      rely upon the public CPE's address for multicast delivery and will
      therefore suffer from IPv4 address depletion

=3D=3D> I don't understand this statement.



=3D=3D> KEY POINT: the underlying assumption in that introduction is that t=
he access network will be IPv6-only.
        I'm OK with that assumption, but it needs to be stated clearly as t=
here are other ways to deal with
        IPv4 address exhaustion (for example private IPv4 + CGN, with or wi=
thout IPv6), for which the rest of
       document may or may not apply.



2.2.  Service Requirements

o  Optimize bandwidth.  Contents should not be multicast twice (i.e.,
      using both versions of IP) to optimize bandwidth usage.  Injecting
      multicast content using both IPv4 and IPv6 raises some
      dimensioning issues that should be carefully evaluated by service
      providers during network planning operations.  For instance, if
      only few IPv6-enabled receivers are in use, it can be more
      convenient to convey multicast traffic over IPv4 rather than
      doubling the consumed resources for few users.  IPv4/IPv6 co-
      existence solutions should be designed to optimize network
      resource utilization.

=3D=3D> CRITICAL: If I follow the logic here and I make the assumption that=
 IPv4-only receivers will NEVER go away,
        them we are stuck forever using IPv4 multicast on the last mile!!!

        This is a VERY serious issue here, and I consider it a show stopper=
, unless there is a way to
        completely segregate CPEs that are multicast IPv6 capable and put t=
hem into a completely different
        infrastructure than those who are not. Even if you were to use a si=
ngle vlan per subscriber,
        can you guarantee that you know exactly if that subscriber CPE is m=
ulticast IPv6 capable or not?
        Maybe you can in some environments and not in others.

        Further more, if you have a mix of multicast v6 subscriber and mult=
icast v4 subscriber, what do you want
        to use as a protocol on the edge network? Are you OK to double the =
bandwidth there or not?
        This is the CORE issue the document should expand on, explaining wh=
en and where it is OK
        to send both v4 multicast and v6 multicast and where it is not. Tex=
t like "content should not be multicast twice"
        is nice and well, but feels a bit like hand waving.

--_000_A7AA8F6D4AB1400AA27B6F04A26A08EAjunipernet_
Content-Type: text/html; charset="us-ascii"
Content-ID: <C1B083A4164FAB4FA9FD021C7503FE38@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div><font face=3D"Arial">Dear wg,</font></div>
<div><font face=3D"Arial"><br>
</font></div>
<div><font face=3D"Arial">Here are comments on&nbsp;</font><span style=3D"f=
ont-size: 12px; ">draft-ietf-mboned-v4v6-mcast-ps-02</span></div>
<div><span style=3D"font-family: Arial; "><br>
</span></div>
<div><span style=3D"font-family: Arial; ">Alain.</span></div>
<div><span style=3D"font-family: Arial; "><br>
</span></div>
<div><span style=3D"font-family: Arial; "><br>
</span></div>
<div><span style=3D"font-family: Arial; ">1. Introduction</span></div>
<div><font face=3D"Arial"><br>
</font></div>
<div>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><font face=3D=
"Arial">   The rarefaction of global IPv4 addresses may indeed affect the
   multicast delivery of IPv4-formatted contents to IPv4 receivers.  For
   example, the observed evolution of ADSL broadband access
   infrastructures from a service-specific, multi-PVC (Permanent Virtual
   Circuit) scheme towards a &quot;service-agnostic&quot;, single PVC schem=
e,
   assumes the allocation of a globally unique IPv4 address on the WAN
   (Wide Area Network) interface of the CPE (Customer Premises
   Equipment), or to a mobile terminal), whatever the number and the
   nature of the services the customer has subscribed to.
</font></pre>
</div>
<div><font face=3D"Arial"><br>
</font></div>
<div><font face=3D"Arial">=3D=3D&gt; In many cases, multicast is used solel=
y for IP-TV class solutions and its scope is limited to the service provide=
r network.</font></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; Hence, global IPv4 ad=
dresses on the CPE are not necessary, private IPv4 addresses can be used to=
 deliver this service.</font></div>
<div><font face=3D"Arial"><br>
</font></div>
<div>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><font face=3D=
"Arial">  Likewise, the global IPv4 address depletion encourages the
   development of IPv6 receivers while contents may very well remain
   IPv4-formatted</font></pre>
<div><font face=3D"Arial"><br>
</font></div>
</div>
<div><font face=3D"Arial">=3D=3D&gt; I do not understand what IPv4 formatte=
d means. Does it mean sourced by an IPv4-only application? If so, say it.</=
font></div>
<div><font face=3D"Arial"><br>
</font></div>
<div>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><font face=3D=
"Arial">   o  The current design of some multicast-based services like TV
      broadcasting often relies upon the use of a private IPv4
      addressing scheme because of a walled garden approach.  Privately-
      addressed IGMP [RFC2236][RFC3376] traffic sent by IPv4 receivers
      is generally forwarded over a specific (e.g., &quot;IPTV&quot;) PVC t=
owards
      an IGMP Querier located in the access infrastructure, e.g., in
      some deployments it is hosted by a BRAS (BRoadband Access Server)
      device that is the PPP (Point-to-Point Protocol) session endpoint
      and which may also act as a PIM DR (Protocol Independent Multicast
      Designated Router)[RFC4601].  This design does not suffer from
      global IPv4 address depletion by definition (since multicast
      traffic relies upon the use of a private IPv4 addressing scheme),
      but it is inconsistent with migrating the access infrastructure
      towards a publicly-addressed single PVC design scheme.</font></pre>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><font face=3D=
"Arial"><br></font></pre>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><font face=3D=
"Arial">=3D=3D&gt; This is somehow echoing the point I made earlier: techni=
cally, you can
</font><span style=3D"font-family: Arial; ">        do this with private IP=
v4 addresses. If you choose not too for other reasons,
</span><span style=3D"font-family: Arial; ">        this is another story. =
 So this all section should be rewritten to explain
</span><span style=3D"font-family: Arial; ">        that the problem statem=
ent ONLY applies to cases where the ISP has decided
</span><span style=3D"font-family: Arial; ">        for whatever reasons to=
 NOT deploy private IPv4 addresses.</span></pre>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><font face=3D=
"Arial">
   o  Likewise, other deployments (e.g., cable operators' environments)
      rely upon the public CPE's address for multicast delivery and will
      therefore suffer from IPv4 address depletion</font></pre>
</div>
<div><font face=3D"Arial">=3D=3D&gt; I don't understand this statement.</fo=
nt></div>
<div><font face=3D"Arial"><br>
</font></div>
<div><font face=3D"Arial"><br>
</font></div>
<div><br>
</div>
<div><font face=3D"Arial">=3D=3D&gt; KEY POINT: the underlying assumption i=
n that introduction is that the access network will be IPv6-only.</font></d=
iv>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; I'm OK with that assu=
mption, but it needs to be stated clearly as there are other ways to deal w=
ith</font></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; IPv4 address exhausti=
on (for example private IPv4 &#43; CGN, with or without IPv6), for which th=
e rest of</font></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp;document may or may no=
t apply.</font></div>
<div><font face=3D"Arial"><br>
</font></div>
<div><font face=3D"Arial"><br>
</font></div>
<div>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><font face=3D=
"Arial">2.2.  Service Requirements</font></pre>
<div>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><font face=3D=
"Arial">o  Optimize bandwidth.  Contents should not be multicast twice (i.e=
.,
      using both versions of IP) to optimize bandwidth usage.  Injecting
      multicast content using both IPv4 and IPv6 raises some
      dimensioning issues that should be carefully evaluated by service
      providers during network planning operations.  For instance, if
      only few IPv6-enabled receivers are in use, it can be more
      convenient to convey multicast traffic over IPv4 rather than
      doubling the consumed resources for few users.  IPv4/IPv6 co-
      existence solutions should be designed to optimize network
      resource utilization.</font></pre>
<div><font face=3D"Arial"><br>
</font></div>
</div>
</div>
<div><font face=3D"Arial">=3D=3D&gt; CRITICAL: If I follow the logic here a=
nd I make the assumption that IPv4-only receivers will NEVER go away,</font=
></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; them we are stuck for=
ever using IPv4 multicast on the last mile!!!</font></div>
<div><font face=3D"Arial"><br>
</font></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; This is a VERY seriou=
s issue here, and I consider it a show stopper, unless there is a way to</f=
ont></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; completely segregate =
CPEs that are multicast IPv6 capable and put them into a completely differe=
nt</font></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; infrastructure than t=
hose who are not.</font><span style=3D"font-family: Arial; ">&nbsp;Even if =
you were to use a single vlan per subscriber,</span></div>
<div><span style=3D"font-family: Arial; ">&nbsp; &nbsp; &nbsp; &nbsp; can y=
ou guarantee that you know exactly if that&nbsp;</span><span style=3D"font-=
family: Arial; ">subscriber CPE is multicast IPv6 capable or not?</span></d=
iv>
<div><span style=3D"font-family: Arial; ">&nbsp; &nbsp; &nbsp; &nbsp; Maybe=
 you can in some environments and not in others.</span></div>
<div><span style=3D"font-family: Arial; "><br>
</span></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; Further more, if you =
have a mix of multicast v6 subscriber and multicast v4 subscriber, what do =
you want</font></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; to use as a protocol =
on the edge network? Are you OK to double the bandwidth there or not?</font=
></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; This is the CORE issu=
e the document should expand on, explaining when and where it is OK</font><=
/div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; to send both v4 multi=
cast and v6 multicast and where it is not. Text like &quot;content should n=
ot be multicast twice&quot;</font></div>
<div><font face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; is nice and well, but=
 feels a bit like hand waving.</font></div>
</body>
</html>

--_000_A7AA8F6D4AB1400AA27B6F04A26A08EAjunipernet_--
