
From hou@cisco.com  Thu Jan  6 16:48:56 2011
Return-Path: <hou@cisco.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 775013A6E41 for <pim@core3.amsl.com>; Thu,  6 Jan 2011 16:48:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.135
X-Spam-Level: 
X-Spam-Status: No, score=-7.135 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JM3w6Q3RXIWG for <pim@core3.amsl.com>; Thu,  6 Jan 2011 16:48:49 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 9C73F3A6E23 for <pim@ietf.org>; Thu,  6 Jan 2011 16:48:49 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiIGAMvxJU2rR7H+/2dsb2JhbACCKYQ9jmuNeFQCc6RzmDKCdIJYBIRnhiKDI4R2
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 07 Jan 2011 00:50:56 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p070oukv019862; Fri, 7 Jan 2011 00:50:56 GMT
Received: from xmb-sjc-231.amer.cisco.com ([128.107.191.73]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 6 Jan 2011 16:50:56 -0800
Received: from 128.107.163.46 ([128.107.163.46]) by xmb-sjc-231.amer.cisco.com ([128.107.191.73]) with Microsoft Exchange Server HTTP-DAV ;  Fri,  7 Jan 2011 00:50:55 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Thu, 06 Jan 2011 16:51:04 -0800
From: hou <hou@cisco.com>
To: Liuhui <helen.liu@huawei.com>, "Mike McBride (mmcbride)" <mmcbride@cisco.com>, "Yiqun Cai (ycai)" <ycai@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Message-ID: <C94BA378.AB0E%hou@cisco.com>
Thread-Topic: [pim] draft-ietf-pim-mtid-05 wglc
Thread-Index: ActapValia8GBshU6kuohlJ+S90GTg6/v+GwAgBdqlAEF8pJjg==
In-Reply-To: <283829E9EFBF22459301B900C9A2E434EF6CD4@SZXEML501-MBX.china.huawei.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3377177464_915637"
X-OriginalArrivalTime: 07 Jan 2011 00:50:56.0238 (UTC) FILETIME=[F15828E0:01CBAE04]
Subject: Re: [pim] draft-ietf-pim-mtid-05 wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 00:48:56 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3377177464_915637
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

    [H] Thanks for your review comments. Reply inline


On 12/16/10 8:58 PM, "Liuhui" <helen.liu@huawei.com> wrote:

> A few comments on the draft:
>=20
> The Introduction only mentions the multiple topology over "separate netwo=
rk
> paths". Is this the only case or can different multicast topologies be bu=
ilt
> over the same physical link? This should be clarified, as the referenced
> [5120] does.=20
>=20
> [H] As mentioned in the =B3Introduction=B2, the main purpose of this
       [H] draft is to prevent multicast traffic loss in case of  single
       [H] network segment failure. Building multicast topologies over
> [H] the same physical network will be against the purpose, but
> [H] can be done if an operator chooses to do so
>=20
> Besides, it might be better to give some explanations for the mtid attrib=
ute's
> influence on forwarding plane, whether it changes the forwarding state/ru=
le or
> not.
>=20
> [H] At the end of Section 2, we mention that =B3The draft does not introduc=
e any
> [H] change to the RPF check procedure used to verify the incoming interfa=
ce
> [H] when a packet is forwarded=B2
>=20
>=20
> Finally, not very clear on the using of two group address G1 and G2 (in
> Introduction section):
> - Since mtid is used to identify the different topology, why additional
> differentiation of group address is needed.
>=20
> [H] mtid and group address servers different purposes: mtid is the path
> [H] identifier, while the group address defines the content that needs to=
 be
> [H] delivered via the path.
>=20
> - Using two addresses to identify the same multicast stream, is it easy t=
o be
> deployed in IPTV network, where group address   often corresponds with a
> channel.
>=20
> [H] In order to achieve multicast resilience as an end-to-end solution
> [H] for IPTV, or other applications,  there will be work from other aspec=
ts,
> [H] besides the transport/network layer approach, as this draft is focusi=
ng
> on.
> [H] The channel to group address mapping actually fits the draft very wel=
l,
> [H] however, the channel/group split/merge functionality is beyond the sc=
ope
> [H] of this draft.
>=20
>    =20
> thanks
> - Heidi
>=20
>=20
> Thanks,
> Liu Hui
>=20
>> > -----Original Message-----
>> > From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of =
Mike
>> > McBride (mmcbride)
>> > Sent: Tuesday, December 07, 2010 8:24 AM
>> > To: Yiqun Cai (ycai); pim@ietf.org
>> > Subject: [pim] draft-ietf-pim-mtid-05 wglc
>> >=20
>>> > > Mike and Stig,  will we need another last call?
>> >=20
>> > Yes, sorry for the delay. Today begins another 2 week wglc for
>> > http://www.ietf.org/id/draft-ietf-pim-mtid-05.txt
>> >=20
>> > Please review the draft and let us know if you support sending it to t=
he
>> > iesg.
>> >=20
>> > thanks,
>> > mike
>> >=20
>>> > > -----Original Message-----
>>> > > From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf =
Of
>>> > > Yiqun Cai (ycai)
>>> > > Sent: Wednesday, September 22, 2010 3:27 PM
>>> > > To: pim@ietf.org
>>> > > Subject: Re: [pim] I-D Action:draft-ietf-pim-mtid-05.txt
>>> > >
>>> > >
>>> > > Chairs, Dimitri,  and WG,
>>> > >
>>> > > The latest update incorporates the comment received from the
>> > discussion
>>> > > during the Last Call.
>>> > >
>>> > > Please review and comment.
>>> > >
>>> > > Mike and Stig,  will we need another last call?
>>> > >
>>> > > Thanks.
>>> > >
>>> > >
>>> > > On 9/22/10 3:00 PM, "Internet-Drafts@ietf.org" <Internet-
>>> > > Drafts@ietf.org>
>>> > > wrote:
>>> > >
>>>> > > > A New Internet-Draft is available from the on-line Internet-Draf=
ts
>>>> > > > directories.
>>>> > > > This draft is a work item of the Protocol Independent Multicast
>>> > > Working Group
>>>> > > > of the IETF.
>>>> > > >
>>>> > > >
>>>> > > > Title           : PIM Multi-Topology ID (MT-ID) Join-Attribute
>>>> > > > Author(s)       : Y. Cai, H. Ou
>>>> > > > Filename        : draft-ietf-pim-mtid-05.txt
>>>> > > > Pages           : 11
>>>> > > > Date            : 2010-09-22
>>>> > > >
>>>> > > > This document introduces a new type of PIM Join Attribute that
>>>> > > > extends PIM signaling to identify a topology that should be used
>> > when
>>>> > > > constructing a particular multicast distribution tree.
>>>> > > >
>>>> > > > A URL for this Internet-Draft is:
>>>> > > > http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-05.txt
>>>> > > >
>>>> > > > Internet-Drafts are also available by anonymous FTP at:
>>>> > > > ftp://ftp.ietf.org/internet-drafts/
>>>> > > >
>>>> > > > Below is the data which will enable a MIME compliant mail reader
>>>> > > > implementation to automatically retrieve the ASCII version of th=
e
>>>> > > > Internet-Draft.
>>>> > > > _______________________________________________
>>>> > > > pim mailing list
>>>> > > > pim@ietf.org
>>>> > > > https://www.ietf.org/mailman/listinfo/pim
>>> > >
>>> > >
>>> > > --
>>> > > Yiqun
>>> > >
>>> > > _______________________________________________
>>> > > pim mailing list
>>> > > pim@ietf.org
>>> > > https://www.ietf.org/mailman/listinfo/pim
>> > _______________________________________________
>> > pim mailing list
>> > pim@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pim
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


--B_3377177464_915637
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [pim] draft-ietf-pim-mtid-05 wglc</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:10pt'> &nbsp;=
&nbsp;<FONT COLOR=3D"#0000FF"> [H] Thanks for your review comments. Reply inli=
ne<BR>
</FONT><BR>
<BR>
On 12/16/10 8:58 PM, &quot;Liuhui&quot; &lt;<a href=3D"helen.liu@huawei.com">=
helen.liu@huawei.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:10pt'>A few comments on the draft:<BR>
<BR>
The Introduction only mentions the multiple topology over &quot;separate ne=
twork paths&quot;. Is this the only case or can different multicast topologi=
es be built over the same physical link? This should be clarified, as the re=
ferenced [5120] does. <BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] As mentioned in the &#8220;Introduction&#8221;, t=
he main purpose of this<BR>
</FONT></SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><S=
PAN STYLE=3D'font-size:10pt'><FONT COLOR=3D"#0000FF"> &nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;[H] draft is to prevent multicast traffic loss in case of &nbsp;si=
ngle<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[H] network segment failure. Buil=
ding multicast topologies over<BR>
</FONT></SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SP=
AN STYLE=3D'font-size:10pt'><FONT COLOR=3D"#0000FF">[H] the same physical networ=
k will be against the purpose, but<BR>
[H] can be done if an operator chooses to do so<BR>
</FONT><BR>
Besides, it might be better to give some explanations for the mtid attribut=
e's influence on forwarding plane, whether it changes the forwarding state/r=
ule or not.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] At the end of Section 2, we mention that &#8220;T=
he draft does not introduce any <BR>
[H] change to the RPF check procedure used to verify the incoming interface=
<BR>
[H] when a packet is forwarded&#8221;<BR>
</FONT><BR>
<BR>
Finally, not very clear on the using of two group address G1 and G2 (in Int=
roduction section): <BR>
- Since mtid is used to identify the different topology, why additional dif=
ferentiation of group address is needed.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] mtid and group address servers different purposes=
: mtid is the path<BR>
[H] identifier, while the group address defines the content that needs to b=
e<BR>
[H] delivered via the path. <BR>
</FONT><BR>
- Using two addresses to identify the same multicast stream, is it easy to =
be deployed in IPTV network, where group address &nbsp;&nbsp;often correspon=
ds with a channel.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] In order to achieve multicast resilience as an en=
d-to-end solution<BR>
[H] for IPTV, or other applications, &nbsp;there will be work from other as=
pects,<BR>
[H] besides the transport/network layer approach, as this draft is focusing=
 on.<BR>
[H] The channel to group address mapping actually fits the draft very well,=
<BR>
[H] however, the channel/group split/merge functionality is beyond the scop=
e<BR>
[H] of this draft.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;<BR>
thanks<BR>
- Heidi<BR>
</FONT><BR>
<BR>
Thanks,<BR>
Liu Hui<BR>
<BR>
&gt; -----Original Message-----<BR>
&gt; From: <a href=3D"pim-bounces@ietf.org">pim-bounces@ietf.org</a> [<a href=
=3D"mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>] On Behalf Of=
 Mike<BR>
&gt; McBride (mmcbride)<BR>
&gt; Sent: Tuesday, December 07, 2010 8:24 AM<BR>
&gt; To: Yiqun Cai (ycai); <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; Subject: [pim] draft-ietf-pim-mtid-05 wglc<BR>
&gt; <BR>
&gt; &gt; Mike and Stig, &nbsp;will we need another last call?<BR>
&gt; <BR>
&gt; Yes, sorry for the delay. Today begins another 2 week wglc for<BR>
&gt; <a href=3D"http://www.ietf.org/id/draft-ietf-pim-mtid-05.txt">http://www=
.ietf.org/id/draft-ietf-pim-mtid-05.txt</a><BR>
&gt; <BR>
&gt; Please review the draft and let us know if you support sending it to t=
he<BR>
&gt; iesg.<BR>
&gt; <BR>
&gt; thanks,<BR>
&gt; mike<BR>
&gt; <BR>
&gt; &gt; -----Original Message-----<BR>
&gt; &gt; From: <a href=3D"pim-bounces@ietf.org">pim-bounces@ietf.org</a> [<a=
 href=3D"mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>] On Beha=
lf Of<BR>
&gt; &gt; Yiqun Cai (ycai)<BR>
&gt; &gt; Sent: Wednesday, September 22, 2010 3:27 PM<BR>
&gt; &gt; To: <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; &gt; Subject: Re: [pim] I-D Action:draft-ietf-pim-mtid-05.txt<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; Chairs, Dimitri, &nbsp;and WG,<BR>
&gt; &gt;<BR>
&gt; &gt; The latest update incorporates the comment received from the<BR>
&gt; discussion<BR>
&gt; &gt; during the Last Call.<BR>
&gt; &gt;<BR>
&gt; &gt; Please review and comment.<BR>
&gt; &gt;<BR>
&gt; &gt; Mike and Stig, &nbsp;will we need another last call?<BR>
&gt; &gt;<BR>
&gt; &gt; Thanks.<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; On 9/22/10 3:00 PM, &quot;<a href=3D"Internet-Drafts@ietf.org">Inte=
rnet-Drafts@ietf.org</a>&quot; &lt;Internet-<BR>
&gt; &gt; <a href=3D"Drafts@ietf.org">Drafts@ietf.org</a>&gt;<BR>
&gt; &gt; wrote:<BR>
&gt; &gt;<BR>
&gt; &gt; &gt; A New Internet-Draft is available from the on-line Internet-=
Drafts<BR>
&gt; &gt; &gt; directories.<BR>
&gt; &gt; &gt; This draft is a work item of the Protocol Independent Multic=
ast<BR>
&gt; &gt; Working Group<BR>
&gt; &gt; &gt; of the IETF.<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Title &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;: PIM Multi-Topology ID (MT-ID) Join-Attribute<BR>
&gt; &gt; &gt; Author(s) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Y. Cai, H. O=
u<BR>
&gt; &gt; &gt; Filename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-i=
etf-pim-mtid-05.txt<BR>
&gt; &gt; &gt; Pages &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;: 11<BR>
&gt; &gt; &gt; Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;: 2010-09-22<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; This document introduces a new type of PIM Join Attribute th=
at<BR>
&gt; &gt; &gt; extends PIM signaling to identify a topology that should be =
used<BR>
&gt; when<BR>
&gt; &gt; &gt; constructing a particular multicast distribution tree.<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; A URL for this Internet-Draft is:<BR>
&gt; &gt; &gt; <a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-pim-=
mtid-05.txt">http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-05.txt<=
/a><BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Internet-Drafts are also available by anonymous FTP at:<BR>
&gt; &gt; &gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf=
.org/internet-drafts/</a><BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Below is the data which will enable a MIME compliant mail re=
ader<BR>
&gt; &gt; &gt; implementation to automatically retrieve the ASCII version o=
f the<BR>
&gt; &gt; &gt; Internet-Draft.<BR>
&gt; &gt; &gt; _______________________________________________<BR>
&gt; &gt; &gt; pim mailing list<BR>
&gt; &gt; &gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://=
www.ietf.org/mailman/listinfo/pim</a><BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; --<BR>
&gt; &gt; Yiqun<BR>
&gt; &gt;<BR>
&gt; &gt; _______________________________________________<BR>
&gt; &gt; pim mailing list<BR>
&gt; &gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.i=
etf.org/mailman/listinfo/pim</a><BR>
&gt; _______________________________________________<BR>
&gt; pim mailing list<BR>
&gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.o=
rg/mailman/listinfo/pim</a><BR>
_______________________________________________<BR>
pim mailing list<BR>
<a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/ma=
ilman/listinfo/pim</a><BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3377177464_915637--


From bernat@luffy.cx  Wed Jan  5 10:36:54 2011
Return-Path: <bernat@luffy.cx>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDCC73A6C74 for <pim@core3.amsl.com>; Wed,  5 Jan 2011 10:36:54 -0800 (PST)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1D36eVL7p317 for <pim@core3.amsl.com>; Wed,  5 Jan 2011 10:36:52 -0800 (PST)
Received: from bart.luffy.cx (bart.luffy.cx [IPv6:2a01:198:201::7]) by core3.amsl.com (Postfix) with ESMTP id 536FF3A6BE9 for <pim@ietf.org>; Wed,  5 Jan 2011 10:36:52 -0800 (PST)
Received: by bart.luffy.cx (Postfix, from userid 65534) id E39DE141E1; Wed,  5 Jan 2011 19:38:56 +0100 (CET)
Received: from neo.luffy.cx (cl-350.bru-01.be.sixxs.net [IPv6:2001:6f8:202:15d::2]) by bart.luffy.cx (Postfix) with ESMTPS id 857BE1409D for <pim@ietf.org>; Wed,  5 Jan 2011 19:38:56 +0100 (CET)
Received: by neo.luffy.cx (Postfix, from userid 500) id 76BAE14DF; Wed,  5 Jan 2011 19:38:55 +0100 (CET)
From: Vincent Bernat <bernat@luffy.cx>
To: pim@ietf.org
Organization: One Piece
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (x86_64-pc-linux-gnu)
X-PGP-KeyID: 0xF22A794E
X-PGP-Fingerprint: 5854 AF2B 65B2 0E96 2161  E32B 285B D7A1 F22A 794E
Date: Wed, 05 Jan 2011 19:38:55 +0100
Message-ID: <m3ipy3tcu8.fsf@neo.luffy.cx>
MIME-Version: 1.0
Content-Type: text/plain
X-Mailman-Approved-At: Fri, 07 Jan 2011 13:32:26 -0800
Subject: [pim] pimd and high availability/performance
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 18:58:21 -0000

Hi!

I would like  to use pimd in network where  routers share three distinct
networks for  redundancy and performance  purpose. For unicast,  OSPF is
running  allowing routers  to  have three  available  routes to  contact
another router. Moreover,  each router has a backup  that will take over
its role in case of failure.

#v+
 R 1 R 2 R 3 R 4 R 5 R 6
 ||| ||| ||| ||| ||| |||
 ||+-||+-||+-||+-||+-||+------ 10.0.0.0/24
 |+--|+--|+--|+--|+--|+------- 10.0.1.0/24
 +---+---+---+---+---+-------- 10.0.2.0/24
#v-

Thanks to OSPF, the routing table of R1 contains things like this:

192.168.0.0/24 proto zebra metric 20
   nexthop via 10.0.0.3 dev eth0 weight 1
   nexthop via 10.0.1.3 dev eth1 weight 1
   nexthop via 10.0.2.3 dev eth2 weight 1

10.0.0.3, 10.0.1.3 and 10.0.2.3 are IP for R3.

With this setup, the use of ECMP (Equal Cost Multipath), we can ensure 2
GBps of output bandwidth even in case of one link failure.

If a link  fails, OSPF is pretty  fast to remove the fautive  hop of the
route (less than 5 seconds).

If the designated router fails, OSPF  is also pretty fast to promote the
backup designated router.

If a router  fails, its backup starts to advertise  the same routes. For
example, if R3 fails, its backup router R4 will advertise 192.168.0.0/24
network the same way than R3. This takes less than 5 seconds to happen.

I have configured pimd such that each  router can be CRP and BSR on each
interface (eth0,  eth1, eth2). I have  run some small  experiments and I
have noticed three things :
 - there is no ECMP
 - a link failure is solved in less than 5 seconds
 - if the RP fails, there is a downtime of more than 1 minute
 - if a backup router takes over, the downtime is also more than 1 minute

My questions are :
 - is there a way to have ECMP multicast with pimd and Linux?
 - is there a way to speed up the recovery when the RP is lost?
 - how to reduce the take-over time?

For  the last point,  here is  how we  work with  OSPF.  Each  couple of
routers   are  responsible   for  a   set  of   networks   (for  example
192.168.0.0/24 is a network behind R3 and R4). With the help of VRRP, R3
and R4 are sharing a VIP  (for example 192.168.0.1).  When R3 is master,
it has the VIP and R4 has  no IP for this network. Therefore, only R3 is
advertising this network  with OSPF. When a take-over  happens, R4 takes
the VIP and immediatly, OSPF starts to advertise the network.

The weakness in my setup of pimd is that I am not able to reproduce this
since pimd  will refuse to do  anything with an interface  without an IP
and  does   not  notice  when  an   interface  gains  or   loses  an  IP
address. Therefore,  when a take-over  happens, I reload pimd.  This may
explain the important time needed to recover the situation.

I don't want  to assign IP for 192.168.0.0/24 network to  both R3 and R4
because both of them will start advertising the network through OSPF and
therefore,  IP  packets  may  come  through R4  and  come  back  through
R3. Since R3 and R4 are also stateful firewalls, this will not work.

Any hint  to reduce down time with  pimd in case of  topology changes is
welcome.
-- 
I WILL NOT TRADE PANTS WITH OTHERS
I WILL NOT TRADE PANTS WITH OTHERS
I WILL NOT TRADE PANTS WITH OTHERS
-+- Bart Simpson on chalkboard in episode 7F05

From helen.liu@huawei.com  Mon Jan 10 02:04:00 2011
Return-Path: <helen.liu@huawei.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE35C28C121 for <pim@core3.amsl.com>; Mon, 10 Jan 2011 02:04:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.816
X-Spam-Level: 
X-Spam-Status: No, score=-0.816 tagged_above=-999 required=5 tests=[AWL=-0.322, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tenP0W91OfRp for <pim@core3.amsl.com>; Mon, 10 Jan 2011 02:03:52 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id CEAAA28C0ED for <pim@ietf.org>; Mon, 10 Jan 2011 02:03:51 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LES0093OXDU5E@szxga05-in.huawei.com> for pim@ietf.org; Mon, 10 Jan 2011 18:05:54 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTP id <0LES00H3BXDNTQ@szxga05-in.huawei.com> for pim@ietf.org; Mon, 10 Jan 2011 18:05:54 +0800 (CST)
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.218.12; Mon, 10 Jan 2011 18:05:49 +0800
Received: from SZXEML519-MBX.china.huawei.com ([169.254.3.243]) by szxeml404-hub.china.huawei.com ([fe80::75b7:3db9:fedc:a56d%13]) with mapi id 14.01.0218.012; Mon, 10 Jan 2011 18:05:50 +0800
Date: Mon, 10 Jan 2011 10:05:49 +0000
From: Liuhui <helen.liu@huawei.com>
In-reply-to: <C94BA378.AB0E%hou@cisco.com>
X-Originating-IP: [10.110.98.169]
To: hou <hou@cisco.com>, "Mike McBride (mmcbride)" <mmcbride@cisco.com>, "Yiqun Cai (ycai)" <ycai@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Message-id: <0521328FA8CCCE4089CA3C9261A28DD901CE38@SZXEML519-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_10zzSYnsWvuLOOTAYKf5DQ)"
Content-language: zh-CN
Accept-Language: en-US, zh-CN
Thread-topic: [pim] draft-ietf-pim-mtid-05 wglc
Thread-index: ActapValia8GBshU6kuohlJ+S90GTg6/v+GwAgBdqlAEF8pJjgCnq2IQ
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <283829E9EFBF22459301B900C9A2E434EF6CD4@SZXEML501-MBX.china.huawei.com> <C94BA378.AB0E%hou@cisco.com>
Subject: Re: [pim] draft-ietf-pim-mtid-05 wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2011 10:04:00 -0000

--Boundary_(ID_10zzSYnsWvuLOOTAYKf5DQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi Heidi,

Thanks for your explanation. I suggest some of them be incorporated into the draft to provide more information and for better understanding, if possible.

Besides, the introduction part should give clearer illustration on whether this method could be used for protection, for load balancing, or for both.  E.g.,  duplicated streams on different topologies will be distributed to the same user group for protection, but to different user groups for load balancing.  I heard different opinions on this point, but no explicit answer could be found.

Thanks,
Liu Hui

From: hou [mailto:hou@cisco.com]
Sent: Friday, January 07, 2011 8:51 AM
To: Liuhui; Mike McBride (mmcbride); Yiqun Cai (ycai); pim@ietf.org
Subject: Re: [pim] draft-ietf-pim-mtid-05 wglc

   [H] Thanks for your review comments. Reply inline


On 12/16/10 8:58 PM, "Liuhui" <helen.liu@huawei.com> wrote:
A few comments on the draft:

The Introduction only mentions the multiple topology over "separate network paths". Is this the only case or can different multicast topologies be built over the same physical link? This should be clarified, as the referenced [5120] does.

[H] As mentioned in the "Introduction", the main purpose of this
      [H] draft is to prevent multicast traffic loss in case of  single
       [H] network segment failure. Building multicast topologies over
[H] the same physical network will be against the purpose, but
[H] can be done if an operator chooses to do so

Besides, it might be better to give some explanations for the mtid attribute's influence on forwarding plane, whether it changes the forwarding state/rule or not.

[H] At the end of Section 2, we mention that "The draft does not introduce any
[H] change to the RPF check procedure used to verify the incoming interface
[H] when a packet is forwarded"


Finally, not very clear on the using of two group address G1 and G2 (in Introduction section):
- Since mtid is used to identify the different topology, why additional differentiation of group address is needed.

[H] mtid and group address servers different purposes: mtid is the path
[H] identifier, while the group address defines the content that needs to be
[H] delivered via the path.

- Using two addresses to identify the same multicast stream, is it easy to be deployed in IPTV network, where group address   often corresponds with a channel.

[H] In order to achieve multicast resilience as an end-to-end solution
[H] for IPTV, or other applications,  there will be work from other aspects,
[H] besides the transport/network layer approach, as this draft is focusing on.
[H] The channel to group address mapping actually fits the draft very well,
[H] however, the channel/group split/merge functionality is beyond the scope
[H] of this draft.


thanks
- Heidi


Thanks,
Liu Hui

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of Mike
> McBride (mmcbride)
> Sent: Tuesday, December 07, 2010 8:24 AM
> To: Yiqun Cai (ycai); pim@ietf.org
> Subject: [pim] draft-ietf-pim-mtid-05 wglc
>
> > Mike and Stig,  will we need another last call?
>
> Yes, sorry for the delay. Today begins another 2 week wglc for
> http://www.ietf.org/id/draft-ietf-pim-mtid-05.txt
>
> Please review the draft and let us know if you support sending it to the
> iesg.
>
> thanks,
> mike
>
> > -----Original Message-----
> > From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
> > Yiqun Cai (ycai)
> > Sent: Wednesday, September 22, 2010 3:27 PM
> > To: pim@ietf.org
> > Subject: Re: [pim] I-D Action:draft-ietf-pim-mtid-05.txt
> >
> >
> > Chairs, Dimitri,  and WG,
> >
> > The latest update incorporates the comment received from the
> discussion
> > during the Last Call.
> >
> > Please review and comment.
> >
> > Mike and Stig,  will we need another last call?
> >
> > Thanks.
> >
> >
> > On 9/22/10 3:00 PM, "Internet-Drafts@ietf.org" <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 Protocol Independent Multicast
> > Working Group
> > > of the IETF.
> > >
> > >
> > > Title           : PIM Multi-Topology ID (MT-ID) Join-Attribute
> > > Author(s)       : Y. Cai, H. Ou
> > > Filename        : draft-ietf-pim-mtid-05.txt
> > > Pages           : 11
> > > Date            : 2010-09-22
> > >
> > > This document introduces a new type of PIM Join Attribute that
> > > extends PIM signaling to identify a topology that should be used
> when
> > > constructing a particular multicast distribution tree.
> > >
> > > A URL for this Internet-Draft is:
> > > http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-05.txt
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > ftp://ftp.ietf.org/internet-drafts/
> > >
> > > Below is the data which will enable a MIME compliant mail reader
> > > implementation to automatically retrieve the ASCII version of the
> > > Internet-Draft.
> > > _______________________________________________
> > > pim mailing list
> > > pim@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pim
> >
> >
> > --
> > Yiqun
> >
> > _______________________________________________
> > pim mailing list
> > pim@ietf.org
> > https://www.ietf.org/mailman/listinfo/pim
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
_______________________________________________
pim mailing list
pim@ietf.org
https://www.ietf.org/mailman/listinfo/pim

--Boundary_(ID_10zzSYnsWvuLOOTAYKf5DQ)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<title>Re: [pim] draft-ietf-pim-mtid-05 wglc</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* 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;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang="ZH-CN" link="blue" vlink="purple">
<div class="Section1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Hi Heidi,
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Thanks for your explanation. I suggest some of them be incorporated into the draft to provide more information and for better understanding,
 if possible.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Besides, the introduction part should give clearer illustration on whether this method could be used for protection, for load balancing, or for
 both.&nbsp; E.g., &nbsp;duplicated streams on different topologies will be distributed to the same user group for protection, but to different user groups for load balancing.&nbsp; I heard different opinions on this point, but no explicit answer could be found.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Liu Hui<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:
&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang="EN-US" style="font-size:10.0pt;
font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> hou [mailto:hou@cisco.com]
<br>
<b>Sent:</b> Friday, January 07, 2011 8:51 AM<br>
<b>To:</b> Liuhui; Mike McBride (mmcbride); Yiqun Cai (ycai); pim@ietf.org<br>
<b>Subject:</b> Re: [pim] draft-ietf-pim-mtid-05 wglc<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;<span style="color:blue"> [H] Thanks for your review comments. Reply inline<br>
</span><br>
<br>
On 12/16/10 8:58 PM, &quot;Liuhui&quot; &lt;<a href="helen.liu@huawei.com">helen.liu@huawei.com</a>&gt; wrote:</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">A few comments on the draft:<br>
<br>
The Introduction only mentions the multiple topology over &quot;separate network paths&quot;. Is this the only case or can different multicast topologies be built over the same physical link? This should be clarified, as the referenced [5120] does.
<br>
<br>
<span style="color:blue">[H] As mentioned in the &#8220;Introduction&#8221;, the main purpose of this</span></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;;
color:blue">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[H] draft is to prevent multicast traffic loss in case of &nbsp;single<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[H] network segment failure. Building multicast topologies over</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;;
color:blue">[H] the same physical network will be against the purpose, but<br>
[H] can be done if an operator chooses to do so<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;"><br>
Besides, it might be better to give some explanations for the mtid attribute's influence on forwarding plane, whether it changes the forwarding state/rule or not.<br>
<br>
<span style="color:blue">[H] At the end of Section 2, we mention that &#8220;The draft does not introduce any
<br>
[H] change to the RPF check procedure used to verify the incoming interface<br>
[H] when a packet is forwarded&#8221;<br>
</span><br>
<br>
Finally, not very clear on the using of two group address G1 and G2 (in Introduction section):
<br>
- Since mtid is used to identify the different topology, why additional differentiation of group address is needed.<br>
<br>
<span style="color:blue">[H] mtid and group address servers different purposes: mtid is the path<br>
[H] identifier, while the group address defines the content that needs to be<br>
[H] delivered via the path. <br>
</span><br>
- Using two addresses to identify the same multicast stream, is it easy to be deployed in IPTV network, where group address &nbsp;&nbsp;often corresponds with a channel.<br>
<br>
<span style="color:blue">[H] In order to achieve multicast resilience as an end-to-end solution<br>
[H] for IPTV, or other applications, &nbsp;there will be work from other aspects,<br>
[H] besides the transport/network layer approach, as this draft is focusing on.<br>
[H] The channel to group address mapping actually fits the draft very well,<br>
[H] however, the channel/group split/merge functionality is beyond the scope<br>
[H] of this draft.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;<br>
thanks<br>
- Heidi<br>
</span><br>
<br>
Thanks,<br>
Liu Hui<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href="pim-bounces@ietf.org">pim-bounces@ietf.org</a> [<a href="mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>] On Behalf Of Mike<br>
&gt; McBride (mmcbride)<br>
&gt; Sent: Tuesday, December 07, 2010 8:24 AM<br>
&gt; To: Yiqun Cai (ycai); <a href="pim@ietf.org">pim@ietf.org</a><br>
&gt; Subject: [pim] draft-ietf-pim-mtid-05 wglc<br>
&gt; <br>
&gt; &gt; Mike and Stig, &nbsp;will we need another last call?<br>
&gt; <br>
&gt; Yes, sorry for the delay. Today begins another 2 week wglc for<br>
&gt; <a href="http://www.ietf.org/id/draft-ietf-pim-mtid-05.txt">http://www.ietf.org/id/draft-ietf-pim-mtid-05.txt</a><br>
&gt; <br>
&gt; Please review the draft and let us know if you support sending it to the<br>
&gt; iesg.<br>
&gt; <br>
&gt; thanks,<br>
&gt; mike<br>
&gt; <br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: <a href="pim-bounces@ietf.org">pim-bounces@ietf.org</a> [<a href="mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>] On Behalf Of<br>
&gt; &gt; Yiqun Cai (ycai)<br>
&gt; &gt; Sent: Wednesday, September 22, 2010 3:27 PM<br>
&gt; &gt; To: <a href="pim@ietf.org">pim@ietf.org</a><br>
&gt; &gt; Subject: Re: [pim] I-D Action:draft-ietf-pim-mtid-05.txt<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Chairs, Dimitri, &nbsp;and WG,<br>
&gt; &gt;<br>
&gt; &gt; The latest update incorporates the comment received from the<br>
&gt; discussion<br>
&gt; &gt; during the Last Call.<br>
&gt; &gt;<br>
&gt; &gt; Please review and comment.<br>
&gt; &gt;<br>
&gt; &gt; Mike and Stig, &nbsp;will we need another last call?<br>
&gt; &gt;<br>
&gt; &gt; Thanks.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On 9/22/10 3:00 PM, &quot;<a href="Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a>&quot; &lt;Internet-<br>
&gt; &gt; <a href="Drafts@ietf.org">Drafts@ietf.org</a>&gt;<br>
&gt; &gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; &gt; A New Internet-Draft is available from the on-line Internet-Drafts<br>
&gt; &gt; &gt; directories.<br>
&gt; &gt; &gt; This draft is a work item of the Protocol Independent Multicast<br>
&gt; &gt; Working Group<br>
&gt; &gt; &gt; of the IETF.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Title &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: PIM Multi-Topology ID (MT-ID) Join-Attribute<br>
&gt; &gt; &gt; Author(s) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Y. Cai, H. Ou<br>
&gt; &gt; &gt; Filename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-ietf-pim-mtid-05.txt<br>
&gt; &gt; &gt; Pages &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 11<br>
&gt; &gt; &gt; Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2010-09-22<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; This document introduces a new type of PIM Join Attribute that<br>
&gt; &gt; &gt; extends PIM signaling to identify a topology that should be used<br>
&gt; when<br>
&gt; &gt; &gt; constructing a particular multicast distribution tree.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; A URL for this Internet-Draft is:<br>
&gt; &gt; &gt; <a href="http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-05.txt">http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-05.txt</a><br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; &gt; &gt; <a href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a><br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Below is the data which will enable a MIME compliant mail reader<br>
&gt; &gt; &gt; implementation to automatically retrieve the ASCII version of the<br>
&gt; &gt; &gt; Internet-Draft.<br>
&gt; &gt; &gt; _______________________________________________<br>
&gt; &gt; &gt; pim mailing list<br>
&gt; &gt; &gt; <a href="pim@ietf.org">pim@ietf.org</a><br>
&gt; &gt; &gt; <a href="https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/mailman/listinfo/pim</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Yiqun<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; pim mailing list<br>
&gt; &gt; <a href="pim@ietf.org">pim@ietf.org</a><br>
&gt; &gt; <a href="https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/mailman/listinfo/pim</a><br>
&gt; _______________________________________________<br>
&gt; pim mailing list<br>
&gt; <a href="pim@ietf.org">pim@ietf.org</a><br>
&gt; <a href="https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/mailman/listinfo/pim</a><br>
_______________________________________________<br>
pim mailing list<br>
<a href="pim@ietf.org">pim@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/mailman/listinfo/pim</a></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--Boundary_(ID_10zzSYnsWvuLOOTAYKf5DQ)--

From Internet-Drafts@ietf.org  Mon Jan 10 09:45:06 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 929353A6B07; Mon, 10 Jan 2011 09:45:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.546
X-Spam-Level: 
X-Spam-Status: No, score=-102.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T4SoOx7sKqth; Mon, 10 Jan 2011 09:45:05 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A046D3A6821; Mon, 10 Jan 2011 09:45:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110110174501.3308.2758.idtracker@localhost>
Date: Mon, 10 Jan 2011 09:45:01 -0800
Cc: pim@ietf.org
Subject: [pim] I-D Action:draft-ietf-pim-registry-02.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2011 17:45:06 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.


	Title           : A Registry for PIM Message Types
	Author(s)       : S. Venaas
	Filename        : draft-ietf-pim-registry-02.txt
	Pages           : 8
	Date            : 2011-01-10

This document provides instructions to IANA for the creation of a
registry for PIM message types.  It specifies initial content of the
registry based on existing RFCs specifying PIM message types.  It
also specifies a procedure for registering new types.

In addition to this, one message type is reserved, and may be used
for a future extension of the message type space.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-registry-02.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-pim-registry-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-10093242.I-D@ietf.org>


--NextPart--

From hou@cisco.com  Mon Jan 10 11:27:13 2011
Return-Path: <hou@cisco.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 098EE28C10D for <pim@core3.amsl.com>; Mon, 10 Jan 2011 11:27:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.135
X-Spam-Level: 
X-Spam-Status: No, score=-7.135 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6F3WJcMXHCU4 for <pim@core3.amsl.com>; Mon, 10 Jan 2011 11:27:03 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 20DC528C113 for <pim@ietf.org>; Mon, 10 Jan 2011 11:27:03 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuQHAELtKk2rR7H+/2dsb2JhbACCOoQ9jwONeFUCc6MSmDaCdIJYBIRnhiODJoR2
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 10 Jan 2011 19:29:17 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0AJTHnt000254; Mon, 10 Jan 2011 19:29:17 GMT
Received: from xmb-sjc-231.amer.cisco.com ([128.107.191.73]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 10 Jan 2011 11:29:17 -0800
Received: from 128.107.163.46 ([128.107.163.46]) by xmb-sjc-231.amer.cisco.com ([128.107.191.73]) with Microsoft Exchange Server HTTP-DAV ;  Mon, 10 Jan 2011 19:29:16 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Mon, 10 Jan 2011 11:29:31 -0800
From: hou <hou@cisco.com>
To: Liuhui <helen.liu@huawei.com>, "Mike McBride (mmcbride)" <mmcbride@cisco.com>, "Yiqun Cai (ycai)" <ycai@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Message-ID: <C9509E1B.AC70%hou@cisco.com>
Thread-Topic: [pim] draft-ietf-pim-mtid-05 wglc
Thread-Index: ActapValia8GBshU6kuohlJ+S90GTg6/v+GwAgBdqlAEF8pJjgCnq2IQABZEJ1A=
In-Reply-To: <0521328FA8CCCE4089CA3C9261A28DD901CE38@SZXEML519-MBX.china.huawei.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3377503771_6437426"
X-OriginalArrivalTime: 10 Jan 2011 19:29:17.0218 (UTC) FILETIME=[ABE26820:01CBB0FC]
Subject: Re: [pim] draft-ietf-pim-mtid-05 wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2011 19:27:13 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3377503771_6437426
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Liu Hui,


On 1/10/11 2:05 AM, "Liuhui" <helen.liu@huawei.com> wrote:

> Hi Heidi,=20
> =20
> Thanks for your explanation. I suggest some of them be incorporated into =
the
> draft to provide more information and for better understanding, if possib=
le.
>=20
> [H2]  Would you please supply some specific text and we will be happy to
> incorporate.
> =20
> Besides, the introduction part should give clearer illustration on whethe=
r
> this method could be used for protection, for load balancing, or for both=
.
> E.g.,  duplicated streams on different topologies will be distributed to =
the
> same user group for protection, but to different user groups for load
> balancing.  I heard different opinions on this point, but no explicit ans=
wer
> could be found.
>=20
> [H2]  The draft only mentioned protection as one of the possible use case=
s. On
> the other hand
> [H2]  the PIM protocols doesn=B9t have the knowledge of applications, we in=
tend
> to focus on=20
> [H2]  the protocol specification, but vendors are free to implement whate=
ver
> applications=20
> [H2]  they see fit on top of the specification.
>=20
> thanks
> - Heidi
> =20
> Thanks,
> Liu Hui
> =20
>=20
> From: hou [mailto:hou@cisco.com]
> Sent: Friday, January 07, 2011 8:51 AM
> To: Liuhui; Mike McBride (mmcbride); Yiqun Cai (ycai); pim@ietf.org
> Subject: Re: [pim] draft-ietf-pim-mtid-05 wglc
> =20
>    [H] Thanks for your review comments. Reply inline
>=20
>=20
> On 12/16/10 8:58 PM, "Liuhui" <helen.liu@huawei.com> wrote:
> A few comments on the draft:
>=20
> The Introduction only mentions the multiple topology over "separate netwo=
rk
> paths". Is this the only case or can different multicast topologies be bu=
ilt
> over the same physical link? This should be clarified, as the referenced
> [5120] does.=20
>=20
> [H] As mentioned in the =B3Introduction=B2, the main purpose of this
>       [H] draft is to prevent multicast traffic loss in case of  single
>        [H] network segment failure. Building multicast topologies over
> [H] the same physical network will be against the purpose, but
> [H] can be done if an operator chooses to do so
>=20
> Besides, it might be better to give some explanations for the mtid attrib=
ute's
> influence on forwarding plane, whether it changes the forwarding state/ru=
le or
> not.
>=20
> [H] At the end of Section 2, we mention that =B3The draft does not introduc=
e any
> [H] change to the RPF check procedure used to verify the incoming interfa=
ce
> [H] when a packet is forwarded=B2
>=20
>=20
> Finally, not very clear on the using of two group address G1 and G2 (in
> Introduction section):
> - Since mtid is used to identify the different topology, why additional
> differentiation of group address is needed.
>=20
> [H] mtid and group address servers different purposes: mtid is the path
> [H] identifier, while the group address defines the content that needs to=
 be
> [H] delivered via the path.
>=20
> - Using two addresses to identify the same multicast stream, is it easy t=
o be
> deployed in IPTV network, where group address   often corresponds with a
> channel.
>=20
> [H] In order to achieve multicast resilience as an end-to-end solution
> [H] for IPTV, or other applications,  there will be work from other aspec=
ts,
> [H] besides the transport/network layer approach, as this draft is focusi=
ng
> on.
> [H] The channel to group address mapping actually fits the draft very wel=
l,
> [H] however, the channel/group split/merge functionality is beyond the sc=
ope
> [H] of this draft.
>=20
>    =20
> thanks
> - Heidi
>=20
>=20
> Thanks,
> Liu Hui
>=20
>> > -----Original Message-----
>> > From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of =
Mike
>> > McBride (mmcbride)
>> > Sent: Tuesday, December 07, 2010 8:24 AM
>> > To: Yiqun Cai (ycai); pim@ietf.org
>> > Subject: [pim] draft-ietf-pim-mtid-05 wglc
>> >=20
>>> > > Mike and Stig,  will we need another last call?
>> >=20
>> > Yes, sorry for the delay. Today begins another 2 week wglc for
>> > http://www.ietf.org/id/draft-ietf-pim-mtid-05.txt
>> >=20
>> > Please review the draft and let us know if you support sending it to t=
he
>> > iesg.
>> >=20
>> > thanks,
>> > mike
>> >=20
>>> > > -----Original Message-----
>>> > > From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf =
Of
>>> > > Yiqun Cai (ycai)
>>> > > Sent: Wednesday, September 22, 2010 3:27 PM
>>> > > To: pim@ietf.org
>>> > > Subject: Re: [pim] I-D Action:draft-ietf-pim-mtid-05.txt
>>> > >
>>> > >
>>> > > Chairs, Dimitri,  and WG,
>>> > >
>>> > > The latest update incorporates the comment received from the
>> > discussion
>>> > > during the Last Call.
>>> > >
>>> > > Please review and comment.
>>> > >
>>> > > Mike and Stig,  will we need another last call?
>>> > >
>>> > > Thanks.
>>> > >
>>> > >
>>> > > On 9/22/10 3:00 PM, "Internet-Drafts@ietf.org" <Internet-
>>> > > Drafts@ietf.org>
>>> > > wrote:
>>> > >
>>>> > > > A New Internet-Draft is available from the on-line Internet-Draf=
ts
>>>> > > > directories.
>>>> > > > This draft is a work item of the Protocol Independent Multicast
>>> > > Working Group
>>>> > > > of the IETF.
>>>> > > >
>>>> > > >
>>>> > > > Title           : PIM Multi-Topology ID (MT-ID) Join-Attribute
>>>> > > > Author(s)       : Y. Cai, H. Ou
>>>> > > > Filename        : draft-ietf-pim-mtid-05.txt
>>>> > > > Pages           : 11
>>>> > > > Date            : 2010-09-22
>>>> > > >
>>>> > > > This document introduces a new type of PIM Join Attribute that
>>>> > > > extends PIM signaling to identify a topology that should be used
>> > when
>>>> > > > constructing a particular multicast distribution tree.
>>>> > > >
>>>> > > > A URL for this Internet-Draft is:
>>>> > > > http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-05.txt
>>>> > > >
>>>> > > > Internet-Drafts are also available by anonymous FTP at:
>>>> > > > ftp://ftp.ietf.org/internet-drafts/
>>>> > > >
>>>> > > > Below is the data which will enable a MIME compliant mail reader
>>>> > > > implementation to automatically retrieve the ASCII version of th=
e
>>>> > > > Internet-Draft.
>>>> > > > _______________________________________________
>>>> > > > pim mailing list
>>>> > > > pim@ietf.org
>>>> > > > https://www.ietf.org/mailman/listinfo/pim
>>> > >
>>> > >
>>> > > --
>>> > > Yiqun
>>> > >
>>> > > _______________________________________________
>>> > > pim mailing list
>>> > > pim@ietf.org
>>> > > https://www.ietf.org/mailman/listinfo/pim
>> > _______________________________________________
>> > pim mailing list
>> > pim@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pim
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>=20


--B_3377503771_6437426
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [pim] draft-ietf-pim-mtid-05 wglc</TITLE>
</HEAD>
<BODY>
<FONT COLOR=3D"#0000FF"><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'f=
ont-size:10pt'>Liu Hui,<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'fo=
nt-size:10pt'><BR>
<BR>
On 1/10/11 2:05 AM, &quot;Liuhui&quot; &lt;<a href=3D"helen.liu@huawei.com">h=
elen.liu@huawei.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><FONT SIZE=
=3D"4"><SPAN STYLE=3D'font-size:11pt'>Hi Heidi, <BR>
&nbsp;<BR>
Thanks for your explanation. I suggest some of them be incorporated into th=
e draft to provide more information and for better understanding, if possibl=
e.<BR>
<BR>
</SPAN></FONT></FONT><FONT SIZE=3D"4"><FONT COLOR=3D"#0000FE"><FONT FACE=3D"Times=
 New Roman"><SPAN STYLE=3D'font-size:12pt'>[H2] &nbsp;</SPAN></FONT></FONT></F=
ONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=
=3D'font-size:10pt'>Would you please supply some specific text and we will be =
happy to incorporate.<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><FONT SIZE=3D"4">=
<SPAN STYLE=3D'font-size:11pt'> <BR>
Besides, the introduction part should give clearer illustration on whether =
this method could be used for protection, for load balancing, or for both. &=
nbsp;E.g., &nbsp;duplicated streams on different topologies will be distribu=
ted to the same user group for protection, but to different user groups for =
load balancing. &nbsp;I heard different opinions on this point, but no expli=
cit answer could be found.<BR>
<BR>
</SPAN></FONT></FONT><FONT SIZE=3D"4"><FONT COLOR=3D"#0000FE"><FONT FACE=3D"Times=
 New Roman"><SPAN STYLE=3D'font-size:12pt'>[H2] &nbsp;The draft only mentioned=
 protection as one of the possible use cases. On the other hand<BR>
[H2] &nbsp;the PIM protocols doesn&#8217;t have the knowledge of applicatio=
ns, we intend to focus on <BR>
[H2] &nbsp;the protocol specification, but vendors are free to implement wh=
atever applications <BR>
[H2] &nbsp;they see fit on top of the specification.<BR>
<BR>
thanks<BR>
- Heidi<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'fo=
nt-size:11pt'> <BR>
Thanks,<BR>
Liu Hui<BR>
&nbsp;<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'fo=
nt-size:10pt'><BR>
<B>From:</B> hou [<a href=3D"mailto:hou@cisco.com">mailto:hou@cisco.com</a>] =
<BR>
<B>Sent:</B> Friday, January 07, 2011 8:51 AM<BR>
<B>To:</B> Liuhui; Mike McBride (mmcbride); Yiqun Cai (ycai); <a href=3D"pim@=
ietf.org">pim@ietf.org</a><BR>
<B>Subject:</B> Re: [pim] draft-ietf-pim-mtid-05 wglc<BR>
</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font=
-size:12pt'> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'fo=
nt-size:10pt'> &nbsp;<FONT COLOR=3D"#0000FF"> [H] Thanks for your review comme=
nts. Reply inline<BR>
</FONT><BR>
<BR>
On 12/16/10 8:58 PM, &quot;Liuhui&quot; &lt;<a href=3D"helen.liu@huawei.com">=
helen.liu@huawei.com</a>&gt; wrote:<BR>
A few comments on the draft:<BR>
<BR>
The Introduction only mentions the multiple topology over &quot;separate ne=
twork paths&quot;. Is this the only case or can different multicast topologi=
es be built over the same physical link? This should be clarified, as the re=
ferenced [5120] does. <BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] As mentioned in the &#8220;Introduction&#8221;, t=
he main purpose of this<BR>
</FONT> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[H] draft is to prevent multicast tra=
ffic loss in case of &nbsp;single<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[H] network segment failure. Buil=
ding multicast topologies over<BR>
[H] the same physical network will be against the purpose, but<BR>
[H] can be done if an operator chooses to do so<BR>
<BR>
Besides, it might be better to give some explanations for the mtid attribut=
e's influence on forwarding plane, whether it changes the forwarding state/r=
ule or not.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] At the end of Section 2, we mention that &#8220;T=
he draft does not introduce any <BR>
[H] change to the RPF check procedure used to verify the incoming interface=
<BR>
[H] when a packet is forwarded&#8221;<BR>
</FONT><BR>
<BR>
Finally, not very clear on the using of two group address G1 and G2 (in Int=
roduction section): <BR>
- Since mtid is used to identify the different topology, why additional dif=
ferentiation of group address is needed.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] mtid and group address servers different purposes=
: mtid is the path<BR>
[H] identifier, while the group address defines the content that needs to b=
e<BR>
[H] delivered via the path. <BR>
</FONT><BR>
- Using two addresses to identify the same multicast stream, is it easy to =
be deployed in IPTV network, where group address &nbsp;&nbsp;often correspon=
ds with a channel.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] In order to achieve multicast resilience as an en=
d-to-end solution<BR>
[H] for IPTV, or other applications, &nbsp;there will be work from other as=
pects,<BR>
[H] besides the transport/network layer approach, as this draft is focusing=
 on.<BR>
[H] The channel to group address mapping actually fits the draft very well,=
<BR>
[H] however, the channel/group split/merge functionality is beyond the scop=
e<BR>
[H] of this draft.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;<BR>
thanks<BR>
- Heidi<BR>
</FONT><BR>
<BR>
Thanks,<BR>
Liu Hui<BR>
<BR>
&gt; -----Original Message-----<BR>
&gt; From: <a href=3D"pim-bounces@ietf.org">pim-bounces@ietf.org</a> [<a href=
=3D"mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>] On Behalf Of=
 Mike<BR>
&gt; McBride (mmcbride)<BR>
&gt; Sent: Tuesday, December 07, 2010 8:24 AM<BR>
&gt; To: Yiqun Cai (ycai); <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; Subject: [pim] draft-ietf-pim-mtid-05 wglc<BR>
&gt; <BR>
&gt; &gt; Mike and Stig, &nbsp;will we need another last call?<BR>
&gt; <BR>
&gt; Yes, sorry for the delay. Today begins another 2 week wglc for<BR>
&gt; <a href=3D"http://www.ietf.org/id/draft-ietf-pim-mtid-05.txt">http://www=
.ietf.org/id/draft-ietf-pim-mtid-05.txt</a><BR>
&gt; <BR>
&gt; Please review the draft and let us know if you support sending it to t=
he<BR>
&gt; iesg.<BR>
&gt; <BR>
&gt; thanks,<BR>
&gt; mike<BR>
&gt; <BR>
&gt; &gt; -----Original Message-----<BR>
&gt; &gt; From: <a href=3D"pim-bounces@ietf.org">pim-bounces@ietf.org</a> [<a=
 href=3D"mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>] On Beha=
lf Of<BR>
&gt; &gt; Yiqun Cai (ycai)<BR>
&gt; &gt; Sent: Wednesday, September 22, 2010 3:27 PM<BR>
&gt; &gt; To: <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; &gt; Subject: Re: [pim] I-D Action:draft-ietf-pim-mtid-05.txt<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; Chairs, Dimitri, &nbsp;and WG,<BR>
&gt; &gt;<BR>
&gt; &gt; The latest update incorporates the comment received from the<BR>
&gt; discussion<BR>
&gt; &gt; during the Last Call.<BR>
&gt; &gt;<BR>
&gt; &gt; Please review and comment.<BR>
&gt; &gt;<BR>
&gt; &gt; Mike and Stig, &nbsp;will we need another last call?<BR>
&gt; &gt;<BR>
&gt; &gt; Thanks.<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; On 9/22/10 3:00 PM, &quot;<a href=3D"Internet-Drafts@ietf.org">Inte=
rnet-Drafts@ietf.org</a>&quot; &lt;Internet-<BR>
&gt; &gt; <a href=3D"Drafts@ietf.org">Drafts@ietf.org</a>&gt;<BR>
&gt; &gt; wrote:<BR>
&gt; &gt;<BR>
&gt; &gt; &gt; A New Internet-Draft is available from the on-line Internet-=
Drafts<BR>
&gt; &gt; &gt; directories.<BR>
&gt; &gt; &gt; This draft is a work item of the Protocol Independent Multic=
ast<BR>
&gt; &gt; Working Group<BR>
&gt; &gt; &gt; of the IETF.<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Title &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;: PIM Multi-Topology ID (MT-ID) Join-Attribute<BR>
&gt; &gt; &gt; Author(s) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Y. Cai, H. O=
u<BR>
&gt; &gt; &gt; Filename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-i=
etf-pim-mtid-05.txt<BR>
&gt; &gt; &gt; Pages &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;: 11<BR>
&gt; &gt; &gt; Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;: 2010-09-22<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; This document introduces a new type of PIM Join Attribute th=
at<BR>
&gt; &gt; &gt; extends PIM signaling to identify a topology that should be =
used<BR>
&gt; when<BR>
&gt; &gt; &gt; constructing a particular multicast distribution tree.<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; A URL for this Internet-Draft is:<BR>
&gt; &gt; &gt; <a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-pim-=
mtid-05.txt">http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-05.txt<=
/a><BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Internet-Drafts are also available by anonymous FTP at:<BR>
&gt; &gt; &gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf=
.org/internet-drafts/</a><BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Below is the data which will enable a MIME compliant mail re=
ader<BR>
&gt; &gt; &gt; implementation to automatically retrieve the ASCII version o=
f the<BR>
&gt; &gt; &gt; Internet-Draft.<BR>
&gt; &gt; &gt; _______________________________________________<BR>
&gt; &gt; &gt; pim mailing list<BR>
&gt; &gt; &gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://=
www.ietf.org/mailman/listinfo/pim</a><BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; --<BR>
&gt; &gt; Yiqun<BR>
&gt; &gt;<BR>
&gt; &gt; _______________________________________________<BR>
&gt; &gt; pim mailing list<BR>
&gt; &gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.i=
etf.org/mailman/listinfo/pim</a><BR>
&gt; _______________________________________________<BR>
&gt; pim mailing list<BR>
&gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.o=
rg/mailman/listinfo/pim</a><BR>
_______________________________________________<BR>
pim mailing list<BR>
<a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/ma=
ilman/listinfo/pim</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3377503771_6437426--


From Adrian.Farrel@huawei.com  Mon Jan 10 19:07:26 2011
Return-Path: <Adrian.Farrel@huawei.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CAD8828C20B for <pim@core3.amsl.com>; Mon, 10 Jan 2011 19:07:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.564
X-Spam-Level: 
X-Spam-Status: No, score=-103.564 tagged_above=-999 required=5 tests=[AWL=-0.965, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Dr2vhjYTc7q for <pim@core3.amsl.com>; Mon, 10 Jan 2011 19:07:26 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 2890328C207 for <pim@ietf.org>; Mon, 10 Jan 2011 19:07:26 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEU00L9U8S4AK@usaga01-in.huawei.com> for pim@ietf.org; Mon, 10 Jan 2011 19:09:40 -0800 (PST)
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LEU00L5G8S2XO@usaga01-in.huawei.com> for pim@ietf.org; Mon, 10 Jan 2011 19:09:40 -0800 (PST)
Date: Tue, 11 Jan 2011 03:09:39 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: draft-ietf-pim-registry@tools.ietf.org
Message-id: <031d01cbb13c$fcbd7560$f6386020$@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset=us-ascii
Content-language: en-gb
Content-transfer-encoding: 7BIT
Thread-index: AcuxPPu67sWUVQiARPmecFZ1rgZ+GA==
Cc: pim@ietf.org
Subject: [pim] AD review of draft-ietf-pim-registry
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian.Farrel@huawei.com
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 03:07:26 -0000

Hi,

Don't panic!

I have performed my AD review of your draft. The purpose of the
review is to catch any nits or issues before the document goes
forward to IETF last call and IESG review. By getting these issues
out at this stage we can hope for a higher quality review and a
smoother passage through the process.

Cracking draft, thank you.

I have only one observation: this I-D needs to be on the Standards Track
in order to create a registry (I think!).

Can you tweak that and resubmit? Then I'll issue IETF last call.

Cheers,
Adrian


From helen.liu@huawei.com  Mon Jan 10 19:28:52 2011
Return-Path: <helen.liu@huawei.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7783928C22B for <pim@core3.amsl.com>; Mon, 10 Jan 2011 19:28:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[AWL=0.834,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7fZ8gUt4xFaz for <pim@core3.amsl.com>; Mon, 10 Jan 2011 19:28:50 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 1D76B28C257 for <pim@ietf.org>; Mon, 10 Jan 2011 19:28:50 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEU00INL9RI4G@szxga03-in.huawei.com> for pim@ietf.org; Tue, 11 Jan 2011 11:30:54 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTP id <0LEU00DRO9RIDJ@szxga03-in.huawei.com> for pim@ietf.org; Tue, 11 Jan 2011 11:30:54 +0800 (CST)
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 11 Jan 2011 11:29:24 +0800
Received: from SZXEML519-MBX.china.huawei.com ([169.254.3.243]) by szxeml404-hub.china.huawei.com ([fe80::75b7:3db9:fedc:a56d%13]) with mapi id 14.01.0218.012; Tue, 11 Jan 2011 11:30:53 +0800
Date: Tue, 11 Jan 2011 03:30:53 +0000
From: Liuhui <helen.liu@huawei.com>
In-reply-to: <C9509E1B.AC70%hou@cisco.com>
X-Originating-IP: [10.110.98.169]
To: hou <hou@cisco.com>, "Mike McBride (mmcbride)" <mmcbride@cisco.com>, "Yiqun Cai (ycai)" <ycai@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Message-id: <0521328FA8CCCE4089CA3C9261A28DD901E160@SZXEML519-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_q2FSBJ7bTROzIZ9OYZelwQ)"
Content-language: zh-CN
Accept-Language: en-US, zh-CN
Thread-topic: [pim] draft-ietf-pim-mtid-05 wglc
Thread-index: ActapValia8GBshU6kuohlJ+S90GTg6/v+GwAgBdqlAEF8pJjgCnq2IQABZEJ1AADvuUUA==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <0521328FA8CCCE4089CA3C9261A28DD901CE38@SZXEML519-MBX.china.huawei.com> <C9509E1B.AC70%hou@cisco.com>
Subject: Re: [pim] draft-ietf-pim-mtid-05 wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 03:28:52 -0000

--Boundary_(ID_q2FSBJ7bTROzIZ9OYZelwQ)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: base64

QWNjb3JkaW5nIHRvIHRoZSBpbGx1c3RyYXRpb24gYmVsb3csIHR3byBwbGFjZXMgb2YgdGhlIGRy
YWZ0IGNvdWxkIGJlIGltcHJvdmVkOg0KDQoxo65TZWN0aW9uIDEgOiBhcHBlbmQgdG8gdGhlIGxh
c3QgcGFyYWdyYXBoDQpUaGUgZHJhZnQgZG9lcyBub3QgaW50cm9kdWNlIGFueSBjaGFuZ2UgdG8g
dGhlIFJQRiBjaGVjayBwcm9jZWR1cmUgdXNlZCB0byB2ZXJpZnkgdGhlIGluY29taW5nIGludGVy
ZmFjZSB3aGVuIGEgcGFja2V0IGlzIGZvcndhcmRlZC4gobBJdCB1c2VzIG11bHRpcGxlIGdyb3Vw
IGFkZHJlc3NlcyB0byBpZGVudGlmeSBhIHVuaXF1ZSBtdWx0aWNhc3Qgc3RyZWFtLCB3aGljaCBy
ZXF1aXJlcyBhZGRyZXNzIHNwbGl0IGFuZCBtZXJnZSB0byBmYWNpbGl0YXRlIHRoZSBhZGRyZXNz
LWNoYW5uZWwgbWFwcGluZyB3aGVuIGJlaW5nIGFwcGxpZWQuIFRoZSBkZXRhaWxlZCBwcm9jZXNz
aW5nIGlzIGJleW9uZCB0aGUgc2NvcGUgb2YgdGhlIGRvY3VtZW50LqGxDQoNCjIuICAgU2VjdGlv
biAzLjIgOiBhZGQgYmVmb3JlIG90aGVyIHByb3BlcnRpZXMNCkZvciBlYWNoIFBJTSBSUEYgdG9w
b2xvZ3kgY3JlYXRlZCwgYSB1bmlxdWUgbnVtZXJpY2FsIElEIGlzIGFzc2lnbmVkIHBlciBQSU0g
ZG9tYWluLiAgVGhpcyBJRCBpcyBjYWxsZWQgUElNIE1ULUlELiBQSU0gTVQtSUQgaGFzIHRoZSBm
b2xsb3dpbmcgcHJvcGVydHksDQqhsC0gSXQgaXMgdGhlIHBhdGggaWRlbnRpZmllciB0aGF0IGlz
IHVzZWQgYnkgUElNIGNvbnRyb2wgcGxhbmUsIGJ1dCBkb2VzIG5vdCBmdW5jdGlvbiBpbiB0aGUg
Zm9yd2FyZGluZyBzdGF0ZSBmb3IgYSBzcGVjaWZpYyB0b3BvbG9neS4gIFRoZSBkaWZmZXJlbnRp
YXRpb24gZm9yIHRvcG9sb2dpZXMgb24gZm9yd2FyZGluZyBwbGFuZSBpcyBtYWRlIGJ5IGRpZmZl
cmVudCBncm91cCBhZGRyZXNzZXMgaW5zdGVhZC6hsQ0KDQpUaGFua3MsDQpMaXUgSHVpDQoNCg0K
RnJvbTogaG91IFttYWlsdG86aG91QGNpc2NvLmNvbV0NClNlbnQ6IFR1ZXNkYXksIEphbnVhcnkg
MTEsIDIwMTEgMzozMCBBTQ0KVG86IExpdWh1aTsgTWlrZSBNY0JyaWRlIChtbWNicmlkZSk7IFlp
cXVuIENhaSAoeWNhaSk7IHBpbUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtwaW1dIGRyYWZ0LWll
dGYtcGltLW10aWQtMDUgd2dsYw0KDQpMaXUgSHVpLA0KDQoNCk9uIDEvMTAvMTEgMjowNSBBTSwg
IkxpdWh1aSIgPGhlbGVuLmxpdUBodWF3ZWkuY29tPiB3cm90ZToNCkhpIEhlaWRpLA0KDQpUaGFu
a3MgZm9yIHlvdXIgZXhwbGFuYXRpb24uIEkgc3VnZ2VzdCBzb21lIG9mIHRoZW0gYmUgaW5jb3Jw
b3JhdGVkIGludG8gdGhlIGRyYWZ0IHRvIHByb3ZpZGUgbW9yZSBpbmZvcm1hdGlvbiBhbmQgZm9y
IGJldHRlciB1bmRlcnN0YW5kaW5nLCBpZiBwb3NzaWJsZS4NCg0KW0gyXSAgV291bGQgeW91IHBs
ZWFzZSBzdXBwbHkgc29tZSBzcGVjaWZpYyB0ZXh0IGFuZCB3ZSB3aWxsIGJlIGhhcHB5IHRvIGlu
Y29ycG9yYXRlLg0KDQpCZXNpZGVzLCB0aGUgaW50cm9kdWN0aW9uIHBhcnQgc2hvdWxkIGdpdmUg
Y2xlYXJlciBpbGx1c3RyYXRpb24gb24gd2hldGhlciB0aGlzIG1ldGhvZCBjb3VsZCBiZSB1c2Vk
IGZvciBwcm90ZWN0aW9uLCBmb3IgbG9hZCBiYWxhbmNpbmcsIG9yIGZvciBib3RoLiAgRS5nLiwg
IGR1cGxpY2F0ZWQgc3RyZWFtcyBvbiBkaWZmZXJlbnQgdG9wb2xvZ2llcyB3aWxsIGJlIGRpc3Ry
aWJ1dGVkIHRvIHRoZSBzYW1lIHVzZXIgZ3JvdXAgZm9yIHByb3RlY3Rpb24sIGJ1dCB0byBkaWZm
ZXJlbnQgdXNlciBncm91cHMgZm9yIGxvYWQgYmFsYW5jaW5nLiAgSSBoZWFyZCBkaWZmZXJlbnQg
b3BpbmlvbnMgb24gdGhpcyBwb2ludCwgYnV0IG5vIGV4cGxpY2l0IGFuc3dlciBjb3VsZCBiZSBm
b3VuZC4NCg0KW0gyXSAgVGhlIGRyYWZ0IG9ubHkgbWVudGlvbmVkIHByb3RlY3Rpb24gYXMgb25l
IG9mIHRoZSBwb3NzaWJsZSB1c2UgY2FzZXMuIE9uIHRoZSBvdGhlciBoYW5kDQpbSDJdICB0aGUg
UElNIHByb3RvY29scyBkb2VzbqGvdCBoYXZlIHRoZSBrbm93bGVkZ2Ugb2YgYXBwbGljYXRpb25z
LCB3ZSBpbnRlbmQgdG8gZm9jdXMgb24NCltIMl0gIHRoZSBwcm90b2NvbCBzcGVjaWZpY2F0aW9u
LCBidXQgdmVuZG9ycyBhcmUgZnJlZSB0byBpbXBsZW1lbnQgd2hhdGV2ZXIgYXBwbGljYXRpb25z
DQpbSDJdICB0aGV5IHNlZSBmaXQgb24gdG9wIG9mIHRoZSBzcGVjaWZpY2F0aW9uLg0KDQp0aGFu
a3MNCi0gSGVpZGkNCg0KVGhhbmtzLA0KTGl1IEh1aQ0KDQoNCkZyb206IGhvdSBbbWFpbHRvOmhv
dUBjaXNjby5jb21dDQpTZW50OiBGcmlkYXksIEphbnVhcnkgMDcsIDIwMTEgODo1MSBBTQ0KVG86
IExpdWh1aTsgTWlrZSBNY0JyaWRlIChtbWNicmlkZSk7IFlpcXVuIENhaSAoeWNhaSk7IHBpbUBp
ZXRmLm9yZw0KU3ViamVjdDogUmU6IFtwaW1dIGRyYWZ0LWlldGYtcGltLW10aWQtMDUgd2dsYw0K
DQogIFtIXSBUaGFua3MgZm9yIHlvdXIgcmV2aWV3IGNvbW1lbnRzLiBSZXBseSBpbmxpbmUNCg0K
DQpPbiAxMi8xNi8xMCA4OjU4IFBNLCAiTGl1aHVpIiA8aGVsZW4ubGl1QGh1YXdlaS5jb20+IHdy
b3RlOg0KQSBmZXcgY29tbWVudHMgb24gdGhlIGRyYWZ0Og0KDQpUaGUgSW50cm9kdWN0aW9uIG9u
bHkgbWVudGlvbnMgdGhlIG11bHRpcGxlIHRvcG9sb2d5IG92ZXIgInNlcGFyYXRlIG5ldHdvcmsg
cGF0aHMiLiBJcyB0aGlzIHRoZSBvbmx5IGNhc2Ugb3IgY2FuIGRpZmZlcmVudCBtdWx0aWNhc3Qg
dG9wb2xvZ2llcyBiZSBidWlsdCBvdmVyIHRoZSBzYW1lIHBoeXNpY2FsIGxpbms/IFRoaXMgc2hv
dWxkIGJlIGNsYXJpZmllZCwgYXMgdGhlIHJlZmVyZW5jZWQgWzUxMjBdIGRvZXMuDQoNCltIXSBB
cyBtZW50aW9uZWQgaW4gdGhlIKGwSW50cm9kdWN0aW9uobEsIHRoZSBtYWluIHB1cnBvc2Ugb2Yg
dGhpcw0KICAgICBbSF0gZHJhZnQgaXMgdG8gcHJldmVudCBtdWx0aWNhc3QgdHJhZmZpYyBsb3Nz
IGluIGNhc2Ugb2YgIHNpbmdsZQ0KICAgICAgIFtIXSBuZXR3b3JrIHNlZ21lbnQgZmFpbHVyZS4g
QnVpbGRpbmcgbXVsdGljYXN0IHRvcG9sb2dpZXMgb3Zlcg0KW0hdIHRoZSBzYW1lIHBoeXNpY2Fs
IG5ldHdvcmsgd2lsbCBiZSBhZ2FpbnN0IHRoZSBwdXJwb3NlLCBidXQNCltIXSBjYW4gYmUgZG9u
ZSBpZiBhbiBvcGVyYXRvciBjaG9vc2VzIHRvIGRvIHNvDQoNCkJlc2lkZXMsIGl0IG1pZ2h0IGJl
IGJldHRlciB0byBnaXZlIHNvbWUgZXhwbGFuYXRpb25zIGZvciB0aGUgbXRpZCBhdHRyaWJ1dGUn
cyBpbmZsdWVuY2Ugb24gZm9yd2FyZGluZyBwbGFuZSwgd2hldGhlciBpdCBjaGFuZ2VzIHRoZSBm
b3J3YXJkaW5nIHN0YXRlL3J1bGUgb3Igbm90Lg0KDQpbSF0gQXQgdGhlIGVuZCBvZiBTZWN0aW9u
IDIsIHdlIG1lbnRpb24gdGhhdCChsFRoZSBkcmFmdCBkb2VzIG5vdCBpbnRyb2R1Y2UgYW55DQpb
SF0gY2hhbmdlIHRvIHRoZSBSUEYgY2hlY2sgcHJvY2VkdXJlIHVzZWQgdG8gdmVyaWZ5IHRoZSBp
bmNvbWluZyBpbnRlcmZhY2UNCltIXSB3aGVuIGEgcGFja2V0IGlzIGZvcndhcmRlZKGxDQoNCg0K
RmluYWxseSwgbm90IHZlcnkgY2xlYXIgb24gdGhlIHVzaW5nIG9mIHR3byBncm91cCBhZGRyZXNz
IEcxIGFuZCBHMiAoaW4gSW50cm9kdWN0aW9uIHNlY3Rpb24pOg0KLSBTaW5jZSBtdGlkIGlzIHVz
ZWQgdG8gaWRlbnRpZnkgdGhlIGRpZmZlcmVudCB0b3BvbG9neSwgd2h5IGFkZGl0aW9uYWwgZGlm
ZmVyZW50aWF0aW9uIG9mIGdyb3VwIGFkZHJlc3MgaXMgbmVlZGVkLg0KDQpbSF0gbXRpZCBhbmQg
Z3JvdXAgYWRkcmVzcyBzZXJ2ZXJzIGRpZmZlcmVudCBwdXJwb3NlczogbXRpZCBpcyB0aGUgcGF0
aA0KW0hdIGlkZW50aWZpZXIsIHdoaWxlIHRoZSBncm91cCBhZGRyZXNzIGRlZmluZXMgdGhlIGNv
bnRlbnQgdGhhdCBuZWVkcyB0byBiZQ0KW0hdIGRlbGl2ZXJlZCB2aWEgdGhlIHBhdGguDQoNCi0g
VXNpbmcgdHdvIGFkZHJlc3NlcyB0byBpZGVudGlmeSB0aGUgc2FtZSBtdWx0aWNhc3Qgc3RyZWFt
LCBpcyBpdCBlYXN5IHRvIGJlIGRlcGxveWVkIGluIElQVFYgbmV0d29yaywgd2hlcmUgZ3JvdXAg
YWRkcmVzcyAgIG9mdGVuIGNvcnJlc3BvbmRzIHdpdGggYSBjaGFubmVsLg0KDQpbSF0gSW4gb3Jk
ZXIgdG8gYWNoaWV2ZSBtdWx0aWNhc3QgcmVzaWxpZW5jZSBhcyBhbiBlbmQtdG8tZW5kIHNvbHV0
aW9uDQpbSF0gZm9yIElQVFYsIG9yIG90aGVyIGFwcGxpY2F0aW9ucywgIHRoZXJlIHdpbGwgYmUg
d29yayBmcm9tIG90aGVyIGFzcGVjdHMsDQpbSF0gYmVzaWRlcyB0aGUgdHJhbnNwb3J0L25ldHdv
cmsgbGF5ZXIgYXBwcm9hY2gsIGFzIHRoaXMgZHJhZnQgaXMgZm9jdXNpbmcgb24uDQpbSF0gVGhl
IGNoYW5uZWwgdG8gZ3JvdXAgYWRkcmVzcyBtYXBwaW5nIGFjdHVhbGx5IGZpdHMgdGhlIGRyYWZ0
IHZlcnkgd2VsbCwNCltIXSBob3dldmVyLCB0aGUgY2hhbm5lbC9ncm91cCBzcGxpdC9tZXJnZSBm
dW5jdGlvbmFsaXR5IGlzIGJleW9uZCB0aGUgc2NvcGUNCltIXSBvZiB0aGlzIGRyYWZ0Lg0KDQoN
CnRoYW5rcw0KLSBIZWlkaQ0KDQoNClRoYW5rcywNCkxpdSBIdWkNCg0KPiAtLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBwaW0tYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnBpbS1i
b3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgTWlrZQ0KPiBNY0JyaWRlIChtbWNicmlkZSkN
Cj4gU2VudDogVHVlc2RheSwgRGVjZW1iZXIgMDcsIDIwMTAgODoyNCBBTQ0KPiBUbzogWWlxdW4g
Q2FpICh5Y2FpKTsgcGltQGlldGYub3JnDQo+IFN1YmplY3Q6IFtwaW1dIGRyYWZ0LWlldGYtcGlt
LW10aWQtMDUgd2dsYw0KPg0KPiA+IE1pa2UgYW5kIFN0aWcsICB3aWxsIHdlIG5lZWQgYW5vdGhl
ciBsYXN0IGNhbGw/DQo+DQo+IFllcywgc29ycnkgZm9yIHRoZSBkZWxheS4gVG9kYXkgYmVnaW5z
IGFub3RoZXIgMiB3ZWVrIHdnbGMgZm9yDQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQt
aWV0Zi1waW0tbXRpZC0wNS50eHQNCj4NCj4gUGxlYXNlIHJldmlldyB0aGUgZHJhZnQgYW5kIGxl
dCB1cyBrbm93IGlmIHlvdSBzdXBwb3J0IHNlbmRpbmcgaXQgdG8gdGhlDQo+IGllc2cuDQo+DQo+
IHRoYW5rcywNCj4gbWlrZQ0KPg0KPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4g
RnJvbTogcGltLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpwaW0tYm91bmNlc0BpZXRmLm9yZ10g
T24gQmVoYWxmIE9mDQo+ID4gWWlxdW4gQ2FpICh5Y2FpKQ0KPiA+IFNlbnQ6IFdlZG5lc2RheSwg
U2VwdGVtYmVyIDIyLCAyMDEwIDM6MjcgUE0NCj4gPiBUbzogcGltQGlldGYub3JnDQo+ID4gU3Vi
amVjdDogUmU6IFtwaW1dIEktRCBBY3Rpb246ZHJhZnQtaWV0Zi1waW0tbXRpZC0wNS50eHQNCj4g
Pg0KPiA+DQo+ID4gQ2hhaXJzLCBEaW1pdHJpLCAgYW5kIFdHLA0KPiA+DQo+ID4gVGhlIGxhdGVz
dCB1cGRhdGUgaW5jb3Jwb3JhdGVzIHRoZSBjb21tZW50IHJlY2VpdmVkIGZyb20gdGhlDQo+IGRp
c2N1c3Npb24NCj4gPiBkdXJpbmcgdGhlIExhc3QgQ2FsbC4NCj4gPg0KPiA+IFBsZWFzZSByZXZp
ZXcgYW5kIGNvbW1lbnQuDQo+ID4NCj4gPiBNaWtlIGFuZCBTdGlnLCAgd2lsbCB3ZSBuZWVkIGFu
b3RoZXIgbGFzdCBjYWxsPw0KPiA+DQo+ID4gVGhhbmtzLg0KPiA+DQo+ID4NCj4gPiBPbiA5LzIy
LzEwIDM6MDAgUE0sICJJbnRlcm5ldC1EcmFmdHNAaWV0Zi5vcmciIDxJbnRlcm5ldC0NCj4gPiBE
cmFmdHNAaWV0Zi5vcmc+DQo+ID4gd3JvdGU6DQo+ID4NCj4gPiA+IEEgTmV3IEludGVybmV0LURy
YWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cw0KPiA+ID4g
ZGlyZWN0b3JpZXMuDQo+ID4gPiBUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRoZSBQcm90
b2NvbCBJbmRlcGVuZGVudCBNdWx0aWNhc3QNCj4gPiBXb3JraW5nIEdyb3VwDQo+ID4gPiBvZiB0
aGUgSUVURi4NCj4gPiA+DQo+ID4gPg0KPiA+ID4gVGl0bGUgICAgICAgICAgIDogUElNIE11bHRp
LVRvcG9sb2d5IElEIChNVC1JRCkgSm9pbi1BdHRyaWJ1dGUNCj4gPiA+IEF1dGhvcihzKSAgICAg
ICA6IFkuIENhaSwgSC4gT3UNCj4gPiA+IEZpbGVuYW1lICAgICAgICA6IGRyYWZ0LWlldGYtcGlt
LW10aWQtMDUudHh0DQo+ID4gPiBQYWdlcyAgICAgICAgICAgOiAxMQ0KPiA+ID4gRGF0ZSAgICAg
ICAgICAgIDogMjAxMC0wOS0yMg0KPiA+ID4NCj4gPiA+IFRoaXMgZG9jdW1lbnQgaW50cm9kdWNl
cyBhIG5ldyB0eXBlIG9mIFBJTSBKb2luIEF0dHJpYnV0ZSB0aGF0DQo+ID4gPiBleHRlbmRzIFBJ
TSBzaWduYWxpbmcgdG8gaWRlbnRpZnkgYSB0b3BvbG9neSB0aGF0IHNob3VsZCBiZSB1c2VkDQo+
IHdoZW4NCj4gPiA+IGNvbnN0cnVjdGluZyBhIHBhcnRpY3VsYXIgbXVsdGljYXN0IGRpc3RyaWJ1
dGlvbiB0cmVlLg0KPiA+ID4NCj4gPiA+IEEgVVJMIGZvciB0aGlzIEludGVybmV0LURyYWZ0IGlz
Og0KPiA+ID4gaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1w
aW0tbXRpZC0wNS50eHQNCj4gPiA+DQo+ID4gPiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZh
aWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQo+ID4gPiBmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50
ZXJuZXQtZHJhZnRzLw0KPiA+ID4NCj4gPiA+IEJlbG93IGlzIHRoZSBkYXRhIHdoaWNoIHdpbGwg
ZW5hYmxlIGEgTUlNRSBjb21wbGlhbnQgbWFpbCByZWFkZXINCj4gPiA+IGltcGxlbWVudGF0aW9u
IHRvIGF1dG9tYXRpY2FsbHkgcmV0cmlldmUgdGhlIEFTQ0lJIHZlcnNpb24gb2YgdGhlDQo+ID4g
PiBJbnRlcm5ldC1EcmFmdC4NCj4gPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQo+ID4gPiBwaW0gbWFpbGluZyBsaXN0DQo+ID4gPiBwaW1AaWV0Zi5v
cmcNCj4gPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltDQo+ID4N
Cj4gPg0KPiA+IC0tDQo+ID4gWWlxdW4NCj4gPg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gcGltIG1haWxpbmcgbGlzdA0KPiA+IHBpbUBp
ZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltDQo+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IHBpbSBt
YWlsaW5nIGxpc3QNCj4gcGltQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vcGltDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KcGltIG1haWxpbmcgbGlzdA0KcGltQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbQ0K

--Boundary_(ID_q2FSBJ7bTROzIZ9OYZelwQ)
Content-type: text/html; charset=gb2312
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=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<title>Re: [pim] draft-ietf-pim-mtid-05 wglc</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* 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;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</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"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;">According to the illustr=
ation below, two places of the draft could be improved:<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;">1</span><span style=3D"f=
ont-size:11.0pt;font-family:=CB=CE=CC=E5">=A3=AE</span><span lang=3D"EN-US"=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;">Section 1 : append
 to the last paragraph<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;">The draft does not intro=
duce any change to the RPF check procedure used to verify the incoming inte=
rface when a packet is forwarded. =A1=B0It uses multiple group
 addresses to identify a unique multicast stream, which requires address sp=
lit and merge to facilitate the address-channel mapping when being applied.=
 The detailed processing is beyond the scope of the document.=A1=B1<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;">2.&nbsp;&nbsp; Section 3=
.2 : add before other properties<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;">For each PIM RPF topolog=
y created, a unique numerical ID is assigned per PIM domain.&nbsp; This ID =
is called PIM MT-ID. PIM MT-ID has the following property,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;">=A1=B0- It is the path i=
dentifier that is used by PIM control plane, but does not function in the f=
orwarding state for a specific topology. &nbsp;The differentiation for
 topologies on forwarding plane is made by different group addresses instea=
d.=A1=B1<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Thanks,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Liu Hui<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span>=
</p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:
&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang=3D"EN=
-US" style=3D"font-size:10.0pt;
font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> hou [mailto:hou@cis=
co.com]
<br>
<b>Sent:</b> Tuesday, January 11, 2011 3:30 AM<br>
<b>To:</b> Liuhui; Mike McBride (mmcbride); Yiqun Cai (ycai); pim@ietf.org<=
br>
<b>Subject:</b> Re: [pim] draft-ietf-pim-mtid-05 wglc<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&=
quot;;color:blue">Liu Hui,<br>
</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Ver=
dana&quot;,&quot;sans-serif&quot;"><br>
<br>
On 1/10/11 2:05 AM, &quot;Liuhui&quot; &lt;<a href=3D"helen.liu@huawei.com"=
>helen.liu@huawei.com</a>&gt; wrote:</span><span lang=3D"EN-US"><o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US" =
style=3D"font-size:11.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&=
quot;">Hi Heidi,
<br>
&nbsp;<br>
Thanks for your explanation. I suggest some of them be incorporated into th=
e draft to provide more information and for better understanding, if possib=
le.<br>
<br>
</span><span lang=3D"EN-US" style=3D"color:#0000FE">[H2] &nbsp;</span><span=
 lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,&=
quot;sans-serif&quot;;
color:blue">Would you please supply some specific text and we will be happy=
 to incorporate.<br>
</span><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Ver=
dana&quot;,&quot;sans-serif&quot;"><br>
Besides, the introduction part should give clearer illustration on whether =
this method could be used for protection, for load balancing, or for both. =
&nbsp;E.g., &nbsp;duplicated streams on different topologies will be distri=
buted to the same user group for protection,
 but to different user groups for load balancing. &nbsp;I heard different o=
pinions on this point, but no explicit answer could be found.<br>
<br>
</span><span lang=3D"EN-US" style=3D"color:#0000FE">[H2] &nbsp;The draft on=
ly mentioned protection as one of the possible use cases. On the other hand=
<br>
[H2] &nbsp;the PIM protocols doesn=A1=AFt have the knowledge of application=
s, we intend to focus on
<br>
[H2] &nbsp;the protocol specification, but vendors are free to implement wh=
atever applications
<br>
[H2] &nbsp;they see fit on top of the specification.<br>
<br>
thanks<br>
- Heidi<br>
</span><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Ver=
dana&quot;,&quot;sans-serif&quot;"><br>
Thanks,<br>
Liu Hui<br>
&nbsp;<br>
</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Ver=
dana&quot;,&quot;sans-serif&quot;"><br>
<b>From:</b> hou [<a href=3D"mailto:hou@cisco.com">mailto:hou@cisco.com</a>=
] <br>
<b>Sent:</b> Friday, January 07, 2011 8:51 AM<br>
<b>To:</b> Liuhui; Mike McBride (mmcbride); Yiqun Cai (ycai); <a href=3D"pi=
m@ietf.org">
pim@ietf.org</a><br>
<b>Subject:</b> Re: [pim] draft-ietf-pim-mtid-05 wglc<br>
</span><span lang=3D"EN-US"><br>
</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Ver=
dana&quot;,&quot;sans-serif&quot;">&nbsp;<span style=3D"color:blue"> [H] Th=
anks for your review comments. Reply inline<br>
</span><br>
<br>
On 12/16/10 8:58 PM, &quot;Liuhui&quot; &lt;<a href=3D"helen.liu@huawei.com=
">helen.liu@huawei.com</a>&gt; wrote:<br>
A few comments on the draft:<br>
<br>
The Introduction only mentions the multiple topology over &quot;separate ne=
twork paths&quot;. Is this the only case or can different multicast topolog=
ies be built over the same physical link? This should be clarified, as the =
referenced [5120] does.
<br>
<br>
<span style=3D"color:blue">[H] As mentioned in the =A1=B0Introduction=A1=B1=
, the main purpose of this<br>
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[H] draft is to prevent multicast traf=
fic loss in case of &nbsp;single<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[H] network segment failure. Buil=
ding multicast topologies over<br>
[H] the same physical network will be against the purpose, but<br>
[H] can be done if an operator chooses to do so<br>
<br>
Besides, it might be better to give some explanations for the mtid attribut=
e's influence on forwarding plane, whether it changes the forwarding state/=
rule or not.<br>
<br>
<span style=3D"color:blue">[H] At the end of Section 2, we mention that =A1=
=B0The draft does not introduce any
<br>
[H] change to the RPF check procedure used to verify the incoming interface=
<br>
[H] when a packet is forwarded=A1=B1<br>
</span><br>
<br>
Finally, not very clear on the using of two group address G1 and G2 (in Int=
roduction section):
<br>
- Since mtid is used to identify the different topology, why additional dif=
ferentiation of group address is needed.<br>
<br>
<span style=3D"color:blue">[H] mtid and group address servers different pur=
poses: mtid is the path<br>
[H] identifier, while the group address defines the content that needs to b=
e<br>
[H] delivered via the path. <br>
</span><br>
- Using two addresses to identify the same multicast stream, is it easy to =
be deployed in IPTV network, where group address &nbsp;&nbsp;often correspo=
nds with a channel.<br>
<br>
<span style=3D"color:blue">[H] In order to achieve multicast resilience as =
an end-to-end solution<br>
[H] for IPTV, or other applications, &nbsp;there will be work from other as=
pects,<br>
[H] besides the transport/network layer approach, as this draft is focusing=
 on.<br>
[H] The channel to group address mapping actually fits the draft very well,=
<br>
[H] however, the channel/group split/merge functionality is beyond the scop=
e<br>
[H] of this draft.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;<br>
thanks<br>
- Heidi<br>
</span><br>
<br>
Thanks,<br>
Liu Hui<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"pim-bounces@ietf.org">pim-bounces@ietf.org</a> [<a hr=
ef=3D"mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>] On Beha=
lf Of Mike<br>
&gt; McBride (mmcbride)<br>
&gt; Sent: Tuesday, December 07, 2010 8:24 AM<br>
&gt; To: Yiqun Cai (ycai); <a href=3D"pim@ietf.org">pim@ietf.org</a><br>
&gt; Subject: [pim] draft-ietf-pim-mtid-05 wglc<br>
&gt; <br>
&gt; &gt; Mike and Stig, &nbsp;will we need another last call?<br>
&gt; <br>
&gt; Yes, sorry for the delay. Today begins another 2 week wglc for<br>
&gt; <a href=3D"http://www.ietf.org/id/draft-ietf-pim-mtid-05.txt">http://w=
ww.ietf.org/id/draft-ietf-pim-mtid-05.txt</a><br>
&gt; <br>
&gt; Please review the draft and let us know if you support sending it to t=
he<br>
&gt; iesg.<br>
&gt; <br>
&gt; thanks,<br>
&gt; mike<br>
&gt; <br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: <a href=3D"pim-bounces@ietf.org">pim-bounces@ietf.org</a> [=
<a href=3D"mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>] On=
 Behalf Of<br>
&gt; &gt; Yiqun Cai (ycai)<br>
&gt; &gt; Sent: Wednesday, September 22, 2010 3:27 PM<br>
&gt; &gt; To: <a href=3D"pim@ietf.org">pim@ietf.org</a><br>
&gt; &gt; Subject: Re: [pim] I-D Action:draft-ietf-pim-mtid-05.txt<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Chairs, Dimitri, &nbsp;and WG,<br>
&gt; &gt;<br>
&gt; &gt; The latest update incorporates the comment received from the<br>
&gt; discussion<br>
&gt; &gt; during the Last Call.<br>
&gt; &gt;<br>
&gt; &gt; Please review and comment.<br>
&gt; &gt;<br>
&gt; &gt; Mike and Stig, &nbsp;will we need another last call?<br>
&gt; &gt;<br>
&gt; &gt; Thanks.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On 9/22/10 3:00 PM, &quot;<a href=3D"Internet-Drafts@ietf.org">In=
ternet-Drafts@ietf.org</a>&quot; &lt;Internet-<br>
&gt; &gt; <a href=3D"Drafts@ietf.org">Drafts@ietf.org</a>&gt;<br>
&gt; &gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; &gt; A New Internet-Draft is available from the on-line Internet-=
Drafts<br>
&gt; &gt; &gt; directories.<br>
&gt; &gt; &gt; This draft is a work item of the Protocol Independent Multic=
ast<br>
&gt; &gt; Working Group<br>
&gt; &gt; &gt; of the IETF.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Title &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;: PIM Multi-Topology ID (MT-ID) Join-Attribute<br>
&gt; &gt; &gt; Author(s) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Y. Cai, H. O=
u<br>
&gt; &gt; &gt; Filename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-i=
etf-pim-mtid-05.txt<br>
&gt; &gt; &gt; Pages &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;: 11<br>
&gt; &gt; &gt; Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;: 2010-09-22<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; This document introduces a new type of PIM Join Attribute th=
at<br>
&gt; &gt; &gt; extends PIM signaling to identify a topology that should be =
used<br>
&gt; when<br>
&gt; &gt; &gt; constructing a particular multicast distribution tree.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; A URL for this Internet-Draft is:<br>
&gt; &gt; &gt; <a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-pi=
m-mtid-05.txt">http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-05.t=
xt</a><br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; &gt; &gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ie=
tf.org/internet-drafts/</a><br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Below is the data which will enable a MIME compliant mail re=
ader<br>
&gt; &gt; &gt; implementation to automatically retrieve the ASCII version o=
f the<br>
&gt; &gt; &gt; Internet-Draft.<br>
&gt; &gt; &gt; _______________________________________________<br>
&gt; &gt; &gt; pim mailing list<br>
&gt; &gt; &gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><br>
&gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https:=
//www.ietf.org/mailman/listinfo/pim</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Yiqun<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; pim mailing list<br>
&gt; &gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www=
.ietf.org/mailman/listinfo/pim</a><br>
&gt; _______________________________________________<br>
&gt; pim mailing list<br>
&gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf=
.org/mailman/listinfo/pim</a><br>
_______________________________________________<br>
pim mailing list<br>
<a href=3D"pim@ietf.org">pim@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/=
mailman/listinfo/pim</a></span><span lang=3D"EN-US"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--Boundary_(ID_q2FSBJ7bTROzIZ9OYZelwQ)--

From hou@cisco.com  Tue Jan 11 00:04:39 2011
Return-Path: <hou@cisco.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 258733A69EF for <pim@core3.amsl.com>; Tue, 11 Jan 2011 00:04:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.727
X-Spam-Level: 
X-Spam-Status: No, score=-7.727 tagged_above=-999 required=5 tests=[AWL=0.591,  BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001,  MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ulf2wFHOOXP5 for <pim@core3.amsl.com>; Tue, 11 Jan 2011 00:04:25 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id C856A3A69BE for <pim@ietf.org>; Tue, 11 Jan 2011 00:04:25 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkMEAOqeK02rR7H+/2dsb2JhbACCOoFOgm+Oc414V3OiO4pVjhqCdIFkdASEZ4YjgyY
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-2.cisco.com with ESMTP; 11 Jan 2011 08:06:31 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0B86V2q025815; Tue, 11 Jan 2011 08:06:31 GMT
Received: from xmb-sjc-231.amer.cisco.com ([128.107.191.73]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 11 Jan 2011 00:06:31 -0800
Received: from 10.21.118.34 ([10.21.118.34]) by xmb-sjc-231.amer.cisco.com ([128.107.191.73]) with Microsoft Exchange Server HTTP-DAV ;  Tue, 11 Jan 2011 08:06:30 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Tue, 11 Jan 2011 00:06:44 -0800
From: hou <hou@cisco.com>
To: Liuhui <helen.liu@huawei.com>, "Mike McBride (mmcbride)" <mmcbride@cisco.com>, "Yiqun Cai (ycai)" <ycai@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Message-ID: <C9514F94.ACE9%hou@cisco.com>
Thread-Topic: [pim] draft-ietf-pim-mtid-05 wglc
Thread-Index: ActapValia8GBshU6kuohlJ+S90GTg6/v+GwAgBdqlAEF8pJjgCnq2IQABZEJ1AADvuUUAALdneB
In-Reply-To: <0521328FA8CCCE4089CA3C9261A28DD901E160@SZXEML519-MBX.china.huawei.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3377549204_8835990"
X-OriginalArrivalTime: 11 Jan 2011 08:06:31.0073 (UTC) FILETIME=[74928110:01CBB166]
Subject: Re: [pim] draft-ietf-pim-mtid-05 wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 08:04:39 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3377549204_8835990
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable




On 1/10/11 7:30 PM, "Liuhui" <helen.liu@huawei.com> wrote:

> According to the illustration below, two places of the draft could be
> improved:
> =20
> 1=EF=BC=8ESection 1 : append to the last paragraph
> The draft does not introduce any change to the RPF check procedure used t=
o
> verify the incoming interface when a packet is forwarded. =E2=80=9CIt uses mult=
iple
> group addresses to identify a unique multicast stream, which requires add=
ress
> split and merge to facilitate the address-channel mapping when being appl=
ied.
> The detailed processing is beyond the scope of the document.=E2=80=9D
>=20
> [H3] I think you mean Section 2. Introduction.
> [H3] With slight modification, we will add this:  =E2=80=9CAs an example to use=
 the
> capability
> [H3] described by this draft, an application can choose to use group
> addresses, and/
> [H3] or source addresses, to identify an unique multicast steam. It might
> further
> [H3] need to perform the functions of splitting and merging. But the deta=
iled
> [H3] processing is beyond the scope of the document=E2=80=9D
>=20
> =20
> 2.   Section 3.2 : add before other properties
> For each PIM RPF topology created, a unique numerical ID is assigned per =
PIM
> domain.  This ID is called PIM MT-ID. PIM MT-ID has the following propert=
y,
> =E2=80=9C- It is the path identifier that is used by PIM control plane, but doe=
s not
> function in the forwarding state for a specific topology.  The differenti=
ation
> for topologies on forwarding plane is made by different group addresses
> instead.=E2=80=9D
>=20
> [H3] How about the following
> [H3] =E2=80=9C- it is the path identifier that is used by PIM control plane, bu=
t does
> not=20
> [H3] function in the forwarding state for a specific topology.  The
> differentiation for
> [H3] topologies on forwarding plane is made by different group addresses,
> and/or
> [H3] sources addresses instead.=E2=80=9D
>=20
> [H3]  Thanks again for your comments.
> [H3]  - Heidi
>=20
>=20
>=20
>=20
> Thanks,
> Liu Hui
> =20
> =20
>=20
> From: hou [mailto:hou@cisco.com]
> Sent: Tuesday, January 11, 2011 3:30 AM
> To: Liuhui; Mike McBride (mmcbride); Yiqun Cai (ycai); pim@ietf.org
> Subject: Re: [pim] draft-ietf-pim-mtid-05 wglc
> =20
> Liu Hui,
>=20
>=20
> On 1/10/11 2:05 AM, "Liuhui" <helen.liu@huawei.com> wrote:
> Hi Heidi,=20
> =20
> Thanks for your explanation. I suggest some of them be incorporated into =
the
> draft to provide more information and for better understanding, if possib=
le.
>=20
> [H2]  Would you please supply some specific text and we will be happy to
> incorporate.
>=20
> Besides, the introduction part should give clearer illustration on whethe=
r
> this method could be used for protection, for load balancing, or for both=
.
> E.g.,  duplicated streams on different topologies will be distributed to =
the
> same user group for protection, but to different user groups for load
> balancing.  I heard different opinions on this point, but no explicit ans=
wer
> could be found.
>=20
> [H2]  The draft only mentioned protection as one of the possible use case=
s. On
> the other hand
> [H2]  the PIM protocols doesn=E2=80=99t have the knowledge of applications, we =
intend
> to focus on=20
> [H2]  the protocol specification, but vendors are free to implement whate=
ver
> applications=20
> [H2]  they see fit on top of the specification.
>=20
> thanks
> - Heidi
>=20
> Thanks,
> Liu Hui
> =20
>=20
> From: hou [mailto:hou@cisco.com]
> Sent: Friday, January 07, 2011 8:51 AM
> To: Liuhui; Mike McBride (mmcbride); Yiqun Cai (ycai); pim@ietf.org
> Subject: Re: [pim] draft-ietf-pim-mtid-05 wglc
>=20
>   [H] Thanks for your review comments. Reply inline
>=20
>=20
> On 12/16/10 8:58 PM, "Liuhui" <helen.liu@huawei.com> wrote:
> A few comments on the draft:
>=20
> The Introduction only mentions the multiple topology over "separate netwo=
rk
> paths". Is this the only case or can different multicast topologies be bu=
ilt
> over the same physical link? This should be clarified, as the referenced
> [5120] does.=20
>=20
> [H] As mentioned in the =E2=80=9CIntroduction=E2=80=9D, the main purpose of this
>      [H] draft is to prevent multicast traffic loss in case of  single
>        [H] network segment failure. Building multicast topologies over
> [H] the same physical network will be against the purpose, but
> [H] can be done if an operator chooses to do so
>=20
> Besides, it might be better to give some explanations for the mtid attrib=
ute's
> influence on forwarding plane, whether it changes the forwarding state/ru=
le or
> not.
>=20
> [H] At the end of Section 2, we mention that =E2=80=9CThe draft does not introd=
uce any
> [H] change to the RPF check procedure used to verify the incoming interfa=
ce
> [H] when a packet is forwarded=E2=80=9D
>=20
>=20
> Finally, not very clear on the using of two group address G1 and G2 (in
> Introduction section):
> - Since mtid is used to identify the different topology, why additional
> differentiation of group address is needed.
>=20
> [H] mtid and group address servers different purposes: mtid is the path
> [H] identifier, while the group address defines the content that needs to=
 be
> [H] delivered via the path.
>=20
> - Using two addresses to identify the same multicast stream, is it easy t=
o be
> deployed in IPTV network, where group address   often corresponds with a
> channel.
>=20
> [H] In order to achieve multicast resilience as an end-to-end solution
> [H] for IPTV, or other applications,  there will be work from other aspec=
ts,
> [H] besides the transport/network layer approach, as this draft is focusi=
ng
> on.
> [H] The channel to group address mapping actually fits the draft very wel=
l,
> [H] however, the channel/group split/merge functionality is beyond the sc=
ope
> [H] of this draft.
>=20
>    =20
> thanks
> - Heidi
>=20
>=20
> Thanks,
> Liu Hui
>=20
>> > -----Original Message-----
>> > From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of =
Mike
>> > McBride (mmcbride)
>> > Sent: Tuesday, December 07, 2010 8:24 AM
>> > To: Yiqun Cai (ycai); pim@ietf.org
>> > Subject: [pim] draft-ietf-pim-mtid-05 wglc
>> >=20
>>> > > Mike and Stig,  will we need another last call?
>> >=20
>> > Yes, sorry for the delay. Today begins another 2 week wglc for
>> > http://www.ietf.org/id/draft-ietf-pim-mtid-05.txt
>> >=20
>> > Please review the draft and let us know if you support sending it to t=
he
>> > iesg.
>> >=20
>> > thanks,
>> > mike
>> >=20
>>> > > -----Original Message-----
>>> > > From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf =
Of
>>> > > Yiqun Cai (ycai)
>>> > > Sent: Wednesday, September 22, 2010 3:27 PM
>>> > > To: pim@ietf.org
>>> > > Subject: Re: [pim] I-D Action:draft-ietf-pim-mtid-05.txt
>>> > >
>>> > >
>>> > > Chairs, Dimitri,  and WG,
>>> > >
>>> > > The latest update incorporates the comment received from the
>> > discussion
>>> > > during the Last Call.
>>> > >
>>> > > Please review and comment.
>>> > >
>>> > > Mike and Stig,  will we need another last call?
>>> > >
>>> > > Thanks.
>>> > >
>>> > >
>>> > > On 9/22/10 3:00 PM, "Internet-Drafts@ietf.org" <Internet-
>>> > > Drafts@ietf.org>
>>> > > wrote:
>>> > >
>>>> > > > A New Internet-Draft is available from the on-line Internet-Draf=
ts
>>>> > > > directories.
>>>> > > > This draft is a work item of the Protocol Independent Multicast
>>> > > Working Group
>>>> > > > of the IETF.
>>>> > > >
>>>> > > >
>>>> > > > Title           : PIM Multi-Topology ID (MT-ID) Join-Attribute
>>>> > > > Author(s)       : Y. Cai, H. Ou
>>>> > > > Filename        : draft-ietf-pim-mtid-05.txt
>>>> > > > Pages           : 11
>>>> > > > Date            : 2010-09-22
>>>> > > >
>>>> > > > This document introduces a new type of PIM Join Attribute that
>>>> > > > extends PIM signaling to identify a topology that should be used
>> > when
>>>> > > > constructing a particular multicast distribution tree.
>>>> > > >
>>>> > > > A URL for this Internet-Draft is:
>>>> > > > http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-05.txt
>>>> > > >
>>>> > > > Internet-Drafts are also available by anonymous FTP at:
>>>> > > > ftp://ftp.ietf.org/internet-drafts/
>>>> > > >
>>>> > > > Below is the data which will enable a MIME compliant mail reader
>>>> > > > implementation to automatically retrieve the ASCII version of th=
e
>>>> > > > Internet-Draft.
>>>> > > > _______________________________________________
>>>> > > > pim mailing list
>>>> > > > pim@ietf.org
>>>> > > > https://www.ietf.org/mailman/listinfo/pim
>>> > >
>>> > >
>>> > > --
>>> > > Yiqun
>>> > >
>>> > > _______________________________________________
>>> > > pim mailing list
>>> > > pim@ietf.org
>>> > > https://www.ietf.org/mailman/listinfo/pim
>> > _______________________________________________
>> > pim mailing list
>> > pim@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pim
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>=20


--B_3377549204_8835990
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [pim] draft-ietf-pim-mtid-05 wglc</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:10pt'><BR>
<BR>
<BR>
On 1/10/11 7:30 PM, &quot;Liuhui&quot; &lt;<a href=3D"helen.liu@huawei.com">h=
elen.liu@huawei.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><FONT SIZE=
=3D"4"><SPAN STYLE=3D'font-size:11pt'>According to the illustration below, two p=
laces of the draft could be improved:<BR>
&nbsp;<BR>
1</SPAN></FONT></FONT><FONT SIZE=3D"4"><SPAN STYLE=3D'font-size:11pt'><FONT FAC=
E=3D"=E5=AE=8B=E4=BD=93">=EF=BC=8E</FONT><FONT FACE=3D"Verdana, Helvetica, Arial">Section 1 : appe=
nd to the last paragraph<BR>
The draft does not introduce any change to the RPF check procedure used to =
verify the incoming interface when a packet is forwarded. &#8220;It uses mul=
tiple group addresses to identify a unique multicast stream, which requires =
address split and merge to facilitate the address-channel mapping when being=
 applied. The detailed processing is beyond the scope of the document.&#8221=
;<BR>
<BR>
<FONT COLOR=3D"#0000FF">[H3] I think you mean Section 2. Introduction.<BR>
</FONT><FONT COLOR=3D"#0000FE">[H3] </FONT><FONT COLOR=3D"#0000FF">With slight =
modification, we will add this: &nbsp;&#8220;As an example to use the capabi=
lity<BR>
</FONT><FONT COLOR=3D"#0000FE">[H3] </FONT><FONT COLOR=3D"#0000FF">described by=
 this draft, </FONT><FONT COLOR=3D"#0000FE">an application can choose to use g=
roup addresses, and/<BR>
[H3] or source addresses, to identify an unique multicast steam. It might f=
urther<BR>
[H3] need to perform the functions of splitting and merging. But the detail=
ed<BR>
[H3] processing is beyond the scope of the document&#8221;<BR>
</FONT></FONT></SPAN><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font-size:12=
pt'><BR>
</SPAN></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size=
:11pt'> <BR>
2. &nbsp;&nbsp;Section 3.2 : add before other properties<BR>
For each PIM RPF topology created, a unique numerical ID is assigned per PI=
M domain. &nbsp;This ID is called PIM MT-ID. PIM MT-ID has the following pro=
perty,<BR>
&#8220;- It is the path identifier that is used by PIM control plane, but d=
oes not function in the forwarding state for a specific topology. &nbsp;The =
differentiation for topologies on forwarding plane is made by different grou=
p addresses instead.&#8221;<BR>
<BR>
<FONT COLOR=3D"#0000FE">[H3] How about the following<BR>
[H3] </FONT><FONT COLOR=3D"#0000FF">&#8220;- it is the path identifier that i=
s used by PIM control plane, but does not <BR>
</FONT><FONT COLOR=3D"#0000FE">[H3] </FONT><FONT COLOR=3D"#0000FF">function in =
the forwarding state for a specific topology. &nbsp;The differentiation for<=
BR>
</FONT><FONT COLOR=3D"#0000FE">[H3] </FONT><FONT COLOR=3D"#0000FF">topologies o=
n forwarding plane is made by different group addresses, and/or<BR>
</FONT><FONT COLOR=3D"#0000FE">[H3] </FONT><FONT COLOR=3D"#0000FF">sources addr=
esses instead.&#8221;<BR>
<BR>
</FONT><FONT COLOR=3D"#0000FE">[H3] &nbsp;Thanks again for your comments.<BR>
[H3] &nbsp;- Heidi<BR>
<BR>
<BR>
<BR>
</FONT></SPAN></FONT><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font-size:12=
pt'><BR>
</SPAN></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size=
:11pt'>Thanks,<BR>
Liu Hui<BR>
&nbsp;<BR>
&nbsp;<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'fo=
nt-size:10pt'><BR>
<B>From:</B> hou [<a href=3D"mailto:hou@cisco.com">mailto:hou@cisco.com</a>] =
<BR>
<B>Sent:</B> Tuesday, January 11, 2011 3:30 AM<BR>
<B>To:</B> Liuhui; Mike McBride (mmcbride); Yiqun Cai (ycai); <a href=3D"pim@=
ietf.org">pim@ietf.org</a><BR>
<B>Subject:</B> Re: [pim] draft-ietf-pim-mtid-05 wglc<BR>
</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font=
-size:12pt'> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'fo=
nt-size:10pt'>Liu Hui,<BR>
<BR>
<BR>
On 1/10/11 2:05 AM, &quot;Liuhui&quot; &lt;<a href=3D"helen.liu@huawei.com">h=
elen.liu@huawei.com</a>&gt; wrote:<BR>
</SPAN><FONT SIZE=3D"4"><SPAN STYLE=3D'font-size:11pt'>Hi Heidi, <BR>
&nbsp;<BR>
Thanks for your explanation. I suggest some of them be incorporated into th=
e draft to provide more information and for better understanding, if possibl=
e.<BR>
<BR>
</SPAN></FONT></FONT><FONT SIZE=3D"4"><FONT COLOR=3D"#0000FE"><FONT FACE=3D"Times=
 New Roman"><SPAN STYLE=3D'font-size:12pt'>[H2] &nbsp;</SPAN></FONT></FONT></F=
ONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:10pt'>Woul=
d you please supply some specific text and we will be happy to incorporate.<=
BR>
</SPAN><FONT SIZE=3D"4"><SPAN STYLE=3D'font-size:11pt'><BR>
Besides, the introduction part should give clearer illustration on whether =
this method could be used for protection, for load balancing, or for both. &=
nbsp;E.g., &nbsp;duplicated streams on different topologies will be distribu=
ted to the same user group for protection, but to different user groups for =
load balancing. &nbsp;I heard different opinions on this point, but no expli=
cit answer could be found.<BR>
<BR>
</SPAN></FONT></FONT><FONT SIZE=3D"4"><FONT COLOR=3D"#0000FE"><FONT FACE=3D"Times=
 New Roman"><SPAN STYLE=3D'font-size:12pt'>[H2] &nbsp;The draft only mentioned=
 protection as one of the possible use cases. On the other hand<BR>
[H2] &nbsp;the PIM protocols doesn&#8217;t have the knowledge of applicatio=
ns, we intend to focus on <BR>
[H2] &nbsp;the protocol specification, but vendors are free to implement wh=
atever applications <BR>
[H2] &nbsp;they see fit on top of the specification.<BR>
<BR>
thanks<BR>
- Heidi<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'fo=
nt-size:11pt'><BR>
Thanks,<BR>
Liu Hui<BR>
&nbsp;<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'fo=
nt-size:10pt'><BR>
<B>From:</B> hou [<a href=3D"mailto:hou@cisco.com">mailto:hou@cisco.com</a>] =
<BR>
<B>Sent:</B> Friday, January 07, 2011 8:51 AM<BR>
<B>To:</B> Liuhui; Mike McBride (mmcbride); Yiqun Cai (ycai); <a href=3D"pim@=
ietf.org">pim@ietf.org</a><BR>
<B>Subject:</B> Re: [pim] draft-ietf-pim-mtid-05 wglc<BR>
</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font=
-size:12pt'><BR>
</SPAN></FONT></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'fo=
nt-size:10pt'> <FONT COLOR=3D"#0000FF"> [H] Thanks for your review comments. R=
eply inline<BR>
</FONT><BR>
<BR>
On 12/16/10 8:58 PM, &quot;Liuhui&quot; &lt;<a href=3D"helen.liu@huawei.com">=
helen.liu@huawei.com</a>&gt; wrote:<BR>
A few comments on the draft:<BR>
<BR>
The Introduction only mentions the multiple topology over &quot;separate ne=
twork paths&quot;. Is this the only case or can different multicast topologi=
es be built over the same physical link? This should be clarified, as the re=
ferenced [5120] does. <BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] As mentioned in the &#8220;Introduction&#8221;, t=
he main purpose of this<BR>
</FONT> &nbsp;&nbsp;&nbsp;&nbsp;[H] draft is to prevent multicast traffic l=
oss in case of &nbsp;single<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[H] network segment failure. Buil=
ding multicast topologies over<BR>
[H] the same physical network will be against the purpose, but<BR>
[H] can be done if an operator chooses to do so<BR>
<BR>
Besides, it might be better to give some explanations for the mtid attribut=
e's influence on forwarding plane, whether it changes the forwarding state/r=
ule or not.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] At the end of Section 2, we mention that &#8220;T=
he draft does not introduce any <BR>
[H] change to the RPF check procedure used to verify the incoming interface=
<BR>
[H] when a packet is forwarded&#8221;<BR>
</FONT><BR>
<BR>
Finally, not very clear on the using of two group address G1 and G2 (in Int=
roduction section): <BR>
- Since mtid is used to identify the different topology, why additional dif=
ferentiation of group address is needed.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] mtid and group address servers different purposes=
: mtid is the path<BR>
[H] identifier, while the group address defines the content that needs to b=
e<BR>
[H] delivered via the path. <BR>
</FONT><BR>
- Using two addresses to identify the same multicast stream, is it easy to =
be deployed in IPTV network, where group address &nbsp;&nbsp;often correspon=
ds with a channel.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[H] In order to achieve multicast resilience as an en=
d-to-end solution<BR>
[H] for IPTV, or other applications, &nbsp;there will be work from other as=
pects,<BR>
[H] besides the transport/network layer approach, as this draft is focusing=
 on.<BR>
[H] The channel to group address mapping actually fits the draft very well,=
<BR>
[H] however, the channel/group split/merge functionality is beyond the scop=
e<BR>
[H] of this draft.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;<BR>
thanks<BR>
- Heidi<BR>
</FONT><BR>
<BR>
Thanks,<BR>
Liu Hui<BR>
<BR>
&gt; -----Original Message-----<BR>
&gt; From: <a href=3D"pim-bounces@ietf.org">pim-bounces@ietf.org</a> [<a href=
=3D"mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>] On Behalf Of=
 Mike<BR>
&gt; McBride (mmcbride)<BR>
&gt; Sent: Tuesday, December 07, 2010 8:24 AM<BR>
&gt; To: Yiqun Cai (ycai); <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; Subject: [pim] draft-ietf-pim-mtid-05 wglc<BR>
&gt; <BR>
&gt; &gt; Mike and Stig, &nbsp;will we need another last call?<BR>
&gt; <BR>
&gt; Yes, sorry for the delay. Today begins another 2 week wglc for<BR>
&gt; <a href=3D"http://www.ietf.org/id/draft-ietf-pim-mtid-05.txt">http://www=
.ietf.org/id/draft-ietf-pim-mtid-05.txt</a><BR>
&gt; <BR>
&gt; Please review the draft and let us know if you support sending it to t=
he<BR>
&gt; iesg.<BR>
&gt; <BR>
&gt; thanks,<BR>
&gt; mike<BR>
&gt; <BR>
&gt; &gt; -----Original Message-----<BR>
&gt; &gt; From: <a href=3D"pim-bounces@ietf.org">pim-bounces@ietf.org</a> [<a=
 href=3D"mailto:pim-bounces@ietf.org">mailto:pim-bounces@ietf.org</a>] On Beha=
lf Of<BR>
&gt; &gt; Yiqun Cai (ycai)<BR>
&gt; &gt; Sent: Wednesday, September 22, 2010 3:27 PM<BR>
&gt; &gt; To: <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; &gt; Subject: Re: [pim] I-D Action:draft-ietf-pim-mtid-05.txt<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; Chairs, Dimitri, &nbsp;and WG,<BR>
&gt; &gt;<BR>
&gt; &gt; The latest update incorporates the comment received from the<BR>
&gt; discussion<BR>
&gt; &gt; during the Last Call.<BR>
&gt; &gt;<BR>
&gt; &gt; Please review and comment.<BR>
&gt; &gt;<BR>
&gt; &gt; Mike and Stig, &nbsp;will we need another last call?<BR>
&gt; &gt;<BR>
&gt; &gt; Thanks.<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; On 9/22/10 3:00 PM, &quot;<a href=3D"Internet-Drafts@ietf.org">Inte=
rnet-Drafts@ietf.org</a>&quot; &lt;Internet-<BR>
&gt; &gt; <a href=3D"Drafts@ietf.org">Drafts@ietf.org</a>&gt;<BR>
&gt; &gt; wrote:<BR>
&gt; &gt;<BR>
&gt; &gt; &gt; A New Internet-Draft is available from the on-line Internet-=
Drafts<BR>
&gt; &gt; &gt; directories.<BR>
&gt; &gt; &gt; This draft is a work item of the Protocol Independent Multic=
ast<BR>
&gt; &gt; Working Group<BR>
&gt; &gt; &gt; of the IETF.<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Title &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;: PIM Multi-Topology ID (MT-ID) Join-Attribute<BR>
&gt; &gt; &gt; Author(s) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Y. Cai, H. O=
u<BR>
&gt; &gt; &gt; Filename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-i=
etf-pim-mtid-05.txt<BR>
&gt; &gt; &gt; Pages &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;: 11<BR>
&gt; &gt; &gt; Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;: 2010-09-22<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; This document introduces a new type of PIM Join Attribute th=
at<BR>
&gt; &gt; &gt; extends PIM signaling to identify a topology that should be =
used<BR>
&gt; when<BR>
&gt; &gt; &gt; constructing a particular multicast distribution tree.<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; A URL for this Internet-Draft is:<BR>
&gt; &gt; &gt; <a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-pim-=
mtid-05.txt">http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-05.txt<=
/a><BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Internet-Drafts are also available by anonymous FTP at:<BR>
&gt; &gt; &gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf=
.org/internet-drafts/</a><BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; Below is the data which will enable a MIME compliant mail re=
ader<BR>
&gt; &gt; &gt; implementation to automatically retrieve the ASCII version o=
f the<BR>
&gt; &gt; &gt; Internet-Draft.<BR>
&gt; &gt; &gt; _______________________________________________<BR>
&gt; &gt; &gt; pim mailing list<BR>
&gt; &gt; &gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://=
www.ietf.org/mailman/listinfo/pim</a><BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; --<BR>
&gt; &gt; Yiqun<BR>
&gt; &gt;<BR>
&gt; &gt; _______________________________________________<BR>
&gt; &gt; pim mailing list<BR>
&gt; &gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.i=
etf.org/mailman/listinfo/pim</a><BR>
&gt; _______________________________________________<BR>
&gt; pim mailing list<BR>
&gt; <a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.o=
rg/mailman/listinfo/pim</a><BR>
_______________________________________________<BR>
pim mailing list<BR>
<a href=3D"pim@ietf.org">pim@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/pim">https://www.ietf.org/ma=
ilman/listinfo/pim</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3377549204_8835990--


From helen.liu@huawei.com  Tue Jan 11 00:48:48 2011
Return-Path: <helen.liu@huawei.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDB073A69BF for <pim@core3.amsl.com>; Tue, 11 Jan 2011 00:48:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.859
X-Spam-Level: 
X-Spam-Status: No, score=-2.859 tagged_above=-999 required=5 tests=[AWL=1.635,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sZ6FDFqhZUwU for <pim@core3.amsl.com>; Tue, 11 Jan 2011 00:48:46 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 08CB93A63EB for <pim@ietf.org>; Tue, 11 Jan 2011 00:48:46 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEU0050ZOF8I5@szxga04-in.huawei.com> for pim@ietf.org; Tue, 11 Jan 2011 16:47:32 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTP id <0LEU009A7OF8FU@szxga04-in.huawei.com> for pim@ietf.org; Tue, 11 Jan 2011 16:47:32 +0800 (CST)
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 11 Jan 2011 16:47:28 +0800
Received: from SZXEML519-MBX.china.huawei.com ([169.254.3.243]) by szxeml404-hub.china.huawei.com ([fe80::75b7:3db9:fedc:a56d%13]) with mapi id 14.01.0218.012; Tue, 11 Jan 2011 16:47:31 +0800
Date: Tue, 11 Jan 2011 08:47:30 +0000
From: Liuhui <helen.liu@huawei.com>
In-reply-to: <C9514F94.ACE9%hou@cisco.com>
X-Originating-IP: [10.110.98.169]
To: hou <hou@cisco.com>, "Mike McBride (mmcbride)" <mmcbride@cisco.com>, "Yiqun Cai (ycai)" <ycai@cisco.com>, "pim@ietf.org" <pim@ietf.org>
Message-id: <0521328FA8CCCE4089CA3C9261A28DD901E5FB@SZXEML519-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_3NHKfZbB743Gt5Hmcpy+AA)"
Content-language: zh-CN
Accept-Language: en-US, zh-CN
Thread-topic: [pim] draft-ietf-pim-mtid-05 wglc
Thread-index: ActapValia8GBshU6kuohlJ+S90GTg6/v+GwAgBdqlAEF8pJjgCnq2IQABZEJ1AADvuUUAALdneBAADT6/A=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <0521328FA8CCCE4089CA3C9261A28DD901E160@SZXEML519-MBX.china.huawei.com> <C9514F94.ACE9%hou@cisco.com>
Subject: Re: [pim] draft-ietf-pim-mtid-05 wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 08:48:48 -0000

--Boundary_(ID_3NHKfZbB743Gt5Hmcpy+AA)
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: base64

SGkgSGVpZGksDQoNCkkgdGhpbmsgeW91ciByZXZpc2lvbiBpcyBhbGwgcmlnaHQuDQoNClRoYW5r
cywNCkxpdSBIdWkNCg0KRnJvbTogaG91IFttYWlsdG86aG91QGNpc2NvLmNvbV0NClNlbnQ6IFR1
ZXNkYXksIEphbnVhcnkgMTEsIDIwMTEgNDowNyBQTQ0KVG86IExpdWh1aTsgTWlrZSBNY0JyaWRl
IChtbWNicmlkZSk7IFlpcXVuIENhaSAoeWNhaSk7IHBpbUBpZXRmLm9yZw0KU3ViamVjdDogUmU6
IFtwaW1dIGRyYWZ0LWlldGYtcGltLW10aWQtMDUgd2dsYw0KDQoNCg0KDQpPbiAxLzEwLzExIDc6
MzAgUE0sICJMaXVodWkiIDxoZWxlbi5saXVAaHVhd2VpLmNvbT4gd3JvdGU6DQpBY2NvcmRpbmcg
dG8gdGhlIGlsbHVzdHJhdGlvbiBiZWxvdywgdHdvIHBsYWNlcyBvZiB0aGUgZHJhZnQgY291bGQg
YmUgaW1wcm92ZWQ6DQoNCjHvvI5TZWN0aW9uIDEgOiBhcHBlbmQgdG8gdGhlIGxhc3QgcGFyYWdy
YXBoDQpUaGUgZHJhZnQgZG9lcyBub3QgaW50cm9kdWNlIGFueSBjaGFuZ2UgdG8gdGhlIFJQRiBj
aGVjayBwcm9jZWR1cmUgdXNlZCB0byB2ZXJpZnkgdGhlIGluY29taW5nIGludGVyZmFjZSB3aGVu
IGEgcGFja2V0IGlzIGZvcndhcmRlZC4g4oCcSXQgdXNlcyBtdWx0aXBsZSBncm91cCBhZGRyZXNz
ZXMgdG8gaWRlbnRpZnkgYSB1bmlxdWUgbXVsdGljYXN0IHN0cmVhbSwgd2hpY2ggcmVxdWlyZXMg
YWRkcmVzcyBzcGxpdCBhbmQgbWVyZ2UgdG8gZmFjaWxpdGF0ZSB0aGUgYWRkcmVzcy1jaGFubmVs
IG1hcHBpbmcgd2hlbiBiZWluZyBhcHBsaWVkLiBUaGUgZGV0YWlsZWQgcHJvY2Vzc2luZyBpcyBi
ZXlvbmQgdGhlIHNjb3BlIG9mIHRoZSBkb2N1bWVudC7igJ0NCg0KW0gzXSBJIHRoaW5rIHlvdSBt
ZWFuIFNlY3Rpb24gMi4gSW50cm9kdWN0aW9uLg0KW0gzXSBXaXRoIHNsaWdodCBtb2RpZmljYXRp
b24sIHdlIHdpbGwgYWRkIHRoaXM6ICDigJxBcyBhbiBleGFtcGxlIHRvIHVzZSB0aGUgY2FwYWJp
bGl0eQ0KW0gzXSBkZXNjcmliZWQgYnkgdGhpcyBkcmFmdCwgYW4gYXBwbGljYXRpb24gY2FuIGNo
b29zZSB0byB1c2UgZ3JvdXAgYWRkcmVzc2VzLCBhbmQvDQpbSDNdIG9yIHNvdXJjZSBhZGRyZXNz
ZXMsIHRvIGlkZW50aWZ5IGFuIHVuaXF1ZSBtdWx0aWNhc3Qgc3RlYW0uIEl0IG1pZ2h0IGZ1cnRo
ZXINCltIM10gbmVlZCB0byBwZXJmb3JtIHRoZSBmdW5jdGlvbnMgb2Ygc3BsaXR0aW5nIGFuZCBt
ZXJnaW5nLiBCdXQgdGhlIGRldGFpbGVkDQpbSDNdIHByb2Nlc3NpbmcgaXMgYmV5b25kIHRoZSBz
Y29wZSBvZiB0aGUgZG9jdW1lbnTigJ0NCg0KDQoyLiAgIFNlY3Rpb24gMy4yIDogYWRkIGJlZm9y
ZSBvdGhlciBwcm9wZXJ0aWVzDQpGb3IgZWFjaCBQSU0gUlBGIHRvcG9sb2d5IGNyZWF0ZWQsIGEg
dW5pcXVlIG51bWVyaWNhbCBJRCBpcyBhc3NpZ25lZCBwZXIgUElNIGRvbWFpbi4gIFRoaXMgSUQg
aXMgY2FsbGVkIFBJTSBNVC1JRC4gUElNIE1ULUlEIGhhcyB0aGUgZm9sbG93aW5nIHByb3BlcnR5
LA0K4oCcLSBJdCBpcyB0aGUgcGF0aCBpZGVudGlmaWVyIHRoYXQgaXMgdXNlZCBieSBQSU0gY29u
dHJvbCBwbGFuZSwgYnV0IGRvZXMgbm90IGZ1bmN0aW9uIGluIHRoZSBmb3J3YXJkaW5nIHN0YXRl
IGZvciBhIHNwZWNpZmljIHRvcG9sb2d5LiAgVGhlIGRpZmZlcmVudGlhdGlvbiBmb3IgdG9wb2xv
Z2llcyBvbiBmb3J3YXJkaW5nIHBsYW5lIGlzIG1hZGUgYnkgZGlmZmVyZW50IGdyb3VwIGFkZHJl
c3NlcyBpbnN0ZWFkLuKAnQ0KDQpbSDNdIEhvdyBhYm91dCB0aGUgZm9sbG93aW5nDQpbSDNdIOKA
nC0gaXQgaXMgdGhlIHBhdGggaWRlbnRpZmllciB0aGF0IGlzIHVzZWQgYnkgUElNIGNvbnRyb2wg
cGxhbmUsIGJ1dCBkb2VzIG5vdA0KW0gzXSBmdW5jdGlvbiBpbiB0aGUgZm9yd2FyZGluZyBzdGF0
ZSBmb3IgYSBzcGVjaWZpYyB0b3BvbG9neS4gIFRoZSBkaWZmZXJlbnRpYXRpb24gZm9yDQpbSDNd
IHRvcG9sb2dpZXMgb24gZm9yd2FyZGluZyBwbGFuZSBpcyBtYWRlIGJ5IGRpZmZlcmVudCBncm91
cCBhZGRyZXNzZXMsIGFuZC9vcg0KW0gzXSBzb3VyY2VzIGFkZHJlc3NlcyBpbnN0ZWFkLuKAnQ0K
DQpbSDNdICBUaGFua3MgYWdhaW4gZm9yIHlvdXIgY29tbWVudHMuDQpbSDNdICAtIEhlaWRpDQoN
Cg0KDQoNClRoYW5rcywNCkxpdSBIdWkNCg0KDQoNCkZyb206IGhvdSBbbWFpbHRvOmhvdUBjaXNj
by5jb21dDQpTZW50OiBUdWVzZGF5LCBKYW51YXJ5IDExLCAyMDExIDM6MzAgQU0NClRvOiBMaXVo
dWk7IE1pa2UgTWNCcmlkZSAobW1jYnJpZGUpOyBZaXF1biBDYWkgKHljYWkpOyBwaW1AaWV0Zi5v
cmcNClN1YmplY3Q6IFJlOiBbcGltXSBkcmFmdC1pZXRmLXBpbS1tdGlkLTA1IHdnbGMNCg0KTGl1
IEh1aSwNCg0KDQpPbiAxLzEwLzExIDI6MDUgQU0sICJMaXVodWkiIDxoZWxlbi5saXVAaHVhd2Vp
LmNvbT4gd3JvdGU6DQpIaSBIZWlkaSwNCg0KVGhhbmtzIGZvciB5b3VyIGV4cGxhbmF0aW9uLiBJ
IHN1Z2dlc3Qgc29tZSBvZiB0aGVtIGJlIGluY29ycG9yYXRlZCBpbnRvIHRoZSBkcmFmdCB0byBw
cm92aWRlIG1vcmUgaW5mb3JtYXRpb24gYW5kIGZvciBiZXR0ZXIgdW5kZXJzdGFuZGluZywgaWYg
cG9zc2libGUuDQoNCltIMl0gIFdvdWxkIHlvdSBwbGVhc2Ugc3VwcGx5IHNvbWUgc3BlY2lmaWMg
dGV4dCBhbmQgd2Ugd2lsbCBiZSBoYXBweSB0byBpbmNvcnBvcmF0ZS4NCg0KQmVzaWRlcywgdGhl
IGludHJvZHVjdGlvbiBwYXJ0IHNob3VsZCBnaXZlIGNsZWFyZXIgaWxsdXN0cmF0aW9uIG9uIHdo
ZXRoZXIgdGhpcyBtZXRob2QgY291bGQgYmUgdXNlZCBmb3IgcHJvdGVjdGlvbiwgZm9yIGxvYWQg
YmFsYW5jaW5nLCBvciBmb3IgYm90aC4gIEUuZy4sICBkdXBsaWNhdGVkIHN0cmVhbXMgb24gZGlm
ZmVyZW50IHRvcG9sb2dpZXMgd2lsbCBiZSBkaXN0cmlidXRlZCB0byB0aGUgc2FtZSB1c2VyIGdy
b3VwIGZvciBwcm90ZWN0aW9uLCBidXQgdG8gZGlmZmVyZW50IHVzZXIgZ3JvdXBzIGZvciBsb2Fk
IGJhbGFuY2luZy4gIEkgaGVhcmQgZGlmZmVyZW50IG9waW5pb25zIG9uIHRoaXMgcG9pbnQsIGJ1
dCBubyBleHBsaWNpdCBhbnN3ZXIgY291bGQgYmUgZm91bmQuDQoNCltIMl0gIFRoZSBkcmFmdCBv
bmx5IG1lbnRpb25lZCBwcm90ZWN0aW9uIGFzIG9uZSBvZiB0aGUgcG9zc2libGUgdXNlIGNhc2Vz
LiBPbiB0aGUgb3RoZXIgaGFuZA0KW0gyXSAgdGhlIFBJTSBwcm90b2NvbHMgZG9lc27igJl0IGhh
dmUgdGhlIGtub3dsZWRnZSBvZiBhcHBsaWNhdGlvbnMsIHdlIGludGVuZCB0byBmb2N1cyBvbg0K
W0gyXSAgdGhlIHByb3RvY29sIHNwZWNpZmljYXRpb24sIGJ1dCB2ZW5kb3JzIGFyZSBmcmVlIHRv
IGltcGxlbWVudCB3aGF0ZXZlciBhcHBsaWNhdGlvbnMNCltIMl0gIHRoZXkgc2VlIGZpdCBvbiB0
b3Agb2YgdGhlIHNwZWNpZmljYXRpb24uDQoNCnRoYW5rcw0KLSBIZWlkaQ0KDQpUaGFua3MsDQpM
aXUgSHVpDQoNCg0KRnJvbTogaG91IFttYWlsdG86aG91QGNpc2NvLmNvbV0NClNlbnQ6IEZyaWRh
eSwgSmFudWFyeSAwNywgMjAxMSA4OjUxIEFNDQpUbzogTGl1aHVpOyBNaWtlIE1jQnJpZGUgKG1t
Y2JyaWRlKTsgWWlxdW4gQ2FpICh5Y2FpKTsgcGltQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW3Bp
bV0gZHJhZnQtaWV0Zi1waW0tbXRpZC0wNSB3Z2xjDQoNCltIXSBUaGFua3MgZm9yIHlvdXIgcmV2
aWV3IGNvbW1lbnRzLiBSZXBseSBpbmxpbmUNCg0KDQpPbiAxMi8xNi8xMCA4OjU4IFBNLCAiTGl1
aHVpIiA8aGVsZW4ubGl1QGh1YXdlaS5jb20+IHdyb3RlOg0KQSBmZXcgY29tbWVudHMgb24gdGhl
IGRyYWZ0Og0KDQpUaGUgSW50cm9kdWN0aW9uIG9ubHkgbWVudGlvbnMgdGhlIG11bHRpcGxlIHRv
cG9sb2d5IG92ZXIgInNlcGFyYXRlIG5ldHdvcmsgcGF0aHMiLiBJcyB0aGlzIHRoZSBvbmx5IGNh
c2Ugb3IgY2FuIGRpZmZlcmVudCBtdWx0aWNhc3QgdG9wb2xvZ2llcyBiZSBidWlsdCBvdmVyIHRo
ZSBzYW1lIHBoeXNpY2FsIGxpbms/IFRoaXMgc2hvdWxkIGJlIGNsYXJpZmllZCwgYXMgdGhlIHJl
ZmVyZW5jZWQgWzUxMjBdIGRvZXMuDQoNCltIXSBBcyBtZW50aW9uZWQgaW4gdGhlIOKAnEludHJv
ZHVjdGlvbuKAnSwgdGhlIG1haW4gcHVycG9zZSBvZiB0aGlzDQogICAgW0hdIGRyYWZ0IGlzIHRv
IHByZXZlbnQgbXVsdGljYXN0IHRyYWZmaWMgbG9zcyBpbiBjYXNlIG9mICBzaW5nbGUNCiAgICAg
ICBbSF0gbmV0d29yayBzZWdtZW50IGZhaWx1cmUuIEJ1aWxkaW5nIG11bHRpY2FzdCB0b3BvbG9n
aWVzIG92ZXINCltIXSB0aGUgc2FtZSBwaHlzaWNhbCBuZXR3b3JrIHdpbGwgYmUgYWdhaW5zdCB0
aGUgcHVycG9zZSwgYnV0DQpbSF0gY2FuIGJlIGRvbmUgaWYgYW4gb3BlcmF0b3IgY2hvb3NlcyB0
byBkbyBzbw0KDQpCZXNpZGVzLCBpdCBtaWdodCBiZSBiZXR0ZXIgdG8gZ2l2ZSBzb21lIGV4cGxh
bmF0aW9ucyBmb3IgdGhlIG10aWQgYXR0cmlidXRlJ3MgaW5mbHVlbmNlIG9uIGZvcndhcmRpbmcg
cGxhbmUsIHdoZXRoZXIgaXQgY2hhbmdlcyB0aGUgZm9yd2FyZGluZyBzdGF0ZS9ydWxlIG9yIG5v
dC4NCg0KW0hdIEF0IHRoZSBlbmQgb2YgU2VjdGlvbiAyLCB3ZSBtZW50aW9uIHRoYXQg4oCcVGhl
IGRyYWZ0IGRvZXMgbm90IGludHJvZHVjZSBhbnkNCltIXSBjaGFuZ2UgdG8gdGhlIFJQRiBjaGVj
ayBwcm9jZWR1cmUgdXNlZCB0byB2ZXJpZnkgdGhlIGluY29taW5nIGludGVyZmFjZQ0KW0hdIHdo
ZW4gYSBwYWNrZXQgaXMgZm9yd2FyZGVk4oCdDQoNCg0KRmluYWxseSwgbm90IHZlcnkgY2xlYXIg
b24gdGhlIHVzaW5nIG9mIHR3byBncm91cCBhZGRyZXNzIEcxIGFuZCBHMiAoaW4gSW50cm9kdWN0
aW9uIHNlY3Rpb24pOg0KLSBTaW5jZSBtdGlkIGlzIHVzZWQgdG8gaWRlbnRpZnkgdGhlIGRpZmZl
cmVudCB0b3BvbG9neSwgd2h5IGFkZGl0aW9uYWwgZGlmZmVyZW50aWF0aW9uIG9mIGdyb3VwIGFk
ZHJlc3MgaXMgbmVlZGVkLg0KDQpbSF0gbXRpZCBhbmQgZ3JvdXAgYWRkcmVzcyBzZXJ2ZXJzIGRp
ZmZlcmVudCBwdXJwb3NlczogbXRpZCBpcyB0aGUgcGF0aA0KW0hdIGlkZW50aWZpZXIsIHdoaWxl
IHRoZSBncm91cCBhZGRyZXNzIGRlZmluZXMgdGhlIGNvbnRlbnQgdGhhdCBuZWVkcyB0byBiZQ0K
W0hdIGRlbGl2ZXJlZCB2aWEgdGhlIHBhdGguDQoNCi0gVXNpbmcgdHdvIGFkZHJlc3NlcyB0byBp
ZGVudGlmeSB0aGUgc2FtZSBtdWx0aWNhc3Qgc3RyZWFtLCBpcyBpdCBlYXN5IHRvIGJlIGRlcGxv
eWVkIGluIElQVFYgbmV0d29yaywgd2hlcmUgZ3JvdXAgYWRkcmVzcyAgIG9mdGVuIGNvcnJlc3Bv
bmRzIHdpdGggYSBjaGFubmVsLg0KDQpbSF0gSW4gb3JkZXIgdG8gYWNoaWV2ZSBtdWx0aWNhc3Qg
cmVzaWxpZW5jZSBhcyBhbiBlbmQtdG8tZW5kIHNvbHV0aW9uDQpbSF0gZm9yIElQVFYsIG9yIG90
aGVyIGFwcGxpY2F0aW9ucywgIHRoZXJlIHdpbGwgYmUgd29yayBmcm9tIG90aGVyIGFzcGVjdHMs
DQpbSF0gYmVzaWRlcyB0aGUgdHJhbnNwb3J0L25ldHdvcmsgbGF5ZXIgYXBwcm9hY2gsIGFzIHRo
aXMgZHJhZnQgaXMgZm9jdXNpbmcgb24uDQpbSF0gVGhlIGNoYW5uZWwgdG8gZ3JvdXAgYWRkcmVz
cyBtYXBwaW5nIGFjdHVhbGx5IGZpdHMgdGhlIGRyYWZ0IHZlcnkgd2VsbCwNCltIXSBob3dldmVy
LCB0aGUgY2hhbm5lbC9ncm91cCBzcGxpdC9tZXJnZSBmdW5jdGlvbmFsaXR5IGlzIGJleW9uZCB0
aGUgc2NvcGUNCltIXSBvZiB0aGlzIGRyYWZ0Lg0KDQoNCnRoYW5rcw0KLSBIZWlkaQ0KDQoNClRo
YW5rcywNCkxpdSBIdWkNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBw
aW0tYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnBpbS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYgT2YgTWlrZQ0KPiBNY0JyaWRlIChtbWNicmlkZSkNCj4gU2VudDogVHVlc2RheSwgRGVjZW1i
ZXIgMDcsIDIwMTAgODoyNCBBTQ0KPiBUbzogWWlxdW4gQ2FpICh5Y2FpKTsgcGltQGlldGYub3Jn
DQo+IFN1YmplY3Q6IFtwaW1dIGRyYWZ0LWlldGYtcGltLW10aWQtMDUgd2dsYw0KPg0KPiA+IE1p
a2UgYW5kIFN0aWcsICB3aWxsIHdlIG5lZWQgYW5vdGhlciBsYXN0IGNhbGw/DQo+DQo+IFllcywg
c29ycnkgZm9yIHRoZSBkZWxheS4gVG9kYXkgYmVnaW5zIGFub3RoZXIgMiB3ZWVrIHdnbGMgZm9y
DQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtaWV0Zi1waW0tbXRpZC0wNS50eHQNCj4N
Cj4gUGxlYXNlIHJldmlldyB0aGUgZHJhZnQgYW5kIGxldCB1cyBrbm93IGlmIHlvdSBzdXBwb3J0
IHNlbmRpbmcgaXQgdG8gdGhlDQo+IGllc2cuDQo+DQo+IHRoYW5rcywNCj4gbWlrZQ0KPg0KPiA+
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4gRnJvbTogcGltLWJvdW5jZXNAaWV0Zi5v
cmcgW21haWx0bzpwaW0tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mDQo+ID4gWWlxdW4g
Q2FpICh5Y2FpKQ0KPiA+IFNlbnQ6IFdlZG5lc2RheSwgU2VwdGVtYmVyIDIyLCAyMDEwIDM6Mjcg
UE0NCj4gPiBUbzogcGltQGlldGYub3JnDQo+ID4gU3ViamVjdDogUmU6IFtwaW1dIEktRCBBY3Rp
b246ZHJhZnQtaWV0Zi1waW0tbXRpZC0wNS50eHQNCj4gPg0KPiA+DQo+ID4gQ2hhaXJzLCBEaW1p
dHJpLCAgYW5kIFdHLA0KPiA+DQo+ID4gVGhlIGxhdGVzdCB1cGRhdGUgaW5jb3Jwb3JhdGVzIHRo
ZSBjb21tZW50IHJlY2VpdmVkIGZyb20gdGhlDQo+IGRpc2N1c3Npb24NCj4gPiBkdXJpbmcgdGhl
IExhc3QgQ2FsbC4NCj4gPg0KPiA+IFBsZWFzZSByZXZpZXcgYW5kIGNvbW1lbnQuDQo+ID4NCj4g
PiBNaWtlIGFuZCBTdGlnLCAgd2lsbCB3ZSBuZWVkIGFub3RoZXIgbGFzdCBjYWxsPw0KPiA+DQo+
ID4gVGhhbmtzLg0KPiA+DQo+ID4NCj4gPiBPbiA5LzIyLzEwIDM6MDAgUE0sICJJbnRlcm5ldC1E
cmFmdHNAaWV0Zi5vcmciIDxJbnRlcm5ldC0NCj4gPiBEcmFmdHNAaWV0Zi5vcmc+DQo+ID4gd3Jv
dGU6DQo+ID4NCj4gPiA+IEEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRo
ZSBvbi1saW5lIEludGVybmV0LURyYWZ0cw0KPiA+ID4gZGlyZWN0b3JpZXMuDQo+ID4gPiBUaGlz
IGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRoZSBQcm90b2NvbCBJbmRlcGVuZGVudCBNdWx0aWNh
c3QNCj4gPiBXb3JraW5nIEdyb3VwDQo+ID4gPiBvZiB0aGUgSUVURi4NCj4gPiA+DQo+ID4gPg0K
PiA+ID4gVGl0bGUgICAgICAgICAgIDogUElNIE11bHRpLVRvcG9sb2d5IElEIChNVC1JRCkgSm9p
bi1BdHRyaWJ1dGUNCj4gPiA+IEF1dGhvcihzKSAgICAgICA6IFkuIENhaSwgSC4gT3UNCj4gPiA+
IEZpbGVuYW1lICAgICAgICA6IGRyYWZ0LWlldGYtcGltLW10aWQtMDUudHh0DQo+ID4gPiBQYWdl
cyAgICAgICAgICAgOiAxMQ0KPiA+ID4gRGF0ZSAgICAgICAgICAgIDogMjAxMC0wOS0yMg0KPiA+
ID4NCj4gPiA+IFRoaXMgZG9jdW1lbnQgaW50cm9kdWNlcyBhIG5ldyB0eXBlIG9mIFBJTSBKb2lu
IEF0dHJpYnV0ZSB0aGF0DQo+ID4gPiBleHRlbmRzIFBJTSBzaWduYWxpbmcgdG8gaWRlbnRpZnkg
YSB0b3BvbG9neSB0aGF0IHNob3VsZCBiZSB1c2VkDQo+IHdoZW4NCj4gPiA+IGNvbnN0cnVjdGlu
ZyBhIHBhcnRpY3VsYXIgbXVsdGljYXN0IGRpc3RyaWJ1dGlvbiB0cmVlLg0KPiA+ID4NCj4gPiA+
IEEgVVJMIGZvciB0aGlzIEludGVybmV0LURyYWZ0IGlzOg0KPiA+ID4gaHR0cDovL3d3dy5pZXRm
Lm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1waW0tbXRpZC0wNS50eHQNCj4gPiA+DQo+
ID4gPiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAg
YXQ6DQo+ID4gPiBmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPiA+ID4NCj4g
PiA+IEJlbG93IGlzIHRoZSBkYXRhIHdoaWNoIHdpbGwgZW5hYmxlIGEgTUlNRSBjb21wbGlhbnQg
bWFpbCByZWFkZXINCj4gPiA+IGltcGxlbWVudGF0aW9uIHRvIGF1dG9tYXRpY2FsbHkgcmV0cmll
dmUgdGhlIEFTQ0lJIHZlcnNpb24gb2YgdGhlDQo+ID4gPiBJbnRlcm5ldC1EcmFmdC4NCj4gPiA+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gPiBw
aW0gbWFpbGluZyBsaXN0DQo+ID4gPiBwaW1AaWV0Zi5vcmcNCj4gPiA+IGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltDQo+ID4NCj4gPg0KPiA+IC0tDQo+ID4gWWlxdW4N
Cj4gPg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQo+ID4gcGltIG1haWxpbmcgbGlzdA0KPiA+IHBpbUBpZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltDQo+IF9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo+IHBpbSBtYWlsaW5nIGxpc3QNCj4gcGltQGlldGYu
b3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KcGltIG1haWxpbmcgbGlz
dA0KcGltQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Bp
bQ0K

--Boundary_(ID_3NHKfZbB743Gt5Hmcpy+AA)
Content-type: text/html; charset=utf-8
Content-transfer-encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHRpdGxl
PlJlOiBbcGltXSBkcmFmdC1pZXRmLXBpbS1tdGlkLTA1IHdnbGM8L3RpdGxlPg0KPHN0eWxlPg0K
PCEtLQ0KIC8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCiBAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OuWui+S9kzsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIg
NDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1
IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEDlrovkvZMiOw0K
CXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpWZXJkYW5hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6VGFob21hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30N
CiAvKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KIHAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRp
di5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9u
dC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseTrlrovkvZM7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5
cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dl
ZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6cGVy
c29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xv
cjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v
bmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0
IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYuU2Vj
dGlvbjENCgl7cGFnZTpTZWN0aW9uMTt9DQotLT4NCjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQogPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4N
CjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KIDxvOnNoYXBlbGF5
b3V0IHY6ZXh0PSJlZGl0Ij4NCiAgPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQog
PC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0i
WkgtQ04iIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iU2VjdGlvbjEi
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+SGkgSGVpZGksPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+SSB0aGluayB5b3VyIHJldmlzaW9uIGlzIGFsbCBy
aWdodC4mbmJzcDsNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDsiPlRoYW5rcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij5MaXUgSHVpPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1
ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAw
Y20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6DQomcXVvdDtUYWhvbWEmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDsNCmZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gaG91IFttYWlsdG86aG91QGNpc2NvLmNvbV0NCjxi
cj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBKYW51YXJ5IDExLCAyMDExIDQ6MDcgUE08YnI+DQo8
Yj5Ubzo8L2I+IExpdWh1aTsgTWlrZSBNY0JyaWRlIChtbWNicmlkZSk7IFlpcXVuIENhaSAoeWNh
aSk7IHBpbUBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW3BpbV0gZHJhZnQtaWV0
Zi1waW0tbXRpZC0wNSB3Z2xjPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbTox
Mi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxicj4NCjxi
cj4NCjxicj4NCk9uIDEvMTAvMTEgNzozMCBQTSwgJnF1b3Q7TGl1aHVpJnF1b3Q7ICZsdDs8YSBo
cmVmPSJoZWxlbi5saXVAaHVhd2VpLmNvbSI+aGVsZW4ubGl1QGh1YXdlaS5jb208L2E+Jmd0OyB3
cm90ZTo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRh
bmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+QWNjb3JkaW5nIHRvIHRoZSBpbGx1c3Ry
YXRpb24gYmVsb3csIHR3byBwbGFjZXMgb2YgdGhlIGRyYWZ0IGNvdWxkIGJlIGltcHJvdmVkOjxi
cj4NCiZuYnNwOzxicj4NCjE8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPu+8
jjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5TZWN0aW9u
IDEgOiBhcHBlbmQgdG8gdGhlIGxhc3QgcGFyYWdyYXBoPGJyPg0KVGhlIGRyYWZ0IGRvZXMgbm90
IGludHJvZHVjZSBhbnkgY2hhbmdlIHRvIHRoZSBSUEYgY2hlY2sgcHJvY2VkdXJlIHVzZWQgdG8g
dmVyaWZ5IHRoZSBpbmNvbWluZyBpbnRlcmZhY2Ugd2hlbiBhIHBhY2tldCBpcyBmb3J3YXJkZWQu
IOKAnEl0IHVzZXMgbXVsdGlwbGUgZ3JvdXAgYWRkcmVzc2VzIHRvIGlkZW50aWZ5IGEgdW5pcXVl
IG11bHRpY2FzdCBzdHJlYW0sIHdoaWNoIHJlcXVpcmVzIGFkZHJlc3Mgc3BsaXQgYW5kIG1lcmdl
IHRvIGZhY2lsaXRhdGUNCiB0aGUgYWRkcmVzcy1jaGFubmVsIG1hcHBpbmcgd2hlbiBiZWluZyBh
cHBsaWVkLiBUaGUgZGV0YWlsZWQgcHJvY2Vzc2luZyBpcyBiZXlvbmQgdGhlIHNjb3BlIG9mIHRo
ZSBkb2N1bWVudC7igJ08YnI+DQo8YnI+DQo8c3BhbiBzdHlsZT0iY29sb3I6Ymx1ZSI+W0gzXSBJ
IHRoaW5rIHlvdSBtZWFuIFNlY3Rpb24gMi4gSW50cm9kdWN0aW9uLjxicj4NCjwvc3Bhbj48c3Bh
biBzdHlsZT0iY29sb3I6IzAwMDBGRSI+W0gzXSA8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOmJs
dWUiPldpdGggc2xpZ2h0IG1vZGlmaWNhdGlvbiwgd2Ugd2lsbCBhZGQgdGhpczogJm5ic3A74oCc
QXMgYW4gZXhhbXBsZSB0byB1c2UgdGhlIGNhcGFiaWxpdHk8YnI+DQo8L3NwYW4+PHNwYW4gc3R5
bGU9ImNvbG9yOiMwMDAwRkUiPltIM10gPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibHVlIj5k
ZXNjcmliZWQgYnkgdGhpcyBkcmFmdCwNCjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6IzAwMDBG
RSI+YW4gYXBwbGljYXRpb24gY2FuIGNob29zZSB0byB1c2UgZ3JvdXAgYWRkcmVzc2VzLCBhbmQv
PGJyPg0KW0gzXSBvciBzb3VyY2UgYWRkcmVzc2VzLCB0byBpZGVudGlmeSBhbiB1bmlxdWUgbXVs
dGljYXN0IHN0ZWFtLiBJdCBtaWdodCBmdXJ0aGVyPGJyPg0KW0gzXSBuZWVkIHRvIHBlcmZvcm0g
dGhlIGZ1bmN0aW9ucyBvZiBzcGxpdHRpbmcgYW5kIG1lcmdpbmcuIEJ1dCB0aGUgZGV0YWlsZWQ8
YnI+DQpbSDNdIHByb2Nlc3NpbmcgaXMgYmV5b25kIHRoZSBzY29wZSBvZiB0aGUgZG9jdW1lbnTi
gJ08YnI+DQo8L3NwYW4+PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij48YnI+DQo8
L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJyPg0KMi4g
Jm5ic3A7Jm5ic3A7U2VjdGlvbiAzLjIgOiBhZGQgYmVmb3JlIG90aGVyIHByb3BlcnRpZXM8YnI+
DQpGb3IgZWFjaCBQSU0gUlBGIHRvcG9sb2d5IGNyZWF0ZWQsIGEgdW5pcXVlIG51bWVyaWNhbCBJ
RCBpcyBhc3NpZ25lZCBwZXIgUElNIGRvbWFpbi4gJm5ic3A7VGhpcyBJRCBpcyBjYWxsZWQgUElN
IE1ULUlELiBQSU0gTVQtSUQgaGFzIHRoZSBmb2xsb3dpbmcgcHJvcGVydHksPGJyPg0K4oCcLSBJ
dCBpcyB0aGUgcGF0aCBpZGVudGlmaWVyIHRoYXQgaXMgdXNlZCBieSBQSU0gY29udHJvbCBwbGFu
ZSwgYnV0IGRvZXMgbm90IGZ1bmN0aW9uIGluIHRoZSBmb3J3YXJkaW5nIHN0YXRlIGZvciBhIHNw
ZWNpZmljIHRvcG9sb2d5LiAmbmJzcDtUaGUgZGlmZmVyZW50aWF0aW9uIGZvciB0b3BvbG9naWVz
IG9uIGZvcndhcmRpbmcgcGxhbmUgaXMgbWFkZSBieSBkaWZmZXJlbnQgZ3JvdXAgYWRkcmVzc2Vz
IGluc3RlYWQu4oCdPGJyPg0KPGJyPg0KPHNwYW4gc3R5bGU9ImNvbG9yOiMwMDAwRkUiPltIM10g
SG93IGFib3V0IHRoZSBmb2xsb3dpbmc8YnI+DQpbSDNdIDwvc3Bhbj48c3BhbiBzdHlsZT0iY29s
b3I6Ymx1ZSI+4oCcLSBpdCBpcyB0aGUgcGF0aCBpZGVudGlmaWVyIHRoYXQgaXMgdXNlZCBieSBQ
SU0gY29udHJvbCBwbGFuZSwgYnV0IGRvZXMgbm90DQo8YnI+DQo8L3NwYW4+PHNwYW4gc3R5bGU9
ImNvbG9yOiMwMDAwRkUiPltIM10gPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibHVlIj5mdW5j
dGlvbiBpbiB0aGUgZm9yd2FyZGluZyBzdGF0ZSBmb3IgYSBzcGVjaWZpYyB0b3BvbG9neS4gJm5i
c3A7VGhlIGRpZmZlcmVudGlhdGlvbiBmb3I8YnI+DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9y
OiMwMDAwRkUiPltIM10gPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibHVlIj50b3BvbG9naWVz
IG9uIGZvcndhcmRpbmcgcGxhbmUgaXMgbWFkZSBieSBkaWZmZXJlbnQgZ3JvdXAgYWRkcmVzc2Vz
LCBhbmQvb3I8YnI+DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMwMDAwRkUiPltIM10gPC9z
cGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibHVlIj5zb3VyY2VzIGFkZHJlc3NlcyBpbnN0ZWFkLuKA
nTxicj4NCjxicj4NCjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6IzAwMDBGRSI+W0gzXSAmbmJz
cDtUaGFua3MgYWdhaW4gZm9yIHlvdXIgY29tbWVudHMuPGJyPg0KW0gzXSAmbmJzcDstIEhlaWRp
PGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPC9zcGFuPjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OywmcXVvdDtzZXJp
ZiZxdW90OyI+PGJyPg0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDsiPlRoYW5rcyw8YnI+DQpMaXUgSHVpPGJyPg0KJm5ic3A7PGJyPg0KJm5ic3A7PGJyPg0K
PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxicj4NCjxi
PkZyb206PC9iPiBob3UgWzxhIGhyZWY9Im1haWx0bzpob3VAY2lzY28uY29tIj5tYWlsdG86aG91
QGNpc2NvLmNvbTwvYT5dIDxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBKYW51YXJ5IDExLCAy
MDExIDM6MzAgQU08YnI+DQo8Yj5Ubzo8L2I+IExpdWh1aTsgTWlrZSBNY0JyaWRlIChtbWNicmlk
ZSk7IFlpcXVuIENhaSAoeWNhaSk7IDxhIGhyZWY9InBpbUBpZXRmLm9yZyI+DQpwaW1AaWV0Zi5v
cmc8L2E+PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbcGltXSBkcmFmdC1pZXRmLXBpbS1tdGlk
LTA1IHdnbGM8YnI+DQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPjxicj4NCjwv
c3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5MaXUgSHVpLDxi
cj4NCjxicj4NCjxicj4NCk9uIDEvMTAvMTEgMjowNSBBTSwgJnF1b3Q7TGl1aHVpJnF1b3Q7ICZs
dDs8YSBocmVmPSJoZWxlbi5saXVAaHVhd2VpLmNvbSI+aGVsZW4ubGl1QGh1YXdlaS5jb208L2E+
Jmd0OyB3cm90ZTo8YnI+DQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+SGkgSGVpZGksDQo8YnI+DQombmJzcDs8YnI+DQpUaGFua3MgZm9yIHlvdXIgZXhw
bGFuYXRpb24uIEkgc3VnZ2VzdCBzb21lIG9mIHRoZW0gYmUgaW5jb3Jwb3JhdGVkIGludG8gdGhl
IGRyYWZ0IHRvIHByb3ZpZGUgbW9yZSBpbmZvcm1hdGlvbiBhbmQgZm9yIGJldHRlciB1bmRlcnN0
YW5kaW5nLCBpZiBwb3NzaWJsZS48YnI+DQo8YnI+DQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7c2Vy
aWYmcXVvdDs7DQpjb2xvcjojMDAwMEZFIj5bSDJdICZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7DQpmb250LWZhbWlseTomcXVvdDtWZXJkYW5h
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPldvdWxkIHlvdSBwbGVhc2Ugc3VwcGx5IHNv
bWUgc3BlY2lmaWMgdGV4dCBhbmQgd2Ugd2lsbCBiZSBoYXBweSB0byBpbmNvcnBvcmF0ZS48YnI+
DQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJyPg0K
QmVzaWRlcywgdGhlIGludHJvZHVjdGlvbiBwYXJ0IHNob3VsZCBnaXZlIGNsZWFyZXIgaWxsdXN0
cmF0aW9uIG9uIHdoZXRoZXIgdGhpcyBtZXRob2QgY291bGQgYmUgdXNlZCBmb3IgcHJvdGVjdGlv
biwgZm9yIGxvYWQgYmFsYW5jaW5nLCBvciBmb3IgYm90aC4gJm5ic3A7RS5nLiwgJm5ic3A7ZHVw
bGljYXRlZCBzdHJlYW1zIG9uIGRpZmZlcmVudCB0b3BvbG9naWVzIHdpbGwgYmUgZGlzdHJpYnV0
ZWQgdG8gdGhlIHNhbWUgdXNlciBncm91cCBmb3IgcHJvdGVjdGlvbiwNCiBidXQgdG8gZGlmZmVy
ZW50IHVzZXIgZ3JvdXBzIGZvciBsb2FkIGJhbGFuY2luZy4gJm5ic3A7SSBoZWFyZCBkaWZmZXJl
bnQgb3BpbmlvbnMgb24gdGhpcyBwb2ludCwgYnV0IG5vIGV4cGxpY2l0IGFuc3dlciBjb3VsZCBi
ZSBmb3VuZC48YnI+DQo8YnI+DQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7DQpj
b2xvcjojMDAwMEZFIj5bSDJdICZuYnNwO1RoZSBkcmFmdCBvbmx5IG1lbnRpb25lZCBwcm90ZWN0
aW9uIGFzIG9uZSBvZiB0aGUgcG9zc2libGUgdXNlIGNhc2VzLiBPbiB0aGUgb3RoZXIgaGFuZDxi
cj4NCltIMl0gJm5ic3A7dGhlIFBJTSBwcm90b2NvbHMgZG9lc27igJl0IGhhdmUgdGhlIGtub3ds
ZWRnZSBvZiBhcHBsaWNhdGlvbnMsIHdlIGludGVuZCB0byBmb2N1cyBvbg0KPGJyPg0KW0gyXSAm
bmJzcDt0aGUgcHJvdG9jb2wgc3BlY2lmaWNhdGlvbiwgYnV0IHZlbmRvcnMgYXJlIGZyZWUgdG8g
aW1wbGVtZW50IHdoYXRldmVyIGFwcGxpY2F0aW9ucw0KPGJyPg0KW0gyXSAmbmJzcDt0aGV5IHNl
ZSBmaXQgb24gdG9wIG9mIHRoZSBzcGVjaWZpY2F0aW9uLjxicj4NCjxicj4NCnRoYW5rczxicj4N
Ci0gSGVpZGk8YnI+DQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+PGJyPg0KVGhhbmtzLDxicj4NCkxpdSBIdWk8YnI+DQombmJzcDs8YnI+DQo8L3NwYW4+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJyPg0KPGI+RnJvbTo8
L2I+IGhvdSBbPGEgaHJlZj0ibWFpbHRvOmhvdUBjaXNjby5jb20iPm1haWx0bzpob3VAY2lzY28u
Y29tPC9hPl0gPGJyPg0KPGI+U2VudDo8L2I+IEZyaWRheSwgSmFudWFyeSAwNywgMjAxMSA4OjUx
IEFNPGJyPg0KPGI+VG86PC9iPiBMaXVodWk7IE1pa2UgTWNCcmlkZSAobW1jYnJpZGUpOyBZaXF1
biBDYWkgKHljYWkpOyA8YSBocmVmPSJwaW1AaWV0Zi5vcmciPg0KcGltQGlldGYub3JnPC9hPjxi
cj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW3BpbV0gZHJhZnQtaWV0Zi1waW0tbXRpZC0wNSB3Z2xj
PGJyPg0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij48YnI+DQo8L3NwYW4+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OzsNCmNvbG9yOmJsdWUiPltIXSBU
aGFua3MgZm9yIHlvdXIgcmV2aWV3IGNvbW1lbnRzLiBSZXBseSBpbmxpbmU8YnI+DQo8L3NwYW4+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJyPg0KPGJyPg0KT24g
MTIvMTYvMTAgODo1OCBQTSwgJnF1b3Q7TGl1aHVpJnF1b3Q7ICZsdDs8YSBocmVmPSJoZWxlbi5s
aXVAaHVhd2VpLmNvbSI+aGVsZW4ubGl1QGh1YXdlaS5jb208L2E+Jmd0OyB3cm90ZTo8YnI+DQpB
IGZldyBjb21tZW50cyBvbiB0aGUgZHJhZnQ6PGJyPg0KPGJyPg0KVGhlIEludHJvZHVjdGlvbiBv
bmx5IG1lbnRpb25zIHRoZSBtdWx0aXBsZSB0b3BvbG9neSBvdmVyICZxdW90O3NlcGFyYXRlIG5l
dHdvcmsgcGF0aHMmcXVvdDsuIElzIHRoaXMgdGhlIG9ubHkgY2FzZSBvciBjYW4gZGlmZmVyZW50
IG11bHRpY2FzdCB0b3BvbG9naWVzIGJlIGJ1aWx0IG92ZXIgdGhlIHNhbWUgcGh5c2ljYWwgbGlu
az8gVGhpcyBzaG91bGQgYmUgY2xhcmlmaWVkLCBhcyB0aGUgcmVmZXJlbmNlZCBbNTEyMF0gZG9l
cy4NCjxicj4NCjxicj4NCjxzcGFuIHN0eWxlPSJjb2xvcjpibHVlIj5bSF0gQXMgbWVudGlvbmVk
IGluIHRoZSDigJxJbnRyb2R1Y3Rpb27igJ0sIHRoZSBtYWluIHB1cnBvc2Ugb2YgdGhpczxicj4N
Cjwvc3Bhbj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtbSF0gZHJhZnQgaXMgdG8gcHJldmVudCBt
dWx0aWNhc3QgdHJhZmZpYyBsb3NzIGluIGNhc2Ugb2YgJm5ic3A7c2luZ2xlPGJyPg0KJm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7W0hdIG5ldHdvcmsgc2VnbWVudCBm
YWlsdXJlLiBCdWlsZGluZyBtdWx0aWNhc3QgdG9wb2xvZ2llcyBvdmVyPGJyPg0KW0hdIHRoZSBz
YW1lIHBoeXNpY2FsIG5ldHdvcmsgd2lsbCBiZSBhZ2FpbnN0IHRoZSBwdXJwb3NlLCBidXQ8YnI+
DQpbSF0gY2FuIGJlIGRvbmUgaWYgYW4gb3BlcmF0b3IgY2hvb3NlcyB0byBkbyBzbzxicj4NCjxi
cj4NCkJlc2lkZXMsIGl0IG1pZ2h0IGJlIGJldHRlciB0byBnaXZlIHNvbWUgZXhwbGFuYXRpb25z
IGZvciB0aGUgbXRpZCBhdHRyaWJ1dGUncyBpbmZsdWVuY2Ugb24gZm9yd2FyZGluZyBwbGFuZSwg
d2hldGhlciBpdCBjaGFuZ2VzIHRoZSBmb3J3YXJkaW5nIHN0YXRlL3J1bGUgb3Igbm90Ljxicj4N
Cjxicj4NCjxzcGFuIHN0eWxlPSJjb2xvcjpibHVlIj5bSF0gQXQgdGhlIGVuZCBvZiBTZWN0aW9u
IDIsIHdlIG1lbnRpb24gdGhhdCDigJxUaGUgZHJhZnQgZG9lcyBub3QgaW50cm9kdWNlIGFueQ0K
PGJyPg0KW0hdIGNoYW5nZSB0byB0aGUgUlBGIGNoZWNrIHByb2NlZHVyZSB1c2VkIHRvIHZlcmlm
eSB0aGUgaW5jb21pbmcgaW50ZXJmYWNlPGJyPg0KW0hdIHdoZW4gYSBwYWNrZXQgaXMgZm9yd2Fy
ZGVk4oCdPGJyPg0KPC9zcGFuPjxicj4NCjxicj4NCkZpbmFsbHksIG5vdCB2ZXJ5IGNsZWFyIG9u
IHRoZSB1c2luZyBvZiB0d28gZ3JvdXAgYWRkcmVzcyBHMSBhbmQgRzIgKGluIEludHJvZHVjdGlv
biBzZWN0aW9uKToNCjxicj4NCi0gU2luY2UgbXRpZCBpcyB1c2VkIHRvIGlkZW50aWZ5IHRoZSBk
aWZmZXJlbnQgdG9wb2xvZ3ksIHdoeSBhZGRpdGlvbmFsIGRpZmZlcmVudGlhdGlvbiBvZiBncm91
cCBhZGRyZXNzIGlzIG5lZWRlZC48YnI+DQo8YnI+DQo8c3BhbiBzdHlsZT0iY29sb3I6Ymx1ZSI+
W0hdIG10aWQgYW5kIGdyb3VwIGFkZHJlc3Mgc2VydmVycyBkaWZmZXJlbnQgcHVycG9zZXM6IG10
aWQgaXMgdGhlIHBhdGg8YnI+DQpbSF0gaWRlbnRpZmllciwgd2hpbGUgdGhlIGdyb3VwIGFkZHJl
c3MgZGVmaW5lcyB0aGUgY29udGVudCB0aGF0IG5lZWRzIHRvIGJlPGJyPg0KW0hdIGRlbGl2ZXJl
ZCB2aWEgdGhlIHBhdGguIDxicj4NCjwvc3Bhbj48YnI+DQotIFVzaW5nIHR3byBhZGRyZXNzZXMg
dG8gaWRlbnRpZnkgdGhlIHNhbWUgbXVsdGljYXN0IHN0cmVhbSwgaXMgaXQgZWFzeSB0byBiZSBk
ZXBsb3llZCBpbiBJUFRWIG5ldHdvcmssIHdoZXJlIGdyb3VwIGFkZHJlc3MgJm5ic3A7Jm5ic3A7
b2Z0ZW4gY29ycmVzcG9uZHMgd2l0aCBhIGNoYW5uZWwuPGJyPg0KPGJyPg0KPHNwYW4gc3R5bGU9
ImNvbG9yOmJsdWUiPltIXSBJbiBvcmRlciB0byBhY2hpZXZlIG11bHRpY2FzdCByZXNpbGllbmNl
IGFzIGFuIGVuZC10by1lbmQgc29sdXRpb248YnI+DQpbSF0gZm9yIElQVFYsIG9yIG90aGVyIGFw
cGxpY2F0aW9ucywgJm5ic3A7dGhlcmUgd2lsbCBiZSB3b3JrIGZyb20gb3RoZXIgYXNwZWN0cyw8
YnI+DQpbSF0gYmVzaWRlcyB0aGUgdHJhbnNwb3J0L25ldHdvcmsgbGF5ZXIgYXBwcm9hY2gsIGFz
IHRoaXMgZHJhZnQgaXMgZm9jdXNpbmcgb24uPGJyPg0KW0hdIFRoZSBjaGFubmVsIHRvIGdyb3Vw
IGFkZHJlc3MgbWFwcGluZyBhY3R1YWxseSBmaXRzIHRoZSBkcmFmdCB2ZXJ5IHdlbGwsPGJyPg0K
W0hdIGhvd2V2ZXIsIHRoZSBjaGFubmVsL2dyb3VwIHNwbGl0L21lcmdlIGZ1bmN0aW9uYWxpdHkg
aXMgYmV5b25kIHRoZSBzY29wZTxicj4NCltIXSBvZiB0aGlzIGRyYWZ0Ljxicj4NCjxicj4NCiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxicj4NCnRoYW5rczxicj4NCi0gSGVpZGk8YnI+DQo8L3Nw
YW4+PGJyPg0KPGJyPg0KVGhhbmtzLDxicj4NCkxpdSBIdWk8YnI+DQo8YnI+DQomZ3Q7IC0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KJmd0OyBGcm9tOiA8YSBocmVmPSJwaW0tYm91bmNl
c0BpZXRmLm9yZyI+cGltLWJvdW5jZXNAaWV0Zi5vcmc8L2E+IFs8YSBocmVmPSJtYWlsdG86cGlt
LWJvdW5jZXNAaWV0Zi5vcmciPm1haWx0bzpwaW0tYm91bmNlc0BpZXRmLm9yZzwvYT5dIE9uIEJl
aGFsZiBPZiBNaWtlPGJyPg0KJmd0OyBNY0JyaWRlIChtbWNicmlkZSk8YnI+DQomZ3Q7IFNlbnQ6
IFR1ZXNkYXksIERlY2VtYmVyIDA3LCAyMDEwIDg6MjQgQU08YnI+DQomZ3Q7IFRvOiBZaXF1biBD
YWkgKHljYWkpOyA8YSBocmVmPSJwaW1AaWV0Zi5vcmciPnBpbUBpZXRmLm9yZzwvYT48YnI+DQom
Z3Q7IFN1YmplY3Q6IFtwaW1dIGRyYWZ0LWlldGYtcGltLW10aWQtMDUgd2dsYzxicj4NCiZndDsg
PGJyPg0KJmd0OyAmZ3Q7IE1pa2UgYW5kIFN0aWcsICZuYnNwO3dpbGwgd2UgbmVlZCBhbm90aGVy
IGxhc3QgY2FsbD88YnI+DQomZ3Q7IDxicj4NCiZndDsgWWVzLCBzb3JyeSBmb3IgdGhlIGRlbGF5
LiBUb2RheSBiZWdpbnMgYW5vdGhlciAyIHdlZWsgd2dsYyBmb3I8YnI+DQomZ3Q7IDxhIGhyZWY9
Imh0dHA6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtaWV0Zi1waW0tbXRpZC0wNS50eHQiPmh0dHA6
Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtaWV0Zi1waW0tbXRpZC0wNS50eHQ8L2E+PGJyPg0KJmd0
OyA8YnI+DQomZ3Q7IFBsZWFzZSByZXZpZXcgdGhlIGRyYWZ0IGFuZCBsZXQgdXMga25vdyBpZiB5
b3Ugc3VwcG9ydCBzZW5kaW5nIGl0IHRvIHRoZTxicj4NCiZndDsgaWVzZy48YnI+DQomZ3Q7IDxi
cj4NCiZndDsgdGhhbmtzLDxicj4NCiZndDsgbWlrZTxicj4NCiZndDsgPGJyPg0KJmd0OyAmZ3Q7
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KJmd0OyAmZ3Q7IEZyb206IDxhIGhyZWY9
InBpbS1ib3VuY2VzQGlldGYub3JnIj5waW0tYm91bmNlc0BpZXRmLm9yZzwvYT4gWzxhIGhyZWY9
Im1haWx0bzpwaW0tYm91bmNlc0BpZXRmLm9yZyI+bWFpbHRvOnBpbS1ib3VuY2VzQGlldGYub3Jn
PC9hPl0gT24gQmVoYWxmIE9mPGJyPg0KJmd0OyAmZ3Q7IFlpcXVuIENhaSAoeWNhaSk8YnI+DQom
Z3Q7ICZndDsgU2VudDogV2VkbmVzZGF5LCBTZXB0ZW1iZXIgMjIsIDIwMTAgMzoyNyBQTTxicj4N
CiZndDsgJmd0OyBUbzogPGEgaHJlZj0icGltQGlldGYub3JnIj5waW1AaWV0Zi5vcmc8L2E+PGJy
Pg0KJmd0OyAmZ3Q7IFN1YmplY3Q6IFJlOiBbcGltXSBJLUQgQWN0aW9uOmRyYWZ0LWlldGYtcGlt
LW10aWQtMDUudHh0PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7
IENoYWlycywgRGltaXRyaSwgJm5ic3A7YW5kIFdHLDxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsg
Jmd0OyBUaGUgbGF0ZXN0IHVwZGF0ZSBpbmNvcnBvcmF0ZXMgdGhlIGNvbW1lbnQgcmVjZWl2ZWQg
ZnJvbSB0aGU8YnI+DQomZ3Q7IGRpc2N1c3Npb248YnI+DQomZ3Q7ICZndDsgZHVyaW5nIHRoZSBM
YXN0IENhbGwuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IFBsZWFzZSByZXZpZXcgYW5k
IGNvbW1lbnQuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IE1pa2UgYW5kIFN0aWcsICZu
YnNwO3dpbGwgd2UgbmVlZCBhbm90aGVyIGxhc3QgY2FsbD88YnI+DQomZ3Q7ICZndDs8YnI+DQom
Z3Q7ICZndDsgVGhhbmtzLjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsg
Jmd0OyBPbiA5LzIyLzEwIDM6MDAgUE0sICZxdW90OzxhIGhyZWY9IkludGVybmV0LURyYWZ0c0Bp
ZXRmLm9yZyI+SW50ZXJuZXQtRHJhZnRzQGlldGYub3JnPC9hPiZxdW90OyAmbHQ7SW50ZXJuZXQt
PGJyPg0KJmd0OyAmZ3Q7IDxhIGhyZWY9IkRyYWZ0c0BpZXRmLm9yZyI+RHJhZnRzQGlldGYub3Jn
PC9hPiZndDs8YnI+DQomZ3Q7ICZndDsgd3JvdGU6PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAm
Z3Q7ICZndDsgQSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxp
bmUgSW50ZXJuZXQtRHJhZnRzPGJyPg0KJmd0OyAmZ3Q7ICZndDsgZGlyZWN0b3JpZXMuPGJyPg0K
Jmd0OyAmZ3Q7ICZndDsgVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUgUHJvdG9jb2wg
SW5kZXBlbmRlbnQgTXVsdGljYXN0PGJyPg0KJmd0OyAmZ3Q7IFdvcmtpbmcgR3JvdXA8YnI+DQom
Z3Q7ICZndDsgJmd0OyBvZiB0aGUgSUVURi48YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsg
Jmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgVGl0bGUgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7OiBQSU0gTXVsdGktVG9wb2xv
Z3kgSUQgKE1ULUlEKSBKb2luLUF0dHJpYnV0ZTxicj4NCiZndDsgJmd0OyAmZ3Q7IEF1dGhvcihz
KSAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs6IFkuIENhaSwgSC4gT3U8YnI+
DQomZ3Q7ICZndDsgJmd0OyBGaWxlbmFtZSAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDs6IGRyYWZ0LWlldGYtcGltLW10aWQtMDUudHh0PGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgUGFnZXMgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7OiAxMTxicj4NCiZndDsgJmd0OyAmZ3Q7IERhdGUgJm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7OiAyMDEw
LTA5LTIyPGJyPg0KJmd0OyAmZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyBUaGlzIGRvY3Vt
ZW50IGludHJvZHVjZXMgYSBuZXcgdHlwZSBvZiBQSU0gSm9pbiBBdHRyaWJ1dGUgdGhhdDxicj4N
CiZndDsgJmd0OyAmZ3Q7IGV4dGVuZHMgUElNIHNpZ25hbGluZyB0byBpZGVudGlmeSBhIHRvcG9s
b2d5IHRoYXQgc2hvdWxkIGJlIHVzZWQ8YnI+DQomZ3Q7IHdoZW48YnI+DQomZ3Q7ICZndDsgJmd0
OyBjb25zdHJ1Y3RpbmcgYSBwYXJ0aWN1bGFyIG11bHRpY2FzdCBkaXN0cmlidXRpb24gdHJlZS48
YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IEEgVVJMIGZvciB0aGlzIElu
dGVybmV0LURyYWZ0IGlzOjxicj4NCiZndDsgJmd0OyAmZ3Q7IDxhIGhyZWY9Imh0dHA6Ly93d3cu
aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtcGltLW10aWQtMDUudHh0Ij5odHRw
Oi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLXBpbS1tdGlkLTA1LnR4
dDwvYT48YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IEludGVybmV0LURy
YWZ0cyBhcmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZUUCBhdDo8YnI+DQomZ3Q7ICZn
dDsgJmd0OyA8YSBocmVmPSJmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLyI+ZnRw
Oi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy88L2E+PGJyPg0KJmd0OyAmZ3Q7ICZndDs8
YnI+DQomZ3Q7ICZndDsgJmd0OyBCZWxvdyBpcyB0aGUgZGF0YSB3aGljaCB3aWxsIGVuYWJsZSBh
IE1JTUUgY29tcGxpYW50IG1haWwgcmVhZGVyPGJyPg0KJmd0OyAmZ3Q7ICZndDsgaW1wbGVtZW50
YXRpb24gdG8gYXV0b21hdGljYWxseSByZXRyaWV2ZSB0aGUgQVNDSUkgdmVyc2lvbiBvZiB0aGU8
YnI+DQomZ3Q7ICZndDsgJmd0OyBJbnRlcm5ldC1EcmFmdC48YnI+DQomZ3Q7ICZndDsgJmd0OyBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsg
Jmd0OyAmZ3Q7IHBpbSBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7ICZndDsgJmd0OyA8YSBocmVmPSJw
aW1AaWV0Zi5vcmciPnBpbUBpZXRmLm9yZzwvYT48YnI+DQomZ3Q7ICZndDsgJmd0OyA8YSBocmVm
PSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbSI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW08L2E+PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0
OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IC0tPGJyPg0KJmd0OyAmZ3Q7IFlpcXVuPGJyPg0KJmd0OyAm
Z3Q7PGJyPg0KJmd0OyAmZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fPGJyPg0KJmd0OyAmZ3Q7IHBpbSBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7ICZndDsg
PGEgaHJlZj0icGltQGlldGYub3JnIj5waW1AaWV0Zi5vcmc8L2E+PGJyPg0KJmd0OyAmZ3Q7IDxh
IGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltIj5odHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbTwvYT48YnI+DQomZ3Q7IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyBwaW0gbWFp
bGluZyBsaXN0PGJyPg0KJmd0OyA8YSBocmVmPSJwaW1AaWV0Zi5vcmciPnBpbUBpZXRmLm9yZzwv
YT48YnI+DQomZ3Q7IDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vcGltIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbTwvYT48YnI+
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCnBp
bSBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJwaW1AaWV0Zi5vcmciPnBpbUBpZXRmLm9yZzwv
YT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Bp
bSI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW08L2E+PC9zcGFuPjxz
cGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9ib2R5Pg0KPC9odG1sPg0K

--Boundary_(ID_3NHKfZbB743Gt5Hmcpy+AA)--

From stig@venaas.com  Tue Jan 11 08:08:09 2011
Return-Path: <stig@venaas.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CFB23A6824 for <pim@core3.amsl.com>; Tue, 11 Jan 2011 08:08:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.293
X-Spam-Level: 
X-Spam-Status: No, score=-102.293 tagged_above=-999 required=5 tests=[AWL=0.307, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4WKtJqMphKJQ for <pim@core3.amsl.com>; Tue, 11 Jan 2011 08:08:08 -0800 (PST)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by core3.amsl.com (Postfix) with ESMTP id 1BFA23A6809 for <pim@ietf.org>; Tue, 11 Jan 2011 08:08:08 -0800 (PST)
Received: from [IPv6:2001:420:4:ea0c:d8ff:796e:15fb:394a] (unknown [IPv6:2001:420:4:ea0c:d8ff:796e:15fb:394a]) by ufisa.uninett.no (Postfix) with ESMTPSA id 6F6A87FEC; Tue, 11 Jan 2011 17:10:23 +0100 (CET)
Message-ID: <4D2C80E8.6010109@venaas.com>
Date: Tue, 11 Jan 2011 08:10:16 -0800
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "adrian.farrel@huawei.com" <adrian.farrel@huawei.com>
References: <031d01cbb13c$fcbd7560$f6386020$@huawei.com>
In-Reply-To: <031d01cbb13c$fcbd7560$f6386020$@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] AD review of draft-ietf-pim-registry
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 16:08:09 -0000

On 1/10/2011 7:09 PM, Adrian Farrel wrote:
> Hi,
>
> Don't panic!
>
> I have performed my AD review of your draft. The purpose of the
> review is to catch any nits or issues before the document goes
> forward to IETF last call and IESG review. By getting these issues
> out at this stage we can hope for a higher quality review and a
> smoother passage through the process.
>
> Cracking draft, thank you.
>
> I have only one observation: this I-D needs to be on the Standards Track
> in order to create a registry (I think!).

Oops, didn't think of that at all, but makes sense :) 03 now submitted.

Stig

> Can you tweak that and resubmit? Then I'll issue IETF last call.
>
> Cheers,
> Adrian
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From Internet-Drafts@ietf.org  Tue Jan 11 08:15:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF5AA28C2C6; Tue, 11 Jan 2011 08:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.508
X-Spam-Level: 
X-Spam-Status: No, score=-102.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CBKkACDyYpjh; Tue, 11 Jan 2011 08:15:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B6493A6A50; Tue, 11 Jan 2011 08:15:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110111161502.22971.83045.idtracker@localhost>
Date: Tue, 11 Jan 2011 08:15:02 -0800
Cc: pim@ietf.org
Subject: [pim] I-D Action:draft-ietf-pim-registry-03.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 16:15:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.


	Title           : A Registry for PIM Message Types
	Author(s)       : S. Venaas
	Filename        : draft-ietf-pim-registry-03.txt
	Pages           : 8
	Date            : 2011-01-11

This document provides instructions to IANA for the creation of a
registry for PIM message types.  It specifies initial content of the
registry based on existing RFCs specifying PIM message types.  It
also specifies a procedure for registering new types.

In addition to this, one message type is reserved, and may be used
for a future extension of the message type space.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-registry-03.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-pim-registry-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-11080311.I-D@ietf.org>


--NextPart--

From iesg-secretary@ietf.org  Tue Jan 11 09:54:05 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B39553A6A7E; Tue, 11 Jan 2011 09:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.464
X-Spam-Level: 
X-Spam-Status: No, score=-102.464 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tWoYjn3PE2SF; Tue, 11 Jan 2011 09:54:04 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1E653A681F; Tue, 11 Jan 2011 09:54:03 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110111175403.16124.76452.idtracker@localhost>
Date: Tue, 11 Jan 2011 09:54:03 -0800
Cc: pim@ietf.org
Subject: [pim] Last Call: <draft-ietf-pim-registry-03.txt> (A Registry for PIM	Message Types) to Informational RFC
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 17:54:05 -0000

The IESG has received a request from the Protocol Independent Multicast
WG (pim) to consider the following document:
- 'A Registry for PIM Message Types'
  <draft-ietf-pim-registry-03.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-01-25. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-pim-registry/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-pim-registry/


No IPR declarations have been submitted directly on this I-D.

From Internet-Drafts@ietf.org  Tue Jan 11 10:45:03 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11FD028C2F2; Tue, 11 Jan 2011 10:45:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRqWH8mEHFzx; Tue, 11 Jan 2011 10:45:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EE6328C2ED; Tue, 11 Jan 2011 10:45:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110111184502.30771.13022.idtracker@localhost>
Date: Tue, 11 Jan 2011 10:45:02 -0800
Cc: pim@ietf.org
Subject: [pim] I-D Action:draft-ietf-pim-mtid-06.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 18:45:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.


	Title           : PIM Multi-Topology ID (MT-ID) Join-Attribute
	Author(s)       : Y. Cai, H. Ou
	Filename        : draft-ietf-pim-mtid-06.txt
	Pages           : 11
	Date            : 2011-01-11

This document introduces a new type of PIM Join Attribute that
extends PIM signaling to identify a topology that should be used when
constructing a particular multicast distribution tree.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-06.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-pim-mtid-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-11104101.I-D@ietf.org>


--NextPart--

From iesg-secretary@ietf.org  Tue Jan 11 11:06:14 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA1F33A6A8A; Tue, 11 Jan 2011 11:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level: 
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HZt4w6lbMY1p; Tue, 11 Jan 2011 11:06:12 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14AD23A67FF; Tue, 11 Jan 2011 11:06:12 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110111190612.4044.64512.idtracker@localhost>
Date: Tue, 11 Jan 2011 11:06:12 -0800
Cc: pim@ietf.org
Subject: [pim] Last Call: <draft-ietf-pim-registry-03.txt> (A Registry for PIM	Message Types) to Proposed Standard
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 19:06:14 -0000

The IESG has received a request from the Protocol Independent Multicast
WG (pim) to consider the following document:
- 'A Registry for PIM Message Types'
  <draft-ietf-pim-registry-03.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-01-25. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-pim-registry/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-pim-registry/


No IPR declarations have been submitted directly on this I-D.

From Internet-Drafts@ietf.org  Wed Jan 12 04:45:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A09D3A6B21; Wed, 12 Jan 2011 04:45:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JSHdABvGE7DJ; Wed, 12 Jan 2011 04:45:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80AB43A6B1D; Wed, 12 Jan 2011 04:45:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110112124501.25134.1184.idtracker@localhost>
Date: Wed, 12 Jan 2011 04:45:01 -0800
Cc: pim@ietf.org
Subject: [pim] I-D Action:draft-ietf-pim-group-rp-mapping-09.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jan 2011 12:45:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.


	Title           : PIM Group-to-RP Mapping
	Author(s)       : B. Joshi, et al.
	Filename        : draft-ietf-pim-group-rp-mapping-09.txt
	Pages           : 19
	Date            : 2011-01-12

Each PIM-SM router in a Protocol Independent Multicast (PIM) Domain
which supports Any Source Multicast (ASM) maintains Group-to-RP
mappings which are used to identify a Rendezvous Point(RP) for a
specific multicast group.  PIM-SM has defined an algorithm to choose
a RP from the Group-to-RP mappings learned using various mechanisms.
This algorithm does not consider the PIM mode and the mechanism
through which a Group-to-RP mapping was learned.

This document defines a standard algorithm to deterministically
choose between several Group-to-RP mappings for a specific group.
This document first explains the requirements to extend the
Group-to-RP mapping algorithm and then proposes the new algorithm.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-group-rp-mapping-09.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pim-group-rp-mapping-09.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-12043928.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Thu Jan 27 19:15:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C7E33A6B8A; Thu, 27 Jan 2011 19:15:02 -0800 (PST)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3rKDOQTt39up; Thu, 27 Jan 2011 19:15:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F3533A6B87; Thu, 27 Jan 2011 19:15:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110128031501.4717.32482.idtracker@localhost>
Date: Thu, 27 Jan 2011 19:15:01 -0800
Cc: pim@ietf.org
Subject: [pim] I-D Action:draft-ietf-pim-group-rp-mapping-10.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jan 2011 03:15:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.


	Title           : PIM Group-to-RP Mapping
	Author(s)       : B. Joshi, et al.
	Filename        : draft-ietf-pim-group-rp-mapping-10.txt
	Pages           : 19
	Date            : 2011-01-27

Each PIM-SM router in a Protocol Independent Multicast (PIM) Domain
which supports Any Source Multicast (ASM) maintains Group-to-RP
mappings which are used to identify a Rendezvous Point(RP) for a
specific multicast group.  PIM-SM has defined an algorithm to choose
a RP from the Group-to-RP mappings learned using various mechanisms.
This algorithm does not consider the PIM mode and the mechanism
through which a Group-to-RP mapping was learned.

This document defines a standard algorithm to deterministically
choose between several Group-to-RP mappings for a specific group.
This document first explains the requirements to extend the
Group-to-RP mapping algorithm and then proposes the new algorithm.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-group-rp-mapping-10.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pim-group-rp-mapping-10.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-27191344.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Mon Jan 31 12:15:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 792AA3A6C70; Mon, 31 Jan 2011 12:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b0LfuQiYCA6C; Mon, 31 Jan 2011 12:15:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE7283A6C4D; Mon, 31 Jan 2011 12:15:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.11
Message-ID: <20110131201501.6269.48671.idtracker@localhost>
Date: Mon, 31 Jan 2011 12:15:01 -0800
Cc: pim@ietf.org
Subject: [pim] I-D Action:draft-ietf-pim-registry-04.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jan 2011 20:15:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.


	Title           : A Registry for PIM Message Types
	Author(s)       : S. Venaas
	Filename        : draft-ietf-pim-registry-04.txt
	Pages           : 8
	Date            : 2011-01-31

This document provides instructions to IANA for the creation of a
registry for PIM message types.  It specifies initial content of the
registry based on existing RFCs specifying PIM message types.  It
also specifies a procedure for registering new types.

In addition to this, one message type is reserved, and may be used
for a future extension of the message type space.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-registry-04.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-pim-registry-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-31120205.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Mon Jan 31 16:00:03 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E58DD3A6C9C; Mon, 31 Jan 2011 16:00:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gqwyrA-K7Kmx; Mon, 31 Jan 2011 16:00:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6E7D3A68B1; Mon, 31 Jan 2011 16:00:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.11
Message-ID: <20110201000001.7214.40891.idtracker@localhost>
Date: Mon, 31 Jan 2011 16:00:01 -0800
Cc: pim@ietf.org
Subject: [pim] I-D Action:draft-ietf-pim-mtid-07.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 00:00:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.


	Title           : PIM Multi-Topology ID (MT-ID) Join-Attribute
	Author(s)       : Y. Cai, H. Ou
	Filename        : draft-ietf-pim-mtid-07.txt
	Pages           : 11
	Date            : 2011-01-31

This document introduces a new type of PIM Join Attribute that
extends PIM signaling to identify a topology that should be used when
constructing a particular multicast distribution tree.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-07.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-pim-mtid-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-31154532.I-D@ietf.org>


--NextPart--

From ycai@cisco.com  Mon Jan 31 16:08:06 2011
Return-Path: <ycai@cisco.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 084BA3A6C97 for <pim@core3.amsl.com>; Mon, 31 Jan 2011 16:08:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.532
X-Spam-Level: 
X-Spam-Status: No, score=-8.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id da0-ehtBtvjg for <pim@core3.amsl.com>; Mon, 31 Jan 2011 16:08:05 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 3F75D3A6C8E for <pim@ietf.org>; Mon, 31 Jan 2011 16:08:05 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtsHAOrdRk2rR7H+/2dsb2JhbACWWo4fAnOhMZs0gneCVwSFE4cOg0uFKg
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 01 Feb 2011 00:11:20 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p110BKN0011385 for <pim@ietf.org>; Tue, 1 Feb 2011 00:11:20 GMT
Received: from xmb-sjc-216.amer.cisco.com ([171.70.151.184]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 31 Jan 2011 16:11:20 -0800
Received: from 128.107.163.124 ([128.107.163.124]) by xmb-sjc-216.amer.cisco.com ([171.70.151.184]) with Microsoft Exchange Server HTTP-DAV ; Tue,  1 Feb 2011 00:11:20 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Mon, 31 Jan 2011 16:11:49 -0800
From: Yiqun Cai <ycai@cisco.com>
To: <pim@ietf.org>
Message-ID: <C96C8FC5.9DC7E%ycai@cisco.com>
Thread-Topic: [pim] I-D Action:draft-ietf-pim-mtid-07.txt
Thread-Index: AcvBpJ6bQgRxjWNFBUGWAoL+MnlP+A==
In-Reply-To: <20110201000001.7214.40891.idtracker@localhost>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 01 Feb 2011 00:11:20.0900 (UTC) FILETIME=[8DDC1840:01CBC1A4]
Subject: Re: [pim] I-D Action:draft-ietf-pim-mtid-07.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 00:08:06 -0000

Fellow Pimmers,

The -07 version corrected earlier mistakes on the PIM MT-ID Hello Option
TLV.  We will correct IANA page soon too.  Thanks.



On 1/31/11 4:00 PM, "Internet-Drafts@ietf.org" <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 Protocol Independent Multicast Working Group
> of the IETF.
> 
> 
> Title           : PIM Multi-Topology ID (MT-ID) Join-Attribute
> Author(s)       : Y. Cai, H. Ou
> Filename        : draft-ietf-pim-mtid-07.txt
> Pages           : 11
> Date            : 2011-01-31
> 
> This document introduces a new type of PIM Join Attribute that
> extends PIM signaling to identify a topology that should be used when
> constructing a particular multicast distribution tree.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pim-mtid-07.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


-- 
Yiqun

