
From christian.jacquenet@orange.com  Mon Jul  1 05:27:58 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 889FC11E82B5 for <mboned@ietfa.amsl.com>; Mon,  1 Jul 2013 05:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.007
X-Spam-Level: 
X-Spam-Status: No, score=-1.007 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, SARE_LWSHORTT=1.24, 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 ydaZCYBWFTir for <mboned@ietfa.amsl.com>; Mon,  1 Jul 2013 05:27:51 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 5FADC11E82C0 for <mboned@ietf.org>; Mon,  1 Jul 2013 05:26:46 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 9AD182645CC; Mon,  1 Jul 2013 14:26:44 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 7ED9D4C015; Mon,  1 Jul 2013 14:26:44 +0200 (CEST)
Received: from PUEXCB1C.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Mon, 1 Jul 2013 14:26:44 +0200
From: <christian.jacquenet@orange.com>
To: Alain Durand <adurand@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
Date: Mon, 1 Jul 2013 14:26:43 +0200
Thread-Topic: Comments on draft-ietf-mboned-v4v6-mcast-ps-02
Thread-Index: AQHOdEnwmm5PwAzUkkKjRu27N+iNf5lPt1Fw
Message-ID: <1965_1372681604_51D17584_1965_407_1_983A1D8DA0DA5F4EB747BF34CBEE5CD15C435E95C4@PUEXCB1C.nanterre.francetelecom.fr>
References: <A7AA8F6D-4AB1-400A-A27B-6F04A26A08EA@juniper.net>
In-Reply-To: <A7AA8F6D-4AB1-400A-A27B-6F04A26A08EA@juniper.net>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_983A1D8DA0DA5F4EB747BF34CBEE5CD15C435E95C4PUEXCB1Cnante_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.6.28.101520
Subject: Re: [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: Mon, 01 Jul 2013 12:27:59 -0000

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

Bonjour Alain,

Thanks for the feedback - please see inline.

[snip]

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.
[CJ] This is precisely the point of the above text. Most of IPTV services a=
re currently designed according to a typical private IPv4 address-based wal=
led garden approach, as you rightfully mention. Such environments usually r=
ely upon an IPTV service-specific PVC, while other traffic (internet, voice=
) is conveyed over different PVCs that remain service-specific. Some operat=
ors are moving from this service-specific, multi-PVC design to a service-ag=
nostic, single PVC design, whatever the number and the nature of the servic=
es subscribed by the customer. In that case, an RFC1918-based walled garden=
 IPTV service design is hard to deploy, as corresponding customers rarely s=
ubscribe to an IPTV service only.


  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.
[CJ] Fair enough.


   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.

[CJ] We cannot restrict the scope of the problem statement to this sole use=
 case, because of the other contexts documented in Section 3.



   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.
[CJ] The CPE is assigned a global IPv4 address. In some environments, this =
address is used for multicast delivery purposes. As a consequence, global I=
Pv4 address depletion may jeopardize the delivery of such services, but I'l=
l let cable representatives further elaborate.



=3D=3D> KEY POINT: the underlying assumption in that introduction is that t=
he access network will be IPv6-only.
[CJ] This should indeed be consistent with a global IPv6 strategy that not =
only relates to Internet services, but also the whole service portfolio of =
an operator, IPTV services included.
        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.
[CJ] Agreed, but please keep in mind this is a problem statement that tries=
 to illustrate contexts where multicast transition techniques may be worth =
the investigation (Section 3). As such, what has been documented in this se=
ction 3 reflects the situation of some of the operators who have co-authore=
d this draft.



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!!!
[CJ] The assumption you make looks a bit strong to me as current SoA seems =
to indicate that Dual Stack committed roadmaps are being specified by the S=
TB vendor industry. The point is to make IPv6 the rule, not the exception e=
ven in typical IPTV service environments. Admittedly, the hardest part is t=
hat current IPTV contents are unlikely to be IPv6 multicast in the short te=
rm.

        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.
[CJ] That would be an easy answer for service providers who provide managed=
 CPEs, obviously (and who master the functional evolution of such CPEs). In=
 case a customer wants to use an off-the-shelf CPE, he/she usually has to m=
ake sure the said CPE complies with the service specifications published by=
 the provider. And this is clearly not IPTV-specific or multicast-specific.

        Furthermore, if you have a mix of multicast v6 subscriber and multi=
cast 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?
[CJ] The mix you mention can reasonably assume the receivers will be DS-ena=
bled, right? But the answer to your question obviously depends on the "form=
at" of the application (IPv4-only content, DS content) and the service prov=
ider's IPv6 strategy, which brings us back to one of your previous points. =
I know some operators privilege IPv6 as the "transport" protocol, regardles=
s of the nature of the services subscribed by the customer, which, in the c=
ase of IPTV for example, would ideally assume IPv6-enabled receivers and, m=
ore importantly, IPv6-formatted contents. Unfortunately, we're not at this =
stage yet. Meaning that for those operators, they either have to (1) stick =
to a typical walled garden design (possibly at the cost of *also* running o=
ut of private IPv4 addresses in a not so distant future (given mobile data =
growth, for example) or (2) investigate multicast transition techniques, su=
ch as the one documented in http://tools.ietf.org/html/draft-ietf-softwire-=
dslite-multicast-05.
        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.
CJ: In that case, I don't think this is a problem statement document anymor=
e. Besides, this kind of recommendation is likely to be dependent on the se=
rvice provider environment, given the nature of the multicast service to be=
 delivered, the foreseen business growth as a function of the market covera=
ge, the network capabilities, etc.

Cheers,

Christian.

___________________________________________________________________________=
______________________________________________

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

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


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:#7030A0;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:#7030A0'>Bonjour Alain,<o:p=
></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font=
-family:"Courier New";color:#7030A0'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:#7030A0'>Thanks for the feedback &#8211; please see inline.<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"C=
ourier New";color:#7030A0'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoN=
ormal style=3D'margin-left:36.0pt'><b><span style=3D'font-size:10.0pt;font-=
family:"Tahoma","sans-serif";color:#7030A0'>[snip]</span></b><o:p></o:p></p=
></div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><o:p>&nbsp;</=
o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><span =
style=3D'font-family:"Arial","sans-serif"'>1. Introduction</span><o:p></o:p=
></p></div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><o:p>&nbs=
p;</o:p></p></div><div><pre style=3D'margin-left:36.0pt;word-wrap: break-wo=
rd;white-space:pre-wrap'><span style=3D'font-family:"Arial","sans-serif"'>&=
nbsp;&nbsp; The rarefaction of global IPv4 addresses may indeed affect the<=
o:p></o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'fon=
t-family:"Arial","sans-serif"'>&nbsp;&nbsp; multicast delivery of IPv4-form=
atted contents to IPv4 receivers.&nbsp; For<o:p></o:p></span></pre><pre sty=
le=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>=
&nbsp;&nbsp; example, the observed evolution of ADSL broadband access<o:p><=
/o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'font-fam=
ily:"Arial","sans-serif"'>&nbsp;&nbsp; infrastructures from a service-speci=
fic, multi-PVC (Permanent Virtual<o:p></o:p></span></pre><pre style=3D'marg=
in-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbs=
p; Circuit) scheme towards a &quot;service-agnostic&quot;, single PVC schem=
e,<o:p></o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'=
font-family:"Arial","sans-serif"'>&nbsp;&nbsp; assumes the allocation of a =
globally unique IPv4 address on the WAN<o:p></o:p></span></pre><pre style=
=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&n=
bsp;&nbsp; (Wide Area Network) interface of the CPE (Customer Premises<o:p>=
</o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'font-fa=
mily:"Arial","sans-serif"'>&nbsp;&nbsp; Equipment), or to a mobile terminal=
), whatever the number and the<o:p></o:p></span></pre><pre style=3D'margin-=
left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp; =
nature of the services the customer has subscribed to.<o:p></o:p></span></p=
re></div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><o:p>&nbsp;=
</o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><spa=
n style=3D'font-family:"Arial","sans-serif"'>=3D=3D&gt; In many cases, mult=
icast is used solely for IP-TV class solutions and its scope is limited to =
the service provider network.</span><o:p></o:p></p></div><div><p class=3DMs=
oNormal style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","sa=
ns-serif"'>&nbsp; &nbsp; &nbsp; &nbsp; Hence, global IPv4 addresses on the =
CPE are not necessary, private IPv4 addresses can be used to deliver this s=
ervice.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
10.0pt;font-family:"Courier New";color:#7030A0'>[CJ] This is precisely the =
point of the above text. Most of IPTV services are currently designed accor=
ding to a typical private IPv4 address-based walled garden approach, as you=
 rightfully mention. Such environments usually rely upon an IPTV service-sp=
ecific PVC, while other traffic (internet, voice) is conveyed over differen=
t PVCs that remain service-specific. Some operators are moving from this se=
rvice-specific, multi-PVC design to a service-agnostic, single PVC design, =
whatever the number and the nature of the services subscribed by the custom=
er. In that case, an RFC1918-based walled garden IPTV service design is har=
d to deploy, as corresponding customers rarely subscribe to an IPTV service=
 only.<o:p></o:p></span></p></div><div><p class=3DMsoNormal style=3D'margin=
-left:36.0pt'><o:p>&nbsp;</o:p></p></div><div><pre style=3D'margin-left:36.=
0pt;word-wrap: break-word;white-space:pre-wrap'><span style=3D'font-family:=
"Arial","sans-serif"'>&nbsp; Likewise, the global IPv4 address depletion en=
courages the<o:p></o:p></span></pre><pre style=3D'margin-left:36.0pt'><span=
 style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp; development of IPv=
6 receivers while contents may very well remain<o:p></o:p></span></pre><pre=
 style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","sans-seri=
f"'>&nbsp;&nbsp; IPv4-formatted</span><o:p></o:p></pre><div><p class=3DMsoN=
ormal style=3D'margin-left:36.0pt'><o:p>&nbsp;</o:p></p></div></div><div><p=
 class=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-family:=
"Arial","sans-serif"'>=3D=3D&gt; I do not understand what IPv4 formatted me=
ans. Does it mean sourced by an IPv4-only application? If so, say it.<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:"Courier New";color:#7030A0'>[CJ] Fair enough.<o:p></o:p></span></p><=
/div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><o:p>&nbsp;</o:=
p></p></div><div><pre style=3D'margin-left:36.0pt;word-wrap: break-word;whi=
te-space:pre-wrap'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&=
nbsp; o&nbsp; The current design of some multicast-based services like TV<o=
:p></o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'font=
-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; broadcasting o=
ften relies upon the use of a private IPv4<o:p></o:p></span></pre><pre styl=
e=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; addressing scheme because of a walled garden =
approach.&nbsp; Privately-<o:p></o:p></span></pre><pre style=3D'margin-left=
:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; addressed IGMP [RFC2236][RFC3376] traffic sent by IPv4 receiv=
ers<o:p></o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D=
'font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is genera=
lly forwarded over a specific (e.g., &quot;IPTV&quot;) PVC towards<o:p></o:=
p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'font-family=
:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; an IGMP Querier locat=
ed in the access infrastructure, e.g., in<o:p></o:p></span></pre><pre style=
=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; some deployments it is hosted by a BRAS (BRoad=
band Access Server)<o:p></o:p></span></pre><pre style=3D'margin-left:36.0pt=
'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; device that is the PPP (Point-to-Point Protocol) session endpoint<o:=
p></o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'font-=
family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and which may a=
lso act as a PIM DR (Protocol Independent Multicast<o:p></o:p></span></pre>=
<pre style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","sans-=
serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Designated Router)[RFC4601].&nbsp; T=
his design does not suffer from<o:p></o:p></span></pre><pre style=3D'margin=
-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; global IPv4 address depletion by definition (since multi=
cast<o:p></o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=
=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; traffi=
c relies upon the use of a private IPv4 addressing scheme),<o:p></o:p></spa=
n></pre><pre style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial=
","sans-serif"'> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;but it is inconsistent with =
migrating the access infrastructure<o:p></o:p></span></pre><pre style=3D'ma=
rgin-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; towards a publicly-addressed single PVC design schem=
e.</span><o:p></o:p></pre><pre style=3D'margin-left:36.0pt;word-wrap: break=
-word;white-space:pre-wrap'><o:p>&nbsp;</o:p></pre><pre style=3D'margin-lef=
t:36.0pt;word-wrap: break-word;white-space:pre-wrap'><span style=3D'font-fa=
mily:"Arial","sans-serif"'>=3D=3D&gt; This is somehow echoing the point I m=
ade earlier: technically, you can<o:p></o:p></span></pre><pre style=3D'marg=
in-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; do this with private IPv4 addresses. If yo=
u choose not too for other reasons,<o:p></o:p></span></pre><pre style=3D'ma=
rgin-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this is another story.&nbsp; So this all=
 section should be rewritten to explain<o:p></o:p></span></pre><pre style=
=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that the problem statement ONLY ap=
plies to cases where the ISP has decided<o:p></o:p></span></pre><pre style=
=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for whatever reasons to NOT deploy=
 private IPv4 addresses.<o:p></o:p></span></pre><pre><span style=3D'color:#=
7030A0'>[CJ] We cannot restrict the scope of the problem statement to this =
sole use case, because of the other contexts documented in Section 3. <o:p>=
</o:p></span></pre><pre style=3D'margin-left:36.0pt;word-wrap: break-word;w=
hite-space:pre-wrap'><span style=3D'font-family:"Arial","sans-serif"'><o:p>=
&nbsp;</o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'f=
ont-family:"Arial","sans-serif"'>&nbsp;&nbsp; o&nbsp; Likewise, other deplo=
yments (e.g., cable operators' environments)<o:p></o:p></span></pre><pre st=
yle=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rely upon the public CPE's address for mult=
icast delivery and will<o:p></o:p></span></pre><pre style=3D'margin-left:36=
.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; therefore suffer from IPv4 address depletion</span><o:p></o:p></=
pre></div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><span styl=
e=3D'font-family:"Arial","sans-serif"'>=3D=3D&gt; I don't understand this s=
tatement.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:10.0pt;font-family:"Courier New";color:#7030A0'>[CJ] The CPE is assigned =
a global IPv4 address. In some environments, this address is used for multi=
cast delivery purposes. As a consequence, global IPv4 address depletion may=
 jeopardize the delivery of such services, but I&#8217;ll let cable represe=
ntatives further elaborate.<o:p></o:p></span></p></div><div><p class=3DMsoN=
ormal style=3D'margin-left:36.0pt'><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal style=3D'margin-left:36.0pt'><o:p>&nbsp;</o:p></p></div><div><=
p class=3DMsoNormal style=3D'margin-left:36.0pt'><o:p>&nbsp;</o:p></p></div=
><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font=
-family:"Arial","sans-serif"'>=3D=3D&gt; KEY POINT: the underlying assumpti=
on in that introduction is that the access network will be IPv6-only.<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:"Courier New";color:#7030A0'>[CJ] This should indeed be consistent wi=
th a global IPv6 strategy that not only relates to Internet services, but a=
lso the whole service portfolio of an operator, IPTV services included.<o:p=
></o:p></span></p></div><div><p class=3DMsoNormal style=3D'margin-left:36.0=
pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp; &nbsp; &nbsp; &=
nbsp; I'm OK with that assumption, but it needs to be stated clearly as the=
re are other ways to deal with</span><o:p></o:p></p></div><div><p class=3DM=
soNormal style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","s=
ans-serif"'>&nbsp; &nbsp; &nbsp; &nbsp; IPv4 address exhaustion (for exampl=
e private IPv4 + CGN, with or without IPv6), for which the rest of</span><o=
:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><=
span style=3D'font-family:"Arial","sans-serif"'>&nbsp; &nbsp; &nbsp; &nbsp;=
document may or may not apply.<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Courier New";color:#7030A0'>[CJ]=
 Agreed, but please keep in mind this is a problem statement that tries to =
illustrate contexts where multicast transition techniques may be worth the =
investigation (Section 3). As such, what has been documented in this sectio=
n 3 reflects the situation of some of the operators who have co-authored th=
is draft.<o:p></o:p></span></p></div><div><p class=3DMsoNormal style=3D'mar=
gin-left:36.0pt'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal style=
=3D'margin-left:36.0pt'><o:p>&nbsp;</o:p></p></div><div><pre style=3D'margi=
n-left:36.0pt;word-wrap: break-word;white-space:pre-wrap'><span style=3D'fo=
nt-family:"Arial","sans-serif"'>2.2.&nbsp; Service Requirements</span><o:p>=
</o:p></pre><div><pre style=3D'margin-left:36.0pt;word-wrap: break-word;whi=
te-space:pre-wrap'><span style=3D'font-family:"Arial","sans-serif"'>o&nbsp;=
 Optimize bandwidth.&nbsp; Contents should not be multicast twice (i.e.,<o:=
p></o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'font-=
family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; using both vers=
ions of IP) to optimize bandwidth usage.&nbsp; Injecting<o:p></o:p></span><=
/pre><pre style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","=
sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast content using both IP=
v4 and IPv6 raises some<o:p></o:p></span></pre><pre style=3D'margin-left:36=
.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; dimensioning issues that should be carefully evaluated by servic=
e<o:p></o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'f=
ont-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; providers d=
uring network planning operations.&nbsp; For instance, if<o:p></o:p></span>=
</pre><pre style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial",=
"sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; only few IPv6-enabled receiver=
s are in use, it can be more<o:p></o:p></span></pre><pre style=3D'margin-le=
ft:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; convenient to convey multicast traffic over IPv4 rather tha=
n<o:p></o:p></span></pre><pre style=3D'margin-left:36.0pt'><span style=3D'f=
ont-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; doubling th=
e consumed resources for few users.&nbsp; IPv4/IPv6 co-<o:p></o:p></span></=
pre><pre style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","s=
ans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; existence solutions should be de=
signed to optimize network<o:p></o:p></span></pre><pre style=3D'margin-left=
:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; resource utilization.</span><o:p></o:p></pre><div><p class=3D=
MsoNormal style=3D'margin-left:36.0pt'><o:p>&nbsp;</o:p></p></div></div></d=
iv><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'fo=
nt-family:"Arial","sans-serif"'>=3D=3D&gt; CRITICAL: If I follow the logic =
here and I make the assumption that IPv4-only receivers will NEVER go away,=
</span><o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:=
36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp; &nbsp; &nbs=
p; &nbsp; them we are stuck forever using IPv4 multicast on the last mile!!=
!<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt=
;font-family:"Courier New";color:#7030A0'>[CJ] The assumption you make look=
s a bit strong to me as current SoA seems to indicate that Dual Stack commi=
tted roadmaps are being specified by the STB vendor industry. The point is =
to make IPv6 the rule, not the exception even in typical IPTV service envir=
onments. Admittedly, the hardest part is that current IPTV contents are unl=
ikely to be IPv6 multicast in the short term.<o:p></o:p></span></p></div><d=
iv><p class=3DMsoNormal style=3D'margin-left:36.0pt'><o:p>&nbsp;</o:p></p><=
/div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'=
font-family:"Arial","sans-serif"'>&nbsp; &nbsp; &nbsp; &nbsp; This is a VER=
Y serious issue here, and I consider it a show stopper, unless there is a w=
ay to</span><o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-=
left:36.0pt'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp; &nbsp;=
 &nbsp; &nbsp; completely segregate CPEs that are multicast IPv6 capable an=
d put them into a completely different</span><o:p></o:p></p></div><div><p c=
lass=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-family:"A=
rial","sans-serif"'>&nbsp; &nbsp; &nbsp; &nbsp; infrastructure than those w=
ho are not.&nbsp;Even if you were to use a single vlan per subscriber,</spa=
n><o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:36.0p=
t'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp; &nbsp; &nbsp; &n=
bsp; can you guarantee that you know exactly if that&nbsp;subscriber CPE is=
 multicast IPv6 capable or not?</span><o:p></o:p></p></div><div><p class=3D=
MsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial","=
sans-serif"'>&nbsp; &nbsp; &nbsp; &nbsp; Maybe you can in some environments=
 and not in others.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:#7030A0'>[CJ] That wou=
ld be an easy answer for service providers who provide managed CPEs, obviou=
sly (and who master the functional evolution of such CPEs). In case a custo=
mer wants to use an off-the-shelf CPE, he/she usually has to make sure the =
said CPE complies with the service specifications published by the provider=
. And this is clearly not IPTV-specific or multicast-specific.<o:p></o:p></=
span></p></div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><o:p>=
&nbsp;</o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt=
'><span style=3D'font-family:"Arial","sans-serif"'>&nbsp; &nbsp; &nbsp; &nb=
sp; Furthermore, if you have a mix of multicast v6 subscriber and multicast=
 v4 subscriber, what do you want</span><o:p></o:p></p></div><div><p class=
=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial=
","sans-serif"'>&nbsp; &nbsp; &nbsp; &nbsp; to use as a protocol on the edg=
e network? Are you OK to double the bandwidth there or not?<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New";color:#7030A0'>[CJ] The mix you mention can reasonably assume the=
 receivers will be DS-enabled, right? But the answer to your question obvio=
usly depends on the &#8220;format&#8221; of the application (IPv4-only cont=
ent, DS content) and the service provider&#8217;s IPv6 strategy, which brin=
gs us back to one of your previous points. I know some operators privilege =
IPv6 as the &#8220;transport&#8221; protocol, regardless of the nature of t=
he services subscribed by the customer, which, in the case of IPTV for exam=
ple, would ideally assume IPv6-enabled receivers and, more importantly, IPv=
6-formatted contents. Unfortunately, we&#8217;re not at this stage yet. Mea=
ning that for those operators, they either have to (1) stick to a typical w=
alled garden design (possibly at the cost of *<b>also</b>* running out of p=
rivate IPv4 addresses in a not so distant future (given mobile data growth,=
 for example) or (2) investigate multicast transition techniques, such as t=
he one documented in <a href=3D"http://tools.ietf.org/html/draft-ietf-softw=
ire-dslite-multicast-05">http://tools.ietf.org/html/draft-ietf-softwire-dsl=
ite-multicast-05</a>. &nbsp;&nbsp;<o:p></o:p></span></p></div><div><p class=
=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-family:"Arial=
","sans-serif"'>&nbsp; &nbsp; &nbsp; &nbsp; This is the CORE issue the docu=
ment should expand on, explaining when and where it is OK</span><o:p></o:p>=
</p></div><div><p class=3DMsoNormal style=3D'margin-left:36.0pt'><span styl=
e=3D'font-family:"Arial","sans-serif"'>&nbsp; &nbsp; &nbsp; &nbsp; to send =
both v4 multicast and v6 multicast and where it is not. Text like &quot;con=
tent should not be multicast twice&quot;</span><o:p></o:p></p></div><div><p=
 class=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-family:=
"Arial","sans-serif"'>&nbsp; &nbsp; &nbsp; &nbsp; is nice and well, but fee=
ls a bit like hand waving.<o:p></o:p></span></p><p class=3DMsoNormal style=
=3D'margin-left:36.0pt'><span style=3D'font-size:10.0pt;font-family:"Courie=
r New";color:#7030A0'>CJ: In that case, I don&#8217;t think this is a probl=
em statement document anymore. Besides, this kind of recommendation is like=
ly to be dependent on the service provider environment, given the nature of=
 the multicast service to be delivered, the foreseen business growth as a f=
unction of the market coverage, the network capabilities, etc.</span><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'><o:p></o:p></span></p>=
<p class=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-famil=
y:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal st=
yle=3D'margin-left:36.0pt'><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New";color:#7030A0'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:36.0pt'><span style=3D'font-size:10.0pt;font-family:"C=
ourier New";color:#7030A0'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
 style=3D'margin-left:36.0pt'><span style=3D'font-size:10.0pt;font-family:"=
Courier New";color:#7030A0'>Christian.<o:p></o:p></span></p></div></div><PR=
E>_________________________________________________________________________=
________________________________________________

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

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

--_000_983A1D8DA0DA5F4EB747BF34CBEE5CD15C435E95C4PUEXCB1Cnante_--

From N.Leymann@telekom.de  Tue Jul  2 05:00:11 2013
Return-Path: <N.Leymann@telekom.de>
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 AA54811E84A5 for <mboned@ietfa.amsl.com>; Tue,  2 Jul 2013 05:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.998
X-Spam-Level: 
X-Spam-Status: No, score=-2.998 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49lL8PNVxgPF for <mboned@ietfa.amsl.com>; Tue,  2 Jul 2013 05:00:06 -0700 (PDT)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) by ietfa.amsl.com (Postfix) with ESMTP id BFAAE11E849C for <mboned@ietf.org>; Tue,  2 Jul 2013 05:00:03 -0700 (PDT)
Received: from he111527.emea1.cds.t-internal.com ([10.125.90.86]) by tcmail41.telekom.de with ESMTP/TLS/AES128-SHA; 02 Jul 2013 13:59:58 +0200
Received: from HE113559.emea1.cds.t-internal.com (10.125.65.101) by HE111527.EMEA1.CDS.T-INTERNAL.COM (10.125.90.86) with Microsoft SMTP Server (TLS) id 8.3.298.1; Tue, 2 Jul 2013 13:59:58 +0200
Received: from HE111543.emea1.cds.t-internal.com ([10.125.90.96]) by HE113559.emea1.cds.t-internal.com ([2002:7cd:4165::7cd:4165]) with mapi; Tue, 2 Jul 2013 13:59:57 +0200
From: <N.Leymann@telekom.de>
To: <adurand@juniper.net>, <mboned@ietf.org>
Date: Tue, 2 Jul 2013 13:59:57 +0200
Thread-Topic: Comments on draft-ietf-mboned-v4v6-mcast-ps-02
Thread-Index: AQHOdEnwmm5PwAzUkkKjRu27N+iNf5lRTGyg
Message-ID: <9762ACF04FA26B4388476841256BDE02011AD557368A@HE111543.emea1.cds.t-internal.com>
References: <A7AA8F6D-4AB1-400A-A27B-6F04A26A08EA@juniper.net>
In-Reply-To: <A7AA8F6D-4AB1-400A-A27B-6F04A26A08EA@juniper.net>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE
Content-Type: multipart/alternative; boundary="_000_9762ACF04FA26B4388476841256BDE02011AD557368AHE111543eme_"
MIME-Version: 1.0
Subject: Re: [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: Tue, 02 Jul 2013 12:00:11 -0000

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

Hi,


=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.

Well, this depends heavily on your deployment scenario. From my point of vi=
ew this assumption is only vaild, if you are running your IPTV service in a=
 walled garden (which is not always the case, because it comes with additon=
al complexity - in operation, provisioning, routing compared to a "single s=
ession" approach). In this case you are able to use a private address. In o=
ther scenarios you have to use a public address - e.g. if you are using onl=
y a single session for all services including the IPTV service.

   regards

      Nic

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dus-ascii" http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.23487"></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-brea=
k: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D772345111-02072013><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Hi,</FONT></SPAN></DIV>
<DIV><FONT face=3DArial>&nbsp;</DIV>
<DIV dir=3Dltr lang=3Dde class=3DOutlookMessageHeader align=3Dleft><FONT co=
lor=3D#0000ff=20
size=3D2></FONT><BR></DIV></FONT>
<DIV><FONT face=3DArial>=3D=3D&gt; In many cases, multicast is used solely =
for IP-TV=20
class solutions and its scope is limited to the service provider=20
network.</FONT></DIV>
<DIV><FONT face=3DArial>&nbsp; &nbsp; &nbsp; &nbsp; Hence, global IPv4 addr=
esses=20
on the CPE are not necessary, private IPv4 addresses can be used to deliver=
 this=20
service.</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D772345111-02072013><FONT color=3D#0000ff size=3D2 face=
=3DArial>Well,=20
this depends heavily on your deployment scenario. From my point of view thi=
s=20
assumption is only vaild, if you are running your IPTV service in a walled=
=20
garden (which is not always the case, because it comes with additonal compl=
exity=20
- in operation, provisioning, routing compared to a "single session" approa=
ch).=20
In this case you are able to use a private address. In other scenarios you =
have=20
to use a public address - e.g. if you are using only a single session for a=
ll=20
services including the IPTV service. </FONT></SPAN></DIV>
<DIV><SPAN class=3D772345111-02072013><FONT color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN><SPAN class=3D772345111-02072013><FONT color=3D#=
0000ff=20
size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D772345111-02072013><FONT color=3D#0000ff size=3D2=20
face=3DArial>&nbsp;&nbsp; regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D772345111-02072013><FONT color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D772345111-02072013><FONT color=3D#0000ff size=3D2=20
face=3DArial>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Nic</FONT></SPAN></DIV></BODY><=
/HTML>

--_000_9762ACF04FA26B4388476841256BDE02011AD557368AHE111543eme_--

From lenny@juniper.net  Tue Jul  2 06:29:35 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 DD6EB21F9D5B for <mboned@ietfa.amsl.com>; Tue,  2 Jul 2013 06:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.099
X-Spam-Level: 
X-Spam-Status: No, score=-105.099 tagged_above=-999 required=5 tests=[AWL=-1.500, 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 p4MbTMLRqhNw for <mboned@ietfa.amsl.com>; Tue,  2 Jul 2013 06:29:30 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe003.messaging.microsoft.com [216.32.180.186]) by ietfa.amsl.com (Postfix) with ESMTP id EDC3621F9590 for <mboned@ietf.org>; Tue,  2 Jul 2013 06:29:29 -0700 (PDT)
Received: from mail116-co1-R.bigfish.com (10.243.78.251) by CO1EHSOBE018.bigfish.com (10.243.66.81) with Microsoft SMTP Server id 14.1.225.23; Tue, 2 Jul 2013 13:29:29 +0000
Received: from mail116-co1 (localhost [127.0.0.1])	by mail116-co1-R.bigfish.com (Postfix) with ESMTP id 44446160102; Tue,  2 Jul 2013 13:29:29 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.54; KIP:(null); UIP:(null); IPV:NLI; H:P-EMHUB02-HQ.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: 2
X-BigFish: VPS2(zz98dIzz1f42h1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kzzz2fh2a8h668h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1d0ch1d2eh1d3fh1de2h1dfeh1dffh1155h)
Received-SPF: pass (mail116-co1: domain of juniper.net designates 66.129.224.54 as permitted sender) client-ip=66.129.224.54; envelope-from=lenny@juniper.net; helo=P-EMHUB02-HQ.jnpr.net ; -HQ.jnpr.net ; 
Received: from mail116-co1 (localhost.localdomain [127.0.0.1]) by mail116-co1 (MessageSwitch) id 1372771767100203_2324; Tue,  2 Jul 2013 13:29:27 +0000 (UTC)
Received: from CO1EHSMHS023.bigfish.com (unknown [10.243.78.235])	by mail116-co1.bigfish.com (Postfix) with ESMTP id 15B6B540046; Tue,  2 Jul 2013 13:29:27 +0000 (UTC)
Received: from P-EMHUB02-HQ.jnpr.net (66.129.224.54) by CO1EHSMHS023.bigfish.com (10.243.66.33) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 2 Jul 2013 13:29:25 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB02-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 2 Jul 2013 06:29:25 -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 r62DTOL85663; Tue, 2 Jul 2013 06:29:24 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id C8DE31144E;  Tue,  2 Jul 2013 06:29:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id BE33A11446; Tue,  2 Jul 2013 06:29:23 -0700 (PDT)
Date: Tue, 2 Jul 2013 06:29:23 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: <N.Leymann@telekom.de>
In-Reply-To: <9762ACF04FA26B4388476841256BDE02011AD557368A@HE111543.emea1.cds.t-internal.com>
Message-ID: <20130702062758.J22291@eng-mail01.juniper.net>
References: <A7AA8F6D-4AB1-400A-A27B-6F04A26A08EA@juniper.net> <9762ACF04FA26B4388476841256BDE02011AD557368A@HE111543.emea1.cds.t-internal.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginatorOrg: juniper.net
Cc: mboned@ietf.org, adurand@juniper.net
Subject: Re: [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: Tue, 02 Jul 2013 13:29:36 -0000

On Tue, 2 Jul 2013, N.Leymann@telekom.de wrote:

-) Hi,
-) 
-) 
-) ==> In many cases, multicast is used solely for IP-TV class solutions and 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.
-) 
-) Well, this depends heavily on your deployment scenario. From my point 
-) of view this assumption is only vaild, if you are running your IPTV 
-) service in a walled garden (which is not always the case, because it 
-) comes with additonal complexity - in operation, provisioning, routing 
-) compared to a "single session" approach). In this case you are able to 
-) use a private address. In other scenarios you have to use a public 
-) address - e.g. if you are using only a single session for all services 
-) including the IPTV service.
-) 

>From 2.1. Scope of this doc:

   Intra-domain only:   The delivery of multicast services such as live
      TV broadcasting often relies upon walled garden designs that
      restrict the scope to the domain where such services can be
      subscribed.  As a consequence, considerations about inter-domain
      multicast are out of the scope of this document.


From tjc@ecs.soton.ac.uk  Tue Jul  2 07:08:03 2013
Return-Path: <tjc@ecs.soton.ac.uk>
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 AAB0121F9E32 for <mboned@ietfa.amsl.com>; Tue,  2 Jul 2013 07:08:03 -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 KDvT4bkStofg for <mboned@ietfa.amsl.com>; Tue,  2 Jul 2013 07:08:02 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA9121F9DC2 for <mboned@ietf.org>; Tue,  2 Jul 2013 07:08:02 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r62E80WF013589; Tue, 2 Jul 2013 15:08:00 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r62E80WF013589
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1372774080; bh=xqOBL0MBGwsH5mClA7ENuXhAT6Y=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=1TbUKEar/qHjK2CoydJtpQpY8NC1gWuaO3vsbSxHs9dxl+JI8gzbJiCI1o/Z7Oqq/ nRCP+SKtAHdM7e4pFZOfpSjv6n5vwSxWHyXJ12mb7rRzo6ulGEQWNepATsCnIbLOjm c4I6ejhkdp+NFUdkdQ71WNAdIKS32c7fF06QoKS4=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p61F7x0544500966Eo ret-id none; Tue, 02 Jul 2013 15:08:00 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r62E7uYu027958 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 2 Jul 2013 15:07:56 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20130702062758.J22291@eng-mail01.juniper.net>
Date: Tue, 2 Jul 2013 15:07:58 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|715e6bb03391521c12b887c02cf2933ep61F7x03tjc|ecs.soton.ac.uk|8A2A44F1-D431-41EC-84F3-7D79DBC7AC50@ecs.soton.ac.uk>
References: <A7AA8F6D-4AB1-400A-A27B-6F04A26A08EA@juniper.net> <9762ACF04FA26B4388476841256BDE02011AD557368A@HE111543.emea1.cds.t-internal.com> <20130702062758.J22291@eng-mail01.juniper.net> <8A2A44F1-D431-41EC-84F3-7D79DBC7AC50@ecs.soton.ac.uk>
To: Leonard Giuliano <lenny@juniper.net>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p61F7x054450096600; tid=p61F7x0544500966Eo; client=relay,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r62E80WF013589
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: mboned@ietf.org, adurand@juniper.net
Subject: Re: [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: Tue, 02 Jul 2013 14:08:03 -0000

On 2 Jul 2013, at 14:29, Leonard Giuliano <lenny@juniper.net> wrote:

> On Tue, 2 Jul 2013, N.Leymann@telekom.de wrote:
> -)=20
> -) =3D=3D> In many cases, multicast is used solely for IP-TV class =
solutions and 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.
> -)=20
> -) Well, this depends heavily on your deployment scenario. =46rom my =
point=20
> -) of view this assumption is only vaild, if you are running your IPTV=20=

> -) service in a walled garden (which is not always the case, because =
it=20
> -) comes with additonal complexity - in operation, provisioning, =
routing=20
> -) compared to a "single session" approach). In this case you are able =
to=20
> -) use a private address. In other scenarios you have to use a public=20=

> -) address - e.g. if you are using only a single session for all =
services=20
> -) including the IPTV service.
> -)=20
>=20
> =46rom 2.1. Scope of this doc:
>=20
>   Intra-domain only:   The delivery of multicast services such as live
>      TV broadcasting often relies upon walled garden designs that
>      restrict the scope to the domain where such services can be
>      subscribed.  As a consequence, considerations about inter-domain
>      multicast are out of the scope of this document.

I think the abstract should make this limited document scope much =
clearer.

Tim=

From N.Leymann@telekom.de  Wed Jul  3 01:32:21 2013
Return-Path: <N.Leymann@telekom.de>
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 E4EDE21F9ACA for <mboned@ietfa.amsl.com>; Wed,  3 Jul 2013 01:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.082
X-Spam-Level: 
X-Spam-Status: No, score=-3.082 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 7qdquTMeSFRw for <mboned@ietfa.amsl.com>; Wed,  3 Jul 2013 01:32:16 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id 89F2421F9C2C for <mboned@ietf.org>; Wed,  3 Jul 2013 01:32:16 -0700 (PDT)
Received: from he113414.emea1.cds.t-internal.com ([10.125.65.80]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 03 Jul 2013 10:32:14 +0200
Received: from HE100013.emea1.cds.t-internal.com (10.125.65.196) by HE113414.emea1.cds.t-internal.com (10.125.65.80) with Microsoft SMTP Server (TLS) id 8.3.298.1; Wed, 3 Jul 2013 10:32:14 +0200
Received: from HE111543.emea1.cds.t-internal.com ([10.125.90.96]) by HE100013.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 3 Jul 2013 10:32:13 +0200
From: <N.Leymann@telekom.de>
To: <lenny@juniper.net>
Date: Wed, 3 Jul 2013 10:32:13 +0200
Thread-Topic: [MBONED] Comments on draft-ietf-mboned-v4v6-mcast-ps-02
Thread-Index: Ac53KByNQGfzwaQtQtqRvCbGQytKcQAn0Z/Q
Message-ID: <9762ACF04FA26B4388476841256BDE02011AD5573BC4@HE111543.emea1.cds.t-internal.com>
References: <A7AA8F6D-4AB1-400A-A27B-6F04A26A08EA@juniper.net> <9762ACF04FA26B4388476841256BDE02011AD557368A@HE111543.emea1.cds.t-internal.com> <20130702062758.J22291@eng-mail01.juniper.net>
In-Reply-To: <20130702062758.J22291@eng-mail01.juniper.net>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mboned@ietf.org, adurand@juniper.net
Subject: Re: [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: Wed, 03 Jul 2013 08:32:22 -0000

Hi,

> -----Urspr=FCngliche Nachricht-----
> Von: Leonard Giuliano [mailto:lenny@juniper.net]
> Gesendet: Dienstag, 2. Juli 2013 15:29
> An: Leymann, Nicolai
> Cc: adurand@juniper.net; mboned@ietf.org
> Betreff: Re: [MBONED] Comments on draft-ietf-mboned-v4v6-mcast-ps-02
>
>
> On Tue, 2 Jul 2013, N.Leymann@telekom.de wrote:
>
> -) Hi,
> -)
> -)
> -) =3D=3D> In many cases, multicast is used solely for IP-TV class soluti=
ons and its scope is limited to the service provider network.
> -)         Hence, global IPv4 addresses on the CPE are not necessary, pri=
vate IPv4 addresses can be used to deliver this service.
> -)
> -) Well, this depends heavily on your deployment scenario. From my point
> -) of view this assumption is only vaild, if you are running your IPTV
> -) service in a walled garden (which is not always the case, because it
> -) comes with additonal complexity - in operation, provisioning, routing
> -) compared to a "single session" approach). In this case you are able to
> -) use a private address. In other scenarios you have to use a public
> -) address - e.g. if you are using only a single session for all services
> -) including the IPTV service.
> -)
>
> From 2.1. Scope of this doc:
>
>    Intra-domain only:   The delivery of multicast services such as live
>       TV broadcasting often relies upon walled garden designs that
>       restrict the scope to the domain where such services can be
>       subscribed.  As a consequence, considerations about inter-domain
>       multicast are out of the scope of this document.
>
Even in the "non walled garden scenario" with a single session the Multicas=
t traffic usually comes from local sources (and therefore is intra domain t=
raffic). From my point of view a scenario with public IP addresses and loca=
l (intra domain) Multicast traffic is in scope.

  Regards

    Nic

From internet-drafts@ietf.org  Fri Jul  5 08:28:01 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 34F2511E813F; Fri,  5 Jul 2013 08:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.090, 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 JdnW3CPdf9NX; Fri,  5 Jul 2013 08:28:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C368611E812F; Fri,  5 Jul 2013 08:28:00 -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.51.p2
Message-ID: <20130705152800.4751.93521.idtracker@ietfa.amsl.com>
Date: Fri, 05 Jul 2013 08:28:00 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-multrans-addr-acquisition-02.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: Fri, 05 Jul 2013 15:28:01 -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-02.txt
	Pages           : 10
	Date            : 2013-07-05

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-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-multrans-addr-acquisit=
ion-02


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


From tom.taylor.stds@gmail.com  Fri Jul  5 11:19:16 2013
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 D8DEF21F85C3 for <mboned@ietfa.amsl.com>; Fri,  5 Jul 2013 11:19:16 -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 ktpcLyTTABwe for <mboned@ietfa.amsl.com>; Fri,  5 Jul 2013 11:19:16 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id E128911E813F for <mboned@ietf.org>; Fri,  5 Jul 2013 11:19:14 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id ar20so6048086iec.35 for <mboned@ietf.org>; Fri, 05 Jul 2013 11:19:12 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=MGetCfaq7nLVzdLzjBB1akCI0lGaOKsxy4Hrs/uAayA=; b=LmiiTrNDSAQtl22qlIxwM66dvPLQ5XzWVPdc0ldyiidy3TBygWnHlDx5ZYFpVut1a3 M7FSOPkdvY3SOKUcvRcHn6AEsm3T0N/ojq9YouWDAbVCTipCx6jCv5WGd8SjDKotK3Fp fVEAk37/LBWQK3oq/QVznypfH4WTebXY8jual6UgRtdJpg6x/vupyaXPff9YwMcdkw0I VFJu4QgHFXJdkHQWD/jA91ul1p71pTe1I1PgvKp6VsD2zvBnS/JqRd6p5IqBI27Cm1cF p875jp8TR5SsiKGCIWL9mru7A30nOztY5aArCMeryNQRgz294oT/6JR01SyU0FnNhV/j aIhQ==
X-Received: by 10.42.133.66 with SMTP id g2mr4240517ict.49.1373048352713; Fri, 05 Jul 2013 11:19:12 -0700 (PDT)
Received: from [192.168.1.64] ([216.254.161.150]) by mx.google.com with ESMTPSA id nr4sm4503903igb.0.2013.07.05.11.19.10 for <mboned@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Jul 2013 11:19:11 -0700 (PDT)
Message-ID: <51D70E20.90803@gmail.com>
Date: Fri, 05 Jul 2013 14:19:12 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: mboned@ietf.org
References: <20130705152800.4751.93521.idtracker@ietfa.amsl.com>
In-Reply-To: <20130705152800.4751.93521.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [MBONED] I-D Action: draft-ietf-mboned-multrans-addr-acquisition-02.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: Fri, 05 Jul 2013 18:19:17 -0000

I note that this seems to be a keep-alive update only. Now that the WG 
has indicated its support of the Problem Statement (even if the Chairs 
haven't admitted that), it seems to me it would be a good idea to 
rewrite the address acquisition document to look specifically at each 
use case identified by the PS, determine whether a problem actually 
exists, and what solutions are suitable for that use case.

Tom Taylor

On 05/07/2013 11:28 AM, internet-drafts@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the MBONE Deployment Working Group of the IETF.
>
> 	Title           : Address Acquisition For Multicast Content When Source and Receiver Support Differing IP Versions
> 	Author(s)       : Tina Tsou
>                            Axel Clauberg
>                            Mohamed Boucadair
>                            Stig Venaas
>                            Qiong Sun
> 	Filename        : draft-ietf-mboned-multrans-addr-acquisition-02.txt
> 	Pages           : 10
> 	Date            : 2013-07-05
>
> 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.
>
...

From Tina.Tsou.Zouting@huawei.com  Fri Jul  5 13:18:33 2013
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 8FC7321F93BF for <mboned@ietfa.amsl.com>; Fri,  5 Jul 2013 13:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.396
X-Spam-Level: 
X-Spam-Status: No, score=-2.396 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, 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 IROVZAFMCdbv for <mboned@ietfa.amsl.com>; Fri,  5 Jul 2013 13:18:29 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D0A8821F9FC0 for <mboned@ietf.org>; Fri,  5 Jul 2013 13:18:28 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AUS36530; Fri, 05 Jul 2013 20:18:26 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 5 Jul 2013 21:18:13 +0100
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 5 Jul 2013 21:18:20 +0100
Received: from DFWEML513-MBS.china.huawei.com ([169.254.4.217]) by dfweml405-hub.china.huawei.com ([10.193.5.102]) with mapi id 14.01.0323.007; Fri, 5 Jul 2013 13:18:14 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] I-D Action: draft-ietf-mboned-multrans-addr-acquisition-02.txt
Thread-Index: AQHOeZRuC6/5hGJKk0eEl71lgl5PVZlW2nsA//+rxwA=
Date: Fri, 5 Jul 2013 20:18:13 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A816846458@dfweml513-mbs.china.huawei.com>
References: <20130705152800.4751.93521.idtracker@ietfa.amsl.com> <51D70E20.90803@gmail.com>
In-Reply-To: <51D70E20.90803@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.193.34.116]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [MBONED] I-D Action:	draft-ietf-mboned-multrans-addr-acquisition-02.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: Fri, 05 Jul 2013 20:18:33 -0000

RGVhciBUb20sDQpHb29kIHBvaW50cy4NCklmIHRoZSBXRyBhZ3JlZXMsIHRoZSBhdXRob3JzIGNv
dWxkIHRyeSB0byByZXZpc2UgdGhlIGRvY3VtZW50IHBlciB5b3VyIHN1Z2dlc3Rpb24uDQoNClRo
YW5rIHlvdSwNClRpbmENCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206
IG1ib25lZC1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86bWJvbmVkLWJvdW5jZXNAaWV0Zi5vcmdd
IE9uIEJlaGFsZg0KPiBPZiBUb20gVGF5bG9yDQo+IFNlbnQ6IDIwMTPE6jfUwjXI1SAxMToxOQ0K
PiBUbzogbWJvbmVkQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbTUJPTkVEXSBJLUQgQWN0aW9u
OiBkcmFmdC1pZXRmLW1ib25lZC1tdWx0cmFucy1hZGRyLQ0KPiBhY3F1aXNpdGlvbi0wMi50eHQN
Cj4gDQo+IEkgbm90ZSB0aGF0IHRoaXMgc2VlbXMgdG8gYmUgYSBrZWVwLWFsaXZlIHVwZGF0ZSBv
bmx5LiBOb3cgdGhhdCB0aGUgV0cNCj4gaGFzIGluZGljYXRlZCBpdHMgc3VwcG9ydCBvZiB0aGUg
UHJvYmxlbSBTdGF0ZW1lbnQgKGV2ZW4gaWYgdGhlIENoYWlycw0KPiBoYXZlbid0IGFkbWl0dGVk
IHRoYXQpLCBpdCBzZWVtcyB0byBtZSBpdCB3b3VsZCBiZSBhIGdvb2QgaWRlYSB0byByZXdyaXRl
DQo+IHRoZSBhZGRyZXNzIGFjcXVpc2l0aW9uIGRvY3VtZW50IHRvIGxvb2sgc3BlY2lmaWNhbGx5
IGF0IGVhY2ggdXNlIGNhc2UNCj4gaWRlbnRpZmllZCBieSB0aGUgUFMsIGRldGVybWluZSB3aGV0
aGVyIGEgcHJvYmxlbSBhY3R1YWxseSBleGlzdHMsIGFuZA0KPiB3aGF0IHNvbHV0aW9ucyBhcmUg
c3VpdGFibGUgZm9yIHRoYXQgdXNlIGNhc2UuDQo+IA0KPiBUb20gVGF5bG9yDQo+IA0KPiBPbiAw
NS8wNy8yMDEzIDExOjI4IEFNLCBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgd3JvdGU6DQo+ID4N
Cj4gPiBBIE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJ
bnRlcm5ldC1EcmFmdHMNCj4gZGlyZWN0b3JpZXMuDQo+ID4gICBUaGlzIGRyYWZ0IGlzIGEgd29y
ayBpdGVtIG9mIHRoZSBNQk9ORSBEZXBsb3ltZW50IFdvcmtpbmcgR3JvdXAgb2YNCj4gdGhlIElF
VEYuDQo+ID4NCj4gPiAJVGl0bGUgICAgICAgICAgIDogQWRkcmVzcyBBY3F1aXNpdGlvbiBGb3Ig
TXVsdGljYXN0IENvbnRlbnQgV2hlbg0KPiBTb3VyY2UgYW5kIFJlY2VpdmVyIFN1cHBvcnQgRGlm
ZmVyaW5nIElQIFZlcnNpb25zDQo+ID4gCUF1dGhvcihzKSAgICAgICA6IFRpbmEgVHNvdQ0KPiA+
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIEF4ZWwgQ2xhdWJlcmcNCj4gPiAgICAgICAgICAg
ICAgICAgICAgICAgICAgICBNb2hhbWVkIEJvdWNhZGFpcg0KPiA+ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIFN0aWcgVmVuYWFzDQo+ID4gICAgICAgICAgICAgICAgICAgICAgICAgICAgUWlv
bmcgU3VuDQo+ID4gCUZpbGVuYW1lICAgICAgICA6IGRyYWZ0LWlldGYtbWJvbmVkLW11bHRyYW5z
LWFkZHItYWNxdWlzaXRpb24tDQo+IDAyLnR4dA0KPiA+IAlQYWdlcyAgICAgICAgICAgOiAxMA0K
PiA+IAlEYXRlICAgICAgICAgICAgOiAyMDEzLTA3LTA1DQo+ID4NCj4gPiBBYnN0cmFjdDoNCj4g
PiAgICAgRWFjaCBJUFRWIG9wZXJhdG9yIGhhcyB0aGVpciBvd24gYXJyYW5nZW1lbnRzIGZvciBw
cmUtcHJvdmlzaW9uaW5nDQo+ID4gICAgIHByb2dyYW0gaW5mb3JtYXRpb24gaW5jbHVkaW5nIGFk
ZHJlc3NlcyBvZiB0aGUgbXVsdGljYXN0IGdyb3Vwcw0KPiA+ICAgICBjb3JyZXNwb25kaW5nIHRv
IGJyb2FkY2FzdCBwcm9ncmFtcyBvbiB0aGUgc3Vic2NyaWJlciByZWNlaXZlci4NCj4gPiAgICAg
RHVyaW5nIHRoZSB0cmFuc2l0aW9uIGZyb20gSVB2NCB0byBJUHY2LCBzY2VuYXJpb3MgY2FuIG9j
Y3VyIHdoZXJlDQo+ID4gICAgIHRoZSBJUCB2ZXJzaW9uIHN1cHBvcnRlZCBieSB0aGUgcmVjZWl2
ZXIgZGlmZmVycyBmcm9tIHRoYXQNCj4gc3VwcG9ydGVkDQo+ID4gICAgIGJ5IHRoZSBzb3VyY2Uu
ICBUaGlzIG1lbW8gZXhhbWluZXMgd2hhdCBoYXMgdG8gYmUgZG9uZSB0byBhbGxvdyB0aGUNCj4g
PiAgICAgcmVjZWl2ZXIgdG8gYWNxdWlyZSBtdWx0aWNhc3QgYWRkcmVzcyBpbmZvcm1hdGlvbiBp
biB0aGUgdmVyc2lvbiBpdA0KPiA+ICAgICBzdXBwb3J0cyBpbiBzdWNoIHNjZW5hcmlvcy4NCj4g
Pg0KPiAuLi4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4gTUJPTkVEIG1haWxpbmcgbGlzdA0KPiBNQk9ORURAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tYm9uZWQNCg==

From internet-drafts@ietf.org  Mon Jul  8 23:13:34 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 1A59421F9F33; Mon,  8 Jul 2013 23:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.482
X-Spam-Level: 
X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.118, 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 gKBzwO3PUqK2; Mon,  8 Jul 2013 23:13:33 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A5C8321F9E9D; Mon,  8 Jul 2013 23:13:33 -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.51.p2
Message-ID: <20130709061333.15880.77347.idtracker@ietfa.amsl.com>
Date: Mon, 08 Jul 2013 23:13:33 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-mtrace-v2-10.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, 09 Jul 2013 06:13:34 -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           : Mtrace Version 2: Traceroute Facility for IP Multicast
	Author(s)       : Hitoshi Asaeda
                          WeeSan Lee
	Filename        : draft-ietf-mboned-mtrace-v2-10.txt
	Pages           : 33
	Date            : 2013-07-08

Abstract:
   This document describes the IP multicast traceroute facility, named
   Mtrace version 2 (Mtrace2).  Unlike unicast traceroute, Mtrace2
   requires special implementations on the part of routers.  This
   specification describes the required functionality in multicast
   routers, as well as how an Mtrace2 client invokes a query and
   receives a reply.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mboned-mtrace-v2-10

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-mtrace-v2-10


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


From internet-drafts@ietf.org  Mon Jul 15 14:42:46 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 ADA7C11E81A5; Mon, 15 Jul 2013 14:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.538
X-Spam-Level: 
X-Spam-Status: No, score=-102.538 tagged_above=-999 required=5 tests=[AWL=0.062, 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 LVL3rh6wZ39H; Mon, 15 Jul 2013 14:42:45 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1E821F9CD3; Mon, 15 Jul 2013 14:42:45 -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.51.p2
Message-ID: <20130715214245.19560.90237.idtracker@ietfa.amsl.com>
Date: Mon, 15 Jul 2013 14:42:45 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-auto-multicast-15.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: Mon, 15 Jul 2013 21:42:46 -0000

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

	Title           : Automatic Multicast Tunneling
	Author(s)       : Gregory Bumgardner
	Filename        : draft-ietf-mboned-auto-multicast-15.txt
	Pages           : 81
	Date            : 2013-07-15

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

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


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mboned-auto-multicast-15

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


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


From gbumgard@gmail.com  Mon Jul 15 22:33:06 2013
Return-Path: <gbumgard@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 86C0A11E8231 for <mboned@ietfa.amsl.com>; Mon, 15 Jul 2013 22:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0k8vLOqnlEzA for <mboned@ietfa.amsl.com>; Mon, 15 Jul 2013 22:33:05 -0700 (PDT)
Received: from mail-bk0-x232.google.com (mail-bk0-x232.google.com [IPv6:2a00:1450:4008:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 0057A11E821A for <mboned@ietf.org>; Mon, 15 Jul 2013 22:33:04 -0700 (PDT)
Received: by mail-bk0-f50.google.com with SMTP id ik8so80153bkc.9 for <mboned@ietf.org>; Mon, 15 Jul 2013 22:33:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=UgCYN6NhKQh+fx4DLt5efvZLzLlwAnro2+S+1IreEVA=; b=LGGTL/LeZOwFFTG3OkBESu6StcFk1CCc0+DLAnOrQ0nqlI2WQ9c9DA9pVdjiHsboRf 1E0TL1vVrZQi5ItaRH9OT4cMpCWSzswNGnj/rnud1wJeoHhTesoLuJGONg07+ApMfDLc ix0ta9CXJBJR4FG4UvFFK0Pn+DFn/iPS3UStqeZlJFdcsGVyfZJsTPdkCpER1oEVgC+k VKdHz4jBjOhnEr9EabRQXAB/teNO//mRVE52fSqWQ3r4sf6ejSTuhHc38cy17VL/nmqb laoDLI2bWkbw0jcfwCvPfKjtLRces9ysljGOjrEuk+2/qWGi3RhKO1NpTNOyw0+2Ssjf S8Ow==
MIME-Version: 1.0
X-Received: by 10.204.3.137 with SMTP id 9mr8113770bkn.147.1373952782827; Mon, 15 Jul 2013 22:33:02 -0700 (PDT)
Received: by 10.205.141.79 with HTTP; Mon, 15 Jul 2013 22:33:02 -0700 (PDT)
In-Reply-To: <51E49AEA.4000705@concordia.ca>
References: <51E49AEA.4000705@concordia.ca>
Date: Mon, 15 Jul 2013 22:33:02 -0700
Message-ID: <CAJkfEFrh=AboKk+PmPXZog2ADKH=XhLQNYMnaca_2ANec5etVQ@mail.gmail.com>
From: Greg Bumgardner <gbumgard@gmail.com>
To: William Atwood <william.atwood@concordia.ca>, "mboned@ietf.org" <mboned@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [MBONED] draft-ietf-mboned-auto-multicast-15
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, 16 Jul 2013 05:33:06 -0000

Thanks Bill,

So much for spell checking the document.

-g.b.

On Mon, Jul 15, 2013 at 5:59 PM, William Atwood
<william.atwood@concordia.ca> wrote:
> Greg,
>
> Here are some nits I discovered on reading the rfcdiff output:
>
> 8 lines below figure 5:
>
> "IGMPv2/MLDv2" -> "IGMPv3/MLDv2"
>
> In 4.2.1.3. Teardown Sequence, para 1, line 7:
>
> "instead relay" -> "instead rely"
>
> 7 lines above 5.3.3.4. Handling a Membership Update Message:
>
> "IGMPv2/MLDv2" -> "IGMPv3/MLDv2"
>
> (You might want to do a search for "IGMPv2/MLDv2" and swat all
> occurrences...)
>
> In 5.3.3.6.2.1. IPv4 Multicast IP Datagrams, para 1, lines 6-7:
>
> Why is [RFC1191] given twice?
>
> In 5.3.3.6.4. Handling Destination Unreachable Messages, para 1, line 7:
>
> "MUTST"=> "MUST"
>
> In 5.3.5. Response MAC Generation, bullet 2, line 1.
>
> "Tp" -> "To"
>
> Three lines above 6.2. Gateways:
>
> "On order" -> "In order"
>
> In 7.1. IPv4 and IPv6 Anycast Prefix Allocation, para 1, line 2.
>
> "as as" -> "as"
>
>   Bill
>
> --
> Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
> Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
> Department of Computer Science
>    and Software Engineering
> Concordia University EV 3.185     email:william.atwood@concordia.ca
> 1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
> Montreal, Quebec Canada H3G 1M8



-- 
Greg Bumgardner
Eugene, OR

From lenny@juniper.net  Wed Jul 17 14:18:28 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 9496421F9C25 for <mboned@ietfa.amsl.com>; Wed, 17 Jul 2013 14:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.224
X-Spam-Level: 
X-Spam-Status: No, score=-104.224 tagged_above=-999 required=5 tests=[AWL=-1.625, 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 e884O1SR0Nkh for <mboned@ietfa.amsl.com>; Wed, 17 Jul 2013 14:18:22 -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 2D63C21F9AFD for <mboned@ietf.org>; Wed, 17 Jul 2013 14:18:22 -0700 (PDT)
Received: from mail18-db8-R.bigfish.com (10.174.8.235) by DB8EHSOBE040.bigfish.com (10.174.4.103) with Microsoft SMTP Server id 14.1.225.22; Wed, 17 Jul 2013 21:18:21 +0000
Received: from mail18-db8 (localhost [127.0.0.1])	by mail18-db8-R.bigfish.com (Postfix) with ESMTP id 29DA2AE00AC	for <mboned@ietf.org>; Wed, 17 Jul 2013 21:18:21 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.51; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF02-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: 3
X-BigFish: VPS3(zzzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kzzz2fh2a8h668h839h944hd25hf0ah11b5h121eh1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1d0ch1d2eh1d3fh1dc1h1de2h1dfeh1dffh1155h)
Received-SPF: pass (mail18-db8: domain of juniper.net designates 66.129.224.51 as permitted sender) client-ip=66.129.224.51; envelope-from=lenny@juniper.net; helo=P-EMF02-SAC.jnpr.net ; SAC.jnpr.net ; 
Received: from mail18-db8 (localhost.localdomain [127.0.0.1]) by mail18-db8 (MessageSwitch) id 1374095899197036_4731; Wed, 17 Jul 2013 21:18:19 +0000 (UTC)
Received: from DB8EHSMHS026.bigfish.com (unknown [10.174.8.248])	by mail18-db8.bigfish.com (Postfix) with ESMTP id 2C273600048	for <mboned@ietf.org>; Wed, 17 Jul 2013 21:18:19 +0000 (UTC)
Received: from P-EMF02-SAC.jnpr.net (66.129.224.51) by DB8EHSMHS026.bigfish.com (10.174.4.36) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 17 Jul 2013 21:18:18 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF02-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 17 Jul 2013 14:18:16 -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 r6HLIFL06990	for <mboned@ietf.org>; Wed, 17 Jul 2013 14:18:15 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 161C711446;  Wed, 17 Jul 2013 14:18:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 05B0C1141B	for <mboned@ietf.org>; Wed, 17 Jul 2013 14:18:15 -0700 (PDT)
Date: Wed, 17 Jul 2013 14:18:14 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
Message-ID: <20130717141632.N27127@eng-mail01.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: [MBONED] MBONED draft 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, 17 Jul 2013 21:18:28 -0000

Here's the draft agenda for MBoned in Berlin.  Quite full.  Please let us 
know if we missed anyone who requested a slot.

IETF 87 Berlin
MBONED Agenda
Tues, Jul 30, 201
5-6:30PM
Charlottenburg 1

Status of WG items, recharter, multrans, AMT
Chairs, 15 min

Multicast across Peering Points
Tarapore, 15 min

draft-kebler-kurapati-l3vpn-mvpn-mtrace-00
Kebler, 10 min

draft-morin-multicast-damping-00
Morin, 10 min

Signal-less Overlay Multicast
Farinacci, 15 min

LISP-RE
Farinacci, 5 min

IPv4-IPv6 Multicast Address Dynamic Conversion
Wei, 10 min

draft-ietf-6man-multicast-addr-arch-update-01
Venaas, 10 min


From asaeda@sfc.wide.ad.jp  Thu Jul 18 07:37:32 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
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 C974F11E813D for <mboned@ietfa.amsl.com>; Thu, 18 Jul 2013 07:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VD0-iy5AgBrw for <mboned@ietfa.amsl.com>; Thu, 18 Jul 2013 07:37:32 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 25D0E11E80E3 for <mboned@ietf.org>; Thu, 18 Jul 2013 07:37:31 -0700 (PDT)
Received: from localhost (p16013-ipngn5101marunouchi.tokyo.ocn.ne.jp [153.161.31.13]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 8840B2780D3 for <mboned@ietf.org>; Thu, 18 Jul 2013 23:37:29 +0900 (JST)
Date: Thu, 18 Jul 2013 23:37:30 +0900 (JST)
Message-Id: <20130718.233730.83400781.asaeda@sfc.wide.ad.jp>
To: mboned@ietf.org
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <20130717141632.N27127@eng-mail01.juniper.net>
References: <20130717141632.N27127@eng-mail01.juniper.net>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [MBONED] MBONED draft 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: Thu, 18 Jul 2013 14:37:33 -0000

Hi,

> Here's the draft agenda for MBoned in Berlin.  Quite full.  Please let
> us know if we missed anyone who requested a slot.

I've not asked a slot for mtrace2 draft update, because the revised
draft is only with editorial update.

http://tools.ietf.org/html/draft-ietf-mboned-mtrace-v2-10

We'd like to ask you to review this revised version as we may later
ask the WGLC based on this document (or next revison if we get comment
to be addressed).

Regards,
--
Hitoshi Asaeda

From pt5947@att.com  Thu Jul 18 07:49:07 2013
Return-Path: <pt5947@att.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 4B7B821E8102 for <mboned@ietfa.amsl.com>; Thu, 18 Jul 2013 07:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c2Scx3FufgzE for <mboned@ietfa.amsl.com>; Thu, 18 Jul 2013 07:49:01 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 3D6A821F94DC for <mboned@ietf.org>; Thu, 18 Jul 2013 07:48:55 -0700 (PDT)
Received: from unknown [144.160.20.146] (EHLO mlpd194.enaf.sfdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 65008e15.0.6393672.00-079.17770443.nbfkord-smmo06.seg.att.com (envelope-from <pt5947@att.com>);  Thu, 18 Jul 2013 14:48:55 +0000 (UTC)
X-MXL-Hash: 51e800576602d56c-c7e00404d4bb12e9f39fae750dc7082e4b1ab7d6
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r6IEms2T020288; Thu, 18 Jul 2013 10:48:54 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r6IEmk9L020100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Jul 2013 10:48:47 -0400
Received: from MISOUT7MSGHUB9B.ITServices.sbc.com (misout7msghub9b.itservices.sbc.com [144.151.223.72]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Thu, 18 Jul 2013 14:48:36 GMT
Received: from MISOUT7MSGUSR9H.ITServices.sbc.com ([144.151.223.88]) by MISOUT7MSGHUB9B.ITServices.sbc.com ([144.151.223.72]) with mapi id 14.02.0342.003; Thu, 18 Jul 2013 10:48:36 -0400
From: "TARAPORE, PERCY S" <pt5947@att.com>
To: "mboned@ietf.org" <mboned@ietf.org>, "'Leonard Giuliano' (lenny@juniper.net)" <lenny@juniper.net>
Thread-Topic: New Version Notification for draft-tarapore-mboned-multicast-cdni-03.txt
Thread-Index: AQHOgYyI4G+JopfgG0KAu+cOKGWICplqh1bQ
Date: Thu, 18 Jul 2013 14:48:36 +0000
Message-ID: <ACC789373DA69C4285B9678D0CEBF86F069BC324@MISOUT7MSGUSR9H.ITServices.sbc.com>
References: <20130715185233.17073.2652.idtracker@ietfa.amsl.com>
In-Reply-To: <20130715185233.17073.2652.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.69.170]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <pt5947@att.com>
X-SOURCE-IP: [144.160.20.146]
X-AnalysisOut: [v=2.0 cv=R5y076tX c=1 sm=0 a=Qs8R1XBwmid1qBFB/a8mmA==:17 a]
X-AnalysisOut: [=P3UzlqUZ-2sA:10 a=0sAT2sIeamgA:10 a=ofMgfj31e3cA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=IkcTkHD0fZMA:10 a=zQP7CpKOAAAA:8 a=XIqpo32R]
X-AnalysisOut: [AAAA:8 a=C88o7j4EcBAA:10 a=48vgC7mUAAAA:8 a=BE7DaeOfmE9gRO]
X-AnalysisOut: [kkMGsA:9 a=QEXdDO2ut3YA:10]
X-Mailman-Approved-At: Thu, 18 Jul 2013 12:53:31 -0700
Subject: [MBONED] FW: New Version Notification for	draft-tarapore-mboned-multicast-cdni-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: Thu, 18 Jul 2013 14:49:07 -0000

QSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LXRhcmFwb3JlLW1ib25lZC1tdWx0aWNhc3QtY2Ru
aS0wMy50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgUGVyY3kgUy4gVGFy
YXBvcmUgYW5kIHBvc3RlZCB0byB0aGUNCklFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6CSBk
cmFmdC10YXJhcG9yZS1tYm9uZWQtbXVsdGljYXN0LWNkbmkNClJldmlzaW9uOgkgMDMNClRpdGxl
OgkJIE11bHRpY2FzdGluZyBBcHBsaWNhdGlvbnMgQWNyb3NzIEludGVyLURvbWFpbiBQZWVyaW5n
IFBvaW50cw0KQ3JlYXRpb24gZGF0ZToJIDIwMTMtMDctMTUNCkdyb3VwOgkJIEluZGl2aWR1YWwg
U3VibWlzc2lvbg0KTnVtYmVyIG9mIHBhZ2VzOiAxNA0KVVJMOiAgICAgICAgICAgICBodHRwOi8v
d3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC10YXJhcG9yZS1tYm9uZWQtbXVsdGlj
YXN0LWNkbmktMDMudHh0DQpTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRm
Lm9yZy9kb2MvZHJhZnQtdGFyYXBvcmUtbWJvbmVkLW11bHRpY2FzdC1jZG5pDQpIdG1saXplZDog
ICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXRhcmFwb3JlLW1ib25lZC1t
dWx0aWNhc3QtY2RuaS0wMw0KRGlmZjogICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL3Jm
Y2RpZmY/dXJsMj1kcmFmdC10YXJhcG9yZS1tYm9uZWQtbXVsdGljYXN0LWNkbmktMDMNCg0KQWJz
dHJhY3Q6DQogICBUaGlzIGRvY3VtZW50IGV4YW1pbmVzIHRoZSBwcm9jZXNzIG9mIHRyYW5zcG9y
dGluZyBhcHBsaWNhdGlvbnMgdmlhDQogICBtdWx0aWNhc3QgYWNyb3NzIGludGVyLWRvbWFpbiBw
ZWVyaW5nIHBvaW50cy4gVGhlIG9iamVjdGl2ZSBpcyB0bw0KICAgZGVzY3JpYmUgdGhlIHNldHVw
IHByb2Nlc3MgZm9yIG11bHRpY2FzdC1iYXNlZCBkZWxpdmVyeSBhY3Jvc3MNCiAgIGFkbWluaXN0
cmF0aXZlIGRvbWFpbnMgYW5kIGRvY3VtZW50IHN1cHBvcnRpbmcgZnVuY3Rpb25hbGl0eSB0bw0K
ICAgZW5hYmxlIHRoaXMgcHJvY2Vzcy4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoN
ClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==

From gjshep@gmail.com  Tue Jul 30 07:17:32 2013
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 DF54321E80FA for <mboned@ietfa.amsl.com>; Tue, 30 Jul 2013 07:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.185
X-Spam-Level: 
X-Spam-Status: No, score=-100.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, 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 E2qTXH1qp54S for <mboned@ietfa.amsl.com>; Tue, 30 Jul 2013 07:17:32 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5203D21F9CC0 for <mboned@ietf.org>; Tue, 30 Jul 2013 07:17:17 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hi8so2409525wib.5 for <mboned@ietf.org>; Tue, 30 Jul 2013 07:17:13 -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=xc62sOrwXKcUlW0MSZXH7PWwcjnN+1oiAeNVUejEK+w=; b=XUgfNJk/zJQgT7ougnPdksXZsrOqpqvenohjwyucvURJNv1d3IwaD4OSEH4MLbM1ED /zaqe4D6efcecMan61IkE7/HDJuFGSqWqLG9eiYou1UgF21YllgD6RoL21FWH5/6T/G5 E36mC2UIDxUayFidaWMBrgD9/JWT4ClJH15yVjbIKGuTiIy5xPWEhwBG9UG9npEw2Q+j heVVKOyrVJM0Wcl711KmQGLRp0fXqeo2inpJ1Sn583VzBbjyaE+h84dtKR0z1c/KHMCE h8gFIsp2g8w9DzuzaRBwKhD0ls6dvJOfjFUgHUveiTvcI9AV5W8vdTSxwvsbSmcNJovI f5ww==
MIME-Version: 1.0
X-Received: by 10.180.149.204 with SMTP id uc12mr1096978wib.47.1375193832948;  Tue, 30 Jul 2013 07:17:12 -0700 (PDT)
Received: by 10.180.185.36 with HTTP; Tue, 30 Jul 2013 07:17:12 -0700 (PDT)
Date: Tue, 30 Jul 2013 07:17:12 -0700
Message-ID: <CABFReBrGk8NC1H7KYvtLragfdQm1CQn+-56=T-LToXBnA8tndg@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
To: "mboned@ietf.org" <mboned@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3893ae90a7604e2bb4395
Subject: [MBONED] Scribe / Jabber Scribe
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: Tue, 30 Jul 2013 14:17:33 -0000

--001a11c3893ae90a7604e2bb4395
Content-Type: text/plain; charset=ISO-8859-1

One hour before our session and we're still looking for a note taker and
jabber scribe. Please come forward and show that you care about the
operation of the group. Just being in the room doesn't count. ;-)

Thanks!,
Greg

--001a11c3893ae90a7604e2bb4395
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">One hour before our session and we&#39;re still looking for a note taker and jabber scribe. Please come forward and show that you care about the operation of the group. Just being in the room doesn&#39;t count. ;-)<div>
<br></div><div style>Thanks!,</div><div style>Greg</div><div style><br></div></div>

--001a11c3893ae90a7604e2bb4395--

From gjshep@gmail.com  Wed Jul 31 06:45:34 2013
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 AA55B11E8187 for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 06:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.391
X-Spam-Level: 
X-Spam-Status: No, score=-101.391 tagged_above=-999 required=5 tests=[AWL=1.206, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.001, 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 HmTNaedpuli6 for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 06:45:33 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 8655411E8184 for <mboned@ietf.org>; Wed, 31 Jul 2013 06:45:33 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id x55so621706wes.18 for <mboned@ietf.org>; Wed, 31 Jul 2013 06:45:32 -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=O1RnvBgV0lW18gZoMC0pELNKcFLsVqgRLURdoibMaeY=; b=n0Srv9wdOo0EssZ7RH0Y0Cce5gUZMKTj7jC/q1K/gTTt0QPsWhfaYLVo6R+Ixh+8fS 6K6/flM68ZJu7VJVOiMogaZ/Bo3xA8E7TqdgglYBJQsX3AOwYRBugwDGzkhRhoPq2HIG 5ALTBNSwpfMtrud9WbS2/JybDZp0JNtKGJbeU4eoSsSlN2VmDSLa1XOgAWM3iFQAlPpb /LbyhSN3g+gov1reINpOhdEWZn9PyU6/pWACKGnZA2MzK8SBRi/cK+K2RDh6iAMEAW65 DLyD1rSfJdaBYwMvhE302rBYHgve5fLBHNvReHHFTMsJzJbbZoS7reLZ7C88Xt7n6mKW Bo9A==
MIME-Version: 1.0
X-Received: by 10.180.149.204 with SMTP id uc12mr4296093wib.47.1375278332561;  Wed, 31 Jul 2013 06:45:32 -0700 (PDT)
Received: by 10.180.185.36 with HTTP; Wed, 31 Jul 2013 06:45:32 -0700 (PDT)
Date: Wed, 31 Jul 2013 06:45:32 -0700
Message-ID: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
To: "mboned@ietf.org" <mboned@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3893a7ad39f04e2cef0f8
Subject: [MBONED] Working Group Adoption?: draft-tarapore-mboned-multicast-cdni-03
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: Wed, 31 Jul 2013 13:45:34 -0000

--001a11c3893a7ad39f04e2cef0f8
Content-Type: text/plain; charset=ISO-8859-1

Please respond with or without your support for adoption
draft-tarapore-mboned-multicast-cdni-03<http://datatracker.ietf.org/doc/draft-tarapore-mboned-multicast-cdni/>
as
a working group item.

Thanks,
Greg

--001a11c3893a7ad39f04e2cef0f8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Please respond with or without your support for adoption=
=A0<a href=3D"http://datatracker.ietf.org/doc/draft-tarapore-mboned-multica=
st-cdni/" style=3D"font-family:arial,helvetica,clean,sans-serif;font-size:1=
3px;line-height:16px;background-color:rgb(237,245,255)">draft-tarapore-mbon=
ed-multicast-cdni-03</a>=A0as a working group item.<div>
<br></div><div>Thanks,</div><div style>Greg</div></div>

--001a11c3893a7ad39f04e2cef0f8--

From lenny@juniper.net  Wed Jul 31 09:18:13 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 091A221F90A7 for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 09:18:13 -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 WKhPmpn5alfP for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 09:18:08 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe010.messaging.microsoft.com [216.32.180.30]) by ietfa.amsl.com (Postfix) with ESMTP id 1E1FA21F9E6A for <mboned@ietf.org>; Wed, 31 Jul 2013 09:17:51 -0700 (PDT)
Received: from mail50-va3-R.bigfish.com (10.7.14.254) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.22; Wed, 31 Jul 2013 16:17:50 +0000
Received: from mail50-va3 (localhost [127.0.0.1])	by mail50-va3-R.bigfish.com (Postfix) with ESMTP id 741C64C00FB; Wed, 31 Jul 2013 16:17:50 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.52; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF01-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: VPS-19(zz98dIda00h4015Idc73hzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kz8dhz1033IL17326ah1de096h8275dh1de097hz2fh2a8h668h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1155h)
Received-SPF: pass (mail50-va3: domain of juniper.net designates 66.129.224.52 as permitted sender) client-ip=66.129.224.52; envelope-from=lenny@juniper.net; helo=P-EMF01-SAC.jnpr.net ; SAC.jnpr.net ; 
Received: from mail50-va3 (localhost.localdomain [127.0.0.1]) by mail50-va3 (MessageSwitch) id 1375287469116768_14034; Wed, 31 Jul 2013 16:17:49 +0000 (UTC)
Received: from VA3EHSMHS040.bigfish.com (unknown [10.7.14.248])	by mail50-va3.bigfish.com (Postfix) with ESMTP id 0E0651E01B1; Wed, 31 Jul 2013 16:17:49 +0000 (UTC)
Received: from P-EMF01-SAC.jnpr.net (66.129.224.52) by VA3EHSMHS040.bigfish.com (10.7.99.50) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 31 Jul 2013 16:17:48 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF01-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 31 Jul 2013 09:17:48 -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 r6VG4bL08609; Wed, 31 Jul 2013 09:04:42 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 4812011446;  Wed, 31 Jul 2013 09:04:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id C6FA61141B; Wed, 31 Jul 2013 09:04:34 -0700 (PDT)
Date: Wed, 31 Jul 2013 09:04:34 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Greg Shepherd <gjshep@gmail.com>
In-Reply-To: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
Message-ID: <20130731090421.J85519@eng-mail01.juniper.net>
References: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Working Group Adoption?: draft-tarapore-mboned-multicast-cdni-03
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, 31 Jul 2013 16:18:13 -0000

I support


On Wed, 31 Jul 2013, Greg Shepherd wrote:

-) Please respond with or without your support for adoption
-) draft-tarapore-mboned-multicast-cdni-03<http://datatracker.ietf.org/doc/draft-tarapore-mboned-multicast-cdni/>
-) as
-) a working group item.
-) 
-) Thanks,
-) Greg
-) 


From pt5947@att.com  Wed Jul 31 10:05:36 2013
Return-Path: <pt5947@att.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 98E4421F9AFE for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 10:05:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hWnNi31V6MGS for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 10:05:30 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id 48A9621F9FC8 for <mboned@ietf.org>; Wed, 31 Jul 2013 10:05:30 -0700 (PDT)
Received: from unknown [144.160.20.146] (EHLO nbfkord-smmo07.seg.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.15.0-1) with ESMTP id ad349f15.596da940.5059982.00-511.13988682.nbfkord-smmo07.seg.att.com (envelope-from <pt5947@att.com>);  Wed, 31 Jul 2013 17:05:30 +0000 (UTC)
X-MXL-Hash: 51f943da0743e2c7-86e13a691c3e5a9507e929a9586986d7c0d21c44
Received: from unknown [144.160.20.146] (EHLO mlpd194.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 8d349f15.0.5059970.00-478.13988623.nbfkord-smmo07.seg.att.com (envelope-from <pt5947@att.com>);  Wed, 31 Jul 2013 17:05:28 +0000 (UTC)
X-MXL-Hash: 51f943d85b7fb3d6-02eecce335565f70c98185626b7e150bcfeec072
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r6VH5RpD018745; Wed, 31 Jul 2013 13:05:27 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r6VH5OW9018695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Jul 2013 13:05:26 -0400
Received: from MISOUT7MSGHUB9D.ITServices.sbc.com (misout7msghub9d.itservices.sbc.com [144.151.223.93]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Wed, 31 Jul 2013 17:05:12 GMT
Received: from MISOUT7MSGUSR9H.ITServices.sbc.com ([144.151.223.88]) by MISOUT7MSGHUB9D.ITServices.sbc.com ([144.151.223.93]) with mapi id 14.02.0342.003; Wed, 31 Jul 2013 13:05:12 -0400
From: "TARAPORE, PERCY S" <pt5947@att.com>
To: "gjshep@gmail.com" <gjshep@gmail.com>, "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] Working Group Adoption?: draft-tarapore-mboned-multicast-cdni-03
Thread-Index: AQHOjfRDMUzfOPHt302XZiYtT3Wmd5l/BB3Q
Date: Wed, 31 Jul 2013 17:05:12 +0000
Message-ID: <ACC789373DA69C4285B9678D0CEBF86F069BEE30@MISOUT7MSGUSR9H.ITServices.sbc.com>
References: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
In-Reply-To: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.145.44]
Content-Type: multipart/alternative; boundary="_000_ACC789373DA69C4285B9678D0CEBF86F069BEE30MISOUT7MSGUSR9H_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <pt5947@att.com>
X-SOURCE-IP: [144.160.20.146]
X-AnalysisOut: [v=2.0 cv=YP8oP26x c=1 sm=0 a=Qs8R1XBwmid1qBFB/a8mmA==:17 a]
X-AnalysisOut: [=-UC7Dr3FgN8A:10 a=gjAo_UbNJIQA:10 a=ofMgfj31e3cA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=zQP7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=dzO8Mw1UQ]
X-AnalysisOut: [c4A:10 a=48vgC7mUAAAA:8 a=6PFQR8dw91e6HwHAU-IA:9 a=CjuIK1q]
X-AnalysisOut: [_8ugA:10 a=lZB815dzVvQA:10 a=M0kP8aE5a_8A:10 a=ggo9SabEGm4]
X-AnalysisOut: [A:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=asXI5FO7wPKXP2cEU]
X-AnalysisOut: [9IA:9 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:1]
X-AnalysisOut: [0 a=frz4AuCg-hUA:10 a=kaYXlqPMx9rUBwhZ:21]
Subject: Re: [MBONED] Working Group Adoption?:	draft-tarapore-mboned-multicast-cdni-03
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, 31 Jul 2013 17:05:36 -0000

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

I support.

Percy S. Tarapore

From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of=
 Greg Shepherd
Sent: Wednesday, July 31, 2013 9:46 AM
To: mboned@ietf.org
Subject: [MBONED] Working Group Adoption?: draft-tarapore-mboned-multicast-=
cdni-03

Please respond with or without your support for adoption draft-tarapore-mbo=
ned-multicast-cdni-03<http://datatracker.ietf.org/doc/draft-tarapore-mboned=
-multicast-cdni/> as a working group item.

Thanks,
Greg

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Book Antiqua";
	panose-1:2 4 6 2 5 3 5 3 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Book Antiqua","serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:13.0pt;font-family:&quot;Bo=
ok Antiqua&quot;,&quot;serif&quot;;color:#1F497D">I support.<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.0pt;font-family:&quot;Bo=
ok Antiqua&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.0pt;font-family:&quot;Bo=
ok Antiqua&quot;,&quot;serif&quot;;color:#1F497D">Percy S. Tarapore<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.0pt;font-family:&quot;Bo=
ok Antiqua&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> mboned-b=
ounces@ietf.org [mailto:mboned-bounces@ietf.org]
<b>On Behalf Of </b>Greg Shepherd<br>
<b>Sent:</b> Wednesday, July 31, 2013 9:46 AM<br>
<b>To:</b> mboned@ietf.org<br>
<b>Subject:</b> [MBONED] Working Group Adoption?: draft-tarapore-mboned-mul=
ticast-cdni-03<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Please respond with or without your support for adop=
tion&nbsp;<a href=3D"http://datatracker.ietf.org/doc/draft-tarapore-mboned-=
multicast-cdni/"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&qu=
ot;,&quot;sans-serif&quot;;background:#EDF5FF">draft-tarapore-mboned-multic=
ast-cdni-03</span></a>&nbsp;as
 a working group item.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Greg<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_ACC789373DA69C4285B9678D0CEBF86F069BEE30MISOUT7MSGUSR9H_--

From rs1983@att.com  Wed Jul 31 13:06:33 2013
Return-Path: <rs1983@att.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 0FCEF21F999E for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 13:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.165
X-Spam-Level: 
X-Spam-Status: No, score=-6.165 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SeE2eYlyXO9p for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 13:06:17 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 7454221F9EF5 for <mboned@ietf.org>; Wed, 31 Jul 2013 13:06:09 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO nbfkord-smmo06.seg.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.15.0-1) with ESMTP id 13e69f15.2aaad4c0d940.6667030.00-547.18366949.nbfkord-smmo06.seg.att.com (envelope-from <rs1983@att.com>);  Wed, 31 Jul 2013 20:06:09 +0000 (UTC)
X-MXL-Hash: 51f96e3125a60986-2c1a4a6cc1c851a8fb95c0666695155f0f895fbd
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 72e69f15.0.6666992.00-267.18366633.nbfkord-smmo06.seg.att.com (envelope-from <rs1983@att.com>);  Wed, 31 Jul 2013 20:06:00 +0000 (UTC)
X-MXL-Hash: 51f96e280280c3f3-9a88fc140a608cece8a19abb1a0b6bf7e4b54c81
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r6VK5xaH014029; Wed, 31 Jul 2013 16:05:59 -0400
Received: from alpi131.aldc.att.com (alpi131.aldc.att.com [130.8.218.69]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r6VK5rt8013969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Jul 2013 16:05:56 -0400
Received: from GAALPA1MSGHUB9B.ITServices.sbc.com (gaalpa1msghub9b.itservices.sbc.com [130.8.36.88]) by alpi131.aldc.att.com (RSA Interceptor); Wed, 31 Jul 2013 20:05:29 GMT
Received: from gaalpa1msgusr9c.ITServices.sbc.com ([130.8.36.60]) by GAALPA1MSGHUB9B.ITServices.sbc.com ([130.8.36.88]) with mapi id 14.02.0342.003; Wed, 31 Jul 2013 16:05:28 -0400
From: "SAYKO, ROBERT J" <rs1983@att.com>
To: "gjshep@gmail.com" <gjshep@gmail.com>, "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] Working Group Adoption?: draft-tarapore-mboned-multicast-cdni-03
Thread-Index: AQHOjfREKdFDliyw+ESCpXaqm95dypl/NqGg
Date: Wed, 31 Jul 2013 20:05:28 +0000
Message-ID: <9B30768B8155174FB7C6B21ABDCD24C026B338B5@GAALPA1MSGUSR9C.ITServices.sbc.com>
References: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
In-Reply-To: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.158.149]
Content-Type: multipart/alternative; boundary="_000_9B30768B8155174FB7C6B21ABDCD24C026B338B5GAALPA1MSGUSR9C_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <rs1983@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=2.0 cv=WbS7nTdX c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=0fs1w2jjP1QA:10 a=gjAo_UbNJIQA:10 a=ofMgfj31e3cA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=zQP7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=dzO8Mw1UQ]
X-AnalysisOut: [c4A:10 a=48vgC7mUAAAA:8 a=6PFQR8dw91e6HwHAU-IA:9 a=CjuIK1q]
X-AnalysisOut: [_8ugA:10 a=lZB815dzVvQA:10 a=0OPL69xBjn8A:10 a=ggo9SabEGm4]
X-AnalysisOut: [A:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=asXI5FO7wPKXP2cEU]
X-AnalysisOut: [9IA:9 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:1]
X-AnalysisOut: [0 a=frz4AuCg-hUA:10 a=QFOZmqExuf3Ysm1C:21]
Subject: Re: [MBONED] Working Group Adoption?:	draft-tarapore-mboned-multicast-cdni-03
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, 31 Jul 2013 20:06:33 -0000

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

I support adoption.

From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of=
 Greg Shepherd
Sent: Wednesday, July 31, 2013 9:46 AM
To: mboned@ietf.org
Subject: [MBONED] Working Group Adoption?: draft-tarapore-mboned-multicast-=
cdni-03

Please respond with or without your support for adoption draft-tarapore-mbo=
ned-multicast-cdni-03<http://datatracker.ietf.org/doc/draft-tarapore-mboned=
-multicast-cdni/> as a working group item.

Thanks,
Greg

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I support adoption.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> mboned-b=
ounces@ietf.org [mailto:mboned-bounces@ietf.org]
<b>On Behalf Of </b>Greg Shepherd<br>
<b>Sent:</b> Wednesday, July 31, 2013 9:46 AM<br>
<b>To:</b> mboned@ietf.org<br>
<b>Subject:</b> [MBONED] Working Group Adoption?: draft-tarapore-mboned-mul=
ticast-cdni-03<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Please respond with or without your support for adop=
tion&nbsp;<a href=3D"http://datatracker.ietf.org/doc/draft-tarapore-mboned-=
multicast-cdni/"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&qu=
ot;,&quot;sans-serif&quot;;background:#EDF5FF">draft-tarapore-mboned-multic=
ast-cdni-03</span></a>&nbsp;as
 a working group item.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Greg<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_9B30768B8155174FB7C6B21ABDCD24C026B338B5GAALPA1MSGUSR9C_--

From asaeda@sfc.wide.ad.jp  Wed Jul 31 14:43:51 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
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 A47D021F9AE2 for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 14:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l-d4A6vb4Fz5 for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 14:43:51 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id AA3A321F9D50 for <mboned@ietf.org>; Wed, 31 Jul 2013 14:43:50 -0700 (PDT)
Received: from localhost (dhcp-4034.meeting.ietf.org [130.129.64.52]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 47527278093 for <mboned@ietf.org>; Thu,  1 Aug 2013 06:43:43 +0900 (JST)
Date: Wed, 31 Jul 2013 23:43:41 +0200 (CEST)
Message-Id: <20130731.234341.230673991.asaeda@sfc.wide.ad.jp>
To: mboned@ietf.org
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
References: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [MBONED] Working Group Adoption?: draft-tarapore-mboned-multicast-cdni-03
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, 31 Jul 2013 21:43:51 -0000

> Please respond with or without your support for adoption
> draft-tarapore-mboned-multicast-cdni-03<http://datatracker.ietf.org/doc/draft-tarapore-mboned-multicast-cdni/>
> as
> a working group item.

Support.
--
Hitoshi Asaeda

From hou@cisco.com  Wed Jul 31 15:49:23 2013
Return-Path: <hou@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 878FC21F9D38 for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 15:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 2hqcjVYQzYAM for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 15:49:18 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 3C14521F9D05 for <mboned@ietf.org>; Wed, 31 Jul 2013 15:49:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2272; q=dns/txt; s=iport; t=1375310957; x=1376520557; h=from:to:subject:date:message-id:mime-version; bh=V2Tk2tb4ddiMuzKVxrnVMfaKxPVCk0GJptC7uCM6u94=; b=jVEFcei1d9qcPTx+9XMcQ6p2Nx+MOdlCFyO1UXh3ZLSOaR8xm2sEds/g SkeptGuJqN9FLryZ0X6C/YyHamvd82aIDofaBhhpGzdKGhSBRy/o+vb0e vhJ7m6yQb14IPoPAQaOUyFW+NEaSSrmKaNaD+IQOSwda5tCNcdOlIV1IV 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAPGT+VGtJXG9/2dsb2JhbABbgkJEgQW+NIEaFnSCJgEEgQsBDAEdVicEG4gImEWgVI9Wg1BzA6ksgxSCKg
X-IronPort-AV: E=Sophos;i="4.89,790,1367971200";  d="scan'208,217";a="241992109"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-8.cisco.com with ESMTP; 31 Jul 2013 22:49:15 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r6VMnE9o025804 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mboned@ietf.org>; Wed, 31 Jul 2013 22:49:14 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.244]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Wed, 31 Jul 2013 17:49:14 -0500
From: "Heidi Ou (hou)" <hou@cisco.com>
To: "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: Question on draft-ietf-mboned-auto-multicast-15
Thread-Index: AQHOjkAuhnZpnAZloUGNJCtJSrXhiw==
Date: Wed, 31 Jul 2013 22:49:14 +0000
Message-ID: <716547F7B399274C9FE8C1CFBC6C95C92A5814FD@xmb-rcd-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.154.209.98]
Content-Type: multipart/alternative; boundary="_000_716547F7B399274C9FE8C1CFBC6C95C92A5814FDxmbrcdx06ciscoc_"
MIME-Version: 1.0
Subject: [MBONED] Question on draft-ietf-mboned-auto-multicast-15
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, 31 Jul 2013 22:49:23 -0000

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

Hi Greg,

I have one question regarding UDP port  in draft-ietf-mboned-auto-multicast=
-15

Can a Relay and a Gateway  build multiple UDP sessions for "multicast data"=
?

The context in section 5.1 indicates that the destination UDP port in Messa=
ge
Type 6 (multicast data)  has to match the source UDP port in Message Type 5
(membership update).  And that also needs to match the source UDP port in
Message Type 3 (Request).

It seems to imply that only one UDP session for "multicast data" can be for=
med
between a Relay/Gateway pair?


Thanks
- Heidi




--_000_716547F7B399274C9FE8C1CFBC6C95C92A5814FDxmbrcdx06ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-ID: <AD71910919B7AB4DA574604584BF86D7@emea.cisco.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; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Hi Greg,</div>
<div><br>
</div>
<div>I have one question regarding UDP port &nbsp;in draft-ietf-mboned-auto=
-multicast-15</div>
<div><br>
</div>
<div>Can a Relay and a Gateway &nbsp;build multiple UDP sessions for &quot;=
multicast data&quot;? &nbsp;</div>
<div>&nbsp;</div>
<div>The context in section 5.1 indicates that the destination UDP port in =
Message&nbsp;</div>
<div>Type 6 (multicast data) &nbsp;has to match the source UDP port in Mess=
age Type 5&nbsp;</div>
<div>(membership update). &nbsp;And that also needs to match the source UDP=
 port in</div>
<div>Message Type 3 (Request). &nbsp;</div>
<div><br>
</div>
<div>It seems to imply that only one UDP session for &quot;multicast data&q=
uot; can be formed</div>
<div>between a Relay/Gateway pair?</div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks</div>
<div>- Heidi</div>
<div><br>
</div>
<div><br>
</div>
<div>&nbsp;</div>
</body>
</html>

--_000_716547F7B399274C9FE8C1CFBC6C95C92A5814FDxmbrcdx06ciscoc_--

From juampe.cerezo@gmail.com  Wed Jul 31 23:45:04 2013
Return-Path: <juampe.cerezo@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 C058421F9D42 for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 23:45:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l-cqNLVJzbkU for <mboned@ietfa.amsl.com>; Wed, 31 Jul 2013 23:45:04 -0700 (PDT)
Received: from mail-ea0-x229.google.com (mail-ea0-x229.google.com [IPv6:2a00:1450:4013:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 0503F21F9D28 for <mboned@ietf.org>; Wed, 31 Jul 2013 23:45:03 -0700 (PDT)
Received: by mail-ea0-f169.google.com with SMTP id z7so775252eaf.14 for <mboned@ietf.org>; Wed, 31 Jul 2013 23:45:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=KRbcIDmDmzxGNuvjaEhHas088VjYYBUUOAZuhL/IHgQ=; b=d1yCm/fcb4VAjy/BDxOncq4x8cz7sKhtYh0Ct/btYfUINwpmFrnXiupUBAVfJ6GnJC 4/YmRLWArauhj+Tt9KHp200ambnkc2I+ofTbW9F9BENAwh+yPD6HQcM+VFKtZbmL1ZA2 kb/5yuY2M92ojUpdgPbKYI7aeclJCDCNlTI6mBmKGfgHKy86xAt3/bBbcgi+8moFPW2h r8o4IuGwOEDaeDw0g47D2KQyXGHoWyZVRnVDY3+61TQJDvGUPw4tJ1IQibNZCTsglWTg zkRcUcf8pjswDomUm6doILEDCakElunVXUECcOt0icYRDQoLQQ0VCTF2k9qosT8LMMb1 hMjw==
X-Received: by 10.15.27.195 with SMTP id p43mr129718eeu.5.1375339502170; Wed, 31 Jul 2013 23:45:02 -0700 (PDT)
Received: from ?IPv6:2001:ac0::972:8ffc:6de:3a33? ([2001:ac0::972:8ffc:6de:3a33]) by mx.google.com with ESMTPSA id bj46sm1889252eeb.13.2013.07.31.23.45.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 31 Jul 2013 23:45:00 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Juan-Pedro Cerezo Martin <juampe.cerezo@gmail.com>
In-Reply-To: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
Date: Thu, 1 Aug 2013 08:44:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7BFC481-D005-452E-BE58-7DCBBD9EF288@gmail.com>
References: <CABFReBpVyWJMf55WjC++fnPk_uubK9nyNLJJhDnRHuzSM20dmQ@mail.gmail.com>
To: gjshep@gmail.com
X-Mailer: Apple Mail (2.1508)
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Working Group Adoption?: draft-tarapore-mboned-multicast-cdni-03
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, 01 Aug 2013 06:45:04 -0000

Support.

JP Cerezo

On Jul 31, 2013, at 3:45 PM, Greg Shepherd <gjshep@gmail.com> wrote:

> Please respond with or without your support for adoption =
draft-tarapore-mboned-multicast-cdni-03 as a working group item.
>=20
> Thanks,
> Greg
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

