
From gregimirsky@gmail.com  Thu Jul  1 00:21:14 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFCEF3A67C3; Thu,  1 Jul 2010 00:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.84
X-Spam-Level: *
X-Spam-Status: No, score=1.84 tagged_above=-999 required=5 tests=[AWL=-3.457,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, J_CHICKENPOX_48=0.6, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, SARE_SUB_ENC_GB2312=1.345]
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 NL4HBVrr3+ul; Thu,  1 Jul 2010 00:21:12 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id EA5313A67A5; Thu,  1 Jul 2010 00:21:11 -0700 (PDT)
Received: by vws14 with SMTP id 14so408566vws.31 for <multiple recipients>; Thu, 01 Jul 2010 00:21:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=6iHkWpUKUH19L12kvRW+CmnNw5DQUj50llwo5jXXokU=; b=cWyqGL4htbYYW2TPXk6P8+CXTBHiZ7g55nqkw9e68oVanbMHhMPDBXAfvfhY/bj493 HCxkrCguHfJH4qxxHgptF2wLA2aWoNr5fbSUYnS3gk5ebvA3NV0Gs+1FoOxNXAkSdP5u y3X/G2pASjbD8yv9appSaNorqsSPF0Y7KlL90=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Or+1rOk6sCzdIyq/36CSEzDU5qqn05cxPOqzrShrsPNF3nW7BkRHfeHLmVK9h47CVY /1hl1sGAIvhQf1/1e/ODHBqIRbOQhwzvwpxn77orq5aNdl8ZWtqMSsTUEanGqX5T1VOU 1vLm+IAPnxkqL+ElU8KW7ZwxwiwlPkSgcfT24=
MIME-Version: 1.0
Received: by 10.220.126.152 with SMTP id c24mr532087vcs.152.1277968874326;  Thu, 01 Jul 2010 00:21:14 -0700 (PDT)
Received: by 10.220.96.210 with HTTP; Thu, 1 Jul 2010 00:21:14 -0700 (PDT)
In-Reply-To: <OFEEF3A03F.79F42228-ON48257753.0024F8D5-48257753.00277275@zte.com.cn>
References: <AANLkTimX-ml464zkvOEjztTWIFVSDdNn0wi1FZVoRwD-@mail.gmail.com> <OFEEF3A03F.79F42228-ON48257753.0024F8D5-48257753.00277275@zte.com.cn>
Date: Thu, 1 Jul 2010 00:21:14 -0700
Message-ID: <AANLkTik8kSOXwAqQtjVl5fl1rzti1ZMhtBLeHJGdNSEf@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: xia.liang2@zte.com.cn
Content-Type: multipart/alternative; boundary=001636c93289c9ca3f048a4e50e5
Cc: mpls-tp@ietf.org, danfrost@cisco.com, mpls@ietf.org, stbryant@cisco.com
Subject: Re: [mpls] =?gb2312?b?tPC4tDogW21wbHMtdHBdIFF1ZXN0aW9uIFJFOmRyYWZ0?= =?gb2312?b?LWZyb3N0LW1wbHMtdHAtbG9zcy1kZWxheS0wMg==?=
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 07:21:14 -0000

--001636c93289c9ca3f048a4e50e5
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Dear Xia,
thank you for the reference to OAM Req. I consider Section as special case
of Segment and thus wonder why Segments are not listed.

Regards,
Greg

2010/7/1 <xia.liang2@zte.com.cn>

>
>
> Hi, Greg:
>   As far as I know, RFC5860(MPLS-TP OAM Requirements) clearly defines tha=
t
> LM and DM functions only need to support PWs, LSPs, Sections.
>   From my understanding, maybe the reason is because it's enough for thes=
e
> two performance measurement functions to be concerned on getting the end =
to
> end client service performance information, they don't care about the
> performance information of a part(Segments or SPME) of an end to end path=
.
>
>                         Xia.Liang
>                        Best regards
>
>
>
> mpls-tp-bounces@ietf.org =D0=B4=D3=DA 2010-07-01 02:32:02:
>
>
> > Dear Editors and All,
> > the document states that DM and LM mechanisms described are
> > applicable to PW, LSPs (p2p bidirectional co-routed and associated
> > as well as p2p, p2mp unidirectional), and Sections. I didn't find
> > reference to Segments or SPME. Would described mechanisms apply to
> > SPME? Your clarification greatly appreciated.
> >
> > Regards,
> > Greg_______________________________________________
>
> > mpls-tp mailing list
> > mpls-tp@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls-tp
>
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail i=
s solely property of the sender's organization. This mail communication is =
confidential. Recipients named above are obligated to maintain secrecy and =
are not permitted to disclose the contents of this communication to others.
> This email and any files transmitted with it are confidential and intende=
d solely for the use of the individual or entity to whom they are addressed=
. If you have received this email in error please notify the originator of =
the message. Any views expressed in this message are those of the individua=
l sender.
> This message has been scanned for viruses and Spam by ZTE Anti-Spam syste=
m.
>
>

--001636c93289c9ca3f048a4e50e5
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Dear Xia,<br>thank you for the reference to OAM Req. I consider Section as =
special case of Segment and thus wonder why Segments are not listed.<br><br=
>Regards,<br>Greg<br><br><div class=3D"gmail_quote">2010/7/1  <span dir=3D"=
ltr">&lt;<a href=3D"mailto:xia.liang2@zte.com.cn">xia.liang2@zte.com.cn</a>=
&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br><font face=3D"sans-serif" size=3D"2"><br>
Hi, Greg: </font>
<br><font face=3D"sans-serif" size=3D"2">&nbsp; As far as I know, RFC5860(M=
PLS-TP
OAM Requirements) clearly defines that LM and DM functions only need to
support PWs, LSPs, Sections. </font>
<br><font face=3D"sans-serif" size=3D"2">&nbsp; From my understanding, mayb=
e
the reason is because it&#39;s enough for these two performance measurement
functions to be concerned on getting the end to end client service performa=
nce
information, they don&#39;t care about the performance information of a par=
t(Segments
or SPME) of an end to end path.</font>
<br>
<br><font face=3D"sans-serif" size=3D"2">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Xia.Liang</font>
<br><font face=3D"sans-serif" size=3D"2">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Best regards</font>
<table>
<tbody><tr>
<td>
<div align=3D"center"></div>
</td><td></td></tr></tbody></table>
<br>
<br>
<br><tt><font size=3D"2"><a href=3D"mailto:mpls-tp-bounces@ietf.org" target=
=3D"_blank">mpls-tp-bounces@ietf.org</a> =D0=B4=D3=DA 2010-07-01 02:32:02:<=
div><div></div><div class=3D"h5"><br>
<br>
&gt; Dear Editors and All,<br>
&gt; the document states that DM and LM mechanisms described are <br>
&gt; applicable to PW, LSPs (p2p bidirectional co-routed and associated
<br>
&gt; as well as p2p, p2mp unidirectional), and Sections. I didn&#39;t find
<br>
&gt; reference to Segments or SPME. Would described mechanisms apply to
<br>
&gt; SPME? Your clarification greatly appreciated.<br>
&gt; <br>
&gt; Regards,<br></div></div>
&gt; Greg_______________________________________________<div class=3D"im"><=
br>
&gt; mpls-tp mailing list<br>
&gt; <a href=3D"mailto:mpls-tp@ietf.org" target=3D"_blank">mpls-tp@ietf.org=
</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mpls-tp" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/mpls-tp</a><br>
</div></font></tt>
<br><div><div></div><div class=3D"h5"><pre>--------------------------------=
------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&n=
bsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property=
&nbsp;of&nbsp;the&nbsp;sender&#39;s&nbsp;organization.&nbsp;This&nbsp;mail&=
nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nb=
sp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;an=
d&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;cont=
ents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbs=
p;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for=
&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbs=
p;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;hav=
e&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;no=
tify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;=
views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbs=
p;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbs=
p;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre></div></div></blockquote></div><br>

--001636c93289c9ca3f048a4e50e5--

From danfrost@cisco.com  Thu Jul  1 00:31:07 2010
Return-Path: <danfrost@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2A783A6897; Thu,  1 Jul 2010 00:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.732
X-Spam-Level: 
X-Spam-Status: No, score=-9.732 tagged_above=-999 required=5 tests=[AWL=0.867,  BAYES_00=-2.599, 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 0yXwEwAKd4zw; Thu,  1 Jul 2010 00:30:37 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 6F4323A6855; Thu,  1 Jul 2010 00:30:35 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.53,518,1272844800"; d="scan'208";a="127473696"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 01 Jul 2010 07:30:39 +0000
Received: from isolaria.cisco.com (isolaria.cisco.com [64.100.19.13]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o617Udaw020299; Thu, 1 Jul 2010 07:30:39 GMT
Received: from isolaria.cisco.com (isolaria [127.0.0.1]) by isolaria.cisco.com (8.13.1/8.13.1) with ESMTP id o617UcKw021109; Thu, 1 Jul 2010 03:30:38 -0400
Received: (from danfrost@localhost) by isolaria.cisco.com (8.13.1/8.13.1/Submit) id o617Uco5021108; Thu, 1 Jul 2010 08:30:38 +0100
Date: Thu, 1 Jul 2010 08:30:38 +0100
From: Dan Frost <danfrost@cisco.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Message-ID: <20100701073038.GA19177@cisco.com>
References: <AANLkTimX-ml464zkvOEjztTWIFVSDdNn0wi1FZVoRwD-@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AANLkTimX-ml464zkvOEjztTWIFVSDdNn0wi1FZVoRwD-@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Cc: mpls@ietf.org, mpls-tp@ietf.org, stbryant@cisco.com
Subject: Re: [mpls] Question RE:draft-frost-mpls-tp-loss-delay-02
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 07:31:08 -0000

Hi Greg,

On Wed, Jun 30, 2010 at 11:32:02AM -0700, Greg Mirsky wrote:
> Dear Editors and All,
> the document states that DM and LM mechanisms described are applicable to
> PW, LSPs (p2p bidirectional co-routed and associated as well as p2p, p2mp
> unidirectional), and Sections. I didn't find reference to Segments or SPME.
> Would described mechanisms apply to SPME? Your clarification greatly
> appreciated.

Certainly, since an SPME is just an LSP.

-d

> Regards,
> Greg

From gregimirsky@gmail.com  Thu Jul  1 00:35:47 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5EBD33A67C3; Thu,  1 Jul 2010 00:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.97
X-Spam-Level: 
X-Spam-Status: No, score=-1.97 tagged_above=-999 required=5 tests=[AWL=0.629,  BAYES_00=-2.599]
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 pR6pZb0AoDal; Thu,  1 Jul 2010 00:35:44 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 8C2283A67A1; Thu,  1 Jul 2010 00:35:42 -0700 (PDT)
Received: by vws14 with SMTP id 14so420779vws.31 for <multiple recipients>; Thu, 01 Jul 2010 00:35:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=WnbJtjthGjQ93qvSpm5lzsYfH3vgdNsavmLszcU6OKc=; b=X4Ns+3YZ0H50/+ZUpVG+DROsqHmCQbzzoV3ALOwLHyufk4p+6bWTbewY0TQgvGlP+/ PC+hs7+ZQruN3fYecj0NNnCdl7aX6aEP/9YXtLfrLCyFjtckoAysLarPwcT2TF9zwOnC hsqoJHkvK4eBLERxUi/LmISLb1v10S5+Jw4QQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ilpGsbtEEpKCWfA7sTMKVcrwbYwfY4xa72V0EPwKQ+8YVLhv4Uf+BqVka1Hl5ga1BA 9yzax0a/1xzAxVreRwt1ymPhIgwFMYabORGbpbdJ97GuWm2mUOYxZjFdZgloHzS9x00Q yekLsZreK2hGs4vsBGiY/A5WFquq+JTxImJqw=
MIME-Version: 1.0
Received: by 10.220.63.71 with SMTP id a7mr76520vci.11.1277969743610; Thu, 01  Jul 2010 00:35:43 -0700 (PDT)
Received: by 10.220.96.210 with HTTP; Thu, 1 Jul 2010 00:35:43 -0700 (PDT)
In-Reply-To: <20100701073038.GA19177@cisco.com>
References: <AANLkTimX-ml464zkvOEjztTWIFVSDdNn0wi1FZVoRwD-@mail.gmail.com> <20100701073038.GA19177@cisco.com>
Date: Thu, 1 Jul 2010 00:35:43 -0700
Message-ID: <AANLkTin1urGA9UcWMk8Xs2Bhz2QMnYlzBqVsnpuCifk_@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Dan Frost <danfrost@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mpls@ietf.org, mpls-tp@ietf.org, stbryant@cisco.com
Subject: Re: [mpls] Question RE:draft-frost-mpls-tp-loss-delay-02
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 07:35:47 -0000

Dear Dan,
yes, in essence, the SPME is an LSP but it's a "special" LSP as it
doesn't directly carry client's load. Perhaps you might consider
explicitly listing SPME.

Regards,
Greg

On Thu, Jul 1, 2010 at 12:30 AM, Dan Frost <danfrost@cisco.com> wrote:
> Hi Greg,
>
> On Wed, Jun 30, 2010 at 11:32:02AM -0700, Greg Mirsky wrote:
>> Dear Editors and All,
>> the document states that DM and LM mechanisms described are applicable to
>> PW, LSPs (p2p bidirectional co-routed and associated as well as p2p, p2mp
>> unidirectional), and Sections. I didn't find reference to Segments or SPME.
>> Would described mechanisms apply to SPME? Your clarification greatly
>> appreciated.
>
> Certainly, since an SPME is just an LSP.
>
> -d
>
>> Regards,
>> Greg
>

From yljiang@huawei.com  Thu Jul  1 02:15:12 2010
Return-Path: <yljiang@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D134E3A68AA for <mpls@core3.amsl.com>; Thu,  1 Jul 2010 02:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 9YhFhZuPXW4l for <mpls@core3.amsl.com>; Thu,  1 Jul 2010 02:15:11 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 44E533A67F7 for <mpls@ietf.org>; Thu,  1 Jul 2010 02:15:11 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4V0002FGC3LP@szxga02-in.huawei.com> for mpls@ietf.org; Thu, 01 Jul 2010 17:14:28 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4V00E05GC39Q@szxga02-in.huawei.com> for mpls@ietf.org; Thu, 01 Jul 2010 17:14:27 +0800 (CST)
Received: from j59929 ([10.70.40.88]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L4V007KLGC33U@szxml06-in.huawei.com> for mpls@ietf.org; Thu, 01 Jul 2010 17:14:27 +0800 (CST)
Date: Thu, 01 Jul 2010 17:14:34 +0800
From: Jiang Yuanlong <yljiang@huawei.com>
To: Loa Andersson <loa@pi.nu>
Message-id: <00e801cb18fd$d2583620$5828460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <4C2A4678.9020806@pi.nu>
Cc: mpls@ietf.org
Subject: Re: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping -	take II
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 09:15:12 -0000

Support.

Thanks
Yuanlong

----- Original Message ----- 
From: "Loa Andersson" <loa@pi.nu>
To: <mpls@ietf.org>
Sent: Wednesday, June 30, 2010 3:16 AM
Subject: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping - 
take II


> Working Group,
>
> this email is to start poll to adopt
> draft-chen-mpls-return-path-specified-lsp-ping
> as an MPLS working group draft.
>
> After recent experience, the chairs would like to remind you all
> what it means to conduct a poll to adopt a draft as a working group
> draft.
>
> - Please recall that the IETF does not "vote." Polls of a working
>   group are to gather information to help the chairs make their
>   decisions. Voting is not part of the normal working methods of
>   an IETF working group.
>
> - The "rough consensus" process used in the working group assumes
>   that people expressing opinions are also participating in the
>   development of standards documents.
>
> - Subscription to the list specifically to express an opinion is
>   noticed by the chairs who has access to information on the new list
>   members. Such behavior is not part of the normal working methods.
>
> - The purpose of a poll for adoption is to help the chairs understand
>   the level of support for a document (i.e. who has read it, who
>   believes it is a good starting point for working group work, who
>   will contribute to the work) and whether there are any significant
>   technical issues. Statements of objection must be backed up by
>   proper technical reasons.
>
> So please respond to this poll indicating whether you support the adoption 
> of this draft or stating your technical issues.
>
> This poll ends eob July 13.
>
>
> Loa and George
> mpls wg co-chairs
> -- 
>
>
> Loa Andersson                         email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                              +46 767 72 92 13
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls 


From root@core3.amsl.com  Thu Jul  1 02:45:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 882C63A67E5; Thu,  1 Jul 2010 02:45:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100701094502.882C63A67E5@core3.amsl.com>
Date: Thu,  1 Jul 2010 02:45:02 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-tp-data-plane-04.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 09: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 Multiprotocol Label Switching Working Group of the IETF.


	Title           : MPLS Transport Profile Data Plane Architecture
	Author(s)       : D. Frost, et al.
	Filename        : draft-ietf-mpls-tp-data-plane-04.txt
	Pages           : 15
	Date            : 2010-07-01

The Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP)
is the set of MPLS protocol functions applicable to the construction
and operation of packet-switched transport networks.  This document
specifies the subset of these functions that comprises the MPLS-TP
data plane: the architectural layer concerned with the encapsulation
and forwarding of packets within an MPLS-TP network.

This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-data-plane-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-mpls-tp-data-plane-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-01023527.I-D@ietf.org>


--NextPart--

From hejia@huawei.com  Thu Jul  1 06:07:30 2010
Return-Path: <hejia@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 297F93A6846 for <mpls@core3.amsl.com>; Thu,  1 Jul 2010 06:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.554
X-Spam-Level: 
X-Spam-Status: No, score=0.554 tagged_above=-999 required=5 tests=[AWL=3.154,  BAYES_00=-2.599]
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 8jPaTTwMzsJK for <mpls@core3.amsl.com>; Thu,  1 Jul 2010 06:07:28 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 840F73A682A for <mpls@ietf.org>; Thu,  1 Jul 2010 06:07:28 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4V00JVHR4QGA@szxga01-in.huawei.com> for mpls@ietf.org; Thu, 01 Jul 2010 21:07:38 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4V005WDR4QSK@szxga01-in.huawei.com> for mpls@ietf.org; Thu, 01 Jul 2010 21:07:38 +0800 (CST)
Received: from h48726 ([10.70.77.157]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L4V00MMKR4Q9G@szxml06-in.huawei.com> for mpls@ietf.org; Thu, 01 Jul 2010 21:07:38 +0800 (CST)
Date: Thu, 01 Jul 2010 21:07:37 +0800
From: Jia HE <hejia@huawei.com>
To: Vishwas Manral <vishwas.ietf@gmail.com>, Loa Andersson <loa@pi.nu>
Message-id: <015c01cb191e$6130ea20$9d4d460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <4C2A4678.9020806@pi.nu> <AANLkTimLqukDS6fWyrwlMPwBtpjhpJPaq6ww_k41SykP@mail.gmail.com>
Cc: mpls@ietf.org
Subject: Re: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping -take II
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 13:07:30 -0000

+1

It might be a good idea to merge all the drafts about LSP Ping extension for easy access. But these extensions might come from different applications. Is it possible to merge? Correct me if I'm wrong. :-)

B.R.
Jia

----- Original Message ----- 
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Loa Andersson" <loa@pi.nu>
Cc: <mpls@ietf.org>
Sent: Thursday, July 01, 2010 2:11 AM
Subject: Re: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping -take II


Support.

We may also however need to merge all LSP ping related extension
drafts into this to have one document instead of multiple such
documents.

Thanks,
Vishwas

On Tue, Jun 29, 2010 at 12:16 PM, Loa Andersson <loa@pi.nu> wrote:
> Working Group,
>
> this email is to start poll to adopt
> draft-chen-mpls-return-path-specified-lsp-ping
> as an MPLS working group draft.
>
> After recent experience, the chairs would like to remind you all
> what it means to conduct a poll to adopt a draft as a working group
> draft.
>
> - Please recall that the IETF does not "vote." Polls of a working
> group are to gather information to help the chairs make their
> decisions. Voting is not part of the normal working methods of
> an IETF working group.
>
> - The "rough consensus" process used in the working group assumes
> that people expressing opinions are also participating in the
> development of standards documents.
>
> - Subscription to the list specifically to express an opinion is
> noticed by the chairs who has access to information on the new list
> members. Such behavior is not part of the normal working methods.
>
> - The purpose of a poll for adoption is to help the chairs understand
> the level of support for a document (i.e. who has read it, who
> believes it is a good starting point for working group work, who
> will contribute to the work) and whether there are any significant
> technical issues. Statements of objection must be backed up by
> proper technical reasons.
>
> So please respond to this poll indicating whether you support the adoption
> of this draft or stating your technical issues.
>
> This poll ends eob July 13.
>
>
> Loa and George
> mpls wg co-chairs
> --
>
>
> Loa Andersson email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager loa@pi.nu
> Ericsson Inc phone: +46 10 717 52 13
> +46 767 72 92 13
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From wwwrun@core3.amsl.com  Thu Jul  1 11:57:40 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 032C128C105; Thu,  1 Jul 2010 11:57:39 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20100701185740.032C128C105@core3.amsl.com>
Date: Thu,  1 Jul 2010 11:57:40 -0700 (PDT)
Cc: mpls mailing list <mpls@ietf.org>, mpls chair <mpls-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [mpls] Protocol Action: 'MPLS Transport Profile Data Plane Architecture' to Proposed Standard
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 18:57:40 -0000

The IESG has approved the following document:

- 'MPLS Transport Profile Data Plane Architecture '
   <draft-ietf-mpls-tp-data-plane-04.txt> as a Proposed Standard


This document is the product of the Multiprotocol Label Switching Working Group. 

The IESG contact persons are Adrian Farrel and Stewart Bryant.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-data-plane-04.txt

Technical Summary

  The MPLS Transport Profile (MPLS-TP) is the set of functions that 
  meet the requirements in RFC5654. The MPLS transport Profile allow
  the deployment and operation of of MPLS based packet-switched 
  transport networks.  MPLS-based packet transport networks
  are defined and described in MPLS-TP Framework.

  This document defines the set of functions that comprise the MPLS-TP
  data plane: the architectural layer concerned with the encapsulation
  and forwarding of packets within an MPLS-TP network.  This layer is
  based on the data plane architectures for MPLS (RFC3031) and
  (RFC3032)) and for Pseudowires (RFC3985).

Working Group Summary

  Since the document is an output from the MPLS-TP project it is the 
  joint output of several IETF working groups and Qustion 9, 10, 12 and
  14 of ITU-T SG15.

Document Quality

   The document is well reviewed in all the groups mentioned above.
   Relevant content can frequently be found in the abstract
   and/or introduction of the document.  If not, this may be 
   an indication that there are deficiencies in the abstract
   or introduction.

Personnel

   Loa Andersson (loa@pi.nu) is the Document Shepherd.
   Adrian Farrel (adrian.farrel@huawei.com) is the Responsible AD.


From zhanghaiyan@huawei.com  Thu Jul  1 18:53:55 2010
Return-Path: <zhanghaiyan@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDE1A3A6823; Thu,  1 Jul 2010 18:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 K8O2thTSF6oY; Thu,  1 Jul 2010 18:53:55 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id DCE643A6767; Thu,  1 Jul 2010 18:53:54 -0700 (PDT)
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 <0L4W000HYQLWU9@szxga03-in.huawei.com>; Fri, 02 Jul 2010 09:53:56 +0800 (CST)
Received: from 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 <0L4W00KUSQLWJG@szxga03-in.huawei.com>; Fri, 02 Jul 2010 09:53:56 +0800 (CST)
Received: from z40693a ([10.70.77.119]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L4W009JFQLV5R@szxml06-in.huawei.com>; Fri, 02 Jul 2010 09:53:56 +0800 (CST)
Date: Fri, 02 Jul 2010 09:53:54 +0800
From: Zhang Haiyan <zhanghaiyan@huawei.com>
To: Loa Andersson <loa@pi.nu>, mpls-tp@ietf.org, mpls@ietf.org, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>
Message-id: <064b01cb1989$6dc2fba0$774d460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <4C1F5616.2060406@pi.nu>
Subject: Re: [mpls] [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jul 2010 01:53:56 -0000

No/ do not support.

Several comments need clarification: 

1) We do not see how the content of the draft satisfies "on-demand-cv" as claimed in the title. We only see "LSP-Ping" and "LSP Traceroute" in the main part of the draft. 
In the introduction part we also see the "on-demand Connectivity Verification, Route Tracing and Adjacency functions". 
Could the authors clarify the "on-demand CV"? 

2) Could the authors clarify the purpose of describing "LSP-Ping with IP encapsulation" and "LSP Traceroute with IP encapsulation"?

The draft seems to be just a regular extension of MPLS LSP ping, not particular for MPLS-TP. Shouldn't it be a draft with the name "mpls-lsp-ping-extensions"?


B.R.
Haiyan


----- Original Message ----- 
From: "Loa Andersson" <loa@pi.nu>
To: <mpls-tp@ietf.org>; <mpls@ietf.org>; "MPLS-TP ad hoc team" <ahmpls-tp@lists.itu.int>
Sent: Monday, June 21, 2010 8:07 PM
Subject: [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document


> 
> Working Group,
> 
> this email is to start poll to adopt
> draft-nitinb-mpls-tp-on-demand-cv-00.txt
> as an MPLS working group draft.
> 
> After recent experience, the chairs would like to remind you all
> what it means to conduct a poll to adopt a draft as a working group
> draft.
> 
> - Please recall that the IETF does not "vote." Polls of a working
>   group are to gather information to help the chairs make their
>   decisions. Voting is not part of the normal working methods of
>   an IETF working group.
> 
> - The "rough consensus" process used in the working group assumes
>   that people expressing opinions are also participating in the
>   development of standards documents.
> 
> - Subscription to the list specifically to express an opinion is
>   noticed by the chairs who has access to information on the new list
>   members. Such behavior is not part of the normal working methods.
> 
> - The purpose of a poll for adoption is to help the chairs understand
>   the level of support for a document (i.e. who has read it, who
>   believes it is a good starting point for working group work, who
>   will contribute to the work) and whether there are any significant
>   technical issues. Statements of objection must be backed up by
>   proper technical reasons.
> 
> So please respond to this poll indicating whether you support the 
> adoption of this draft or stating your technical issues.
> 
> Please also not that this draft has after a discussion with the
> working group chairs been renamed, it was earlier know as
> draft-nitinb-mpls-tp-lsp-ping-extensions-01.
> 
> This poll ends eob July 5.
> 
> 
> Loa and George
> mpls wg co-chairs
> 
> -- 
> 
> 
> Loa Andersson                         email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                              +46 767 72 92 13
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp

From xia.liang2@zte.com.cn  Thu Jul  1 00:13:31 2010
Return-Path: <xia.liang2@zte.com.cn>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DA7C3A67A5; Thu,  1 Jul 2010 00:13:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.19
X-Spam-Level: 
X-Spam-Status: No, score=-92.19 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, J_CHICKENPOX_48=0.6, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_GB2312=1.345, 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 s0jH5G6VgunT; Thu,  1 Jul 2010 00:13:30 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 57EF93A67C3; Thu,  1 Jul 2010 00:13:29 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 552341570495873; Thu, 1 Jul 2010 15:13:08 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 2748.7349437453; Thu, 1 Jul 2010 15:13:34 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o617B6oc039965; Thu, 1 Jul 2010 15:11:06 +0800 (CST) (envelope-from xia.liang2@zte.com.cn)
In-Reply-To: <AANLkTimX-ml464zkvOEjztTWIFVSDdNn0wi1FZVoRwD-@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFEEF3A03F.79F42228-ON48257753.0024F8D5-48257753.00277275@zte.com.cn>
From: xia.liang2@zte.com.cn
Date: Thu, 1 Jul 2010 15:06:08 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-01 15:10:55, Serialize complete at 2010-07-01 15:10:55
Content-Type: multipart/alternative; boundary="=_alternative 0027727248257753_="
X-MAIL: mse2.zte.com.cn o617B6oc039965
X-Mailman-Approved-At: Fri, 02 Jul 2010 07:18:01 -0700
Cc: mpls-tp@ietf.org, danfrost@cisco.com, mpls@ietf.org, stbryant@cisco.com
Subject: [mpls] =?gb2312?b?tPC4tDogW21wbHMtdHBdIFF1ZXN0aW9uIFJFOmRyYWZ0?= =?gb2312?b?LWZyb3N0LW1wbHMtdHAtbG9zcy1kZWxheS0wMg==?=
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 07:13:31 -0000

This is a multipart message in MIME format.
--=_alternative 0027727248257753_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SGksIEdyZWc6IA0KICBBcyBmYXIgYXMgSSBrbm93LCBSRkM1ODYwKE1QTFMtVFAgT0FNIFJlcXVp
cmVtZW50cykgY2xlYXJseSBkZWZpbmVzIHRoYXQgDQpMTSBhbmQgRE0gZnVuY3Rpb25zIG9ubHkg
bmVlZCB0byBzdXBwb3J0IFBXcywgTFNQcywgU2VjdGlvbnMuIA0KICBGcm9tIG15IHVuZGVyc3Rh
bmRpbmcsIG1heWJlIHRoZSByZWFzb24gaXMgYmVjYXVzZSBpdCdzIGVub3VnaCBmb3IgdGhlc2Ug
DQp0d28gcGVyZm9ybWFuY2UgbWVhc3VyZW1lbnQgZnVuY3Rpb25zIHRvIGJlIGNvbmNlcm5lZCBv
biBnZXR0aW5nIHRoZSBlbmQgDQp0byBlbmQgY2xpZW50IHNlcnZpY2UgcGVyZm9ybWFuY2UgaW5m
b3JtYXRpb24sIHRoZXkgZG9uJ3QgY2FyZSBhYm91dCB0aGUgDQpwZXJmb3JtYW5jZSBpbmZvcm1h
dGlvbiBvZiBhIHBhcnQoU2VnbWVudHMgb3IgU1BNRSkgb2YgYW4gZW5kIHRvIGVuZCBwYXRoLg0K
DQogICAgICAgICAgICAgICAgICAgICAgICBYaWEuTGlhbmcNCiAgICAgICAgICAgICAgICAgICAg
ICAgQmVzdCByZWdhcmRzDQoNCg0KDQoNCm1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZyDQtNPaIDIw
MTAtMDctMDEgMDI6MzI6MDI6DQoNCj4gRGVhciBFZGl0b3JzIGFuZCBBbGwsDQo+IHRoZSBkb2N1
bWVudCBzdGF0ZXMgdGhhdCBETSBhbmQgTE0gbWVjaGFuaXNtcyBkZXNjcmliZWQgYXJlIA0KPiBh
cHBsaWNhYmxlIHRvIFBXLCBMU1BzIChwMnAgYmlkaXJlY3Rpb25hbCBjby1yb3V0ZWQgYW5kIGFz
c29jaWF0ZWQgDQo+IGFzIHdlbGwgYXMgcDJwLCBwMm1wIHVuaWRpcmVjdGlvbmFsKSwgYW5kIFNl
Y3Rpb25zLiBJIGRpZG4ndCBmaW5kIA0KPiByZWZlcmVuY2UgdG8gU2VnbWVudHMgb3IgU1BNRS4g
V291bGQgZGVzY3JpYmVkIG1lY2hhbmlzbXMgYXBwbHkgdG8gDQo+IFNQTUU/IFlvdXIgY2xhcmlm
aWNhdGlvbiBncmVhdGx5IGFwcHJlY2lhdGVkLg0KPiANCj4gUmVnYXJkcywNCj4gR3JlZ19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IG1wbHMtdHAgbWFp
bGluZyBsaXN0DQo+IG1wbHMtdHBAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9tcGxzLXRwDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFIEluZm9ybWF0aW9uIFNlY3VyaXR5IE5v
dGljZTogVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIG1haWwgaXMgc29sZWx5IHBy
b3BlcnR5IG9mIHRoZSBzZW5kZXIncyBvcmdhbml6YXRpb24uIFRoaXMgbWFpbCBjb21tdW5pY2F0
aW9uIGlzIGNvbmZpZGVudGlhbC4gUmVjaXBpZW50cyBuYW1lZCBhYm92ZSBhcmUgb2JsaWdhdGVk
IHRvIG1haW50YWluIHNlY3JlY3kgYW5kIGFyZSBub3QgcGVybWl0dGVkIHRvIGRpc2Nsb3NlIHRo
ZSBjb250ZW50cyBvZiB0aGlzIGNvbW11bmljYXRpb24gdG8gb3RoZXJzLg0KVGhpcyBlbWFpbCBh
bmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgYXJlIGNvbmZpZGVudGlhbCBhbmQgaW50
ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9yIGVudGl0eSB0byB3
aG9tIHRoZXkgYXJlIGFkZHJlc3NlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBp
biBlcnJvciBwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIG9mIHRoZSBtZXNzYWdlLiBBbnkg
dmlld3MgZXhwcmVzc2VkIGluIHRoaXMgbWVzc2FnZSBhcmUgdGhvc2Ugb2YgdGhlIGluZGl2aWR1
YWwgc2VuZGVyLg0KVGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNjYW5uZWQgZm9yIHZpcnVzZXMgYW5k
IFNwYW0gYnkgWlRFIEFudGktU3BhbSBzeXN0ZW0uDQo=
--=_alternative 0027727248257753_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCkhpLCBHcmVnOiA8L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyBBcyBmYXIgYXMg
SSBrbm93LCBSRkM1ODYwKE1QTFMtVFANCk9BTSBSZXF1aXJlbWVudHMpIGNsZWFybHkgZGVmaW5l
cyB0aGF0IExNIGFuZCBETSBmdW5jdGlvbnMgb25seSBuZWVkIHRvDQpzdXBwb3J0IFBXcywgTFNQ
cywgU2VjdGlvbnMuIDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+
Jm5ic3A7IEZyb20gbXkgdW5kZXJzdGFuZGluZywgbWF5YmUNCnRoZSByZWFzb24gaXMgYmVjYXVz
ZSBpdCdzIGVub3VnaCBmb3IgdGhlc2UgdHdvIHBlcmZvcm1hbmNlIG1lYXN1cmVtZW50DQpmdW5j
dGlvbnMgdG8gYmUgY29uY2VybmVkIG9uIGdldHRpbmcgdGhlIGVuZCB0byBlbmQgY2xpZW50IHNl
cnZpY2UgcGVyZm9ybWFuY2UNCmluZm9ybWF0aW9uLCB0aGV5IGRvbid0IGNhcmUgYWJvdXQgdGhl
IHBlcmZvcm1hbmNlIGluZm9ybWF0aW9uIG9mIGEgcGFydChTZWdtZW50cw0Kb3IgU1BNRSkgb2Yg
YW4gZW5kIHRvIGVuZCBwYXRoLjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsNCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFhpYS5MaWFuZzwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsNCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7QmVzdCByZWdhcmRzPC9mb250Pg0KPHRhYmxlPg0KPHRyPg0KPHRkPg0KPGRpdiBhbGln
bj1jZW50ZXI+PC9kaXY+DQo8dGQ+PC90YWJsZT4NCjxicj4NCjxicj4NCjxicj48dHQ+PGZvbnQg
c2l6ZT0yPm1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZyDQtNPaIDIwMTAtMDctMDEgMDI6MzI6MDI6
PGJyPg0KPGJyPg0KJmd0OyBEZWFyIEVkaXRvcnMgYW5kIEFsbCw8YnI+DQomZ3Q7IHRoZSBkb2N1
bWVudCBzdGF0ZXMgdGhhdCBETSBhbmQgTE0gbWVjaGFuaXNtcyBkZXNjcmliZWQgYXJlIDxicj4N
CiZndDsgYXBwbGljYWJsZSB0byBQVywgTFNQcyAocDJwIGJpZGlyZWN0aW9uYWwgY28tcm91dGVk
IGFuZCBhc3NvY2lhdGVkDQo8YnI+DQomZ3Q7IGFzIHdlbGwgYXMgcDJwLCBwMm1wIHVuaWRpcmVj
dGlvbmFsKSwgYW5kIFNlY3Rpb25zLiBJIGRpZG4ndCBmaW5kDQo8YnI+DQomZ3Q7IHJlZmVyZW5j
ZSB0byBTZWdtZW50cyBvciBTUE1FLiBXb3VsZCBkZXNjcmliZWQgbWVjaGFuaXNtcyBhcHBseSB0
bw0KPGJyPg0KJmd0OyBTUE1FPyBZb3VyIGNsYXJpZmljYXRpb24gZ3JlYXRseSBhcHByZWNpYXRl
ZC48YnI+DQomZ3Q7IDxicj4NCiZndDsgUmVnYXJkcyw8YnI+DQomZ3Q7IEdyZWdfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsgbXBscy10cCBt
YWlsaW5nIGxpc3Q8YnI+DQomZ3Q7IG1wbHMtdHBAaWV0Zi5vcmc8YnI+DQomZ3Q7IGh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscy10cDxicj4NCjwvZm9udD48L3R0Pg0K
PGJyPjxwcmU+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KWlRFJm5ic3A7SW5mb3JtYXRpb24mbmJzcDtTZWN1cml0eSZuYnNwO05vdGlj
ZTombmJzcDtUaGUmbmJzcDtpbmZvcm1hdGlvbiZuYnNwO2NvbnRhaW5lZCZuYnNwO2luJm5ic3A7
dGhpcyZuYnNwO21haWwmbmJzcDtpcyZuYnNwO3NvbGVseSZuYnNwO3Byb3BlcnR5Jm5ic3A7b2Ym
bmJzcDt0aGUmbmJzcDtzZW5kZXIncyZuYnNwO29yZ2FuaXphdGlvbi4mbmJzcDtUaGlzJm5ic3A7
bWFpbCZuYnNwO2NvbW11bmljYXRpb24mbmJzcDtpcyZuYnNwO2NvbmZpZGVudGlhbC4mbmJzcDtS
ZWNpcGllbnRzJm5ic3A7bmFtZWQmbmJzcDthYm92ZSZuYnNwO2FyZSZuYnNwO29ibGlnYXRlZCZu
YnNwO3RvJm5ic3A7bWFpbnRhaW4mbmJzcDtzZWNyZWN5Jm5ic3A7YW5kJm5ic3A7YXJlJm5ic3A7
bm90Jm5ic3A7cGVybWl0dGVkJm5ic3A7dG8mbmJzcDtkaXNjbG9zZSZuYnNwO3RoZSZuYnNwO2Nv
bnRlbnRzJm5ic3A7b2YmbmJzcDt0aGlzJm5ic3A7Y29tbXVuaWNhdGlvbiZuYnNwO3RvJm5ic3A7
b3RoZXJzLg0KVGhpcyZuYnNwO2VtYWlsJm5ic3A7YW5kJm5ic3A7YW55Jm5ic3A7ZmlsZXMmbmJz
cDt0cmFuc21pdHRlZCZuYnNwO3dpdGgmbmJzcDtpdCZuYnNwO2FyZSZuYnNwO2NvbmZpZGVudGlh
bCZuYnNwO2FuZCZuYnNwO2ludGVuZGVkJm5ic3A7c29sZWx5Jm5ic3A7Zm9yJm5ic3A7dGhlJm5i
c3A7dXNlJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtpbmRpdmlkdWFsJm5ic3A7b3ImbmJzcDtlbnRp
dHkmbmJzcDt0byZuYnNwO3dob20mbmJzcDt0aGV5Jm5ic3A7YXJlJm5ic3A7YWRkcmVzc2VkLiZu
YnNwO0lmJm5ic3A7eW91Jm5ic3A7aGF2ZSZuYnNwO3JlY2VpdmVkJm5ic3A7dGhpcyZuYnNwO2Vt
YWlsJm5ic3A7aW4mbmJzcDtlcnJvciZuYnNwO3BsZWFzZSZuYnNwO25vdGlmeSZuYnNwO3RoZSZu
YnNwO29yaWdpbmF0b3ImbmJzcDtvZiZuYnNwO3RoZSZuYnNwO21lc3NhZ2UuJm5ic3A7QW55Jm5i
c3A7dmlld3MmbmJzcDtleHByZXNzZWQmbmJzcDtpbiZuYnNwO3RoaXMmbmJzcDttZXNzYWdlJm5i
c3A7YXJlJm5ic3A7dGhvc2UmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO2luZGl2aWR1YWwmbmJzcDtz
ZW5kZXIuDQpUaGlzJm5ic3A7bWVzc2FnZSZuYnNwO2hhcyZuYnNwO2JlZW4mbmJzcDtzY2FubmVk
Jm5ic3A7Zm9yJm5ic3A7dmlydXNlcyZuYnNwO2FuZCZuYnNwO1NwYW0mbmJzcDtieSZuYnNwO1pU
RSZuYnNwO0FudGktU3BhbSZuYnNwO3N5c3RlbS4NCjwvcHJlPg==
--=_alternative 0027727248257753_=--


From xia.liang2@zte.com.cn  Thu Jul  1 00:21:16 2010
Return-Path: <xia.liang2@zte.com.cn>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E11A3A67A5; Thu,  1 Jul 2010 00:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.912
X-Spam-Level: 
X-Spam-Status: No, score=-94.912 tagged_above=-999 required=5 tests=[AWL=2.722, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, 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 YAZ2Tb7ERqWK; Thu,  1 Jul 2010 00:21:14 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 3EB803A67A1; Thu,  1 Jul 2010 00:21:12 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 552341911657480; Thu, 1 Jul 2010 15:20:38 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 6892.3038837400; Thu, 1 Jul 2010 15:14:20 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o617IxrJ059356; Thu, 1 Jul 2010 15:19:00 +0800 (CST) (envelope-from xia.liang2@zte.com.cn)
In-Reply-To: <4C2B111A.3000407@pi.nu>
To: Loa Andersson <loa@pi.nu>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFE4D9FE60.CBF194C1-ON48257753.0027A737-48257753.00282B89@zte.com.cn>
From: xia.liang2@zte.com.cn
Date: Thu, 1 Jul 2010 15:14:02 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-01 15:18:49, Serialize complete at 2010-07-01 15:18:49
Content-Type: multipart/alternative; boundary="=_alternative 00282B8748257753_="
X-MAIL: mse2.zte.com.cn o617IxrJ059356
X-Mailman-Approved-At: Fri, 02 Jul 2010 07:18:01 -0700
Cc: mpls@ietf.org, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, mpls-tp-bounces@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [mpls-tp] poll on draft-frost-mpls-tp-loss-delay-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 07:21:16 -0000

This is a multipart message in MIME format.
--=_alternative 00282B8748257753_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

WWVzL1N1cHBvcnQNCg0KDQoNCg0KDQptcGxzLXRwLWJvdW5jZXNAaWV0Zi5vcmcg0LTT2iAyMDEw
LTA2LTMwIDE3OjQwOjQyOg0KDQo+IFdvcmtpbmcgR3JvdXAsDQo+IA0KPiB0aGlzIGVtYWlsIGlz
IHRvIHN0YXJ0IGEgcG9sbCB0byBhZG9wdA0KPiBkcmFmdC1mcm9zdC1tcGxzLXRwLWxvc3MtZGVs
YXktMDIudHh0DQo+IGFzIGFuIE1QTFMgd29ya2luZyBncm91cCBkcmFmdC4NCj4gDQo+IEFmdGVy
IHJlY2VudCBleHBlcmllbmNlLCB0aGUgY2hhaXJzIHdvdWxkIGxpa2UgdG8gcmVtaW5kIHlvdSBh
bGwNCj4gd2hhdCBpdCBtZWFucyB0byBjb25kdWN0IGEgcG9sbCB0byBhZG9wdCBhIGRyYWZ0IGFz
IGEgd29ya2luZyBncm91cA0KPiBkcmFmdC4NCj4gDQo+IC0gUGxlYXNlIHJlY2FsbCB0aGF0IHRo
ZSBJRVRGIGRvZXMgbm90ICJ2b3RlLiIgUG9sbHMgb2YgYSB3b3JraW5nDQo+ICAgIGdyb3VwIGFy
ZSB0byBnYXRoZXIgaW5mb3JtYXRpb24gdG8gaGVscCB0aGUgY2hhaXJzIG1ha2UgdGhlaXINCj4g
ICAgZGVjaXNpb25zLiBWb3RpbmcgaXMgbm90IHBhcnQgb2YgdGhlIG5vcm1hbCB3b3JraW5nIG1l
dGhvZHMgb2YNCj4gICAgYW4gSUVURiB3b3JraW5nIGdyb3VwLg0KPiANCj4gLSBUaGUgInJvdWdo
IGNvbnNlbnN1cyIgcHJvY2VzcyB1c2VkIGluIHRoZSB3b3JraW5nIGdyb3VwIGFzc3VtZXMNCj4g
ICAgdGhhdCBwZW9wbGUgZXhwcmVzc2luZyBvcGluaW9ucyBhcmUgYWxzbyBwYXJ0aWNpcGF0aW5n
IGluIHRoZQ0KPiAgICBkZXZlbG9wbWVudCBvZiBzdGFuZGFyZHMgZG9jdW1lbnRzLg0KPiANCj4g
LSBTdWJzY3JpcHRpb24gdG8gdGhlIGxpc3Qgc3BlY2lmaWNhbGx5IHRvIGV4cHJlc3MgYW4gb3Bp
bmlvbiBpcw0KPiAgICBub3RpY2VkIGJ5IHRoZSBjaGFpcnMgd2hvIGhhcyBhY2Nlc3MgdG8gaW5m
b3JtYXRpb24gb24gdGhlIG5ldyBsaXN0DQo+ICAgIG1lbWJlcnMuIFN1Y2ggYmVoYXZpb3IgaXMg
bm90IHBhcnQgb2YgdGhlIG5vcm1hbCB3b3JraW5nIG1ldGhvZHMuDQo+IA0KPiAtIFRoZSBwdXJw
b3NlIG9mIGEgcG9sbCBmb3IgYWRvcHRpb24gaXMgdG8gaGVscCB0aGUgY2hhaXJzIHVuZGVyc3Rh
bmQNCj4gICAgdGhlIGxldmVsIG9mIHN1cHBvcnQgZm9yIGEgZG9jdW1lbnQgKGkuZS4gd2hvIGhh
cyByZWFkIGl0LCB3aG8NCj4gICAgYmVsaWV2ZXMgaXQgaXMgYSBnb29kIHN0YXJ0aW5nIHBvaW50
IGZvciB3b3JraW5nIGdyb3VwIHdvcmssIHdobw0KPiAgICB3aWxsIGNvbnRyaWJ1dGUgdG8gdGhl
IHdvcmspIGFuZCB3aGV0aGVyIHRoZXJlIGFyZSBhbnkgc2lnbmlmaWNhbnQNCj4gICAgdGVjaG5p
Y2FsIGlzc3Vlcy4gU3RhdGVtZW50cyBvZiBvYmplY3Rpb24gbXVzdCBiZSBiYWNrZWQgdXAgYnkN
Cj4gICAgcHJvcGVyIHRlY2huaWNhbCByZWFzb25zLg0KPiANCj4gU28gcGxlYXNlIHJlc3BvbmQg
dG8gdGhpcyBwb2xsIGluZGljYXRpbmcgd2hldGhlciB5b3Ugc3VwcG9ydCB0aGUgDQo+IGFkb3B0
aW9uIG9mIHRoaXMgZHJhZnQgb3Igc3RhdGluZyB5b3VyIHRlY2huaWNhbCBpc3N1ZXMuDQo+IA0K
PiBUaGlzIHBvbGwgZW5kcyBlb2IgSnVseSAxNS4NCj4gDQo+IA0KPiBMb2EgYW5kIEdlb3JnZQ0K
PiBtcGxzIHdnIGNvLWNoYWlycw0KPiANCj4gLS0gDQo+IA0KPiANCj4gTG9hIEFuZGVyc3NvbiAg
ICAgICAgICAgICAgICAgICAgICAgICBlbWFpbDogbG9hLmFuZGVyc3NvbkBlcmljc3Nvbi5jb20N
Cj4gU3IgU3RyYXRlZ3kgYW5kIFN0YW5kYXJkcyBNYW5hZ2VyICAgICAgICAgICAgbG9hQHBpLm51
DQo+IEVyaWNzc29uIEluYyAgICAgICAgICAgICAgICAgICAgICAgICAgcGhvbmU6ICs0NiAxMCA3
MTcgNTIgMTMNCj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICs0NiA3NjcgNzIgOTIgMTMNCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4gbXBscy10cCBtYWlsaW5nIGxpc3QNCj4gbXBscy10cEBpZXRmLm9yZw0K
PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMtdHANCj4gDQoNCg0K
DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LQ0KWlRFIEluZm9ybWF0aW9uIFNlY3VyaXR5IE5vdGljZTogVGhlIGluZm9ybWF0aW9uIGNvbnRh
aW5lZCBpbiB0aGlzIG1haWwgaXMgc29sZWx5IHByb3BlcnR5IG9mIHRoZSBzZW5kZXIncyBvcmdh
bml6YXRpb24uIFRoaXMgbWFpbCBjb21tdW5pY2F0aW9uIGlzIGNvbmZpZGVudGlhbC4gUmVjaXBp
ZW50cyBuYW1lZCBhYm92ZSBhcmUgb2JsaWdhdGVkIHRvIG1haW50YWluIHNlY3JlY3kgYW5kIGFy
ZSBub3QgcGVybWl0dGVkIHRvIGRpc2Nsb3NlIHRoZSBjb250ZW50cyBvZiB0aGlzIGNvbW11bmlj
YXRpb24gdG8gb3RoZXJzLg0KVGhpcyBlbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdp
dGggaXQgYXJlIGNvbmZpZGVudGlhbCBhbmQgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9m
IHRoZSBpbmRpdmlkdWFsIG9yIGVudGl0eSB0byB3aG9tIHRoZXkgYXJlIGFkZHJlc3NlZC4gSWYg
eW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciBwbGVhc2Ugbm90aWZ5IHRoZSBv
cmlnaW5hdG9yIG9mIHRoZSBtZXNzYWdlLiBBbnkgdmlld3MgZXhwcmVzc2VkIGluIHRoaXMgbWVz
c2FnZSBhcmUgdGhvc2Ugb2YgdGhlIGluZGl2aWR1YWwgc2VuZGVyLg0KVGhpcyBtZXNzYWdlIGhh
cyBiZWVuIHNjYW5uZWQgZm9yIHZpcnVzZXMgYW5kIFNwYW0gYnkgWlRFIEFudGktU3BhbSBzeXN0
ZW0uDQo=
--=_alternative 00282B8748257753_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlllcy9TdXBwb3J0PGJyPg0KPC9m
b250Pg0KPHRhYmxlPg0KPHRyPg0KPHRkPg0KPGRpdiBhbGlnbj1jZW50ZXI+PC9kaXY+DQo8dGQ+
PC90YWJsZT4NCjxicj4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPm1wbHMtdHAtYm91bmNl
c0BpZXRmLm9yZyDQtNPaIDIwMTAtMDYtMzAgMTc6NDA6NDI6PGJyPg0KPGJyPg0KJmd0OyBXb3Jr
aW5nIEdyb3VwLDxicj4NCiZndDsgPGJyPg0KJmd0OyB0aGlzIGVtYWlsIGlzIHRvIHN0YXJ0IGEg
cG9sbCB0byBhZG9wdDxicj4NCiZndDsgZHJhZnQtZnJvc3QtbXBscy10cC1sb3NzLWRlbGF5LTAy
LnR4dDxicj4NCiZndDsgYXMgYW4gTVBMUyB3b3JraW5nIGdyb3VwIGRyYWZ0Ljxicj4NCiZndDsg
PGJyPg0KJmd0OyBBZnRlciByZWNlbnQgZXhwZXJpZW5jZSwgdGhlIGNoYWlycyB3b3VsZCBsaWtl
IHRvIHJlbWluZCB5b3UgYWxsPGJyPg0KJmd0OyB3aGF0IGl0IG1lYW5zIHRvIGNvbmR1Y3QgYSBw
b2xsIHRvIGFkb3B0IGEgZHJhZnQgYXMgYSB3b3JraW5nIGdyb3VwPGJyPg0KJmd0OyBkcmFmdC48
YnI+DQomZ3Q7IDxicj4NCiZndDsgLSBQbGVhc2UgcmVjYWxsIHRoYXQgdGhlIElFVEYgZG9lcyBu
b3QgJnF1b3Q7dm90ZS4mcXVvdDsgUG9sbHMgb2YNCmEgd29ya2luZzxicj4NCiZndDsgJm5ic3A7
ICZuYnNwO2dyb3VwIGFyZSB0byBnYXRoZXIgaW5mb3JtYXRpb24gdG8gaGVscCB0aGUgY2hhaXJz
IG1ha2UNCnRoZWlyPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ZGVjaXNpb25zLiBWb3RpbmcgaXMg
bm90IHBhcnQgb2YgdGhlIG5vcm1hbCB3b3JraW5nIG1ldGhvZHMNCm9mPGJyPg0KJmd0OyAmbmJz
cDsgJm5ic3A7YW4gSUVURiB3b3JraW5nIGdyb3VwLjxicj4NCiZndDsgPGJyPg0KJmd0OyAtIFRo
ZSAmcXVvdDtyb3VnaCBjb25zZW5zdXMmcXVvdDsgcHJvY2VzcyB1c2VkIGluIHRoZSB3b3JraW5n
IGdyb3VwDQphc3N1bWVzPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7dGhhdCBwZW9wbGUgZXhwcmVz
c2luZyBvcGluaW9ucyBhcmUgYWxzbyBwYXJ0aWNpcGF0aW5nDQppbiB0aGU8YnI+DQomZ3Q7ICZu
YnNwOyAmbmJzcDtkZXZlbG9wbWVudCBvZiBzdGFuZGFyZHMgZG9jdW1lbnRzLjxicj4NCiZndDsg
PGJyPg0KJmd0OyAtIFN1YnNjcmlwdGlvbiB0byB0aGUgbGlzdCBzcGVjaWZpY2FsbHkgdG8gZXhw
cmVzcyBhbiBvcGluaW9uIGlzPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7bm90aWNlZCBieSB0aGUg
Y2hhaXJzIHdobyBoYXMgYWNjZXNzIHRvIGluZm9ybWF0aW9uIG9uDQp0aGUgbmV3IGxpc3Q8YnI+
DQomZ3Q7ICZuYnNwOyAmbmJzcDttZW1iZXJzLiBTdWNoIGJlaGF2aW9yIGlzIG5vdCBwYXJ0IG9m
IHRoZSBub3JtYWwgd29ya2luZw0KbWV0aG9kcy48YnI+DQomZ3Q7IDxicj4NCiZndDsgLSBUaGUg
cHVycG9zZSBvZiBhIHBvbGwgZm9yIGFkb3B0aW9uIGlzIHRvIGhlbHAgdGhlIGNoYWlycyB1bmRl
cnN0YW5kPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7dGhlIGxldmVsIG9mIHN1cHBvcnQgZm9yIGEg
ZG9jdW1lbnQgKGkuZS4gd2hvIGhhcyByZWFkDQppdCwgd2hvPGJyPg0KJmd0OyAmbmJzcDsgJm5i
c3A7YmVsaWV2ZXMgaXQgaXMgYSBnb29kIHN0YXJ0aW5nIHBvaW50IGZvciB3b3JraW5nIGdyb3Vw
DQp3b3JrLCB3aG88YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDt3aWxsIGNvbnRyaWJ1dGUgdG8gdGhl
IHdvcmspIGFuZCB3aGV0aGVyIHRoZXJlIGFyZSBhbnkNCnNpZ25pZmljYW50PGJyPg0KJmd0OyAm
bmJzcDsgJm5ic3A7dGVjaG5pY2FsIGlzc3Vlcy4gU3RhdGVtZW50cyBvZiBvYmplY3Rpb24gbXVz
dCBiZSBiYWNrZWQNCnVwIGJ5PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7cHJvcGVyIHRlY2huaWNh
bCByZWFzb25zLjxicj4NCiZndDsgPGJyPg0KJmd0OyBTbyBwbGVhc2UgcmVzcG9uZCB0byB0aGlz
IHBvbGwgaW5kaWNhdGluZyB3aGV0aGVyIHlvdSBzdXBwb3J0IHRoZQ0KPGJyPg0KJmd0OyBhZG9w
dGlvbiBvZiB0aGlzIGRyYWZ0IG9yIHN0YXRpbmcgeW91ciB0ZWNobmljYWwgaXNzdWVzLjxicj4N
CiZndDsgPGJyPg0KJmd0OyBUaGlzIHBvbGwgZW5kcyBlb2IgSnVseSAxNS48YnI+DQomZ3Q7IDxi
cj4NCiZndDsgPGJyPg0KJmd0OyBMb2EgYW5kIEdlb3JnZTxicj4NCiZndDsgbXBscyB3ZyBjby1j
aGFpcnM8YnI+DQomZ3Q7IDxicj4NCiZndDsgLS0gPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4N
CiZndDsgTG9hIEFuZGVyc3NvbiAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgZW1haWw6IGxv
YS5hbmRlcnNzb25AZXJpY3Nzb24uY29tPGJyPg0KJmd0OyBTciBTdHJhdGVneSBhbmQgU3RhbmRh
cmRzIE1hbmFnZXIgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7bG9h
QHBpLm51PGJyPg0KJmd0OyBFcmljc3NvbiBJbmMgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwO3Bob25lOiArNDYgMTAgNzE3IDUyIDEzPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsNCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsNCiZuYnNwOyAmbmJzcDsgKzQ2IDc2NyA3MiA5MiAxMzxicj4NCiZn
dDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQom
Z3Q7IG1wbHMtdHAgbWFpbGluZyBsaXN0PGJyPg0KJmd0OyBtcGxzLXRwQGlldGYub3JnPGJyPg0K
Jmd0OyBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMtdHA8YnI+DQom
Z3Q7IDxicj4NCjwvZm9udD48L3R0Pg0KPGJyPjxwcmU+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFJm5ic3A7SW5mb3JtYXRpb24m
bmJzcDtTZWN1cml0eSZuYnNwO05vdGljZTombmJzcDtUaGUmbmJzcDtpbmZvcm1hdGlvbiZuYnNw
O2NvbnRhaW5lZCZuYnNwO2luJm5ic3A7dGhpcyZuYnNwO21haWwmbmJzcDtpcyZuYnNwO3NvbGVs
eSZuYnNwO3Byb3BlcnR5Jm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtzZW5kZXIncyZuYnNwO29yZ2Fu
aXphdGlvbi4mbmJzcDtUaGlzJm5ic3A7bWFpbCZuYnNwO2NvbW11bmljYXRpb24mbmJzcDtpcyZu
YnNwO2NvbmZpZGVudGlhbC4mbmJzcDtSZWNpcGllbnRzJm5ic3A7bmFtZWQmbmJzcDthYm92ZSZu
YnNwO2FyZSZuYnNwO29ibGlnYXRlZCZuYnNwO3RvJm5ic3A7bWFpbnRhaW4mbmJzcDtzZWNyZWN5
Jm5ic3A7YW5kJm5ic3A7YXJlJm5ic3A7bm90Jm5ic3A7cGVybWl0dGVkJm5ic3A7dG8mbmJzcDtk
aXNjbG9zZSZuYnNwO3RoZSZuYnNwO2NvbnRlbnRzJm5ic3A7b2YmbmJzcDt0aGlzJm5ic3A7Y29t
bXVuaWNhdGlvbiZuYnNwO3RvJm5ic3A7b3RoZXJzLg0KVGhpcyZuYnNwO2VtYWlsJm5ic3A7YW5k
Jm5ic3A7YW55Jm5ic3A7ZmlsZXMmbmJzcDt0cmFuc21pdHRlZCZuYnNwO3dpdGgmbmJzcDtpdCZu
YnNwO2FyZSZuYnNwO2NvbmZpZGVudGlhbCZuYnNwO2FuZCZuYnNwO2ludGVuZGVkJm5ic3A7c29s
ZWx5Jm5ic3A7Zm9yJm5ic3A7dGhlJm5ic3A7dXNlJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtpbmRp
dmlkdWFsJm5ic3A7b3ImbmJzcDtlbnRpdHkmbmJzcDt0byZuYnNwO3dob20mbmJzcDt0aGV5Jm5i
c3A7YXJlJm5ic3A7YWRkcmVzc2VkLiZuYnNwO0lmJm5ic3A7eW91Jm5ic3A7aGF2ZSZuYnNwO3Jl
Y2VpdmVkJm5ic3A7dGhpcyZuYnNwO2VtYWlsJm5ic3A7aW4mbmJzcDtlcnJvciZuYnNwO3BsZWFz
ZSZuYnNwO25vdGlmeSZuYnNwO3RoZSZuYnNwO29yaWdpbmF0b3ImbmJzcDtvZiZuYnNwO3RoZSZu
YnNwO21lc3NhZ2UuJm5ic3A7QW55Jm5ic3A7dmlld3MmbmJzcDtleHByZXNzZWQmbmJzcDtpbiZu
YnNwO3RoaXMmbmJzcDttZXNzYWdlJm5ic3A7YXJlJm5ic3A7dGhvc2UmbmJzcDtvZiZuYnNwO3Ro
ZSZuYnNwO2luZGl2aWR1YWwmbmJzcDtzZW5kZXIuDQpUaGlzJm5ic3A7bWVzc2FnZSZuYnNwO2hh
cyZuYnNwO2JlZW4mbmJzcDtzY2FubmVkJm5ic3A7Zm9yJm5ic3A7dmlydXNlcyZuYnNwO2FuZCZu
YnNwO1NwYW0mbmJzcDtieSZuYnNwO1pURSZuYnNwO0FudGktU3BhbSZuYnNwO3N5c3RlbS4NCjwv
cHJlPg==
--=_alternative 00282B8748257753_=--


From simon.delord@gmail.com  Thu Jul  1 00:31:00 2010
Return-Path: <simon.delord@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E4483A67D7 for <mpls@core3.amsl.com>; Thu,  1 Jul 2010 00:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 zh3jdyYP+WPo for <mpls@core3.amsl.com>; Thu,  1 Jul 2010 00:30:37 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 268353A67C3 for <mpls@ietf.org>; Thu,  1 Jul 2010 00:30:10 -0700 (PDT)
Received: by gwb10 with SMTP id 10so978545gwb.31 for <mpls@ietf.org>; Thu, 01 Jul 2010 00:30:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=d7oM77tzk5B84M11AOZWEDyZGZTMEK2Hj90m4pqngz4=; b=azgoIb9w8SzXhX5ziV3C/ajeuPd1txBo2Ev3DDJl4v+cbYEhhe5jhXEs12k07vjMk+ CeT5vkU4lc0OEGkxKTNfjSR5qI8ycMbAS3Ai9XTN+es9VOVg0N76IZ9wrG7rsdtnRp5d ls4EG56mV6P9GmdT4fj0/bw+Pi3gvpdPzLDjg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=VwBzZVgMXMfU2QjIFHGkEKaTUJxSMftGOsfoIABgmdM4Ss0RctS30q8f/lBYPtPeuc zNEQTgPOFdMyKu0FPXJorUhv5RGLFIzskz5xYvpd+az+ILGvQ93t3ek09j64AMN/ppM7 atb3nvr0F9cW4OxCBQOxjdiRUSRSBKZu4GG6I=
MIME-Version: 1.0
Received: by 10.90.197.4 with SMTP id u4mr8823119agf.22.1277969415469; Thu, 01  Jul 2010 00:30:15 -0700 (PDT)
Received: by 10.90.94.18 with HTTP; Thu, 1 Jul 2010 00:30:15 -0700 (PDT)
Date: Thu, 1 Jul 2010 09:30:15 +0200
Message-ID: <AANLkTimqaOEotBK6bpuqtFndFDCEfA6-6dmAGfsIcjPE@mail.gmail.com>
From: Simon Delord <simon.delord@gmail.com>
To: mpls@ietf.org
Content-Type: multipart/alternative; boundary=0016361e83c80af9b5048a4e71f4
X-Mailman-Approved-At: Fri, 02 Jul 2010 07:18:01 -0700
Subject: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping - take II
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 07:31:00 -0000

--0016361e83c80af9b5048a4e71f4
Content-Type: text/plain; charset=ISO-8859-1

support.
Simon


> -----Original Message-----
> From: mpls-bounces at ietf.org [mailto:mpls-bounces <mpls-bounces> at
ietf.org] On
> Behalf Of Loa Andersson
> Sent: Wednesday, June 30, 2010 3:16 AM
> To: mpls at ietf.org
> Subject: [mpls] poll on
> draft-chen-mpls-return-path-specified-lsp-ping - take II
>
> Working Group,
>
> this email is to start poll to adopt
> draft-chen-mpls-return-path-specified-lsp-ping
> as an MPLS working group draft.
>
> After recent experience, the chairs would like to remind you
> all what it means to conduct a poll to adopt a draft as a
> working group draft.
>
> - Please recall that the IETF does not "vote." Polls of a working
>    group are to gather information to help the chairs make their
>    decisions. Voting is not part of the normal working methods of
>    an IETF working group.
>
> - The "rough consensus" process used in the working group assumes
>    that people expressing opinions are also participating in the
>    development of standards documents.
>
> - Subscription to the list specifically to express an opinion is
>    noticed by the chairs who has access to information on the new list
>    members. Such behavior is not part of the normal working methods.
>
> - The purpose of a poll for adoption is to help the chairs understand
>    the level of support for a document (i.e. who has read it, who
>    believes it is a good starting point for working group work, who
>    will contribute to the work) and whether there are any significant
>    technical issues. Statements of objection must be backed up by
>    proper technical reasons.
>
> So please respond to this poll indicating whether you support
> the adoption of this draft or stating your technical issues.
>
> This poll ends eob July 13.
>
>
> Loa and George
> mpls wg co-chairs
> --

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

<div>support.</div>
<div>Simon</div>
<div>=A0</div>
<div>=A0</div>
<div>&gt; -----Original Message-----<br>&gt; From: mpls-bounces at <a href=
=3D"http://ietf.org">ietf.org</a> [<a href=3D"mailto:mpls-bounces" rel=3D"n=
ofollow">mailto:mpls-bounces</a> at <a href=3D"http://ietf.org">ietf.org</a=
>] On <br>
&gt; Behalf Of Loa Andersson<br>&gt; Sent: Wednesday, June 30, 2010 3:16 AM=
<br>&gt; To: mpls at <a href=3D"http://ietf.org">ietf.org</a><br>&gt; Subje=
ct: [mpls] poll on <br>&gt; draft-chen-mpls-return-path-specified-lsp-ping =
- take II<br>
&gt; <br>&gt; Working Group,<br>&gt; <br>&gt; this email is to start poll t=
o adopt<br>&gt; draft-chen-mpls-return-path-specified-lsp-ping<br>&gt; as a=
n MPLS working group draft.<br>&gt; <br>&gt; After recent experience, the c=
hairs would like to remind you <br>
&gt; all what it means to conduct a poll to adopt a draft as a <br>&gt; wor=
king group draft.<br>&gt; <br>&gt; - Please recall that the IETF does not &=
quot;vote.&quot; Polls of a working<br>&gt;=A0=A0=A0 group are to gather in=
formation to help the chairs make their<br>
&gt;=A0=A0=A0 decisions. Voting is not part of the normal working methods o=
f<br>&gt;=A0=A0=A0 an IETF working group.<br>&gt; <br>&gt; - The &quot;roug=
h consensus&quot; process used in the working group assumes<br>&gt;=A0=A0=
=A0 that people expressing opinions are also participating in the<br>
&gt;=A0=A0=A0 development of standards documents.<br>&gt; <br>&gt; - Subscr=
iption to the list specifically to express an opinion is<br>&gt;=A0=A0=A0 n=
oticed by the chairs who has access to information on the new list<br>&gt;=
=A0=A0=A0 members. Such behavior is not part of the normal working methods.=
<br>
&gt; <br>&gt; - The purpose of a poll for adoption is to help the chairs un=
derstand<br>&gt;=A0=A0=A0 the level of support for a document (i.e. who has=
 read it, who<br>&gt;=A0=A0=A0 believes it is a good starting point for wor=
king group work, who<br>
&gt;=A0=A0=A0 will contribute to the work) and whether there are any signif=
icant<br>&gt;=A0=A0=A0 technical issues. Statements of objection must be ba=
cked up by<br>&gt;=A0=A0=A0 proper technical reasons.<br>&gt; <br>&gt; So p=
lease respond to this poll indicating whether you support <br>
&gt; the adoption of this draft or stating your technical issues.<br>&gt; <=
br>&gt; This poll ends eob July 13.<br>&gt; <br>&gt; <br>&gt; Loa and Georg=
e<br>&gt; mpls wg co-chairs<br>&gt; -- <br></div>

--0016361e83c80af9b5048a4e71f4--

From root@core3.amsl.com  Fri Jul  2 12:15:06 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 8F8653A690C; Fri,  2 Jul 2010 12:15:03 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100702191505.8F8653A690C@core3.amsl.com>
Date: Fri,  2 Jul 2010 12:15:03 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-ldp-igp-sync-bcast-03.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jul 2010 19:15:07 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.


	Title           : LDP IGP Synchronization for broadcast networks
	Author(s)       : S. Kini, W. Lu
	Filename        : draft-ietf-mpls-ldp-igp-sync-bcast-03.txt
	Pages           : 11
	Date            : 2010-07-02

RFC 5443 describes a mechanism to achieve LDP IGP Synchronization to
prevent black-holing traffic (e.g. VPN) when an interior gateway
protocol (IGP) is operational on a link but Label Distribution
Protocol (LDP) is not. If this mechanism is applied to broadcast
links that have more than one LDP/IGP peer, the metric increase
procedure can only be applied to the link as a whole but not an
individual peer. When a new LDP peer comes up on a broadcast network,
this can result in loss of traffic through other established peers on
that network. This document describes a mechanism to address that
use-case without dropping traffic. The mechanism does not introduce
any protocol message changes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-igp-sync-bcast-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-mpls-ldp-igp-sync-bcast-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-02121426.I-D@ietf.org>


--NextPart--

From lizhong.jin@zte.com.cn  Fri Jul  2 16:45:25 2010
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 980A53A696C; Fri,  2 Jul 2010 16:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.608
X-Spam-Level: 
X-Spam-Status: No, score=-99.608 tagged_above=-999 required=5 tests=[AWL=-0.229, BAYES_20=-0.74, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_DOUBLE_IP_LOOSE=0.76, 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 MS4lWbzAMOfa; Fri,  2 Jul 2010 16:45:23 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id A8E5D3A695F; Fri,  2 Jul 2010 16:45:21 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 552342254107577; Sat, 3 Jul 2010 07:44:37 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 2748.17449783116; Sat, 3 Jul 2010 07:45:28 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o62NjF1U014002; Sat, 3 Jul 2010 07:45:16 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
To: l3vpn@ietf.org, l2vpn@ietf.org, mpls@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF4AB9D6AB.7EB75BED-ON48257754.00807EA6-48257754.00827B49@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Sat, 3 Jul 2010 07:45:10 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2010-07-03 07:45:12, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2010-07-03 07:45:12, Serialize complete at 2010-07-03 07:45:12, S/MIME Sign failed at 2010-07-03 07:45:12: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-03 07:45:13, Serialize complete at 2010-07-03 07:45:13
Content-Type: multipart/alternative; boundary="=_alternative 00827B4948257754_="
X-MAIL: mse2.zte.com.cn o62NjF1U014002
Cc: Shane Amante <Shane.Amante@Level3.com>, ice@cisco.com, thomas.morin@francetelecom.com, tme@multicasttech.com, "DeLord, Simon A" <Simon.A.DeLord@team.telstra.com>, stbryant@cisco.com, Giles Heron <giles.heron@bt.com>
Subject: [mpls] Ask for comments for draft-jin-mpls-mldp-leaf-discovery-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jul 2010 23:45:25 -0000

This is a multipart message in MIME format.
--=_alternative 00827B4948257754_=
Content-Type: text/plain; charset="US-ASCII"

Dear all experts,
An updated version of draft-jin-mpls-mldp-leaf-discovery-01 is available, 
and I sincerely ask for comments from you. This mechanism solves the 
problem where the application use mLDP P2MP LSP setup by other 
applications, e.g, static configuration. Please see the section 2 
"motivation and problem statement" for detail. The main updated content is 
to add leaf discovery mechanism based on MP-BGP and it depends on 
application to choose which mechanism to choose. That's because different 
applications may require different signaling mechanism to do the mldp leaf 
discovery.

Abstract of the draft:
This document describes a mechanism for a root node to discover the leaf 
nodes of an mLDP based P2MP/MP2MP LSP.  Such kind of function can then be 
used for multiplexing/aggregating various applications relying on mLDP as 
the P2MP/MP2MP LSP setup.  Examples of such applications are P2MP PW 
[I-D.draft-martini-pwe3-p2mp-pw], VPLS multicast 
[I-D.draft-ietf-l2vpn-vpls-mcast], L3VPN multicast 
[I-D.draft-ietf-l3vpn-2547bis-mcast].

Best Regards
Lizhong

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 00827B4948257754_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Dear all experts,</font>
<br><font size=2 face="sans-serif">An updated version of draft-jin-mpls-mldp-leaf-discovery-01
is available, and I sincerely ask for comments from you. This mechanism
solves the problem where the application use mLDP P2MP LSP setup by other
applications, e.g, static configuration. Please see the section 2 &quot;motivation
and problem statement&quot; for detail. The main updated content is to
add leaf discovery mechanism based on MP-BGP and it depends on application
to choose which mechanism to choose. That's because different applications
may require different signaling mechanism to do the mldp leaf discovery.</font>
<br>
<br><tt><font size=2>Abstract of the draft:<br>
This document describes a mechanism for a root node to discover the leaf
nodes of an mLDP based P2MP/MP2MP LSP. &nbsp;Such kind of function can
then be used for multiplexing/aggregating various applications relying
on mLDP as the P2MP/MP2MP LSP setup. &nbsp;Examples of such applications
are P2MP PW [I-D.draft-martini-pwe3-p2mp-pw], VPLS multicast [I-D.draft-ietf-l2vpn-vpls-mcast],
L3VPN multicast [I-D.draft-ietf-l3vpn-2547bis-mcast].</font></tt>
<br>
<br><tt><font size=2>Best Regards</font></tt>
<br><tt><font size=2>Lizhong</font></tt><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 00827B4948257754_=--


From ehudd@orckit.com  Fri Jul  2 21:26:12 2010
Return-Path: <ehudd@orckit.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE1AF3A68F3 for <mpls@core3.amsl.com>; Fri,  2 Jul 2010 21:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.649
X-Spam-Level: 
X-Spam-Status: No, score=-0.649 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_50=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 BSQX0Y5vNfRt for <mpls@core3.amsl.com>; Fri,  2 Jul 2010 21:26:10 -0700 (PDT)
Received: from tlvmail1.orckit.com (tlvmail1.orckit.com [213.31.203.2]) by core3.amsl.com (Postfix) with ESMTP id 1C8FD3A683D for <mpls@ietf.org>; Fri,  2 Jul 2010 21:26:09 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 3 Jul 2010 07:26:17 +0300
Message-ID: <44F4E579A764584EA9BDFD07D0CA081305DB5B82@tlvmail1>
In-reply-to: <8548C29168214E52BE48A8B0A30A6142@m55527c>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: "Questions and comments on draft-chen-mpls-return-path-specified-lsp-ping-02".
Thread-Index: AcsR+vABDMNzquLzRFKnU/9va5MwTQFbg6Yg
References: <44F4E579A764584EA9BDFD07D0CA081305CFFE0C@tlvmail1> <8548C29168214E52BE48A8B0A30A6142@m55527c>
From: "Ehud Doron" <ehudd@orckit.com>
To: "Mach Chen" <mach@huawei.com>
Cc: Yossi Fridman <Yossifr@orckit.com>, Rafi Ram <RafiR@orckit.com>, Nir Ben Avraham <nirb@orckit.com>, mpls@ietf.org
Subject: Re: [mpls] "Questions and comments on draft-chen-mpls-return-path-specified-lsp-ping-02".
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Jul 2010 04:26:12 -0000

Hi Mach

Thanks for your comprehensive answers.=20
Please see my comments below.=20

We are highly recommend to add a new field to the RP TLV, it will make
reply path specific LSP actions much
simple and less error prone. It also helps us to report both forward and
reply path results.

In addition, here are typos in: page 4 chapter 2.1 second paragraph ,
page 10 first paragraph (extra dot)=20
=20

Best wishes, =20
Ehud Doron
Orckit - Corrigent=20


-----Original Message-----
From: Mach Chen [mailto:mach@huawei.com]=20
Sent: Tuesday, June 22, 2010 2:04 PM
To: Ehud Doron
Cc: Ehud Doron; Rafi Ram; mpls@ietf.org
Subject: Re: "Questions and comments on
draft-chen-mpls-return-path-specified-lsp-ping-02".

Hi Ehud,

Thanks for your comments!

Please see my reply inline...

--------------------------------------------------
From: "Ehud Doron" <ehudd@orckit.com>
Sent: Tuesday, June 22, 2010 4:21 PM
To: "Mach Chen" <mach@huawei.com>
Cc: "Ehud Doron" <ehudd@orckit.com>; "Rafi Ram" <RafiR@orckit.com>;=20
<mpls@ietf.org>
Subject: "Questions and comments on=20
draft-chen-mpls-return-path-specified-lsp-ping-02".

> Dear Mach
>
>
>
> We have a few questions and comment regarding current version of the
> draft:
>
>
>
> 1. In page 12 chapter 4.2 paragraph 1 :  If the egress LSR doesn't
find
> the desired return path, in which path it should sent an echo reply
with
> Errored TLVs? I assume that via the IP path. It should be specified in
> the text. In this case does the reply mode in the echo reply shall
> remain 5?
>
Here it actually assumes via default return path, it could be either IP
or=20
LSP path. And in this case, although the return path may not be the one=20
specified by the ingress, the echo reply is still a reply of previous
echo=20
request with reply mode 5, so, it's better to keep the reply mode as 5.
Of=20
cause, set to other return modes will work as well.

>>Ehud - I recommend to explicitly specify in the text that: 1. the
return=20
>>code shall be 5 and that 2. The return path can be any suitable LSP or
IP. =20

>
> 2. In page 12 chapter 4.2 paragraph 2 :  The paragraph shall be better
> explained. What in the meaning of "2) indicating whether the return
path
> SHOULD be tested (by carrying the FEC stack TLV of the return path)."
?

Sorry for the confusion, actually the follow up two paragraphs are
trying to=20
explain the two functions, respectively.

In the draft, whether carrying the Any Candidate sub-TLV in the echo
request=20
implicitly indicates whether testing/detecting the return path. That is,
if=20
the Any Candidate sub-TLV present, means not to test the return path and
it=20
just tells the egress to exclude some return paths or select an
alternate=20
return path. If the Any Candidate sub-TLV does not carried in the echo=20
request and only a RP TLV carried, means that the echo reply should
carry=20
the FEC stack information of the return path and to test it.

>>Ehud - OK, please update the text it will be better explained.
>>Please see my comment to 4 below. Using ACTION field in RP TLV for the
forward
>>path, can make it much clearer.
>>

>
>
> 3. In page 12 chapter 4.2 paragraph 3 :  In "select other path to send
> the echo reply" , do you mean that the egress LER shall independently
> find other LSP that ends in the Ingress LER ?

Yes,

In this case, the egress should exclude the paths carried in the RP TLV
and=20
find an alternate return path to send the echo reply (in this case, as
said=20
above, the Any Candidate sub-TLV is carried). For example, if there are
3=20
return paths(1,2,3), when path 1 failed, the operator may not want to=20
specify path 2 or 3 as the return path specifically , it just carries
the=20
previous tried return path (path 1) and the Any Candidate sub-TLV to
tell=20
the egress to select one from path 2 and 3 as an alternate return path.
This=20
is useful when the default return path is suspected, the operator just
needs=20
to tell egress to choose an alternate path to confirm/exclude the
suspicion.

>>Ehud - OK. I think these explanations can make the text much clear, so
they=20
>>need to be added to the text.=20

>
> 4. In page 12 chapter 4.2 paragraph 1 : In cases the Egress LER
receives
> echo reply with Error TLV contains the RP TLV in it, how can the
Ingress
> LER can deduce whether the Egress LER didn't find the return path LSP
or
> just didn't recognized some TLV (maybe the return status)? We strongly
> claim that a dedicated status shall be added to the RP TLV, explicitly
> define the exact operation took by the Egress LER. Otherwise un
covered
> issues and misinterpretations might arise and cause problem. In
> addition, taking action according to existence or inexistence of
> sub-TLV, make the implementation cumbersome and bug sensitive.

In the current draft, if the egress could not find a matched LSP, the
egress=20
reply with Error TLV to indicate this. If the egress does not recognize
the=20
TLV, the existing LSP Ping return code 2( One or more of the TLVs was
not=20
understood) can cover this.

>>Ehud - I think that this indication is wrong, adding the Error TLV
when all TLVs=20
>>are OK  is problematic. I can describe some cases when it might be
troublesome:
>>1. Let's assume that all the forward path verifications passed
successfully.=20
>>In the case the RP cannot be reached, the return code indicates a
problem, in spite of=20
>>the fact that the forward path results are OK. What should be reported
to the operator=20
>> about forward path results?
>>2. Or another case there is a failure in the return path (for example
"No label entry"),=20
>>And again the RP cannot be reached. The return code MUST be 11 (for
forward path indication)=20
>>rather than 2.=20
>>I am sure one can think on other scenarios with difficulties.=20

Since the current return code defined in the echo request/reply message
is=20
for reporting the result of the forward direction detection, it could
not be=20
re-used to reflect the egress operation anymore, unless defines a new
code=20
somewhere, do you have any suggestion.

>>Ehud - I am strongly suggest to add a new field to the RP TLV named
"ACTION".=20
>>It the echo request, the LSP head end can use the ACTION field to
explicitly=20
>>define its desires (specific LSP, tunnel, any return path etc.).
>>More important, in the echo reply, the LSP tail end can use the ACTION
field to=20
>>report its behaviors. For example, it the RP cannot be reached, we can
use an=20
>>action code equal to "RP CAN NOT BE FOUND", and add the sub-TLV of
that RP in the RP TLV
>>and not in the Errored TLV.
>>Using a separate status for forward path and reply path is very useful
and allows a separate=20
>>reports (to the operator) about tests results for both forward and
reply path. Verify both
>>paths is one of this draft targets.   =20


>
> 5. In page 13 chapter 4.3 paragraph 1 : Typo in the end of the
> paragraph.

OK, will fix it.

>
> 6. In page 13 chapter 4.3 paragraph 3 : This chapter shall be better
> explained. What is the exact scenario handled in the chapter?

The scenario is that the operator just want to specify the return path
in=20
order to help doing fault localization, for example try to specify an=20
alternate return path to exclude/comfirm the suspision of the default
return=20
path.

>
> 7. In page 13 chapter 4.3 paragraph 4 : We strongly claim that the RP
> TLV is required with a dedicated status, describe the exact operations
> took by the egress LER.

Same as comments 4 above.

>>Ehud - Same as comment 4 above.

>
> 8. If there are some faults in the ping for the forward path, does the
> egress LER shall use the specified return path? I assume it should. It
> should be specified in the test.

Yes, it could if the echo requect can reach to the egress. The current
draft=20
does not exclude this.

>>Ehud- OK, it should be added to the text.=20

>
> 9. A considerations for Echo Request with RP TLV received by LSR are
> required to be added.

OK.

Best regards,
Mach

>
> I will forward you more comments after we will agreed on those stated
> above.
>
>
>
> Best wishes,
>
>
>
> Ehud Doron
>
> Orckit- Corrigent
>
>
>
>=20

From root@core3.amsl.com  Sun Jul  4 00:45:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id BC9AA3A686B; Sun,  4 Jul 2010 00:45:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100704074502.BC9AA3A686B@core3.amsl.com>
Date: Sun,  4 Jul 2010 00:45:02 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-tp-oam-analysis-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Jul 2010 07: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 Multiprotocol Label Switching Working Group of the IETF.


	Title           : MPLS-TP OAM Analysis
	Author(s)       : N. Sprecher, et al.
	Filename        : draft-ietf-mpls-tp-oam-analysis-02.txt
	Pages           : 13
	Date            : 2010-07-04

This document analyzes the set of requirements for Operations,
Administration, and Maintenance (OAM) for the Transport Profile of
MPLS(MPLS-TP) as defined in [MPLS-TP OAM Reqs], to evaluate whether
existing OAM tools (either from the current MPLS toolset or from the
ITU-T documents) can be applied to these requirements.  Eventually,
the purpose of the document is to map the set of functions to a set
of tools based on the existing OAM toolset.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-oam-analysis-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-mpls-tp-oam-analysis-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-04003918.I-D@ietf.org>


--NextPart--

From mach@huawei.com  Sun Jul  4 18:16:57 2010
Return-Path: <mach@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 210553A6827 for <mpls@core3.amsl.com>; Sun,  4 Jul 2010 18:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.106
X-Spam-Level: **
X-Spam-Status: No, score=2.106 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, STOX_REPLY_TYPE=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 fOsGuH8qT3ih for <mpls@core3.amsl.com>; Sun,  4 Jul 2010 18:16:55 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 9350F3A6817 for <mpls@ietf.org>; Sun,  4 Jul 2010 18:16:55 -0700 (PDT)
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 <0L52001998VXW2@szxga04-in.huawei.com> for mpls@ietf.org; Mon, 05 Jul 2010 09:16:45 +0800 (CST)
Received: from m55527c ([10.110.98.169]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L52006SW8VXGA@szxga04-in.huawei.com> for mpls@ietf.org; Mon, 05 Jul 2010 09:16:45 +0800 (CST)
Date: Mon, 05 Jul 2010 09:16:45 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <44F4E579A764584EA9BDFD07D0CA081305DB5B82@tlvmail1>
To: Ehud Doron <ehudd@orckit.com>
Message-id: <4D11BAC1310B4A0D860A00681CF69AE5@m55527c>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206
X-Mailer: Microsoft Windows Live Mail 14.0.8064.206
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
References: <44F4E579A764584EA9BDFD07D0CA081305CFFE0C@tlvmail1> <8548C29168214E52BE48A8B0A30A6142@m55527c> <44F4E579A764584EA9BDFD07D0CA081305DB5B82@tlvmail1>
Cc: Yossi Fridman <Yossifr@orckit.com>, Rafi Ram <RafiR@orckit.com>, Nir Ben Avraham <nirb@orckit.com>, mpls@ietf.org
Subject: Re: [mpls] "Questions and comments on draft-chen-mpls-return-path-specified-lsp-ping-02".
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jul 2010 01:16:57 -0000

Hi Ehud,

Thanks for your valuable comments and suggestions! We will think it over and 
try to make the draft clearer in the next reversion, especially for the new 
flag field to RP TLV.

Many thanks,
Mach

--------------------------------------------------
From: "Ehud Doron" <ehudd@orckit.com>
Sent: Saturday, July 03, 2010 12:26 PM
To: "Mach Chen" <mach@huawei.com>
Cc: "Rafi Ram" <RafiR@orckit.com>; <mpls@ietf.org>; "Nir Ben Avraham" 
<nirb@orckit.com>; "Yossi Fridman" <Yossifr@orckit.com>
Subject: RE: "Questions and comments on 
draft-chen-mpls-return-path-specified-lsp-ping-02".

> Hi Mach
>
> Thanks for your comprehensive answers.
> Please see my comments below.
>
> We are highly recommend to add a new field to the RP TLV, it will make
> reply path specific LSP actions much
> simple and less error prone. It also helps us to report both forward and
> reply path results.
>
> In addition, here are typos in: page 4 chapter 2.1 second paragraph ,
> page 10 first paragraph (extra dot)
>
>
> Best wishes,
> Ehud Doron
> Orckit - Corrigent
>
>
> -----Original Message-----
> From: Mach Chen [mailto:mach@huawei.com]
> Sent: Tuesday, June 22, 2010 2:04 PM
> To: Ehud Doron
> Cc: Ehud Doron; Rafi Ram; mpls@ietf.org
> Subject: Re: "Questions and comments on
> draft-chen-mpls-return-path-specified-lsp-ping-02".
>
> Hi Ehud,
>
> Thanks for your comments!
>
> Please see my reply inline...
>
> --------------------------------------------------
> From: "Ehud Doron" <ehudd@orckit.com>
> Sent: Tuesday, June 22, 2010 4:21 PM
> To: "Mach Chen" <mach@huawei.com>
> Cc: "Ehud Doron" <ehudd@orckit.com>; "Rafi Ram" <RafiR@orckit.com>;
> <mpls@ietf.org>
> Subject: "Questions and comments on
> draft-chen-mpls-return-path-specified-lsp-ping-02".
>
>> Dear Mach
>>
>>
>>
>> We have a few questions and comment regarding current version of the
>> draft:
>>
>>
>>
>> 1. In page 12 chapter 4.2 paragraph 1 :  If the egress LSR doesn't
> find
>> the desired return path, in which path it should sent an echo reply
> with
>> Errored TLVs? I assume that via the IP path. It should be specified in
>> the text. In this case does the reply mode in the echo reply shall
>> remain 5?
>>
> Here it actually assumes via default return path, it could be either IP
> or
> LSP path. And in this case, although the return path may not be the one
> specified by the ingress, the echo reply is still a reply of previous
> echo
> request with reply mode 5, so, it's better to keep the reply mode as 5.
> Of
> cause, set to other return modes will work as well.
>
>>>Ehud - I recommend to explicitly specify in the text that: 1. the
> return
>>>code shall be 5 and that 2. The return path can be any suitable LSP or
> IP.

OK.

>
>>
>> 2. In page 12 chapter 4.2 paragraph 2 :  The paragraph shall be better
>> explained. What in the meaning of "2) indicating whether the return
> path
>> SHOULD be tested (by carrying the FEC stack TLV of the return path)."
> ?
>
> Sorry for the confusion, actually the follow up two paragraphs are
> trying to
> explain the two functions, respectively.
>
> In the draft, whether carrying the Any Candidate sub-TLV in the echo
> request
> implicitly indicates whether testing/detecting the return path. That is,
> if
> the Any Candidate sub-TLV present, means not to test the return path and
> it
> just tells the egress to exclude some return paths or select an
> alternate
> return path. If the Any Candidate sub-TLV does not carried in the echo
> request and only a RP TLV carried, means that the echo reply should
> carry
> the FEC stack information of the return path and to test it.
>
>>>Ehud - OK, please update the text it will be better explained.
>>>Please see my comment to 4 below. Using ACTION field in RP TLV for the
> forward
>>>path, can make it much clearer.
>>>
>
>>
>>
>> 3. In page 12 chapter 4.2 paragraph 3 :  In "select other path to send
>> the echo reply" , do you mean that the egress LER shall independently
>> find other LSP that ends in the Ingress LER ?
>
> Yes,
>
> In this case, the egress should exclude the paths carried in the RP TLV
> and
> find an alternate return path to send the echo reply (in this case, as
> said
> above, the Any Candidate sub-TLV is carried). For example, if there are
> 3
> return paths(1,2,3), when path 1 failed, the operator may not want to
> specify path 2 or 3 as the return path specifically , it just carries
> the
> previous tried return path (path 1) and the Any Candidate sub-TLV to
> tell
> the egress to select one from path 2 and 3 as an alternate return path.
> This
> is useful when the default return path is suspected, the operator just
> needs
> to tell egress to choose an alternate path to confirm/exclude the
> suspicion.
>
>>>Ehud - OK. I think these explanations can make the text much clear, so
> they
>>>need to be added to the text.
>
>>
>> 4. In page 12 chapter 4.2 paragraph 1 : In cases the Egress LER
> receives
>> echo reply with Error TLV contains the RP TLV in it, how can the
> Ingress
>> LER can deduce whether the Egress LER didn't find the return path LSP
> or
>> just didn't recognized some TLV (maybe the return status)? We strongly
>> claim that a dedicated status shall be added to the RP TLV, explicitly
>> define the exact operation took by the Egress LER. Otherwise un
> covered
>> issues and misinterpretations might arise and cause problem. In
>> addition, taking action according to existence or inexistence of
>> sub-TLV, make the implementation cumbersome and bug sensitive.
>
> In the current draft, if the egress could not find a matched LSP, the
> egress
> reply with Error TLV to indicate this. If the egress does not recognize
> the
> TLV, the existing LSP Ping return code 2( One or more of the TLVs was
> not
> understood) can cover this.
>
>>>Ehud - I think that this indication is wrong, adding the Error TLV
> when all TLVs
>>>are OK  is problematic. I can describe some cases when it might be
> troublesome:
>>>1. Let's assume that all the forward path verifications passed
> successfully.
>>>In the case the RP cannot be reached, the return code indicates a
> problem, in spite of
>>>the fact that the forward path results are OK. What should be reported
> to the operator
>>> about forward path results?
>>>2. Or another case there is a failure in the return path (for example
> "No label entry"),
>>>And again the RP cannot be reached. The return code MUST be 11 (for
> forward path indication)
>>>rather than 2.
>>>I am sure one can think on other scenarios with difficulties.
>
> Since the current return code defined in the echo request/reply message
> is
> for reporting the result of the forward direction detection, it could
> not be
> re-used to reflect the egress operation anymore, unless defines a new
> code
> somewhere, do you have any suggestion.
>
>>>Ehud - I am strongly suggest to add a new field to the RP TLV named
> "ACTION".
>>>It the echo request, the LSP head end can use the ACTION field to
> explicitly
>>>define its desires (specific LSP, tunnel, any return path etc.).
>>>More important, in the echo reply, the LSP tail end can use the ACTION
> field to
>>>report its behaviors. For example, it the RP cannot be reached, we can
> use an
>>>action code equal to "RP CAN NOT BE FOUND", and add the sub-TLV of
> that RP in the RP TLV
>>>and not in the Errored TLV.
>>>Using a separate status for forward path and reply path is very useful
> and allows a separate
>>>reports (to the operator) about tests results for both forward and
> reply path. Verify both
>>>paths is one of this draft targets.
>
>
>>
>> 5. In page 13 chapter 4.3 paragraph 1 : Typo in the end of the
>> paragraph.
>
> OK, will fix it.
>
>>
>> 6. In page 13 chapter 4.3 paragraph 3 : This chapter shall be better
>> explained. What is the exact scenario handled in the chapter?
>
> The scenario is that the operator just want to specify the return path
> in
> order to help doing fault localization, for example try to specify an
> alternate return path to exclude/comfirm the suspision of the default
> return
> path.
>
>>
>> 7. In page 13 chapter 4.3 paragraph 4 : We strongly claim that the RP
>> TLV is required with a dedicated status, describe the exact operations
>> took by the egress LER.
>
> Same as comments 4 above.
>
>>>Ehud - Same as comment 4 above.
>
>>
>> 8. If there are some faults in the ping for the forward path, does the
>> egress LER shall use the specified return path? I assume it should. It
>> should be specified in the test.
>
> Yes, it could if the echo requect can reach to the egress. The current
> draft
> does not exclude this.
>
>>>Ehud- OK, it should be added to the text.
>
>>
>> 9. A considerations for Echo Request with RP TLV received by LSR are
>> required to be added.
>
> OK.
>
> Best regards,
> Mach
>
>>
>> I will forward you more comments after we will agreed on those stated
>> above.
>>
>>
>>
>> Best wishes,
>>
>>
>>
>> Ehud Doron
>>
>> Orckit- Corrigent
>>
>>
>>
>> 

From ehudd@orckit.com  Mon Jul  5 00:07:05 2010
Return-Path: <ehudd@orckit.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60F5B3A6912 for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 00:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvZEevPfnn4R for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 00:07:04 -0700 (PDT)
Received: from tlvmail1.orckit.com (tlvmail1.orckit.com [213.31.203.2]) by core3.amsl.com (Postfix) with ESMTP id 312D23A687A for <mpls@ietf.org>; Mon,  5 Jul 2010 00:07:03 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 5 Jul 2010 10:07:02 +0300
Message-ID: <44F4E579A764584EA9BDFD07D0CA081305DB5F24@tlvmail1>
In-reply-to: <4C2A4678.9020806@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping -take II
Thread-Index: AcsXv7pN4D8V0wUOQj+BiDHVoFAUsAEULbWQ
References: <4C2A4678.9020806@pi.nu>
From: "Ehud Doron" <ehudd@orckit.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls@ietf.org>
Subject: Re: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping -take II
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jul 2010 07:07:05 -0000

Support=20

Ehud Doron
System Architect=20
Orckit - Corrigent

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Loa Andersson
Sent: Tuesday, June 29, 2010 10:16 PM
To: mpls@ietf.org
Subject: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping
-take II

Working Group,

this email is to start poll to adopt
draft-chen-mpls-return-path-specified-lsp-ping
as an MPLS working group draft.

After recent experience, the chairs would like to remind you all
what it means to conduct a poll to adopt a draft as a working group
draft.

- Please recall that the IETF does not "vote." Polls of a working
   group are to gather information to help the chairs make their
   decisions. Voting is not part of the normal working methods of
   an IETF working group.

- The "rough consensus" process used in the working group assumes
   that people expressing opinions are also participating in the
   development of standards documents.

- Subscription to the list specifically to express an opinion is
   noticed by the chairs who has access to information on the new list
   members. Such behavior is not part of the normal working methods.

- The purpose of a poll for adoption is to help the chairs understand
   the level of support for a document (i.e. who has read it, who
   believes it is a good starting point for working group work, who
   will contribute to the work) and whether there are any significant
   technical issues. Statements of objection must be backed up by
   proper technical reasons.

So please respond to this poll indicating whether you support the=20
adoption of this draft or stating your technical issues.

This poll ends eob July 13.


Loa and George
mpls wg co-chairs
--=20


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From hhelvoort@chello.nl  Mon Jul  5 01:45:18 2010
Return-Path: <hhelvoort@chello.nl>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36D3F3A6881 for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 01:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 vmEhqOCav+RM for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 01:45:17 -0700 (PDT)
Received: from fep13.mx.upcmail.net (fep13.mx.upcmail.net [62.179.121.33]) by core3.amsl.com (Postfix) with ESMTP id 9DF6F3A683E for <mpls@ietf.org>; Mon,  5 Jul 2010 01:45:16 -0700 (PDT)
Received: from edge01.upcmail.net ([192.168.13.236]) by viefep13-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100705084515.SNCI23743.viefep13-int.chello.at@edge01.upcmail.net> for <mpls@ietf.org>; Mon, 5 Jul 2010 10:45:15 +0200
Received: from McAsterix.local ([77.250.51.60]) by edge01.upcmail.net with edge id e8lE1e00x1Hw6VZ018lFNs; Mon, 05 Jul 2010 10:45:15 +0200
X-SourceIP: 77.250.51.60
Message-ID: <4C319B9A.1020709@chello.nl>
Date: Mon, 05 Jul 2010 10:45:14 +0200
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Cloudmark-Analysis: v=1.1 cv=LDjS4OUiOlTC72n1a9cQM4olW91MdL4bu39eiUxSmiw= c=1 sm=0 a=4nSpd5z9GxQA:10 a=uEzv4HemXiYA:10 a=8nJEP1OIZ-IA:10 a=48vgC7mUAAAA:8 a=yRXzihTDNOoa717JtPQA:9 a=3zBGU3400acq9ZDkKzpme2ydeS4A:4 a=wPNLvfGTeEIA:10 a=kkUMZHjH4KkA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Subject: Re: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping -	take II
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jul 2010 08:45:18 -0000

yes/support

Cheers, Huub.

  > -----Original Message-----
  > From: mpls-bounces at ietf.org <http://ietf.org> [mailto:mpls-bounces
at ietf.org <http://ietf.org>] On
  > Behalf Of Loa Andersson
  > Sent: Wednesday, June 30, 2010 3:16 AM
  > To: mpls at ietf.org <http://ietf.org>
  > Subject: [mpls] poll on
  > draft-chen-mpls-return-path-specified-lsp-ping - take II
  >
  > Working Group,
  >
  > this email is to start poll to adopt
  > draft-chen-mpls-return-path-specified-lsp-ping
  > as an MPLS working group draft.
  >
  > After recent experience, the chairs would like to remind you
  > all what it means to conduct a poll to adopt a draft as a
  > working group draft.
  >
  > - Please recall that the IETF does not "vote." Polls of a working
  >    group are to gather information to help the chairs make their
  >    decisions. Voting is not part of the normal working methods of
  >    an IETF working group.
  >
  > - The "rough consensus" process used in the working group assumes
  >    that people expressing opinions are also participating in the
  >    development of standards documents.
  >
  > - Subscription to the list specifically to express an opinion is
  >    noticed by the chairs who has access to information on the new list
  >    members. Such behavior is not part of the normal working methods.
  >
  > - The purpose of a poll for adoption is to help the chairs understand
  >    the level of support for a document (i.e. who has read it, who
  >    believes it is a good starting point for working group work, who
  >    will contribute to the work) and whether there are any significant
  >    technical issues. Statements of objection must be backed up by
  >    proper technical reasons.
  >
  > So please respond to this poll indicating whether you support
  > the adoption of this draft or stating your technical issues.
  >
  > This poll ends eob July 13.
  >
  >
  > Loa and George
  > mpls wg co-chairs
  > --

From italo.busi@alcatel-lucent.com  Mon Jul  5 03:25:47 2010
Return-Path: <italo.busi@alcatel-lucent.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 847B73A68B3; Mon,  5 Jul 2010 03:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.249
X-Spam-Level: 
X-Spam-Status: No, score=-4.249 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 tWhNlV85vBSL; Mon,  5 Jul 2010 03:25:46 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id 5AFDB3A63EC; Mon,  5 Jul 2010 03:25:45 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o65APQgq026288 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 5 Jul 2010 12:25:43 +0200
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.40]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Mon, 5 Jul 2010 12:25:43 +0200
From: "BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com>
To: Loa Andersson <loa@pi.nu>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>
Date: Mon, 5 Jul 2010 12:25:42 +0200
Thread-Topic: [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
Thread-Index: AcsROjrrF49QvhDORjuDFaI2E7/UkQK8vpMA
Message-ID: <15740615FC9674499FBCE797B011623F0B730111@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <4C1F5616.2060406@pi.nu>
In-Reply-To: <4C1F5616.2060406@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Subject: Re: [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jul 2010 10:25:47 -0000

The current draft does not clearly articulate how the solution mechanism is=
 satisfying the requirements and behaviors associated with on-demand CV (e.=
g., support of per-interface MIP model).  It is important that this be docu=
mented.

Italo=20

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On=20
> Behalf Of Loa Andersson
> Sent: luned=EC 21 giugno 2010 14.08
> To: mpls-tp@ietf.org; mpls@ietf.org; MPLS-TP ad hoc team
> Subject: [mpls] poll to adopt=20
> draft-nitinb-mpls-tp-on-demand-cv as a working group document
>=20
>=20
> Working Group,
>=20
> this email is to start poll to adopt
> draft-nitinb-mpls-tp-on-demand-cv-00.txt
> as an MPLS working group draft.
>=20
> After recent experience, the chairs would like to remind you=20
> all what it means to conduct a poll to adopt a draft as a=20
> working group draft.
>=20
> - Please recall that the IETF does not "vote." Polls of a working
>    group are to gather information to help the chairs make their
>    decisions. Voting is not part of the normal working methods of
>    an IETF working group.
>=20
> - The "rough consensus" process used in the working group assumes
>    that people expressing opinions are also participating in the
>    development of standards documents.
>=20
> - Subscription to the list specifically to express an opinion is
>    noticed by the chairs who has access to information on the new list
>    members. Such behavior is not part of the normal working methods.
>=20
> - The purpose of a poll for adoption is to help the chairs understand
>    the level of support for a document (i.e. who has read it, who
>    believes it is a good starting point for working group work, who
>    will contribute to the work) and whether there are any significant
>    technical issues. Statements of objection must be backed up by
>    proper technical reasons.
>=20
> So please respond to this poll indicating whether you support=20
> the adoption of this draft or stating your technical issues.
>=20
> Please also not that this draft has after a discussion with=20
> the working group chairs been renamed, it was earlier know as=20
> draft-nitinb-mpls-tp-lsp-ping-extensions-01.
>=20
> This poll ends eob July 5.
>=20
>=20
> Loa and George
> mpls wg co-chairs
>=20
> --=20
>=20
>=20
> Loa Andersson                         email:=20
> loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                               +46 767 72 92=20
> 13 _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> =

From hhelvoort@chello.nl  Mon Jul  5 04:55:40 2010
Return-Path: <hhelvoort@chello.nl>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8704D3A6908; Mon,  5 Jul 2010 04:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
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 kCbjykEREj16; Mon,  5 Jul 2010 04:55:39 -0700 (PDT)
Received: from fep12.mx.upcmail.net (fep12.mx.upcmail.net [62.179.121.32]) by core3.amsl.com (Postfix) with ESMTP id CD7EB3A63EC; Mon,  5 Jul 2010 04:55:38 -0700 (PDT)
Received: from edge02.upcmail.net ([192.168.13.237]) by viefep12-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100705115537.SXO20209.viefep12-int.chello.at@edge02.upcmail.net>;  Mon, 5 Jul 2010 13:55:37 +0200
Received: from McAsterix.local ([77.250.51.60]) by edge02.upcmail.net with edge id eBvb1e03a1Hw6VZ02Bvcng; Mon, 05 Jul 2010 13:55:37 +0200
X-SourceIP: 77.250.51.60
Message-ID: <4C31C837.7020601@chello.nl>
Date: Mon, 05 Jul 2010 13:55:35 +0200
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
References: <4C1F5616.2060406@pi.nu>
In-Reply-To: <4C1F5616.2060406@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Cloudmark-Analysis: v=1.1 cv=K3uBg944YaUT+Qsu6bWO0a0V3uPy4DQNslbdoMCD4tw= c=1 sm=0 a=AV6CXIDOiCQA:10 a=yQWWgrYGNuUA:10 a=8nJEP1OIZ-IA:10 a=OLZQc8AWAAAA:8 a=JE_rWdhESM8hsm6hcWgA:9 a=tZBYp2jxjF3YeOgadCkA:7 a=IUQgeAsT81bc1q5f5XMvD5mMYfoA:4 a=wPNLvfGTeEIA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: mpls@ietf.org, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jul 2010 11:55:40 -0000

No/do not support

The change of the name of this draft gives the impression
that the content of the draft changed as well.
So before it can be adopted the text has to be aligned
with the title: On-demand CV for MPLS-TP.

I see that it is still focused on extending LSP-Ping but
not for use in a transport environment.
It does not indicate where the transport OAM requirements
are met.
It does not indicate how the ACh is used.
What is the meaning of "adjacency" in the context of MPLS-TP?
It does not document how this tool can be used in transport
environment where tools are enabled/disabled static (compared
to the dynamic set-up of LSP-ping.

Regards, Huub.

==============
On 21-06-10 14:07, Loa Andersson wrote:
>
> Working Group,
>
> this email is to start poll to adopt
> draft-nitinb-mpls-tp-on-demand-cv-00.txt
> as an MPLS working group draft.
>
> After recent experience, the chairs would like to remind you all
> what it means to conduct a poll to adopt a draft as a working group
> draft.
>
> - Please recall that the IETF does not "vote." Polls of a working
> group are to gather information to help the chairs make their
> decisions. Voting is not part of the normal working methods of
> an IETF working group.
>
> - The "rough consensus" process used in the working group assumes
> that people expressing opinions are also participating in the
> development of standards documents.
>
> - Subscription to the list specifically to express an opinion is
> noticed by the chairs who has access to information on the new list
> members. Such behavior is not part of the normal working methods.
>
> - The purpose of a poll for adoption is to help the chairs understand
> the level of support for a document (i.e. who has read it, who
> believes it is a good starting point for working group work, who
> will contribute to the work) and whether there are any significant
> technical issues. Statements of objection must be backed up by
> proper technical reasons.
>
> So please respond to this poll indicating whether you support the
> adoption of this draft or stating your technical issues.
>
> Please also not that this draft has after a discussion with the
> working group chairs been renamed, it was earlier know as
> draft-nitinb-mpls-tp-lsp-ping-extensions-01.
>
> This poll ends eob July 5.
>
>
> Loa and George
> mpls wg co-chairs
>

-- 
================================================================
                   http://www.van-helvoort.eu/
================================================================
Always remember that you are unique...just like everyone else...

From swallow@cisco.com  Mon Jul  5 15:15:44 2010
Return-Path: <swallow@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAF4D3A6A10 for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 15:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id moXZwL1V9aGr for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 15:15:44 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id EF5D13A6A51 for <mpls@ietf.org>; Mon,  5 Jul 2010 15:15:43 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai4GALv2MUytJV2Z/2dsb2JhbACTP4w3caUomjKFJQSIOoIs
X-IronPort-AV: E=Sophos;i="4.53,542,1272844800"; d="scan'208";a="129015001"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rtp-iport-2.cisco.com with ESMTP; 05 Jul 2010 22:15:44 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o65MFi71008081;  Mon, 5 Jul 2010 22:15:44 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 5 Jul 2010 17:15:44 -0500
Received: from 10.86.253.186 ([10.86.253.186]) by XMB-RCD-106.cisco.com ([72.163.62.148]) with Microsoft Exchange Server HTTP-DAV ;  Mon,  5 Jul 2010 22:15:44 +0000
User-Agent: Microsoft-Entourage/12.25.0.100505
Date: Mon, 05 Jul 2010 18:15:43 -0400
From: George Swallow <swallow@cisco.com>
To: <mpls@ietf.org>
Message-ID: <C857D1CF.219DA%swallow@cisco.com>
Thread-Topic: Last call on draft-ietf-mpls-rsvp-te-no-php-oob-mapping-04
Thread-Index: Acscj5vN8TaSRH03Fkuv6KsOo39lEg==
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 05 Jul 2010 22:15:44.0972 (UTC) FILETIME=[9CF9F8C0:01CB1C8F]
Cc: "Zafar Ali \(zali\)" <zali@cisco.com>
Subject: [mpls] Last call on draft-ietf-mpls-rsvp-te-no-php-oob-mapping-04
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jul 2010 22:15:45 -0000

This begins a two week last call on
draft-ietf-mpls-rsvp-te-no-php-oob-mapping-04, "Non PHP Behavior and
out-of-band mapping for RSVP-TE LSPs".

https://datatracker.ietf.org/doc/draft-ietf-mpls-rsvp-te-no-php-oob-mapping

The last call ends on July 19, 2010 at 24:00 UTC.

George and Loa


From daniel@olddog.co.uk  Mon Jul  5 19:20:22 2010
Return-Path: <daniel@olddog.co.uk>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDA9E3A697D for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 19:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
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 m8NXMlGeQpn1 for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 19:20:22 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by core3.amsl.com (Postfix) with ESMTP id A557E3A67B4 for <mpls@ietf.org>; Mon,  5 Jul 2010 19:20:21 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id o662KLEF009932 for <mpls@ietf.org>; Tue, 6 Jul 2010 03:20:21 +0100
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id o662KKQR009928 for <mpls@ietf.org>; Tue, 6 Jul 2010 03:20:20 +0100
From: "Daniel King" <daniel@olddog.co.uk>
To: <mpls@ietf.org>
References: 
In-Reply-To: 
Date: Tue, 6 Jul 2010 03:20:21 +0100
Message-ID: <001201cb1cb1$c95a0460$5c0e0d20$@co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsckTnApYLx6t11QCS544RROt0s1wAIAbBw
Content-Language: en-gb
x-cr-hashedpuzzle: AVwq AV5G AgOS AtGU B1Ny C2/4 D19o Eof8 Fq27 FzMQ Hs7o Hxyq Ib9M Ilva Itw0 Ja9b; 1; bQBwAGwAcwBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {6DD3199A-1E06-4C3E-AF0B-22975601DA22}; ZABhAG4AaQBlAGwAQABvAGwAZABkAG8AZwAuAGMAbwAuAHUAawA=; Tue, 06 Jul 2010 02:20:19 GMT; TQBQAEwAUwAtAFQAUAAgAE0ASQBCAC0AYgBhAHMAZQBkACAATQBhAG4AYQBnAGUAbQBlAG4AdAAgAE8AdgBlAHIAdgBpAGUAdwA=
x-cr-puzzleid: {6DD3199A-1E06-4C3E-AF0B-22975601DA22}
Subject: [mpls] MPLS-TP MIB-based Management Overview
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jul 2010 02:20:22 -0000

Hello All, 

Please find a new draft for your reading pleasure: 

http://tools.ietf.org/html/draft-farrel-mpls-tp-mib-management-overview-00

The document draft-farrel-mpls-tp-mib-management-overview-00 describes the
MIB-based management architecture for MPLS-TP and indicates the
interrelationships between the different MIB modules used for MPLS-TP
network management. The document also indentifies areas where additional MIB
modules would be required to support an MPLS-TP network.

The document uses a similar format to the MPLS Management Overview [RFC4221]
and we appreciate the effort the authors made when creating RFC4221. 

As ever, WG feedback and contributions are warmly welcome. 

Br, Dan. 


From loa@pi.nu  Tue Jul  6 08:44:25 2010
Return-Path: <loa@pi.nu>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C45C13A65A6; Tue,  6 Jul 2010 08:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Level: 
X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619]
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 PyABNfD3jp0Y; Tue,  6 Jul 2010 08:44:24 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 936143A6980; Tue,  6 Jul 2010 08:44:24 -0700 (PDT)
Received: from [10.154.12.226] (unknown [192.165.126.74]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 77176D404F; Tue,  6 Jul 2010 17:44:25 +0200 (CEST)
Message-ID: <4C334F76.2060305@pi.nu>
Date: Tue, 06 Jul 2010 17:44:54 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1
MIME-Version: 1.0
To: mpls@ietf.org
References: <4C1F5616.2060406@pi.nu>
In-Reply-To: <4C1F5616.2060406@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jul 2010 15:44:25 -0000

Working Group,

this poll has ended.

We have a new working group draft, could the authors
please republish as:

draft-ietf-mpls-tp-on-demand-cv-00.txt

this version of the document should be identical to the
document we polled with the exception on name and date
changes.

There has also been good comments that the authors should
take care to respond to and address in the -01 version of the
document.

/Loa

On 2010-06-21 14:07, Loa Andersson wrote:
>
> Working Group,
>
> this email is to start poll to adopt
> draft-nitinb-mpls-tp-on-demand-cv-00.txt
> as an MPLS working group draft.
>
> After recent experience, the chairs would like to remind you all
> what it means to conduct a poll to adopt a draft as a working group
> draft.
>
> - Please recall that the IETF does not "vote." Polls of a working
> group are to gather information to help the chairs make their
> decisions. Voting is not part of the normal working methods of
> an IETF working group.
>
> - The "rough consensus" process used in the working group assumes
> that people expressing opinions are also participating in the
> development of standards documents.
>
> - Subscription to the list specifically to express an opinion is
> noticed by the chairs who has access to information on the new list
> members. Such behavior is not part of the normal working methods.
>
> - The purpose of a poll for adoption is to help the chairs understand
> the level of support for a document (i.e. who has read it, who
> believes it is a good starting point for working group work, who
> will contribute to the work) and whether there are any significant
> technical issues. Statements of objection must be backed up by
> proper technical reasons.
>
> So please respond to this poll indicating whether you support the
> adoption of this draft or stating your technical issues.
>
> Please also not that this draft has after a discussion with the
> working group chairs been renamed, it was earlier know as
> draft-nitinb-mpls-tp-lsp-ping-extensions-01.
>
> This poll ends eob July 5.
>
>
> Loa and George
> mpls wg co-chairs
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From jdrake@juniper.net  Tue Jul  6 09:14:06 2010
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0622B3A688A; Tue,  6 Jul 2010 09:14:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tymkUvV15n57; Tue,  6 Jul 2010 09:14:05 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by core3.amsl.com (Postfix) with ESMTP id 921C03A67FB; Tue,  6 Jul 2010 09:14:04 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKTDNWQ/IDAAC5Nf3C5RwrUmerQHqBe2E/@postini.com; Tue, 06 Jul 2010 09:14:07 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Tue, 6 Jul 2010 09:10:36 -0700
From: John E Drake <jdrake@juniper.net>
To: "curtis@occnc.com" <curtis@occnc.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Date: Tue, 6 Jul 2010 09:10:35 -0700
Thread-Topic: [PWE3] Multiple RSVP paths
Thread-Index: AcsdICeLrK/RZfGiTIyQXS2B8tj2VgABXQWw
Message-ID: <5E893DB832F57341992548CDBB3331639843877BA7@EMBX01-HQ.jnpr.net>
References: Your message of "Mon, 05 Jul 2010 15:07:21 BST." <4C31E719.1060402@cisco.com> <201007061530.o66FU4Q6007184@harbor.orleans.occnc.com>
In-Reply-To: <201007061530.o66FU4Q6007184@harbor.orleans.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-pwe3-fat-pw@tools.ietf.org" <draft-ietf-pwe3-fat-pw@tools.ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, pwe3 <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] Multiple RSVP paths
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jul 2010 16:14:06 -0000

Hi,

A related ID:

http://www.ietf.org/id/draft-kompella-mpls-rsvp-ecmp-00.txt

Thanks,

John
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> Curtis Villamizar
> Sent: Tuesday, July 06, 2010 8:30 AM
> To: stbryant@cisco.com
> Cc: draft-ietf-pwe3-fat-pw@tools.ietf.org; pwe3
> Subject: Re: [PWE3] Multiple RSVP paths
>=20
>=20
> In message <4C31E719.1060402@cisco.com>
> Stewart Bryant writes:
> >
> > In response to a comment received during last call I have added a new
> > section 7.3 entitled : "Multiple RSVP-TE Paths" which says:
> >
> > In some networks it is desirable for a Label Edge Router (LER) to be
> > able to load balance a PW across multiple RSVP-TE tunnels. The flow
> > label mechanism described in this document may be used to provide the
> > LER with the required flow information, and necessary entropy to provid=
e
> > this type of load balancing. Methods by which the LER is configured to
> > apply this type of ECMP is outside the scope of this document.
> >
> > - Stewart
>=20
>=20
> Stewart,
>=20
> You could mention using a link bundle with the all ones component
> link as a possibility but still leave further details out of scope and
> not preclude other mechanisms that are local to the LER.
>=20
> Curtis
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

From nurit.sprecher@nsn.com  Tue Jul  6 09:29:21 2010
Return-Path: <nurit.sprecher@nsn.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 392133A688A; Tue,  6 Jul 2010 09:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 7Nv7pIWdGd7y; Tue,  6 Jul 2010 09:29:14 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id E30F93A63EC; Tue,  6 Jul 2010 09:29:13 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o66GTBEC001850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Jul 2010 18:29:11 +0200
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o66GT8LJ002474; Tue, 6 Jul 2010 18:29:11 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 6 Jul 2010 18:29:04 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB1D28.58E63D75"
Date: Tue, 6 Jul 2010 18:29:02 +0200
Message-ID: <077E41CFFD002C4CAB7DFA4386A5326402540581@DEMUEXC014.nsn-intra.net>
In-Reply-To: <4C31C837.7020601@chello.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
Thread-Index: AcscOQ0vhhdSnjmnTj2ArRo+PCSjRgAIiqyg
References: <4C1F5616.2060406@pi.nu> <4C31C837.7020601@chello.nl>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: <hhelvoort@chello.nl>, "Loa Andersson" <loa@pi.nu>
X-OriginalArrivalTime: 06 Jul 2010 16:29:04.0063 (UTC) FILETIME=[5914E4F0:01CB1D28]
Cc: mpls@ietf.org, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, mpls-tp@ietf.org
Subject: Re: [mpls] [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jul 2010 16:29:21 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB1D28.58E63D75
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Huub,

Please see inline.

Best regards,

Nurit

=20

-----Original Message-----

From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
Behalf Of ext Huub van Helvoort

Sent: Monday, July 05, 2010 2:56 PM

To: Loa Andersson

Cc: mpls@ietf.org; MPLS-TP ad hoc team; mpls-tp@ietf.org

Subject: Re: [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv
as a working group document

=20

No/do not support

=20

The change of the name of this draft gives the impression

that the content of the draft changed as well.

So before it can be adopted the text has to be aligned

with the title: On-demand CV for MPLS-TP.

=20

I see that it is still focused on extending LSP-Ping but

not for use in a transport environment.

<Nurit> please be more specific. For me it looks that you just missed
the statement in the document saying "In such scenarios, LSP-Ping SHOULD
be run without IP addressing, using the ACH channel type specified in
(I-D.ietf-mpls-tp-lsp-ping-bfd-procedures]. Maybe you should look at
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-lsp-ping-bfd-procedur
es/ \<Nurit>

It does not indicate where the transport OAM requirements

are met.

<Nurit> the assumption it is unless you prove otherwise \<Nurit>

It does not indicate how the ACh is used.

<Nurit> see above. You probably missed in your review the reference to
ietf-mpls-tp-lsp-ping-bfd-procedures \<Nurit>

What is the meaning of "adjacency" in the context of MPLS-TP?

It does not document how this tool can be used in transport

environment where tools are enabled/disabled static (compared

to the dynamic set-up of LSP-ping.

<Nurit> your comment is not clear \<Nurit>

=20

Regards, Huub.

=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On 21-06-10 14:07, Loa Andersson wrote:

>=20

> Working Group,

>=20

> this email is to start poll to adopt

> draft-nitinb-mpls-tp-on-demand-cv-00.txt

> as an MPLS working group draft.

>=20

> After recent experience, the chairs would like to remind you all

> what it means to conduct a poll to adopt a draft as a working group

> draft.

>=20

> - Please recall that the IETF does not "vote." Polls of a working

> group are to gather information to help the chairs make their

> decisions. Voting is not part of the normal working methods of

> an IETF working group.

>=20

> - The "rough consensus" process used in the working group assumes

> that people expressing opinions are also participating in the

> development of standards documents.

>=20

> - Subscription to the list specifically to express an opinion is

> noticed by the chairs who has access to information on the new list

> members. Such behavior is not part of the normal working methods.

>=20

> - The purpose of a poll for adoption is to help the chairs understand

> the level of support for a document (i.e. who has read it, who

> believes it is a good starting point for working group work, who

> will contribute to the work) and whether there are any significant

> technical issues. Statements of objection must be backed up by

> proper technical reasons.

>=20

> So please respond to this poll indicating whether you support the

> adoption of this draft or stating your technical issues.

>=20

> Please also not that this draft has after a discussion with the

> working group chairs been renamed, it was earlier know as

> draft-nitinb-mpls-tp-lsp-ping-extensions-01.

>=20

> This poll ends eob July 5.

>=20

>=20

> Loa and George

> mpls wg co-chairs

>=20

=20

--=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

                   http://www.van-helvoort.eu/

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Always remember that you are unique...just like everyone else...

_______________________________________________

mpls-tp mailing list

mpls-tp@ietf.org

https://www.ietf.org/mailman/listinfo/mpls-tp


------_=_NextPart_001_01CB1D28.58E63D75
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.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=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoPlainText>Huub,<o:p></o:p></p>

<p class=3DMsoPlainText>Please see inline.<o:p></o:p></p>

<p class=3DMsoPlainText>Best regards,<o:p></o:p></p>

<p class=3DMsoPlainText>Nurit<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>-----Original Message-----<o:p></o:p></p>

<p class=3DMsoPlainText>From: mpls-tp-bounces@ietf.org
[mailto:mpls-tp-bounces@ietf.org] On Behalf Of ext Huub van =
Helvoort<o:p></o:p></p>

<p class=3DMsoPlainText>Sent: Monday, July 05, 2010 2:56 =
PM<o:p></o:p></p>

<p class=3DMsoPlainText>To: Loa Andersson<o:p></o:p></p>

<p class=3DMsoPlainText>Cc: mpls@ietf.org; MPLS-TP ad hoc team; =
mpls-tp@ietf.org<o:p></o:p></p>

<p class=3DMsoPlainText>Subject: Re: [mpls-tp] poll to adopt
draft-nitinb-mpls-tp-on-demand-cv as a working group =
document<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>No/do not support<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>The change of the name of this draft gives the =
impression<o:p></o:p></p>

<p class=3DMsoPlainText>that the content of the draft changed as =
well.<o:p></o:p></p>

<p class=3DMsoPlainText>So before it can be adopted the text has to be =
aligned<o:p></o:p></p>

<p class=3DMsoPlainText>with the title: On-demand CV for =
MPLS-TP.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>I see that it is still focused on extending =
LSP-Ping but<o:p></o:p></p>

<p class=3DMsoPlainText>not for use in a transport =
environment.<o:p></o:p></p>

<pre><span style=3D'color:#4F81BD'>&lt;Nurit&gt; please be more =
specific. For me it looks that you just missed the statement in the =
document saying &#8220;In such scenarios, LSP-Ping SHOULD be run without =
IP addressing, using the ACH channel type specified in =
(I-D.ietf-mpls-tp-lsp-ping-bfd-procedures]. Maybe you should look =
at</span> <a
href=3D"http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-lsp-ping-bfd-p=
rocedures/">http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-lsp-ping-b=
fd-procedures/</a> <span
style=3D'color:#4F81BD'>\&lt;Nurit&gt;</span><o:p></o:p></pre>

<p class=3DMsoPlainText>It does not indicate where the transport OAM =
requirements<o:p></o:p></p>

<p class=3DMsoPlainText>are met.<o:p></o:p></p>

<p class=3DMsoPlainText><span style=3D'color:#4F81BD'>&lt;Nurit&gt; the =
assumption
it is unless you prove otherwise \&lt;Nurit&gt;<o:p></o:p></span></p>

<p class=3DMsoPlainText>It does not indicate how the ACh is =
used.<o:p></o:p></p>

<p class=3DMsoPlainText><span style=3D'color:#4F81BD'>&lt;Nurit&gt; see =
above. You probably
missed in your review the reference to </span><span =
style=3D'font-size:10.0pt;
font-family:"Courier =
New";color:#4F81BD'>ietf-mpls-tp-lsp-ping-bfd-procedures</span><span
style=3D'color:#4F81BD'> \&lt;Nurit&gt;<o:p></o:p></span></p>

<p class=3DMsoPlainText>What is the meaning of &quot;adjacency&quot; in =
the
context of MPLS-TP?<o:p></o:p></p>

<p class=3DMsoPlainText>It does not document how this tool can be used =
in
transport<o:p></o:p></p>

<p class=3DMsoPlainText>environment where tools are enabled/disabled =
static
(compared<o:p></o:p></p>

<p class=3DMsoPlainText>to the dynamic set-up of =
LSP-ping.<o:p></o:p></p>

<p class=3DMsoPlainText><span style=3D'color:#4F81BD'>&lt;Nurit&gt; your =
comment is
not clear \&lt;Nurit&gt;<o:p></o:p></span></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Regards, Huub.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p =
class=3DMsoPlainText>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p=
></p>

<p class=3DMsoPlainText>On 21-06-10 14:07, Loa Andersson =
wrote:<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; Working Group,<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; this email is to start poll to =
adopt<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; =
draft-nitinb-mpls-tp-on-demand-cv-00.txt<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; as an MPLS working group =
draft.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; After recent experience, the chairs would =
like to
remind you all<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; what it means to conduct a poll to adopt a =
draft as
a working group<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; draft.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; - Please recall that the IETF does not
&quot;vote.&quot; Polls of a working<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; group are to gather information to help the =
chairs
make their<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; decisions. Voting is not part of the normal =
working
methods of<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; an IETF working group.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; - The &quot;rough consensus&quot; process =
used in
the working group assumes<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; that people expressing opinions are also
participating in the<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; development of standards =
documents.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; - Subscription to the list specifically to =
express
an opinion is<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; noticed by the chairs who has access to =
information
on the new list<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; members. Such behavior is not part of the =
normal
working methods.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; - The purpose of a poll for adoption is to =
help the
chairs understand<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; the level of support for a document (i.e. =
who has
read it, who<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; believes it is a good starting point for =
working
group work, who<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; will contribute to the work) and whether =
there are
any significant<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; technical issues. Statements of objection =
must be
backed up by<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; proper technical reasons.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; So please respond to this poll indicating =
whether
you support the<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; adoption of this draft or stating your =
technical
issues.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; Please also not that this draft has after a
discussion with the<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; working group chairs been renamed, it was =
earlier
know as<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; =
draft-nitinb-mpls-tp-lsp-ping-extensions-01.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; This poll ends eob July 5.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; Loa and George<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; mpls wg co-chairs<o:p></o:p></p>

<p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>-- <o:p></o:p></p>

<p =
class=3DMsoPlainText>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p=
></p>

<p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a =
href=3D"http://www.van-helvoort.eu/">http://www.van-helvoort.eu/</a><o:p>=
</o:p></p>

<p =
class=3DMsoPlainText>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p=
></p>

<p class=3DMsoPlainText>Always remember that you are unique...just like =
everyone
else...<o:p></o:p></p>

<p =
class=3DMsoPlainText>_______________________________________________<o:p>=
</o:p></p>

<p class=3DMsoPlainText>mpls-tp mailing list<o:p></o:p></p>

<p class=3DMsoPlainText><a =
href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a><o:p></o:p></p>

<p class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls-tp">https://www.ietf.o=
rg/mailman/listinfo/mpls-tp</a><o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01CB1D28.58E63D75--

From root@core3.amsl.com  Tue Jul  6 09:30:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 028FD3A688A; Tue,  6 Jul 2010 09:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100706163002.028FD3A688A@core3.amsl.com>
Date: Tue,  6 Jul 2010 09:30:02 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-tp-fault-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jul 2010 16:30:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.


	Title           : MPLS Fault Management OAM
	Author(s)       : G. Swallow, et al.
	Filename        : draft-ietf-mpls-tp-fault-02.txt
	Pages           : 14
	Date            : 2010-07-05

This draft specifies OAM messages to indicate service disruptive
conditions for MPLS Transport Profile (MPLS-TP) Label Switched Paths
(LSPs).  The notification mechanism employs a generic method for a
service disruptive condition to be communicated to a Maintenance End
Point (MEP).  An MPLS Operation, Administration, and Maintenance
(OAM) channel is defined along with messages to communicate various
types of service disruptive conditions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-fault-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-mpls-tp-fault-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-06092136.I-D@ietf.org>


--NextPart--

From curtis@occnc.com  Tue Jul  6 11:12:17 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C5A983A68C6; Tue,  6 Jul 2010 11:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.217
X-Spam-Level: 
X-Spam-Status: No, score=-2.217 tagged_above=-999 required=5 tests=[AWL=0.382,  BAYES_00=-2.599]
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 brT0UvI-6OLT; Tue,  6 Jul 2010 11:12:16 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 1B1BA3A688A; Tue,  6 Jul 2010 11:12:15 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o66ICFR0010664; Tue, 6 Jul 2010 14:12:15 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007061812.o66ICFR0010664@harbor.orleans.occnc.com>
To: John E Drake <jdrake@juniper.net>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Tue, 06 Jul 2010 09:10:35 PDT." <5E893DB832F57341992548CDBB3331639843877BA7@EMBX01-HQ.jnpr.net> 
Date: Tue, 06 Jul 2010 14:12:15 -0400
Sender: curtis@occnc.com
Cc: "draft-ietf-pwe3-fat-pw@tools.ietf.org" <draft-ietf-pwe3-fat-pw@tools.ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>, pwe3 <pwe3@ietf.org>, "curtis@occnc.com" <curtis@occnc.com>
Subject: Re: [mpls] [PWE3] Multiple RSVP paths
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jul 2010 18:12:18 -0000

In message <5E893DB832F57341992548CDBB3331639843877BA7@EMBX01-HQ.jnpr.net>
John E Drake writes:
>  
> Hi,
>  
> A related ID:
>  
> http://www.ietf.org/id/draft-kompella-mpls-rsvp-ecmp-00.txt
>  
> Thanks,
>  
> John


John,

The use of the E-bit is not clear.  If the sub-LSP all have E=0, is
the load split proportional to the sub-LSP reserved bandwidth?  If E=1
are the reserved bandwidths of the component LSP all ignored?  What
happens if E=0 for some sub-LSP and E=1 for others?

Also in the figure:

                          ------------- M -----
                         /                      \
                        /           --- P --     \
                       /           /         \    \
                      A --- X --- Y --- Q --- T --- B
                             \     \              / |
                              \     --- R -------   |
                               \                    |
                                ------- S ----------

It is possible to set up link bundle Y-P-T and Y-Q-T as Y-T at PSC-4,
then bundle Y-P-T-B and Y-R-B as Y-B at PSC-3, then X-Y-B and X-S-B as
X-B at PSC-2, and A-M-B and A-X-B as A-B as PSC-1.  Done with one PSC
value to spare (the implied PSC=0).

This use of link bundling would yield the finest control over the
allocation of resources.  Each link bundle is the sum of the
components.

The problem with link bundling and a limitation of the draft in
question is that some LSP over this bundled LSP cannot specify that it
*needs* to take one component (to be MPLS-TP compliant, for example),
and allow other LSP to indicate that it is fine to load split it.

[  And now a word for our sponsor.  :-)  ]
See draft-villamizar-mpls-tp-multipath-00 for further requirements.

Curtis


> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> > Curtis Villamizar
> > Sent: Tuesday, July 06, 2010 8:30 AM
> > To: stbryant@cisco.com
> > Cc: draft-ietf-pwe3-fat-pw@tools.ietf.org; pwe3
> > Subject: Re: [PWE3] Multiple RSVP paths
> > 
> > 
> > In message <4C31E719.1060402@cisco.com>
> > Stewart Bryant writes:
> > >
> > > In response to a comment received during last call I have added a new
> > > section 7.3 entitled : "Multiple RSVP-TE Paths" which says:
> > >
> > > In some networks it is desirable for a Label Edge Router (LER) to be
> > > able to load balance a PW across multiple RSVP-TE tunnels. The flow
> > > label mechanism described in this document may be used to provide the
> > > LER with the required flow information, and necessary entropy to provide
> > > this type of load balancing. Methods by which the LER is configured to
> > > apply this type of ECMP is outside the scope of this document.
> > >
> > > - Stewart
> > 
> > 
> > Stewart,
> > 
> > You could mention using a link bundle with the all ones component
> > link as a possibility but still leave further details out of scope and
> > not preclude other mechanisms that are local to the LER.
> > 
> > Curtis
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3


From hhelvoort@chello.nl  Tue Jul  6 22:52:26 2010
Return-Path: <hhelvoort@chello.nl>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C2E43A659B; Tue,  6 Jul 2010 22:52:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g9dQVsX1262s; Tue,  6 Jul 2010 22:52:24 -0700 (PDT)
Received: from fep32.mx.upcmail.net (fep32.mx.upcmail.net [62.179.121.50]) by core3.amsl.com (Postfix) with ESMTP id A95243A67AC; Tue,  6 Jul 2010 22:52:23 -0700 (PDT)
Received: from edge03.upcmail.net ([192.168.13.238]) by viefep16-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100707053523.ULMT26979.viefep16-int.chello.at@edge03.upcmail.net>; Wed, 7 Jul 2010 07:35:23 +0200
Received: from viefep11.chello.at ([192.168.14.250]) by edge03.upcmail.net with edge id etbP1e01f5PiXJQ03tbPFn; Wed, 07 Jul 2010 07:35:23 +0200
X-SourceIP: 192.168.14.250
Message-ID: <23010270.1278480923880.JavaMail.root@viefep11.chello.at>
Date: Wed, 7 Jul 2010 5:35:23 +0000
From: <hhelvoort@chello.nl>
To: mpls-tp@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
Sensitivity: Normal
X-Originating-IP: from 217.133.95.28 by web-edge.chello.com; Wed, 7 Jul 2010 7:35:23 +0200
X-Cloudmark-Analysis: v=1.1 cv=KBHyIoyMIRH440NzHl6uMYpbxJngTLC2P1JzLC/QbPg= c=1 sm=0 a=ljhsCbbW0vwA:10 a=0qYQvVkOOIcA:10 a=IkcTkHD0fZMA:10 a=48vgC7mUAAAA:8 a=dS8YiDXwOnpl5-OKLHAA:9 a=lD4Mda5SaSCGFRqV0qYZHbqOe_cA:4 a=QEXdDO2ut3YA:10 a=lZB815dzVvQA:10 a=PQwv-0s9RZXQzKR3:21 a=XaY8Z6orFiRFemDW:21 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: mpls@ietf.org, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>
Subject: Re: [mpls] comment draft-nitinb-mpls-tp-on-demand-cv
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2010 05:52:26 -0000

Dear Nurit,

(I changed the subject line as requested by the WG chair)

Please see in-line [hvh]

Best regards, Huub.


On 06-07-10 18:29, Sprecher, Nurit wrote:
> Huub,
>=20
> Please see inline.
>=20
> Best regards,
>=20
> Nurit
>=20
> -----Original Message-----
>=20
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On=20
> Behalf Of ext Huub van Helvoort
>=20
> Sent: Monday, July 05, 2010 2:56 PM
>=20
> To: Loa Andersson
>=20
> Cc: mpls@ietf.org; MPLS-TP ad hoc team; mpls-tp@ietf.org
>=20
> Subject: Re: [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv=20
> as a working group document
>=20
> No/do not support
>=20
> The change of the name of this draft gives the impression
>=20
> that the content of the draft changed as well.
>=20
> So before it can be adopted the text has to be aligned
>=20
> with the title: On-demand CV for MPLS-TP.
>=20
> I see that it is still focused on extending LSP-Ping but
>=20
> not for use in a transport environment.
>=20
> <Nurit>  please be more specific. For me it looks that you just missed th=
e statement in the document saying=E2=80=9CIn such scenarios, LSP-Ping SHOU=
LD be run without IP addressing, using the ACH channel type specified in (I=
-D.ietf-mpls-tp-lsp-ping-bfd-procedures]. Maybe you should look at  http://=
datatracker.ietf.org/doc/draft-ietf-mpls-tp-lsp-ping-bfd-procedures/  \<Nur=
it>
>=20
> It does not indicate where the transport OAM requirements
>=20
> are met.
>=20
> <Nurit> the assumption it is unless you prove otherwise \<Nurit>

[hvh] standardisation is not a religion; religions are based on assumptions=
, standards describe facts.

> It does not indicate how the ACh is used.
>=20
> <Nurit> see above. You probably missed in your review the reference to=20
> ietf-mpls-tp-lsp-ping-bfd-procedures \<Nurit>
>=20
> What is the meaning of "adjacency" in the context of MPLS-TP?
>=20
> It does not document how this tool can be used in transport
>=20
> environment where tools are enabled/disabled static (compared
>=20
> to the dynamic set-up of LSP-ping.
>=20
> <Nurit> your comment is not clear \<Nurit>
>=20
> Regards, Huub.
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Always remember that you are unique...just like everyone else...


From yaacov.weingarten@nsn.com  Wed Jul  7 02:54:59 2010
Return-Path: <yaacov.weingarten@nsn.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2E623A67CF; Wed,  7 Jul 2010 02:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 yp5+dlrfCJGy; Wed,  7 Jul 2010 02:54:57 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 284A13A67CC; Wed,  7 Jul 2010 02:54:56 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o679ssCC010142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 7 Jul 2010 11:54:54 +0200
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o679sgDO022916; Wed, 7 Jul 2010 11:54:53 +0200
Received: from DEMUEXC030.nsn-intra.net ([10.150.128.57]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 7 Jul 2010 11:54:51 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Jul 2010 11:54:48 +0200
Message-ID: <62D9AC1F11702146A0387CBFF3A8CD3D025DD950@DEMUEXC030.nsn-intra.net>
In-Reply-To: <23010270.1278480923880.JavaMail.root@viefep11.chello.at>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] comment draft-nitinb-mpls-tp-on-demand-cv
Thread-Index: AcsdmJrc4KuZr0LNSb6gENV1J9BhpAAIP7dA
References: <23010270.1278480923880.JavaMail.root@viefep11.chello.at>
From: "Weingarten, Yaacov (NSN - IL/Hod HaSharon)" <yaacov.weingarten@nsn.com>
To: <hhelvoort@chello.nl>, <mpls-tp@ietf.org>
X-OriginalArrivalTime: 07 Jul 2010 09:54:51.0174 (UTC) FILETIME=[71463460:01CB1DBA]
Cc: mpls@ietf.org, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>
Subject: Re: [mpls] [mpls-tp] comment draft-nitinb-mpls-tp-on-demand-cv
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2010 09:54:59 -0000

Huub, hi

You wrote (snipped)
*******************************

[hvh] standardisation is not a religion; religions are based on
assumptions, standards describe facts.

*************************

[yw>] Unfortunately, I have seen very many times that standardization
has been turned into very strange religious wars!! Where the two camps
involved abandon all technical arguments and resort to - "this isn't
what I proposed and therefore I cannot support it"

Hoping that this will be taken with the right measure of non-religion!
;-)

BR,
yaacov

From root@core3.amsl.com  Wed Jul  7 07:31:00 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id B4E1E3A6832; Wed,  7 Jul 2010 07:30:09 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100707143025.B4E1E3A6832@core3.amsl.com>
Date: Wed,  7 Jul 2010 07:30:10 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-mldp-in-band-signaling-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2010 14:31:00 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.


	Title           : mLDP based in-band signaling for Point-to-Multipoint and Multipoint-to- Multipoint Label Switched Paths
	Author(s)       : I. Wijnands, et al.
	Filename        : draft-ietf-mpls-mldp-in-band-signaling-02.txt
	Pages           : 13
	Date            : 2010-07-07

Suppose an IP multicast tree, constructed by Protocol Independent
Multicast (PIM), needs to pass through an MPLS domain in which
Multipoint LDP (mLDP) Point-to-Multipoint and/or Multipoint-to-
Multipoint Labels Switched Paths (LSPs) can be created.  The part of
the IP multicast tree that traverses the MPLS domain can be
instantiated as a multipoint LSP.  When a PIM Join message is
received at the border of the MPLS domain, information from that
message is encoded into mLDP messages.  When the mLDP messages are
received at the border of the next IP domain, the encoded information
is used to generate PIM messages that can be sent through the IP
domain.  The result is an IP multicast tree consisting of a set of IP
multicast sub-trees that are spliced together with a multipoint LSP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-mldp-in-band-signaling-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-mpls-mldp-in-band-signaling-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-07071904.I-D@ietf.org>


--NextPart--

From db3546@att.com  Wed Jul  7 07:57:07 2010
Return-Path: <db3546@att.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 678603A67D3; Wed,  7 Jul 2010 07:57:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUwwwPSj0laM; Wed,  7 Jul 2010 07:57:06 -0700 (PDT)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id 876CC3A67C3; Wed,  7 Jul 2010 07:57:05 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: db3546@att.com
X-Msg-Ref: server-5.tower-129.messagelabs.com!1278514627!33491293!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 1761 invoked from network); 7 Jul 2010 14:57:08 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-5.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Jul 2010 14:57:08 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o67EugbU004225; Wed, 7 Jul 2010 10:56:43 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o67EueTR004216; Wed, 7 Jul 2010 10:56:41 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Jul 2010 10:57:03 -0400
Message-ID: <D6CB948F7AFD6F4881D4B4F80C8509AA073E0923@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last call on draft-ietf-ccamp-mpls-tp-cp-framework-02.txt
Thread-Index: Acsd5KjavXnp1fQlSf+BwrHsqstq4w==
From: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
To: "CCAMP" <ccamp@ietf.org>, <pwe3@ietf.org>
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: [mpls] Last call on draft-ietf-ccamp-mpls-tp-cp-framework-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2010 14:57:07 -0000

This begins a joint ccamp and pwe3 last call on
draft-ietf-ccamp-mpls-tp-cp-framework-02.txt:
http://www.ietf.org/id/draft-ietf-ccamp-mpls-tp-cp-framework-02.txt

The last call ends on July 21, 2010 at 24:00 UTC.

Please send comments to the ccamp and pwe3 lists.

Deborah and Andy and Matthew

From wwwrun@rfc-editor.org  Wed Jul  7 08:22:13 2010
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 04A7A3A67E7 for <mpls@core3.amsl.com>; Wed,  7 Jul 2010 08:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J3waMjv0TkW5 for <mpls@core3.amsl.com>; Wed,  7 Jul 2010 08:22:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 94F2A3A6812 for <mpls@ietf.org>; Wed,  7 Jul 2010 08:22:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 490DEE0677; Wed,  7 Jul 2010 08:22:12 -0700 (PDT)
To: yakov@juniper.net, erosen@cisco.com, stbryant@cisco.com, adrian.farrel@huawei.com, swallow@cisco.com, loa@pi.nu
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20100707152212.490DEE0677@rfc-editor.org>
Date: Wed,  7 Jul 2010 08:22:12 -0700 (PDT)
Cc: rfc-editor@rfc-editor.org, mpls@ietf.org
Subject: [mpls] [Technical Errata Reported] RFC3107 (2319)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2010 15:22:13 -0000

The following errata report has been submitted for RFC3107,
"Carrying Label Information in BGP-4".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3107&eid=2319

--------------------------------------
Type: Technical
Reported by: Bruno Decraene <bruno.decraene@orange-ftgroup.com>

Section: 5

Original Text
-------------
"A BGP speaker should not advertise this capability to another BGP speaker unless there is a Label Switched Path (LSP) between the two speakers."


Corrected Text
--------------
"An eBGP speaker should not advertise this capability to another eBGP speaker unless there is a Label Switched Path (LSP) or layer two interface between the two speakers."

Or just remove completely that sentence.

Notes
-----
1) :s/BGP/eBGP
An iBGP router should be able to set up an internal BGP session for AFI 1 / SAFI 4 toward a Route Reflector even if the Route Reflector is not capabble of forwarding MPLS packets (This case is even described in the section 2 of the RFC)

2) + layer two interface
If both router are connected by a direct (sub)interface, they should be able to exchange MPLS packets even if there is no LSP between them.

3) Remove the sentence
AFAIK, the point is now better addressed by draft-ietf-idr-bgp-bestpath-selection-criteria-01.txt

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC3107 (draft-ietf-mpls-bgp4-mpls-04)
--------------------------------------
Title               : Carrying Label Information in BGP-4
Publication Date    : May 2001
Author(s)           : Y. Rekhter, E. Rosen
Category            : PROPOSED STANDARD
Source              : Multiprotocol Label Switching
Area                : Routing
Stream              : IETF
Verifying Party     : IESG

From wwwrun@core3.amsl.com  Thu Jul  8 08:10:15 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 4366B3A6AE9; Thu,  8 Jul 2010 08:10:15 -0700 (PDT)
From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: greg.jones@itu.int
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100708151015.4366B3A6AE9@core3.amsl.com>
Date: Thu,  8 Jul 2010 08:10:15 -0700 (PDT)
Cc: mpls@ietf.org, stbryant@cisco.com, greg.jones@itu.int, Matthew.Bocci@alcatel-lucent.com, malcolm.betts@zte.com.cn, andrew.g.malis@verizon.com, dward@juniper.net, yoichi.maeda@ntt-at.co.jp, mpls-tp@ietf.org, ahmpls-tp@lists.itu.int, paf@cisco.com, adrian.farrel@huawei.com, rcallon@juniper.net, tsbsg15@itu.int, hhelvoort@huawei.com, hklam@alcatel-lucent.com, ghani.abbas@ericsson.com
Subject: [mpls] New Liaison Statement, "MPLS-TP Control Plane Framework #036.01"
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: db3546@att.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2010 15:10:15 -0000

Title: MPLS-TP Control Plane Framework #036.01
Submission Date: 2010-07-08
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=921 
Please reply by 2010-07-26

From: Loa Andersson(IETF MPLS WG) <loa@pi.nu>
To: ITU-T SG15 Q9, Q10, Q12 and Q14(greg.jones@itu.int)
Cc: yoichi.maeda@ntt-at.co.jp
greg.jones@itu.int
ghani.abbas@ericsson.com
hhelvoort@huawei.com
malcolm.betts@zte.com.cn
hklam@alcatel-lucent.com
tsbsg15@itu.int
ahmpls-tp@lists.itu.int
dward@juniper.net
adrian.farrel@huawei.com
rcallon@juniper.net
paf@cisco.com
stbryant@cisco.com
mpls@ietf.org
mpls-tp@ietf.org
swallow@cisco.com
Matthew.Bocci@alcatel-lucent.com
andrew.g.malis@verizon.com
Reponse Contact: db3546@att.com
Technical Contact: db3546@att.com
Purpose: For comment 
Body: 

Title: MPLS-TP Control Plane Framework #036.01

We like to to inform you that the CCAMP, PWE3 and MPLS working 
groups just started a joint working group last call on the 
"MPLS-TP Control Plane Framework":

http://www.ietf.org/id/draft-ietf-ccamp-mpls-tp-cp-framework-02.txt

In order to progress this work in a timely manner we need to receive
comments from the ITU-T by July 26th 2010.

Deborah Brungard and Lou Berger
CCAMP working group co-chairs

Matthew Bocci & Andy Malis
PWE3 working group co-chairs

Loa Andersson & George Swallow
MPLS Working Group co-chairs
Attachment(s):
No document has been attached



From db3546@att.com  Thu Jul  8 09:40:21 2010
Return-Path: <db3546@att.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFEBA3A6AF3; Thu,  8 Jul 2010 09:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FM87gLG6+e5F; Thu,  8 Jul 2010 09:40:20 -0700 (PDT)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id 7255F3A6B30; Thu,  8 Jul 2010 09:40:20 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: db3546@att.com
X-Msg-Ref: server-11.tower-167.messagelabs.com!1278607223!27370463!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 19154 invoked from network); 8 Jul 2010 16:40:24 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-11.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Jul 2010 16:40:24 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o68GduVi005594; Thu, 8 Jul 2010 12:39:56 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o68Gdqjh005558; Thu, 8 Jul 2010 12:39:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 8 Jul 2010 12:40:15 -0400
Message-ID: <D6CB948F7AFD6F4881D4B4F80C8509AA07433478@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [CCAMP] Last call on draft-ietf-ccamp-mpls-tp-cp-framework-02.txt
Thread-Index: Acsd5KjavXnp1fQlSf+BwrHsqstq4wA1mEKg
From: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
To: "CCAMP" <ccamp@ietf.org>, <pwe3@ietf.org>, <mpls@ietf.org>
Cc: mpls-tp@ietf.org
Subject: [mpls] FW: [CCAMP] Last call on draft-ietf-ccamp-mpls-tp-cp-framework-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2010 16:40:21 -0000

This WG Last Call will be extended to be a joint last call of the ccamp,
pwe3, and mpls wgs and the end date extended to July 26th.

Thanks,
CCAMP Co-Chairs, PWE3 Co-Chairs, MPLS Co-Chairs

-----Original Message-----
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf
Of BRUNGARD, DEBORAH A (ATTLABS)
Sent: Wednesday, July 07, 2010 10:57 AM
To: CCAMP; pwe3@ietf.org
Cc: mpls@ietf.org; mpls-tp@ietf.org
Subject: [CCAMP] Last call on
draft-ietf-ccamp-mpls-tp-cp-framework-02.txt

This begins a joint ccamp and pwe3 last call on
draft-ietf-ccamp-mpls-tp-cp-framework-02.txt:
http://www.ietf.org/id/draft-ietf-ccamp-mpls-tp-cp-framework-02.txt

The last call ends on July 21, 2010 at 24:00 UTC.

Please send comments to the ccamp and pwe3 lists.

Deborah and Andy and Matthew
_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp

From lavanya.srivatsa@aricent.com  Mon Jul  5 05:52:59 2010
Return-Path: <lavanya.srivatsa@aricent.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7905A3A6838 for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 05:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKSf9-2ZOTco for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 05:52:58 -0700 (PDT)
Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by core3.amsl.com (Postfix) with ESMTP id A7CCA3A68CC for <mpls@ietf.org>; Mon,  5 Jul 2010 05:52:57 -0700 (PDT)
Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id AAFFD36B75; Mon,  5 Jul 2010 18:22:34 +0530 (IST)
Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (Postfix) with ESMTP id 9524E36B2D; Mon,  5 Jul 2010 18:22:34 +0530 (IST)
Received: from GUREXMB02.ASIAN.AD.ARICENT.COM ([10.203.171.134]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Mon, 5 Jul 2010 18:22:56 +0530
From: Lavanya Srivatsa <lavanya.srivatsa@aricent.com>
To: MPLS TP <mpls-tp@ietf.org>, "loa@pi.nu" <loa@pi.nu>
Date: Mon, 5 Jul 2010 18:22:57 +0530
Thread-Topic: [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
Thread-Index: AcscPcK0uiKqVsQRQCSiVMrEbZSWCwAAJksr
Message-ID: <AF085525D89CCA4EB233BE7E5BF2FDAB1693A750CA@GUREXMB02.ASIAN.AD.ARICENT.COM>
References: <4C1F5616.2060406@pi.nu>, <AANLkTimgyh5dMZ_vl07c518rpxNpQg5Jcei4Qs6UU5vn@mail.gmail.com>
In-Reply-To: <AANLkTimgyh5dMZ_vl07c518rpxNpQg5Jcei4Qs6UU5vn@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Jul 2010 11:38:35 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ahmpls-tp@lists.itu.int" <ahmpls-tp@lists.itu.int>
Subject: Re: [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jul 2010 12:52:59 -0000

Yes / Support.

However, I have some comments/queries that I would request be updated in th=
e next version (if the authors
agree with my comments, of course!).

(1)  In Section 2.2, it states "When sending LSP-Ping packets using ACH, wi=
thout IP encapsulation,
   there MAY be a need to identify the source address of the packet.
   This source address will be specified via the Source Address TLV,
   being defined in [I-D.ietf-mpls-tp-ach-tlv]"
[LS] The ACH TLV draft has Source Address only in
the IP format and not in the non-IP format as per mpls-tp-identifiers draft=
.

(2) Section 2.3 states - "Only one identifier (MEP or MIP) MUST be present =
in a packet."
[LS] Would there not be a scenario that a Source MEP and a Destination MIP =
might need
to be carried in the packet for connectivity verification to intermediate/t=
ransit nodes?
I agree that source MEP/source MIP and destination MEP/destination MIP are =
invalid combinations
but Source MEP/Destination MIP seems a "possible" combination?

(3) Section 3.3 states that the Egress Node may add the Target FEC Stack TL=
V in its echo responses.
[LS] How will the egress node know when to do so? Is it expected/mandated t=
hat the echo request
should have an newly defined bit set in the Global Flags field to indicate =
that the response should
contain a Target FEC stack? If so, then I think that this draft needs to ex=
plain this modification on
the base rfc 4379.
On the same lines, would it also be recommended that the echo response cont=
ains the V bit
set in the Global Flags to indicate that the ingress must validate the reve=
rse FEC?

- Lavanya


---------- Forwarded message ----------
From: Loa Andersson <loa@pi.nu<mailto:loa@pi.nu>>
Date: Mon, Jun 21, 2010 at 5:37 PM
Subject: [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a workin=
g group document
To: "mpls-tp@ietf.org<mailto:mpls-tp@ietf.org>" <mpls-tp@ietf.org<mailto:mp=
ls-tp@ietf.org>>, mpls@ietf.org<mailto:mpls@ietf.org>, MPLS-TP ad hoc team =
<ahmpls-tp@lists.itu.int<mailto:ahmpls-tp@lists.itu.int>>



Working Group,

this email is to start poll to adopt
draft-nitinb-mpls-tp-on-demand-cv-00.txt
as an MPLS working group draft.

After recent experience, the chairs would like to remind you all
what it means to conduct a poll to adopt a draft as a working group
draft.

- Please recall that the IETF does not "vote." Polls of a working
 group are to gather information to help the chairs make their
 decisions. Voting is not part of the normal working methods of
 an IETF working group.

- The "rough consensus" process used in the working group assumes
 that people expressing opinions are also participating in the
 development of standards documents.

- Subscription to the list specifically to express an opinion is
 noticed by the chairs who has access to information on the new list
 members. Such behavior is not part of the normal working methods.

- The purpose of a poll for adoption is to help the chairs understand
 the level of support for a document (i.e. who has read it, who
 believes it is a good starting point for working group work, who
 will contribute to the work) and whether there are any significant
 technical issues. Statements of objection must be backed up by
 proper technical reasons.

So please respond to this poll indicating whether you support the adoption =
of this draft or stating your technical issues.

Please also not that this draft has after a discussion with the
working group chairs been renamed, it was earlier know as
draft-nitinb-mpls-tp-lsp-ping-extensions-01.

This poll ends eob July 5.


Loa and George
mpls wg co-chairs

--


Loa Andersson                         email: loa.andersson@ericsson.com<mai=
lto:loa.andersson@ericsson.com>
Sr Strategy and Standards Manager            loa@pi.nu<mailto:loa@pi.nu>
Ericsson Inc                          phone: +46 10 717 52 13
                                            +46 767 72 92 13
_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls


"DISCLAIMER: This message is proprietary to Aricent and is intended solely =
for the use of the individual to whom it is addressed. It may contain privi=
leged or confidential information and should not be circulated or used for =
any purpose other than for what it is intended. If you have received this m=
essage in error, please notify the originator immediately. If you are not t=
he intended recipient, you are notified that you are strictly prohibited fr=
om using, copying, altering, or disclosing the contents of this message. Ar=
icent accepts no responsibility for loss or damage arising from the use of =
the information transmitted by this email including damage from virus."

From daniel@olddog.co.uk  Mon Jul  5 15:27:19 2010
Return-Path: <daniel@olddog.co.uk>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60F293A6966 for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 15:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
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 Tq5zEQJUNHdu for <mpls@core3.amsl.com>; Mon,  5 Jul 2010 15:27:18 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id 5F6583A694A for <mpls@ietf.org>; Mon,  5 Jul 2010 15:27:18 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id o65MRIsw001289 for <mpls@ietf.org>; Mon, 5 Jul 2010 23:27:18 +0100
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id o65MRHmW001284 for <mpls@ietf.org>; Mon, 5 Jul 2010 23:27:18 +0100
From: "Daniel King" <daniel@olddog.co.uk>
To: <mpls@ietf.org>
Date: Mon, 5 Jul 2010 23:27:19 +0100
Message-ID: <000901cb1c91$3b35d350$b1a179f0$@co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsckTnApYLx6t11QCS544RROt0s1w==
Content-Language: en-gb
x-cr-hashedpuzzle: BXbA B4cp CuUg DPeE DVgR Dt84 EEU4 EFMy GfZA GuVd HOu1 H0EJ IYvV IovQ IuKe Ix+i; 1; bQBwAGwAcwBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {D55F6363-4AE7-4AA7-A7D5-A3D00A82656D}; ZABhAG4AaQBlAGwAQABvAGwAZABkAG8AZwAuAGMAbwAuAHUAawA=; Mon, 05 Jul 2010 22:27:17 GMT; TQBQAEwAUwAtAFQAUAAgAE0ASQBCAC0AYgBhAHMAZQBkACAATQBhAG4AYQBnAGUAbQBlAG4AdAAgAE8AdgBlAHIAdgBpAGUAdwA=
x-cr-puzzleid: {D55F6363-4AE7-4AA7-A7D5-A3D00A82656D}
X-Mailman-Approved-At: Thu, 08 Jul 2010 11:38:35 -0700
Subject: [mpls] MPLS-TP MIB-based Management Overview
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jul 2010 22:27:19 -0000

Hello All, 

Please find a new draft for your reading pleasure: 

http://tools.ietf.org/html/draft-farrel-mpls-tp-mib-management-overview-00

The document draft-farrel-mpls-tp-mib-management-overview-00 describes the
MIB-based management architecture for MPLS-TP and indicates the
interrelationships between the different MIB modules used for MPLS-TP
network management. The document also indentifies areas where additional MIB
modules would be required to support an MPLS-TP network.

The document uses a similar format to MPLS Management Overview [RFC4221] and
we appreciate the effort the authors made when compiling RFC4221. 

As ever, WG feedback and contributions are warmly welcome. 

Br, Dan. 


From eric.gray@ericsson.com  Wed Jul  7 08:23:15 2010
Return-Path: <eric.gray@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41D443A67B6; Wed,  7 Jul 2010 08:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.398
X-Spam-Level: 
X-Spam-Status: No, score=-3.398 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_MED=-4]
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 XTHxXbMV8znC; Wed,  7 Jul 2010 08:23:13 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 07E5A3A67E7; Wed,  7 Jul 2010 08:23:12 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o67FUpXH032273; Wed, 7 Jul 2010 10:30:51 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.117]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Wed, 7 Jul 2010 11:22:42 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Adrian Farrell <adrian@olddog.co.uk>, Daniel King <daneil@olddog.co.uk>, Venkatesan Mahalingam <venkatesan.mahalingam@aricent.com>, Scott Mansfield <scott.mansfield@ericsson.com>, Jeong-dong Ryoo <ryoo@etri.re.kr>, A S Kiran Koushik <kkoushik@cisco.com>
Date: Wed, 7 Jul 2010 11:22:41 -0400
Thread-Topic: MPLS-TP management overview draft - draft-farrel-mpls-tp-mib-management-overview
Thread-Index: AcscD8GdnJJt1+P0Qm+EW0w8sk3FrgACrfGAAAHgH+AANWxFIAABH7PgAAJfaFAAN/YnMA==
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F1053B72289E@EUSAACMS0701.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C0AC8FAB6849AB4FADACCC70A949E2F1053B72289EEUSAACMS0701e_"
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Jul 2010 11:38:35 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: [mpls] MPLS-TP management overview draft - draft-farrel-mpls-tp-mib-management-overview
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2010 15:23:15 -0000

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

Authors,

    Some comments on your draft...

    As a general comment, in addition to the MIBs already explicitly refere=
nced in this draft, you should probably
include:

o RFC 4801 ( "Definitions of Textual Conventions for Generalized Multiproto=
col Label Switching (GMPLS) Management " ),
o RFC 4802 ("Generalized Multiprotocol Label Switching (GMPLS) Traffic Engi=
neering Management Information Base"),
o RFC 4220 ("Traffic Engineering Link Management Information Base");

As is, there is a curious dearth of MIB references for GMPLS related MIBs, =
given GMPLS will be the signaling
method used for MPLS-TP LSPs.

    NITs:
    =3D=3D=3D

"functionss" is usually spelled with one "s" (page 7)

"exchaging" usually includes another "n" (page 7)

"MPLS packets are encapsulated by using its own header" doesn't
parse (page 7).  The second sentence in the same paragraph is just
barely more readable.  I would suggest re-writing the paragraph using
the phrase "label-stack" to replace "header."  This also eliminates the
need to identify the "header" as a "label-stack."

"path(" needs a space (page 8).

Change "The two important .." to "Two important ..." (page 8).  The
"two important applications" should be in bullet format.

"a MPLS" should be "an MPLS" anywhere that the indefinite article is
used in conjunction with "MPLS."

In the 5th paragraph on page 10, to what does "The document" refer?

Page 11 contains a number of examples where the first word following
a colon (":") is capitalized; this is not proper English - particularly whe=
n
the text following the colon is not in the form of a bulleted list.  I did =
not
check the entire draft for this, but suggest the authors should.

In the 2nd sentence, 7th paragraph of page 11, to what does "This MIB
module" refer?

The 2nd sentence in section 5.2.9 (top of page 13) does not parse.  I
suggest breaking this sentence down and clarifying what is meant by it.

The 2nd paragraph in section 5.2.10 (page 13) does not completely
describe the notation used.  An arrow indicates a dependency between
two MIB modules, but is clearly a directed dependency and meaning
is not clear: I suggest using a more illustrative example by making the
following change:

Change -
A relationship "MIB module A depends on MIB module B" means that
MIB module A uses an object, object identifier, or textual convention
defined in MIB module B, or that MIB module A contains a pointer
(index or RowPointer) to an object in MIB module B.
To -
The relationship "A --> B" means A depends on B and that MIB module
A uses an object, object identifier, or textual convention defined in MIB
module B, or that MIB module A contains a pointer (index or RowPointer)
to an object in MIB module B.
(Note that I am assumng I have the order of dependency correct, based
on conventional "logical dependency" - I did not verify this be analyzing
the diagram on page 14)

I suggest restructuring the last paragraph on page 16 (continuing on to
page 17) as two paragraphs, each including bulleted lists, as follows:

"The following MPLS-TP OAM functionalities can be achieved using the
 MPLSTP-OAM-STD-MIB mib extensions:

    o    Continuity Check and Connectivity Verification,
    o    Alarm Reporting, Diagnostic,
    o    Route Tracing,
    o    Loopback tool,
    o    Lock Instruct,
    o    Lock Reporting Remote Defect Indication,
    o    Client Failure Indication,
    o    Packet Loss Measurement and
    o    Packet Delay Measurement

"MPLS-TP OAM managed objects are defined based on the drafts:
    o    draft-ietf-mpls-tp-oam-requirements-06,
    o    draft-ietf-mpls-tp-oam-framework-06 and
    o    draft-ietf-mpls-tp-identifiers-01."

The last paragraph on page 17 (continuing on to page 18) has the same
problem as the 2nd paragraph on page 13 (described above) and needs
a similar resolution.  One approach might be to include this as part of a
new section (under modified section 2 "Conventions and Terminology"),
so that it does not need to be repeated.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D

    Not so NITty:
    =3D=3D=3D=3D=3D=3D=3D=3D=3D

There are several problems with this paragraph (page 7):

"The basic unit in an MPLS network is called LSR(Label switched
  router). It implements the control and forwarding plane of MPLS."

o    as a NIT, "LSR(" needs a space;
o    the meaning of "basic unit" is not at all clear;
o    an LSR does not necessarily implement a control plane.
---------------------------------------------------------------------------=
------------------------------

The next paragraph is also inaccurate  (also page 7) .

The control plane of an LSR is not directly responsible for exchanging
routing information (that is the control plane of the "router" part of an
LSR, again not necessarily part of an LSR in the general sense).  This
"routing information" - if present - is simply one source of information
that an LSR uses to "program" (not the best wording choice - I suggest
"populate") forwarding tables.

The LSR "control plane" provides information in terms of label bindings
which are part of the information used to populate forwarding tables in
an LSR.  An LSR determines which label bindings to seek and retain
based on configuration and other information (such as that which may
be provided by routing).

While the primary intent (and common implementation) relies on use of
the 20 bit label as an "index into a forwarding table", this is not the onl=
y
way that an LSR may be implemented, nor is it necessarily presumed
to be implemented this way.  This misconception is at the bottom of a
number of bad ideas that have been proposed in the MPLS WG (as well
as other places).  How an LSR chooses to employ the 20 bit labels it
assigns for use by its peers is entirely up to the implementation.

---------------------------------------------------------------------------=
------------------------------

The remaining paragraphs in the section are slightly inaccurate as well.

At "MPLS ingress", a "label stack" is prefixed.  In the simplest case, the
"label stack" comprises a single label-stack entry.

At LSP ingress (because of the possibility of nested - or hierarchical -
LSPs), there is the possibility that one or more additional label-stack
entries will be "pushed" onto the label stack - if there is a label stack
present already. Otherwise, the paragraph above applies.

In at least the first case, there is more to "encapsulating" the packet
than simply prefixing an MPLS label (stack).  It is also necessary to
add the appropriate "MPLS-specific" L2 encapsulation (including, for
instance, the MPLS PID).

For all "swap", "pop" and "push" operations, one or more labels may
be involved.

---------------------------------------------------------------------------=
------------------------------

I believe the last paragraph in section 5.2.6 (on page 12) is inaccurate.
A device that terminates an ATM pseudo-wire will almost certainly offer
an ATM interface to other devices (otherwise, what is the point of using
an ATM pseudowire?).  If it does, it will necessarily have to include that
interface as part of the ifTable.

In any case, inclusion of the last two sentence in the last paragraph of
section 5.2.6 is unnecessary and those sentences should be removed.

---------------------------------------------------------------------------=
------------------------------

In the Security Considerations section, in the 3rd paragraph, you point
out the potential issues with allowing write and create access.  In the
same paragraph, you then go on to say "allowed to access and GET"
MIB objects.  I suggest deleting "and GET" from this paragraph.

---------------------------------------------------------------------------=
------------------------------

In the IANA Considerations section, given this is an overview document,
I think you are safe in at least starting off with the basic "IANA has no
actions" text found in most IDs of this type.  It is fairly certain that th=
is
will not change, so you might as well get it out of the way.

=3D=3D=3D
Eric

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18470" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><![if !supportAnnotations]>
<STYLE id=3DdynCom type=3Dtext/css></STYLE>

<SCRIPT language=3DJavaScript><!--
function msoCommentShow(anchor_id, com_id)
{
	if(msoBrowserCheck())=20
		{
		c =3D document.all(com_id);
		a =3D document.all(anchor_id);
		if (null !=3D c && null =3D=3D c.length && null !=3D a && null =3D=3D a.l=
ength)
			{
			var cw =3D c.offsetWidth;
			var ch =3D c.offsetHeight;
			var aw =3D a.offsetWidth;
			var ah =3D a.offsetHeight;
			var x  =3D a.offsetLeft;
			var y  =3D a.offsetTop;
			var el =3D a;
			while (el.tagName !=3D "BODY")=20
				{
				el =3D el.offsetParent;
				x =3D x + el.offsetLeft;
				y =3D y + el.offsetTop;
				}
			var bw =3D document.body.clientWidth;
			var bh =3D document.body.clientHeight;
			var bsl =3D document.body.scrollLeft;
			var bst =3D document.body.scrollTop;
			if (x + cw + ah / 2 > bw + bsl && x + aw - ah / 2 - cw >=3D bsl )=20
				{ c.style.left =3D x + aw - ah / 2 - cw; }
			else=20
				{ c.style.left =3D x + ah / 2; }
			if (y + ch + ah / 2 > bh + bst && y + ah / 2 - ch >=3D bst )=20
				{ c.style.top =3D y + ah / 2 - ch; }
			else=20
				{ c.style.top =3D y + ah / 2; }
			c.style.visibility =3D "visible";
}	}	}
function msoCommentHide(com_id)=20
{
	if(msoBrowserCheck())
		{
		c =3D document.all(com_id);
		if (null !=3D c && null =3D=3D c.length)
		{
		c.style.visibility =3D "hidden";
		c.style.left =3D -1000;
		c.style.top =3D -1000;
		} }=20
}
function msoBrowserCheck()
{
	ms =3D navigator.appVersion.indexOf("MSIE");
	vers =3D navigator.appVersion.substring(ms + 5, ms + 6);
	ie4 =3D (ms > 0) && (parseInt(vers) >=3D 4);
	return ie4;
}
if (msoBrowserCheck())
{
	document.styleSheets.dynCom.addRule(".msocomanchor","background: infobackg=
round");
	document.styleSheets.dynCom.addRule(".msocomoff","display: none");
	document.styleSheets.dynCom.addRule(".msocomtxt","visibility: hidden");
	document.styleSheets.dynCom.addRule(".msocomtxt","position: absolute");
	document.styleSheets.dynCom.addRule(".msocomtxt","top: -1000");
	document.styleSheets.dynCom.addRule(".msocomtxt","left: -1000");
	document.styleSheets.dynCom.addRule(".msocomtxt","width: 33%");
	document.styleSheets.dynCom.addRule(".msocomtxt","background: infobackgrou=
nd");
	document.styleSheets.dynCom.addRule(".msocomtxt","color: infotext");
	document.styleSheets.dynCom.addRule(".msocomtxt","border-top: 1pt solid th=
reedlightshadow");
	document.styleSheets.dynCom.addRule(".msocomtxt","border-right: 2pt solid =
threedshadow");
	document.styleSheets.dynCom.addRule(".msocomtxt","border-bottom: 2pt solid=
 threedshadow");
	document.styleSheets.dynCom.addRule(".msocomtxt","border-left: 1pt solid t=
hreedlightshadow");
	document.styleSheets.dynCom.addRule(".msocomtxt","padding: 3pt 3pt 3pt 3pt=
");
	document.styleSheets.dynCom.addRule(".msocomtxt","z-index: 100");
}
// --></SCRIPT>
<![endif]>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.=
0pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
P.MsoCommentText {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","seri=
f"; mso-style-priority: 99; mso-style-link: "Comment Text Char"
}
LI.MsoCommentText {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","seri=
f"; mso-style-priority: 99; mso-style-link: "Comment Text Char"
}
DIV.MsoCommentText {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","seri=
f"; mso-style-priority: 99; mso-style-link: "Comment Text Char"
}
SPAN.MsoCommentReference {
	mso-style-priority: 99
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: "Times =
New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; =
mso-style-priority: 99
}
P.MsoCommentSubject {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tim=
es New Roman","serif"; mso-style-priority: 99; mso-style-link: "Comment Sub=
ject Char"
}
LI.MsoCommentSubject {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tim=
es New Roman","serif"; mso-style-priority: 99; mso-style-link: "Comment Sub=
ject Char"
}
DIV.MsoCommentSubject {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tim=
es New Roman","serif"; mso-style-priority: 99; mso-style-link: "Comment Sub=
ject Char"
}
P.MsoAcetate {
	FONT-SIZE: 8pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
	FONT-SIZE: 8pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
	FONT-SIZE: 8pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Tahoma","sans-serif"; m=
so-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso=
nal
}
SPAN.CommentTextChar {
	FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 99; mso-style-lin=
k: "Comment Text"; mso-style-name: "Comment Text Char"
}
SPAN.CommentSubjectChar {
	FONT-WEIGHT: bold; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority=
: 99; mso-style-link: "Comment Subject"; mso-style-name: "Comment Subject C=
har"
}
SPAN.EmailStyle24 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso=
nal-reply
}
SPAN.BalloonTextChar {
	FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link=
: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-GB vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT color=3D#0000ff><FONT =
size=3D2><SPAN=20
class=3D204040315-07072010>Authors</SPAN><SPAN class=3D037432012-06072010>,=
<SPAN=20
class=3D204040315-07072010>&nbsp;</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT color=3D#0000ff><FONT =
size=3D2><SPAN=20
class=3D037432012-06072010><SPAN=20
class=3D204040315-07072010></SPAN></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT color=3D#0000ff><FONT =
size=3D2><SPAN=20
class=3D037432012-06072010><SPAN=20
class=3D204040315-07072010>&nbsp;&nbsp;&nbsp;&nbsp;Some comments on your=20
draft...</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010>&nbsp;&nbsp;&n=
bsp;<FONT=20
face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D204040315-07072010>&nbsp;As a&nbsp;general comment, i</SPAN>n addit=
ion to=20
the MIBs already explicitly referenced in this draft, you should=20
probably&nbsp;<SPAN=20
class=3D204040315-07072010>&nbsp;</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>include: </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT face=3DA=
rial><FONT=20
color=3D#0000ff><FONT size=3D2>o RFC 4801 (<SPAN=20
class=3D204040315-07072010>&nbsp;"</SPAN><FONT face=3D"Times New Roman">Def=
initions=20
of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS=
)=20
Management</FONT><FONT face=3DArial><SPAN class=3D204040315-07072010>&nbsp;=
<FONT=20
face=3D"Times New Roman">"</FONT>&nbsp;</SPAN>),=20
</FONT></FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT face=3DA=
rial><FONT=20
color=3D#0000ff><FONT size=3D2>o RFC 4802 (<SPAN=20
class=3D204040315-07072010>"</SPAN><FONT face=3D"Times New Roman">Generaliz=
ed=20
Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Inform=
ation=20
Base</FONT><FONT face=3DArial><SPAN class=3D204040315-07072010><FONT=20
face=3D"Times New Roman">"</FONT></SPAN>),</FONT></FONT></FONT></FONT></SPA=
N></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT face=3DA=
rial><FONT=20
color=3D#0000ff><FONT size=3D2>o RFC 4220 (<SPAN=20
class=3D204040315-07072010>"</SPAN><FONT face=3D"Times New Roman">Traffic=20
Engineering Link Management Information Base</FONT><FONT face=3DArial><SPAN=
=20
class=3D204040315-07072010><FONT=20
face=3D"Times New Roman">"</FONT></SPAN>);</FONT></FONT></FONT></FONT></SPA=
N></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>As is, there is a curious dearth of MIB references=
 for=20
GMPLS related MIBs, given GMPLS will be the signaling</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT face=3DA=
rial><FONT=20
color=3D#0000ff><FONT size=3D2>method used for MPLS-TP LSPs.<SPAN=20
class=3D204040315-07072010>&nbsp;</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT face=3DA=
rial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D204040315-07072010></SPAN></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D037432012-06072010><FONT><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN class=3D204040315-07072010>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT=20
face=3DArial>&nbsp;&nbsp;&nbsp; <FONT color=3D#0000ff=20
size=3D2>NITs:</FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT=20
face=3DArial>&nbsp;&nbsp;&nbsp; <FONT color=3D#0000ff=20
size=3D2>=3D=3D=3D</FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>"functionss" is usually spelled with one "s" (page=
=20
7)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>"exchaging" usually includes another "n" (page=20
7)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>"MPLS packets are encapsulated by using its own he=
ader"=20
doesn't </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>parse (page 7).&nbsp; The second sentence in the s=
ame=20
paragraph is just</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>barely more readable.&nbsp; I would suggest re-wri=
ting the=20
paragraph using </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN class=3D856523512-0607=
2010><FONT=20
color=3D#0000ff size=3D2>the </FONT></SPAN><SPAN class=3D856523512-06072010=
><FONT=20
color=3D#0000ff size=3D2>phrase "label-stack" to replace "header."&nbsp; Th=
is also=20
eliminates the</FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>need to identify the "header" as a=20
"label-stack."</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>"path(" needs a space (page 8).</FONT></SPAN></DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Change "The two important .." to "Two important ..=
." (page=20
8).&nbsp; The </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>"two important applications" should be in bullet=20
format.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>"a MPLS" should be "an MPLS" anywhere that the ind=
efinite=20
article is</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>used in conjunction with "MPLS."</FONT></SPAN></DI=
V>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>In the 5th paragraph on page 10, to what does "The=
=20
document" refer?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Page 11 contains a number of examples where the fi=
rst word=20
following</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>a colon (":") is capitalized; this is not proper E=
nglish -=20
particularly when</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>the text following the colon is not in the form of=
 a=20
bulleted list.&nbsp; I did not</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>check the entire draft for this, but suggest the a=
uthors=20
should.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>In the 2nd sentence, 7th paragraph of page 11, to =
what does=20
"This MIB </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN class=3D856523512-0607=
2010><FONT=20
color=3D#0000ff size=3D2>module" </FONT></SPAN><SPAN class=3D856523512-0607=
2010><FONT=20
color=3D#0000ff size=3D2>refer?</FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>The&nbsp;2nd sentence in section 5.2.9 (top of pag=
e 13)=20
does not parse.&nbsp; I</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>suggest breaking this sentence down and clarifying=
 what is=20
meant by it.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>The 2nd paragraph in section 5.2.10 (page 13) does=
 not=20
completely</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>describe the notation used.&nbsp; An arrow indicat=
es a=20
dependency between</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>two MIB modules, but is clearly a directed depende=
ncy and=20
meaning</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>is not clear: I suggest using a more&nbsp;illustra=
tive=20
example by making the</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>following change:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Change -</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#ff0000 size=3D2>A relationship "MIB module A depends on MIB module=
 B" means=20
that </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#ff0000 size=3D2>MIB&nbsp;module A uses an object, object identifie=
r, or=20
textual convention<BR>defined in MIB module B, or that MIB module A contain=
s a=20
pointer<BR>(index or RowPointer) to an object in MIB module=20
B.<BR></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#ff0000=20
size=3D2><FONT face=3DArial color=3D#0000ff>To -</FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#ff0000=20
size=3D2>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN class=3D856523512-0607=
2010><FONT=20
color=3D#008000 size=3D2>The&nbsp;relationship "A --&gt; B"&nbsp;means A de=
pends on=20
B&nbsp;and that </FONT></SPAN><SPAN class=3D856523512-06072010><FONT color=
=3D#ff0000=20
size=3D2><FONT color=3D#008000>MIB&nbsp;module </FONT></FONT></SPAN></FONT>=
</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#ff0000=20
size=3D2><FONT face=3DArial color=3D#008000>A uses an object, object identi=
fier, or=20
textual convention defined in MIB </FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#ff0000=20
size=3D2><FONT face=3DArial color=3D#008000>module B, or that MIB module A =
contains a=20
pointer (index or RowPointer) </FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#ff0000=20
size=3D2><FONT face=3DArial><FONT color=3D#008000>to an object in MIB modul=
e=20
B.</FONT><BR></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#ff0000=20
size=3D2><FONT face=3DArial color=3D#0000ff>(Note that I am assumng I have =
the order=20
of dependency correct, based</FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#ff0000=20
size=3D2><FONT face=3DArial color=3D#0000ff>on conventional "logical depend=
ency" - I=20
did not verify this be analyzing</FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#ff0000=20
size=3D2><FONT face=3DArial color=3D#0000ff>the diagram on page=20
14)</FONT></DIV></FONT></SPAN></DIV></FONT></SPAN>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I suggest restructuring the last paragraph on page=
 16=20
(continuing on to</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN class=3D856523512-0607=
2010><FONT=20
color=3D#0000ff size=3D2>page 17) as&nbsp;two paragraphs, </FONT></SPAN><SP=
AN=20
class=3D856523512-06072010><FONT color=3D#0000ff size=3D2>each including bu=
lleted=20
lists, </FONT></SPAN><SPAN class=3D856523512-06072010><FONT color=3D#0000ff=
=20
size=3D2>as </FONT></SPAN><SPAN class=3D856523512-06072010><FONT color=3D#0=
000ff=20
size=3D2>follows:</FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial><FONT=20
color=3D#0000ff size=3D2>"</FONT><FONT color=3D#008000 size=3D2>The followi=
ng MPLS-TP=20
OAM functionalities&nbsp;can be achieved using the </FONT></FONT></SPAN></D=
IV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2>&nbsp;MPLSTP-OAM-STD-MIB mib=20
extensions:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Continuity =
Check and=20
Connectivity&nbsp;Verification, </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Alarm Repor=
ting,=20
Diagnostic, </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Route Traci=
ng,=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Loopback&nb=
sp;tool,=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Lock Instru=
ct,=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Lock Report=
ing=20
Remote Defect Indication, </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Client&nbsp=
;Failure=20
Indication, </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Packet Loss=
=20
Measurement and</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#008000 size=3D2>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Packet Dela=
y=20
Measurement</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#0000ff=20
size=3D2><FONT face=3DArial>"</FONT><FONT face=3DArial color=3D#008000>MPLS=
-TP&nbsp;OAM=20
managed objects are defined based on the drafts:<BR></FONT></FONT></SPAN></=
DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#008000=20
size=3D2><FONT face=3DArial>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp;=20
draft-ietf-mpls-tp-oam-requirements-06,&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;o&=
nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-mpls-tp-oam-framework-06=20
and&nbsp;<BR>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp;=20
draft-ietf-mpls-tp-identifiers-01.<FONT=20
color=3D#0000ff>"</FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>The last paragraph on page 17 (continuing on to pa=
ge 18)=20
has the same</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>problem as the 2nd paragraph on page 13 (described=
 above)=20
and needs</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>a similar resolution.&nbsp; One approach might be =
to=20
include this as part of a</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>new section (under modified section 2 "Conventions=
 and=20
Terminology"),</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>so that it does not need to be=20
repeated.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff=20
size=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT=20
face=3DArial>&nbsp;&nbsp;&nbsp; <FONT color=3D#0000ff size=3D2>Not so=20
NITty:</FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT=20
face=3DArial>&nbsp;&nbsp;&nbsp; <FONT color=3D#0000ff=20
size=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>There are several problems with this paragraph (pa=
ge=20
7):</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT color=3D=
#0000ff=20
size=3D2><FONT face=3DArial>"</FONT><FONT color=3D#000000 size=3D3><FONT fa=
ce=3DArial=20
color=3D#0000ff size=3D2>The basic unit in an MPLS network is called LSR(La=
bel=20
switched<BR>&nbsp; router). It implements the control and forwarding plane =
of=20
MPLS."</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff size=3D2>o&nbsp=
;&nbsp;&nbsp;=20
as a NIT, "LSR(" needs a space;</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff size=3D2>o&nbsp=
;&nbsp;&nbsp;=20
the meaning of "basic unit" is not at all=20
clear;</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff size=3D2>o&nbsp=
;&nbsp;&nbsp;=20
an LSR does not necessarily implement a control=20
plane.</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff=20
size=3D2>------------------------------------------------------------------=
---------------------------------------</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>The next paragraph=
 is also=20
inaccurate<SPAN class=3D204040315-07072010>&nbsp; (also page=20
7)&nbsp;</SPAN>.</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial><SPAN class=3D856523512-06072010><FONT color=3D#000=
0ff=20
size=3D2><FONT color=3D#000000 size=3D3><FONT color=3D#0000ff size=3D2>The =
control plane=20
of an LSR is </FONT></FONT></FONT></SPAN><SPAN class=3D856523512-06072010><=
FONT=20
color=3D#0000ff size=3D2><FONT color=3D#000000 size=3D3><FONT color=3D#0000=
ff size=3D2>not=20
directly responsible for exchanging </FONT></FONT></FONT></SPAN></FONT></DI=
V>
<DIV><FONT face=3DArial><SPAN class=3D856523512-06072010><FONT color=3D#000=
0ff=20
size=3D2><FONT color=3D#000000 size=3D3><FONT color=3D#0000ff size=3D2>rout=
ing information=20
(that is the </FONT></FONT></FONT></SPAN><SPAN class=3D856523512-06072010><=
FONT=20
color=3D#0000ff size=3D2><FONT color=3D#000000 size=3D3><FONT color=3D#0000=
ff=20
size=3D2>control plane of the "router" part of an=20
</FONT></FONT></FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial><SPAN class=3D856523512-06072010><FONT color=3D#000=
0ff=20
size=3D2><FONT color=3D#000000 size=3D3><FONT color=3D#0000ff size=3D2>LSR,=
 again not=20
necessarily part </FONT></FONT></FONT></SPAN><SPAN=20
class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT color=3D#00=
0000=20
size=3D3><FONT color=3D#0000ff size=3D2>of an LSR in the general sense).&nb=
sp; This=20
</FONT></FONT></FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial><SPAN class=3D856523512-06072010><FONT color=3D#000=
0ff=20
size=3D2><FONT color=3D#000000 size=3D3><FONT color=3D#0000ff size=3D2>"rou=
ting=20
information" - if present </FONT></FONT></FONT></SPAN><SPAN=20
class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT color=3D#00=
0000=20
size=3D3><FONT color=3D#0000ff size=3D2>- is simply one source of informati=
on=20
</FONT></FONT></FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial><SPAN class=3D856523512-06072010><FONT color=3D#000=
0ff=20
size=3D2><FONT color=3D#000000 size=3D3><FONT color=3D#0000ff size=3D2>that=
 an LSR uses to=20
"program" </FONT></FONT></FONT></SPAN><SPAN class=3D856523512-06072010><FON=
T=20
color=3D#0000ff size=3D2><FONT color=3D#000000 size=3D3><FONT color=3D#0000=
ff size=3D2>(not=20
the best wording choice - I suggest </FONT></FONT></FONT></SPAN></FONT></DI=
V>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff size=3D2>"popul=
ate")=20
forwarding tables.&nbsp;</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial><FONT color=3D#000=
0ff=20
size=3D2>The LSR "control plane" provides information</FONT>&nbsp;<FONT=20
color=3D#0000ff size=3D2>in terms of label bindings</FONT></FONT></SPAN></D=
IV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>which=20
are part of the information used to populate forwarding tables=20
in</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>an=20
LSR.&nbsp; An LSR determines which label bindings to seek and=20
retain</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>based=20
on configuration and other information (such as that which may=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>be=20
provided by routing).</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>While=20
the primary intent (and common implementation) relies on use=20
of</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>the 20=20
bit label as an "index into a forwarding table", this is not the=20
only</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>way=20
that an LSR may be implemented, nor is it necessarily presumed=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>to be=20
implemented this way.&nbsp; This misconception is at the bottom of=20
a</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>number=20
of bad ideas that have been proposed in the MPLS WG (as well</FONT></SPAN><=
/DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>as=20
other places).&nbsp; How an LSR chooses to employ the 20 bit labels=20
it</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial color=3D#0000ff=20
size=3D2>assigns for use by its peers is entirely up to the=20
implementation.</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff=20
size=3D2>------------------------------------------------------------------=
---------------------------------------</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial></FONT></SPAN>&nbs=
p;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>The&nbsp;remaining=
=20
paragraphs in the section are slightly inaccurate as well.</FONT></SPAN></D=
IV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial></FONT></SPAN>&nbs=
p;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>At&nbsp;"MPLS ingr=
ess", a=20
"label stack" is prefixed.&nbsp; In the simplest case, the </FONT></SPAN></=
DIV>
<DIV><FONT face=3DArial><SPAN class=3D856523512-06072010>"label </SPAN><SPA=
N=20
class=3D856523512-06072010>stack" comprises a single label-stack=20
entry.</SPAN></FONT></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial></FONT></SPAN>&nbs=
p;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>At LSP ingress (be=
cause of=20
the possibility of nested - or hierarchical -&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>LSPs), there is th=
e=20
possibility that one or more additional label-stack</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>entries will be "p=
ushed"=20
onto the label stack&nbsp;- if there is a label stack</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>present already. O=
therwise,=20
the paragraph above applies.</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial></FONT></SPAN>&nbs=
p;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>In at least the fi=
rst case,=20
there is more to "encapsulating" the packet</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>than simply prefix=
ing an=20
MPLS label (stack).&nbsp; It is also necessary to</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>add&nbsp;the appro=
priate=20
"MPLS-specific" L2 encapsulation (including, for</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>instance, the MPLS=
=20
PID).</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial></FONT></SPAN>&nbs=
p;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial>For all "swap", "p=
op" and=20
"push" operations, one <EM><STRONG>or more</STRONG></EM> labels may=20
</FONT></SPAN></DIV>
<DIV><FONT face=3DArial><SPAN class=3D856523512-06072010>be </SPAN><SPAN=20
class=3D856523512-06072010>involved.</SPAN></FONT></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial><SPAN=20
class=3D204040315-07072010>&nbsp;</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT=20
face=3DArial>--------------------------------------------------------------=
-------------------------------------------</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff size=3D2>I beli=
eve the last=20
paragraph in section 5.2.6 (on page 12) is=20
inaccurate.</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT color=3D#0000ff size=3D2><FONT=
=20
color=3D#000000 size=3D3><FONT face=3DArial color=3D#0000ff size=3D2>A devi=
ce that=20
terminates an ATM pseudo-wire will almost certainly=20
offer</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial size=3D2>an ATM in=
terface to=20
other devices (otherwise, what is the point of using</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial size=3D2>an ATM=20
pseudowire?).&nbsp; If it does, it will necessarily have to include=20
that</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial size=3D2>interface=
 as part of=20
the ifTable.</FONT></SPAN></DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial size=3D2>In any ca=
se,=20
inclusion of the last two sentence in the last paragraph of </FONT></SPAN><=
/DIV>
<DIV><SPAN class=3D856523512-06072010><FONT face=3DArial size=3D2>section 5=
.2.6 is=20
unnecessary and those sentences&nbsp;should be removed.</FONT></SPAN><SPAN=
=20
class=3D856523512-06072010><FONT size=3D+0><FONT size=3D+0></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D+0><FONT size=3D+0><SPAN class=3D856523512-06072010><FONT=
 face=3DArial=20
size=3D2>------------------------------------------------------------------=
---------------------------------------</FONT></SPAN></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D+0><SPAN class=3D856523512-06072010><FONT face=3DArial si=
ze=3D2>In the=20
Security Considerations section, in the 3rd paragraph, you point=20
</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D+0><SPAN class=3D856523512-06072010><F=
ONT=20
size=3D2>out the potential issues </FONT></SPAN></FONT><FONT size=3D+0><SPA=
N=20
class=3D856523512-06072010><FONT size=3D2>with allowing&nbsp;write and crea=
te=20
access.&nbsp; In the </FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D+0><SPAN class=3D856523512-06072010><F=
ONT=20
size=3D2>same paragraph, you then </FONT></SPAN></FONT><FONT size=3D+0><SPA=
N=20
class=3D856523512-06072010><FONT size=3D2>go on to say "allowed to access a=
nd GET"=20
</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D+0><SPAN class=3D856523512-06072010><F=
ONT=20
size=3D2>MIB objects.&nbsp; I suggest </FONT></SPAN></FONT><FONT size=3D+0>=
<SPAN=20
class=3D856523512-06072010><FONT size=3D2>deleting "and GET" from=20
this&nbsp;paragraph.</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D856523512-06072010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D856523512-06072010>------------------------------------------------=
---------------------------------------------------------</SPAN></FONT></DI=
V>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D856523512-06072010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN class=3D856523512-06072010><SP=
AN=20
class=3D204040315-07072010>In the IANA Considerations section,=20
g</SPAN></SPAN><SPAN class=3D856523512-06072010>iven this is an overview=20
document,&nbsp;<SPAN=20
class=3D204040315-07072010>&nbsp;</SPAN></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT><FONT size=3D2><SPAN class=3D856523512-060720=
10>I think=20
you are safe in at least </SPAN></FONT></FONT><SPAN=20
class=3D856523512-06072010><FONT size=3D2>starting off with the basic "IANA=
 has=20
no&nbsp;<SPAN class=3D204040315-07072010>&nbsp;</SPAN></FONT></SPAN></FONT>=
</DIV>
<DIV><FONT><SPAN class=3D856523512-06072010><FONT face=3DArial><FONT size=
=3D2>actions"=20
text found in most IDs<SPAN=20
class=3D204040315-07072010>&nbsp;</SPAN></FONT></FONT></SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN class=3D856523512-06072010>of this type.&nbsp; =
It is=20
fairly certain that this&nbsp;<SPAN=20
class=3D204040315-07072010>&nbsp;</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT><SPAN class=3D856523512-060720=
10>will not=20
change, so you might as<SPAN=20
class=3D204040315-07072010>&nbsp;</SPAN></SPAN></FONT><SPAN=20
class=3D856523512-06072010>well get it out of the way.</SPAN></FONT></FONT>=
<FONT=20
size=3D+0></DIV><FONT size=3D2></FONT></FONT></FONT></FONT></FONT></FONT></=
SPAN>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
size=3D2>=3D=3D=3D</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D856523512-06072010><FONT face=3DA=
rial=20
size=3D2>Eric</FONT></SPAN></SPAN></FONT></FONT></FONT></SPAN></DIV></DIV><=
![if !supportAnnotations]><![endif]></BODY></HTML>

--_000_C0AC8FAB6849AB4FADACCC70A949E2F1053B72289EEUSAACMS0701e_--

From tnadeau@lucidvision.com  Thu Jul  8 12:43:29 2010
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAF6C3A68C0; Thu,  8 Jul 2010 12:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HTML_MESSAGE=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 9s1-sFINBMZQ; Thu,  8 Jul 2010 12:43:29 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by core3.amsl.com (Postfix) with ESMTP id BB38F3A685A; Thu,  8 Jul 2010 12:43:28 -0700 (PDT)
Received: from [192.168.1.133] (unknown [72.71.250.36]) by lucidvision.com (Postfix) with ESMTP id E6A095AD7BF; Thu,  8 Jul 2010 15:43:32 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-3--336698879
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <C0AC8FAB6849AB4FADACCC70A949E2F1053B72289E@EUSAACMS0701.eamcs.ericsson.se>
Date: Thu, 8 Jul 2010 15:43:31 -0400
Message-Id: <0D0FBB3D-8C67-44E6-BDCA-D757A62E43FF@lucidvision.com>
References: <C0AC8FAB6849AB4FADACCC70A949E2F1053B72289E@EUSAACMS0701.eamcs.ericsson.se>
To: Eric Gray <eric.gray@ericsson.com>
X-Mailer: Apple Mail (2.1081)
Cc: A S Kiran Koushik <kkoushik@cisco.com>, Daniel King <daneil@olddog.co.uk>, Venkatesan Mahalingam <venkatesan.mahalingam@aricent.com>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] MPLS-TP management overview draft - draft-farrel-mpls-tp-mib-management-overview
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2010 19:43:30 -0000

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


	Why are we including GMPLS-related MIBs in this?  I'd like to =
not confuse the fact that the basic version of TP is supposed to be =
static, and handled (managed) as such. If you do talk about GMPLS MIBs =
in there, then I'd like to be very clear that it is optional.

	--Tom


> Authors,=20
> =20
>     Some comments on your draft...
> =20
>     As a general comment, in addition to the MIBs already explicitly =
referenced in this draft, you should probably =20
> include:
> =20
> o RFC 4801 ( "Definitions of Textual Conventions for Generalized =
Multiprotocol Label Switching (GMPLS) Management " ),
> o RFC 4802 ("Generalized Multiprotocol Label Switching (GMPLS) Traffic =
Engineering Management Information Base"),
> o RFC 4220 ("Traffic Engineering Link Management Information Base");
> =20
> As is, there is a curious dearth of MIB references for GMPLS related =
MIBs, given GMPLS will be the signaling
> method used for MPLS-TP LSPs.=20
> =20
>   =20

--Apple-Mail-3--336698879
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><base href=3D"x-msg://26/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><br></div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Why are we including =
GMPLS-related MIBs in this? &nbsp;I'd like to not confuse the fact that =
the basic version of TP is supposed to be static, and handled (managed) =
as such. If you do talk about GMPLS MIBs in there, then I'd like to be =
very clear that it is optional.<div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>--Tom</div><div><br><div><div><br></div><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-GB" vlink=3D"purple" link=3D"blue"><div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial"><font color=3D"#0000ff"><font =
size=3D"2"><span class=3D"204040315-07072010">Authors</span><span =
class=3D"037432012-06072010">,<span =
class=3D"204040315-07072010">&nbsp;</span></span></font></font></font></di=
v><div dir=3D"ltr" align=3D"left"><font face=3D"Arial"><font =
color=3D"#0000ff"><font size=3D"2"><span =
class=3D"037432012-06072010"><span =
class=3D"204040315-07072010"></span></span></font></font></font>&nbsp;</di=
v><div dir=3D"ltr" align=3D"left"><font face=3D"Arial"><font =
color=3D"#0000ff"><font size=3D"2"><span =
class=3D"037432012-06072010"><span =
class=3D"204040315-07072010">&nbsp;&nbsp;&nbsp;&nbsp;Some comments on =
your draft...</span></span></font></font></font></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"037432012-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"037432012-06072010">&nbsp;&nbsp;&nbsp;<font =
face=3D"Arial"><font color=3D"#0000ff"><font size=3D"2"><span =
class=3D"204040315-07072010">&nbsp;As a&nbsp;general comment, i</span>n =
addition to the MIBs already explicitly referenced in this draft, you =
should probably&nbsp;<span =
class=3D"204040315-07072010">&nbsp;</span></font></font></font></span></di=
v><div dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font=
 face=3D"Arial" color=3D"#0000ff" =
size=3D"2">include:</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"037432012-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"037432012-06072010"><font =
face=3D"Arial"><font color=3D"#0000ff"><font size=3D"2">o RFC 4801 =
(<span class=3D"204040315-07072010">&nbsp;"</span><font face=3D"Times =
New Roman">Definitions of Textual Conventions for Generalized =
Multiprotocol Label Switching (GMPLS) Management</font><font =
face=3D"Arial"><span class=3D"204040315-07072010">&nbsp;<font =
face=3D"Times New =
Roman">"</font>&nbsp;</span>),</font></font></font></font></span></div><di=
v dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font =
face=3D"Arial"><font color=3D"#0000ff"><font size=3D"2">o RFC 4802 =
(<span class=3D"204040315-07072010">"</span><font face=3D"Times New =
Roman">Generalized Multiprotocol Label Switching (GMPLS) Traffic =
Engineering Management Information Base</font><font face=3D"Arial"><span =
class=3D"204040315-07072010"><font face=3D"Times New =
Roman">"</font></span>),</font></font></font></font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font =
face=3D"Arial"><font color=3D"#0000ff"><font size=3D"2">o RFC 4220 =
(<span class=3D"204040315-07072010">"</span><font face=3D"Times New =
Roman">Traffic Engineering Link Management Information Base</font><font =
face=3D"Arial"><span class=3D"204040315-07072010"><font face=3D"Times =
New =
Roman">"</font></span>);</font></font></font></font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div=
 dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">As is, there is a curious =
dearth of MIB references for GMPLS related MIBs, given GMPLS will be the =
signaling</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"037432012-06072010"><font face=3D"Arial"><font =
color=3D"#0000ff"><font size=3D"2">method used for MPLS-TP LSPs.<span =
class=3D"204040315-07072010">&nbsp;</span></font></font></font></span></di=
v><div dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font=
 face=3D"Arial"><font color=3D"#0000ff"><font size=3D"2"><span =
class=3D"204040315-07072010"></span></font></font></font></span>&nbsp;</di=
v><div dir=3D"ltr" align=3D"left"><span =
class=3D"037432012-06072010"><font><font color=3D"#0000ff"><font =
size=3D"2"><span class=3D"204040315-07072010"><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial">&nbsp;&nbsp;&nbsp;</font></span></div></span></font></font>=
</font></span></div></div></span></blockquote></div></div></body></html>=

--Apple-Mail-3--336698879--

From nitinb@juniper.net  Thu Jul  8 12:45:22 2010
Return-Path: <nitinb@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD84B3A67D4; Thu,  8 Jul 2010 12:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gvUsWm8MzUT; Thu,  8 Jul 2010 12:45:21 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by core3.amsl.com (Postfix) with ESMTP id 62DA53A68A3; Thu,  8 Jul 2010 12:45:21 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKTDYqzoAGbNNwnDzSBb1FVkP2i5x7htPw@postini.com; Thu, 08 Jul 2010 12:45:26 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Thu, 8 Jul 2010 12:39:56 -0700
From: Nitin Bahadur <nitinb@juniper.net>
To: "hhelvoort@chello.nl" <hhelvoort@chello.nl>, Loa Andersson <loa@pi.nu>
Date: Thu, 8 Jul 2010 12:39:53 -0700
Thread-Topic: [mpls] [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
Thread-Index: AcscOQXgTOdlFbQaQ5G9X2cMvBZ4zQCnFAhj
Message-ID: <C85B7799.12744%nitinb@juniper.net>
In-Reply-To: <4C31C837.7020601@chello.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.4.0.100208
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2010 19:45:22 -0000

Hi Hubb,

On 7/5/10 4:55 AM, "Huub van Helvoort" <hhelvoort@chello.nl> wrote:

> No/do not support
>=20
> The change of the name of this draft gives the impression
> that the content of the draft changed as well.
> So before it can be adopted the text has to be aligned
> with the title: On-demand CV for MPLS-TP.
>=20
> I see that it is still focused on extending LSP-Ping but
> not for use in a transport environment.
> It does not indicate where the transport OAM requirements
> are met.

The authors will clarify that in the next revision. As you and others have
pointed out, the text is more centered today around the solution (lsp-ping)=
,
rather than the how the requirement is met.

> It does not indicate how the ACh is used.

Section 3.2 alludes to it. I will update that section to have a pointer to
the first normative reference.

> What is the meaning of "adjacency" in the context of MPLS-TP?

Adjacency came from -01 version of mpls-tp-oam-requirements draft. Currentl=
y
there is no adjacency requirement, so we'll get rid of the term of this
draft as well.

> It does not document how this tool can be used in transport
> environment where tools are enabled/disabled static (compared
> to the dynamic set-up of LSP-ping.

LSP-Ping is indeed dynamic in the request/response sense. However, the LSP
by itself can be setup statically or using RSVP-TE. If it is setup
statically, then section 2.4 applies. Can you clarify your comment.

Thanks
Nitin

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> On 21-06-10 14:07, Loa Andersson wrote:
>>=20
>> Working Group,
>>=20
>> this email is to start poll to adopt
>> draft-nitinb-mpls-tp-on-demand-cv-00.txt
>> as an MPLS working group draft.
>>=20
>> After recent experience, the chairs would like to remind you all
>> what it means to conduct a poll to adopt a draft as a working group
>> draft.
>>=20
>> - Please recall that the IETF does not "vote." Polls of a working
>> group are to gather information to help the chairs make their
>> decisions. Voting is not part of the normal working methods of
>> an IETF working group.
>>=20
>> - The "rough consensus" process used in the working group assumes
>> that people expressing opinions are also participating in the
>> development of standards documents.
>>=20
>> - Subscription to the list specifically to express an opinion is
>> noticed by the chairs who has access to information on the new list
>> members. Such behavior is not part of the normal working methods.
>>=20
>> - The purpose of a poll for adoption is to help the chairs understand
>> the level of support for a document (i.e. who has read it, who
>> believes it is a good starting point for working group work, who
>> will contribute to the work) and whether there are any significant
>> technical issues. Statements of objection must be backed up by
>> proper technical reasons.
>>=20
>> So please respond to this poll indicating whether you support the
>> adoption of this draft or stating your technical issues.
>>=20
>> Please also not that this draft has after a discussion with the
>> working group chairs been renamed, it was earlier know as
>> draft-nitinb-mpls-tp-lsp-ping-extensions-01.
>>=20
>> This poll ends eob July 5.
>>=20
>>=20
>> Loa and George
>> mpls wg co-chairs
>>=20


From nitinb@juniper.net  Thu Jul  8 12:47:55 2010
Return-Path: <nitinb@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97CB43A6B5A; Thu,  8 Jul 2010 12:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P4RYJkDkJFVG; Thu,  8 Jul 2010 12:47:54 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id 9D0553A6907; Thu,  8 Jul 2010 12:47:53 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKTDYraDJmIveCOgucwUUuTI89nYvQVg7p@postini.com; Thu, 08 Jul 2010 12:47:58 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Thu, 8 Jul 2010 12:17:41 -0700
From: Nitin Bahadur <nitinb@juniper.net>
To: Zhang Haiyan <zhanghaiyan@huawei.com>, Loa Andersson <loa@pi.nu>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Date: Thu, 8 Jul 2010 12:17:39 -0700
Thread-Topic: [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
Thread-Index: AcsZiXdjlKOm3gv1QlKpPJpZ/bBWzgFSMN+8
Message-ID: <C85B7263.12736%nitinb@juniper.net>
In-Reply-To: <064b01cb1989$6dc2fba0$774d460a@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.4.0.100208
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mpls] [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2010 19:47:55 -0000

Hi Haiyan,

On 7/1/10 6:53 PM, "Zhang Haiyan" <zhanghaiyan@huawei.com> wrote:

> No/ do not support.
>=20
> Several comments need clarification:
>=20
> 1) We do not see how the content of the draft satisfies "on-demand-cv" as
> claimed in the title. We only see "LSP-Ping" and "LSP Traceroute" in the =
main
> part of the draft.

> In the introduction part we also see the "on-demand Connectivity Verifica=
tion,
> Route Tracing and Adjacency functions".
> Could the authors clarify the "on-demand CV"?

I agree that the text needs a little working to make it clear how on-demand
CV, Route tracing and Adjaceny are achieved. The current text is based
around the solution (lsp-ping), rather than the requirement (cv,
route-tracing). The authors will fix this in the next revision.
=20
> 2) Could the authors clarify the purpose of describing "LSP-Ping with IP
> encapsulation" and "LSP Traceroute with IP encapsulation"?

Thanks for asking. As per Section 2.1.4 of RFC 5860

" It MUST be possible to deploy the OAM functionality in any of these
   environments.  As a result, it MUST be possible to operate OAM
   functions with or without relying on IP capabilities, and it MUST be
   possible to choose to make use of IP capabilities when these are
   present."

To ensure that the above requirement was met, we added the sections on
LSP-ping with IP encap.

> The draft seems to be just a regular extension of MPLS LSP ping, not
> particular for MPLS-TP. Shouldn't it be a draft with the name
> "mpls-lsp-ping-extensions"?

Godo question. It is true that the extensions apply equally well to regular
MPLS LSPs. As per the MPLS-TP Joint Working Team guidelines, all drafts tha=
t
address mpls-tp requirement/solutions should have a mpls-tp name (for
simplicity for IETF WG chairs and their ITU counter-parts).
=20
Hope that helps.
Nitin
=20
> ----- Original Message -----
> From: "Loa Andersson" <loa@pi.nu>
> To: <mpls-tp@ietf.org>; <mpls@ietf.org>; "MPLS-TP ad hoc team"
> <ahmpls-tp@lists.itu.int>
> Sent: Monday, June 21, 2010 8:07 PM
> Subject: [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a
> working group document
>=20
>=20
>>=20
>> Working Group,
>>=20
>> this email is to start poll to adopt
>> draft-nitinb-mpls-tp-on-demand-cv-00.txt
>> as an MPLS working group draft.
>>=20
>> After recent experience, the chairs would like to remind you all
>> what it means to conduct a poll to adopt a draft as a working group
>> draft.
>>=20
>> - Please recall that the IETF does not "vote." Polls of a working
>>   group are to gather information to help the chairs make their
>>   decisions. Voting is not part of the normal working methods of
>>   an IETF working group.
>>=20
>> - The "rough consensus" process used in the working group assumes
>>   that people expressing opinions are also participating in the
>>   development of standards documents.
>>=20
>> - Subscription to the list specifically to express an opinion is
>>   noticed by the chairs who has access to information on the new list
>>   members. Such behavior is not part of the normal working methods.
>>=20
>> - The purpose of a poll for adoption is to help the chairs understand
>>   the level of support for a document (i.e. who has read it, who
>>   believes it is a good starting point for working group work, who
>>   will contribute to the work) and whether there are any significant
>>   technical issues. Statements of objection must be backed up by
>>   proper technical reasons.
>>=20
>> So please respond to this poll indicating whether you support the
>> adoption of this draft or stating your technical issues.
>>=20
>> Please also not that this draft has after a discussion with the
>> working group chairs been renamed, it was earlier know as
>> draft-nitinb-mpls-tp-lsp-ping-extensions-01.
>>=20
>> This poll ends eob July 5.
>>=20
>>=20
>> Loa and George
>> mpls wg co-chairs
>>=20
>> --=20
>>=20
>>=20
>> Loa Andersson                         email: loa.andersson@ericsson.com
>> Sr Strategy and Standards Manager            loa@pi.nu
>> Ericsson Inc                          phone: +46 10 717 52 13
>>                                              +46 767 72 92 13
>> _______________________________________________
>> mpls-tp mailing list
>> mpls-tp@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls-tp
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


From nitinb@juniper.net  Thu Jul  8 12:50:16 2010
Return-Path: <nitinb@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D26EB3A684C; Thu,  8 Jul 2010 12:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57vzcTh7ED9r; Thu,  8 Jul 2010 12:50:14 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by core3.amsl.com (Postfix) with ESMTP id 054853A6830; Thu,  8 Jul 2010 12:50:03 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKTDYr7EcV9JlrK7pTWAoTjg4r9EhEuT8E@postini.com; Thu, 08 Jul 2010 12:50:19 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Thu, 8 Jul 2010 12:48:52 -0700
From: Nitin Bahadur <nitinb@juniper.net>
To: Lavanya Srivatsa <lavanya.srivatsa@aricent.com>, MPLS TP <mpls-tp@ietf.org>, Loa Andersson <loa@pi.nu>
Date: Thu, 8 Jul 2010 12:48:49 -0700
Thread-Topic: [mpls-tp] [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
Thread-Index: AcscPcK0uiKqVsQRQCSiVMrEbZSWCwAAJksrAKYOZxQ=
Message-ID: <C85B79B1.1274E%nitinb@juniper.net>
In-Reply-To: <AF085525D89CCA4EB233BE7E5BF2FDAB1693A750CA@GUREXMB02.ASIAN.AD.ARICENT.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.4.0.100208
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ahmpls-tp@lists.itu.int" <ahmpls-tp@lists.itu.int>
Subject: Re: [mpls] [mpls-tp] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2010 19:50:16 -0000

Hi Lavanya,

On 7/5/10 5:52 AM, "Lavanya Srivatsa" <lavanya.srivatsa@aricent.com> wrote:

> Yes / Support.
>=20
> However, I have some comments/queries that I would request be updated in =
the
> next version (if the authors
> agree with my comments, of course!).
>=20
> (1)  In Section 2.2, it states "When sending LSP-Ping packets using ACH,
> without IP encapsulation,
>    there MAY be a need to identify the source address of the packet.
>    This source address will be specified via the Source Address TLV,
>    being defined in [I-D.ietf-mpls-tp-ach-tlv]"
> [LS] The ACH TLV draft has Source Address only in
> the IP format and not in the non-IP format as per mpls-tp-identifiers dra=
ft.

New address types for src-addr tlv is not in the purview of this draft.
=20
> (2) Section 2.3 states - "Only one identifier (MEP or MIP) MUST be presen=
t in
> a packet."
> [LS] Would there not be a scenario that a Source MEP and a Destination MI=
P
> might need=20
> to be carried in the packet for connectivity verification to
> intermediate/transit nodes?
> I agree that source MEP/source MIP and destination MEP/destination MIP ar=
e
> invalid combinations
> but Source MEP/Destination MIP seems a "possible" combination?

I'm not sure. I am willing to change this if others on the wg mailing list
think so as well.

> (3) Section 3.3 states that the Egress Node may add the Target FEC Stack =
TLV
> in its echo responses.
> [LS] How will the egress node know when to do so? Is it expected/mandated=
 that
> the echo request=20
> should have an newly defined bit set in the Global Flags field to indicat=
e
> that the response should
> contain a Target FEC stack? If so, then I think that this draft needs to
> explain this modification on
> the base rfc 4379.

This section needs some work. Next revision :-)

> On the same lines, would it also be recommended that the echo response
> contains the V bit
> set in the Global Flags to indicate that the ingress must validate the re=
verse
> FEC?

Yes, I will add some text to indicate that V flag can be set in the reverse
direction as well.
=20
> - Lavanya
>=20
>=20
> ---------- Forwarded message ----------
> From: Loa Andersson <loa@pi.nu<mailto:loa@pi.nu>>
> Date: Mon, Jun 21, 2010 at 5:37 PM
> Subject: [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a work=
ing
> group document
> To: "mpls-tp@ietf.org<mailto:mpls-tp@ietf.org>"
> <mpls-tp@ietf.org<mailto:mpls-tp@ietf.org>>,
> mpls@ietf.org<mailto:mpls@ietf.org>, MPLS-TP ad hoc team
> <ahmpls-tp@lists.itu.int<mailto:ahmpls-tp@lists.itu.int>>
>=20
>=20
>=20
> Working Group,
>=20
> this email is to start poll to adopt
> draft-nitinb-mpls-tp-on-demand-cv-00.txt
> as an MPLS working group draft.
>=20
> After recent experience, the chairs would like to remind you all
> what it means to conduct a poll to adopt a draft as a working group
> draft.
>=20
> - Please recall that the IETF does not "vote." Polls of a working
>  group are to gather information to help the chairs make their
>  decisions. Voting is not part of the normal working methods of
>  an IETF working group.
>=20
> - The "rough consensus" process used in the working group assumes
>  that people expressing opinions are also participating in the
>  development of standards documents.
>=20
> - Subscription to the list specifically to express an opinion is
>  noticed by the chairs who has access to information on the new list
>  members. Such behavior is not part of the normal working methods.
>=20
> - The purpose of a poll for adoption is to help the chairs understand
>  the level of support for a document (i.e. who has read it, who
>  believes it is a good starting point for working group work, who
>  will contribute to the work) and whether there are any significant
>  technical issues. Statements of objection must be backed up by
>  proper technical reasons.
>=20
> So please respond to this poll indicating whether you support the adoptio=
n of
> this draft or stating your technical issues.
>=20
> Please also not that this draft has after a discussion with the
> working group chairs been renamed, it was earlier know as
> draft-nitinb-mpls-tp-lsp-ping-extensions-01.
>=20
> This poll ends eob July 5.
>=20
>=20
> Loa and George
> mpls wg co-chairs
>=20
> --
>=20
>=20
> Loa Andersson                         email:
> loa.andersson@ericsson.com<mailto:loa.andersson@ericsson.com>
> Sr Strategy and Standards Manager            loa@pi.nu<mailto:loa@pi.nu>
> Ericsson Inc                          phone: +46 10 717 52 13
>                                             +46 767 72 92 13
> _______________________________________________
> mpls mailing list
> mpls@ietf.org<mailto:mpls@ietf.org>
> https://www.ietf.org/mailman/listinfo/mpls
>=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


From lucyyong@huawei.com  Thu Jul  8 15:15:22 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D9533A6968; Thu,  8 Jul 2010 15:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 tMKIenCuDihh; Thu,  8 Jul 2010 15:15:18 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 9717C3A6948; Thu,  8 Jul 2010 15:15:17 -0700 (PDT)
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 <0L5900L4ZF5BBC@szxga04-in.huawei.com>; Fri, 09 Jul 2010 06:15:11 +0800 (CST)
Received: from 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 <0L59004FHF5BGK@szxga04-in.huawei.com>; Fri, 09 Jul 2010 06:15:11 +0800 (CST)
Received: from y736742 ([10.124.12.56]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5900HI9F58IJ@szxml04-in.huawei.com>; Fri, 09 Jul 2010 06:15:11 +0800 (CST)
Date: Thu, 08 Jul 2010 17:15:08 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <5E893DB832F57341992548CDBB3331639843877BA7@EMBX01-HQ.jnpr.net>
To: 'John E Drake' <jdrake@juniper.net>, curtis@occnc.com, stbryant@cisco.com
Message-id: <00fb01cb1eeb$08036860$380c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsdICeLrK/RZfGiTIyQXS2B8tj2VgABXQWwAG+wX9A=
References: "Your message of Mon, 05 Jul 2010 15:07:21 BST." <4C31E719.1060402@cisco.com> <201007061530.o66FU4Q6007184@harbor.orleans.occnc.com> <5E893DB832F57341992548CDBB3331639843877BA7@EMBX01-HQ.jnpr.net>
Cc: draft-ietf-pwe3-fat-pw@tools.ietf.org, mpls@ietf.org, 'pwe3' <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] Multiple RSVP paths
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2010 22:15:22 -0000

Hi John,

It is not clear to me 

1) how the proposed solution works in Figure 1 situation of the draft. Even
the receiver B assigns the same label for all five sub-LSPs, because there
are intermediate nodes between A and B, the sender A will be asked to use
the different labels for five sub-LSPs, is that right?  

2) For the following MLSP case, do sub-LSPs start from node A or from node
W?

                                        
                           --L--   --P-- 
                          /     \ /     \
                  A------W       S---Q---B
                          \     / \     /
                           --M--   --R-- 

Thanks,
Lucy



> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> John E Drake
> Sent: Tuesday, July 06, 2010 11:11 AM
> To: curtis@occnc.com; stbryant@cisco.com
> Cc: draft-ietf-pwe3-fat-pw@tools.ietf.org; mpls@ietf.org; pwe3
> Subject: Re: [mpls] [PWE3] Multiple RSVP paths
> 
> Hi,
> 
> A related ID:
> 
> http://www.ietf.org/id/draft-kompella-mpls-rsvp-ecmp-00.txt
> 
> Thanks,
> 
> John
> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> > Curtis Villamizar
> > Sent: Tuesday, July 06, 2010 8:30 AM
> > To: stbryant@cisco.com
> > Cc: draft-ietf-pwe3-fat-pw@tools.ietf.org; pwe3
> > Subject: Re: [PWE3] Multiple RSVP paths
> >
> >
> > In message <4C31E719.1060402@cisco.com>
> > Stewart Bryant writes:
> > >
> > > In response to a comment received during last call I have added a new
> > > section 7.3 entitled : "Multiple RSVP-TE Paths" which says:
> > >
> > > In some networks it is desirable for a Label Edge Router (LER) to be
> > > able to load balance a PW across multiple RSVP-TE tunnels. The flow
> > > label mechanism described in this document may be used to provide the
> > > LER with the required flow information, and necessary entropy to
> provide
> > > this type of load balancing. Methods by which the LER is configured to
> > > apply this type of ECMP is outside the scope of this document.
> > >
> > > - Stewart
> >
> >
> > Stewart,
> >
> > You could mention using a link bundle with the all ones component
> > link as a possibility but still leave further details out of scope and
> > not preclude other mechanisms that are local to the LER.
> >
> > Curtis
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From wwwrun@rfc-editor.org  Fri Jul  9 16:27:22 2010
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 45EE43A6830; Fri,  9 Jul 2010 16:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[AWL=0.604,  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 4sACgcLDjXsn; Fri,  9 Jul 2010 16:27:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 3FD0F3A65A6; Fri,  9 Jul 2010 16:27:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E0EE4E0698; Fri,  9 Jul 2010 16:27:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100709232726.E0EE4E0698@rfc-editor.org>
Date: Fri,  9 Jul 2010 16:27:26 -0700 (PDT)
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 5920 on Security Framework for MPLS and GMPLS Networks
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jul 2010 23:27:22 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5920

        Title:      Security Framework for MPLS and 
                    GMPLS Networks 
        Author:     L. Fang, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       July 2010
        Mailbox:    lufang@cisco.com
        Pages:      66
        Characters: 152830
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-mpls-and-gmpls-security-framework-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5920.txt

This document provides a security framework for Multiprotocol Label
Switching (MPLS) and Generalized Multiprotocol Label Switching
(GMPLS) Networks.  This document addresses the security aspects that
are relevant in the context of MPLS and GMPLS.  It describes the
security threats, the related defensive techniques, and the
mechanisms for detection and reporting.  This document emphasizes
RSVP-TE and LDP security considerations, as well as inter-AS and
inter-provider security considerations for building and maintaining
MPLS and GMPLS networks across different domains or different
Service Providers.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From wwwrun@rfc-editor.org  Fri Jul  9 16:27:33 2010
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FEB93A6947; Fri,  9 Jul 2010 16:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[AWL=0.402,  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 MZMe4V6tF18I; Fri,  9 Jul 2010 16:27:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 5BE513A6944; Fri,  9 Jul 2010 16:27:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 201BAE06B8; Fri,  9 Jul 2010 16:27:38 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100709232738.201BAE06B8@rfc-editor.org>
Date: Fri,  9 Jul 2010 16:27:38 -0700 (PDT)
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 5921 on A Framework for MPLS in Transport Networks
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jul 2010 23:27:33 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5921

        Title:      A Framework for MPLS in 
                    Transport Networks 
        Author:     M. Bocci, Ed.,
                    S. Bryant, Ed.,
                    D. Frost, Ed.,
                    L. Levrau, L. Berger
        Status:     Informational
        Stream:     IETF
        Date:       July 2010
        Mailbox:    matthew.bocci@alcatel-lucent.com, 
                    stbryant@cisco.com, 
                    danfrost@cisco.com, lieven.levrau@alcatel-lucent.com, 
                    lberger@labn.net
        Pages:      56
        Characters: 129318
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-tp-framework-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5921.txt

This document specifies an architectural framework for the
application of Multiprotocol Label Switching (MPLS) to the
construction of packet-switched transport networks.  It describes a
common set of protocol functions -- the MPLS Transport Profile
(MPLS-TP) -- that supports the operational models and capabilities
typical of such networks, including signaled or explicitly
provisioned bidirectional connection-oriented paths, protection and
restoration mechanisms, comprehensive Operations, Administration, and
Maintenance (OAM) functions, and network operation in the absence of
a dynamic control plane or IP forwarding support.  Some of these
functions are defined in existing MPLS specifications, while others
require extensions to existing specifications to meet the
requirements of the MPLS-TP.

This document defines the subset of the MPLS-TP applicable in general
and to point-to-point transport paths.  The remaining subset,
applicable specifically to point-to-multipoint transport paths, is
outside the scope of this document.

This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
(PWE3) architectures to support the capabilities and functionalities
of a packet transport network as defined by the ITU-T.  This document 
is not an Internet Standards Track specification; it is published for 
informational purposes.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From tnadeau@lucidvision.com  Thu Jul  8 12:42:14 2010
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A04F3A68A3; Thu,  8 Jul 2010 12:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6]
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 pD43duYnX4iV; Thu,  8 Jul 2010 12:42:12 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by core3.amsl.com (Postfix) with ESMTP id DA7063A68C0; Thu,  8 Jul 2010 12:42:11 -0700 (PDT)
Received: from [192.168.1.133] (unknown [72.71.250.36]) by lucidvision.com (Postfix) with ESMTP id 9A13B5AD784; Thu,  8 Jul 2010 15:42:15 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-2--336776210
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <C0AC8FAB6849AB4FADACCC70A949E2F1053B72289E@EUSAACMS0701.eamcs.ericsson.se>
Date: Thu, 8 Jul 2010 15:42:14 -0400
Message-Id: <829184DB-D53C-4B1A-9BDD-3C4762EBF978@lucidvision.com>
References: <C0AC8FAB6849AB4FADACCC70A949E2F1053B72289E@EUSAACMS0701.eamcs.ericsson.se>
To: Eric Gray <eric.gray@ericsson.com>
X-Mailer: Apple Mail (2.1081)
X-Mailman-Approved-At: Sat, 10 Jul 2010 18:14:09 -0700
Cc: A S Kiran Koushik <kkoushik@cisco.com>, Daniel King <daneil@olddog.co.uk>, Venkatesan Mahalingam <venkatesan.mahalingam@aricent.com>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] MPLS-TP management overview draft - draft-farrel-mpls-tp-mib-management-overview
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2010 19:42:14 -0000

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


	Why are we including GMPLS-related MIBs in this?  I'd like to =
not confuse the fact that the basic version of TP is supposed to be =
static, and handled (managed) as such. If you do talk about GMPLS MIBs =
in there, then I'd like to be very clear that it is optional.

	--Tom


> Authors,=20
> =20
>     Some comments on your draft...
> =20
>     As a general comment, in addition to the MIBs already explicitly =
referenced in this draft, you should probably =20
> include:
> =20
> o RFC 4801 ( "Definitions of Textual Conventions for Generalized =
Multiprotocol Label Switching (GMPLS) Management " ),
> o RFC 4802 ("Generalized Multiprotocol Label Switching (GMPLS) Traffic =
Engineering Management Information Base"),
> o RFC 4220 ("Traffic Engineering Link Management Information Base");
> =20
> As is, there is a curious dearth of MIB references for GMPLS related =
MIBs, given GMPLS will be the signaling
> method used for MPLS-TP LSPs.=20
> =20
>     NITs:
>     =3D=3D=3D
> =20
> "functionss" is usually spelled with one "s" (page 7)
> =20
> "exchaging" usually includes another "n" (page 7)
> =20
> "MPLS packets are encapsulated by using its own header" doesn't
> parse (page 7).  The second sentence in the same paragraph is just
> barely more readable.  I would suggest re-writing the paragraph using
> the phrase "label-stack" to replace "header."  This also eliminates =
the
> need to identify the "header" as a "label-stack."
> =20
> "path(" needs a space (page 8).
> =20
> Change "The two important .." to "Two important ..." (page 8).  The
> "two important applications" should be in bullet format.
> =20
> "a MPLS" should be "an MPLS" anywhere that the indefinite article is
> used in conjunction with "MPLS."
> =20
> In the 5th paragraph on page 10, to what does "The document" refer?
> =20
> Page 11 contains a number of examples where the first word following
> a colon (":") is capitalized; this is not proper English - =
particularly when
> the text following the colon is not in the form of a bulleted list.  I =
did not
> check the entire draft for this, but suggest the authors should.
> =20
> In the 2nd sentence, 7th paragraph of page 11, to what does "This MIB
> module" refer?
> =20
> The 2nd sentence in section 5.2.9 (top of page 13) does not parse.  I
> suggest breaking this sentence down and clarifying what is meant by =
it.
> =20
> The 2nd paragraph in section 5.2.10 (page 13) does not completely
> describe the notation used.  An arrow indicates a dependency between
> two MIB modules, but is clearly a directed dependency and meaning
> is not clear: I suggest using a more illustrative example by making =
the
> following change:
> =20
> Change -
> A relationship "MIB module A depends on MIB module B" means that
> MIB module A uses an object, object identifier, or textual convention
> defined in MIB module B, or that MIB module A contains a pointer
> (index or RowPointer) to an object in MIB module B.
> To -
> The relationship "A --> B" means A depends on B and that MIB module
> A uses an object, object identifier, or textual convention defined in =
MIB
> module B, or that MIB module A contains a pointer (index or =
RowPointer)
> to an object in MIB module B.
> (Note that I am assumng I have the order of dependency correct, based
> on conventional "logical dependency" - I did not verify this be =
analyzing
> the diagram on page 14)
> =20
> I suggest restructuring the last paragraph on page 16 (continuing on =
to
> page 17) as two paragraphs, each including bulleted lists, as follows:
> =20
> "The following MPLS-TP OAM functionalities can be achieved using the
>  MPLSTP-OAM-STD-MIB mib extensions:
> =20
>     o    Continuity Check and Connectivity Verification,
>     o    Alarm Reporting, Diagnostic,
>     o    Route Tracing,
>     o    Loopback tool,
>     o    Lock Instruct,
>     o    Lock Reporting Remote Defect Indication,
>     o    Client Failure Indication,
>     o    Packet Loss Measurement and
>     o    Packet Delay Measurement
> =20
> "MPLS-TP OAM managed objects are defined based on the drafts:
>     o    draft-ietf-mpls-tp-oam-requirements-06,=20
>     o    draft-ietf-mpls-tp-oam-framework-06 and=20
>     o    draft-ietf-mpls-tp-identifiers-01."
> =20
> The last paragraph on page 17 (continuing on to page 18) has the same
> problem as the 2nd paragraph on page 13 (described above) and needs
> a similar resolution.  One approach might be to include this as part =
of a
> new section (under modified section 2 "Conventions and Terminology"),
> so that it does not need to be repeated.
> =20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> =20
>     Not so NITty:
>     =3D=3D=3D=3D=3D=3D=3D=3D=3D
> =20
> There are several problems with this paragraph (page 7):
> =20
> "The basic unit in an MPLS network is called LSR(Label switched
>   router). It implements the control and forwarding plane of MPLS."
> =20
> o    as a NIT, "LSR(" needs a space;
> o    the meaning of "basic unit" is not at all clear;
> o    an LSR does not necessarily implement a control plane.
> =
--------------------------------------------------------------------------=
-------------------------------
> =20
> The next paragraph is also inaccurate  (also page 7) .
> =20
> The control plane of an LSR is not directly responsible for exchanging
> routing information (that is the control plane of the "router" part of =
an
> LSR, again not necessarily part of an LSR in the general sense).  This
> "routing information" - if present - is simply one source of =
information
> that an LSR uses to "program" (not the best wording choice - I suggest
> "populate") forwarding tables.=20
> =20
> The LSR "control plane" provides information in terms of label =
bindings
> which are part of the information used to populate forwarding tables =
in
> an LSR.  An LSR determines which label bindings to seek and retain
> based on configuration and other information (such as that which may
> be provided by routing).
> =20
> While the primary intent (and common implementation) relies on use of
> the 20 bit label as an "index into a forwarding table", this is not =
the only
> way that an LSR may be implemented, nor is it necessarily presumed
> to be implemented this way.  This misconception is at the bottom of a
> number of bad ideas that have been proposed in the MPLS WG (as well
> as other places).  How an LSR chooses to employ the 20 bit labels it
> assigns for use by its peers is entirely up to the implementation.
> =20
> =
--------------------------------------------------------------------------=
-------------------------------
> =20
> The remaining paragraphs in the section are slightly inaccurate as =
well.
> =20
> At "MPLS ingress", a "label stack" is prefixed.  In the simplest case, =
the
> "label stack" comprises a single label-stack entry.
> =20
> At LSP ingress (because of the possibility of nested - or hierarchical =
-=20
> LSPs), there is the possibility that one or more additional =
label-stack
> entries will be "pushed" onto the label stack - if there is a label =
stack
> present already. Otherwise, the paragraph above applies.
> =20
> In at least the first case, there is more to "encapsulating" the =
packet
> than simply prefixing an MPLS label (stack).  It is also necessary to
> add the appropriate "MPLS-specific" L2 encapsulation (including, for
> instance, the MPLS PID).
> =20
> For all "swap", "pop" and "push" operations, one or more labels may
> be involved.
> =20
> =
--------------------------------------------------------------------------=
-------------------------------
> =20
> I believe the last paragraph in section 5.2.6 (on page 12) is =
inaccurate.
> A device that terminates an ATM pseudo-wire will almost certainly =
offer
> an ATM interface to other devices (otherwise, what is the point of =
using
> an ATM pseudowire?).  If it does, it will necessarily have to include =
that
> interface as part of the ifTable.
> =20
> In any case, inclusion of the last two sentence in the last paragraph =
of
> section 5.2.6 is unnecessary and those sentences should be removed.
> =20
> =
--------------------------------------------------------------------------=
-------------------------------
> =20
> In the Security Considerations section, in the 3rd paragraph, you =
point
> out the potential issues with allowing write and create access.  In =
the
> same paragraph, you then go on to say "allowed to access and GET"
> MIB objects.  I suggest deleting "and GET" from this paragraph.
> =20
> =
--------------------------------------------------------------------------=
-------------------------------
> =20
> In the IANA Considerations section, given this is an overview =
document, =20
> I think you are safe in at least starting off with the basic "IANA has =
no =20
> actions" text found in most IDs of this type.  It is fairly certain =
that this =20
> will not change, so you might as well get it out of the way.
> =20
> =3D=3D=3D
> Eric
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


--Apple-Mail-2--336776210
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><base href=3D"x-msg://26/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><br></div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Why are we including =
GMPLS-related MIBs in this? &nbsp;I'd like to not confuse the fact that =
the basic version of TP is supposed to be static, and handled (managed) =
as such. If you do talk about GMPLS MIBs in there, then I'd like to be =
very clear that it is optional.<div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>--Tom</div><div><br><div><div><br></div><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-GB" vlink=3D"purple" link=3D"blue"><div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial"><font color=3D"#0000ff"><font =
size=3D"2"><span class=3D"204040315-07072010">Authors</span><span =
class=3D"037432012-06072010">,<span =
class=3D"204040315-07072010">&nbsp;</span></span></font></font></font></di=
v><div dir=3D"ltr" align=3D"left"><font face=3D"Arial"><font =
color=3D"#0000ff"><font size=3D"2"><span =
class=3D"037432012-06072010"><span =
class=3D"204040315-07072010"></span></span></font></font></font>&nbsp;</di=
v><div dir=3D"ltr" align=3D"left"><font face=3D"Arial"><font =
color=3D"#0000ff"><font size=3D"2"><span =
class=3D"037432012-06072010"><span =
class=3D"204040315-07072010">&nbsp;&nbsp;&nbsp;&nbsp;Some comments on =
your draft...</span></span></font></font></font></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"037432012-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"037432012-06072010">&nbsp;&nbsp;&nbsp;<font =
face=3D"Arial"><font color=3D"#0000ff"><font size=3D"2"><span =
class=3D"204040315-07072010">&nbsp;As a&nbsp;general comment, i</span>n =
addition to the MIBs already explicitly referenced in this draft, you =
should probably&nbsp;<span =
class=3D"204040315-07072010">&nbsp;</span></font></font></font></span></di=
v><div dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font=
 face=3D"Arial" color=3D"#0000ff" =
size=3D"2">include:</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"037432012-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"037432012-06072010"><font =
face=3D"Arial"><font color=3D"#0000ff"><font size=3D"2">o RFC 4801 =
(<span class=3D"204040315-07072010">&nbsp;"</span><font face=3D"Times =
New Roman">Definitions of Textual Conventions for Generalized =
Multiprotocol Label Switching (GMPLS) Management</font><font =
face=3D"Arial"><span class=3D"204040315-07072010">&nbsp;<font =
face=3D"Times New =
Roman">"</font>&nbsp;</span>),</font></font></font></font></span></div><di=
v dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font =
face=3D"Arial"><font color=3D"#0000ff"><font size=3D"2">o RFC 4802 =
(<span class=3D"204040315-07072010">"</span><font face=3D"Times New =
Roman">Generalized Multiprotocol Label Switching (GMPLS) Traffic =
Engineering Management Information Base</font><font face=3D"Arial"><span =
class=3D"204040315-07072010"><font face=3D"Times New =
Roman">"</font></span>),</font></font></font></font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font =
face=3D"Arial"><font color=3D"#0000ff"><font size=3D"2">o RFC 4220 =
(<span class=3D"204040315-07072010">"</span><font face=3D"Times New =
Roman">Traffic Engineering Link Management Information Base</font><font =
face=3D"Arial"><span class=3D"204040315-07072010"><font face=3D"Times =
New =
Roman">"</font></span>);</font></font></font></font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div=
 dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">As is, there is a curious =
dearth of MIB references for GMPLS related MIBs, given GMPLS will be the =
signaling</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"037432012-06072010"><font face=3D"Arial"><font =
color=3D"#0000ff"><font size=3D"2">method used for MPLS-TP LSPs.<span =
class=3D"204040315-07072010">&nbsp;</span></font></font></font></span></di=
v><div dir=3D"ltr" align=3D"left"><span class=3D"037432012-06072010"><font=
 face=3D"Arial"><font color=3D"#0000ff"><font size=3D"2"><span =
class=3D"204040315-07072010"></span></font></font></font></span>&nbsp;</di=
v><div dir=3D"ltr" align=3D"left"><span =
class=3D"037432012-06072010"><font><font color=3D"#0000ff"><font =
size=3D"2"><span class=3D"204040315-07072010"><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial">&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span><font color=3D"#0000ff" =
size=3D"2">NITs:</font></font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial">&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span><font color=3D"#0000ff" =
size=3D"2">=3D=3D=3D</font></font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">"functionss" is usually spelled with one =
"s" (page 7)</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">"exchaging" usually includes another "n" (page =
7)</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">"MPLS packets are encapsulated by using its own header" =
doesn't</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">parse (page 7).&nbsp; The second sentence in the same =
paragraph is just</font></span></div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">barely more readable.&nbsp; I would suggest re-writing the =
paragraph using</font></span></div><div dir=3D"ltr" align=3D"left"><font =
face=3D"Arial"><span class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2">the<span =
class=3D"Apple-converted-space">&nbsp;</span></font></span><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2">phrase =
"label-stack" to replace "header."&nbsp; This also eliminates =
the</font></span></font></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">need to identify the "header" as a =
"label-stack."</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">"path(" needs a space (page 8).</font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div=
 dir=3D"ltr" align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">Change "The two important =
.." to "Two important ..." (page 8).&nbsp; The</font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">"two important applications" =
should be in bullet format.</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">"a MPLS" should be "an MPLS" anywhere that =
the indefinite article is</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">used in conjunction with =
"MPLS."</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">In the 5th paragraph on page 10, to what does "The document" =
refer?</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Page 11 contains a number of examples where the first word =
following</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">a colon (":") is capitalized; this is not proper English - =
particularly when</font></span></div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">the text following the colon is not in the form of a bulleted =
list.&nbsp; I did not</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">check the entire draft for this, but =
suggest the authors should.</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">In the 2nd sentence, 7th paragraph of page =
11, to what does "This MIB</font></span></div><div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial"><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2">module"<span =
class=3D"Apple-converted-space">&nbsp;</span></font></span><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2">refer?</font></span></font></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">The&nbsp;2nd sentence in section 5.2.9 (top =
of page 13) does not parse.&nbsp; I</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">suggest breaking this sentence down and =
clarifying what is meant by it.</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">The 2nd paragraph in section 5.2.10 (page =
13) does not completely</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">describe the notation used.&nbsp; An arrow =
indicates a dependency between</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">two MIB modules, but is clearly a directed =
dependency and meaning</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">is not clear: I suggest using a =
more&nbsp;illustrative example by making the</font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">following =
change:</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Change -</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#ff0000" size=3D"2">A relationship "MIB module A depends on MIB =
module B" means that</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#ff0000" size=3D"2">MIB&nbsp;module A uses an object, object =
identifier, or textual convention<br>defined in MIB module B, or that =
MIB module A contains a pointer<br>(index or RowPointer) to an object in =
MIB module B.<br></font></span></div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font color=3D"#ff0000" size=3D"2"><font =
face=3D"Arial" color=3D"#0000ff">To -</font></font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"856523512-06072010"><font =
color=3D"#ff0000" size=3D"2"><div dir=3D"ltr" align=3D"left"><font =
face=3D"Arial"><span class=3D"856523512-06072010"><font color=3D"#008000" =
size=3D"2">The&nbsp;relationship "A --&gt; B"&nbsp;means A depends on =
B&nbsp;and that<span =
class=3D"Apple-converted-space">&nbsp;</span></font></span><span =
class=3D"856523512-06072010"><font color=3D"#ff0000" size=3D"2"><font =
color=3D"#008000">MIB&nbsp;module</font></font></span></font></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"856523512-06072010"><font =
color=3D"#ff0000" size=3D"2"><font face=3D"Arial" color=3D"#008000">A =
uses an object, object identifier, or textual convention defined in =
MIB</font></font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font color=3D"#ff0000" size=3D"2"><font =
face=3D"Arial" color=3D"#008000">module B, or that MIB module A contains =
a pointer (index or RowPointer)</font></font></span></div><div dir=3D"ltr"=
 align=3D"left"><span class=3D"856523512-06072010"><font color=3D"#ff0000"=
 size=3D"2"><font face=3D"Arial"><font color=3D"#008000">to an object in =
MIB module B.</font><br></font></font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font color=3D"#ff0000" =
size=3D"2"><font face=3D"Arial" color=3D"#0000ff">(Note that I am =
assumng I have the order of dependency correct, =
based</font></font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font color=3D"#ff0000" size=3D"2"><font =
face=3D"Arial" color=3D"#0000ff">on conventional "logical dependency" - =
I did not verify this be analyzing</font></font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"856523512-06072010"><font =
color=3D"#ff0000" size=3D"2"><font face=3D"Arial" color=3D"#0000ff">the =
diagram on page 14)</font></font></span></div><font color=3D"#ff0000" =
size=3D"2"></font></font></span><font color=3D"#ff0000" =
size=3D"2"></font></div><font color=3D"#ff0000" =
size=3D"2"></font></span><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">I suggest restructuring the last paragraph on page 16 =
(continuing on to</font></span></div><div dir=3D"ltr" align=3D"left"><font=
 face=3D"Arial"><span class=3D"856523512-06072010"><font color=3D"#0000ff"=
 size=3D"2">page 17) as&nbsp;two paragraphs,<span =
class=3D"Apple-converted-space">&nbsp;</span></font></span><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2">each =
including bulleted lists,<span =
class=3D"Apple-converted-space">&nbsp;</span></font></span><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2">as<span =
class=3D"Apple-converted-space">&nbsp;</span></font></span><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2">follows:</font></span></font></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial"><font color=3D"#0000ff" size=3D"2">"</font><font =
color=3D"#008000" size=3D"2">The following MPLS-TP OAM =
functionalities&nbsp;can be achieved using =
the</font></font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#008000" =
size=3D"2">&nbsp;MPLSTP-OAM-STD-MIB mib =
extensions:</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#008000" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#008000" =
size=3D"2">&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Continuity Check and =
Connectivity&nbsp;Verification,</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#008000" size=3D"2">&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; =
Alarm Reporting, Diagnostic,</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#008000" size=3D"2">&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; =
Route Tracing,</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#008000" =
size=3D"2">&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; =
Loopback&nbsp;tool,</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#008000" size=3D"2">&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Lock =
Instruct,</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#008000" =
size=3D"2">&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; Lock Reporting Remote =
Defect Indication,</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#008000" size=3D"2">&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; =
Client&nbsp;Failure Indication,</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#008000" size=3D"2">&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; =
Packet Loss Measurement and</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#008000" size=3D"2">&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; =
Packet Delay Measurement</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2"><font face=3D"Arial">"</font><font face=3D"Arial" =
color=3D"#008000">MPLS-TP&nbsp;OAM managed objects are defined based on =
the drafts:<br></font></font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font color=3D"#008000" =
size=3D"2"><font face=3D"Arial">&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; =
draft-ietf-mpls-tp-oam-requirements-06,&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp;o=
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-mpls-tp-oam-framework-06 =
and&nbsp;<br>&nbsp;&nbsp;&nbsp; o&nbsp;&nbsp;&nbsp; =
draft-ietf-mpls-tp-identifiers-01.<font =
color=3D"#0000ff">"</font></font></font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">The last paragraph on page 17 (continuing =
on to page 18) has the same</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">problem as the 2nd paragraph on page 13 =
(described above) and needs</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">a similar resolution.&nbsp; One approach =
might be to include this as part of a</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">new section (under modified section 2 =
"Conventions and Terminology"),</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">so that it does not need to be =
repeated.</font></span></div><div dir=3D"ltr" align=3D"left"><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial">&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span><font color=3D"#0000ff" =
size=3D"2">Not so NITty:</font></font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial">&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span><font color=3D"#0000ff" =
size=3D"2">=3D=3D=3D=3D=3D=3D=3D=3D=3D</font></font></span></div><div =
dir=3D"ltr" align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div=
 dir=3D"ltr" align=3D"left"><span class=3D"856523512-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">There are several problems =
with this paragraph (page 7):</font></span></div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2"><font face=3D"Arial">"</font><font color=3D"#000000" =
size=3D"3"><font face=3D"Arial" color=3D"#0000ff" size=3D"2">The basic =
unit in an MPLS network is called LSR(Label switched<br>&nbsp; router). =
It implements the control and forwarding plane of =
MPLS."</font></font></font></span></div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></font></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">o&nbsp;&nbsp;&nbsp; as a NIT, "LSR(" needs a =
space;</font></font></font></span></div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">o&nbsp;&nbsp;&nbsp; the meaning of "basic unit" is not at all =
clear;</font></font></font></span></div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">o&nbsp;&nbsp;&nbsp; an LSR does not necessarily implement a =
control plane.</font></font></font></span></div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">---------------------------------------------------------------=
------------------------------------------</font></font></font></span></di=
v><div><span class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2"><font color=3D"#000000" size=3D"3"><font face=3D"Arial" =
color=3D"#0000ff" =
size=3D"2"></font></font></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial">The next paragraph is =
also inaccurate<span class=3D"204040315-07072010">&nbsp; (also page =
7)&nbsp;</span>.</font></span></div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></font></font></span>&nbsp;</div><div><font =
face=3D"Arial"><span class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2"><font color=3D"#000000" size=3D"3"><font color=3D"#0000ff" =
size=3D"2">The control plane of an LSR is<span =
class=3D"Apple-converted-space">&nbsp;</span></font></font></font></span><=
span class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font=
 color=3D"#000000" size=3D"3"><font color=3D"#0000ff" size=3D"2">not =
directly responsible for =
exchanging</font></font></font></span></font></div><div><font =
face=3D"Arial"><span class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2"><font color=3D"#000000" size=3D"3"><font color=3D"#0000ff" =
size=3D"2">routing information (that is the<span =
class=3D"Apple-converted-space">&nbsp;</span></font></font></font></span><=
span class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font=
 color=3D"#000000" size=3D"3"><font color=3D"#0000ff" size=3D"2">control =
plane of the "router" part of =
an</font></font></font></span></font></div><div><font face=3D"Arial"><span=
 class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font color=3D"#0000ff" size=3D"2">LSR, =
again not necessarily part<span =
class=3D"Apple-converted-space">&nbsp;</span></font></font></font></span><=
span class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font=
 color=3D"#000000" size=3D"3"><font color=3D"#0000ff" size=3D"2">of an =
LSR in the general sense).&nbsp; =
This</font></font></font></span></font></div><div><font =
face=3D"Arial"><span class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2"><font color=3D"#000000" size=3D"3"><font color=3D"#0000ff" =
size=3D"2">"routing information" - if present<span =
class=3D"Apple-converted-space">&nbsp;</span></font></font></font></span><=
span class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font=
 color=3D"#000000" size=3D"3"><font color=3D"#0000ff" size=3D"2">- is =
simply one source of =
information</font></font></font></span></font></div><div><font =
face=3D"Arial"><span class=3D"856523512-06072010"><font color=3D"#0000ff" =
size=3D"2"><font color=3D"#000000" size=3D"3"><font color=3D"#0000ff" =
size=3D"2">that an LSR uses to "program"<span =
class=3D"Apple-converted-space">&nbsp;</span></font></font></font></span><=
span class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font=
 color=3D"#000000" size=3D"3"><font color=3D"#0000ff" size=3D"2">(not =
the best wording choice - I =
suggest</font></font></font></span></font></div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">"populate") forwarding =
tables.&nbsp;</font></font></font></span></div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></font></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial"><font color=3D"#0000ff" =
size=3D"2">The LSR "control plane" provides =
information</font>&nbsp;<font color=3D"#0000ff" size=3D"2">in terms of =
label bindings</font></font></span></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">which are part of the information used to populate forwarding =
tables in</font></span></div><div><span class=3D"856523512-06072010"><font=
 face=3D"Arial" color=3D"#0000ff" size=3D"2">an LSR.&nbsp; An LSR =
determines which label bindings to seek and =
retain</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">based on configuration and =
other information (such as that which may</font></span></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">be provided by routing).</font></span></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">While the primary intent (and common implementation) relies =
on use of</font></span></div><div><span class=3D"856523512-06072010"><font=
 face=3D"Arial" color=3D"#0000ff" size=3D"2">the 20 bit label as an =
"index into a forwarding table", this is not the =
only</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">way that an LSR may be =
implemented, nor is it necessarily =
presumed</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">to be implemented this =
way.&nbsp; This misconception is at the bottom of =
a</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">number of bad ideas that =
have been proposed in the MPLS WG (as well</font></span></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">as other places).&nbsp; How an LSR chooses to employ the 20 =
bit labels it</font></span></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">assigns for use by its peers is entirely up to the =
implementation.</font></span></div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></font></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></font></font></span></div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">---------------------------------------------------------------=
------------------------------------------</font></font></font></span></di=
v><div><span class=3D"856523512-06072010"><font =
face=3D"Arial"></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial">The&nbsp;remaining =
paragraphs in the section are slightly inaccurate as =
well.</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial"></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial">At&nbsp;"MPLS =
ingress", a "label stack" is prefixed.&nbsp; In the simplest case, =
the</font></span></div><div><font face=3D"Arial"><span =
class=3D"856523512-06072010">"label<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
class=3D"856523512-06072010">stack" comprises a single label-stack =
entry.</span></font></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial"></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial">At LSP ingress =
(because of the possibility of nested - or hierarchical =
-&nbsp;</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial">LSPs), there is the possibility that one or more =
additional label-stack</font></span></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial">entries will be =
"pushed" onto the label stack&nbsp;- if there is a label =
stack</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial">present already. Otherwise, the paragraph above =
applies.</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial"></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial">In at least the first =
case, there is more to "encapsulating" the =
packet</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial">than simply prefixing an MPLS label (stack).&nbsp; It is =
also necessary to</font></span></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial">add&nbsp;the =
appropriate "MPLS-specific" L2 encapsulation (including, =
for</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial">instance, the MPLS PID).</font></span></div><div><span =
class=3D"856523512-06072010"><font =
face=3D"Arial"></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial">For all "swap", "pop" =
and "push" operations, one<span =
class=3D"Apple-converted-space">&nbsp;</span><em><strong>or =
more</strong></em><span =
class=3D"Apple-converted-space">&nbsp;</span>labels =
may</font></span></div><div><font face=3D"Arial"><span =
class=3D"856523512-06072010">be<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
class=3D"856523512-06072010">involved.</span></font></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial"><span =
class=3D"204040315-07072010">&nbsp;</span></font></span></div><div><span =
class=3D"856523512-06072010"><font =
face=3D"Arial">-----------------------------------------------------------=
----------------------------------------------</font></span></div><div><sp=
an class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></font></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">I believe the last paragraph in section 5.2.6 (on page 12) is =
inaccurate.</font></font></font></span></div><div><span =
class=3D"856523512-06072010"><font color=3D"#0000ff" size=3D"2"><font =
color=3D"#000000" size=3D"3"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">A device that terminates an ATM pseudo-wire will almost =
certainly offer</font></font></font></span></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial" size=3D"2">an ATM =
interface to other devices (otherwise, what is the point of =
using</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial" size=3D"2">an ATM pseudowire?).&nbsp; If it does, it will =
necessarily have to include that</font></span></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial" size=3D"2">interface =
as part of the ifTable.</font></span></div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial" =
size=3D"2"></font></span>&nbsp;</div><div><span =
class=3D"856523512-06072010"><font face=3D"Arial" size=3D"2">In any =
case, inclusion of the last two sentence in the last paragraph =
of</font></span></div><div><span class=3D"856523512-06072010"><font =
face=3D"Arial" size=3D"2">section 5.2.6 is unnecessary and those =
sentences&nbsp;should be removed.</font></span><span =
class=3D"856523512-06072010"><font size=3D"+0"><font =
size=3D"+0"></font></font></span></div><font size=3D"+0"><font =
size=3D"+0"><div><font face=3D"Arial" =
size=3D"2"></font>&nbsp;</div><div><font size=3D"+0"><font =
size=3D"+0"><span class=3D"856523512-06072010"><font face=3D"Arial" =
size=3D"2">---------------------------------------------------------------=
------------------------------------------</font></span></font></font></di=
v><font size=3D"+0"><font size=3D"+0"><div><font =
face=3D"Arial"></font>&nbsp;</div><div><font size=3D"+0"><span =
class=3D"856523512-06072010"><font face=3D"Arial" size=3D"2">In the =
Security Considerations section, in the 3rd paragraph, you =
point</font></span></font></div><div><font face=3D"Arial"><font =
size=3D"+0"><span class=3D"856523512-06072010"><font size=3D"2">out the =
potential issues<span =
class=3D"Apple-converted-space">&nbsp;</span></font></span></font><font =
size=3D"+0"><span class=3D"856523512-06072010"><font size=3D"2">with =
allowing&nbsp;write and create access.&nbsp; In =
the</font></span></font></font></div><div><font face=3D"Arial"><font =
size=3D"+0"><span class=3D"856523512-06072010"><font size=3D"2">same =
paragraph, you then<span =
class=3D"Apple-converted-space">&nbsp;</span></font></span></font><font =
size=3D"+0"><span class=3D"856523512-06072010"><font size=3D"2">go on to =
say "allowed to access and =
GET"</font></span></font></font></div><div><font face=3D"Arial"><font =
size=3D"+0"><span class=3D"856523512-06072010"><font size=3D"2">MIB =
objects.&nbsp; I suggest<span =
class=3D"Apple-converted-space">&nbsp;</span></font></span></font><font =
size=3D"+0"><span class=3D"856523512-06072010"><font size=3D"2">deleting =
"and GET" from =
this&nbsp;paragraph.</font></span></font></font></div><div><font =
face=3D"Arial" size=3D"2"><span =
class=3D"856523512-06072010"></span></font>&nbsp;</div><div><font =
face=3D"Arial" size=3D"2"><span =
class=3D"856523512-06072010">---------------------------------------------=
------------------------------------------------------------</span></font>=
</div><div><font face=3D"Arial" size=3D"2"><span =
class=3D"856523512-06072010"></span></font>&nbsp;</div><div><font =
face=3D"Arial"><font size=3D"2"><span class=3D"856523512-06072010"><span =
class=3D"204040315-07072010">In the IANA Considerations section, =
g</span></span><span class=3D"856523512-06072010">iven this is an =
overview document,&nbsp;<span =
class=3D"204040315-07072010">&nbsp;</span></span></font></font></div><div>=
<font face=3D"Arial"><font><font size=3D"2"><span =
class=3D"856523512-06072010">I think you are safe in at least<span =
class=3D"Apple-converted-space">&nbsp;</span></span></font></font><span =
class=3D"856523512-06072010"><font size=3D"2">starting off with the =
basic "IANA has no&nbsp;<span =
class=3D"204040315-07072010">&nbsp;</span></font></span></font></div><div>=
<font><span class=3D"856523512-06072010"><font face=3D"Arial"><font =
size=3D"2">actions" text found in most IDs<span =
class=3D"204040315-07072010">&nbsp;</span></font></font></span></font><fon=
t face=3D"Arial" size=3D"2"><span class=3D"856523512-06072010">of this =
type.&nbsp; It is fairly certain that this&nbsp;<span =
class=3D"204040315-07072010">&nbsp;</span></span></font></div><div><font =
face=3D"Arial"><font size=3D"2"><font><span =
class=3D"856523512-06072010">will not change, so you might as<span =
class=3D"204040315-07072010">&nbsp;</span></span></font><span =
class=3D"856523512-06072010">well get it out of the =
way.</span></font></font><font size=3D"+0"></font></div><font =
size=3D"+0"><font =
size=3D"2"></font></font></font></font></font></font></font></font></font>=
</span><font><font color=3D"#0000ff"><font size=3D"2"><div dir=3D"ltr" =
align=3D"left"><span class=3D"856523512-06072010"><font face=3D"Arial" =
size=3D"2"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span=
 class=3D"856523512-06072010"><font face=3D"Arial" =
size=3D"2">=3D=3D=3D</font></span></div></font></font></font><div =
dir=3D"ltr" align=3D"left"><font><font color=3D"#0000ff"><font =
size=3D"2"><span class=3D"856523512-06072010"><font face=3D"Arial" =
size=3D"2">Eric</font></span></font></font></font></div></div>____________=
___________________________________<br>mpls mailing list<br><a =
href=3D"mailto:mpls@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">mpls@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/mpls</a><br></div></span></blockqu=
ote></div><br></div></body></html>=

--Apple-Mail-2--336776210--

From eric.gray@ericsson.com  Sat Jul 10 18:21:54 2010
Return-Path: <eric.gray@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2ED93A67F0 for <mpls@core3.amsl.com>; Sat, 10 Jul 2010 18:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.998
X-Spam-Level: 
X-Spam-Status: No, score=-2.998 tagged_above=-999 required=5 tests=[AWL=-0.399, BAYES_00=-2.599]
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 N7SfnkPifukV for <mpls@core3.amsl.com>; Sat, 10 Jul 2010 18:21:53 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 50B7A3A67AE for <mpls@ietf.org>; Sat, 10 Jul 2010 18:21:53 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6B1LrGB031566 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 10 Jul 2010 20:21:58 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.117]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Sat, 10 Jul 2010 21:21:53 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Loa Andersson <loa@pi.nu>
Date: Sat, 10 Jul 2010 21:21:51 -0400
Thread-Topic: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping -	take II
Thread-Index: AcsXv/I+Zr+AVglRQ7G6kfgbGwGjsgI13ZvA
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F1053B9876E8@EUSAACMS0701.eamcs.ericsson.se>
References: <4C2A4678.9020806@pi.nu>
In-Reply-To: <4C2A4678.9020806@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping -	take II
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jul 2010 01:21:54 -0000

 Support.

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa=
 Andersson
Sent: Tuesday, June 29, 2010 3:16 PM
To: mpls@ietf.org
Subject: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping - ta=
ke II

Working Group,

this email is to start poll to adopt
draft-chen-mpls-return-path-specified-lsp-ping
as an MPLS working group draft.

After recent experience, the chairs would like to remind you all
what it means to conduct a poll to adopt a draft as a working group
draft.

- Please recall that the IETF does not "vote." Polls of a working
   group are to gather information to help the chairs make their
   decisions. Voting is not part of the normal working methods of
   an IETF working group.

- The "rough consensus" process used in the working group assumes
   that people expressing opinions are also participating in the
   development of standards documents.

- Subscription to the list specifically to express an opinion is
   noticed by the chairs who has access to information on the new list
   members. Such behavior is not part of the normal working methods.

- The purpose of a poll for adoption is to help the chairs understand
   the level of support for a document (i.e. who has read it, who
   believes it is a good starting point for working group work, who
   will contribute to the work) and whether there are any significant
   technical issues. Statements of objection must be backed up by
   proper technical reasons.

So please respond to this poll indicating whether you support the=20
adoption of this draft or stating your technical issues.

This poll ends eob July 13.


Loa and George
mpls wg co-chairs
--=20


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From root@core3.amsl.com  Sat Jul 10 23:15:03 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id B54743A6840; Sat, 10 Jul 2010 23:15:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100711061503.B54743A6840@core3.amsl.com>
Date: Sat, 10 Jul 2010 23:15:03 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-ldp-p2mp-10.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jul 2010 06:15:04 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.


	Title           : Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths
	Author(s)       : I. Minei, et al.
	Filename        : draft-ietf-mpls-ldp-p2mp-10.txt
	Pages           : 38
	Date            : 2010-07-10

This document describes extensions to the Label Distribution Protocol
(LDP) for the setup of point to multi-point (P2MP) and multipoint-to-
multipoint (MP2MP) Label Switched Paths (LSPs) in Multi-Protocol
Label Switching (MPLS) networks.  These extensions are also referred
to as mLDP Multicast LDP. mLDP constructs the P2MP or MP2MP LSPs
without interacting with or relying upon any other multicast tree
construction protocol.  Protocol elements and procedures for this
solution are described for building such LSPs in a receiver-initiated
manner.  There can be various applications for P2MP/MP2MP LSPs, for
example IP multicast or support for multicast in BGP/MPLS L3VPNs.
Specification of how such applications can use a LDP signaled P2MP/
MP2MP LSP is outside the scope of this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-p2mp-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-mpls-ldp-p2mp-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-10230606.I-D@ietf.org>


--NextPart--

From agmalis@gmail.com  Sun Jul 11 10:12:27 2010
Return-Path: <agmalis@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DFC523A69C8; Sun, 11 Jul 2010 10:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
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 GTBTCVkMWZog; Sun, 11 Jul 2010 10:12:25 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 445993A6832; Sun, 11 Jul 2010 10:12:25 -0700 (PDT)
Received: by vws14 with SMTP id 14so3715684vws.31 for <multiple recipients>; Sun, 11 Jul 2010 10:12:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=UYhX8Y4I0yhBTsjV2hF3RMXyZap+U46stWjgHUs4t50=; b=o1HtAz6KkX0K6RA7HTIySsRPEz7bfl3H922JcZAyLrxa/w+XFYkBa63zmFlzdi9FlD mKSEFHBXBVbh+ySjus5S+0hZSiWr55rN+a2IOtkAWb+KToQQBL2ksyPdYKPATK+yQ/Pw qrp03EPA3i5E/Baa5PmhtvyVCrX86cdR0JIiI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=npvY3O8LMbRLBBVYuvlBcnI2F6DYGJCXqHgsON0Mvql/Q1HdziYtVLCHV4lkTT1wkx iwFlhU9IQn32+8uM6TmQLKQ+k/33sbxb+RTYGzcJBUwikote4POq1dYNDw86gjbL8Xol pmTcdNGSqVLhYN2ue/F3qQkQ32GWi2OyRvvOg=
Received: by 10.220.124.153 with SMTP id u25mr6345775vcr.66.1278868347122;  Sun, 11 Jul 2010 10:12:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.86.69 with HTTP; Sun, 11 Jul 2010 10:12:07 -0700 (PDT)
In-Reply-To: <829184DB-D53C-4B1A-9BDD-3C4762EBF978@lucidvision.com>
References: <C0AC8FAB6849AB4FADACCC70A949E2F1053B72289E@EUSAACMS0701.eamcs.ericsson.se> <829184DB-D53C-4B1A-9BDD-3C4762EBF978@lucidvision.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sun, 11 Jul 2010 13:12:07 -0400
Message-ID: <AANLkTil9EPC7Xlss8wIV8MtKBkZg6eepiqjfwv8Wu0Ie@mail.gmail.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: A S Kiran Koushik <kkoushik@cisco.com>, Daniel King <daneil@olddog.co.uk>, Venkatesan Mahalingam <venkatesan.mahalingam@aricent.com>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] MPLS-TP management overview draft - draft-farrel-mpls-tp-mib-management-overview
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jul 2010 17:12:27 -0000

Tom,

While MPLS-TP can be run in a static environment, there will be
dynamically signaled deployments as well. As such, Eric is correct
that GMPLS-related MIBs should be included in the draft. There should
probably be an additional sub-section in section 6 to say that the
applicability for GMPLS MIBs would be for networks that are using
dynamically signaled LSPs.

Cheers,
Andy

On Thu, Jul 8, 2010 at 3:42 PM, Thomas Nadeau <tnadeau@lucidvision.com> wro=
te:
>
> Why are we including GMPLS-related MIBs in this? =A0I'd like to not confu=
se
> the fact that the basic version of TP is supposed to be static, and handl=
ed
> (managed) as such. If you do talk about GMPLS MIBs in there, then I'd lik=
e
> to be very clear that it is optional.
> --Tom
>
> Authors,
>
> =A0=A0=A0=A0Some comments on your draft...
>
> =A0=A0=A0=A0As a=A0general comment, in addition to the MIBs already expli=
citly
> referenced in this draft, you should probably
> include:
>
> o RFC 4801 (=A0"Definitions of Textual Conventions for Generalized
> Multiprotocol Label Switching (GMPLS) Management=A0"=A0),
> o RFC 4802 ("Generalized Multiprotocol Label Switching (GMPLS) Traffic
> Engineering Management Information Base"),
> o RFC 4220 ("Traffic Engineering Link Management Information Base");
>
> As is, there is a curious dearth of MIB references for GMPLS related MIBs=
,
> given GMPLS will be the signaling
> method used for MPLS-TP LSPs.
>
> =A0=A0=A0=A0NITs:
> =A0=A0=A0=A0=3D=3D=3D
>
> "functionss" is usually spelled with one "s" (page 7)
>
> "exchaging" usually includes another "n" (page 7)
>
> "MPLS packets are encapsulated by using its own header" doesn't
> parse (page 7).=A0 The second sentence in the same paragraph is just
> barely more readable.=A0 I would suggest re-writing the paragraph using
> the=A0phrase "label-stack" to replace "header."=A0 This also eliminates t=
he
> need to identify the "header" as a "label-stack."
>
> "path(" needs a space (page 8).
>
> Change "The two important .." to "Two important ..." (page 8).=A0 The
> "two important applications" should be in bullet format.
>
> "a MPLS" should be "an MPLS" anywhere that the indefinite article is
> used in conjunction with "MPLS."
>
> In the 5th paragraph on page 10, to what does "The document" refer?
>
> Page 11 contains a number of examples where the first word following
> a colon (":") is capitalized; this is not proper English - particularly w=
hen
> the text following the colon is not in the form of a bulleted list.=A0 I =
did
> not
> check the entire draft for this, but suggest the authors should.
>
> In the 2nd sentence, 7th paragraph of page 11, to what does "This MIB
> module"=A0refer?
>
> The=A02nd sentence in section 5.2.9 (top of page 13) does not parse.=A0 I
> suggest breaking this sentence down and clarifying what is meant by it.
>
> The 2nd paragraph in section 5.2.10 (page 13) does not completely
> describe the notation used.=A0 An arrow indicates a dependency between
> two MIB modules, but is clearly a directed dependency and meaning
> is not clear: I suggest using a more=A0illustrative example by making the
> following change:
>
> Change -
> A relationship "MIB module A depends on MIB module B" means that
> MIB=A0module A uses an object, object identifier, or textual convention
> defined in MIB module B, or that MIB module A contains a pointer
> (index or RowPointer) to an object in MIB module B.
> To -
> The=A0relationship "A --> B"=A0means A depends on B=A0and that=A0MIB=A0mo=
dule
> A uses an object, object identifier, or textual convention defined in MIB
> module B, or that MIB module A contains a pointer (index or RowPointer)
> to an object in MIB module B.
> (Note that I am assumng I have the order of dependency correct, based
> on conventional "logical dependency" - I did not verify this be analyzing
> the diagram on page 14)
>
> I suggest restructuring the last paragraph on page 16 (continuing on to
> page 17) as=A0two paragraphs,=A0each including bulleted lists,=A0as=A0fol=
lows:
>
> "The following MPLS-TP OAM functionalities=A0can be achieved using the
> =A0MPLSTP-OAM-STD-MIB mib extensions:
>
> =A0=A0=A0 o=A0=A0=A0 Continuity Check and Connectivity=A0Verification,
> =A0=A0=A0 o=A0=A0=A0 Alarm Reporting, Diagnostic,
> =A0=A0=A0 o=A0=A0=A0 Route Tracing,
> =A0=A0=A0 o=A0=A0=A0 Loopback=A0tool,
> =A0=A0=A0 o=A0=A0=A0 Lock Instruct,
> =A0=A0=A0 o=A0=A0=A0 Lock Reporting Remote Defect Indication,
> =A0=A0=A0 o=A0=A0=A0 Client=A0Failure Indication,
> =A0=A0=A0 o=A0=A0=A0 Packet Loss Measurement and
> =A0=A0=A0 o=A0=A0=A0 Packet Delay Measurement
>
> "MPLS-TP=A0OAM managed objects are defined based on the drafts:
> =A0=A0=A0 o=A0=A0=A0 draft-ietf-mpls-tp-oam-requirements-06,
> =A0=A0=A0=A0o=A0=A0=A0=A0draft-ietf-mpls-tp-oam-framework-06 and
> =A0=A0=A0 o=A0=A0=A0 draft-ietf-mpls-tp-identifiers-01."
>
> The last paragraph on page 17 (continuing on to page 18) has the same
> problem as the 2nd paragraph on page 13 (described above) and needs
> a similar resolution.=A0 One approach might be to include this as part of=
 a
> new section (under modified section 2 "Conventions and Terminology"),
> so that it does not need to be repeated.
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
>
> =A0=A0=A0=A0Not so NITty:
> =A0=A0=A0=A0=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> There are several problems with this paragraph (page 7):
>
> "The basic unit in an MPLS network is called LSR(Label switched
> =A0 router). It implements the control and forwarding plane of MPLS."
>
> o=A0=A0=A0 as a NIT, "LSR(" needs a space;
> o=A0=A0=A0 the meaning of "basic unit" is not at all clear;
> o=A0=A0=A0 an LSR does not necessarily implement a control plane.
> -------------------------------------------------------------------------=
--------------------------------
>
> The next paragraph is also inaccurate=A0 (also page 7)=A0.
>
> The control plane of an LSR is=A0not directly responsible for exchanging
> routing information (that is the=A0control plane of the "router" part of =
an
> LSR, again not necessarily part=A0of an LSR in the general sense).=A0 Thi=
s
> "routing information" - if present=A0- is simply one source of informatio=
n
> that an LSR uses to "program"=A0(not the best wording choice - I suggest
> "populate") forwarding tables.
>
> The LSR "control plane" provides information=A0in terms of label bindings
> which are part of the information used to populate forwarding tables in
> an LSR.=A0 An LSR determines which label bindings to seek and retain
> based on configuration and other information (such as that which may
> be provided by routing).
>
> While the primary intent (and common implementation) relies on use of
> the 20 bit label as an "index into a forwarding table", this is not the o=
nly
> way that an LSR may be implemented, nor is it necessarily presumed
> to be implemented this way.=A0 This misconception is at the bottom of a
> number of bad ideas that have been proposed in the MPLS WG (as well
> as other places).=A0 How an LSR chooses to employ the 20 bit labels it
> assigns for use by its peers is entirely up to the implementation.
>
> -------------------------------------------------------------------------=
--------------------------------
>
> The=A0remaining paragraphs in the section are slightly inaccurate as well=
.
>
> At=A0"MPLS ingress", a "label stack" is prefixed.=A0 In the simplest case=
, the
> "label=A0stack" comprises a single label-stack entry.
>
> At LSP ingress (because of the possibility of nested - or hierarchical -
> LSPs), there is the possibility that one or more additional label-stack
> entries will be "pushed" onto the label stack=A0- if there is a label sta=
ck
> present already. Otherwise, the paragraph above applies.
>
> In at least the first case, there is more to "encapsulating" the packet
> than simply prefixing an MPLS label (stack).=A0 It is also necessary to
> add=A0the appropriate "MPLS-specific" L2 encapsulation (including, for
> instance, the MPLS PID).
>
> For all "swap", "pop" and "push" operations, one=A0or more=A0labels may
> be=A0involved.
>
> -------------------------------------------------------------------------=
--------------------------------
>
> I believe the last paragraph in section 5.2.6 (on page 12) is inaccurate.
> A device that terminates an ATM pseudo-wire will almost certainly offer
> an ATM interface to other devices (otherwise, what is the point of using
> an ATM pseudowire?).=A0 If it does, it will necessarily have to include t=
hat
> interface as part of the ifTable.
>
> In any case, inclusion of the last two sentence in the last paragraph of
> section 5.2.6 is unnecessary and those sentences=A0should be removed.
>
> -------------------------------------------------------------------------=
--------------------------------
>
> In the Security Considerations section, in the 3rd paragraph, you point
> out the potential issues=A0with allowing=A0write and create access.=A0 In=
 the
> same paragraph, you then=A0go on to say "allowed to access and GET"
> MIB objects.=A0 I suggest=A0deleting "and GET" from this=A0paragraph.
>
> -------------------------------------------------------------------------=
--------------------------------
>
> In the IANA Considerations section, given this is an overview document,
> I think you are safe in at least=A0starting off with the basic "IANA has =
no
> actions" text found in most IDs=A0of this type.=A0 It is fairly certain t=
hat
> this
> will not change, so you might as=A0well get it out of the way.
>
> =3D=3D=3D
> Eric
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>

From lucyyong@huawei.com  Sun Jul 11 12:01:58 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62D373A69FC; Sun, 11 Jul 2010 12:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 xl1X3vyZCDAL; Sun, 11 Jul 2010 12:01:57 -0700 (PDT)
Received: from szxga05-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id DA3653A69E9; Sun, 11 Jul 2010 12:01:54 -0700 (PDT)
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 <0L5E00CHIQ79G0@szxga05-in.huawei.com>; Mon, 12 Jul 2010 03:01:57 +0800 (CST)
Received: from 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 <0L5E003MYQ788S@szxga05-in.huawei.com>; Mon, 12 Jul 2010 03:01:57 +0800 (CST)
Received: from y736742 (cpe-173-173-72-139.tx.res.rr.com [173.173.72.139]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L5E003JWQ75RU@szxml01-in.huawei.com>; Mon, 12 Jul 2010 03:01:56 +0800 (CST)
Date: Sun, 11 Jul 2010 14:01:44 -0500
From: Yong Lucy <lucyyong@huawei.com>
To: 'pwe3' <pwe3@ietf.org>, mpls@ietf.org
Message-id: <005601cb212b$88c87520$6901a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcshKn//sN+AIOU8QTaFblRParU41QAAMiWA
Subject: [mpls] FW: New Version Notification for draft-yong-pwe3-lfc-fat-pw-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jul 2010 19:01:58 -0000

Look forward to hearing your feedbacks on this in Maastricht. -Lucy



A new version of I-D, draft-yong-pwe3-lfc-fat-pw-01.txt has been
successfully submitted by Lucy Yong and posted to the IETF repository.

Filename:	 draft-yong-pwe3-lfc-fat-pw
Revision:	 01
Title:		 Large Flow Classification in Flow Aware Transport over PSN
Creation_date:	 2010-07-11
WG ID:		 Independent Submission
Number_of_pages: 17

Abstract:
Network traffic has shown the combination of few very high bit rate
flows (large flow) and a huge amount of very low bit rate flows
(small flow), which causes uneven load balance over ECMP or LAG.
Differentiating large flow and small flow packets in IP/MPLS
networks enables an enhanced ECMP transport. Enhanced ECMP applies
different distribution methods to large flow packets and small flow
packets to improve the load balance and congestion control. This
draft proposes large flow classification scheme for flow awareness
transport in PSN.
 



The IETF Secretariat.



From tnadeau@lucidvision.com  Sun Jul 11 15:27:15 2010
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A36CE3A686D; Sun, 11 Jul 2010 15:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.603
X-Spam-Level: 
X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_35=0.6, MIME_QP_LONG_LINE=1.396]
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 JEDl89dszZnQ; Sun, 11 Jul 2010 15:27:14 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by core3.amsl.com (Postfix) with ESMTP id 0F3223A6807; Sun, 11 Jul 2010 15:27:13 -0700 (PDT)
Received: from [10.121.43.159] (unknown [166.137.4.62]) by lucidvision.com (Postfix) with ESMTP id D57015B8FB7; Sun, 11 Jul 2010 18:27:16 -0400 (EDT)
References: <C0AC8FAB6849AB4FADACCC70A949E2F1053B72289E@EUSAACMS0701.eamcs.ericsson.se> <829184DB-D53C-4B1A-9BDD-3C4762EBF978@lucidvision.com> <AANLkTil9EPC7Xlss8wIV8MtKBkZg6eepiqjfwv8Wu0Ie@mail.gmail.com>
In-Reply-To: <AANLkTil9EPC7Xlss8wIV8MtKBkZg6eepiqjfwv8Wu0Ie@mail.gmail.com>
Mime-Version: 1.0 (iPhone Mail 8A293)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <437A4733-6E9E-4700-8238-75AC4E88E8C3@lucidvision.com>
X-Mailer: iPhone Mail (8A293)
From: Thomas Nadeau <tnadeau@lucidvision.com>
Date: Sun, 11 Jul 2010 18:28:03 -0400
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: A S Kiran Koushik <kkoushik@cisco.com>, Daniel King <daneil@olddog.co.uk>, Venkatesan Mahalingam <venkatesan.mahalingam@aricent.com>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] MPLS-TP management overview draft - draft-farrel-mpls-tp-mib-management-overview
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jul 2010 22:27:15 -0000

I'm not disputing that; just ask that we are clearly separating things.

Sent from my iPhone

On Jul 11, 2010, at 1:12 PM, "Andrew G. Malis" <agmalis@gmail.com> wrote:

> Tom,
>=20
> While MPLS-TP can be run in a static environment, there will be
> dynamically signaled deployments as well. As such, Eric is correct
> that GMPLS-related MIBs should be included in the draft. There should
> probably be an additional sub-section in section 6 to say that the
> applicability for GMPLS MIBs would be for networks that are using
> dynamically signaled LSPs.
>=20
> Cheers,
> Andy
>=20
> On Thu, Jul 8, 2010 at 3:42 PM, Thomas Nadeau <tnadeau@lucidvision.com> wr=
ote:
>>=20
>> Why are we including GMPLS-related MIBs in this?  I'd like to not confuse=

>> the fact that the basic version of TP is supposed to be static, and handl=
ed
>> (managed) as such. If you do talk about GMPLS MIBs in there, then I'd lik=
e
>> to be very clear that it is optional.
>> --Tom
>>=20
>> Authors,
>>=20
>>     Some comments on your draft...
>>=20
>>     As a general comment, in addition to the MIBs already explicitly
>> referenced in this draft, you should probably
>> include:
>>=20
>> o RFC 4801 ( "Definitions of Textual Conventions for Generalized
>> Multiprotocol Label Switching (GMPLS) Management " ),
>> o RFC 4802 ("Generalized Multiprotocol Label Switching (GMPLS) Traffic
>> Engineering Management Information Base"),
>> o RFC 4220 ("Traffic Engineering Link Management Information Base");
>>=20
>> As is, there is a curious dearth of MIB references for GMPLS related MIBs=
,
>> given GMPLS will be the signaling
>> method used for MPLS-TP LSPs.
>>=20
>>     NITs:
>>     =3D=3D=3D
>>=20
>> "functionss" is usually spelled with one "s" (page 7)
>>=20
>> "exchaging" usually includes another "n" (page 7)
>>=20
>> "MPLS packets are encapsulated by using its own header" doesn't
>> parse (page 7).  The second sentence in the same paragraph is just
>> barely more readable.  I would suggest re-writing the paragraph using
>> the phrase "label-stack" to replace "header."  This also eliminates the
>> need to identify the "header" as a "label-stack."
>>=20
>> "path(" needs a space (page 8).
>>=20
>> Change "The two important .." to "Two important ..." (page 8).  The
>> "two important applications" should be in bullet format.
>>=20
>> "a MPLS" should be "an MPLS" anywhere that the indefinite article is
>> used in conjunction with "MPLS."
>>=20
>> In the 5th paragraph on page 10, to what does "The document" refer?
>>=20
>> Page 11 contains a number of examples where the first word following
>> a colon (":") is capitalized; this is not proper English - particularly w=
hen
>> the text following the colon is not in the form of a bulleted list.  I di=
d
>> not
>> check the entire draft for this, but suggest the authors should.
>>=20
>> In the 2nd sentence, 7th paragraph of page 11, to what does "This MIB
>> module" refer?
>>=20
>> The 2nd sentence in section 5.2.9 (top of page 13) does not parse.  I
>> suggest breaking this sentence down and clarifying what is meant by it.
>>=20
>> The 2nd paragraph in section 5.2.10 (page 13) does not completely
>> describe the notation used.  An arrow indicates a dependency between
>> two MIB modules, but is clearly a directed dependency and meaning
>> is not clear: I suggest using a more illustrative example by making the
>> following change:
>>=20
>> Change -
>> A relationship "MIB module A depends on MIB module B" means that
>> MIB module A uses an object, object identifier, or textual convention
>> defined in MIB module B, or that MIB module A contains a pointer
>> (index or RowPointer) to an object in MIB module B.
>> To -
>> The relationship "A --> B" means A depends on B and that MIB module
>> A uses an object, object identifier, or textual convention defined in MIB=

>> module B, or that MIB module A contains a pointer (index or RowPointer)
>> to an object in MIB module B.
>> (Note that I am assumng I have the order of dependency correct, based
>> on conventional "logical dependency" - I did not verify this be analyzing=

>> the diagram on page 14)
>>=20
>> I suggest restructuring the last paragraph on page 16 (continuing on to
>> page 17) as two paragraphs, each including bulleted lists, as follows:
>>=20
>> "The following MPLS-TP OAM functionalities can be achieved using the
>>  MPLSTP-OAM-STD-MIB mib extensions:
>>=20
>>     o    Continuity Check and Connectivity Verification,
>>     o    Alarm Reporting, Diagnostic,
>>     o    Route Tracing,
>>     o    Loopback tool,
>>     o    Lock Instruct,
>>     o    Lock Reporting Remote Defect Indication,
>>     o    Client Failure Indication,
>>     o    Packet Loss Measurement and
>>     o    Packet Delay Measurement
>>=20
>> "MPLS-TP OAM managed objects are defined based on the drafts:
>>     o    draft-ietf-mpls-tp-oam-requirements-06,
>>     o    draft-ietf-mpls-tp-oam-framework-06 and
>>     o    draft-ietf-mpls-tp-identifiers-01."
>>=20
>> The last paragraph on page 17 (continuing on to page 18) has the same
>> problem as the 2nd paragraph on page 13 (described above) and needs
>> a similar resolution.  One approach might be to include this as part of a=

>> new section (under modified section 2 "Conventions and Terminology"),
>> so that it does not need to be repeated.
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>>=20
>>     Not so NITty:
>>     =3D=3D=3D=3D=3D=3D=3D=3D=3D
>>=20
>> There are several problems with this paragraph (page 7):
>>=20
>> "The basic unit in an MPLS network is called LSR(Label switched
>>   router). It implements the control and forwarding plane of MPLS."
>>=20
>> o    as a NIT, "LSR(" needs a space;
>> o    the meaning of "basic unit" is not at all clear;
>> o    an LSR does not necessarily implement a control plane.
>> -------------------------------------------------------------------------=
--------------------------------
>>=20
>> The next paragraph is also inaccurate  (also page 7) .
>>=20
>> The control plane of an LSR is not directly responsible for exchanging
>> routing information (that is the control plane of the "router" part of an=

>> LSR, again not necessarily part of an LSR in the general sense).  This
>> "routing information" - if present - is simply one source of information
>> that an LSR uses to "program" (not the best wording choice - I suggest
>> "populate") forwarding tables.
>>=20
>> The LSR "control plane" provides information in terms of label bindings
>> which are part of the information used to populate forwarding tables in
>> an LSR.  An LSR determines which label bindings to seek and retain
>> based on configuration and other information (such as that which may
>> be provided by routing).
>>=20
>> While the primary intent (and common implementation) relies on use of
>> the 20 bit label as an "index into a forwarding table", this is not the o=
nly
>> way that an LSR may be implemented, nor is it necessarily presumed
>> to be implemented this way.  This misconception is at the bottom of a
>> number of bad ideas that have been proposed in the MPLS WG (as well
>> as other places).  How an LSR chooses to employ the 20 bit labels it
>> assigns for use by its peers is entirely up to the implementation.
>>=20
>> -------------------------------------------------------------------------=
--------------------------------
>>=20
>> The remaining paragraphs in the section are slightly inaccurate as well.
>>=20
>> At "MPLS ingress", a "label stack" is prefixed.  In the simplest case, th=
e
>> "label stack" comprises a single label-stack entry.
>>=20
>> At LSP ingress (because of the possibility of nested - or hierarchical -
>> LSPs), there is the possibility that one or more additional label-stack
>> entries will be "pushed" onto the label stack - if there is a label stack=

>> present already. Otherwise, the paragraph above applies.
>>=20
>> In at least the first case, there is more to "encapsulating" the packet
>> than simply prefixing an MPLS label (stack).  It is also necessary to
>> add the appropriate "MPLS-specific" L2 encapsulation (including, for
>> instance, the MPLS PID).
>>=20
>> For all "swap", "pop" and "push" operations, one or more labels may
>> be involved.
>>=20
>> -------------------------------------------------------------------------=
--------------------------------
>>=20
>> I believe the last paragraph in section 5.2.6 (on page 12) is inaccurate.=

>> A device that terminates an ATM pseudo-wire will almost certainly offer
>> an ATM interface to other devices (otherwise, what is the point of using
>> an ATM pseudowire?).  If it does, it will necessarily have to include tha=
t
>> interface as part of the ifTable.
>>=20
>> In any case, inclusion of the last two sentence in the last paragraph of
>> section 5.2.6 is unnecessary and those sentences should be removed.
>>=20
>> -------------------------------------------------------------------------=
--------------------------------
>>=20
>> In the Security Considerations section, in the 3rd paragraph, you point
>> out the potential issues with allowing write and create access.  In the
>> same paragraph, you then go on to say "allowed to access and GET"
>> MIB objects.  I suggest deleting "and GET" from this paragraph.
>>=20
>> -------------------------------------------------------------------------=
--------------------------------
>>=20
>> In the IANA Considerations section, given this is an overview document,
>> I think you are safe in at least starting off with the basic "IANA has no=

>> actions" text found in most IDs of this type.  It is fairly certain that
>> this
>> will not change, so you might as well get it out of the way.
>>=20
>> =3D=3D=3D
>> Eric
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>=20
>>=20
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>=20
>>=20
>=20

From eric.gray@ericsson.com  Sun Jul 11 15:35:15 2010
Return-Path: <eric.gray@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D0B528C0F6; Sun, 11 Jul 2010 15:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.499
X-Spam-Level: 
X-Spam-Status: No, score=-4.499 tagged_above=-999 required=5 tests=[AWL=1.500,  BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_MED=-4]
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 yX7mI7EoX1L6; Sun, 11 Jul 2010 15:35:13 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 77C493A6844; Sun, 11 Jul 2010 15:35:13 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o6BMhVlP001454; Sun, 11 Jul 2010 17:43:31 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.117]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Sun, 11 Jul 2010 18:35:11 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>, "Andrew G. Malis" <agmalis@gmail.com>
Date: Sun, 11 Jul 2010 18:35:09 -0400
Thread-Topic: [mpls] MPLS-TP management overview draft - draft-farrel-mpls-tp-mib-management-overview
Thread-Index: AcshSN04ux2QjVnPTa+sE7NkUri7yAAAC0Ag
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F1053B98774D@EUSAACMS0701.eamcs.ericsson.se>
References: <C0AC8FAB6849AB4FADACCC70A949E2F1053B72289E@EUSAACMS0701.eamcs.ericsson.se> <829184DB-D53C-4B1A-9BDD-3C4762EBF978@lucidvision.com> <AANLkTil9EPC7Xlss8wIV8MtKBkZg6eepiqjfwv8Wu0Ie@mail.gmail.com> <437A4733-6E9E-4700-8238-75AC4E88E8C3@lucidvision.com>
In-Reply-To: <437A4733-6E9E-4700-8238-75AC4E88E8C3@lucidvision.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: A S Kiran Koushik <kkoushik@cisco.com>, "mpls@ietf.org" <mpls@ietf.org>, Daniel King <daneil@olddog.co.uk>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, Venkatesan Mahalingam <venkatesan.mahalingam@aricent.com>
Subject: Re: [mpls] MPLS-TP management overview draft - draft-farrel-mpls-tp-mib-management-overview
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jul 2010 22:35:15 -0000

Tom,

	I would support the approach Andy suggests.  This is supposed
to be an overview for management in MPLS-TP networks - hence it must
at least touch on the set of reasonable possibilties we are aware of
at the present time.

--
Eric=20

-----Original Message-----
From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]=20
Sent: Sunday, July 11, 2010 6:28 PM
To: Andrew G. Malis
Cc: Eric Gray; A S Kiran Koushik; Daniel King; Venkatesan Mahalingam; mpls@=
ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls] MPLS-TP management overview draft - draft-farrel-mpls-t=
p-mib-management-overview

I'm not disputing that; just ask that we are clearly separating things.

Sent from my iPhone

On Jul 11, 2010, at 1:12 PM, "Andrew G. Malis" <agmalis@gmail.com> wrote:

> Tom,
>=20
> While MPLS-TP can be run in a static environment, there will be
> dynamically signaled deployments as well. As such, Eric is correct
> that GMPLS-related MIBs should be included in the draft. There should
> probably be an additional sub-section in section 6 to say that the
> applicability for GMPLS MIBs would be for networks that are using
> dynamically signaled LSPs.
>=20
> Cheers,
> Andy
>=20
> On Thu, Jul 8, 2010 at 3:42 PM, Thomas Nadeau <tnadeau@lucidvision.com> w=
rote:
>>=20
>> Why are we including GMPLS-related MIBs in this?  I'd like to not confus=
e
>> the fact that the basic version of TP is supposed to be static, and hand=
led
>> (managed) as such. If you do talk about GMPLS MIBs in there, then I'd li=
ke
>> to be very clear that it is optional.
>> --Tom
>>=20
>> Authors,
>>=20
>>     Some comments on your draft...
>>=20
>>     As a general comment, in addition to the MIBs already explicitly
>> referenced in this draft, you should probably
>> include:
>>=20
>> o RFC 4801 ( "Definitions of Textual Conventions for Generalized
>> Multiprotocol Label Switching (GMPLS) Management " ),
>> o RFC 4802 ("Generalized Multiprotocol Label Switching (GMPLS) Traffic
>> Engineering Management Information Base"),
>> o RFC 4220 ("Traffic Engineering Link Management Information Base");
>>=20
>> As is, there is a curious dearth of MIB references for GMPLS related MIB=
s,
>> given GMPLS will be the signaling
>> method used for MPLS-TP LSPs.
>>=20
>>     NITs:
>>     =3D=3D=3D
>>=20
>> "functionss" is usually spelled with one "s" (page 7)
>>=20
>> "exchaging" usually includes another "n" (page 7)
>>=20
>> "MPLS packets are encapsulated by using its own header" doesn't
>> parse (page 7).  The second sentence in the same paragraph is just
>> barely more readable.  I would suggest re-writing the paragraph using
>> the phrase "label-stack" to replace "header."  This also eliminates the
>> need to identify the "header" as a "label-stack."
>>=20
>> "path(" needs a space (page 8).
>>=20
>> Change "The two important .." to "Two important ..." (page 8).  The
>> "two important applications" should be in bullet format.
>>=20
>> "a MPLS" should be "an MPLS" anywhere that the indefinite article is
>> used in conjunction with "MPLS."
>>=20
>> In the 5th paragraph on page 10, to what does "The document" refer?
>>=20
>> Page 11 contains a number of examples where the first word following
>> a colon (":") is capitalized; this is not proper English - particularly =
when
>> the text following the colon is not in the form of a bulleted list.  I d=
id
>> not
>> check the entire draft for this, but suggest the authors should.
>>=20
>> In the 2nd sentence, 7th paragraph of page 11, to what does "This MIB
>> module" refer?
>>=20
>> The 2nd sentence in section 5.2.9 (top of page 13) does not parse.  I
>> suggest breaking this sentence down and clarifying what is meant by it.
>>=20
>> The 2nd paragraph in section 5.2.10 (page 13) does not completely
>> describe the notation used.  An arrow indicates a dependency between
>> two MIB modules, but is clearly a directed dependency and meaning
>> is not clear: I suggest using a more illustrative example by making the
>> following change:
>>=20
>> Change -
>> A relationship "MIB module A depends on MIB module B" means that
>> MIB module A uses an object, object identifier, or textual convention
>> defined in MIB module B, or that MIB module A contains a pointer
>> (index or RowPointer) to an object in MIB module B.
>> To -
>> The relationship "A --> B" means A depends on B and that MIB module
>> A uses an object, object identifier, or textual convention defined in MI=
B
>> module B, or that MIB module A contains a pointer (index or RowPointer)
>> to an object in MIB module B.
>> (Note that I am assumng I have the order of dependency correct, based
>> on conventional "logical dependency" - I did not verify this be analyzin=
g
>> the diagram on page 14)
>>=20
>> I suggest restructuring the last paragraph on page 16 (continuing on to
>> page 17) as two paragraphs, each including bulleted lists, as follows:
>>=20
>> "The following MPLS-TP OAM functionalities can be achieved using the
>>  MPLSTP-OAM-STD-MIB mib extensions:
>>=20
>>     o    Continuity Check and Connectivity Verification,
>>     o    Alarm Reporting, Diagnostic,
>>     o    Route Tracing,
>>     o    Loopback tool,
>>     o    Lock Instruct,
>>     o    Lock Reporting Remote Defect Indication,
>>     o    Client Failure Indication,
>>     o    Packet Loss Measurement and
>>     o    Packet Delay Measurement
>>=20
>> "MPLS-TP OAM managed objects are defined based on the drafts:
>>     o    draft-ietf-mpls-tp-oam-requirements-06,
>>     o    draft-ietf-mpls-tp-oam-framework-06 and
>>     o    draft-ietf-mpls-tp-identifiers-01."
>>=20
>> The last paragraph on page 17 (continuing on to page 18) has the same
>> problem as the 2nd paragraph on page 13 (described above) and needs
>> a similar resolution.  One approach might be to include this as part of =
a
>> new section (under modified section 2 "Conventions and Terminology"),
>> so that it does not need to be repeated.
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
>>=20
>>     Not so NITty:
>>     =3D=3D=3D=3D=3D=3D=3D=3D=3D
>>=20
>> There are several problems with this paragraph (page 7):
>>=20
>> "The basic unit in an MPLS network is called LSR(Label switched
>>   router). It implements the control and forwarding plane of MPLS."
>>=20
>> o    as a NIT, "LSR(" needs a space;
>> o    the meaning of "basic unit" is not at all clear;
>> o    an LSR does not necessarily implement a control plane.
>> ------------------------------------------------------------------------=
---------------------------------
>>=20
>> The next paragraph is also inaccurate  (also page 7) .
>>=20
>> The control plane of an LSR is not directly responsible for exchanging
>> routing information (that is the control plane of the "router" part of a=
n
>> LSR, again not necessarily part of an LSR in the general sense).  This
>> "routing information" - if present - is simply one source of information
>> that an LSR uses to "program" (not the best wording choice - I suggest
>> "populate") forwarding tables.
>>=20
>> The LSR "control plane" provides information in terms of label bindings
>> which are part of the information used to populate forwarding tables in
>> an LSR.  An LSR determines which label bindings to seek and retain
>> based on configuration and other information (such as that which may
>> be provided by routing).
>>=20
>> While the primary intent (and common implementation) relies on use of
>> the 20 bit label as an "index into a forwarding table", this is not the =
only
>> way that an LSR may be implemented, nor is it necessarily presumed
>> to be implemented this way.  This misconception is at the bottom of a
>> number of bad ideas that have been proposed in the MPLS WG (as well
>> as other places).  How an LSR chooses to employ the 20 bit labels it
>> assigns for use by its peers is entirely up to the implementation.
>>=20
>> ------------------------------------------------------------------------=
---------------------------------
>>=20
>> The remaining paragraphs in the section are slightly inaccurate as well.
>>=20
>> At "MPLS ingress", a "label stack" is prefixed.  In the simplest case, t=
he
>> "label stack" comprises a single label-stack entry.
>>=20
>> At LSP ingress (because of the possibility of nested - or hierarchical -
>> LSPs), there is the possibility that one or more additional label-stack
>> entries will be "pushed" onto the label stack - if there is a label stac=
k
>> present already. Otherwise, the paragraph above applies.
>>=20
>> In at least the first case, there is more to "encapsulating" the packet
>> than simply prefixing an MPLS label (stack).  It is also necessary to
>> add the appropriate "MPLS-specific" L2 encapsulation (including, for
>> instance, the MPLS PID).
>>=20
>> For all "swap", "pop" and "push" operations, one or more labels may
>> be involved.
>>=20
>> ------------------------------------------------------------------------=
---------------------------------
>>=20
>> I believe the last paragraph in section 5.2.6 (on page 12) is inaccurate=
.
>> A device that terminates an ATM pseudo-wire will almost certainly offer
>> an ATM interface to other devices (otherwise, what is the point of using
>> an ATM pseudowire?).  If it does, it will necessarily have to include th=
at
>> interface as part of the ifTable.
>>=20
>> In any case, inclusion of the last two sentence in the last paragraph of
>> section 5.2.6 is unnecessary and those sentences should be removed.
>>=20
>> ------------------------------------------------------------------------=
---------------------------------
>>=20
>> In the Security Considerations section, in the 3rd paragraph, you point
>> out the potential issues with allowing write and create access.  In the
>> same paragraph, you then go on to say "allowed to access and GET"
>> MIB objects.  I suggest deleting "and GET" from this paragraph.
>>=20
>> ------------------------------------------------------------------------=
---------------------------------
>>=20
>> In the IANA Considerations section, given this is an overview document,
>> I think you are safe in at least starting off with the basic "IANA has n=
o
>> actions" text found in most IDs of this type.  It is fairly certain that
>> this
>> will not change, so you might as well get it out of the way.
>>=20
>> =3D=3D=3D
>> Eric
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>=20
>>=20
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>=20
>>=20
>=20

From eosborne@cisco.com  Mon Jul 12 07:39:40 2010
Return-Path: <eosborne@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFD0F3A6985; Mon, 12 Jul 2010 07:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MneXOeZx2THw; Mon, 12 Jul 2010 07:39:36 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 074A43A63EC; Mon, 12 Jul 2010 07:39:34 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJfGOkytJV2d/2dsb2JhbACgPnGkZZpJhScEg3uGfw
X-IronPort-AV: E=Sophos;i="4.55,188,1278288000"; d="scan'208";a="131356791"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rtp-iport-1.cisco.com with ESMTP; 12 Jul 2010 14:33:13 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id o6CEXDII020865;  Mon, 12 Jul 2010 14:33:13 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 12 Jul 2010 09:33:13 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Jul 2010 09:33:12 -0500
Message-ID: <D29E470202D67745B61059870F433B5402245F75@XMB-RCD-202.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02
Thread-Index: AcshyL90GhPgcnxAQ9GjiNSI5C9EEQ==
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: <pwe3@ietf.org>, <mpls@ietf.org>, <mpls-tp@ietf.org>, <ccamp@ietf.org>
X-OriginalArrivalTime: 12 Jul 2010 14:33:13.0137 (UTC) FILETIME=[287C4210:01CB21CF]
Subject: [mpls] Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2010 14:39:40 -0000

I have a few questions.  Nothing major, as the draft is in general
pretty solid.



1) Section 4.1 reviews existing GMPLS functionality and describes
applicability to TP.  Section 4.1.8 defines LSP hierarchy but doesn't
say anything about how it applies to TP.  It probably needs a line like
"Hierarchical LSPs may be used in MPLS-TP at the discretion of the
network operator" or something similar ot what's in other subsections of
4.1.


2) Some of section 4.1.9 is out of sync with the surviveability
framework (draft-ietf-mpls-tp-survive-fwk)

 - survive-fwk draws a distinction between protection and restoration
that  cp-framework lumps under 'recovery'.  It may be worth calling out
both protection and restoration as separate things.

- Section 4.1.9 lists five recovery types:

     - 1+1 bidirectional protection for P2P LSPs
     - 1+1 unidirectional protection for P2MP LSPs
     - 1:n (including 1:1) protection with or without extra traffic
     - Rerouting without extra traffic (sometimes known as soft
       rerouting), including shared mesh restoration
     - Full LSP rerouting


I don't see where these five types come from.  rfc5654 requirements R65
and R67 list five MUST types (bidir 1+1 p2p, unidir 1+1 p2p, unidir 1+1
p2mp, bidir 1:n p2p, unidir 1:n p2mp) and one optional (undir 1:n p2p).
R68 requires 1:n (including 1:1) ahread mesh recovery. =20

How do the five types in section 4.1. 9 map to the requirements in
rfc5654?  At first glance I don't see unidir 1+1 p2p in sec. 4.1.9,
although perhaps it's implied in 'rerouting without extra traffic'.
'Full LSP rerouting' also seems like it may mean something specific to
whomever wrote it but as far as I can tell there's no explicit
definition of 'Full LSP rerouting' (as opposed to partial?  as opposed
to something other than rerouting?) anywhere in rfc5654 or survive-fwk.
And 'soft rerouting appears to be survive-fwk's 'soft restoration'.

3) Section 4.1.9, "it's use is not precluded" , s/it's/its/


4) Section 4.4.1 is entitled "MPLS to MPLS-TP Interworking".  The
section talks about " interworking of MPLS-TE and GMPLS control plane",
so shouldn't the section be "MPLS-TE to MPLS-TP Interworking"?  Unless
things like LDP-to-TP interworking are in someone's plans, I think "TE
to TP Interworking" is a better fit.







eric


From ehudd@orckit.com  Mon Jul 12 08:09:44 2010
Return-Path: <ehudd@orckit.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61AF33A6972 for <mpls@core3.amsl.com>; Mon, 12 Jul 2010 08:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level: 
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[AWL=-1.800, BAYES_50=0.001, EXTRA_MPART_TYPE=1, HTML_MESSAGE=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 Yv-35ubE3xa8 for <mpls@core3.amsl.com>; Mon, 12 Jul 2010 08:09:39 -0700 (PDT)
Received: from tlvmail1.orckit.com (tlvmail1.orckit.com [213.31.203.2]) by core3.amsl.com (Postfix) with ESMTP id 09FC03A6927 for <mpls@ietf.org>; Mon, 12 Jul 2010 08:09:37 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
x-cr-hashedpuzzle: Uok= DHak EDW9 GVID NCRU NfNi OH7p OjZ1 PkFH QdGC QyEE RiNG Rlok SAGh S/nh TkO+; 2; bQBhAGMAaABAAGgAdQBhAHcAZQBpAC4AYwBvAG0AOwBtAHAAbABzAEAAaQBlAHQAZgAuAG8AcgBnAA==; Sosha1_v1; 7; {117B1D5D-EB08-4C85-97E2-54D4F7624393}; ZQBoAHUAZABkAEAAbwByAGMAawBpAHQALgBjAG8AbQA=; Mon, 12 Jul 2010 15:09:38 GMT; UgBlAHQAdQByAG4AIABwAGEAdABoACAAcwBwAGUAcwBpAGYAaQBlAGQAIABMAFMAUAAgAFAAaQBuAGcAIABkAHIAYQBmAHQAIAAgAC0AIAByAGUAcQB1AGkAcgBlAGQAIAB1AHAAZABhAHQAZQBzAA==
MIME-Version: 1.0
Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01CB21D4.4235CDEC"
x-cr-puzzleid: {117B1D5D-EB08-4C85-97E2-54D4F7624393}
Content-class: urn:content-classes:message
Date: Mon, 12 Jul 2010 18:09:38 +0300
Message-ID: <44F4E579A764584EA9BDFD07D0CA081305E35619@tlvmail1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Return path spesified LSP Ping draft  - required updates
Thread-Index: Acsh1D7u6gsU66+4QPepF7sNaQPIfw==
From: "Ehud Doron" <ehudd@orckit.com>
To: "Mach Chen" <mach@huawei.com>
Cc: mpls@ietf.org, Ofer Dayan <Oferd@orckit.com>, Yossi Fridman <Yossifr@orckit.com>, Shai Bromberg <ShaiB@orckit.com>, Nir Ben Avraham <nirb@orckit.com>, Rafi Ram <RafiR@orckit.com>, Ronen Solomon <RonenS@orckit.com>
Subject: [mpls] Return path spesified LSP Ping draft  - required updates
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2010 15:09:44 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB21D4.4235CDEC
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01CB21D4.4235CDEC"


------_=_NextPart_002_01CB21D4.4235CDEC
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Mach

=20

Kindly we would like to suggest the following enhancements for the
Return path specified LSP Ping next draft.

=20

1.       Reply Path (RP) Return Code

Following our last discussions please find attached our suggestions for
RP Return Code.

=20

The RP return code shall be part of RP TLV. The RP TLV shall have the
following structure:

0                              7  8                                15 16
23 24                            31

RP return code

RP return sub-code

RP sub-TLVs

=20

=20

The Reply Path Return Code it a dedicated return code for RP operations
(separated from the forward return code  in Echo Reply header). It used
by the forward LSP Tail End to report the forward LSP Head End about the
actions he took while selecting the RP. The forward LSP Tail End can set
it to one of the values listed below. The RP Return Subcode must be set
to zero.

=20

  Value Meaning

----------------------

0 - No return code

1 - Malformed RP TLV was received

2 - One or more of the sub-TLVs in RP TLV was not understood

3 - The echo reply was sent successfully using the specified RP=20

4 - The specified RP was not found, the echo reply was sent via other
LSP

5 - The specified RP was not found, the echo reply was sent via IP path

6 - The Reply mode in echo request was not set to 5 (replay via
specified path) although RP TLV exists

7 - RP TLV was missing in echo reply

=20

Examples of usage of this return code:

If the RP TLV contains IPv4 RSVP-TE tunnel sub-TLV and the flag fields
are P=3D1 S=3D1, it is required to set the RP Return Code to 2 , "One or
more of the sub-TLVs in RP TLV was not understood". Here it is required
to use the default return path.

=20

If the Reply Mode field in the received echo request is equal to "Reply
via specified path" and no RP TLV exists in the echo request, it is
required to set the RP Return Code to "RP TLV was missing in echo
reply". Here it is required to use the default return path.

=20

=20

2.       New sub-TLV for RP EXP=20

In addition, we conclude that it is required to add new sub-TLV to RP
TLV  the RP EXP sub-TLV. This TLV is used by the originator of the echo
request to specify the echo reply sender which EXP bits to use while
sending the echo reply in the specified LSP. This TLV is similar in its
sense to Reply TOS Byte TLV for IP reply path (as defined in RFC4379).

RP EXP sub-TLV structure:

0              2              7  8                                15 16
23 24                            31

RP EXP bit

Must be Zero

=20

We think that this sub-TLV is essential and must be added.=20

=20

=20

=20

Please refer

=20

=20

Ehud    Doron

System Architect=20

Orckit - Corrigent

ehudd@orckit.com <mailto:username@orckit.com>   =20

Tel: 972-3-69456327

www.orckit.com <http://www.orckit.com/> =20

=20

  <http://www.orckit.com/>=20

Pushing technology to the edge

=20

=20


------_=_NextPart_002_01CB21D4.4235CDEC
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Miriam;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:181749384;
	mso-list-type:hybrid;
	mso-list-template-ids:-562007378 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hi Mach<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Kindly we would like to suggest the following =
enhancements for
the Return path specified LSP Ping next draft.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><b><span
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></b><![endif]><span dir=3DLTR></span><b>Reply Path (RP) =
Return Code<o:p></o:p></b></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>Following our last =
discussions
please find attached our suggestions for RP Return Code.<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>The RP return code =
shall be part
of RP TLV. The RP TLV shall have the following structure:<o:p></o:p></p>

<table class=3DMsoNormalTable border=3D1 cellspacing=3D0 cellpadding=3D0
 style=3D'border-collapse:collapse;border:none'>
 <tr>
  <td width=3D616 colspan=3D2 valign=3Dtop =
style=3D'width:462.15pt;border:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal =
style=3D'margin-bottom:6.0pt;text-align:justify'><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  7&nbsp; =
8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  15
  =
16&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  23 =
24&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
  31<o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D307 valign=3Dtop style=3D'width:3.2in;border:solid =
windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter =
style=3D'margin-bottom:6.0pt;text-align:center'><span
  style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>RP =
return code<o:p></o:p></span></p>
  </td>
  <td width=3D309 valign=3Dtop =
style=3D'width:231.75pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid =
windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter =
style=3D'margin-bottom:6.0pt;text-align:center'><span
  style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>RP =
return
  sub-code<o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D616 colspan=3D2 valign=3Dtop =
style=3D'width:462.15pt;border:solid windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt;border:solid windowtext =
1.0pt !msorm;
  border-top:none !msorm;padding:0in 5.4pt 0in 5.4pt !msorm'>
  <p class=3DMsoNormal align=3Dcenter =
style=3D'margin-bottom:6.0pt;text-align:center'><span
  style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>RP =
sub-TLVs<o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>The Reply Path Return =
Code it a
dedicated return code for RP operations (<b><u>separated</u></b> from =
the
forward return code &nbsp;in Echo Reply header). It used by the forward =
LSP
Tail End to report the forward LSP Head End about the actions he took =
while
selecting the RP. The forward LSP Tail End can set it to one of the =
values
listed below. The RP Return Subcode must be set to zero.<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>&nbsp;&nbsp;Value =
Meaning<o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in'>----------------------<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>0 - No return =
code<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>1 - Malformed RP TLV =
was received<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>2 - One or more of the =
sub-TLVs in
RP TLV was not understood<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>3 - The echo reply was =
sent
successfully using the specified RP <o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>4 - The specified RP =
was not
found, the echo reply was sent via other LSP<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>5 - The specified RP =
was not
found, the echo reply was sent via IP path<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>6 - The Reply mode in =
echo request
was not set to 5 (replay via specified path) although RP TLV =
exists<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>7 - RP TLV was missing =
in echo
reply<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>Examples of usage of =
this return
code:<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>If the RP TLV contains =
IPv4
RSVP-TE tunnel sub-TLV and the flag fields are P=3D1 S=3D1, it is =
required to set
the RP Return Code to 2 , &#8220;One or more of the sub-TLVs in RP TLV =
was not
understood&#8221;. Here it is required to use the default return =
path.<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>If the Reply Mode field =
in the
received echo request is equal to &quot;Reply via specified path&quot; =
and no
RP TLV exists in the echo request, it is required to set the RP Return =
Code to
&#8220;RP TLV was missing in echo reply&#8221;. Here it is required to =
use the default
return path.<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><b><span
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></b><![endif]><span dir=3DLTR></span><b>New sub-TLV for RP =
EXP <o:p></o:p></b></p>

<p class=3DMsoListParagraph>In addition, we conclude that it is required =
to add new
sub-TLV to RP TLV &nbsp;the RP EXP sub-TLV. This TLV is used by the =
originator
of the echo request to specify the echo reply sender which EXP bits to =
use
while sending the echo reply in the specified LSP. This TLV is similar =
in its
sense to Reply TOS Byte TLV for IP reply path (as defined in =
RFC4379).<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'>RP EXP sub-TLV =
structure:<o:p></o:p></p>

<table class=3DMsoNormalTable border=3D1 cellspacing=3D0 cellpadding=3D0
 style=3D'border-collapse:collapse;border:none'>
 <tr>
  <td width=3D616 colspan=3D2 valign=3Dtop =
style=3D'width:462.15pt;border:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal =
style=3D'margin-bottom:6.0pt;text-align:justify'><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;
  =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
  7&nbsp; 8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;15
  =
16&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  23
  =
24&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
  31<o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D79 valign=3Dtop style=3D'width:59.4pt;border:solid =
windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter =
style=3D'margin-bottom:6.0pt;text-align:center'><span
  style=3D'font-size:10.0pt;font-family:"Times New Roman","serif"'>RP =
EXP bit<o:p></o:p></span></p>
  </td>
  <td width=3D537 valign=3Dtop =
style=3D'width:402.75pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid =
windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal align=3Dcenter =
style=3D'margin-bottom:6.0pt;text-align:center'><span
  style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Must =
be Zero<o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'text-indent:.25in'>We think that this =
sub-TLV is
essential and must be added. <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Please refer<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Comic =
Sans MS";
color:gray'>Ehud&nbsp;&nbsp;&nbsp; Doron</span><span =
style=3D'font-family:"Comic Sans MS"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Comic =
Sans MS";
color:gray'>System Architect </span><span style=3D'font-family:"Comic =
Sans MS"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Comic =
Sans MS";
color:gray'>Orckit - Corrigent</span><span style=3D'font-family:"Comic =
Sans MS"'><o:p></o:p></span></p>

<p class=3DMsoNormal><u><span =
style=3D'font-size:10.0pt;color:blue'>ehudd<a
href=3D"mailto:username@orckit.com" =
title=3D"mailto:username@orckit.com"><span
style=3D'color:blue'>@orckit.com</span></a></span></u><span =
style=3D'font-size:
10.0pt;color:#1F497D'>&nbsp;&nbsp; </span><o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;color:gray'>Tel:
972-3-69456327</span><o:p></o:p></p>

<p class=3DMsoNormal><a href=3D"http://www.orckit.com/"
title=3D"http://www.orckit.com/"><span =
style=3D'font-size:10.0pt;color:blue'>www.orckit.com</span></a><span
style=3D'font-size:10.0pt;color:#1F497D'> </span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p class=3DMsoNormal><a href=3D"http://www.orckit.com/"
title=3D"http://www.orckit.com/"><span =
style=3D'color:gray;text-decoration:none'><img
border=3D0 width=3D109 height=3D51 id=3D"Picture_x0020_1"
src=3D"cid:image001.jpg@01CB21A8.53E4FF90" =
alt=3Dlogo-orckit-corrigent></span></a><o:p></o:p></p>

<p class=3DMsoNormal><i><span =
style=3D'font-size:10.0pt;color:gray'>Pushing
technology to the edge</span></i><o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_002_01CB21D4.4235CDEC--

------_=_NextPart_001_01CB21D4.4235CDEC
Content-Type: image/jpeg;
	name="image001.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image001.jpg@01CB21A8.53E4FF90>
Content-Description: image001.jpg
Content-Location: image001.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAzAG0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD2aiis
vWtZj0mFeN88nEcY5J/Cmk27Imc1CPNLYyde8a2+n3UllagyTx8OQM4PoK5xvHOpJIC6FQegZiM/
piulTw9qOov9qvrwWjvyUt0XcPq3rWPqR02ykNuPFti8nQwXroyn2OOldUZUoqzVzzKtPFVG5Rk0
um3+ZqaJ40hv3ENwpST0PX6j1/nXVKwZQykEEZBHevMtf8Orp1rDrOlzRyWxwZPIfcsbeqn+7muq
8O6/aDTljv7y2tpVxhJZlU4IzjBP+cipqwhy88DXDVaym6Vbfv3OloqOKaKeMSQypIh6MjAg/iKZ
d3tpYQma8uYreMfxyuFH5muY9AnorLsvE2hajP5Fnq9nPKeiJMpJ+g71Zi1XT576SwivYHuo8l4F
kBdceo696ALdFUn1jTIr9dPe/t1u2xiAyDec/wCz1oj1jTJbma2jv7d5rcFpo1kBaMDqSO2KALtF
ZH/CWeHf+g5p/wD4EL/jV6y1Cz1KEzWN1DcxBtpeJwwB9MigCxXCNd/bfiWsc5/dwNtjU9Mhcj9T
Xd15l4ugn0jxX9ujyomIljb/AGh1H6V0YdJya7o8/MG401Pomm/QufFbWb62g07RLCY27anIVklB
wduQMZ7AlufpWnp/wv8ACtnYLbzact3Jt+eeZjuY9yMHj8Kq63p2n/Ebw/CkdytrqFud8TH+Bu4P
sf8ACqdvqvxM0qBbGbQLbUnQbUuhKBuHYnkZ/SsJRcXZndCcZxUovQwrixPgjxwNAtJ3l0jV4sNb
u27ZuyAfqCOvpUHhmPw4fF+tHxGtkYQkflm7AxuwM4z3xV240XU7K8l8Q+KLmOXWbhTHaWkJyIcj
G449AeAO5rV0HwFcS6lrZ1yzjNhqMKLFhwXBGOcfwkVTi1C5mqkXVcVulqVPCaQQ/Eac+FEn/wCE
fMB+04DeRvxxsz74/XtVLw1p4+JnifUdT16V5bSyYLDZhyFAJOB9MDn1Jrr/AApba/4bMmk6zJBP
pcRxZ3zTKrheysp/z+FY994M1/w9r82ueDJoXjuSWmspjhTk5IHYjPTkEVBsdOvgLwvHcW9xBpEE
E1tIskUkWVIIOR9fxryvVvENz4Z+I3iC/s4RJO4eJGIyIydvzH1xj8672z1n4hX13BDL4ds7CHzF
8+d5t2Fz820Z64+tUrHwZfTfELW73U7BW0m/ikjDF1O/O3HGcjofyoA0fh94Ys7KwXXpbpdR1LUF
8yS7J3YB6qp/nXP+D4o5viz4mikQMjrMrKe4LrkVq+DtD8R+ENcuNLMJvNBlctFP5i7oj67c59iP
XmneF/DWrad8Rta1e6tRHZXXmeTJ5indlwRwDkcCgDmPiF4e0fS/FXh+1sdOgt4bhwJURcBxvUc/
ga9Y0zSdP0a2NtptpFawsxcpGMAn1/SuN8eeGtX1rxPod7p9qJYLRwZm8xV2/Op6E88Cu+oAKoax
o9prdi1rdLkdVcdUPqKv1SuJbtWIRPl7EU07aoTSaszzu78I6/pFwXtFa5QfdkhOGx7iprdvGsuI
Y47tAeMuAoH4mu1M913LflSefdf3mro+sya1SZ5/9nU07wk15JmboPhF7W6Go6vN9qvOqgnKofXn
qa6isxJ7zPAJ+oq/A0jJmVQDWM5ubuzspUYUo8sEUruMx6iLqS0a6i8rYoQBjGckng+vHPtUd/8A
bhIn2VZkXyx5SxhdofPR8/w4x09/ataioNSi0d4bi7k8x9ojAgQY2528n1zn1pIYrqMWQd3lIBMz
vjOSvt7+lX6KAMDTru7nu5IkmleZbdzIsm0xrLkAYxzjr+HvUtuNVbT7gNJKJyFCFkGVb+LB6Efp
WwFVSSFAzycDrTqAMiWC82Qh3uHEN5kMpG5o9pAz6jJrXoooAKKKKAEwPSjA9KKKAFooooAKKKKA
CiiigAooooAKKKKAP//Z

------_=_NextPart_001_01CB21D4.4235CDEC--

From root@core3.amsl.com  Mon Jul 12 08:45:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 2FEE33A6824; Mon, 12 Jul 2010 08:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100712154502.2FEE33A6824@core3.amsl.com>
Date: Mon, 12 Jul 2010 08:45:02 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D ACTION:draft-ietf-mpls-tp-oam-framework-07.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2010 15: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 Multiprotocol Label Switching Working Group of the IETF.

	Title		: MPLS-TP OAM Framework
	Author(s)	: D. Allan, I. Busi, B. Niven-Jenkins, A. Fulignoli, E. Hernandez-Valencia, L. Levrau, D. Mohan, V. Sestito, N. Sprecher, H. Helvoort, M. Vigoureux, Y. Weingarten, R. Winter
	Filename	: draft-ietf-mpls-tp-oam-framework-07.txt
	Pages		: 56
	Date		: 2010-7-12
	
The Transport Profile of Multi-Protocol Label Switching 
   (MPLS-TP) is a packet-based transport technology based on the 
   MPLS Traffic Engineering (MPLS-TE) and Pseudowire (PW) data 
   plane architectures. 

   This document describes a framework to support a comprehensive 
   set of Operations, Administration and Maintenance (OAM) 
   procedures that fulfill the MPLS-TP OAM requirements for fault, 
   performance and protection-switching management and that do not 
   rely on the presence of a control plane. 

   This document is a product of a joint Internet Engineering Task 
   Force (IETF) / International Telecommunications Union 
   Telecommunication Standardization Sector (ITU-T) effort to 
   include an MPLS Transport Profile within the IETF MPLS and PWE3 
   architectures to support the capabilities and functionalities of 
   a packet transport network as defined by the ITU-T.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-oam-framework-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-mpls-tp-oam-framework-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-7-12084208.I-D@ietf.org>


--NextPart--


From root@core3.amsl.com  Mon Jul 12 09:15:05 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 542A43A6A1C; Mon, 12 Jul 2010 09:15:04 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100712161505.542A43A6A1C@core3.amsl.com>
Date: Mon, 12 Jul 2010 09:15:05 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-tp-cc-cv-rdi-01.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2010 16:15:05 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.


	Title           : Proactive Connection Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile
	Author(s)       : D. Allan, et al.
	Filename        : draft-ietf-mpls-tp-cc-cv-rdi-01.txt
	Pages           : 16
	Date            : 2010-07-12

Continuity Check (CC), Proactive Connectivity Verification (CV) and 
Remote Defect Indication (RDI) functionalities required for are MPLS-
TP OAM.  
 
Continuity Check monitors the integrity of the continuity of the path 
for any loss of continuity defect. Connectivity verification monitors 
the integrity of the routing of the path between sink and source for 
any connectivity issues. RDI enables an End Point to report, to its 
associated End Point, a fault or defect condition that it detects on 
a PW, LSP or Section. 
 
This document specifies methods for proactive CV, CC, and RDI for 
MPLS-TP Label Switched Path (LSP), PWs and Sections using 
Bidirectional Forwarding Detection (BFD). 
 

Requirements Language 

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
document are to be interpreted as described in RFC2119 [1].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-cc-cv-rdi-01.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-mpls-tp-cc-cv-rdi-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-12090408.I-D@ietf.org>


--NextPart--

From swallow@cisco.com  Mon Jul 12 13:32:39 2010
Return-Path: <swallow@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E19243A6C87; Mon, 12 Jul 2010 13:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.435
X-Spam-Level: 
X-Spam-Status: No, score=-9.435 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599, 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 XVNclhL8RsYR; Mon, 12 Jul 2010 13:32:33 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id CFC4E3A69FF; Mon, 12 Jul 2010 13:32:11 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAFAJ4YO0ytJV2Y/2dsb2JhbACBQ54TY3GlBpp5AoJcgkkEiEyCLg
X-IronPort-AV: E=Sophos;i="4.55,190,1278288000";  d="scan'208,217";a="131503398"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rtp-iport-1.cisco.com with ESMTP; 12 Jul 2010 20:32:05 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id o6CKW57V011207;  Mon, 12 Jul 2010 20:32:05 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 12 Jul 2010 15:32:05 -0500
Received: from 10.98.32.163 ([10.98.32.163]) by XMB-RCD-106.cisco.com ([72.163.62.148]) with Microsoft Exchange Server HTTP-DAV ;  Mon, 12 Jul 2010 20:32:04 +0000
User-Agent: Microsoft-Entourage/12.25.0.100505
Date: Mon, 12 Jul 2010 16:32:01 -0400
From: George Swallow <swallow@cisco.com>
To: venkatesan mahalingam <venkatflex@gmail.com>
Message-ID: <C860F401.275DD%swallow@cisco.com>
Thread-Topic: [PWE3] [mpls] [mpls-tp] mpls wg last call ondraft-ietf-mpls-tp-identifiers-01
Thread-Index: AcrxGuIPFXGqnEbSTAOCqYWtKQomNww5mYI3
In-Reply-To: <q2k715756491005061108r650202bfm6c36bc6d31a4b7cb@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3361797121_20969207"
X-OriginalArrivalTime: 12 Jul 2010 20:32:05.0309 (UTC) FILETIME=[4AA8F6D0:01CB2201]
Cc: mpls@ietf.org, ccamp@ietf.org, Attila Takacs <Attila.Takacs@ericsson.com>, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] [mpls-tp] mpls wg last call ondraft-ietf-mpls-tp-identifiers-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2010 20:32: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_3361797121_20969207
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

In line -


On 5/6/10 2:08 PM, "venkatesan mahalingam" <venkatflex@gmail.com> wrote:

> Hi George,
>>> >> Is it there to support associated unidirectional Tunnels/LSPs? If so=
 it
>>> should
>>> >> be called out in the text.
>=20
>> >That was not my original intent, but you are quite correct that this wo=
uld
>> >be very useful. =A0Particularly if the associated tunnels pass through a =
share
>> >mid-point somewhere along the path.
> VM: Can you please explain the original intention with an example?
>=20
> The original intent was to allow a compact form for a globally unique MEP=
-ID
> that is,
>=20
> Node_ID::Tunnel_Num::LSP_ID would be unique within an operator.  This req=
uires
> that Tunnel_Num be unique to the node (not the node pair).  That makes it
> impossible to coodinate the Tunnel_Num spaces across nodes, hence two tun=
nel
> numbers.
>=20
>>> >> -In Section 5.3 Mapping to GMPLS signaling does not use the
>>> Dst-Tunnel_Num. So
>>> >> this means that we may have two different tunnels identified with
>>> >> Src-Node_ID::Src-Tunnel_Num::
> Dst-Node_ID::Dst-Tunnel_Num. Is this intentional,
>>> >> e.g., the associated unidirectional case?
>=20
>> >For the associated unidirectional, this works perfectly. =A0For bidirecti=
onal,
>> >I was thinking of two options.
>=20
>> >1) =A0Strict binding =A0- =A0both ends are configure with the full identifier=
 and
>> >will only accept the connection if everything matches.
>=20
>> >2) =A0Dynamic binding - Source signals with just its Tunnel_Num. =A0RESV me=
ssage
>> >would carry back the destination's tunnel_num. =A0Note that both ends nee=
d
>> >both pieces for some of the OAM to work.
> VM: Do we need extensions in the RSVP-TE signaling to carry back the
> destination's tunnel_num in the RESV message?
>=20
> Yes, this and probably quite a few more.   Note that there is a draft for
> adding signaling of OAM capabilities in the works.
>=20
> ...George
>=20
> Thanks,
> Venkatesan Mahalingam
>=20
> On Fri, Apr 16, 2010 at 10:15 PM, George Swallow <swallow@cisco.com> wrot=
e:
>>=20
>>=20
>>=20
>> On 4/2/10 2:53 AM, "Attila Takacs" <Attila.Takacs@ericsson.com> wrote:
>>=20
>>> > Hi Matthew and George,
>>> >
>>> > Please find some comments/questions below.
>>> >
>>> > -In Section 5.1 you have:
>>> >
>>> > Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num
>>> >
>>> > What is the reason of having a Dst-Tunnel_Num besides the Src-Tunnel_=
Num?
>>=20
>> Existing implementations of RSVP-TE have used the tunnel space as global=
 to
>> the node. =A0It is difficult if not impossible to coordinate such spaces
>> between nodes. =A0In RSVP-TE the coordination does not matter, since the t=
ail
>> end of the tunnel doesn't have a real interface - it only receives and
>> usually with a PHP of the tunnel label, so the packets only belong to th=
e
>> physical interface.
>>=20
>> In a bidirectional world, separate tunnel spaces at the two ends becomes
>> useful.
>>=20
>> If this independence is not need is some environments then one can confi=
gure
>> just one value and use it in both fields.
>>=20
>>> > Is it there to support associated unidirectional Tunnels/LSPs? If so =
it
>>> should
>>> > be called out in the text.
>>=20
>> That was not my original intent, but you are quite correct that this wou=
ld
>> be very useful. =A0Particularly if the associated tunnels pass through a s=
hare
>> mid-point somewhere along the path.
>>=20
>>> > Same applies to the globally unique case.
>>=20
>> Of course.
>>=20
>>> > -In Section 5.2 you simply append one LSP_Num to the above. This is a=
 bit
>>> > confusing to me, if there are Src/Dst Tunnel_Nums then two LSP_Nums w=
ould
>>> be
>>> > needed too, wouldn't it?
>>=20
>> Once, you have independent tunnel-ids, coordination of the LSP numbers
>> becomes easy. =A0It also could be used to allow the two ends to readily
>> identify which is working and which is protection.
>>=20
>>> > -In Section 5.3 Mapping to GMPLS signaling does not use the
>>> Dst-Tunnel_Num. So
>>> > this means that we may have two different tunnels identified with
>>> > Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num. Is this
>>> intentional,
>>> > e.g., the associated unidirectional case?
>>=20
>> For the associated unidirectional, this works perfectly. =A0For bidirectio=
nal,
>> I was thinking of two options.
>>=20
>> 1) =A0Strict binding =A0- =A0both ends are configure with the full identifier =
and
>> will only accept the connection if everything matches.
>>=20
>> 2) =A0Dynamic binding - Source signals with just its Tunnel_Num. =A0RESV mes=
sage
>> would carry back the destination's tunnel_num. =A0Note that both ends need
>> both pieces for some of the OAM to work.
>>=20
>>> > This should be clarified.
>>=20
>> I'll see what I can do. =A0But this is not supposed to the MPLS-TP signali=
ng
>> draft.
>>=20
>>> > Hmm, maybe the Dst-Tunnel_Num should be omitted altogether.
>>=20
>> I'm planning to keep it.
>>=20
>>> > -Section 7 has a note saying to be aligned with the OAM fwk, is this =
still
>>> to
>>> > be done?
>>=20
>> Yes. =A0That draft is also being updated. =A0We appear to be converging.
>>=20
>>> > -In section 7.1.2.1 there is a discussion on Tunnel MEG IDs.
>>> > How would Tunnel and LSP MEGs be used? What OAM would run at the Tunn=
el
>>> level
>>> > and not at the LSP level?
>>> >
>>> > Do we need Tunnel MEG_IDs as defined in 7.1.2.1?
>>=20
>> I had been told early on that MEGs were needed for tunnels. =A0Now getting
>> comments that they are not (same comment is in the ITU liaison). =A0So I
>> planning to remove it, unless I hear other opinions.
>>=20
>>> > -Section 7.1.2.2, the Dst-Tunnel_Num question applies here too.
>>=20
>> See above.
>>=20
>>> > -Section 8 talks about open issues? When will these be addressed?
>>=20
>> Before it is re-issued. =A0Goal is end of next week.
>>=20
>> ...George
>>=20
>>> > Thanks,
>>> > Attila
>>> >
>>>> >> -----Original Message-----
>>>> >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
>>>> >> Behalf Of Loa Andersson
>>>> >> Sent: Friday, March 12, 2010 12:33 AM
>>>> >> To: mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ietf.org
>>>> >> Subject: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers=
-01
>>>> >>
>>>> >> All,
>>>> >>
>>>> >> this is to start an MPLS working group last call on
>>>> >> draft-ietf-mpls-tp-identifiers-01
>>>> >>
>>>> >> There is a discussion on the OAM model for MS-PWs where we
>>>> >> haven't been able to come to conclusion. Once we reach
>>>> >> agreement the document will be updated. Comments in this area
>>>> >> are welcome during the working group last call.
>>>> >>
>>>> >>
>>>> >> Please send your comments to the mpls-tp@ietf.org mailing list.
>>>> >>
>>>> >> The working group last ends eob April 2nd.
>>>> >>
>>>> >> /Loa
>>>> >>
>>>> >> --
>>>> >>
>>>> >> Loa Andersson
>>>> >>
>>>> >> Sr Strategy and Standards Manager
>>>> >> Ericsson ///
>>>> >> =A0 =A0phone: =A0+46 10 717 52 13
>>>> >> =A0 =A0 =A0 =A0 =A0 =A0+46 767 72 92 13
>>>> >>
>>>> >> =A0 =A0email: =A0loa.andersson@ericsson.com
>>>> >> =A0 =A0 =A0 =A0 =A0 =A0loa@pi.nu
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> _______________________________________________
>>>> >> mpls mailing list
>>>> >> mpls@ietf.org
>>>> >> https://www.ietf.org/mailman/listinfo/mpls
>>>> >>
>>> > _______________________________________________
>>> > mpls-tp mailing list
>>> > mpls-tp@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/mpls-tp
>>=20
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>=20
>=20


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

<HTML>
<HEAD>
<TITLE>Re: [PWE3] [mpls] [mpls-tp] mpls wg last call ondraft-ietf-mpls-tp-i=
dentifiers-01</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:14pt'>In line=
 -<BR>
<BR>
<BR>
On 5/6/10 2:08 PM, &quot;venkatesan mahalingam&quot; &lt;<a href=3D"venkatfle=
x@gmail.com">venkatflex@gmail.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'>Hi George,<BR>
&gt;&gt; Is it there to support associated unidirectional Tunnels/LSPs? If =
so it should<BR>
&gt;&gt; be called out in the text.<BR>
<BR>
&gt;That was not my original intent, but you are quite correct that this wo=
uld<BR>
&gt;be very useful. =A0Particularly if the associated tunnels pass through a =
share<BR>
&gt;mid-point somewhere along the path.<BR>
VM: Can you please explain the original intention with an example? <BR>
<BR>
The original intent was to allow a compact form for a globally unique MEP-I=
D that is,<BR>
<BR>
Node_ID::Tunnel_Num::LSP_ID would be unique within an operator. &nbsp;This =
requires that Tunnel_Num be unique to the node (not the node pair). &nbsp;Th=
at makes it impossible to coodinate the Tunnel_Num spaces across nodes, henc=
e two tunnel numbers.<BR>
<BR>
&gt;&gt; -In Section 5.3 Mapping to GMPLS signaling does not use the Dst-Tu=
nnel_Num. So<BR>
&gt;&gt; this means that we may have two different tunnels identified with<=
BR>
&gt;&gt; Src-Node_ID::Src-Tunnel_Num::<BR>
Dst-Node_ID::Dst-Tunnel_Num. Is this intentional,<BR>
&gt;&gt; e.g., the associated unidirectional case?<BR>
<BR>
&gt;For the associated unidirectional, this works perfectly. =A0For bidirecti=
onal,<BR>
&gt;I was thinking of two options.<BR>
<BR>
&gt;1) =A0Strict binding =A0- =A0both ends are configure with the full identifier=
 and<BR>
&gt;will only accept the connection if everything matches.<BR>
<BR>
&gt;2) =A0Dynamic binding - Source signals with just its Tunnel_Num. =A0RESV me=
ssage<BR>
&gt;would carry back the destination's tunnel_num. =A0Note that both ends nee=
d<BR>
&gt;both pieces for some of the OAM to work.<BR>
VM: Do we need extensions in the RSVP-TE signaling to carry back the destin=
ation's tunnel_num in the RESV message?<BR>
<BR>
Yes, this and probably quite a few more. &nbsp;&nbsp;Note that there is a d=
raft for adding signaling of OAM capabilities in the works.<BR>
<BR>
...George<BR>
<BR>
Thanks,<BR>
Venkatesan Mahalingam<BR>
<BR>
On Fri, Apr 16, 2010 at 10:15 PM, George Swallow &lt;<a href=3D"swallow@cisco=
.com">swallow@cisco.com</a>&gt; wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:14pt'><BR>
<BR>
<BR>
On 4/2/10 2:53 AM, &quot;Attila Takacs&quot; &lt;<a href=3D"Attila.Takacs@eri=
csson.com">Attila.Takacs@ericsson.com</a>&gt; wrote:<BR>
<BR>
&gt; Hi Matthew and George,<BR>
&gt;<BR>
&gt; Please find some comments/questions below.<BR>
&gt;<BR>
&gt; -In Section 5.1 you have:<BR>
&gt;<BR>
&gt; Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num<BR>
&gt;<BR>
&gt; What is the reason of having a Dst-Tunnel_Num besides the Src-Tunnel_N=
um?<BR>
<BR>
Existing implementations of RSVP-TE have used the tunnel space as global to=
<BR>
the node. =A0It is difficult if not impossible to coordinate such spaces<BR>
between nodes. =A0In RSVP-TE the coordination does not matter, since the tail=
<BR>
end of the tunnel doesn't have a real interface - it only receives and<BR>
usually with a PHP of the tunnel label, so the packets only belong to the<B=
R>
physical interface.<BR>
<BR>
In a bidirectional world, separate tunnel spaces at the two ends becomes<BR=
>
useful.<BR>
<BR>
If this independence is not need is some environments then one can configur=
e<BR>
just one value and use it in both fields.<BR>
<BR>
&gt; Is it there to support associated unidirectional Tunnels/LSPs? If so i=
t should<BR>
&gt; be called out in the text.<BR>
<BR>
That was not my original intent, but you are quite correct that this would<=
BR>
be very useful. =A0Particularly if the associated tunnels pass through a shar=
e<BR>
mid-point somewhere along the path.<BR>
<BR>
&gt; Same applies to the globally unique case.<BR>
<BR>
Of course.<BR>
<BR>
&gt; -In Section 5.2 you simply append one LSP_Num to the above. This is a =
bit<BR>
&gt; confusing to me, if there are Src/Dst Tunnel_Nums then two LSP_Nums wo=
uld be<BR>
&gt; needed too, wouldn't it?<BR>
<BR>
Once, you have independent tunnel-ids, coordination of the LSP numbers<BR>
becomes easy. =A0It also could be used to allow the two ends to readily<BR>
identify which is working and which is protection.<BR>
<BR>
&gt; -In Section 5.3 Mapping to GMPLS signaling does not use the Dst-Tunnel=
_Num. So<BR>
&gt; this means that we may have two different tunnels identified with<BR>
&gt; Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num. Is this inte=
ntional,<BR>
&gt; e.g., the associated unidirectional case?<BR>
<BR>
For the associated unidirectional, this works perfectly. =A0For bidirectional=
,<BR>
I was thinking of two options.<BR>
<BR>
1) =A0Strict binding =A0- =A0both ends are configure with the full identifier and=
<BR>
will only accept the connection if everything matches.<BR>
<BR>
2) =A0Dynamic binding - Source signals with just its Tunnel_Num. =A0RESV messag=
e<BR>
would carry back the destination's tunnel_num. =A0Note that both ends need<BR=
>
both pieces for some of the OAM to work.<BR>
<BR>
&gt; This should be clarified.<BR>
<BR>
I'll see what I can do. =A0But this is not supposed to the MPLS-TP signaling<=
BR>
draft.<BR>
<BR>
&gt; Hmm, maybe the Dst-Tunnel_Num should be omitted altogether.<BR>
<BR>
I'm planning to keep it.<BR>
<BR>
&gt; -Section 7 has a note saying to be aligned with the OAM fwk, is this s=
till to<BR>
&gt; be done?<BR>
<BR>
Yes. =A0That draft is also being updated. =A0We appear to be converging.<BR>
<BR>
&gt; -In section 7.1.2.1 there is a discussion on Tunnel MEG IDs.<BR>
&gt; How would Tunnel and LSP MEGs be used? What OAM would run at the Tunne=
l level<BR>
&gt; and not at the LSP level?<BR>
&gt;<BR>
&gt; Do we need Tunnel MEG_IDs as defined in 7.1.2.1?<BR>
<BR>
I had been told early on that MEGs were needed for tunnels. =A0Now getting<BR=
>
comments that they are not (same comment is in the ITU liaison). =A0So I<BR>
planning to remove it, unless I hear other opinions.<BR>
<BR>
&gt; -Section 7.1.2.2, the Dst-Tunnel_Num question applies here too.<BR>
<BR>
See above.<BR>
<BR>
&gt; -Section 8 talks about open issues? When will these be addressed?<BR>
<BR>
Before it is re-issued. =A0Goal is end of next week.<BR>
<BR>
...George<BR>
<BR>
&gt; Thanks,<BR>
&gt; Attila<BR>
&gt;<BR>
&gt;&gt; -----Original Message-----<BR>
&gt;&gt; From: <a href=3D"mpls-bounces@ietf.org">mpls-bounces@ietf.org</a> [<=
a href=3D"mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>] On<B=
R>
&gt;&gt; Behalf Of Loa Andersson<BR>
&gt;&gt; Sent: Friday, March 12, 2010 12:33 AM<BR>
&gt;&gt; To: <a href=3D"mpls@ietf.org">mpls@ietf.org</a>; <a href=3D"mpls-tp@ie=
tf.org">mpls-tp@ietf.org</a>; <a href=3D"pwe3@ietf.org">pwe3@ietf.org</a>; <a =
href=3D"ccamp@ietf.org">ccamp@ietf.org</a><BR>
&gt;&gt; Subject: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifier=
s-01<BR>
&gt;&gt;<BR>
&gt;&gt; All,<BR>
&gt;&gt;<BR>
&gt;&gt; this is to start an MPLS working group last call on<BR>
&gt;&gt; draft-ietf-mpls-tp-identifiers-01<BR>
&gt;&gt;<BR>
&gt;&gt; There is a discussion on the OAM model for MS-PWs where we<BR>
&gt;&gt; haven't been able to come to conclusion. Once we reach<BR>
&gt;&gt; agreement the document will be updated. Comments in this area<BR>
&gt;&gt; are welcome during the working group last call.<BR>
&gt;&gt;<BR>
&gt;&gt;<BR>
&gt;&gt; Please send your comments to the <a href=3D"mpls-tp@ietf.org">mpls-t=
p@ietf.org</a> mailing list.<BR>
&gt;&gt;<BR>
&gt;&gt; The working group last ends eob April 2nd.<BR>
&gt;&gt;<BR>
&gt;&gt; /Loa<BR>
&gt;&gt;<BR>
&gt;&gt; --<BR>
&gt;&gt;<BR>
&gt;&gt; Loa Andersson<BR>
&gt;&gt;<BR>
&gt;&gt; Sr Strategy and Standards Manager<BR>
&gt;&gt; Ericsson ///<BR>
&gt;&gt; =A0 =A0phone: =A0+46 10 717 52 13<BR>
&gt;&gt; =A0 =A0 =A0 =A0 =A0 =A0+46 767 72 92 13<BR>
&gt;&gt;<BR>
&gt;&gt; =A0 =A0email: =A0<a href=3D"loa.andersson@ericsson.com">loa.andersson@eric=
sson.com</a><BR>
&gt;&gt; =A0 =A0 =A0 =A0 =A0 =A0<a href=3D"loa@pi.nu">loa@pi.nu</a><BR>
&gt;&gt;<BR>
&gt;&gt;<BR>
&gt;&gt;<BR>
&gt;&gt;<BR>
&gt;&gt; _______________________________________________<BR>
&gt;&gt; mpls mailing list<BR>
&gt;&gt; <a href=3D"mpls@ietf.org">mpls@ietf.org</a><BR>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.i=
etf.org/mailman/listinfo/mpls</a><BR>
&gt;&gt;<BR>
&gt; _______________________________________________<BR>
&gt; mpls-tp mailing list<BR>
&gt; <a href=3D"mpls-tp@ietf.org">mpls-tp@ietf.org</a><BR>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mpls-tp">https://www.ie=
tf.org/mailman/listinfo/mpls-tp</a><BR>
<BR>
_______________________________________________<BR>
mpls mailing list<BR>
<a href=3D"mpls@ietf.org">mpls@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/m=
ailman/listinfo/mpls</a><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:14pt'><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3361797121_20969207--


From yry@cs.yale.edu  Mon Jul 12 15:18:46 2010
Return-Path: <yry@cs.yale.edu>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29DF73A6CAC for <mpls@core3.amsl.com>; Mon, 12 Jul 2010 15:18:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.073
X-Spam-Level: 
X-Spam-Status: No, score=-0.073 tagged_above=-999 required=5 tests=[AWL=2.525,  BAYES_00=-2.599, HTML_MESSAGE=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 KSr0xpwD136f for <mpls@core3.amsl.com>; Mon, 12 Jul 2010 15:18:45 -0700 (PDT)
Received: from pantheon-po45.its.yale.edu (pantheon-po45.its.yale.edu [130.132.50.79]) by core3.amsl.com (Postfix) with ESMTP id 364743A67EE for <mpls@ietf.org>; Mon, 12 Jul 2010 15:18:41 -0700 (PDT)
Received: from [130.132.249.132] (dhcp130132249132.its.yale.edu [130.132.249.132]) (authenticated bits=0) by pantheon-po45.its.yale.edu (8.12.11.20060308/8.12.11) with ESMTP id o6CMIjNt004211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 12 Jul 2010 18:18:45 -0400
Message-ID: <4C3B94C5.30506@cs.yale.edu>
Date: Mon, 12 Jul 2010 18:18:45 -0400
From: "Y. R. Yang" <yry@cs.yale.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: mpls@ietf.org
Content-Type: multipart/alternative; boundary="------------020101090501040709030502"
X-YaleITSMailFilter: Version 1.2c (attachment(s) not renamed)
Subject: [mpls] Fwd: New Version Notification for draft-yang-mpls-ff-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2010 22:18:46 -0000

This is a multi-part message in MIME format.
--------------020101090501040709030502
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

We have submitted a draft, available at:
http://www.ietf.org/id/draft-yang-mpls-ff-01.txt

The proposal is motivated by some recent studies available at:
http://cs-www.cs.yale.edu/homes/yry/projects/reinforce/r3-sigcomm10.pdf
http://www-net.cs.yale.edu/publications/WYLW07.pdf (Section 3.4)
http://www-net.cs.yale.edu/publications/WXQY06.pdf

In the orignal papers, we called the scheme flow-based routing, and in 
the -01 ID, we changed the name to be fractional forwarding to avoid 
potential confusions.

We feel that proposed scheme can be a good bridge to transfer recent new 
capabilities into practice. Thus, any comments or suggestions, in 
particular from this community, will be highly helpful and thus appreciated!

Regards,

Richard Yang
http://www.cs.yale.edu/~yry/

-------- Original Message --------
Subject: 	New Version Notification for draft-yang-mpls-ff-01
Date: 	Mon, 12 Jul 2010 15:11:28 -0700 (PDT)
From: 	IETF I-D Submission Tool <idsubmission@ietf.org>
To: 	yry@cs.yale.edu
CC: 	yzhang@cs.utexas.edu,lili@cs.utexas.edu



A new version of I-D, draft-yang-mpls-ff-01.txt has been successfully submitted by Yang Yang and posted to the IETF repository.

Filename:	 draft-yang-mpls-ff
Revision:	 01
Title:		 MPLS-ff for Supporting Fractional Forwarding
Creation_date:	 2010-07-12
WG ID:		 Independent Submission
Number_of_pages: 9

Abstract:
A fractional-forwarding scheme is a highly compact, flexible scheme
for specify routing for both traffic engineering (TE) and fast
rerouting.  The ability of fractional forwarding can be a key benefit
of MPLS over OSPF/IS-IS.  Many highly effective TE algorithms are
proposed and evaluated based on fractional forwarding.

In this document, we propose MPLS-ff, an extension to MPLS to allow
efficient implementation of fractional forwarding.  We present the
required extensions in the MPLS data forwarding plane.  We also list
the requirements in signaling for MPLS-ff.



The IETF Secretariat.



--------------020101090501040709030502
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>

<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
We have submitted a draft, available at:<br>
<a href="http://www.ietf.org/id/draft-yang-mpls-ff-01.txt">http://www.ietf.org/id/draft-yang-mpls-ff-01.txt</a><br>
<br>
The proposal is motivated by some recent studies available at:<br>
<a
 href="http://cs-www.cs.yale.edu/homes/yry/projects/reinforce/r3-sigcomm10.pdf">http://cs-www.cs.yale.edu/homes/yry/projects/reinforce/r3-sigcomm10.pdf</a><br>
<a href="http://www-net.cs.yale.edu/publications/WYLW07.pdf">http://www-net.cs.yale.edu/publications/WYLW07.pdf</a>
(Section 3.4)<br>
<a href="http://www-net.cs.yale.edu/publications/WXQY06.pdf">http://www-net.cs.yale.edu/publications/WXQY06.pdf</a><br>
<br>
In the orignal papers, we called the scheme flow-based routing, and in
the -01 ID, we changed the name to be fractional forwarding to avoid
potential confusions. <br>
<br>
We feel that proposed scheme can be a good bridge to transfer recent
new capabilities into practice. Thus, any comments or suggestions, in
particular from this community, will be highly helpful and thus
appreciated!<br>
<br>
Regards,<br>
<br>
Richard Yang<br>
<a class="moz-txt-link-freetext" href="http://www.cs.yale.edu/~yry/">http://www.cs.yale.edu/~yry/</a><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
 cellspacing="0">
  <tbody>
    <tr>
      <th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject: </th>
      <td>New Version Notification for draft-yang-mpls-ff-01</td>
    </tr>
    <tr>
      <th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
      <td>Mon, 12 Jul 2010 15:11:28 -0700 (PDT)</td>
    </tr>
    <tr>
      <th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
      <td>IETF I-D Submission Tool <a class="moz-txt-link-rfc2396E" href="mailto:idsubmission@ietf.org">&lt;idsubmission@ietf.org&gt;</a></td>
    </tr>
    <tr>
      <th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
      <td><a class="moz-txt-link-abbreviated" href="mailto:yry@cs.yale.edu">yry@cs.yale.edu</a></td>
    </tr>
    <tr>
      <th valign="BASELINE" align="RIGHT" nowrap="nowrap">CC: </th>
      <td><a class="moz-txt-link-abbreviated" href="mailto:yzhang@cs.utexas.edu,lili@cs.utexas.edu">yzhang@cs.utexas.edu,lili@cs.utexas.edu</a></td>
    </tr>
  </tbody>
</table>
<br>
<br>
<pre>A new version of I-D, draft-yang-mpls-ff-01.txt has been successfully submitted by Yang Yang and posted to the IETF repository.

Filename:	 draft-yang-mpls-ff
Revision:	 01
Title:		 MPLS-ff for Supporting Fractional Forwarding
Creation_date:	 2010-07-12
WG ID:		 Independent Submission
Number_of_pages: 9

Abstract:
A fractional-forwarding scheme is a highly compact, flexible scheme
for specify routing for both traffic engineering (TE) and fast
rerouting.  The ability of fractional forwarding can be a key benefit
of MPLS over OSPF/IS-IS.  Many highly effective TE algorithms are
proposed and evaluated based on fractional forwarding.

In this document, we propose MPLS-ff, an extension to MPLS to allow
efficient implementation of fractional forwarding.  We present the
required extensions in the MPLS data forwarding plane.  We also list
the requirements in signaling for MPLS-ff.
                                                                                  


The IETF Secretariat.

</pre>
</body>
</html>

--------------020101090501040709030502--

From root@core3.amsl.com  Mon Jul 12 16:30:41 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 67F423A68DA; Mon, 12 Jul 2010 16:30:29 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100712233030.67F423A68DA@core3.amsl.com>
Date: Mon, 12 Jul 2010 16:30:29 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-tp-identifiers-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2010 23:30:41 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.


	Title           : MPLS-TP Identifiers
	Author(s)       : M. Bocci, G. Swallow
	Filename        : draft-ietf-mpls-tp-identifiers-02.txt
	Pages           : 14
	Date            : 2010-07-12

This document specifies identifiers for MPLS-TP objects.  Included
are identifiers conformant to existing ITU conventions and
identifiers which are compatible with existing IP, MPLS, GMPLS, and
Pseudowire definitions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-identifiers-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-mpls-tp-identifiers-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-12162139.I-D@ietf.org>


--NextPart--

From venkatflex@gmail.com  Mon Jul 12 22:51:54 2010
Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03F813A67C0; Mon, 12 Jul 2010 22:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 HpLHOPp76rZf; Mon, 12 Jul 2010 22:51:51 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 080493A68CE; Mon, 12 Jul 2010 22:51:47 -0700 (PDT)
Received: by pwj1 with SMTP id 1so2516566pwj.31 for <multiple recipients>; Mon, 12 Jul 2010 22:51:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=jaCUzhHCk4K7N7qlcTHL3b037+RINUX0G15/ecSNCNw=; b=pDfAiymXjINBSQDr57drIO3ENCAsQFxKzwyCVQ5t5DjykRQzC02mWIm/QjCBz6eZYC qmJ4GKHT2IZYfUQlWxiQnuu0H+Ce2PLyaQp51VPsGIKmUHvI9AoqSPURYqRYwMWlZ0RS HvOjULeFIWsS3I6I6efKN/10HpLWCzCCEGFkc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TQ3HHqdf73B567nGfW56+vb4Z3APxHKqe3wUronlEuBUO4ChRHUKg95J3XNEsQzCqp 2waKibORTS6P2crvyPVwPPI+13zkf2fl4VcP/tri2b6urpinCJG9BL8BFuAkPXIgxs8B sosfg5dujvRyB61MUFJMrKEOiwXe47qQ/Agp8=
MIME-Version: 1.0
Received: by 10.142.136.1 with SMTP id j1mr5555740wfd.26.1279000313134; Mon,  12 Jul 2010 22:51:53 -0700 (PDT)
Received: by 10.143.167.14 with HTTP; Mon, 12 Jul 2010 22:51:52 -0700 (PDT)
In-Reply-To: <C860F401.275DD%swallow@cisco.com>
References: <q2k715756491005061108r650202bfm6c36bc6d31a4b7cb@mail.gmail.com> <C860F401.275DD%swallow@cisco.com>
Date: Tue, 13 Jul 2010 11:21:52 +0530
Message-ID: <AANLkTikDW9mjenUT3KfLvWm6MN5Nct9y4yBgndF-zMMb@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: George Swallow <swallow@cisco.com>
Content-Type: multipart/alternative; boundary=000e0cd32cc6550100048b3e776e
Cc: mpls@ietf.org, ccamp@ietf.org, Attila Takacs <Attila.Takacs@ericsson.com>, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] [mpls-tp] mpls wg last call ondraft-ietf-mpls-tp-identifiers-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2010 05:51:54 -0000

--000e0cd32cc6550100048b3e776e
Content-Type: text/plain; charset=ISO-8859-1

 George,
Thanks for your response, please find the followup questions below,

Even though Dest_Tunnel_Num is primarily required for bidirectional LSP,
this is NOT required for unidirectional LSP.

In MPLS_TP environment, if user configures an unidirectional LSP (I guess
this is not a violation), then the Dest_Tunnel_Num should be ignored.

Is this a correct understanding?

And, for bidirectional LSPs, even though the Dest_Tunnel_Num is required to
identify the reverse tunnel, it need not be an INDEX to identify the
bidirectional Tunnel.

Is this a correct understanding?

BR,

--Venkat.

On Tue, Jul 13, 2010 at 2:02 AM, George Swallow <swallow@cisco.com> wrote:

> In line -
>
>
>
> On 5/6/10 2:08 PM, "venkatesan mahalingam" <venkatflex@gmail.com> wrote:
>
>  Hi George,
> >> Is it there to support associated unidirectional Tunnels/LSPs? If so it
> should
> >> be called out in the text.
>
> >That was not my original intent, but you are quite correct that this would
> >be very useful.  Particularly if the associated tunnels pass through a
> share
> >mid-point somewhere along the path.
> VM: Can you please explain the original intention with an example?
>
> The original intent was to allow a compact form for a globally unique
> MEP-ID that is,
>
> Node_ID::Tunnel_Num::LSP_ID would be unique within an operator.  This
> requires that Tunnel_Num be unique to the node (not the node pair).  That
> makes it impossible to coodinate the Tunnel_Num spaces across nodes, hence
> two tunnel numbers.
>
>
> >> -In Section 5.3 Mapping to GMPLS signaling does not use the
> Dst-Tunnel_Num. So
> >> this means that we may have two different tunnels identified with
> >> Src-Node_ID::Src-Tunnel_Num::
> Dst-Node_ID::Dst-Tunnel_Num. Is this intentional,
> >> e.g., the associated unidirectional case?
>
> >For the associated unidirectional, this works perfectly.  For
> bidirectional,
> >I was thinking of two options.
>
> >1)  Strict binding  -  both ends are configure with the full identifier
> and
> >will only accept the connection if everything matches.
>
> >2)  Dynamic binding - Source signals with just its Tunnel_Num.  RESV
> message
> >would carry back the destination's tunnel_num.  Note that both ends need
> >both pieces for some of the OAM to work.
> VM: Do we need extensions in the RSVP-TE signaling to carry back the
> destination's tunnel_num in the RESV message?
>
> Yes, this and probably quite a few more.   Note that there is a draft for
> adding signaling of OAM capabilities in the works.
>
> ...George
>
>
> Thanks,
> Venkatesan Mahalingam
>
> On Fri, Apr 16, 2010 at 10:15 PM, George Swallow <swallow@cisco.com>
> wrote:
>
>
>
>
> On 4/2/10 2:53 AM, "Attila Takacs" <Attila.Takacs@ericsson.com> wrote:
>
> > Hi Matthew and George,
> >
> > Please find some comments/questions below.
> >
> > -In Section 5.1 you have:
> >
> > Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num
> >
> > What is the reason of having a Dst-Tunnel_Num besides the Src-Tunnel_Num?
>
> Existing implementations of RSVP-TE have used the tunnel space as global to
> the node.  It is difficult if not impossible to coordinate such spaces
> between nodes.  In RSVP-TE the coordination does not matter, since the tail
> end of the tunnel doesn't have a real interface - it only receives and
> usually with a PHP of the tunnel label, so the packets only belong to the
> physical interface.
>
> In a bidirectional world, separate tunnel spaces at the two ends becomes
> useful.
>
> If this independence is not need is some environments then one can
> configure
> just one value and use it in both fields.
>
> > Is it there to support associated unidirectional Tunnels/LSPs? If so it
> should
> > be called out in the text.
>
> That was not my original intent, but you are quite correct that this would
> be very useful.  Particularly if the associated tunnels pass through a
> share
> mid-point somewhere along the path.
>
> > Same applies to the globally unique case.
>
> Of course.
>
> > -In Section 5.2 you simply append one LSP_Num to the above. This is a bit
> > confusing to me, if there are Src/Dst Tunnel_Nums then two LSP_Nums would
> be
> > needed too, wouldn't it?
>
> Once, you have independent tunnel-ids, coordination of the LSP numbers
> becomes easy.  It also could be used to allow the two ends to readily
> identify which is working and which is protection.
>
> > -In Section 5.3 Mapping to GMPLS signaling does not use the
> Dst-Tunnel_Num. So
> > this means that we may have two different tunnels identified with
> > Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num. Is this
> intentional,
> > e.g., the associated unidirectional case?
>
> For the associated unidirectional, this works perfectly.  For
> bidirectional,
> I was thinking of two options.
>
> 1)  Strict binding  -  both ends are configure with the full identifier and
> will only accept the connection if everything matches.
>
> 2)  Dynamic binding - Source signals with just its Tunnel_Num.  RESV
> message
> would carry back the destination's tunnel_num.  Note that both ends need
> both pieces for some of the OAM to work.
>
> > This should be clarified.
>
> I'll see what I can do.  But this is not supposed to the MPLS-TP signaling
> draft.
>
> > Hmm, maybe the Dst-Tunnel_Num should be omitted altogether.
>
> I'm planning to keep it.
>
> > -Section 7 has a note saying to be aligned with the OAM fwk, is this
> still to
> > be done?
>
> Yes.  That draft is also being updated.  We appear to be converging.
>
> > -In section 7.1.2.1 there is a discussion on Tunnel MEG IDs.
> > How would Tunnel and LSP MEGs be used? What OAM would run at the Tunnel
> level
> > and not at the LSP level?
> >
> > Do we need Tunnel MEG_IDs as defined in 7.1.2.1?
>
> I had been told early on that MEGs were needed for tunnels.  Now getting
> comments that they are not (same comment is in the ITU liaison).  So I
> planning to remove it, unless I hear other opinions.
>
> > -Section 7.1.2.2, the Dst-Tunnel_Num question applies here too.
>
> See above.
>
> > -Section 8 talks about open issues? When will these be addressed?
>
> Before it is re-issued.  Goal is end of next week.
>
> ...George
>
> > Thanks,
> > Attila
> >
> >> -----Original Message-----
> >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org<mpls-bounces@ietf.org>]
> On
> >> Behalf Of Loa Andersson
> >> Sent: Friday, March 12, 2010 12:33 AM
> >> To: mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ietf.org
> >> Subject: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
> >>
> >> All,
> >>
> >> this is to start an MPLS working group last call on
> >> draft-ietf-mpls-tp-identifiers-01
> >>
> >> There is a discussion on the OAM model for MS-PWs where we
> >> haven't been able to come to conclusion. Once we reach
> >> agreement the document will be updated. Comments in this area
> >> are welcome during the working group last call.
> >>
> >>
> >> Please send your comments to the mpls-tp@ietf.org mailing list.
> >>
> >> The working group last ends eob April 2nd.
> >>
> >> /Loa
> >>
> >> --
> >>
> >> Loa Andersson
> >>
> >> Sr Strategy and Standards Manager
> >> Ericsson ///
> >>    phone:  +46 10 717 52 13
> >>            +46 767 72 92 13
> >>
> >>    email:  loa.andersson@ericsson.com
> >>            loa@pi.nu
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> >>
> > _______________________________________________
> > mpls-tp mailing list
> > mpls-tp@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls-tp
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>
>
>


-- 
Best Regards,
Venkatesan Mahalingam.

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

<div><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: &#39;Cali=
bri&#39;,&#39;sans-serif&#39;">
<div>George,</div>
<div>Thanks for your response, please find=A0the followup questions below,<=
/div>
<div><br>Even though Dest_Tunnel_Num is primarily required for bidirectiona=
l LSP, this is NOT required for unidirectional LSP.</div></span></div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: &#39;Calibri&#39;,&#39;sans-serif&#39;">In MPLS_TP environment, if=
 user configures an unidirectional LSP (I guess this is not a violation), t=
hen the Dest_Tunnel_Num should be ignored. </span></p>

<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: &#39;Calibri&#39;,&#39;sans-serif&#39;">Is this a correct understa=
nding?</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: &#39;Calibri&#39;,&#39;sans-serif&#39;">And, for bidirectional LSP=
s, even though the Dest_Tunnel_Num is required to identify the reverse tunn=
el, it need not be an INDEX to identify the bidirectional Tunnel. </span></=
p>

<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: &#39;Calibri&#39;,&#39;sans-serif&#39;">Is this a correct understa=
nding?</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: &#39;Calibri&#39;,&#39;sans-serif&#39;">BR,</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: &#39;Calibri&#39;,&#39;sans-serif&#39;"></span><span style=3D"FONT=
-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: &#39;Calibri&#39;,&#39;sans-serif=
&#39;">--Venkat.</span></p>

<p class=3D"MsoNormal">On Tue, Jul 13, 2010 at 2:02 AM, George Swallow <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:swallow@cisco.com">swallow@cisco.com</a=
>&gt;</span> wrote:<br></p></div>
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div><font face=3D"Verdana, Helvetica, Arial"><span style=3D"FONT-SIZE: 14p=
t">In line -=20
<div class=3D"im"><br><br><br>On 5/6/10 2:08 PM, &quot;venkatesan mahalinga=
m&quot; &lt;<a href=3D"http://venkatflex@gmail.com" target=3D"_blank">venka=
tflex@gmail.com</a>&gt; wrote:<br><br></div></span></font>
<blockquote><font face=3D"Verdana, Helvetica, Arial"><span style=3D"FONT-SI=
ZE: 14pt">
<div class=3D"im">Hi George,<br>&gt;&gt; Is it there to support associated =
unidirectional Tunnels/LSPs? If so it should<br>&gt;&gt; be called out in t=
he text.<br><br>&gt;That was not my original intent, but you are quite corr=
ect that this would<br>
&gt;be very useful. =A0Particularly if the associated tunnels pass through =
a share<br>&gt;mid-point somewhere along the path.<br>VM: Can you please ex=
plain the original intention with an example? <br><br></div>The original in=
tent was to allow a compact form for a globally unique MEP-ID that is,<br>
<br>Node_ID::Tunnel_Num::LSP_ID would be unique within an operator. =A0This=
 requires that Tunnel_Num be unique to the node (not the node pair). =A0Tha=
t makes it impossible to coodinate the Tunnel_Num spaces across nodes, henc=
e two tunnel numbers.=20
<div class=3D"im"><br><br>&gt;&gt; -In Section 5.3 Mapping to GMPLS signali=
ng does not use the Dst-Tunnel_Num. So<br>&gt;&gt; this means that we may h=
ave two different tunnels identified with<br>&gt;&gt; Src-Node_ID::Src-Tunn=
el_Num::<br>
Dst-Node_ID::Dst-Tunnel_Num. Is this intentional,<br>&gt;&gt; e.g., the ass=
ociated unidirectional case?<br><br>&gt;For the associated unidirectional, =
this works perfectly. =A0For bidirectional,<br>&gt;I was thinking of two op=
tions.<br>
<br>&gt;1) =A0Strict binding =A0- =A0both ends are configure with the full =
identifier and<br>&gt;will only accept the connection if everything matches=
.<br><br>&gt;2) =A0Dynamic binding - Source signals with just its Tunnel_Nu=
m. =A0RESV message<br>
&gt;would carry back the destination&#39;s tunnel_num. =A0Note that both en=
ds need<br>&gt;both pieces for some of the OAM to work.<br>VM: Do we need e=
xtensions in the RSVP-TE signaling to carry back the destination&#39;s tunn=
el_num in the RESV message?<br>
<br></div>Yes, this and probably quite a few more. =A0=A0Note that there is=
 a draft for adding signaling of OAM capabilities in the works.<br><br>...G=
eorge=20
<div>
<div></div>
<div class=3D"h5"><br><br>Thanks,<br>Venkatesan Mahalingam<br><br>On Fri, A=
pr 16, 2010 at 10:15 PM, George Swallow &lt;<a href=3D"http://swallow@cisco=
.com" target=3D"_blank">swallow@cisco.com</a>&gt; wrote:<br></div></div></s=
pan></font>
<div>
<div></div>
<div class=3D"h5">
<blockquote><font face=3D"Verdana, Helvetica, Arial"><span style=3D"FONT-SI=
ZE: 14pt"><br><br><br>On 4/2/10 2:53 AM, &quot;Attila Takacs&quot; &lt;<a h=
ref=3D"http://Attila.Takacs@ericsson.com" target=3D"_blank">Attila.Takacs@e=
ricsson.com</a>&gt; wrote:<br>
<br>&gt; Hi Matthew and George,<br>&gt;<br>&gt; Please find some comments/q=
uestions below.<br>&gt;<br>&gt; -In Section 5.1 you have:<br>&gt;<br>&gt; S=
rc-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num<br>&gt;<br>&gt; Wha=
t is the reason of having a Dst-Tunnel_Num besides the Src-Tunnel_Num?<br>
<br>Existing implementations of RSVP-TE have used the tunnel space as globa=
l to<br>the node. =A0It is difficult if not impossible to coordinate such s=
paces<br>between nodes. =A0In RSVP-TE the coordination does not matter, sin=
ce the tail<br>
end of the tunnel doesn&#39;t have a real interface - it only receives and<=
br>usually with a PHP of the tunnel label, so the packets only belong to th=
e<br>physical interface.<br><br>In a bidirectional world, separate tunnel s=
paces at the two ends becomes<br>
useful.<br><br>If this independence is not need is some environments then o=
ne can configure<br>just one value and use it in both fields.<br><br>&gt; I=
s it there to support associated unidirectional Tunnels/LSPs? If so it shou=
ld<br>
&gt; be called out in the text.<br><br>That was not my original intent, but=
 you are quite correct that this would<br>be very useful. =A0Particularly i=
f the associated tunnels pass through a share<br>mid-point somewhere along =
the path.<br>
<br>&gt; Same applies to the globally unique case.<br><br>Of course.<br><br=
>&gt; -In Section 5.2 you simply append one LSP_Num to the above. This is a=
 bit<br>&gt; confusing to me, if there are Src/Dst Tunnel_Nums then two LSP=
_Nums would be<br>
&gt; needed too, wouldn&#39;t it?<br><br>Once, you have independent tunnel-=
ids, coordination of the LSP numbers<br>becomes easy. =A0It also could be u=
sed to allow the two ends to readily<br>identify which is working and which=
 is protection.<br>
<br>&gt; -In Section 5.3 Mapping to GMPLS signaling does not use the Dst-Tu=
nnel_Num. So<br>&gt; this means that we may have two different tunnels iden=
tified with<br>&gt; Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Nu=
m. Is this intentional,<br>
&gt; e.g., the associated unidirectional case?<br><br>For the associated un=
idirectional, this works perfectly. =A0For bidirectional,<br>I was thinking=
 of two options.<br><br>1) =A0Strict binding =A0- =A0both ends are configur=
e with the full identifier and<br>
will only accept the connection if everything matches.<br><br>2) =A0Dynamic=
 binding - Source signals with just its Tunnel_Num. =A0RESV message<br>woul=
d carry back the destination&#39;s tunnel_num. =A0Note that both ends need<=
br>
both pieces for some of the OAM to work.<br><br>&gt; This should be clarifi=
ed.<br><br>I&#39;ll see what I can do. =A0But this is not supposed to the M=
PLS-TP signaling<br>draft.<br><br>&gt; Hmm, maybe the Dst-Tunnel_Num should=
 be omitted altogether.<br>
<br>I&#39;m planning to keep it.<br><br>&gt; -Section 7 has a note saying t=
o be aligned with the OAM fwk, is this still to<br>&gt; be done?<br><br>Yes=
. =A0That draft is also being updated. =A0We appear to be converging.<br><b=
r>
&gt; -In section 7.1.2.1 there is a discussion on Tunnel MEG IDs.<br>&gt; H=
ow would Tunnel and LSP MEGs be used? What OAM would run at the Tunnel leve=
l<br>&gt; and not at the LSP level?<br>&gt;<br>&gt; Do we need Tunnel MEG_I=
Ds as defined in 7.1.2.1?<br>
<br>I had been told early on that MEGs were needed for tunnels. =A0Now gett=
ing<br>comments that they are not (same comment is in the ITU liaison). =A0=
So I<br>planning to remove it, unless I hear other opinions.<br><br>&gt; -S=
ection 7.1.2.2, the Dst-Tunnel_Num question applies here too.<br>
<br>See above.<br><br>&gt; -Section 8 talks about open issues? When will th=
ese be addressed?<br><br>Before it is re-issued. =A0Goal is end of next wee=
k.<br><br>...George<br><br>&gt; Thanks,<br>&gt; Attila<br>&gt;<br>&gt;&gt; =
-----Original Message-----<br>
&gt;&gt; From: <a href=3D"http://mpls-bounces@ietf.org" target=3D"_blank">m=
pls-bounces@ietf.org</a> [<a href=3D"mailto:mpls-bounces@ietf.org" target=
=3D"_blank">mailto:mpls-bounces@ietf.org</a>] On<br>&gt;&gt; Behalf Of Loa =
Andersson<br>
&gt;&gt; Sent: Friday, March 12, 2010 12:33 AM<br>&gt;&gt; To: <a href=3D"h=
ttp://mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>; <a href=3D"http:/=
/mpls-tp@ietf.org" target=3D"_blank">mpls-tp@ietf.org</a>; <a href=3D"http:=
//pwe3@ietf.org" target=3D"_blank">pwe3@ietf.org</a>; <a href=3D"http://cca=
mp@ietf.org" target=3D"_blank">ccamp@ietf.org</a><br>
&gt;&gt; Subject: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifier=
s-01<br>&gt;&gt;<br>&gt;&gt; All,<br>&gt;&gt;<br>&gt;&gt; this is to start =
an MPLS working group last call on<br>&gt;&gt; draft-ietf-mpls-tp-identifie=
rs-01<br>
&gt;&gt;<br>&gt;&gt; There is a discussion on the OAM model for MS-PWs wher=
e we<br>&gt;&gt; haven&#39;t been able to come to conclusion. Once we reach=
<br>&gt;&gt; agreement the document will be updated. Comments in this area<=
br>
&gt;&gt; are welcome during the working group last call.<br>&gt;&gt;<br>&gt=
;&gt;<br>&gt;&gt; Please send your comments to the <a href=3D"http://mpls-t=
p@ietf.org" target=3D"_blank">mpls-tp@ietf.org</a> mailing list.<br>&gt;&gt=
;<br>
&gt;&gt; The working group last ends eob April 2nd.<br>&gt;&gt;<br>&gt;&gt;=
 /Loa<br>&gt;&gt;<br>&gt;&gt; --<br>&gt;&gt;<br>&gt;&gt; Loa Andersson<br>&=
gt;&gt;<br>&gt;&gt; Sr Strategy and Standards Manager<br>&gt;&gt; Ericsson =
///<br>
&gt;&gt; =A0 =A0phone: =A0+46 10 717 52 13<br>&gt;&gt; =A0 =A0 =A0 =A0 =A0 =
=A0+46 767 72 92 13<br>&gt;&gt;<br>&gt;&gt; =A0 =A0email: =A0<a href=3D"htt=
p://loa.andersson@ericsson.com" target=3D"_blank">loa.andersson@ericsson.co=
m</a><br>&gt;&gt; =A0 =A0 =A0 =A0 =A0 =A0<a href=3D"http://loa@pi.nu" targe=
t=3D"_blank">loa@pi.nu</a><br>
&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; __________________=
_____________________________<br>&gt;&gt; mpls mailing list<br>&gt;&gt; <a =
href=3D"http://mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a><br>&gt;&g=
t; <a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/mpls</a><br>
&gt;&gt;<br>&gt; _______________________________________________<br>&gt; mp=
ls-tp mailing list<br>&gt; <a href=3D"http://mpls-tp@ietf.org" target=3D"_b=
lank">mpls-tp@ietf.org</a><br>&gt; <a href=3D"https://www.ietf.org/mailman/=
listinfo/mpls-tp" target=3D"_blank">https://www.ietf.org/mailman/listinfo/m=
pls-tp</a><br>
<br>_______________________________________________<br>mpls mailing list<br=
><a href=3D"http://mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a><br><a=
 href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">http=
s://www.ietf.org/mailman/listinfo/mpls</a><br>
</span></font></blockquote><font face=3D"Verdana, Helvetica, Arial"><span s=
tyle=3D"FONT-SIZE: 14pt"><br><br></span></font></div></div></blockquote></d=
iv></blockquote></div><br><br clear=3D"all"><br>-- <br>Best Regards,<br>Ven=
katesan Mahalingam.<br>

--000e0cd32cc6550100048b3e776e--

From mach@huawei.com  Tue Jul 13 01:12:49 2010
Return-Path: <mach@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8717E3A6944 for <mpls@core3.amsl.com>; Tue, 13 Jul 2010 01:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.061
X-Spam-Level: 
X-Spam-Status: No, score=-0.061 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1, STOX_REPLY_TYPE=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 fNfa9U7jdHPt for <mpls@core3.amsl.com>; Tue, 13 Jul 2010 01:12:48 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id A6C503A67BD for <mpls@ietf.org>; Tue, 13 Jul 2010 01:12:43 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5H00B44LGYYK@szxga01-in.huawei.com> for mpls@ietf.org; Tue, 13 Jul 2010 16:12:35 +0800 (CST)
Received: from m55527c ([10.110.98.169]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5H007S6LGV4T@szxga01-in.huawei.com> for mpls@ietf.org; Tue, 13 Jul 2010 16:12:34 +0800 (CST)
Date: Tue, 13 Jul 2010 16:12:25 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <44F4E579A764584EA9BDFD07D0CA081305E35619@tlvmail1>
To: Ehud Doron <ehudd@orckit.com>
Message-id: <9D87ABFE12734FCF9484DB68977B06CA@m55527c>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206
X-Mailer: Microsoft Windows Live Mail 14.0.8064.206
Content-type: text/plain; format=flowed; charset=ISO-8859-1; reply-type=original
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
References: <44F4E579A764584EA9BDFD07D0CA081305E35619@tlvmail1>
Cc: mpls@ietf.org, Ofer Dayan <Oferd@orckit.com>, Yossi Fridman <Yossifr@orckit.com>, Shai Bromberg <ShaiB@orckit.com>, Nir Ben Avraham <nirb@orckit.com>, Rafi Ram <RafiR@orckit.com>, Ronen Solomon <RonenS@orckit.com>
Subject: Re: [mpls] Return path spesified LSP Ping draft - required updates
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2010 08:12:49 -0000

Hi Ehud,

Thanks for your detailed suggestions! We will consider the suggestion and 
try to incorporate them into the next revision.

Best regards,
Mach

--------------------------------------------------
From: "Ehud Doron" <ehudd@orckit.com>
Sent: Monday, July 12, 2010 11:09 PM
To: "Mach Chen" <mach@huawei.com>
Cc: "Yossi Fridman" <Yossifr@orckit.com>; "Ehud Doron" <ehudd@orckit.com>; 
"Rafi Ram" <RafiR@orckit.com>; "Nir Ben Avraham" <nirb@orckit.com>; "Ofer 
Dayan" <Oferd@orckit.com>; <mpls@ietf.org>; "Ronen Solomon" 
<RonenS@orckit.com>; "Shai Bromberg" <ShaiB@orckit.com>
Subject: Return path spesified LSP Ping draft  - required updates

> Hi Mach
>
>
>
> Kindly we would like to suggest the following enhancements for the
> Return path specified LSP Ping next draft.
>
>
>
> 1.       Reply Path (RP) Return Code
>
> Following our last discussions please find attached our suggestions for
> RP Return Code.
>
>
>
> The RP return code shall be part of RP TLV. The RP TLV shall have the
> following structure:
>
> 0                              7  8                                15 16
> 23 24                            31
>
> RP return code
>
> RP return sub-code
>
> RP sub-TLVs
>
>
>
>
>
> The Reply Path Return Code it a dedicated return code for RP operations
> (separated from the forward return code  in Echo Reply header). It used
> by the forward LSP Tail End to report the forward LSP Head End about the
> actions he took while selecting the RP. The forward LSP Tail End can set
> it to one of the values listed below. The RP Return Subcode must be set
> to zero.
>
>
>
>  Value Meaning
>
> ----------------------
>
> 0 - No return code
>
> 1 - Malformed RP TLV was received
>
> 2 - One or more of the sub-TLVs in RP TLV was not understood
>
> 3 - The echo reply was sent successfully using the specified RP
>
> 4 - The specified RP was not found, the echo reply was sent via other
> LSP
>
> 5 - The specified RP was not found, the echo reply was sent via IP path
>
> 6 - The Reply mode in echo request was not set to 5 (replay via
> specified path) although RP TLV exists
>
> 7 - RP TLV was missing in echo reply
>
>
>
> Examples of usage of this return code:
>
> If the RP TLV contains IPv4 RSVP-TE tunnel sub-TLV and the flag fields
> are P=1 S=1, it is required to set the RP Return Code to 2 , "One or
> more of the sub-TLVs in RP TLV was not understood". Here it is required
> to use the default return path.
>
>
>
> If the Reply Mode field in the received echo request is equal to "Reply
> via specified path" and no RP TLV exists in the echo request, it is
> required to set the RP Return Code to "RP TLV was missing in echo
> reply". Here it is required to use the default return path.
>
>
>
>
>
> 2.       New sub-TLV for RP EXP
>
> In addition, we conclude that it is required to add new sub-TLV to RP
> TLV  the RP EXP sub-TLV. This TLV is used by the originator of the echo
> request to specify the echo reply sender which EXP bits to use while
> sending the echo reply in the specified LSP. This TLV is similar in its
> sense to Reply TOS Byte TLV for IP reply path (as defined in RFC4379).
>
> RP EXP sub-TLV structure:
>
> 0              2              7  8                                15 16
> 23 24                            31
>
> RP EXP bit
>
> Must be Zero
>
>
>
> We think that this sub-TLV is essential and must be added.
>
>
>
>
>
>
>
> Please refer
>
>
>
>
>
> Ehud    Doron
>
> System Architect
>
> Orckit - Corrigent
>
> ehudd@orckit.com <mailto:username@orckit.com>
>
> Tel: 972-3-69456327
>
> www.orckit.com <http://www.orckit.com/>
>
>
>
>  <http://www.orckit.com/>
>
> Pushing technology to the edge
>
>
>
>
>
> 

From venkatflex@gmail.com  Tue Jul 13 08:43:08 2010
Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BACB3A6818; Tue, 13 Jul 2010 08:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.448
X-Spam-Level: 
X-Spam-Status: No, score=-1.448 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_GIRL=2.3]
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 fkqCFiUiAb8Q; Tue, 13 Jul 2010 08:43:06 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id 802E03A6B2E; Tue, 13 Jul 2010 08:42:43 -0700 (PDT)
Received: by pzk6 with SMTP id 6so1731327pzk.31 for <multiple recipients>; Tue, 13 Jul 2010 08:42:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=X1CTMdrPiEpjBO2n9Z1Kggkjhz+zqH7uqAddy/mQTZU=; b=Vf0FNzWuLbY8z35O/Yp8t4flxEj996T3QDssj6lSnhAYTP3nWWKq1obVt042yiVyE/ R8r96LEEq+PNyMPZULJUZZGVBmeYPmowbX93Ygqfr9c8t41ej95kMKf3TAEVIeg7SrTL CJzM4WGbNnLxD0qZ8tUiGQbbwBhQW/GnmdNCI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=r7Yrtt8LkdE6szeoFYlBywnBXpfekpCJ7onm2c34amb7IopV9D436Q3MGwccT+mLTc 97m9oXxD99ounneBfExgNoFFKIHSRTKHu87dTeHiFuEJkfeo+0VjeRQNZQZHh970pkjP 4Ux/zld12P/NcJ//dQAy6sn+m19Iy1jESBBQA=
MIME-Version: 1.0
Received: by 10.142.73.1 with SMTP id v1mr18293362wfa.29.1279035758954; Tue,  13 Jul 2010 08:42:38 -0700 (PDT)
Received: by 10.143.167.14 with HTTP; Tue, 13 Jul 2010 08:42:38 -0700 (PDT)
In-Reply-To: <20100712233030.67F423A68DA@core3.amsl.com>
References: <20100712233030.67F423A68DA@core3.amsl.com>
Date: Tue, 13 Jul 2010 21:12:38 +0530
Message-ID: <AANLkTilqobseCxAIZMh6bPGM8YPOSbOBAzKMIgn6giie@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: George Swallow <swallow@cisco.com>, mpls <mpls@ietf.org>, mpls-tp@ietf.org
Content-Type: multipart/alternative; boundary=001636ed675813fca6048b46b80d
Subject: Re: [mpls] I-D Action:draft-ietf-mpls-tp-identifiers-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2010 15:43:08 -0000

--001636ed675813fca6048b46b80d
Content-Type: text/plain; charset=ISO-8859-1

George,

Please find the comments inlined <VM> on this MPLS_TP identifiers draft,

Section 5.1.  MPLS-TP Point to Point Tunnel Identifiers
It is RECOMMENDED that the IF_Num be auto-generated by adding
   2^31 to the local Tunnel_Num

<VM> What was the intention to auto-generate IF_Num by adding 2^31 to the
local Tunnel_Num?

7.2.2.2.  MEP_IDs for Pseudowires
 where the Node_ID is the node in which the MEP is located and
   Tunnel_Num is the tunnel number unique to that node.
<VM> Typo error, please correct it.

 6.  Pseudowire Path Identifiers

      AGI:Src-Global_ID::Src-Node_ID::Src-AC_ID::Dst-Global_ID::
      Dst-Node_ID::Dst-AC_ID
<VM> Does FEC 129 AII Type 2 configuration applicable for both manual and
signalling PWs?
     How to represent this AC_ID in the PW mibs? Will there be any
augmentation in the PW AC mibs (PW-ENET-STD-MIB)?

GS: In Stockholm I was convinced that for ICC based identifiers, only the
MEG-ID and/or ME-ID would need to be configured at various points along an
LSP.  Much has changed on this project since then.  Is what we have not
sufficient?

<VM>  What I infer from your response is, ICC based identifiers are
applicable only for the MEG-ID and/or ME-ID identification. So, does it mean
that ICC based operator environment also, MPLS-TP LSP will be created using
Global_ID? If the answer is yes, i.e Global_Id and ICC should co-exist for
creating/monitoring the MPLS-TP tunnel, in that case can't we completely
eliminate the need of ICC based identifier and Global_ID identifier can
alone be used for creating/monitoring the MPLS-TP tunnel?

 7.1.2.1.  MPLS-TP LSP MEG_IDs
 Since a MEG pertains to a single MPLS-TP LSP, IP compatible MEG_IDs
   for MPLS-TP LSPs are simply the corresponding LSP_IDs

<VM> For uni-directional/bi-directional tunnel, one MEG is associated with
only one LSP (ME).
For P2MP unidirectional tunnel, one MEG is associated with multiple
destination LSPs (MEs)
Is this understanding correct?

<VM> How to configure multiple client MEGs in a server MEG? I believe, we
don't follow the ITU-T Y1731 MEG level concept in MPLS-TP. Please give us
some insight into the client MEG and server MEG handling for MPLS-TP.

 >> 2. In your draft, an LSP is identified by the combination of
Src-Global_ID,
>> Src-Node_ID, Src-Tunnel_Num, Dst-Global_ID, Dst-Node_ID, Dst-Tunnel_Num,
>> LSP_Num, this is fine for unidirectional and co-routed bidirectional LSP,
>> but it is not enough for associated bidirectional LSP that is combined
with
>> two reverse unidirectional LSPs and IMHO two LSP_Nums are required.

>We should discuss this (and the above if you like) in Maastricht.

<VM> I agree with Mach Chen for two LSP_Nums for associated bi-directional
tunnel,

For example, consider the below topology,

All routers are in different Global_ID operators domain.

  R1-----R2---------R3
  |                       |
  |______R4_____|

Tunnel LSP identifier:
Src-Global_Node_ID::Src-Tunnel_Num::Dst-Global_Node_ID::Dst-Tunnel_Num::LSP_Num

Co-routed bi-directional tunnel:
Co-routed bi-directional tunnel (Tnl_Num=100, LSP_Num=1, Src=R1, Dst=R3) is
established from R1 to R3 via R2.
Forward and reverse directions LSP identifier: G1_R1::100::G3_R3::100::1

Associated bi-directional tunnel:
Associated bi-directional tunnel is established from R1 to R3 via R2 for
forward direction.
For this forward direction, LSP identifier is: G1_R1::100::G3_R3::200::*1
*For reverse direction, a LSP from R3 to R1 via R4 may exist.
For this reverse direction LSP identifier: G3_R3::200::G1_R1::100::*2
*

If I assume that the above scenario is valid, we can combine these two
different LSPs as a single bidirectional LSP only when we have two LSP_Nums.

IMO, two LSP_Nums are required to identify the reverse direction tunnel from
the forward direction tunnel identifiers and vice versa.

If we want to combine them as single LSP identifier, the LSP identifier
should be as follows.

Tunnel LSP identifier:
Src-Global_Node_ID::Src-Tunnel_Num::Src-LSP_Num::Dst-Global_Node_ID::Dst-Tunnel_Num::Dst-LSP_Num

Example: G1_R1::100::*1*::G3_R3::200::*2*

Please correct me if I'm wrong in the understanding.

BR,

Venkat.

On Tue, Jul 13, 2010 at 5:00 AM, <Internet-Drafts@ietf.org> wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiprotocol Label Switching Working
> Group of the IETF.
>
>
>        Title           : MPLS-TP Identifiers
>        Author(s)       : M. Bocci, G. Swallow
>        Filename        : draft-ietf-mpls-tp-identifiers-02.txt
>        Pages           : 14
>        Date            : 2010-07-12
>
> This document specifies identifiers for MPLS-TP objects.  Included
> are identifiers conformant to existing ITU conventions and
> identifiers which are compatible with existing IP, MPLS, GMPLS, and
> Pseudowire definitions.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-identifiers-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.
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>


-- 
Best Regards,
Venkatesan Mahalingam.

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

<div>
<p class=3D"MsoNormal">George,</p>
<p class=3D"MsoNormal">Please find the comments inlined &lt;VM&gt; on this =
MPLS_TP identifiers draft,</p>
<p class=3D"MsoNormal">Section 5.1.=A0 MPLS-TP Point to Point Tunnel Identi=
fiers<br>It is RECOMMENDED that the IF_Num be auto-generated by adding<br>=
=A0=A0 2^31 to the local Tunnel_Num</p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">&lt;VM&gt; What was the inte=
ntion to auto-generate IF_Num by adding 2^31 to the local Tunnel_Num?</font=
></p>
<p class=3D"MsoNormal">7.2.2.2.=A0 MEP_IDs for Pseudowires<br>=A0where the =
Node_ID is the node in which the MEP is located and<br>=A0=A0 Tunnel_Num is=
 the tunnel number unique to that node.<br><font color=3D"#3366ff">&lt;VM&g=
t; Typo error, please correct it.</font></p>

<p class=3D"MsoNormal">=A06.=A0 Pseudowire Path Identifiers</p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0 AGI:Src-Global_ID::Src-Node_ID::Src-=
AC_ID::Dst-Global_ID::<br>=A0=A0=A0=A0=A0 Dst-Node_ID::Dst-AC_ID<br><font c=
olor=3D"#3366ff">&lt;VM&gt; Does FEC 129 AII Type 2 configuration applicabl=
e for both manual and signalling PWs?<br>
=A0=A0=A0=A0 How to represent this AC_ID in the PW mibs? Will there be any =
augmentation in the PW AC mibs (PW-ENET-STD-MIB)?</font></p>
<p class=3D"MsoNormal">GS: In Stockholm I was convinced that for ICC based =
identifiers, only the MEG-ID and/or ME-ID would need to be configured at va=
rious points along an LSP.=A0 Much has changed on this project since then.=
=A0 Is what we have not sufficient?</p>

<p class=3D"MsoNormal"><font color=3D"#3366ff">&lt;VM&gt;=A0 What I infer f=
rom your response is, ICC based identifiers are applicable only for the MEG=
-ID and/or ME-ID identification. So, does it mean that ICC based operator e=
nvironment also, MPLS-TP LSP will be created using Global_ID? If the answer=
 is yes, i.e Global_Id and ICC should co-exist for creating/monitoring the =
MPLS-TP tunnel, in that case can&#39;t we completely eliminate the need of =
ICC based identifier and Global_ID identifier can alone be used for creatin=
g/monitoring the MPLS-TP tunnel?</font></p>

<p class=3D"MsoNormal">=A07.1.2.1.=A0 MPLS-TP LSP MEG_IDs<br>=A0Since a MEG=
 pertains to a single MPLS-TP LSP, IP compatible MEG_IDs<br>=A0=A0 for MPLS=
-TP LSPs are simply the corresponding LSP_IDs</p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">&lt;VM&gt; For uni-direction=
al/bi-directional tunnel, one MEG is associated with only one LSP (ME).<br>=
For P2MP unidirectional tunnel, one MEG is associated with multiple destina=
tion LSPs (MEs)<br>
Is this understanding correct?</font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">&lt;VM&gt; How to configure =
multiple client MEGs in a server MEG? I believe, we don&#39;t follow the IT=
U-T Y1731 MEG level concept in MPLS-TP. Please give us some insight into th=
e client MEG and server MEG handling for MPLS-TP.</font></p>

<p class=3D"MsoNormal">=A0&gt;&gt; 2. In your draft, an LSP is identified b=
y the combination of Src-Global_ID,<br>&gt;&gt; Src-Node_ID, Src-Tunnel_Num=
, Dst-Global_ID, Dst-Node_ID, Dst-Tunnel_Num,<br>&gt;&gt; LSP_Num, this is =
fine for unidirectional and co-routed bidirectional LSP,<br>
&gt;&gt; but it is not enough for associated bidirectional LSP that is comb=
ined with<br>&gt;&gt; two reverse unidirectional LSPs and IMHO two LSP_Nums=
 are required.</p>
<p class=3D"MsoNormal">&gt;We should discuss this (and the above if you lik=
e) in Maastricht.</p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">&lt;VM&gt; I agree with Mach=
 Chen for two LSP_Nums for associated bi-directional tunnel, </font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">For example, consider the be=
low topology,</font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">All routers are in different=
 Global_ID operators domain.</font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">=A0 R1-----R2---------R3<br>=
=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<b=
r>=A0 |______R4_____|</font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">Tunnel LSP identifier: Src-G=
lobal_Node_ID::Src-Tunnel_Num::Dst-Global_Node_ID::Dst-Tunnel_Num::LSP_Num<=
/font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">Co-routed bi-directional tun=
nel:<br>Co-routed bi-directional tunnel (Tnl_Num=3D100, LSP_Num=3D1, Src=3D=
R1, Dst=3DR3) is established from R1 to R3 via R2.<br>Forward and reverse d=
irections LSP identifier: G1_R1::100::G3_R3::100::1</font></p>

<p class=3D"MsoNormal"><font color=3D"#3366ff">Associated bi-directional tu=
nnel:<br>Associated bi-directional tunnel is established from R1 to R3 via =
R2 for forward direction.<br>For this forward direction, LSP identifier is:=
 G1_R1::100::G3_R3::200::<strong>1<br>
</strong>For reverse direction, a LSP from R3 to R1 via R4 may exist. <br>F=
or this reverse direction LSP identifier: G3_R3::200::G1_R1::100::<strong>2=
<br></strong></font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">If I assume that the above s=
cenario is valid, we can combine these two different LSPs as a single bidir=
ectional LSP only when we have two LSP_Nums.</font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">IMO, two LSP_Nums are requir=
ed to identify the reverse direction tunnel from the forward direction tunn=
el identifiers and vice versa. </font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">If we want to combine them a=
s single LSP identifier, the LSP identifier should be as follows.</font></p=
>
<p class=3D"MsoNormal"><font color=3D"#3366ff">Tunnel LSP identifier: Src-G=
lobal_Node_ID::Src-Tunnel_Num::Src-LSP_Num::Dst-Global_Node_ID::Dst-Tunnel_=
Num::Dst-LSP_Num</font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">Example: G1_R1::100::<strong=
>1</strong>::G3_R3::200::<strong>2</strong></font></p>
<p class=3D"MsoNormal"><font color=3D"#3366ff">Please correct me if I&#39;m=
 wrong in the understanding.</font></p>
<p class=3D"MsoNormal">BR,</p>
<p class=3D"MsoNormal">Venkat.<br></p>
<p class=3D"MsoNormal">On Tue, Jul 13, 2010 at 5:00 AM, <span dir=3D"ltr">&=
lt;<a href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a>=
&gt;</span> wrote:<br></p></div>
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">A New Internet-Draft is availabl=
e from the on-line Internet-Drafts directories.<br>This draft is a work ite=
m of the Multiprotocol Label Switching Working Group of the IETF.<br>
<br><br>=A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : MPLS-TP Identifiers<br>=
=A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : M. Bocci, G. Swallow<br>=A0 =A0 =A0 =
=A0Filename =A0 =A0 =A0 =A0: draft-ietf-mpls-tp-identifiers-02.txt<br>=A0 =
=A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 14<br>=A0 =A0 =A0 =A0Date =A0 =A0 =
=A0 =A0 =A0 =A0: 2010-07-12<br>
<br>This document specifies identifiers for MPLS-TP objects. =A0Included<br=
>are identifiers conformant to existing ITU conventions and<br>identifiers =
which are compatible with existing IP, MPLS, GMPLS, and<br>Pseudowire defin=
itions.<br>
<br>A URL for this Internet-Draft is:<br><a href=3D"http://www.ietf.org/int=
ernet-drafts/draft-ietf-mpls-tp-identifiers-02.txt" target=3D"_blank">http:=
//www.ietf.org/internet-drafts/draft-ietf-mpls-tp-identifiers-02.txt</a><br=
>
<br>Internet-Drafts are also available by anonymous FTP at:<br><a href=3D"f=
tp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp.ietf.org/in=
ternet-drafts/</a><br><br>Below is the data which will enable a MIME compli=
ant mail reader<br>
implementation to automatically retrieve the ASCII version of the<br>Intern=
et-Draft.<br><br><br>_______________________________________________<br>mpl=
s mailing list<br><a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">https=
://www.ietf.org/mailman/listinfo/mpls</a><br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Best Regards,<br>Ve=
nkatesan Mahalingam.<br>

--001636ed675813fca6048b46b80d--

From wwwrun@core3.amsl.com  Tue Jul 13 09:22:39 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 9E3A93A6A42; Tue, 13 Jul 2010 09:22:39 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20100713162239.9E3A93A6A42@core3.amsl.com>
Date: Tue, 13 Jul 2010 09:22:39 -0700 (PDT)
Cc: mpls mailing list <mpls@ietf.org>, mpls chair <mpls-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [mpls] Document Action: 'Multiprotocol Label Switching Transport Profile Survivability Framework' to Informational RFC
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2010 16:22:39 -0000

The IESG has approved the following document:

- 'Multiprotocol Label Switching Transport Profile Survivability 
   Framework '
   <draft-ietf-mpls-tp-survive-fwk-06.txt> as an Informational RFC


This document is the product of the Multiprotocol Label Switching Working Group. 

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-survive-fwk-06.txt

Technical Summary

  This document specifies the taxonomy for MPLS-TP survivability,
  the surviability architecture and key components need to meet
  survivability requiremetns. Network survivability is the network's
  ability to recover traffic delivery following the failure or
  degradation of traffic caused by a network fault or a denial
  of service attacks. Survivability isa critical characteristic of
  reliable services in transport networks.

  The MPLS transport profiles are designed to be consistent with
  existing transport network operations and management models.

  Some of the MPLS transport profile recovery mechanisms do not
  depend on a control plane but use OAM mechanisms or management
  actions to trigger recovery actions.

  MPLS and GMPLS protection mechanisms are applicable in for the
  MPLS transport profiles. It is also be possible to provision and
  manage the related protection entities and functions defined in MPLS
  and GMPLS using the management plane. Regardless of whether
  an OAM, management, or control plane initiation mechanism is used,
  the protection-switching operation is a data-plane operation.


Working Group Summary

  Since the document is an output from the MPLS-TP project it is the
  joint output of several IETF working groups and Qustion 9, 10, 12 and
  14 of ITU-T SG15.

Document Quality

The document is well reviewed in all the groups mentioned above.

Personnel

Loa Andersson is Document Shepherd for this document.
Stewart Bryant is the Responsible Area Director.

RFC Editor Note

===========
1) Section 1.2: r/in[RFC4427]/in [RFC4427]

2) Section 2: I a verb is missing:

 The terms "defect" and "failure" are used interchangeably to
 indicate any defect or failure in the sense that they defined in
                                                      ^ are
 [G.806].

3) Section 4.1: r/OAM mechanisms ,/OAM mechanisms,

4) Section 4.1.3: Add period: [MPLS-TP-OAM-Framework].
                                                     ^

5) Section 4.4.2: Add period: (1:n or m:n).
                                          ^

6) Section 4.4.3: Add period: service degradation.
                                                 ^

7) Section 4.7: Missing ): (see Section
   4.5 associated with the protection function. 

8) Section 4.7.6: Extra "1"?:

 Additionally, note that the shared-protection resources could be used
 1 to carry extra traffic,  for example, in Figure 4, an LSP JPQRK
 ^ ?

9) Section 6.1.1: Missing period: etc.).
                                       ^

10) Section 6.1.2: Missing periods (X2): recovery entity.
                                                       ^

11) Section 6.4: r/(Maintenance Group Intermediate Points (MIPs)/MIPs
(Maintenance Group Intermediate Points)

12) Section 6.5: r/t1he/the

===========


Add a new last para to section 4.3.2

In an MPLS-TP network, the degree to which a resource is shared 
between LSPs is a policy issue. This policy may be applied to the
resource or to the LSPs, and may be pre-configured, configured 
per LSP and installed during LSP establishment, or may be 
dynamically configured.

==========================

In Section 4.7.4

Old
An in-band, data-plane protocol for use in MPLS-TP networks will 
be documented in [MPLS-TP-Linear-Protection] for this purpose.

New 
An in-band, data-plane protocol for use in MPLS-TP networks will 
be documented in [MPLS-TP-Linear-Protection] for linear protection
(ring protection is discussed in Section 4.8 of this document).

==========================

In Section 1.4. Scope of this Framework

Please change all instances of the word "level" to "grade"

In Section 4 Functional Architecture (main section)

Please change the word "level" to "grade"

In Section 4.1.1.  Operator Control

Please change the word "level" to "grade"

In Section 4.3 Level of Recovery (main section)

Please change the word "level" to "grade"

In Section 4.3.2 Shared protection

Please change the word "level" to "grade"

In Section 4.4.1 Link-Level Protection

OLD
   Link-level protection offers the following levels of protection:
NEW
   Link-level protection offers the following grades of protection:
END

In Section 4.4.2.  Alternate Paths and Segments

OLD
   Different levels of protection may be provided:
NEW
   Different grades of protection may be provided:
END

In Section 4.4.3.  Protection Tunnels

OLD
   Different levels of protection may be provided:
NEW
   Different grades of protection may be provided:
END

In Section 4.6.  Protection in Different Topologies

OLD
concatenation of recovery domains, each providing some level of
recovery in part of the network.
NEW
concatenation of recovery domains, each providing some grade of
recovery in part of the network.
END

In Section 4.9.  Recovery in Layered Networks
Please change all instances of the word "level" to "grade". 
However please DO NOT change "Layered" in the title of this section.

In Section 7.  Pseudowire Recovery Considerations

OLD
The pseudowire may, itself, require a level of protection, in order
to meet the service-level guarantees of its SLA.  
NEW
The pseudowire may, itself, require protection, in order
to meet the service-level guarantees of its SLA.  
END

===============================
Change title of section

OLD
4.2.  Elements of Recovery
NEW
4.2.  Recovery Scope
END

===============================

In Section 4.2.1.  Span Recovery

OLD
   Moving the protected LSP to another TE link between the same pair of
   neighbors is a form of segment recovery and is described in Section
   4.2.2.
NEW
   Moving the protected LSP to another TE link between the same pair of
   neighbors is a form of segment recovery and not a form of span
recovery.
   Segment Recovery is described in Section 4.2.2.
END

==============================

In Section 4.3.  Levels of Recovery

New last paragraph

The selection of the recovery grade and schemes to satisfy the 
service grades for an LSP using available network resources is 
subject to network and local policy and may be pre-designated 
through network planning or may be dynamically determined 
by the network.

============================

In Section 4.4.3.  Protection Tunnels

OLD
   A protection tunnel is a hierarchical LSP that is pre-provisioned in
   order to protect against a failure condition along a sequence of
   spans in the network. 
NEW
   A protection tunnel is pre-provisioned in
   order to protect against a failure condition along a sequence of
   spans in the network. This may be achieved using LSP heirarchy. 
END

============================


From Manuel.Paul@telekom.de  Tue Jul 13 10:17:27 2010
Return-Path: <Manuel.Paul@telekom.de>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57AAF3A6840 for <mpls@core3.amsl.com>; Tue, 13 Jul 2010 10:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-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 vhhXxbSZzTPj for <mpls@core3.amsl.com>; Tue, 13 Jul 2010 10:17:26 -0700 (PDT)
Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by core3.amsl.com (Postfix) with ESMTP id 80F3B3A6B4E for <mpls@ietf.org>; Tue, 13 Jul 2010 10:17:10 -0700 (PDT)
Received: from s4de9jsaanm.mgb.telekom.de (HELO S4DE9JSAANM.ost.t-com.de) ([10.125.177.122]) by tcmail81.telekom.de with ESMTP; 13 Jul 2010 19:17:15 +0200
Received: from S4DE9JSAANI.ost.t-com.de ([10.125.177.223]) by S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Jul 2010 19:17:14 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 13 Jul 2010 19:17:19 +0200
Message-ID: <40FB0FFB97588246A1BEFB05759DC8A00478DFEB@S4DE9JSAANI.ost.t-com.de>
In-Reply-To: <4C29EB04.4080609@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping
thread-index: AcsXiQwrRPXcalofThqIiNZT5vaiZQLJc/bw
References: <4C29EB04.4080609@pi.nu>
From: <Manuel.Paul@telekom.de>
To: <mpls@ietf.org>
X-OriginalArrivalTime: 13 Jul 2010 17:17:14.0868 (UTC) FILETIME=[3D06FB40:01CB22AF]
Subject: Re: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2010 17:17:27 -0000

WWVzIC8gU3VwcG9ydC4NCg0KQmVzdCBSZWdhcmRzIA0KTWFudWVsIA0KDQoNCj4gLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogbXBscy1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86
bXBscy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YNCj4gTG9hIEFuZGVyc3Nvbg0KPiBT
ZW50OiBUdWVzZGF5LCBKdW5lIDI5LCAyMDEwIDI6NDYgUE0NCj4gVG86IG1wbHNAaWV0Zi5vcmcN
Cj4gQ2M6IEFkcmlhbiBGYXJyZWw7IFN0ZXdhcnQgQnJ5YW50DQo+IFN1YmplY3Q6IFttcGxzXSBw
b2xsIG9uIGRyYWZ0LWNoZW4tbXBscy1yZXR1cm4tcGF0aC1zcGVjaWZpZWQtbHNwLXBpbmcNCj4g
DQo+IFdvcmtpbmcgR3JvdXAsDQo+IA0KPiB0aGlzIGVtYWlsIGlzIHRvIHN0YXJ0IHBvbGwgdG8g
YWRvcHQNCj4gZHJhZnQtY2hlbi1tcGxzLXJldHVybi1wYXRoLXNwZWNpZmllZC1sc3AtcGluZw0K
PiBhcyBhbiBNUExTIHdvcmtpbmcgZ3JvdXAgZHJhZnQuDQo+IA0KPiBBZnRlciByZWNlbnQgZXhw
ZXJpZW5jZSwgdGhlIGNoYWlycyB3b3VsZCBsaWtlIHRvIHJlbWluZCB5b3UgYWxsDQo+IHdoYXQg
aXQgbWVhbnMgdG8gY29uZHVjdCBhIHBvbGwgdG8gYWRvcHQgYSBkcmFmdCBhcyBhIHdvcmtpbmcg
Z3JvdXANCj4gZHJhZnQuDQo+IA0KPiAtIFBsZWFzZSByZWNhbGwgdGhhdCB0aGUgSUVURiBkb2Vz
IG5vdCAidm90ZS4iIFBvbGxzIG9mIGEgd29ya2luZw0KPiAgICBncm91cCBhcmUgdG8gZ2F0aGVy
IGluZm9ybWF0aW9uIHRvIGhlbHAgdGhlIGNoYWlycyBtYWtlIHRoZWlyDQo+ICAgIGRlY2lzaW9u
cy4gVm90aW5nIGlzIG5vdCBwYXJ0IG9mIHRoZSBub3JtYWwgd29ya2luZyBtZXRob2RzIG9mDQo+
ICAgIGFuIElFVEYgd29ya2luZyBncm91cC4NCj4gDQo+IC0gVGhlICJyb3VnaCBjb25zZW5zdXMi
IHByb2Nlc3MgdXNlZCBpbiB0aGUgd29ya2luZyBncm91cCBhc3N1bWVzDQo+ICAgIHRoYXQgcGVv
cGxlIGV4cHJlc3Npbmcgb3BpbmlvbnMgYXJlIGFsc28gcGFydGljaXBhdGluZyBpbiB0aGUNCj4g
ICAgZGV2ZWxvcG1lbnQgb2Ygc3RhbmRhcmRzIGRvY3VtZW50cy4NCj4gDQo+IC0gU3Vic2NyaXB0
aW9uIHRvIHRoZSBsaXN0IHNwZWNpZmljYWxseSB0byBleHByZXNzIGFuIG9waW5pb24gaXMNCj4g
ICAgbm90aWNlZCBieSB0aGUgY2hhaXJzIHdobyBoYXMgYWNjZXNzIHRvIGluZm9ybWF0aW9uIG9u
IHRoZSBuZXcgbGlzdA0KPiAgICBtZW1iZXJzLiBTdWNoIGJlaGF2aW9yIGlzIG5vdCBwYXJ0IG9m
IHRoZSBub3JtYWwgd29ya2luZyBtZXRob2RzLg0KPiANCj4gLSBUaGUgcHVycG9zZSBvZiBhIHBv
bGwgZm9yIGFkb3B0aW9uIGlzIHRvIGhlbHAgdGhlIGNoYWlycyB1bmRlcnN0YW5kDQo+ICAgIHRo
ZSBsZXZlbCBvZiBzdXBwb3J0IGZvciBhIGRvY3VtZW50IChpLmUuIHdobyBoYXMgcmVhZCBpdCwg
d2hvDQo+ICAgIGJlbGlldmVzIGl0IGlzIGEgZ29vZCBzdGFydGluZyBwb2ludCBmb3Igd29ya2lu
ZyBncm91cCB3b3JrLCB3aG8NCj4gICAgd2lsbCBjb250cmlidXRlIHRvIHRoZSB3b3JrKSBhbmQg
d2hldGhlciB0aGVyZSBhcmUgYW55IHNpZ25pZmljYW50DQo+ICAgIHRlY2huaWNhbCBpc3N1ZXMu
IFN0YXRlbWVudHMgb2Ygb2JqZWN0aW9uIG11c3QgYmUgYmFja2VkIHVwIGJ5DQo+ICAgIHByb3Bl
ciB0ZWNobmljYWwgcmVhc29ucy4NCj4gDQo+IFNvIHBsZWFzZSByZXNwb25kIHRvIHRoaXMgcG9s
bCBpbmRpY2F0aW5nIHdoZXRoZXIgeW91IHN1cHBvcnQgdGhlDQo+IGFkb3B0aW9uIG9mIHRoaXMg
ZHJhZnQgb3Igc3RhdGluZyB5b3VyIHRlY2huaWNhbCBpc3N1ZXMuDQo+IA0KPiBQbGVhc2UgYWxz
byBub3QgdGhhdCB0aGlzIGRyYWZ0IGhhcyBhZnRlciBhIGRpc2N1c3Npb24gd2l0aCB0aGUNCj4g
d29ya2luZyBncm91cCBjaGFpcnMgYmVlbiByZW5hbWVkLCBpdCB3YXMgZWFybGllciBrbm93IGFz
DQo+IGRyYWZ0LW5pdGluYi1tcGxzLXRwLWxzcC1waW5nLWV4dGVuc2lvbnMtMDEuDQo+IA0KPiBU
aGlzIHBvbGwgZW5kcyBlb2IgSnVseSAxMy4NCj4gDQo+IA0KPiBMb2EgYW5kIEdlb3JnZQ0KPiBt
cGxzIHdnIGNvLWNoYWlycw0KPiANCj4gLS0NCj4gDQo+IA0KPiBMb2EgQW5kZXJzc29uICAgICAg
ICAgICAgICAgICAgICAgICAgIGVtYWlsOiBsb2EuYW5kZXJzc29uQGVyaWNzc29uLmNvbQ0KPiBT
ciBTdHJhdGVneSBhbmQgU3RhbmRhcmRzIE1hbmFnZXIgICAgICAgICAgICBsb2FAcGkubnUNCj4g
RXJpY3Nzb24gSW5jICAgICAgICAgICAgICAgICAgICAgICAgICBwaG9uZTogKzQ2IDEwIDcxNyA1
MiAxMw0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKzQ2
IDc2NyA3MiA5MiAxMw0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPiBtcGxzIG1haWxpbmcgbGlzdA0KPiBtcGxzQGlldGYub3JnDQo+IGh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0K

From gregimirsky@gmail.com  Tue Jul 13 12:36:31 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C6A93A6B2E; Tue, 13 Jul 2010 12:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.687
X-Spam-Level: 
X-Spam-Status: No, score=-1.687 tagged_above=-999 required=5 tests=[AWL=0.912,  BAYES_00=-2.599]
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 WGO+m01wAFj5; Tue, 13 Jul 2010 12:36:06 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 8D86A3A6B77; Tue, 13 Jul 2010 12:32:16 -0700 (PDT)
Received: by vws14 with SMTP id 14so6491674vws.31 for <multiple recipients>; Tue, 13 Jul 2010 12:31:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=roCCxWVvJ7N00rnMWpRe9M6yDNlnc3M7/C5Rbnp/mug=; b=Mtj5kLtEpuwOFSZnzIJeTdcBx5SUt6jCv+vOzgFFzhqM4C51DVGbnbLN8nB0eNdbGC ki63cZ/pvs94Kt9y2ospo0WG5zU1qVaUZ3uVrXOZpFkOtGBsbjytrf4yTuvLysyoTUlR djpTcV7PPmYwWY2gIiBvzRYNaTRmLEV353KkM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ai/Cko9n1DTIqKpmQHjzLSa/utrmDznU8LoBzuHl+bfIYOh62v0fCpje9zB8Jq+FZd /Z/w8Pu9im2nbU/45K+KGoujDTgRWFfz9hGvjXhWdZG/NjtTRxbn5+tCnp4mvCzzxv0b JGKx0Z/yJco6C1i4/is5gJLIjrVXvyFzjqJmc=
MIME-Version: 1.0
Received: by 10.220.126.197 with SMTP id d5mr7957559vcs.29.1279049479048; Tue,  13 Jul 2010 12:31:19 -0700 (PDT)
Received: by 10.220.86.72 with HTTP; Tue, 13 Jul 2010 12:31:18 -0700 (PDT)
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com>
References: <AcseCEd9mnzzxo1OTmOJFTkIhCTCgg==> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com>
Date: Tue, 13 Jul 2010 12:31:18 -0700
Message-ID: <AANLkTims1ZxsDuxamWE28TqAlgeIywSCCbOzTx5FYVmh@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Shahram Davari <davari@broadcom.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2010 19:36:31 -0000

Dear Shahram, Authors and All,
below please find my notes:
- Abstract, first paragraph - extra "to enable"
- I believe that goal to transport PTP over MPLS PSN stated in
Abstract contradicts with declared in Introduction requirement to
perform TC function on LSR(s). Transport, in my view, assumes
transparency for payload, PTP in case.
- Providing or using TC capability by transient MPLS nodes might be
supported by ability to advertise such capability (or afinity). Then
LSP can be set suing this capability as a constrain.
- As mentioned by others, nodes that don't support TC should not be
affected and perform as LSR. (Not sure if non-TC capable node will be
considered for LER).

Regards,
Greg

On Wed, Jul 7, 2010 at 12:12 PM, Shahram Davari <davari@broadcom.com> wrote=
:
> Hi All,
>
>
>
> Please find attached our first draft of 1588 over MPLS. Since we have som=
e
> technical issues converting the Word format to Txt we couldn=92t =A0uploa=
d the
> draft before the cut-off date. However we will present the draft in the n=
ext
> IETF meeting and will upload the draft after the meeting.
>
>
>
> Note that the main WG is TicToc but may require consultation with MPLS an=
d
> PWE3 WGs.
>
>
>
> Thanks,
>
> Shahram Davari
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>

From hejia@huawei.com  Tue Jul 13 21:50:39 2010
Return-Path: <hejia@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 905FD3A6910; Tue, 13 Jul 2010 21:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.143
X-Spam-Level: **
X-Spam-Status: No, score=2.143 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, 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 HEIGQxAVcvfQ; Tue, 13 Jul 2010 21:50:36 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id B032B3A690F; Tue, 13 Jul 2010 21:50:35 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5J00MQF6SAZL@szxga01-in.huawei.com>; Wed, 14 Jul 2010 12:50:34 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5J00MXI6SAHI@szxga01-in.huawei.com>; Wed, 14 Jul 2010 12:50:34 +0800 (CST)
Received: from h48726 ([10.70.77.157]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5J00AD16SAKK@szxml04-in.huawei.com>; Wed, 14 Jul 2010 12:50:34 +0800 (CST)
Date: Wed, 14 Jul 2010 12:50:37 +0800
From: Jia HE <hejia@huawei.com>
To: Shahram Davari <davari@broadcom.com>
Message-id: <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: multipart/alternative; boundary="Boundary_(ID_bYwRpWPeiJdb1XPcrVoftQ)"
X-Priority: 3
X-MSMail-priority: Normal
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com>
Cc: mpls@ietf.org, pwe3@ietf.org, ticctoc@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 04:50:39 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_bYwRpWPeiJdb1XPcrVoftQ)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Hi Shahram,

One question about "PTP Label Range":

To my knowledge, label in MPLS network is a local matter. For example, we may have per-interface or per-platform label space. Will this specificed "PTP Label Range" conflict with the current in-use labels for common LSPs? 

B.R.
Jia

  ----- Original Message ----- 
  From: Shahram Davari 
  To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org 
  Sent: Thursday, July 08, 2010 3:12 AM
  Subject: [PWE3] 1588 over MPLS draft


  Hi All,

   

  Please find attached our first draft of 1588 over MPLS. Since we have some technical issues converting the Word format to Txt we couldn't  upload the draft before the cut-off date. However we will present the draft in the next IETF meeting and will upload the draft after the meeting.

   

  Note that the main WG is TicToc but may require consultation with MPLS and PWE3 WGs.

   

  Thanks,

  Shahram Davari



------------------------------------------------------------------------------


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

--Boundary_(ID_bYwRpWPeiJdb1XPcrVoftQ)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIiB4bWxu
czp2ID0gDQoidXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm8gPSANCiJ1cm46
c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiIHhtbG5zOncgPSANCiJ1cm46c2No
ZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczp4ID0gDQoidXJuOnNjaGVtYXMt
bWljcm9zb2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOnAgPSANCiJ1cm46c2NoZW1hcy1taWNy
b3NvZnQtY29tOm9mZmljZTpwb3dlcnBvaW50IiB4bWxuczphID0gDQoidXJuOnNjaGVtYXMtbWlj
cm9zb2Z0LWNvbTpvZmZpY2U6YWNjZXNzIiB4bWxuczpkdCA9IA0KInV1aWQ6QzJGNDEwMTAtNjVC
My0xMWQxLUEyOUYtMDBBQTAwQzE0ODgyIiB4bWxuczpzID0gDQoidXVpZDpCREM2RTNGMC02REEz
LTExZDEtQTJBMy0wMEFBMDBDMTQ4ODIiIHhtbG5zOnJzID0gDQoidXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpyb3dzZXQiIHhtbG5zOnogPSAiI1Jvd3NldFNjaGVtYSIgeG1sbnM6YiA9IA0KInVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOnB1Ymxpc2hlciIgeG1sbnM6c3MgPSANCiJ1
cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpzcHJlYWRzaGVldCIgeG1sbnM6YyA9IA0K
InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOmNvbXBvbmVudDpzcHJlYWRzaGVldCIg
eG1sbnM6b2RjID0gDQoidXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2RjIiB4bWxu
czpvYSA9IA0KInVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOmFjdGl2YXRpb24iIHht
bG5zOmh0bWwgPSANCiJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIiB4bWxuczpxID0g
DQoiaHR0cDovL3NjaGVtYXMueG1sc29hcC5vcmcvc29hcC9lbnZlbG9wZS8iIHhtbG5zOnJ0YyA9
IA0KImh0dHA6Ly9taWNyb3NvZnQuY29tL29mZmljZW5ldC9jb25mZXJlbmNpbmciIFhNTE5TOkQg
PSAiREFWOiIgWE1MTlM6UmVwbCA9IA0KImh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vcmVw
bC8iIHhtbG5zOm10ID0gDQoiaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9zaGFyZXBvaW50
L3NvYXAvbWVldGluZ3MvIiB4bWxuczp4MiA9IA0KImh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vb2ZmaWNlL2V4Y2VsLzIwMDMveG1sIiB4bWxuczpwcGRhID0gDQoiaHR0cDovL3d3dy5wYXNz
cG9ydC5jb20vTmFtZVNwYWNlLnhzZCIgeG1sbnM6b2lzID0gDQoiaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9zaGFyZXBvaW50L3NvYXAvb2lzLyIgeG1sbnM6ZGlyID0gDQoiaHR0cDovL3Nj
aGVtYXMubWljcm9zb2Z0LmNvbS9zaGFyZXBvaW50L3NvYXAvZGlyZWN0b3J5LyIgeG1sbnM6ZHMg
PSANCiJodHRwOi8vd3d3LnczLm9yZy8yMDAwLzA5L3htbGRzaWcjIiB4bWxuczpkc3AgPSANCiJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL3NoYXJlcG9pbnQvZHNwIiB4bWxuczp1ZGMgPSAN
CiJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL2RhdGEvdWRjIiB4bWxuczp4c2QgPSANCiJo
dHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYSIgeG1sbnM6c3ViID0gDQoiaHR0cDovL3Nj
aGVtYXMubWljcm9zb2Z0LmNvbS9zaGFyZXBvaW50L3NvYXAvMjAwMi8xL2FsZXJ0cy8iIHhtbG5z
OmVjID0gDQoiaHR0cDovL3d3dy53My5vcmcvMjAwMS8wNC94bWxlbmMjIiB4bWxuczpzcCA9IA0K
Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2ludC8iIHhtbG5zOnNwcyA9IA0K
Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2ludC9zb2FwLyIgeG1sbnM6eHNp
ID0gDQoiaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbWEtaW5zdGFuY2UiIHhtbG5zOnVk
Y3MgPSANCiJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL2RhdGEvdWRjL3NvYXAiIHhtbG5z
OnVkY3hmID0gDQoiaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9kYXRhL3VkYy94bWxmaWxl
IiB4bWxuczp1ZGNwMnAgPSANCiJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL2RhdGEvdWRj
L3BhcnR0b3BhcnQiIHhtbG5zOndmID0gDQoiaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9z
aGFyZXBvaW50L3NvYXAvd29ya2Zsb3cvIiB4bWxuczpkc3NzID0gDQoiaHR0cDovL3NjaGVtYXMu
bWljcm9zb2Z0LmNvbS9vZmZpY2UvMjAwNi9kaWdzaWctc2V0dXAiIHhtbG5zOmRzc2kgPSANCiJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA2L2RpZ3NpZyIgeG1sbnM6bWRz
c2kgPSANCiJodHRwOi8vc2NoZW1hcy5vcGVueG1sZm9ybWF0cy5vcmcvcGFja2FnZS8yMDA2L2Rp
Z2l0YWwtc2lnbmF0dXJlIiB4bWxuczptdmVyID0gDQoiaHR0cDovL3NjaGVtYXMub3BlbnhtbGZv
cm1hdHMub3JnL21hcmt1cC1jb21wYXRpYmlsaXR5LzIwMDYiIHhtbG5zOm0gPSANCiJodHRwOi8v
c2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zOm1yZWxzID0g
DQoiaHR0cDovL3NjaGVtYXMub3BlbnhtbGZvcm1hdHMub3JnL3BhY2thZ2UvMjAwNi9yZWxhdGlv
bnNoaXBzIiB4bWxuczpzcHdwID0gDQoiaHR0cDovL21pY3Jvc29mdC5jb20vc2hhcmVwb2ludC93
ZWJwYXJ0cGFnZXMiIHhtbG5zOmV4MTJ0ID0gDQoiaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNv
bS9leGNoYW5nZS9zZXJ2aWNlcy8yMDA2L3R5cGVzIiB4bWxuczpleDEybSA9IA0KImh0dHA6Ly9z
Y2hlbWFzLm1pY3Jvc29mdC5jb20vZXhjaGFuZ2Uvc2VydmljZXMvMjAwNi9tZXNzYWdlcyIgeG1s
bnM6cHB0c2wgPSANCiJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL3NoYXJlcG9pbnQvc29h
cC9TbGlkZUxpYnJhcnkvIiB4bWxuczpzcHNsID0gDQoiaHR0cDovL21pY3Jvc29mdC5jb20vd2Vi
c2VydmljZXMvU2hhcmVQb2ludFBvcnRhbFNlcnZlci9QdWJsaXNoZWRMaW5rc1NlcnZpY2UiIA0K
WE1MTlM6WiA9ICJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOiIgeG1sbnM6c3QgPSAiASI+PEhF
QUQ+DQo8TUVUQSBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZSBjb250ZW50PSJ0ZXh0L2h0bWw7IGNo
YXJzZXQ9aXNvLTg4NTktMSI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4wMC4yOTAwLjM2NzYi
IG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPkBmb250LWZhY2Ugew0KCWZvbnQtZmFtaWx5OiBDYW1i
cmlhIE1hdGg7DQp9DQpAZm9udC1mYWNlIHsNCglmb250LWZhbWlseTogQ2FsaWJyaTsNCn0NCkBw
YWdlIFNlY3Rpb24xIHtzaXplOiA4LjVpbiAxMS4waW47IG1hcmdpbjogMS4waW4gMS4waW4gMS4w
aW4gMS4waW47IH0NClAuTXNvTm9ybWFsIHsNCglGT05ULVNJWkU6IDExcHQ7IE1BUkdJTjogMGlu
IDBpbiAwcHQ7IEZPTlQtRkFNSUxZOiAiQ2FsaWJyaSIsInNhbnMtc2VyaWYiDQp9DQpMSS5Nc29O
b3JtYWwgew0KCUZPTlQtU0laRTogMTFwdDsgTUFSR0lOOiAwaW4gMGluIDBwdDsgRk9OVC1GQU1J
TFk6ICJDYWxpYnJpIiwic2Fucy1zZXJpZiINCn0NCkRJVi5Nc29Ob3JtYWwgew0KCUZPTlQtU0la
RTogMTFwdDsgTUFSR0lOOiAwaW4gMGluIDBwdDsgRk9OVC1GQU1JTFk6ICJDYWxpYnJpIiwic2Fu
cy1zZXJpZiINCn0NCkE6bGluayB7DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVDT1JBVElPTjogdW5k
ZXJsaW5lOyBtc28tc3R5bGUtcHJpb3JpdHk6IDk5DQp9DQpTUEFOLk1zb0h5cGVybGluayB7DQoJ
Q09MT1I6IGJsdWU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJsaW5lOyBtc28tc3R5bGUtcHJpb3Jp
dHk6IDk5DQp9DQpBOnZpc2l0ZWQgew0KCUNPTE9SOiBwdXJwbGU7IFRFWFQtREVDT1JBVElPTjog
dW5kZXJsaW5lOyBtc28tc3R5bGUtcHJpb3JpdHk6IDk5DQp9DQpTUEFOLk1zb0h5cGVybGlua0Zv
bGxvd2VkIHsNCglDT0xPUjogcHVycGxlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZTsgbXNv
LXN0eWxlLXByaW9yaXR5OiA5OQ0KfQ0KU1BBTi5FbWFpbFN0eWxlMTcgew0KCUNPTE9SOiB3aW5k
b3d0ZXh0OyBGT05ULUZBTUlMWTogIkNhbGlicmkiLCJzYW5zLXNlcmlmIjsgbXNvLXN0eWxlLXR5
cGU6IHBlcnNvbmFsLWNvbXBvc2UNCn0NCi5Nc29DaHBEZWZhdWx0IHsNCgltc28tc3R5bGUtdHlw
ZTogZXhwb3J0LW9ubHkNCn0NCkRJVi5TZWN0aW9uMSB7DQoJcGFnZTogU2VjdGlvbjENCn0NCjwv
U1RZTEU+DQo8IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCiA8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0
PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQogPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KICA8bzppZG1hcCB2
OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCiA8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZd
LS0+PC9IRUFEPg0KPEJPRFkgbGFuZz1FTi1VUyB2TGluaz1wdXJwbGUgbGluaz1ibHVlIGJnQ29s
b3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj5IaSBT
aGFocmFtLDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNp
emU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3
OyBzaXplPTI+T25lIHF1ZXN0aW9uIGFib3V0ICJQVFAgTGFiZWwgUmFuZ2UiOjwvRk9OVD48L0RJ
Vj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+Jm5ic3A7
PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+VG8gbXkga25v
d2xlZGdlLCBsYWJlbCBpbiBNUExTIG5ldHdvcmsgaXMgYSBsb2NhbCANCm1hdHRlci4gRm9yIGV4
YW1wbGUsIHdlIG1heSBoYXZlIHBlci1pbnRlcmZhY2Ugb3IgcGVyLXBsYXRmb3JtIGxhYmVsIHNw
YWNlLiBXaWxsIA0KdGhpcyBzcGVjaWZpY2VkICJQVFAgTGFiZWwgUmFuZ2UiIGNvbmZsaWN0IHdp
dGggdGhlIGN1cnJlbnQgaW4tdXNlJm5ic3A7bGFiZWxzIA0KZm9yIGNvbW1vbiBMU1BzPyA8L0ZP
TlQ+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0K
PERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPkIuUi48L0ZPTlQ+PC9ESVY+
DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+SmlhPC9GT05UPjwvRElW
Pg0KPERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8
L0RJVj4NCjxCTE9DS1FVT1RFIA0Kc3R5bGU9IlBBRERJTkctUklHSFQ6IDBweDsgUEFERElORy1M
RUZUOiA1cHg7IE1BUkdJTi1MRUZUOiA1cHg7IEJPUkRFUi1MRUZUOiAjMDAwMDAwIDJweCBzb2xp
ZDsgTUFSR0lOLVJJR0hUOiAwcHgiPg0KICA8RElWIHN0eWxlPSJGT05UOiA5cHQgJiMyMzQzNTsm
IzIwMzA3OyI+LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSA8L0RJVj4NCiAgPERJViBzdHls
ZT0iQkFDS0dST1VORDogI2U0ZTRlNDsgRk9OVDogOXB0ICYjMjM0MzU7JiMyMDMwNzs7IGZvbnQt
Y29sb3I6IGJsYWNrIj48Qj5Gcm9tOjwvQj4gDQogIDxBIHRpdGxlPWRhdmFyaUBicm9hZGNvbS5j
b20gaHJlZj0ibWFpbHRvOmRhdmFyaUBicm9hZGNvbS5jb20iPlNoYWhyYW0gDQogIERhdmFyaTwv
QT4gPC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQ6IDlwdCAmIzIzNDM1OyYjMjAzMDc7Ij48Qj5U
bzo8L0I+IDxBIHRpdGxlPXRpY2N0b2NAaWV0Zi5vcmcgDQogIGhyZWY9Im1haWx0bzp0aWNjdG9j
QGlldGYub3JnIj50aWNjdG9jQGlldGYub3JnPC9BPiA7IDxBIHRpdGxlPW1wbHNAaWV0Zi5vcmcg
DQogIGhyZWY9Im1haWx0bzptcGxzQGlldGYub3JnIj5tcGxzQGlldGYub3JnPC9BPiA7IDxBIHRp
dGxlPW1wbHMtdHBAaWV0Zi5vcmcgDQogIGhyZWY9Im1haWx0bzptcGxzLXRwQGlldGYub3JnIj5t
cGxzLXRwQGlldGYub3JnPC9BPiA7IDxBIHRpdGxlPXB3ZTNAaWV0Zi5vcmcgDQogIGhyZWY9Im1h
aWx0bzpwd2UzQGlldGYub3JnIj5wd2UzQGlldGYub3JnPC9BPiA8L0RJVj4NCiAgPERJViBzdHls
ZT0iRk9OVDogOXB0ICYjMjM0MzU7JiMyMDMwNzsiPjxCPlNlbnQ6PC9CPiBUaHVyc2RheSwgSnVs
eSAwOCwgMjAxMCAzOjEyIEFNPC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQ6IDlwdCAmIzIzNDM1
OyYjMjAzMDc7Ij48Qj5TdWJqZWN0OjwvQj4gW1BXRTNdIDE1ODggb3ZlciBNUExTIGRyYWZ0PC9E
SVY+DQogIDxESVY+PEJSPjwvRElWPg0KICA8RElWIGNsYXNzPVNlY3Rpb24xPg0KICA8UCBjbGFz
cz1Nc29Ob3JtYWw+SGkgQWxsLDxvOnA+PC9vOnA+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+
PG86cD4mbmJzcDs8L286cD48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD5QbGVhc2UgZmluZCBh
dHRhY2hlZCBvdXIgZmlyc3QgZHJhZnQgb2YgMTU4OCBvdmVyIE1QTFMuIA0KICBTaW5jZSB3ZSBo
YXZlIHNvbWUgdGVjaG5pY2FsIGlzc3VlcyBjb252ZXJ0aW5nIHRoZSBXb3JkIGZvcm1hdCB0byBU
eHQgd2UgDQogIGNvdWxkbpJ0ICZuYnNwO3VwbG9hZCB0aGUgZHJhZnQgYmVmb3JlIHRoZSBjdXQt
b2ZmIGRhdGUuIEhvd2V2ZXIgd2Ugd2lsbCANCiAgcHJlc2VudCB0aGUgZHJhZnQgaW4gdGhlIG5l
eHQgSUVURiBtZWV0aW5nIGFuZCB3aWxsIHVwbG9hZCB0aGUgZHJhZnQgYWZ0ZXIgdGhlIA0KICBt
ZWV0aW5nLjxvOnA+PC9vOnA+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8
L286cD48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD5Ob3RlIHRoYXQgdGhlIG1haW4gV0cgaXMg
VGljVG9jIGJ1dCBtYXkgcmVxdWlyZSANCiAgY29uc3VsdGF0aW9uIHdpdGggTVBMUyBhbmQgUFdF
MyBXR3MuPG86cD48L286cD48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwv
bzpwPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPlRoYW5rcyw8bzpwPjwvbzpwPjwvUD4NCiAg
PFAgY2xhc3M9TXNvTm9ybWFsPlNoYWhyYW0gRGF2YXJpPG86cD48L286cD48L1A+PC9ESVY+DQog
IDxQPg0KICA8SFI+DQoNCiAgPFA+PC9QPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fPEJSPnB3ZTMgbWFpbGluZyANCiAgbGlzdDxCUj48QSBocmVmPSJtYWls
dG86cHdlM0BpZXRmLm9yZyI+cHdlM0BpZXRmLm9yZzwvQT48QlI+PEEgDQogIGhyZWY9Imh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHdlMyI+aHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9wd2UzPC9BPjxCUj48L0JMT0NLUVVPVEU+PC9CT0RZPjwvSFRN
TD4NCg==

--Boundary_(ID_bYwRpWPeiJdb1XPcrVoftQ)--

From davarish@yahoo.com  Tue Jul 13 23:31:28 2010
Return-Path: <davarish@yahoo.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1BD13A6965 for <mpls@core3.amsl.com>; Tue, 13 Jul 2010 23:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.885
X-Spam-Level: 
X-Spam-Status: No, score=0.885 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, REPTO_QUOTE_YAHOO=2.599]
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 PJwjLIKyoddA for <mpls@core3.amsl.com>; Tue, 13 Jul 2010 23:31:26 -0700 (PDT)
Received: from n15b.bullet.mail.mud.yahoo.com (n15b.bullet.mail.mud.yahoo.com [68.142.207.236]) by core3.amsl.com (Postfix) with SMTP id B00C43A682F for <mpls@ietf.org>; Tue, 13 Jul 2010 23:31:26 -0700 (PDT)
Received: from [68.142.200.221] by n15.bullet.mail.mud.yahoo.com with NNFMP; 14 Jul 2010 06:31:33 -0000
Received: from [66.196.97.154] by t9.bullet.mud.yahoo.com with NNFMP; 14 Jul 2010 06:31:33 -0000
Received: from [127.0.0.1] by omp207.mail.re3.yahoo.com with NNFMP; 14 Jul 2010 06:31:33 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 210865.87236.bm@omp207.mail.re3.yahoo.com
Received: (qmail 65211 invoked by uid 60001); 14 Jul 2010 06:31:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1279089093; bh=9iquuYZu0c3jDbZ8sKOFqe5AiSnbd5PtwNTmabMnFrI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=ZeSAbHg1YPcAcoLZSx+apzJopgmZvEHuFxqQXat/47JTdFg3iCN5rU6muwhNSdZxtGlVoiLxkhTejK71lLlVhTSabG+HsIUWsD49aE4eWeVQKhA9dGW4E6vP3n8c2PiJl0tRKN/rsa/skuJ8Y9SGtgSiM0DBHVG6C35nn/i5ewU=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=pqrFAhM7C+s8RRCNsygILXhhBqKWOq4RjKLnLdyN8QHZmcQw5TrxgDAEhnfNFk1sNKo706kwMr8K2eUAZDoHNGxef7dXRqB9yY67Z9/DfcoDySjbv7tIg4c+q3Wd2IzbEYzOgbWfmdh/RXXmkhdObr0NducWMgWLgm+q0COMCZo=;
Message-ID: <89571.47481.qm@web88402.mail.re1.yahoo.com>
X-YMail-OSG: Y7ww.6sVM1maDpdiTY6JVJyh1.5vo.lEBAenuKP4WN1ztqE NRAfRnjcK8O9dFd5vlZXkM_S4ZV8LZN0w2SKtMrrQ4TuUZycUIurIwRi20CC 5ZBGALHBbi3FgvUz0pPp5llAhAUMq2F8GvIT_YqIwz0FKwkBJBwJkhhChcWV AYc9_kkvL2gf5cd_1V.p1AFvo4nj9gcHP7l3DeaVGWlq5r3l.MGoygtKdywT OfKWZI0KrRrVoUf8Zj99PMIGbw6IDL_D9ZlS41BRGdN2tgTNE8Z.AOq6MsYk zDtJx52O4IJv.z7EA0P2ZqH8TtjAiA9In0IbHiYn.jTKhqoKC
Received: from [24.6.170.59] by web88402.mail.re1.yahoo.com via HTTP; Tue, 13 Jul 2010 23:31:32 PDT
X-Mailer: YahooMailRC/420.4 YahooMailWebService/0.8.104.274457
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com>
Date: Tue, 13 Jul 2010 23:31:32 -0700 (PDT)
From: "S. Davari" <davarish@yahoo.com>
To: Jia HE <hejia@huawei.com>, Shahram Davari <davari@broadcom.com>
In-Reply-To: <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-478951688-1279089092=:47481"
Cc: mpls@ietf.org, pwe3@ietf.org, ticctoc@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "S. Davari" <davarish@yahoo.com>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 06:31:28 -0000

--0-478951688-1279089092=:47481
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Jia,=0A=0ALabel range is a SHOULD requirements and not MUST. The reason =
for Label Range is =0Amainly for PHY chips that don't have large memory and=
 can't store a lot of =0ALabels. Otherwise the PTP LSP is setup via signali=
ng that specifies the LSP as =0Acarrying 1588.=0A=0ASo the answer is that i=
f a Label range is used it must be a Global range within =0Aa network and s=
hould not be used by any router for other applications.=0A=0AThanks,=0AShah=
ram=0A=0A=0A=0A________________________________=0AFrom: Jia HE <hejia@huawe=
i.com>=0ATo: Shahram Davari <davari@broadcom.com>=0ACc: mpls@ietf.org; pwe3=
@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org=0ASent: Tue, July 13, 2010 9:=
50:37 PM=0ASubject: Re: [mpls] [PWE3] 1588 over MPLS draft=0A=0A =0AHi Shah=
ram,=0A =0AOne question about "PTP Label Range":=0A =0ATo my knowledge, lab=
el in MPLS network is a local  matter. For example, we may =0Ahave per-inte=
rface or per-platform label space. Will  this specificed "PTP Label =0ARang=
e" conflict with the current in-use labels  for common LSPs? =0A=0A =0AB.R.=
=0AJia=0A =0A----- Original Message ----- =0A>From: Shahram    Davari =0A>T=
o: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org =0A>=
Sent: Thursday, July 08, 2010 3:12 AM=0A>Subject: [PWE3] 1588 over MPLS dra=
ft=0A>=0A>=0A>Hi All,=0A> =0A>Please find attached our first draft of 1588 =
over MPLS.    Since we have some =0A>technical issues converting the Word f=
ormat to Txt we    couldn=E2=80=99t  upload the =0A>draft before the cut-of=
f date. However we will    present the draft in the next =0A>IETF meeting a=
nd will upload the draft after the    meeting.=0A> =0A>Note that the main W=
G is TicToc but may require    consultation with MPLS and =0A>PWE3 WGs.=0A>=
 =0A>Thanks,=0A>Shahram Davari=0A________________________________=0A ______=
_________________________________________=0A>pwe3 mailing    list=0A>pwe3@i=
etf.org=0A>https://www.ietf.org/mailman/listinfo/pwe3=0A>=0A=0A
--0-478951688-1279089092=:47481
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:'Courier New', courier, monaco, monospac=
e, sans-serif;font-size:12pt"><div>Hi Jia,</div><div><br></div><div>Label r=
ange is a SHOULD requirements and not MUST. The reason for Label Range is m=
ainly for PHY chips that don't have large memory and can't store a lot of L=
abels. Otherwise the PTP LSP is setup via signaling that specifies the LSP =
as carrying 1588.</div><div><br></div><div>So the answer is that if a Label=
 range is used it must be a Global range within a network and should not be=
 used by any router for other applications.</div><div><br></div><div>Thanks=
,</div><div>Shahram</div><div style=3D"font-family:Courier New, courier, mo=
naco, monospace, sans-serif;font-size:12pt"><br><div style=3D"font-family:t=
imes new roman, new york, times, serif;font-size:12pt"><font size=3D"2" fac=
e=3D"Tahoma"><hr size=3D"1"><b><span style=3D"font-weight: bold;">From:</sp=
an></b>
 Jia HE &lt;hejia@huawei.com&gt;<br><b><span style=3D"font-weight: bold;">T=
o:</span></b> Shahram Davari &lt;davari@broadcom.com&gt;<br><b><span style=
=3D"font-weight: bold;">Cc:</span></b> mpls@ietf.org; pwe3@ietf.org; ticcto=
c@ietf.org; mpls-tp@ietf.org<br><b><span style=3D"font-weight: bold;">Sent:=
</span></b> Tue, July 13, 2010 9:50:37 PM<br><b><span style=3D"font-weight:=
 bold;">Subject:</span></b> Re: [mpls] [PWE3] 1588 over MPLS draft<br></fon=
t><br>=0A=0A =0A =0A<style> _filtered {=0Afont-family:Cambria Math;=0A}=0A =
_filtered {=0Afont-family:Calibri;=0A}=0A _filtered {margin:1.0in 1.0in 1.0=
in 1.0in;}=0AP.MsoNormal {=0AFONT-SIZE:11pt;MARGIN:0in 0in 0pt;FONT-FAMILY:=
"sans-serif";}=0ALI.MsoNormal {=0AFONT-SIZE:11pt;MARGIN:0in 0in 0pt;FONT-FA=
MILY:"sans-serif";}=0ADIV.MsoNormal {=0AFONT-SIZE:11pt;MARGIN:0in 0in 0pt;F=
ONT-FAMILY:"sans-serif";}=0AA:link {=0ACOLOR:blue;TEXT-DECORATION:underline=
;}=0ASPAN.MsoHyperlink {=0ACOLOR:blue;TEXT-DECORATION:underline;}=0AA:visit=
ed {=0ACOLOR:purple;TEXT-DECORATION:underline;}=0ASPAN.MsoHyperlinkFollowed=
 {=0ACOLOR:purple;TEXT-DECORATION:underline;}=0ASPAN.EmailStyle17 {=0ACOLOR=
:windowtext;FONT-FAMILY:"sans-serif";}=0A.MsoChpDefault {=0A}=0ADIV.Section=
1 {=0A}=0A</style>=0A=0A=0A<div><font face=3D"=E5=AE=8B=E4=BD=93" size=3D"2=
">Hi Shahram,</font></div>=0A<div><font face=3D"=E5=AE=8B=E4=BD=93" size=3D=
"2"></font>&nbsp;</div>=0A<div><font face=3D"=E5=AE=8B=E4=BD=93" size=3D"2"=
>One question about "PTP Label Range":</font></div>=0A<div><font face=3D"=
=E5=AE=8B=E4=BD=93" size=3D"2"></font>&nbsp;</div>=0A<div><font face=3D"=E5=
=AE=8B=E4=BD=93" size=3D"2">To my knowledge, label in MPLS network is a loc=
al =0Amatter. For example, we may have per-interface or per-platform label =
space. Will =0Athis specificed "PTP Label Range" conflict with the current =
in-use&nbsp;labels =0Afor common LSPs? </font><font face=3D"=E5=AE=8B=E4=BD=
=93" size=3D"2"></font></div>=0A<div><font face=3D"=E5=AE=8B=E4=BD=93" size=
=3D"2"></font>&nbsp;</div>=0A<div><font face=3D"=E5=AE=8B=E4=BD=93" size=3D=
"2">B.R.</font></div>=0A<div><font face=3D"=E5=AE=8B=E4=BD=93" size=3D"2">J=
ia</font></div>=0A<div><font face=3D"=E5=AE=8B=E4=BD=93" size=3D"2"></font>=
&nbsp;</div>=0A<blockquote style=3D"PADDING-RIGHT:0px;PADDING-LEFT:5px;MARG=
IN-LEFT:5px;BORDER-LEFT:#000000 2px solid;MARGIN-RIGHT:0px;">=0A  <div styl=
e=3D"FONT:9pt;">----- Original Message ----- </div>=0A  <div style=3D"BACKG=
ROUND:#e4e4e4;FONT:9pt;"><b>From:</b> =0A  <a rel=3D"nofollow" title=3D"dav=
ari@broadcom.com" ymailto=3D"mailto:davari@broadcom.com" target=3D"_blank" =
href=3D"mailto:davari@broadcom.com">Shahram =0A  Davari</a> </div>=0A  <div=
 style=3D"FONT:9pt;"><b>To:</b> <a rel=3D"nofollow" title=3D"ticctoc@ietf.o=
rg" ymailto=3D"mailto:ticctoc@ietf.org" target=3D"_blank" href=3D"mailto:ti=
cctoc@ietf.org">ticctoc@ietf.org</a> ; <a rel=3D"nofollow" title=3D"mpls@ie=
tf.org" ymailto=3D"mailto:mpls@ietf.org" target=3D"_blank" href=3D"mailto:m=
pls@ietf.org">mpls@ietf.org</a> ; <a rel=3D"nofollow" title=3D"mpls-tp@ietf=
.org" ymailto=3D"mailto:mpls-tp@ietf.org" target=3D"_blank" href=3D"mailto:=
mpls-tp@ietf.org">mpls-tp@ietf.org</a> ; <a rel=3D"nofollow" title=3D"pwe3@=
ietf.org" ymailto=3D"mailto:pwe3@ietf.org" target=3D"_blank" href=3D"mailto=
:pwe3@ietf.org">pwe3@ietf.org</a> </div>=0A  <div style=3D"FONT:9pt;"><b>Se=
nt:</b> Thursday, July 08, 2010 3:12 AM</div>=0A  <div style=3D"FONT:9pt;">=
<b>Subject:</b> [PWE3] 1588 over MPLS draft</div>=0A  <div><br></div>=0A  <=
div class=3D"Section1">=0A  <p class=3D"MsoNormal">Hi All,</p> =0A  <p clas=
s=3D"MsoNormal"> &nbsp;</p> =0A  <p class=3D"MsoNormal">Please find attache=
d our first draft of 1588 over MPLS. =0A  Since we have some technical issu=
es converting the Word format to Txt we =0A  couldn=E2=80=99t &nbsp;upload =
the draft before the cut-off date. However we will =0A  present the draft i=
n the next IETF meeting and will upload the draft after the =0A  meeting.</=
p> =0A  <p class=3D"MsoNormal"> &nbsp;</p> =0A  <p class=3D"MsoNormal">Note=
 that the main WG is TicToc but may require =0A  consultation with MPLS and=
 PWE3 WGs.</p> =0A  <p class=3D"MsoNormal"> &nbsp;</p> =0A  <p class=3D"Mso=
Normal">Thanks,</p> =0A  <p class=3D"MsoNormal">Shahram Davari</p></div> =
=0A  <p>=0A  </p><hr>=0A=0A  <p></p>_______________________________________=
________<br>pwe3 mailing =0A  list<br><a rel=3D"nofollow" ymailto=3D"mailto=
:pwe3@ietf.org" target=3D"_blank" href=3D"mailto:pwe3@ietf.org">pwe3@ietf.o=
rg</a><br><a rel=3D"nofollow" target=3D"_blank" href=3D"https://www.ietf.or=
g/mailman/listinfo/pwe3">https://www.ietf.org/mailman/listinfo/pwe3</a><br>=
</blockquote>=0A</div></div><div style=3D"position:fixed"></div>=0A=0A=0A</=
div><br></body></html>
--0-478951688-1279089092=:47481--


From mach@huawei.com  Wed Jul 14 01:53:58 2010
Return-Path: <mach@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F22E3A698D; Wed, 14 Jul 2010 01:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.169
X-Spam-Level: 
X-Spam-Status: No, score=-0.169 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1, STOX_REPLY_TYPE=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 pS9mn3euIKn7; Wed, 14 Jul 2010 01:53:57 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 0CF893A68A4; Wed, 14 Jul 2010 01:53:57 -0700 (PDT)
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 <0L5J004EEI0OA7@szxga03-in.huawei.com>; Wed, 14 Jul 2010 16:53:13 +0800 (CST)
Received: from m55527c ([10.110.98.169]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5J00GX7I0OE8@szxga03-in.huawei.com>; Wed, 14 Jul 2010 16:53:12 +0800 (CST)
Date: Wed, 14 Jul 2010 16:53:11 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <89571.47481.qm@web88402.mail.re1.yahoo.com>
To: "S. Davari" <davarish@yahoo.com>, Jia HE <hejia@huawei.com>, Shahram Davari <davari@broadcom.com>
Message-id: <F8A42E669722437AB6CD24CFD4586300@m55527c>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206
X-Mailer: Microsoft Windows Live Mail 14.0.8064.206
Content-type: text/plain; format=flowed; charset=utf-8; reply-type=original
Content-transfer-encoding: 8BIT
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com>
Cc: mpls@ietf.org, pwe3@ietf.org, ticctoc@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 08:53:58 -0000

Hi Shahram,

>From the view of implementation, there is no more difference between SHOULD 
and MUST :-)
For me, the Label Range is more like a mechanim to notify related nodes that 
some LSPs are dedicated for PTP messages other than the chips memory 
limitation, because the memory restriction is always there whatever you use 
Label Range or not.
IMHO, since the objective is to tell related MPLS nodes which LSPs are PTP 
LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and seems 
more common. And it will avoid the strict requirement of "the network and 
all nodes required to support the Label range".
In addition, there should be some mechanims(e.g., ISIS/OSPF extensions) for 
nodes to advertise their PTP capability hence to help PTP LSPs computation.

Best regards,
Mach


--------------------------------------------------
From: "S. Davari" <davarish@yahoo.com>
Sent: Wednesday, July 14, 2010 2:31 PM
To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" <davari@broadcom.com>
Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft

> Hi Jia,
>
> Label range is a SHOULD requirements and not MUST. The reason for Label 
> Range is
> mainly for PHY chips that don't have large memory and can't store a lot of
> Labels. Otherwise the PTP LSP is setup via signaling that specifies the 
> LSP as
> carrying 1588.
>
> So the answer is that if a Label range is used it must be a Global range 
> within
> a network and should not be used by any router for other applications.
>
> Thanks,
> Shahram
>
>
>
> ________________________________
> From: Jia HE <hejia@huawei.com>
> To: Shahram Davari <davari@broadcom.com>
> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> Sent: Tue, July 13, 2010 9:50:37 PM
> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>
>
> Hi Shahram,
>
> One question about "PTP Label Range":
>
> To my knowledge, label in MPLS network is a local  matter. For example, we 
> may
> have per-interface or per-platform label space. Will  this specificed "PTP 
> Label
> Range" conflict with the current in-use labels  for common LSPs?
>
>
> B.R.
> Jia
>
> ----- Original Message ----- 
>>From: Shahram    Davari
>>To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org
>>Sent: Thursday, July 08, 2010 3:12 AM
>>Subject: [PWE3] 1588 over MPLS draft
>>
>>
>>Hi All,
>>
>>Please find attached our first draft of 1588 over MPLS.    Since we have 
>>some
>>technical issues converting the Word format to Txt we    couldnâ€™t  upload 
>>the
>>draft before the cut-off date. However we will    present the draft in the 
>>next
>>IETF meeting and will upload the draft after the    meeting.
>>
>>Note that the main WG is TicToc but may require    consultation with MPLS 
>>and
>>PWE3 WGs.
>>
>>Thanks,
>>Shahram Davari
> ________________________________
> _______________________________________________
>>pwe3 mailing    list
>>pwe3@ietf.org
>>https://www.ietf.org/mailman/listinfo/pwe3
>>
>
>



> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 

From stbryant@cisco.com  Wed Jul 14 04:23:46 2010
Return-Path: <stbryant@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B64773A6842; Wed, 14 Jul 2010 04:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.511
X-Spam-Level: 
X-Spam-Status: No, score=-10.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, 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 vvNvRHXdA4UK; Wed, 14 Jul 2010 04:23:46 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id A54B93A67C3; Wed, 14 Jul 2010 04:23:45 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAKc7PUxAZnwN/2dsb2JhbACDHpxKcaRrggILAYchkSeBKYMJcgSIUA
X-IronPort-AV: E=Sophos;i="4.55,201,1278288000"; d="scan'208";a="132252547"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 14 Jul 2010 11:23:55 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o6EBNrb4006638; Wed, 14 Jul 2010 11:23:54 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-25.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o6EBNp620354; Wed, 14 Jul 2010 12:23:52 +0100 (BST)
Message-ID: <4C3D9E47.6000002@cisco.com>
Date: Wed, 14 Jul 2010 12:23:51 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.4) Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1
MIME-Version: 1.0
To: Mach Chen <mach@huawei.com>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com>	<04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com>	<89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c>
In-Reply-To: <F8A42E669722437AB6CD24CFD4586300@m55527c>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, ticctoc@ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3]   1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 11:23:46 -0000

  On 14/07/2010 09:53, Mach Chen wrote:
> Hi Shahram,
>
> For me, the Label Range is more like a mechanim to notify related 
> nodes that some LSPs are dedicated for PTP messages
Yes
> IMHO, since the objective is to tell related MPLS nodes which LSPs are 
> PTP LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough 
> and seems more common. And it will avoid the strict requirement of 
> "the network and all nodes required to support the Label range".
> In addition, there should be some mechanims(e.g., ISIS/OSPF 
> extensions) for nodes to advertise their PTP capability hence to help 
> PTP LSPs computation.
>
Yes.

I would anticipate that the path would be set up using RSVP-TE since 
this is a better match to the needs of a timing path. However you could 
do it with a separate instance of the IGP and then use LDP, so we should 
not exclude that case.

Stewart



From kam.lam@alcatel-lucent.com  Wed Jul 14 07:04:36 2010
Return-Path: <kam.lam@alcatel-lucent.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0B4B3A6AAB; Wed, 14 Jul 2010 07:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 FrQ4GxhZ1F28; Wed, 14 Jul 2010 07:04:22 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 426EA3A6908; Wed, 14 Jul 2010 07:04:22 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id o6EE4V3P011619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Jul 2010 09:04:31 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o6EE4UvV018580; Wed, 14 Jul 2010 09:04:30 -0500
Received: from USNAVSXCHMBSA2.ndc.alcatel-lucent.com ([135.3.39.126]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Wed, 14 Jul 2010 09:04:30 -0500
From: "Lam, Hing-Kam (Kam)" <kam.lam@alcatel-lucent.com>
To: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>
Date: Wed, 14 Jul 2010 09:04:27 -0500
Thread-Topic: [mpls] poll on draft-frost-mpls-tp-loss-delay-02.txt
Thread-Index: AcsYOEkMIl3n0p8OQRS+s+w7eD3h6gLJI8tQ
Message-ID: <7F76AEFB05C38145BABA0D545E3CFFD5437D1E6E@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
References: <4C2B111A.3000407@pi.nu>
In-Reply-To: <4C2B111A.3000407@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F76AEFB05C38145BABA0D545E3CFFD5437D1E6EUSNAVSXCHMBSA2n_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: Re: [mpls] poll on draft-frost-mpls-tp-loss-delay-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 14:04:36 -0000

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

Hi,

The following comments on draft-frost-mpls-tp-loss-delay-02 need to be addr=
essed

1) Section 3.1 second last paragraph (and section 4.1.4 second paragraph) a=
nd section 3.2 second last paragraph (and section 4.2.3 second paragraph):
Why move fields in the packet when generating the response. A node could ea=
sily understand where to write timestamps/packet counters based on the ACH =
channel type and the Q/R bit. More specifically:
-        On the LM procedure, justification/clarification is missing on the=
 why node B has to move the values of A_TxP and B_RxP from counter fields 1=
 and 2 to 3 and 4. We see no reason for doing the moving and suggest let co=
unter fields 1, 2, and 3 dedicated for A_TxP, B_RxP, and B_TxP respectively=
.
-        On the DM procedure, justification/clarification is missing on the=
 why node B has to move the values of T1 and T2 from Timestamp fields 1 and=
 2 to 3 and 4. We see no reason for doing the moving and suggest let Timest=
amp fields 1, 2, and 3 dedicated for T1, T2, and T3 respectively.

2) Section 3.1, sequence number should be removed. In MPLS-TP (where ECMP i=
s not used), packet misorderings are very rare events.

3) Post-processing of DM and LM
The post-processing of DM and LM is quite application specific and therefor=
e the reference to RFC 3393 should be removed. Transport networks will not =
rely on RFC 3393 for PDV calculation.

4) Control (error) code
In case an errored Query message is received, the generation of a Response =
message with an error code must be optional. Also the processing of a Respo=
nse message with an error code (including also the automatic suspension of =
the LM/DM operation) should be optional.

5) Section 4.1.7 LM packet loss
The considerations in section 4.1.7 about loss of LM packets are not 100% a=
ccurate. As long as the counters do not wrap past the last saved count, los=
t LM packets do not cause any issue. The loss is simply calculated over the=
 longer interval.

6) Section 4.1.7 LM packet misorder
The document should mention that in MPLS-TP (where ECMP is not used), packe=
t misorderings are very rare events.

7) Section 4.2.5 Timestamp format negotiation
The timestamp negotiation procedure in section 4.2.5 is a configuration iss=
ue and must not be piggybacked to the OAM packet. Piggybacking the negotiat=
ion procedure in the OAM packet creates the unnecessary burden at the queri=
er and responder to process these fields in every message exchange.

8) Section 1.1.2 Requirements for DM:
Not clear to what type(s) of LSP the last phrase of section 1.1.2 ("but onl=
y to enable the quantification of the one-way delay") refers to, point-to-p=
oint associated bidirectional LSPs, point-to-point unidirectional LSPs, poi=
nt-to-multipoint (unidirectional) LSPs, or all?

9) Section 1.2 Protocol Summary
The sentence "The LM protocol provides perfect loss measurement if the nece=
ssary implementation support is available" needs clarification or justifica=
tion.
The sentence "The LM and DM protocols are designed to be simple and to supp=
ort efficient hardware processing" is judgmental and not a summary of the p=
rotocol.

10) LM and DM frame format:
Clarification is needed on why need the fourth LM counter (A_RxP) and the f=
ourth DM timestamp (T4) of DM in the protocol messages given that they are =
not exchanged/shared between the nodes. If the reason is to simplify hardwa=
re implementations at the receiver equipment in node A, please explicitly c=
larify so.

11) Section 2.1 the last sentence
Suggest change the last sentence from "This alternative approach to LM is f=
or further study and will be described in a companion document" to "Such al=
ternative approach to LM is outside the scope of this document".

12) Section 2.2 the fourth paragraph
Define and explain the "response code" in the phrase "At this point, B inse=
rts an appropriate response code into the message ...."

13) Section 2.3 the sixth paragraph
Define and explain the "response code" in the phrase "B inserts an appropri=
ate response code ..."

14) Section 3.2 last paragraph Padding:
Need to give the rationale for the option of not copying padding to the Del=
ay Measurement response.
Need to add text to note that in case where no padding in the Delay Measure=
ment response, the Message Length field needs to match with the length of t=
he response message.

15) Section 5.1 second paragraph
Why the support of per-traffic-class basis LM is SHOULD and not a MUST?
Also, LM frames MUST have the same traffic class as the service they measur=
e else misordering is invited. This consideration makes the option of  LM c=
onducted over multiple classes unattractive.



Regards,

Kam







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

> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of

> Loa Andersson

> Sent: Wednesday, June 30, 2010 5:41 AM

> To: mpls@ietf.org; mpls-tp@ietf.org; MPLS-TP ad hoc team

> Subject: [mpls] poll on draft-frost-mpls-tp-loss-delay-02.txt

>

> Working Group,

>

> this email is to start a poll to adopt

> draft-frost-mpls-tp-loss-delay-02.txt

> as an MPLS working group draft.

>

> After recent experience, the chairs would like to remind you all

> what it means to conduct a poll to adopt a draft as a working group

> draft.

>

> - Please recall that the IETF does not "vote." Polls of a working

>    group are to gather information to help the chairs make their

>    decisions. Voting is not part of the normal working methods of

>    an IETF working group.

>

> - The "rough consensus" process used in the working group assumes

>    that people expressing opinions are also participating in the

>    development of standards documents.

>

> - Subscription to the list specifically to express an opinion is

>    noticed by the chairs who has access to information on the new list

>    members. Such behavior is not part of the normal working methods.

>

> - The purpose of a poll for adoption is to help the chairs understand

>    the level of support for a document (i.e. who has read it, who

>    believes it is a good starting point for working group work, who

>    will contribute to the work) and whether there are any significant

>    technical issues. Statements of objection must be backed up by

>    proper technical reasons.

>

> So please respond to this poll indicating whether you support the

> adoption of this draft or stating your technical issues.

>

> This poll ends eob July 15.

>

>

> Loa and George

> mpls wg co-chairs

>

> --

>

>

> Loa Andersson                         email: loa.andersson@ericsson.com

> Sr Strategy and Standards Manager            loa@pi.nu

> Ericsson Inc                          phone: +46 10 717 52 13

>                                               +46 767 72 92 13

> _______________________________________________

> mpls mailing list

> mpls@ietf.org

> https://www.ietf.org/mailman/listinfo/mpls

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 77.95pt 1.0in 77.95pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:41640896;
	mso-list-type:hybrid;
	mso-list-template-ids:116425430 -1169532656 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F02D;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoPlainText><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>Hi,<o:p></o:p></sp=
an></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>The following comments on draft-frost-mpls-tp-loss-delay-02 need to=
 be
addressed<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>1) Section 3.1 second last paragraph (and section 4.1.4 second
paragraph) and section 3.2 second last paragraph (and section 4.2.3 second
paragraph): <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>Why move fields in the packet when generating the response. A node
could easily understand where to write timestamps/packet counters based on =
the
ACH channel type and the Q/R bit. More specifically:<o:p></o:p></span></fon=
t></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in;mso-list:=
l0 level1 lfo1'><![if !supportLists]><font
size=3D3 face=3DSymbol><span style=3D'font-size:12.0pt;font-family:Symbol'>=
<span
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></font></span></span></font><![endif]>On the LM procedure,
justification/clarification is missing on the why node B has to move the va=
lues
of A_TxP and B_RxP from counter fields 1 and 2 to 3 and 4. We see no reason=
 for
doing the moving and suggest let counter fields 1, 2, and 3 dedicated for
A_TxP, B_RxP, and B_TxP respectively. <o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in;mso-list:=
l0 level1 lfo1'><![if !supportLists]><font
size=3D3 face=3DSymbol><span style=3D'font-size:12.0pt;font-family:Symbol'>=
<span
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></font></span></span></font><![endif]>On the DM procedure,
justification/clarification is missing on the why node B has to move the va=
lues
of T1 and T2 from Timestamp fields 1 and 2 to 3 and 4. We see no reason for
doing the moving and suggest let Timestamp fields 1, 2, and 3 dedicated for=
 T1,
T2, and T3 respectively. <o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 face=3D"Time=
s New Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>2) Section 3.1, sequence number should be removed. In MPLS-TP (wher=
e
ECMP is not used), packet misorderings are very rare events.<o:p></o:p></sp=
an></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>3) Post-processing of DM and LM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>The post-processing of DM and LM is quite application specific and =
therefore
the reference to RFC 3393 should be removed. Transport networks will not re=
ly
on RFC 3393 for PDV calculation. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>4) Control (error) code<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>In case an errored Query message is received, the generation of a
Response message with an error code must be optional. Also the processing o=
f a
Response message with an error code (including also the automatic suspensio=
n of
the LM/DM operation) should be optional. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>5) Section 4.1.7 LM packet loss<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>The considerations in section 4.1.7 about loss of LM packets are no=
t
100% accurate. As long as the counters do not wrap past the last saved coun=
t, lost
LM packets do not cause any issue. The loss is simply calculated over the
longer interval.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>6) Section 4.1.7 LM packet misorder<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>The document should mention that in MPLS-TP (where ECMP is not used=
),
packet misorderings are very rare events. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>7) Section 4.2.5 Timestamp format negotiation<o:p></o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>The timestamp negotiation procedure in section 4.2.5 is a configura=
tion
issue and must not be piggybacked to the OAM packet. Piggybacking the
negotiation procedure in the OAM packet creates the unnecessary burden at t=
he
querier and responder to process these fields in every message exchange. <o=
:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>8) Section 1.1.2 Requirements for DM: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>Not clear to what type(s) of LSP the last phrase of section 1.1.2
(&#8220;but only to enable the quantification of the one-way delay&#8221;) =
refers
to, point-to-point associated bidirectional LSPs, point-to-point unidirecti=
onal
LSPs, point-to-multipoint (unidirectional) LSPs, or all?<o:p></o:p></span><=
/font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>9) Section 1.2 Protocol Summary <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>The sentence &#8220;The LM protocol provides perfect loss measureme=
nt
if the necessary implementation support is available&#8221; needs clarifica=
tion
or justification.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>The sentence &#8220;The LM and DM protocols are designed to be simp=
le
and to support efficient hardware processing&#8221; is judgmental and not a
summary of the protocol.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>10) LM and DM frame format: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>Clarification is needed on why need the fourth LM counter (A_RxP) a=
nd
the fourth DM timestamp (T4) of DM in the protocol messages given that they=
 are
not exchanged/shared between the nodes. If the reason is to simplify hardwa=
re
implementations at the receiver equipment in node A, please explicitly clar=
ify
so.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p><=
/span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>11) Section 2.1 the last sentence<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>Suggest change the last sentence from &#8220;<i><span style=3D'font=
-style:
italic'>This alternative approach to LM is for further study and will be
described in a companion document</span></i>&#8221; to &#8220;<i><span
style=3D'font-style:italic'>Such alternative approach to LM is outside the =
scope
of this document</span></i>&#8221;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>12) Section 2.2 the fourth paragraph<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>Define and explain the &#8220;response code&#8221; in the phrase
&#8220;At this point, B inserts an appropriate response code into the messa=
ge
&#8230;.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>13) Section 2.3 the sixth paragraph<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>Define and explain the &#8220;response code&#8221; in the phrase
&#8220;B inserts an appropriate response code &#8230;&#8221;<o:p></o:p></sp=
an></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>14) Section 3.2 last paragraph Padding:<o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>Need to give the rationale for the option of not copying padding to=
 the
Delay Measurement response.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>Need to add text to note that in case where no padding in the Delay
Measurement response, the Message Length field needs to match with the leng=
th
of the response message.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>15) Section 5.1 second paragraph<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>Why the support of per-traffic-class basis LM is SHOULD and not a M=
UST?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>Also, LM frames MUST have the same traffic class as the service the=
y
measure else misordering is invited. This consideration makes the option
of&nbsp; LM conducted over multiple classes unattractive.<o:p></o:p></span>=
</font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Kam<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; -----Original Message-----</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
Behalf Of</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; Loa Andersson</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; Sent: Wednesday, June 30, 2010 5:41 AM</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; To: <st1:PersonName w:st=3D"on">mpls@ietf.org</st1:PersonName>=
; <st1:PersonName
w:st=3D"on">mpls-tp@ietf.org</st1:PersonName>; <st1:PersonName w:st=3D"on">=
MPLS-TP
 ad hoc team</st1:PersonName></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; Subject: [mpls] poll on draft-frost-mpls-tp-loss-delay-02.txt<=
/span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; Working Group,</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; this email is to start a poll to adopt</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; draft-frost-mpls-tp-loss-delay-02.txt</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; as an MPLS working group draft.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; After recent experience, the chairs would like to remind you a=
ll</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; what it means to conduct a poll to adopt a draft as a working
group</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; draft.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; - Please recall that the IETF does not &quot;vote.&quot; Polls=
 of
a working</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;group are to gather information to help the
chairs make their</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;decisions. Voting is not part of the normal
working methods of</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;an IETF working group.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; - The &quot;rough consensus&quot; process used in the working
group assumes</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;that people expressing opinions are also
participating in the</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;development of standards documents.</span></=
font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; - Subscription to the list specifically to express an opinion =
is</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;noticed by the chairs who has access to
information on the new list</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;members. Such behavior is not part of the no=
rmal
working methods.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; - The purpose of a poll for adoption is to help the chairs
understand</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;the level of support for a document (i.e. wh=
o
has read it, who</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;believes it is a good starting point for wor=
king
group work, who</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;will contribute to the work) and whether the=
re
are any significant</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;technical issues. Statements of objection mu=
st
be backed up by</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;proper technical reasons.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; So please respond to this poll indicating whether you support =
the</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; adoption of this draft or stating your technical issues.</span=
></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; This poll ends eob July 15.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; Loa and George</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; mpls wg co-chairs</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; --</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; Loa
Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
email: <st1:PersonName w:st=3D"on">loa.andersson@ericsson.com</st1:PersonNa=
me></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; Sr Strategy and Standards
Manager&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
loa@pi.nu</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; Ericsson
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
phone: +46 10 717 52 13</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+46
767 72 92 13</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; _______________________________________________</span></font><=
/p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; mpls mailing list</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; <st1:PersonName w:st=3D"on">mpls@ietf.org</st1:PersonName></sp=
an></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&gt; https://www.ietf.org/mailman/listinfo/mpls</span></font></p>

</div>

</body>

</html>

--_000_7F76AEFB05C38145BABA0D545E3CFFD5437D1E6EUSNAVSXCHMBSA2n_--

From stbryant@cisco.com  Wed Jul 14 08:51:44 2010
Return-Path: <stbryant@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E4F23A6968; Wed, 14 Jul 2010 08:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.519
X-Spam-Level: 
X-Spam-Status: No, score=-10.519 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 vHhooHlL6H7H; Wed, 14 Jul 2010 08:51:35 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id DE4EF3A6852; Wed, 14 Jul 2010 08:51:34 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAP95PUxAZnwM/2dsb2JhbACBRJ4ncaYJggILAZg/AoUiBIhQ
X-IronPort-AV: E=Sophos;i="4.55,202,1278288000";  d="scan'208,217";a="132338892"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 14 Jul 2010 15:51:44 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o6EFphuk018263; Wed, 14 Jul 2010 15:51:43 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-25.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o6EFpe610701; Wed, 14 Jul 2010 16:51:41 +0100 (BST)
Message-ID: <4C3DDD0C.9050907@cisco.com>
Date: Wed, 14 Jul 2010 16:51:40 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.4) Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1
MIME-Version: 1.0
To: "Lam, Hing-Kam (Kam)" <kam.lam@alcatel-lucent.com>
References: <4C2B111A.3000407@pi.nu> <7F76AEFB05C38145BABA0D545E3CFFD5437D1E6E@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
In-Reply-To: <7F76AEFB05C38145BABA0D545E3CFFD5437D1E6E@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------080406050800050208020004"
Cc: "mpls@ietf.org" <mpls@ietf.org>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [mpls-tp] poll on draft-frost-mpls-tp-loss-delay-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 15:51:44 -0000

This is a multi-part message in MIME format.
--------------080406050800050208020004
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

  Kam

To pick up on a recurrent theme here, the concept is that the low level 
h/w can stamp the packet by simply (only) recognizing the ACH. It does 
not need to understand whether the msg is a request or a response, all 
that happens at another layer in the processing. So the packet format is 
marginally more complex at the higher layer, but as simple as possible 
at the lower layer.

Stewart



On 14/07/2010 15:04, Lam, Hing-Kam (Kam) wrote:
>
> Hi,
>
> The following comments on draft-frost-mpls-tp-loss-delay-02 need to be 
> addressed
>
> 1) Section 3.1 second last paragraph (and section 4.1.4 second 
> paragraph) and section 3.2 second last paragraph (and section 4.2.3 
> second paragraph):
>
> Why move fields in the packet when generating the response. A node 
> could easily understand where to write timestamps/packet counters 
> based on the ACH channel type and the Q/R bit. More specifically:
>
> - On the LM procedure, justification/clarification is missing on the 
> why node B has to move the values of A_TxP and B_RxP from counter 
> fields 1 and 2 to 3 and 4. We see no reason for doing the moving and 
> suggest let counter fields 1, 2, and 3 dedicated for A_TxP, B_RxP, and 
> B_TxP respectively.
>
> - On the DM procedure, justification/clarification is missing on the 
> why node B has to move the values of T1 and T2 from Timestamp fields 1 
> and 2 to 3 and 4. We see no reason for doing the moving and suggest 
> let Timestamp fields 1, 2, and 3 dedicated for T1, T2, and T3 
> respectively.
>
> 2) Section 3.1, sequence number should be removed. In MPLS-TP (where 
> ECMP is not used), packet misorderings are very rare events.
>
> 3) Post-processing of DM and LM
>
> The post-processing of DM and LM is quite application specific and 
> therefore the reference to RFC 3393 should be removed. Transport 
> networks will not rely on RFC 3393 for PDV calculation.
>
> 4) Control (error) code
>
> In case an errored Query message is received, the generation of a 
> Response message with an error code must be optional. Also the 
> processing of a Response message with an error code (including also 
> the automatic suspension of the LM/DM operation) should be optional.
>
> 5) Section 4.1.7 LM packet loss
>
> The considerations in section 4.1.7 about loss of LM packets are not 
> 100% accurate. As long as the counters do not wrap past the last saved 
> count, lost LM packets do not cause any issue. The loss is simply 
> calculated over the longer interval.
>
> 6) Section 4.1.7 LM packet misorder
>
> The document should mention that in MPLS-TP (where ECMP is not used), 
> packet misorderings are very rare events.
>
> 7) Section 4.2.5 Timestamp format negotiation
>
> The timestamp negotiation procedure in section 4.2.5 is a 
> configuration issue and must not be piggybacked to the OAM packet. 
> Piggybacking the negotiation procedure in the OAM packet creates the 
> unnecessary burden at the querier and responder to process these 
> fields in every message exchange.
>
> 8) Section 1.1.2 Requirements for DM:
>
> Not clear to what type(s) of LSP the last phrase of section 1.1.2 
> ("but only to enable the quantification of the one-way delay") refers 
> to, point-to-point associated bidirectional LSPs, point-to-point 
> unidirectional LSPs, point-to-multipoint (unidirectional) LSPs, or all?
>
> 9) Section 1.2 Protocol Summary
>
> The sentence "The LM protocol provides perfect loss measurement if the 
> necessary implementation support is available" needs clarification or 
> justification.
>
> The sentence "The LM and DM protocols are designed to be simple and to 
> support efficient hardware processing" is judgmental and not a summary 
> of the protocol.
>
> 10) LM and DM frame format:
>
> Clarification is needed on why need the fourth LM counter (A_RxP) and 
> the fourth DM timestamp (T4) of DM in the protocol messages given that 
> they are not exchanged/shared between the nodes. If the reason is to 
> simplify hardware implementations at the receiver equipment in node A, 
> please explicitly clarify so.
>
> 11) Section 2.1 the last sentence
>
> Suggest change the last sentence from "/This alternative approach to 
> LM is for further study and will be described in a companion 
> document/" to "/Such alternative approach to LM is outside the scope 
> of this document/".
>
> 12) Section 2.2 the fourth paragraph
>
> Define and explain the "response code" in the phrase "At this point, B 
> inserts an appropriate response code into the message ...."
>
> 13) Section 2.3 the sixth paragraph
>
> Define and explain the "response code" in the phrase "B inserts an 
> appropriate response code ..."
>
> 14) Section 3.2 last paragraph Padding:
>
> Need to give the rationale for the option of not copying padding to 
> the Delay Measurement response.
>
> Need to add text to note that in case where no padding in the Delay 
> Measurement response, the Message Length field needs to match with the 
> length of the response message.
>
> 15) Section 5.1 second paragraph
>
> Why the support of per-traffic-class basis LM is SHOULD and not a MUST?
>
> Also, LM frames MUST have the same traffic class as the service they 
> measure else misordering is invited. This consideration makes the 
> option of  LM conducted over multiple classes unattractive.
>
> Regards,
>
> Kam
>
> > -----Original Message-----
>
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
>
> > Loa Andersson
>
> > Sent: Wednesday, June 30, 2010 5:41 AM
>
> > To: mpls@ietf.org; mpls-tp@ietf.org; MPLS-TP ad hoc team
>
> > Subject: [mpls] poll on draft-frost-mpls-tp-loss-delay-02.txt
>
> >
>
> > Working Group,
>
> >
>
> > this email is to start a poll to adopt
>
> > draft-frost-mpls-tp-loss-delay-02.txt
>
> > as an MPLS working group draft.
>
> >
>
> > After recent experience, the chairs would like to remind you all
>
> > what it means to conduct a poll to adopt a draft as a working group
>
> > draft.
>
> >
>
> > - Please recall that the IETF does not "vote." Polls of a working
>
> >    group are to gather information to help the chairs make their
>
> >    decisions. Voting is not part of the normal working methods of
>
> >    an IETF working group.
>
> >
>
> > - The "rough consensus" process used in the working group assumes
>
> >    that people expressing opinions are also participating in the
>
> >    development of standards documents.
>
> >
>
> > - Subscription to the list specifically to express an opinion is
>
> >    noticed by the chairs who has access to information on the new list
>
> >    members. Such behavior is not part of the normal working methods.
>
> >
>
> > - The purpose of a poll for adoption is to help the chairs understand
>
> >    the level of support for a document (i.e. who has read it, who
>
> >    believes it is a good starting point for working group work, who
>
> >    will contribute to the work) and whether there are any significant
>
> >    technical issues. Statements of objection must be backed up by
>
> >    proper technical reasons.
>
> >
>
> > So please respond to this poll indicating whether you support the
>
> > adoption of this draft or stating your technical issues.
>
> >
>
> > This poll ends eob July 15.
>
> >
>
> >
>
> > Loa and George
>
> > mpls wg co-chairs
>
> >
>
> > --
>
> >
>
> >
>
> > Loa Andersson                         email: loa.andersson@ericsson.com
>
> > Sr Strategy and Standards Manager            loa@pi.nu
>
> > Ericsson Inc                          phone: +46 10 717 52 13
>
> >                                               +46 767 72 92 13
>
> > _______________________________________________
>
> > mpls mailing list
>
> > mpls@ietf.org
>
> > https://www.ietf.org/mailman/listinfo/mpls
>
>
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



--------------080406050800050208020004
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Kam<br>
    <br>
    To pick up on a recurrent theme here, the concept is that the low
    level h/w can stamp the packet by simply (only) recognizing the ACH.
    It does not need to understand whether the msg is a request or a
    response, all that happens at another layer in the processing. So
    the packet format is marginally more complex at the higher layer,
    but as simple as possible at the lower layer.<br>
    <br>
    Stewart<br>
    <br>
    <br>
    <br>
    On 14/07/2010 15:04, Lam, Hing-Kam (Kam) wrote:
    <blockquote
cite="mid:7F76AEFB05C38145BABA0D545E3CFFD5437D1E6E@USNAVSXCHMBSA2.ndc.alcatel-lucent.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 11 (filtered
        medium)">
      <o:smarttagtype
        namespaceuri="urn:schemas-microsoft-com:office:smarttags"
        name="PersonName">
        <!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
        <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 77.95pt 1.0in 77.95pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:41640896;
	mso-list-type:hybrid;
	mso-list-template-ids:116425430 -1169532656 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F02D;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</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]-->
        <div class="Section1">
          <p class="MsoPlainText"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt; font-family: &quot;Times New
                Roman&quot;;">Hi,<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">The following comments on
                draft-frost-mpls-tp-loss-delay-02 need to be
                addressed<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">1) Section 3.1 second last
                paragraph (and section 4.1.4 second
                paragraph) and section 3.2 second last paragraph (and
                section 4.2.3 second
                paragraph): <o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">Why move fields in the packet
                when generating the response. A node
                could easily understand where to write timestamps/packet
                counters based on the
                ACH channel type and the Q/R bit. More specifically:<o:p></o:p></span></font></p>
          <p class="MsoNormal" style="margin-left: 0.5in; text-indent:
            -0.25in;"><!--[if !supportLists]--><font face="Symbol"
              size="3"><span style="font-size: 12pt; font-family:
                Symbol;"><span style="">-<font face="Times New Roman"
                    size="1"><span style="font: 7pt &quot;Times New
                      Roman&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                    </span></font></span></span></font><!--[endif]-->On
            the LM procedure,
            justification/clarification is missing on the why node B has
            to move the values
            of A_TxP and B_RxP from counter fields 1 and 2 to 3 and 4.
            We see no reason for
            doing the moving and suggest let counter fields 1, 2, and 3
            dedicated for
            A_TxP, B_RxP, and B_TxP respectively. <o:p></o:p></p>
          <p class="MsoNormal" style="margin-left: 0.5in; text-indent:
            -0.25in;"><!--[if !supportLists]--><font face="Symbol"
              size="3"><span style="font-size: 12pt; font-family:
                Symbol;"><span style="">-<font face="Times New Roman"
                    size="1"><span style="font: 7pt &quot;Times New
                      Roman&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                    </span></font></span></span></font><!--[endif]-->On
            the DM procedure,
            justification/clarification is missing on the why node B has
            to move the values
            of T1 and T2 from Timestamp fields 1 and 2 to 3 and 4. We
            see no reason for
            doing the moving and suggest let Timestamp fields 1, 2, and
            3 dedicated for T1,
            T2, and T3 respectively. <o:p></o:p></p>
          <p class="MsoNormal" style="margin-left: 0.5in;"><font
              face="Times New Roman" size="3"><span style="font-size:
                12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">2) Section 3.1, sequence number
                should be removed. In MPLS-TP (where
                ECMP is not used), packet misorderings are very rare
                events.<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">3) Post-processing of DM and LM<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">The post-processing of DM and
                LM is quite application specific and therefore
                the reference to RFC 3393 should be removed. Transport
                networks will not rely
                on RFC 3393 for PDV calculation. <o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">4) Control (error) code<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">In case an errored Query
                message is received, the generation of a
                Response message with an error code must be optional.
                Also the processing of a
                Response message with an error code (including also the
                automatic suspension of
                the LM/DM operation) should be optional. <o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">5) Section 4.1.7 LM packet loss<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">The considerations in section
                4.1.7 about loss of LM packets are not
                100% accurate. As long as the counters do not wrap past
                the last saved count, lost
                LM packets do not cause any issue. The loss is simply
                calculated over the
                longer interval.<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">6) Section 4.1.7 LM packet
                misorder<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">The document should mention
                that in MPLS-TP (where ECMP is not used),
                packet misorderings are very rare events. <o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">7) Section 4.2.5 Timestamp
                format negotiation<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">The timestamp negotiation
                procedure in section 4.2.5 is a configuration
                issue and must not be piggybacked to the OAM packet.
                Piggybacking the
                negotiation procedure in the OAM packet creates the
                unnecessary burden at the
                querier and responder to process these fields in every
                message exchange. <o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">8) Section 1.1.2 Requirements
                for DM: <o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">Not clear to what type(s) of
                LSP the last phrase of section 1.1.2
                (&#8220;but only to enable the quantification of the one-way
                delay&#8221;) refers
                to, point-to-point associated bidirectional LSPs,
                point-to-point unidirectional
                LSPs, point-to-multipoint (unidirectional) LSPs, or all?<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">9) Section 1.2 Protocol Summary
                <o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">The sentence &#8220;The LM protocol
                provides perfect loss measurement
                if the necessary implementation support is available&#8221;
                needs clarification
                or justification.<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">The sentence &#8220;The LM and DM
                protocols are designed to be simple
                and to support efficient hardware processing&#8221; is
                judgmental and not a
                summary of the protocol.<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">10) LM and DM frame format: <o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">Clarification is needed on why
                need the fourth LM counter (A_RxP) and
                the fourth DM timestamp (T4) of DM in the protocol
                messages given that they are
                not exchanged/shared between the nodes. If the reason is
                to simplify hardware
                implementations at the receiver equipment in node A,
                please explicitly clarify
                so.<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">11) Section 2.1 the last
                sentence<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">Suggest change the last
                sentence from &#8220;<i><span style="font-style: italic;">This
                    alternative approach to LM is for further study and
                    will be
                    described in a companion document</span></i>&#8221; to &#8220;<i><span
                    style="font-style: italic;">Such alternative
                    approach to LM is outside the scope
                    of this document</span></i>&#8221;.<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">12) Section 2.2 the fourth
                paragraph<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">Define and explain the
                &#8220;response code&#8221; in the phrase
                &#8220;At this point, B inserts an appropriate response code
                into the message
                &#8230;.&#8221;<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">13) Section 2.3 the sixth
                paragraph<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">Define and explain the
                &#8220;response code&#8221; in the phrase
                &#8220;B inserts an appropriate response code &#8230;&#8221;<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">14) Section 3.2 last paragraph
                Padding:<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">Need to give the rationale for
                the option of not copying padding to the
                Delay Measurement response.<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">Need to add text to note that
                in case where no padding in the Delay
                Measurement response, the Message Length field needs to
                match with the length
                of the response message.<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">15) Section 5.1 second
                paragraph<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">Why the support of
                per-traffic-class basis LM is SHOULD and not a MUST?<o:p></o:p></span></font></p>
          <p class="MsoNormal"><font face="Times New Roman" size="3"><span
                style="font-size: 12pt;">Also, LM frames MUST have the
                same traffic class as the service they
                measure else misordering is invited. This consideration
                makes the option
                of&nbsp; LM conducted over multiple classes unattractive.<o:p></o:p></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">Regards,<o:p></o:p></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">Kam<o:p></o:p></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&nbsp;<o:p></o:p></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;"><o:p>&nbsp;</o:p></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; -----Original Message-----</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; From:
                <a class="moz-txt-link-abbreviated" href="mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>] On
                Behalf Of</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; Loa Andersson</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; Sent: Wednesday, June 30,
                2010 5:41 AM</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; To: <st1:personname
                  w:st="on"><a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a></st1:personname>; <st1:personname
                  w:st="on"><a class="moz-txt-link-abbreviated" href="mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a></st1:personname>; <st1:personname
                  w:st="on">MPLS-TP ad hoc team</st1:personname></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; Subject: [mpls] poll on
                draft-frost-mpls-tp-loss-delay-02.txt</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; Working Group,</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; this email is to start a
                poll to adopt</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt;
                draft-frost-mpls-tp-loss-delay-02.txt</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; as an MPLS working group
                draft.</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; After recent experience,
                the chairs would like to remind you all</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; what it means to conduct a
                poll to adopt a draft as a working
                group</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; draft.</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; - Please recall that the
                IETF does not "vote." Polls of
                a working</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;group are to gather
                information to help the
                chairs make their</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;decisions. Voting is
                not part of the normal
                working methods of</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;an IETF working group.</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; - The "rough consensus"
                process used in the working
                group assumes</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;that people expressing
                opinions are also
                participating in the</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;development of
                standards documents.</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; - Subscription to the list
                specifically to express an opinion is</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;noticed by the chairs
                who has access to
                information on the new list</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;members. Such behavior
                is not part of the normal
                working methods.</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; - The purpose of a poll
                for adoption is to help the chairs
                understand</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;the level of support
                for a document (i.e. who
                has read it, who</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;believes it is a good
                starting point for working
                group work, who</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;will contribute to the
                work) and whether there
                are any significant</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;technical issues.
                Statements of objection must
                be backed up by</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; &nbsp;&nbsp;&nbsp;proper technical
                reasons.</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; So please respond to this
                poll indicating whether you support the</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; adoption of this draft or
                stating your technical issues.</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; This poll ends eob July
                15.</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; Loa and George</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; mpls wg co-chairs</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; --</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; </span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; Loa
                Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                email: <st1:personname w:st="on"><a class="moz-txt-link-abbreviated" href="mailto:loa.andersson@ericsson.com">loa.andersson@ericsson.com</a></st1:personname></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; Sr Strategy and Standards
                Manager&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                <a class="moz-txt-link-abbreviated" href="mailto:loa@pi.nu">loa@pi.nu</a></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; Ericsson
                Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                phone: +46 10 717 52 13</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt;
                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+46
                767 72 92 13</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt;
                _______________________________________________</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; mpls mailing list</span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt; <st1:personname w:st="on"><a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a></st1:personname></span></font></p>
          <p class="MsoPlainText"><font face="Courier New" size="2"><span
                style="font-size: 10pt;">&gt;
                <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/mailman/listinfo/mpls</a></span></font></p>
        </div>
        <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
mpls-tp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mpls-tp">https://www.ietf.org/mailman/listinfo/mpls-tp</a>
</pre>
      </o:smarttagtype></blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------080406050800050208020004--

From curtis@occnc.com  Wed Jul 14 10:04:22 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FF563A67BD; Wed, 14 Jul 2010 10:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.352
X-Spam-Level: 
X-Spam-Status: No, score=-2.352 tagged_above=-999 required=5 tests=[AWL=0.247,  BAYES_00=-2.599]
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 AnFT1dMyYrl4; Wed, 14 Jul 2010 10:04:21 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 58B9F3A686D; Wed, 14 Jul 2010 10:04:21 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6EH4T2I045662; Wed, 14 Jul 2010 13:04:29 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007141704.o6EH4T2I045662@harbor.orleans.occnc.com>
To: "Shahram Davari" <davari@broadcom.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Wed, 07 Jul 2010 12:12:04 PDT." <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com>
Date: Wed, 14 Jul 2010 13:04:29 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 17:04:22 -0000

In message <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com>
"Shahram Davari" writes:
>  
>  
> Hi All,
>  
> Please find attached our first draft of 1588 over MPLS. Since we have some =
> technical issues converting the Word format to Txt we couldn't  upload the =
> draft before the cut-off date. However we will present the draft in the nex=
> t IETF meeting and will upload the draft after the meeting.
>  
> Note that the main WG is TicToc but may require consultation with MPLS and =
> PWE3 WGs.
>  
> Thanks,
> Shahram Davari


IMO Attaching a word doc and asking for a slot at the meeting is
unacceptable.  At least convert the document to text or don't bother
and submit the draft after the meeting.  In any case, the cutoffs are
there for a reason and this should be given low priority at the
meeting (presented if there is time left over).

Curtis

From curtis@occnc.com  Wed Jul 14 10:07:36 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FB4E3A6B45; Wed, 14 Jul 2010 10:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 tagged_above=-999 required=5 tests=[AWL=0.237,  BAYES_00=-2.599]
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 PVX0YP3himPg; Wed, 14 Jul 2010 10:07:34 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id F195A3A6A43; Wed, 14 Jul 2010 10:07:32 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6EH7R2W045708; Wed, 14 Jul 2010 13:07:27 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007141707.o6EH7R2W045708@harbor.orleans.occnc.com>
To: Yong Lucy <lucyyong@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Sun, 11 Jul 2010 14:01:44 CDT." <005601cb212b$88c87520$6901a8c0@china.huawei.com> 
Date: Wed, 14 Jul 2010 13:07:27 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org, 'pwe3' <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] FW: New Version Notification for draft-yong-pwe3-lfc-fat-pw-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 17:07:36 -0000

In message <005601cb212b$88c87520$6901a8c0@china.huawei.com>
Yong Lucy writes:
>  
> Look forward to hearing your feedbacks on this in Maastricht. -Lucy
>  
> A new version of I-D, draft-yong-pwe3-lfc-fat-pw-01.txt has been
> successfully submitted by Lucy Yong and posted to the IETF repository.


I thought this was presented and soundly rejected at the prior meeting.

Curtis

From davari@broadcom.com  Wed Jul 14 10:58:58 2010
Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F9543A6820; Wed, 14 Jul 2010 10:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.43
X-Spam-Level: 
X-Spam-Status: No, score=-2.43 tagged_above=-999 required=5 tests=[AWL=0.169,  BAYES_00=-2.599]
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 AkX4EulKfQIA; Wed, 14 Jul 2010 10:58:57 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by core3.amsl.com (Postfix) with ESMTP id 15E0B3A689E; Wed, 14 Jul 2010 10:58:57 -0700 (PDT)
Received: from [10.16.192.224] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 14 Jul 2010 10:58:55 -0700
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Wed, 14 Jul 2010 10:58:55 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Mach Chen" <mach@huawei.com>, "S. Davari" <davarish@yahoo.com>, "Jia HE" <hejia@huawei.com>
Date: Wed, 14 Jul 2010 10:58:52 -0700
Thread-Topic: [mpls] [PWE3] 1588 over MPLS draft
Thread-Index: AcsjMgdiunhK8zDyRjCGPXWCrcIDMgASzymg
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c>
In-Reply-To: <F8A42E669722437AB6CD24CFD4586300@m55527c>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6023255410030838795-01-01
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 17:58:58 -0000

SGkgTWFjaCwNCg0KV2hlbiBhIHNlcnZpY2UgcHJvdmlkZXIgd2FudHMgdG8gY3JlYXRlIHRoZXNl
IFBUUCBMU1BzLCB3aGF0IGlzIHdyb25nIHdpdGggYWxsb2NhdGluZyBhIHJhbmdlIG9mIGxhYmVs
cyBmb3IgdGhpcyBwdXJwb3NlPyBUaGlzIGlzIHB1cmVseSBhIHNvZnR3YXJlIGV4ZXJjaXNlLiBU
aGVyZSBhcmUgMiBtaWxsaW9uIGxhYmVscyBhdmFpbGFibGUgdG8gZWFjaCBub2RlLCB3aHkgY2Fu
J3Qgc29tZSBvZiB0aGVtIGJlIGFsbG9jYXRlZCBieSBzb2Z0d2FyZSB0byBQVFA/DQoNCkluIHRo
ZW9yeSB3aGF0IHlvdSBzYXkgaXMgY29ycmVjdCBhbmQgc2hvdWxkIHdvcmssIGJ1dCBpbiBwcmFj
dGljZSB0aGVyZSBpcyBhIGZ1bmN0aW9uIGNhbGxlZCAxLXN0ZXAgVHJhbnNwYXJlbnQgY2xvY2tp
bmcgdGhhdCByZXF1aXJlcyB0aW1lIHN0YW1waW5nIGF0IHRoZSBQSFkgKGltbWVkaWF0ZWx5IHdo
ZW4gdGhlIHBhY2tldCBpcyByZWNlaXZlZCBvciB0cmFuc21pdHRlZCkuIFBIWSBjaGlwcyBkb24n
dCBoYXZlIENBTSBvciBsb3RzIG9mIG1lbW9yeSB0byBzdG9yZSBhIGZldyB0aG91c2FuZCByYW5k
b20gbGFiZWxzLiBUaGUgbGFiZWwgcmFuZ2Ugd2lsbCBzb2x2ZSB0aGF0IHByb2JsZW0gYW5kIGlz
IGNvbnNpc3RlbnQgd2l0aCBNUExTIGFyY2hpdGVjdHVyZS4NCg0KVGhhbmtzLA0KU2hhaHJhbQ0K
DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogTWFjaCBDaGVuIFttYWlsdG86bWFj
aEBodWF3ZWkuY29tXSANClNlbnQ6IFdlZG5lc2RheSwgSnVseSAxNCwgMjAxMCAxOjUzIEFNDQpU
bzogUy4gRGF2YXJpOyBKaWEgSEU7IFNoYWhyYW0gRGF2YXJpDQpDYzogbXBsc0BpZXRmLm9yZzsg
cHdlM0BpZXRmLm9yZzsgdGljY3RvY0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KU3ViamVj
dDogUmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCg0KSGkgU2hhaHJhbSwN
Cg0KRnJvbSB0aGUgdmlldyBvZiBpbXBsZW1lbnRhdGlvbiwgdGhlcmUgaXMgbm8gbW9yZSBkaWZm
ZXJlbmNlIGJldHdlZW4gU0hPVUxEIA0KYW5kIE1VU1QgOi0pDQpGb3IgbWUsIHRoZSBMYWJlbCBS
YW5nZSBpcyBtb3JlIGxpa2UgYSBtZWNoYW5pbSB0byBub3RpZnkgcmVsYXRlZCBub2RlcyB0aGF0
IA0Kc29tZSBMU1BzIGFyZSBkZWRpY2F0ZWQgZm9yIFBUUCBtZXNzYWdlcyBvdGhlciB0aGFuIHRo
ZSBjaGlwcyBtZW1vcnkgDQpsaW1pdGF0aW9uLCBiZWNhdXNlIHRoZSBtZW1vcnkgcmVzdHJpY3Rp
b24gaXMgYWx3YXlzIHRoZXJlIHdoYXRldmVyIHlvdSB1c2UgDQpMYWJlbCBSYW5nZSBvciBub3Qu
DQpJTUhPLCBzaW5jZSB0aGUgb2JqZWN0aXZlIGlzIHRvIHRlbGwgcmVsYXRlZCBNUExTIG5vZGVz
IHdoaWNoIExTUHMgYXJlIFBUUCANCkxTUHMsIGFuIGluZGljYXRpb24gaW4gdGhlIHNpZ25hbGlu
ZyhSU1ZQLVRFL0dNUExTL0xEUCkgaXMgZW5vdWdoIGFuZCBzZWVtcyANCm1vcmUgY29tbW9uLiBB
bmQgaXQgd2lsbCBhdm9pZCB0aGUgc3RyaWN0IHJlcXVpcmVtZW50IG9mICJ0aGUgbmV0d29yayBh
bmQgDQphbGwgbm9kZXMgcmVxdWlyZWQgdG8gc3VwcG9ydCB0aGUgTGFiZWwgcmFuZ2UiLg0KSW4g
YWRkaXRpb24sIHRoZXJlIHNob3VsZCBiZSBzb21lIG1lY2hhbmltcyhlLmcuLCBJU0lTL09TUEYg
ZXh0ZW5zaW9ucykgZm9yIA0Kbm9kZXMgdG8gYWR2ZXJ0aXNlIHRoZWlyIFBUUCBjYXBhYmlsaXR5
IGhlbmNlIHRvIGhlbHAgUFRQIExTUHMgY29tcHV0YXRpb24uDQoNCkJlc3QgcmVnYXJkcywNCk1h
Y2gNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LQ0KRnJvbTogIlMuIERhdmFyaSIgPGRhdmFyaXNoQHlhaG9vLmNvbT4NClNlbnQ6IFdlZG5lc2Rh
eSwgSnVseSAxNCwgMjAxMCAyOjMxIFBNDQpUbzogIkppYSBIRSIgPGhlamlhQGh1YXdlaS5jb20+
OyAiU2hhaHJhbSBEYXZhcmkiIDxkYXZhcmlAYnJvYWRjb20uY29tPg0KQ2M6IDxtcGxzQGlldGYu
b3JnPjsgPHB3ZTNAaWV0Zi5vcmc+OyA8dGljY3RvY0BpZXRmLm9yZz47IDxtcGxzLXRwQGlldGYu
b3JnPg0KU3ViamVjdDogUmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCg0K
PiBIaSBKaWEsDQo+DQo+IExhYmVsIHJhbmdlIGlzIGEgU0hPVUxEIHJlcXVpcmVtZW50cyBhbmQg
bm90IE1VU1QuIFRoZSByZWFzb24gZm9yIExhYmVsIA0KPiBSYW5nZSBpcw0KPiBtYWlubHkgZm9y
IFBIWSBjaGlwcyB0aGF0IGRvbid0IGhhdmUgbGFyZ2UgbWVtb3J5IGFuZCBjYW4ndCBzdG9yZSBh
IGxvdCBvZg0KPiBMYWJlbHMuIE90aGVyd2lzZSB0aGUgUFRQIExTUCBpcyBzZXR1cCB2aWEgc2ln
bmFsaW5nIHRoYXQgc3BlY2lmaWVzIHRoZSANCj4gTFNQIGFzDQo+IGNhcnJ5aW5nIDE1ODguDQo+
DQo+IFNvIHRoZSBhbnN3ZXIgaXMgdGhhdCBpZiBhIExhYmVsIHJhbmdlIGlzIHVzZWQgaXQgbXVz
dCBiZSBhIEdsb2JhbCByYW5nZSANCj4gd2l0aGluDQo+IGEgbmV0d29yayBhbmQgc2hvdWxkIG5v
dCBiZSB1c2VkIGJ5IGFueSByb3V0ZXIgZm9yIG90aGVyIGFwcGxpY2F0aW9ucy4NCj4NCj4gVGhh
bmtzLA0KPiBTaGFocmFtDQo+DQo+DQo+DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+IEZyb206IEppYSBIRSA8aGVqaWFAaHVhd2VpLmNvbT4NCj4gVG86IFNoYWhyYW0gRGF2
YXJpIDxkYXZhcmlAYnJvYWRjb20uY29tPg0KPiBDYzogbXBsc0BpZXRmLm9yZzsgcHdlM0BpZXRm
Lm9yZzsgdGljY3RvY0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KPiBTZW50OiBUdWUsIEp1
bHkgMTMsIDIwMTAgOTo1MDozNyBQTQ0KPiBTdWJqZWN0OiBSZTogW21wbHNdIFtQV0UzXSAxNTg4
IG92ZXIgTVBMUyBkcmFmdA0KPg0KPg0KPiBIaSBTaGFocmFtLA0KPg0KPiBPbmUgcXVlc3Rpb24g
YWJvdXQgIlBUUCBMYWJlbCBSYW5nZSI6DQo+DQo+IFRvIG15IGtub3dsZWRnZSwgbGFiZWwgaW4g
TVBMUyBuZXR3b3JrIGlzIGEgbG9jYWwgIG1hdHRlci4gRm9yIGV4YW1wbGUsIHdlIA0KPiBtYXkN
Cj4gaGF2ZSBwZXItaW50ZXJmYWNlIG9yIHBlci1wbGF0Zm9ybSBsYWJlbCBzcGFjZS4gV2lsbCAg
dGhpcyBzcGVjaWZpY2VkICJQVFAgDQo+IExhYmVsDQo+IFJhbmdlIiBjb25mbGljdCB3aXRoIHRo
ZSBjdXJyZW50IGluLXVzZSBsYWJlbHMgIGZvciBjb21tb24gTFNQcz8NCj4NCj4NCj4gQi5SLg0K
PiBKaWENCj4NCj4gLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCj4+RnJvbTogU2hhaHJh
bSAgICBEYXZhcmkNCj4+VG86IHRpY2N0b2NAaWV0Zi5vcmcgOyBtcGxzQGlldGYub3JnIDsgbXBs
cy10cEBpZXRmLm9yZyA7IHB3ZTNAaWV0Zi5vcmcNCj4+U2VudDogVGh1cnNkYXksIEp1bHkgMDgs
IDIwMTAgMzoxMiBBTQ0KPj5TdWJqZWN0OiBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCj4+
DQo+Pg0KPj5IaSBBbGwsDQo+Pg0KPj5QbGVhc2UgZmluZCBhdHRhY2hlZCBvdXIgZmlyc3QgZHJh
ZnQgb2YgMTU4OCBvdmVyIE1QTFMuICAgIFNpbmNlIHdlIGhhdmUgDQo+PnNvbWUNCj4+dGVjaG5p
Y2FsIGlzc3VlcyBjb252ZXJ0aW5nIHRoZSBXb3JkIGZvcm1hdCB0byBUeHQgd2UgICAgY291bGRu
4oCZdCAgdXBsb2FkIA0KPj50aGUNCj4+ZHJhZnQgYmVmb3JlIHRoZSBjdXQtb2ZmIGRhdGUuIEhv
d2V2ZXIgd2Ugd2lsbCAgICBwcmVzZW50IHRoZSBkcmFmdCBpbiB0aGUgDQo+Pm5leHQNCj4+SUVU
RiBtZWV0aW5nIGFuZCB3aWxsIHVwbG9hZCB0aGUgZHJhZnQgYWZ0ZXIgdGhlICAgIG1lZXRpbmcu
DQo+Pg0KPj5Ob3RlIHRoYXQgdGhlIG1haW4gV0cgaXMgVGljVG9jIGJ1dCBtYXkgcmVxdWlyZSAg
ICBjb25zdWx0YXRpb24gd2l0aCBNUExTIA0KPj5hbmQNCj4+UFdFMyBXR3MuDQo+Pg0KPj5UaGFu
a3MsDQo+PlNoYWhyYW0gRGF2YXJpDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PnB3
ZTMgbWFpbGluZyAgICBsaXN0DQo+PnB3ZTNAaWV0Zi5vcmcNCj4+aHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9wd2UzDQo+Pg0KPg0KPg0KDQoNCg0KPiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBtcGxzIG1haWxpbmcgbGlzdA0K
PiBtcGxzQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
bXBscw0KPiANCg0KDQo=


From davari@broadcom.com  Wed Jul 14 11:06:58 2010
Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A3B63A6A9E; Wed, 14 Jul 2010 11:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.456
X-Spam-Level: 
X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599]
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 1XdhFZYrBKCt; Wed, 14 Jul 2010 11:06:56 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by core3.amsl.com (Postfix) with ESMTP id 68D8F3A696D; Wed, 14 Jul 2010 11:06:54 -0700 (PDT)
Received: from [10.16.192.224] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 14 Jul 2010 11:06:55 -0700
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Wed, 14 Jul 2010 11:06:55 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "curtis@occnc.com" <curtis@occnc.com>
Date: Wed, 14 Jul 2010 11:06:53 -0700
Thread-Topic: [PWE3] 1588 over MPLS draft
Thread-Index: AcsjdqeBK5kQ5GQWSx+iGBw4iS9MLAACF+Fg
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FB1@SJEXCHCCR02.corp.ad.broadcom.com>
References: Your message of "Wed, 07 Jul 2010 12:12:04 PDT." <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <201007141704.o6EH4T2I045662@harbor.orleans.occnc.com>
In-Reply-To: <201007141704.o6EH4T2I045662@harbor.orleans.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6023233410030845477-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 18:06:58 -0000

Hi Cutris,

Are you saying you can't read the word doc? Could you do me a favor and tel=
l me how to convert it to txt. I have been working on it without success. I=
 am trying now to write it in XML (which I am learning now).

Also note that the main thing is the idea and not what format the document =
is.=20

Thanks,
Shahram

-----Original Message-----
From: curtis@occnc.com [mailto:curtis@occnc.com]=20
Sent: Wednesday, July 14, 2010 10:04 AM
To: Shahram Davari
Cc: ticctoc@ietf.org; mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
Subject: Re: [PWE3] 1588 over MPLS draft


In message <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.=
broadcom.com>
"Shahram Davari" writes:
> =20
> =20
> Hi All,
> =20
> Please find attached our first draft of 1588 over MPLS. Since we have som=
e =3D
> technical issues converting the Word format to Txt we couldn't  upload th=
e =3D
> draft before the cut-off date. However we will present the draft in the n=
ex=3D
> t IETF meeting and will upload the draft after the meeting.
> =20
> Note that the main WG is TicToc but may require consultation with MPLS an=
d =3D
> PWE3 WGs.
> =20
> Thanks,
> Shahram Davari


IMO Attaching a word doc and asking for a slot at the meeting is
unacceptable.  At least convert the document to text or don't bother
and submit the draft after the meeting.  In any case, the cutoffs are
there for a reason and this should be given low priority at the
meeting (presented if there is time left over).

Curtis



From curtis@occnc.com  Wed Jul 14 15:10:21 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E51D3A6765; Wed, 14 Jul 2010 15:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.407
X-Spam-Level: 
X-Spam-Status: No, score=-2.407 tagged_above=-999 required=5 tests=[AWL=0.192,  BAYES_00=-2.599]
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 OYmvV57vLsPk; Wed, 14 Jul 2010 15:10:16 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 53FE93A63C9; Wed, 14 Jul 2010 15:10:16 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6EMAOhm050683; Wed, 14 Jul 2010 18:10:24 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007142210.o6EMAOhm050683@harbor.orleans.occnc.com>
To: "Shahram Davari" <davari@broadcom.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Wed, 14 Jul 2010 11:06:53 PDT." <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FB1@SJEXCHCCR02.corp.ad.broadcom.com>
Date: Wed, 14 Jul 2010 18:10:24 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2010 22:10:21 -0000

In message <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FB1@SJEXCHCCR02.corp.ad.broadcom.com>
"Shahram Davari" writes:
>  
> Hi Cutris,
>  
> Are you saying you can't read the word doc?  Could you do me a favor
> and tell me how to convert it to txt. I have been working on it
> without success. I am trying now to write it in XML (which I am
> learning now).

Converting to XML is the best approach.

Reading word is somewhat inconventient but doable since I have to move
the file to another machine that runs openoffice.  I wouldn't run an
insecure app like that (or worse yet an insecure OS with an even less
secure app) on any machine I actually cared about.  :-)

The XML is quite easy once you've done it the first time.

I'll wait for you to convert to XML and I'll deal with what you sent.

> Also note that the main thing is the idea and not what format the
> document is.

Yes, but some document formats are simply unacceptable and word is one
of them.  Not too fond of powerpoint either.

> Thanks,
> Shahram

Thanks,

Curtis



> -----Original Message-----
> From: curtis@occnc.com [mailto:curtis@occnc.com] 
> Sent: Wednesday, July 14, 2010 10:04 AM
> To: Shahram Davari
> Cc: ticctoc@ietf.org; mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> Subject: Re: [PWE3] 1588 over MPLS draft
>  
>  
> In message <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com>
> "Shahram Davari" writes:
> >  
> >  
> > Hi All,
> >  
> > Please find attached our first draft of 1588 over MPLS. Since we have some =
> > technical issues converting the Word format to Txt we couldn't  upload the =
> > draft before the cut-off date. However we will present the draft in the nex=
> > t IETF meeting and will upload the draft after the meeting.
> >  
> > Note that the main WG is TicToc but may require consultation with MPLS and =
> > PWE3 WGs.
> >  
> > Thanks,
> > Shahram Davari
>  
>  
> IMO Attaching a word doc and asking for a slot at the meeting is
> unacceptable.  At least convert the document to text or don't bother
> and submit the draft after the meeting.  In any case, the cutoffs are
> there for a reason and this should be given low priority at the
> meeting (presented if there is time left over).
>  
> Curtis

From mach@huawei.com  Wed Jul 14 19:20:29 2010
Return-Path: <mach@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F41963A68B5; Wed, 14 Jul 2010 19:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.286
X-Spam-Level: 
X-Spam-Status: No, score=-1.286 tagged_above=-999 required=5 tests=[AWL=1.312,  BAYES_00=-2.599, STOX_REPLY_TYPE=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 zSktby3YEZJH; Wed, 14 Jul 2010 19:20:27 -0700 (PDT)
Received: from szxga05-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 8206C3A6883; Wed, 14 Jul 2010 19:20:27 -0700 (PDT)
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 <0L5K00DGCUFZ8F@szxga05-in.huawei.com>; Thu, 15 Jul 2010 10:19:11 +0800 (CST)
Received: from m55527c ([10.110.98.169]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5K00GK9UFX23@szxga05-in.huawei.com>; Thu, 15 Jul 2010 10:19:11 +0800 (CST)
Date: Thu, 15 Jul 2010 10:19:09 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com>
To: Shahram Davari <davari@broadcom.com>, "S. Davari" <davarish@yahoo.com>, Jia HE <hejia@huawei.com>
Message-id: <6862C24AB1F4468D8F3265AE705925C6@m55527c>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206
X-Mailer: Microsoft Windows Live Mail 14.0.8064.206
Content-type: text/plain; format=flowed; charset=utf-8; reply-type=original
Content-transfer-encoding: 8BIT
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com>
Cc: mpls@ietf.org, pwe3@ietf.org, ticctoc@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 02:20:29 -0000

Hi Shahram,

I agree that the label range idea is an efficient way that could reduce the 
storage requirement of PHY chips.

It's easy to require one or limited nodes to reserve a label range, but 
IMHO, it very difficut to require all nodes of a large network to do this 
and even worse when some labels are already used by other LSPs, unless there 
are some mechanisms to negotiate/advertise(e.g., flooding the label range by 
IGP within the network) the proper label range hence to aviod label 
collision.

Best regards,
Mach

--------------------------------------------------
From: "Shahram Davari" <davari@broadcom.com>
Sent: Thursday, July 15, 2010 1:58 AM
To: "Mach Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>; "Jia 
HE" <hejia@huawei.com>
Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; <mpls-tp@ietf.org>
Subject: RE: [mpls] [PWE3] 1588 over MPLS draft

> Hi Mach,
>
> When a service provider wants to create these PTP LSPs, what is wrong with 
> allocating a range of labels for this purpose? This is purely a software 
> exercise. There are 2 million labels available to each node, why can't 
> some of them be allocated by software to PTP?
>
> In theory what you say is correct and should work, but in practice there 
> is a function called 1-step Transparent clocking that requires time 
> stamping at the PHY (immediately when the packet is received or 
> transmitted). PHY chips don't have CAM or lots of memory to store a few 
> thousand random labels. The label range will solve that problem and is 
> consistent with MPLS architecture.
>
> Thanks,
> Shahram
>
> -----Original Message-----
> From: Mach Chen [mailto:mach@huawei.com]
> Sent: Wednesday, July 14, 2010 1:53 AM
> To: S. Davari; Jia HE; Shahram Davari
> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>
> Hi Shahram,
>
> From the view of implementation, there is no more difference between 
> SHOULD
> and MUST :-)
> For me, the Label Range is more like a mechanim to notify related nodes 
> that
> some LSPs are dedicated for PTP messages other than the chips memory
> limitation, because the memory restriction is always there whatever you 
> use
> Label Range or not.
> IMHO, since the objective is to tell related MPLS nodes which LSPs are PTP
> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and 
> seems
> more common. And it will avoid the strict requirement of "the network and
> all nodes required to support the Label range".
> In addition, there should be some mechanims(e.g., ISIS/OSPF extensions) 
> for
> nodes to advertise their PTP capability hence to help PTP LSPs 
> computation.
>
> Best regards,
> Mach
>
>
> --------------------------------------------------
> From: "S. Davari" <davarish@yahoo.com>
> Sent: Wednesday, July 14, 2010 2:31 PM
> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" <davari@broadcom.com>
> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
> <mpls-tp@ietf.org>
> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>
>> Hi Jia,
>>
>> Label range is a SHOULD requirements and not MUST. The reason for Label
>> Range is
>> mainly for PHY chips that don't have large memory and can't store a lot 
>> of
>> Labels. Otherwise the PTP LSP is setup via signaling that specifies the
>> LSP as
>> carrying 1588.
>>
>> So the answer is that if a Label range is used it must be a Global range
>> within
>> a network and should not be used by any router for other applications.
>>
>> Thanks,
>> Shahram
>>
>>
>>
>> ________________________________
>> From: Jia HE <hejia@huawei.com>
>> To: Shahram Davari <davari@broadcom.com>
>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>> Sent: Tue, July 13, 2010 9:50:37 PM
>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>
>>
>> Hi Shahram,
>>
>> One question about "PTP Label Range":
>>
>> To my knowledge, label in MPLS network is a local  matter. For example, 
>> we
>> may
>> have per-interface or per-platform label space. Will  this specificed 
>> "PTP
>> Label
>> Range" conflict with the current in-use labels  for common LSPs?
>>
>>
>> B.R.
>> Jia
>>
>> ----- Original Message ----- 
>>>From: Shahram    Davari
>>>To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org
>>>Sent: Thursday, July 08, 2010 3:12 AM
>>>Subject: [PWE3] 1588 over MPLS draft
>>>
>>>
>>>Hi All,
>>>
>>>Please find attached our first draft of 1588 over MPLS.    Since we have
>>>some
>>>technical issues converting the Word format to Txt we    couldnâ€™t 
>>>upload
>>>the
>>>draft before the cut-off date. However we will    present the draft in 
>>>the
>>>next
>>>IETF meeting and will upload the draft after the    meeting.
>>>
>>>Note that the main WG is TicToc but may require    consultation with MPLS
>>>and
>>>PWE3 WGs.
>>>
>>>Thanks,
>>>Shahram Davari
>> ________________________________
>> _______________________________________________
>>>pwe3 mailing    list
>>>pwe3@ietf.org
>>>https://www.ietf.org/mailman/listinfo/pwe3
>>>
>>
>>
>
>
>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>
>
> 

From swallow@cisco.com  Wed Jul 14 19:57:52 2010
Return-Path: <swallow@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 227293A677C for <mpls@core3.amsl.com>; Wed, 14 Jul 2010 19:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.18
X-Spam-Level: 
X-Spam-Status: No, score=-10.18 tagged_above=-999 required=5 tests=[AWL=0.419,  BAYES_00=-2.599, 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 J3rX8Lzq0TqP for <mpls@core3.amsl.com>; Wed, 14 Jul 2010 19:57:51 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 1A0613A63CB for <mpls@ietf.org>; Wed, 14 Jul 2010 19:57:51 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtUFANoVPkytJV2b/2dsb2JhbACTLoxIcaVtmmqFJASIUII0
X-IronPort-AV: E=Sophos;i="4.55,205,1278288000"; d="scan'208";a="132532672"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rtp-iport-1.cisco.com with ESMTP; 15 Jul 2010 02:57:58 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id o6F2vwu8019192 for <mpls@ietf.org>; Thu, 15 Jul 2010 02:57:58 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 14 Jul 2010 21:57:58 -0500
Received: from 10.98.32.163 ([10.98.32.163]) by XMB-RCD-106.cisco.com ([72.163.62.148]) with Microsoft Exchange Server HTTP-DAV ;  Thu, 15 Jul 2010 02:57:58 +0000
User-Agent: Microsoft-Entourage/12.25.0.100505
Date: Wed, 14 Jul 2010 22:57:57 -0400
From: George Swallow <swallow@cisco.com>
To: <mpls@ietf.org>
Message-ID: <C863F175.277EE%swallow@cisco.com>
Thread-Topic: poll on draft-chen-mpls-return-path-specified-lsp-ping
Thread-Index: AcsjyYb4daQy1EhyXkGjfIBKdsbukg==
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 15 Jul 2010 02:57:58.0886 (UTC) FILETIME=[8817F060:01CB23C9]
Subject: [mpls] poll on draft-chen-mpls-return-path-specified-lsp-ping
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 02:57:52 -0000

The poll on draft-chen-mpls-return-path-specified-lsp-ping closed yesterday.
There was strong support and no objections to making this a WG document.

Mach - please submit the draft (unchanged) as
draft-ietf-mpls-return-path-specified-lsp-ping as soon as submissions are
re-opened.

...George


From jmh@joelhalpern.com  Wed Jul 14 20:20:29 2010
Return-Path: <jmh@joelhalpern.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D02283A6925; Wed, 14 Jul 2010 20:20:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
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 vTYtZ7HL83J4; Wed, 14 Jul 2010 20:20:28 -0700 (PDT)
Received: from hgblob.mail.tigertech.net (hgblob.mail.tigertech.net [64.62.209.71]) by core3.amsl.com (Postfix) with ESMTP id 75B8D3A68D4; Wed, 14 Jul 2010 20:20:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id AA57F32365D1; Wed, 14 Jul 2010 20:20:38 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-61.clppva.btas.verizon.net [71.161.50.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id E30303228BD7; Wed, 14 Jul 2010 20:20:36 -0700 (PDT)
Message-ID: <4C3E7E83.9080603@joelhalpern.com>
Date: Wed, 14 Jul 2010 23:20:35 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Mach Chen <mach@huawei.com>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com>	<04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com>	<89571.47481.qm@web88402.mail.re1.yahoo.com>	<F8A42E669722437AB6CD24CFD4586300@m55527c>	<2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c>
In-Reply-To: <6862C24AB1F4468D8F3265AE705925C6@m55527c>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: mpls@ietf.org, ticctoc@ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 03:20:29 -0000

Remember that if what is required is that the message arriving at the 
1588 supporting device have a certain label range, that is a purely 
local matter.  As long as the singaling carries the indication that the 
LSP is to be dedicated to 1588 traffic (a reasonable extension to the 
signaling), the downstream switch can pick what label to assign to that LSP.

If the goal is to have the outgoing label be from a specific range, that 
is essentially impossible in the proposed architecture.  The proposed 
architecture is one in which 1588 switches are peers with existing LSRs 
using MPLS.  As such, in order to have a label range for outgoing 
labels, the existing MPLS LSR would somehow have to know about this 
reserved label range, not use those labels for other purposes, and 
assign those labels to 1588 LSPs.  All of which is 
non-backwards-compatible.  If the 1588 LSPs were actually pseudowires, 
tunneled over LSPs, then any number of things are possible.

Yours,
Joel M. Halpern

Mach Chen wrote:
> Hi Shahram,
> 
> I agree that the label range idea is an efficient way that could reduce 
> the storage requirement of PHY chips.
> 
> It's easy to require one or limited nodes to reserve a label range, but 
> IMHO, it very difficut to require all nodes of a large network to do 
> this and even worse when some labels are already used by other LSPs, 
> unless there are some mechanisms to negotiate/advertise(e.g., flooding 
> the label range by IGP within the network) the proper label range hence 
> to aviod label collision.
> 
> Best regards,
> Mach
> 
> --------------------------------------------------
> From: "Shahram Davari" <davari@broadcom.com>
> Sent: Thursday, July 15, 2010 1:58 AM
> To: "Mach Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>; 
> "Jia HE" <hejia@huawei.com>
> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
> <mpls-tp@ietf.org>
> Subject: RE: [mpls] [PWE3] 1588 over MPLS draft
> 
>> Hi Mach,
>>
>> When a service provider wants to create these PTP LSPs, what is wrong 
>> with allocating a range of labels for this purpose? This is purely a 
>> software exercise. There are 2 million labels available to each node, 
>> why can't some of them be allocated by software to PTP?
>>
>> In theory what you say is correct and should work, but in practice 
>> there is a function called 1-step Transparent clocking that requires 
>> time stamping at the PHY (immediately when the packet is received or 
>> transmitted). PHY chips don't have CAM or lots of memory to store a 
>> few thousand random labels. The label range will solve that problem 
>> and is consistent with MPLS architecture.
>>
>> Thanks,
>> Shahram
>>
>> -----Original Message-----
>> From: Mach Chen [mailto:mach@huawei.com]
>> Sent: Wednesday, July 14, 2010 1:53 AM
>> To: S. Davari; Jia HE; Shahram Davari
>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>
>> Hi Shahram,
>>
>> From the view of implementation, there is no more difference between 
>> SHOULD
>> and MUST :-)
>> For me, the Label Range is more like a mechanim to notify related 
>> nodes that
>> some LSPs are dedicated for PTP messages other than the chips memory
>> limitation, because the memory restriction is always there whatever 
>> you use
>> Label Range or not.
>> IMHO, since the objective is to tell related MPLS nodes which LSPs are 
>> PTP
>> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and 
>> seems
>> more common. And it will avoid the strict requirement of "the network and
>> all nodes required to support the Label range".
>> In addition, there should be some mechanims(e.g., ISIS/OSPF 
>> extensions) for
>> nodes to advertise their PTP capability hence to help PTP LSPs 
>> computation.
>>
>> Best regards,
>> Mach
>>
>>
>> --------------------------------------------------
>> From: "S. Davari" <davarish@yahoo.com>
>> Sent: Wednesday, July 14, 2010 2:31 PM
>> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" <davari@broadcom.com>
>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
>> <mpls-tp@ietf.org>
>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>
>>> Hi Jia,
>>>
>>> Label range is a SHOULD requirements and not MUST. The reason for Label
>>> Range is
>>> mainly for PHY chips that don't have large memory and can't store a 
>>> lot of
>>> Labels. Otherwise the PTP LSP is setup via signaling that specifies the
>>> LSP as
>>> carrying 1588.
>>>
>>> So the answer is that if a Label range is used it must be a Global range
>>> within
>>> a network and should not be used by any router for other applications.
>>>
>>> Thanks,
>>> Shahram
>>>
>>>
>>>
>>> ________________________________
>>> From: Jia HE <hejia@huawei.com>
>>> To: Shahram Davari <davari@broadcom.com>
>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>>> Sent: Tue, July 13, 2010 9:50:37 PM
>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>
>>>
>>> Hi Shahram,
>>>
>>> One question about "PTP Label Range":
>>>
>>> To my knowledge, label in MPLS network is a local  matter. For 
>>> example, we
>>> may
>>> have per-interface or per-platform label space. Will  this specificed 
>>> "PTP
>>> Label
>>> Range" conflict with the current in-use labels  for common LSPs?
>>>
>>>
>>> B.R.
>>> Jia
>>>
>>> ----- Original Message -----
>>>> From: Shahram    Davari
>>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org
>>>> Sent: Thursday, July 08, 2010 3:12 AM
>>>> Subject: [PWE3] 1588 over MPLS draft
>>>>
>>>>
>>>> Hi All,
>>>>
>>>> Please find attached our first draft of 1588 over MPLS.    Since we 
>>>> have
>>>> some
>>>> technical issues converting the Word format to Txt we    couldnâ€™t 
>>>> upload
>>>> the
>>>> draft before the cut-off date. However we will    present the draft 
>>>> in the
>>>> next
>>>> IETF meeting and will upload the draft after the    meeting.
>>>>
>>>> Note that the main WG is TicToc but may require    consultation with 
>>>> MPLS
>>>> and
>>>> PWE3 WGs.
>>>>
>>>> Thanks,
>>>> Shahram Davari
>>> ________________________________
>>> _______________________________________________
>>>> pwe3 mailing    list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>
>>>
>>>
>>
>>
>>
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>>>
>>
>>
>>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From mach@huawei.com  Wed Jul 14 20:56:26 2010
Return-Path: <mach@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C5CE63A63CB; Wed, 14 Jul 2010 20:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.453
X-Spam-Level: 
X-Spam-Status: No, score=-0.453 tagged_above=-999 required=5 tests=[AWL=0.042,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 qiHfHUMLuwEY; Wed, 14 Jul 2010 20:56:24 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 089C43A68BE; Wed, 14 Jul 2010 20:56:24 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5K006XEYXUPL@szxga02-in.huawei.com>; Thu, 15 Jul 2010 11:56:18 +0800 (CST)
Received: from m55527c ([10.110.98.169]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5K00DJNYXTN1@szxga02-in.huawei.com>; Thu, 15 Jul 2010 11:56:17 +0800 (CST)
Date: Thu, 15 Jul 2010 11:56:16 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <4C3E7E83.9080603@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-id: <C4C5E3E9C1B04C5E8ED4A4F04E296EE8@m55527c>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206
X-Mailer: Microsoft Windows Live Mail 14.0.8064.206
Content-type: text/plain; format=flowed; charset=utf-8; reply-type=response
Content-transfer-encoding: 8BIT
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c> <4C3E7E83.9080603@joelhalpern.com>
Cc: mpls@ietf.org, ticctoc@ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 03:56:26 -0000

Hi Joel,

Please see inline...
--------------------------------------------------
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Sent: Thursday, July 15, 2010 11:20 AM
To: "Mach Chen" <mach@huawei.com>
Cc: "Shahram Davari" <davari@broadcom.com>; "S. Davari" 
<davarish@yahoo.com>; "Jia HE" <hejia@huawei.com>; <mpls@ietf.org>; 
<pwe3@ietf.org>; <ticctoc@ietf.org>; <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft

> Remember that if what is required is that the message arriving at the 1588 
> supporting device have a certain label range, that is a purely local 
> matter.  As long as the singaling carries the indication that the LSP is 
> to be dedicated to 1588 traffic (a reasonable extension to the signaling), 
> the downstream switch can pick what label to assign to that LSP.

Agree, that is my original suggestion.

Best regards,
Mach

>
> If the goal is to have the outgoing label be from a specific range, that 
> is essentially impossible in the proposed architecture.  The proposed 
> architecture is one in which 1588 switches are peers with existing LSRs 
> using MPLS.  As such, in order to have a label range for outgoing labels, 
> the existing MPLS LSR would somehow have to know about this reserved label 
> range, not use those labels for other purposes, and assign those labels to 
> 1588 LSPs.  All of which is non-backwards-compatible.  If the 1588 LSPs 
> were actually pseudowires, tunneled over LSPs, then any number of things 
> are possible.
>
> Yours,
> Joel M. Halpern
>
> Mach Chen wrote:
>> Hi Shahram,
>>
>> I agree that the label range idea is an efficient way that could reduce 
>> the storage requirement of PHY chips.
>>
>> It's easy to require one or limited nodes to reserve a label range, but 
>> IMHO, it very difficut to require all nodes of a large network to do this 
>> and even worse when some labels are already used by other LSPs, unless 
>> there are some mechanisms to negotiate/advertise(e.g., flooding the label 
>> range by IGP within the network) the proper label range hence to aviod 
>> label collision.
>>
>> Best regards,
>> Mach
>>
>> --------------------------------------------------
>> From: "Shahram Davari" <davari@broadcom.com>
>> Sent: Thursday, July 15, 2010 1:58 AM
>> To: "Mach Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>; "Jia 
>> HE" <hejia@huawei.com>
>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
>> <mpls-tp@ietf.org>
>> Subject: RE: [mpls] [PWE3] 1588 over MPLS draft
>>
>>> Hi Mach,
>>>
>>> When a service provider wants to create these PTP LSPs, what is wrong 
>>> with allocating a range of labels for this purpose? This is purely a 
>>> software exercise. There are 2 million labels available to each node, 
>>> why can't some of them be allocated by software to PTP?
>>>
>>> In theory what you say is correct and should work, but in practice there 
>>> is a function called 1-step Transparent clocking that requires time 
>>> stamping at the PHY (immediately when the packet is received or 
>>> transmitted). PHY chips don't have CAM or lots of memory to store a few 
>>> thousand random labels. The label range will solve that problem and is 
>>> consistent with MPLS architecture.
>>>
>>> Thanks,
>>> Shahram
>>>
>>> -----Original Message-----
>>> From: Mach Chen [mailto:mach@huawei.com]
>>> Sent: Wednesday, July 14, 2010 1:53 AM
>>> To: S. Davari; Jia HE; Shahram Davari
>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>
>>> Hi Shahram,
>>>
>>> From the view of implementation, there is no more difference between 
>>> SHOULD
>>> and MUST :-)
>>> For me, the Label Range is more like a mechanim to notify related nodes 
>>> that
>>> some LSPs are dedicated for PTP messages other than the chips memory
>>> limitation, because the memory restriction is always there whatever you 
>>> use
>>> Label Range or not.
>>> IMHO, since the objective is to tell related MPLS nodes which LSPs are 
>>> PTP
>>> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and 
>>> seems
>>> more common. And it will avoid the strict requirement of "the network 
>>> and
>>> all nodes required to support the Label range".
>>> In addition, there should be some mechanims(e.g., ISIS/OSPF extensions) 
>>> for
>>> nodes to advertise their PTP capability hence to help PTP LSPs 
>>> computation.
>>>
>>> Best regards,
>>> Mach
>>>
>>>
>>> --------------------------------------------------
>>> From: "S. Davari" <davarish@yahoo.com>
>>> Sent: Wednesday, July 14, 2010 2:31 PM
>>> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" <davari@broadcom.com>
>>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
>>> <mpls-tp@ietf.org>
>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>
>>>> Hi Jia,
>>>>
>>>> Label range is a SHOULD requirements and not MUST. The reason for Label
>>>> Range is
>>>> mainly for PHY chips that don't have large memory and can't store a lot 
>>>> of
>>>> Labels. Otherwise the PTP LSP is setup via signaling that specifies the
>>>> LSP as
>>>> carrying 1588.
>>>>
>>>> So the answer is that if a Label range is used it must be a Global 
>>>> range
>>>> within
>>>> a network and should not be used by any router for other applications.
>>>>
>>>> Thanks,
>>>> Shahram
>>>>
>>>>
>>>>
>>>> ________________________________
>>>> From: Jia HE <hejia@huawei.com>
>>>> To: Shahram Davari <davari@broadcom.com>
>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>>>> Sent: Tue, July 13, 2010 9:50:37 PM
>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>
>>>>
>>>> Hi Shahram,
>>>>
>>>> One question about "PTP Label Range":
>>>>
>>>> To my knowledge, label in MPLS network is a local  matter. For example, 
>>>> we
>>>> may
>>>> have per-interface or per-platform label space. Will  this specificed 
>>>> "PTP
>>>> Label
>>>> Range" conflict with the current in-use labels  for common LSPs?
>>>>
>>>>
>>>> B.R.
>>>> Jia
>>>>
>>>> ----- Original Message -----
>>>>> From: Shahram    Davari
>>>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; 
>>>>> pwe3@ietf.org
>>>>> Sent: Thursday, July 08, 2010 3:12 AM
>>>>> Subject: [PWE3] 1588 over MPLS draft
>>>>>
>>>>>
>>>>> Hi All,
>>>>>
>>>>> Please find attached our first draft of 1588 over MPLS.    Since we 
>>>>> have
>>>>> some
>>>>> technical issues converting the Word format to Txt we    couldnâ€™t 
>>>>> upload
>>>>> the
>>>>> draft before the cut-off date. However we will    present the draft in 
>>>>> the
>>>>> next
>>>>> IETF meeting and will upload the draft after the    meeting.
>>>>>
>>>>> Note that the main WG is TicToc but may require    consultation with 
>>>>> MPLS
>>>>> and
>>>>> PWE3 WGs.
>>>>>
>>>>> Thanks,
>>>>> Shahram Davari
>>>> ________________________________
>>>> _______________________________________________
>>>>> pwe3 mailing    list
>>>>> pwe3@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>> _______________________________________________
>>>> mpls mailing list
>>>> mpls@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>>
>>>
>>>
>>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls 


From hejia@huawei.com  Thu Jul 15 01:17:03 2010
Return-Path: <hejia@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB3313A6A8B; Thu, 15 Jul 2010 01:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.416
X-Spam-Level: 
X-Spam-Status: No, score=-0.416 tagged_above=-999 required=5 tests=[AWL=1.298,  BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=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 eXDrdn4x99FN; Thu, 15 Jul 2010 01:16:52 -0700 (PDT)
Received: from szxga05-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 1FB063A6A44; Thu, 15 Jul 2010 01:16:50 -0700 (PDT)
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 <0L5L00D10AXJDP@szxga05-in.huawei.com>; Thu, 15 Jul 2010 16:15:19 +0800 (CST)
Received: from 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 <0L5L00478AXIMD@szxga05-in.huawei.com>; Thu, 15 Jul 2010 16:15:18 +0800 (CST)
Received: from h48726 ([10.70.77.157]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5L00FQ5AXIFR@szxml04-in.huawei.com>; Thu, 15 Jul 2010 16:15:18 +0800 (CST)
Date: Thu, 15 Jul 2010 16:15:17 +0800
From: Jia HE <hejia@huawei.com>
To: "S. Davari" <davarish@yahoo.com>, Shahram Davari <davari@broadcom.com>
Message-id: <06cd01cb23f5$dc51a910$9d4d460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: multipart/alternative; boundary="Boundary_(ID_Q4723r3ARmAyP+mq2Atcaw)"
X-Priority: 3
X-MSMail-priority: Normal
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com>
Cc: mpls@ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 08:17:04 -0000

This is a multi-part message in MIME format.

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

SGkgU2hhaHJhbSwNCg0KVGhhbmtzIGZvciB5b3VyIHJlc3BvbnNlLiBCdXQgc3RpbGwgbW9yZSBm
b3IgY2xhcmlmaWNhdGlvbjoNCg0KU28gdGhlIHNwZWNpZmllZCBQVFAgTGFiZWwgUmFuZ2UgaXMg
Zm9yIHRoZSBQSFkgdG8gZWFzaWx5IHJlY29nbml6ZSBhbmQgZ2V0IHRvIHByb2Nlc3MgUFRQIGlu
Zm9ybWF0aW9uIHRoYXQgaXMgY2FycmllZCBvbiBMU1BzIG9yIFBXcy4gVGhpcyBpcyBlZmZpY2ll
bnQgd2hlbiB3ZSBkZWZpbmUgYW5kIG1ha2Uga25vd24gc3VjaCBhIExhYmVsIHJhbmdlIGdsb2Jh
bGx5IGF0IHRoZSBiZWdpbm5pbmcgb2Ygc2V0dGluZyB1cCBhIG5ldHdvcmsuIFdoYXQgaWYgd2Ug
d2FudCB0byBzZXQgdXAgc3VjaCBQVFAgTFNQcyB1c2luZyBhIGdsb2JhbCBsYWJlbCByYW5nZSB3
aGVuIHRoZXJlIGFyZSBhbHJlYWR5IExTUHMgaW4gdXNlIGluIHRoZSBuZXR3b3JrPyBJdCBtaWdo
dCBiZSBkaWZmaWN1bHQgdG8gZ2V0IGEgZ2xvYmFsIGxhYmVsIHJhbmdlIGluIHRoaXMgY2FzZSBj
b25zaWRlcmluZyB0aGUgcG9zc2libGUgbGFiZWwgY29sbGlzaW9uLiBPciBpbiB0aGlzIGNhc2Ug
d2UgZGVwZW5kIG9uIHNpZ25hbGluZyBidXQgbWF5IGNhdXNlIGJ1cmRlbiBmb3IgUEhZIGNoaXBz
LiBJZiBJJ20gcmlnaHQsIGl0IHNlZW1zIGEgY29tcHJvbWlzZSBiZXR3ZWVuIHRoZSB0d28uIElz
IHRoYXQgdHJ1ZT8NCg0KVGhhbmtzIQ0KDQpCLlIuDQpKaWENCg0KICAtLS0tLSBPcmlnaW5hbCBN
ZXNzYWdlIC0tLS0tIA0KICBGcm9tOiBTLiBEYXZhcmkgDQogIFRvOiBKaWEgSEUgOyBTaGFocmFt
IERhdmFyaSANCiAgQ2M6IG1wbHNAaWV0Zi5vcmcgOyBwd2UzQGlldGYub3JnIDsgdGljY3RvY0Bp
ZXRmLm9yZyA7IG1wbHMtdHBAaWV0Zi5vcmcgDQogIFNlbnQ6IFdlZG5lc2RheSwgSnVseSAxNCwg
MjAxMCAyOjMxIFBNDQogIFN1YmplY3Q6IFJlOiBbbXBsc10gW1BXRTNdIDE1ODggb3ZlciBNUExT
IGRyYWZ0DQoNCg0KICBIaSBKaWEsDQoNCg0KICBMYWJlbCByYW5nZSBpcyBhIFNIT1VMRCByZXF1
aXJlbWVudHMgYW5kIG5vdCBNVVNULiBUaGUgcmVhc29uIGZvciBMYWJlbCBSYW5nZSBpcyBtYWlu
bHkgZm9yIFBIWSBjaGlwcyB0aGF0IGRvbid0IGhhdmUgbGFyZ2UgbWVtb3J5IGFuZCBjYW4ndCBz
dG9yZSBhIGxvdCBvZiBMYWJlbHMuIE90aGVyd2lzZSB0aGUgUFRQIExTUCBpcyBzZXR1cCB2aWEg
c2lnbmFsaW5nIHRoYXQgc3BlY2lmaWVzIHRoZSBMU1AgYXMgY2FycnlpbmcgMTU4OC4NCg0KDQog
IFNvIHRoZSBhbnN3ZXIgaXMgdGhhdCBpZiBhIExhYmVsIHJhbmdlIGlzIHVzZWQgaXQgbXVzdCBi
ZSBhIEdsb2JhbCByYW5nZSB3aXRoaW4gYSBuZXR3b3JrIGFuZCBzaG91bGQgbm90IGJlIHVzZWQg
YnkgYW55IHJvdXRlciBmb3Igb3RoZXIgYXBwbGljYXRpb25zLg0KDQoNCiAgVGhhbmtzLA0KICBT
aGFocmFtDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiAgRnJvbTogSmlhIEhFIDxoZWpp
YUBodWF3ZWkuY29tPg0KICBUbzogU2hhaHJhbSBEYXZhcmkgPGRhdmFyaUBicm9hZGNvbS5jb20+
DQogIENjOiBtcGxzQGlldGYub3JnOyBwd2UzQGlldGYub3JnOyB0aWNjdG9jQGlldGYub3JnOyBt
cGxzLXRwQGlldGYub3JnDQogIFNlbnQ6IFR1ZSwgSnVseSAxMywgMjAxMCA5OjUwOjM3IFBNDQog
IFN1YmplY3Q6IFJlOiBbbXBsc10gW1BXRTNdIDE1ODggb3ZlciBNUExTIGRyYWZ0DQoNCg0KICBI
aSBTaGFocmFtLA0KDQogIE9uZSBxdWVzdGlvbiBhYm91dCAiUFRQIExhYmVsIFJhbmdlIjoNCg0K
ICBUbyBteSBrbm93bGVkZ2UsIGxhYmVsIGluIE1QTFMgbmV0d29yayBpcyBhIGxvY2FsIG1hdHRl
ci4gRm9yIGV4YW1wbGUsIHdlIG1heSBoYXZlIHBlci1pbnRlcmZhY2Ugb3IgcGVyLXBsYXRmb3Jt
IGxhYmVsIHNwYWNlLiBXaWxsIHRoaXMgc3BlY2lmaWNlZCAiUFRQIExhYmVsIFJhbmdlIiBjb25m
bGljdCB3aXRoIHRoZSBjdXJyZW50IGluLXVzZSBsYWJlbHMgZm9yIGNvbW1vbiBMU1BzPyANCg0K
ICBCLlIuDQogIEppYQ0KDQogICAgLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCiAgICBG
cm9tOiBTaGFocmFtIERhdmFyaSANCiAgICBUbzogdGljY3RvY0BpZXRmLm9yZyA7IG1wbHNAaWV0
Zi5vcmcgOyBtcGxzLXRwQGlldGYub3JnIDsgcHdlM0BpZXRmLm9yZyANCiAgICBTZW50OiBUaHVy
c2RheSwgSnVseSAwOCwgMjAxMCAzOjEyIEFNDQogICAgU3ViamVjdDogW1BXRTNdIDE1ODggb3Zl
ciBNUExTIGRyYWZ0DQoNCg0KICAgIEhpIEFsbCwNCg0KDQoNCiAgICBQbGVhc2UgZmluZCBhdHRh
Y2hlZCBvdXIgZmlyc3QgZHJhZnQgb2YgMTU4OCBvdmVyIE1QTFMuIFNpbmNlIHdlIGhhdmUgc29t
ZSB0ZWNobmljYWwgaXNzdWVzIGNvbnZlcnRpbmcgdGhlIFdvcmQgZm9ybWF0IHRvIFR4dCB3ZSBj
b3VsZG7igJl0ICB1cGxvYWQgdGhlIGRyYWZ0IGJlZm9yZSB0aGUgY3V0LW9mZiBkYXRlLiBIb3dl
dmVyIHdlIHdpbGwgcHJlc2VudCB0aGUgZHJhZnQgaW4gdGhlIG5leHQgSUVURiBtZWV0aW5nIGFu
ZCB3aWxsIHVwbG9hZCB0aGUgZHJhZnQgYWZ0ZXIgdGhlIG1lZXRpbmcuDQoNCg0KDQogICAgTm90
ZSB0aGF0IHRoZSBtYWluIFdHIGlzIFRpY1RvYyBidXQgbWF5IHJlcXVpcmUgY29uc3VsdGF0aW9u
IHdpdGggTVBMUyBhbmQgUFdFMyBXR3MuDQoNCg0KDQogICAgVGhhbmtzLA0KDQogICAgU2hhaHJh
bSBEYXZhcmkNCg0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KDQogICAgX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgICBwd2UzIG1haWxpbmcgbGlz
dA0KICAgIHB3ZTNAaWV0Zi5vcmcNCiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3B3ZTMNCg0KDQo=

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

77u/PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9u
YWwvL0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29u
dGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxTVFlMRSB0eXBlPXRleHQvY3NzPkRJ
ViB7DQoJTUFSR0lOOiAwcHgNCn0NCjwvU1RZTEU+DQoNCjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA2
LjAwLjI5MDAuMzY3NiIgbmFtZT1HRU5FUkFUT1I+PC9IRUFEPg0KPEJPRFkgYmdDb2xvcj0jZmZm
ZmZmPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsPkhpIFNoYWhyYW0sPC9GT05UPjwvRElWPg0KPERJ
Vj48Rk9OVCBmYWNlPUFyaWFsPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1B
cmlhbD5UaGFua3MgZm9yIHlvdXIgcmVzcG9uc2UuIEJ1dCBzdGlsbCBtb3JlIGZvciANCmNsYXJp
ZmljYXRpb246PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsPjwvRk9OVD4mbmJz
cDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbD5TbyB0aGUgc3BlY2lmaWVkIFBUUCBMYWJl
bCBSYW5nZSBpcyBmb3IgdGhlIFBIWSB0byBlYXNpbHkgDQpyZWNvZ25pemUgYW5kIGdldCZuYnNw
O3RvJm5ic3A7cHJvY2VzcyZuYnNwO1BUUCBpbmZvcm1hdGlvbiB0aGF0IGlzIGNhcnJpZWQgDQpv
biZuYnNwO0xTUHMgb3IgUFdzLiBUaGlzJm5ic3A7aXMgZWZmaWNpZW50Jm5ic3A7d2hlbiB3ZSBk
ZWZpbmUgYW5kIG1ha2UgDQprbm93biZuYnNwO3N1Y2ggYSZuYnNwO0xhYmVsIHJhbmdlJm5ic3A7
Z2xvYmFsbHkmbmJzcDthdCB0aGUmbmJzcDtiZWdpbm5pbmcgb2YgDQpzZXR0aW5nIHVwIGEgbmV0
d29yay4gV2hhdCZuYnNwO2lmIHdlJm5ic3A7d2FudCB0byBzZXQgdXAgc3VjaCZuYnNwO1BUUCBM
U1BzIA0KdXNpbmcgYSBnbG9iYWwgbGFiZWwmbmJzcDtyYW5nZSZuYnNwO3doZW4gdGhlcmUgYXJl
IGFscmVhZHkgTFNQcyBpbiB1c2UgaW4gdGhlIA0KbmV0d29yaz8gSXQgbWlnaHQgYmUgZGlmZmlj
dWx0IHRvIGdldCBhIGdsb2JhbCBsYWJlbCByYW5nZSBpbiB0aGlzIGNhc2UgDQpjb25zaWRlcmlu
ZyB0aGUgcG9zc2libGUgbGFiZWwgY29sbGlzaW9uLiZuYnNwO09yIGluIHRoaXMgY2FzZSB3ZSBk
ZXBlbmQgDQpvbiZuYnNwO3NpZ25hbGluZyBidXQgbWF5IGNhdXNlIGJ1cmRlbiBmb3IgUEhZIGNo
aXBzLiBJZiBJJ20gcmlnaHQsIGl0IHNlZW1zIA0KYSZuYnNwO2NvbXByb21pc2UgYmV0d2VlbiB0
aGUgdHdvLiBJcyB0aGF0IHRydWU/PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFs
PjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbD5UaGFua3MhPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+
PEZPTlQgZmFjZT1BcmlhbD5CLlIuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFs
PkppYTwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT3lrovkvZMgc2l6ZT0yPjwvRk9OVD4m
bmJzcDs8L0RJVj4NCjxCTE9DS1FVT1RFIA0Kc3R5bGU9IlBBRERJTkctUklHSFQ6IDBweDsgUEFE
RElORy1MRUZUOiA1cHg7IE1BUkdJTi1MRUZUOiA1cHg7IEJPUkRFUi1MRUZUOiAjMDAwMDAwIDJw
eCBzb2xpZDsgTUFSR0lOLVJJR0hUOiAwcHgiPg0KICA8RElWIHN0eWxlPSJGT05UOiA5cHQg5a6L
5L2TIj4tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIDwvRElWPg0KICA8RElWIHN0eWxlPSJC
QUNLR1JPVU5EOiAjZTRlNGU0OyBGT05UOiA5cHQg5a6L5L2TOyBmb250LWNvbG9yOiBibGFjayI+
PEI+RnJvbTo8L0I+IA0KICA8QSB0aXRsZT1kYXZhcmlzaEB5YWhvby5jb20gaHJlZj0ibWFpbHRv
OmRhdmFyaXNoQHlhaG9vLmNvbSI+Uy4gRGF2YXJpPC9BPiANCiAgPC9ESVY+DQogIDxESVYgc3R5
bGU9IkZPTlQ6IDlwdCDlrovkvZMiPjxCPlRvOjwvQj4gPEEgdGl0bGU9aGVqaWFAaHVhd2VpLmNv
bSANCiAgaHJlZj0ibWFpbHRvOmhlamlhQGh1YXdlaS5jb20iPkppYSBIRTwvQT4gOyA8QSB0aXRs
ZT1kYXZhcmlAYnJvYWRjb20uY29tIA0KICBocmVmPSJtYWlsdG86ZGF2YXJpQGJyb2FkY29tLmNv
bSI+U2hhaHJhbSBEYXZhcmk8L0E+IDwvRElWPg0KICA8RElWIHN0eWxlPSJGT05UOiA5cHQg5a6L
5L2TIj48Qj5DYzo8L0I+IDxBIHRpdGxlPW1wbHNAaWV0Zi5vcmcgDQogIGhyZWY9Im1haWx0bzpt
cGxzQGlldGYub3JnIj5tcGxzQGlldGYub3JnPC9BPiA7IDxBIHRpdGxlPXB3ZTNAaWV0Zi5vcmcg
DQogIGhyZWY9Im1haWx0bzpwd2UzQGlldGYub3JnIj5wd2UzQGlldGYub3JnPC9BPiA7IDxBIHRp
dGxlPXRpY2N0b2NAaWV0Zi5vcmcgDQogIGhyZWY9Im1haWx0bzp0aWNjdG9jQGlldGYub3JnIj50
aWNjdG9jQGlldGYub3JnPC9BPiA7IDxBIA0KICB0aXRsZT1tcGxzLXRwQGlldGYub3JnIGhyZWY9
Im1haWx0bzptcGxzLXRwQGlldGYub3JnIj5tcGxzLXRwQGlldGYub3JnPC9BPiANCiAgPC9ESVY+
DQogIDxESVYgc3R5bGU9IkZPTlQ6IDlwdCDlrovkvZMiPjxCPlNlbnQ6PC9CPiBXZWRuZXNkYXks
IEp1bHkgMTQsIDIwMTAgMjozMSBQTTwvRElWPg0KICA8RElWIHN0eWxlPSJGT05UOiA5cHQg5a6L
5L2TIj48Qj5TdWJqZWN0OjwvQj4gUmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgDQog
IGRyYWZ0PC9ESVY+DQogIDxESVY+PEJSPjwvRElWPg0KICA8RElWIA0KICBzdHlsZT0iRk9OVC1T
SVpFOiAxMnB0OyBGT05ULUZBTUlMWTogJ0NvdXJpZXIgTmV3JywgY291cmllciwgbW9uYWNvLCBt
b25vc3BhY2UsIHNhbnMtc2VyaWYiPg0KICA8RElWPkhpIEppYSw8L0RJVj4NCiAgPERJVj48QlI+
PC9ESVY+DQogIDxESVY+TGFiZWwgcmFuZ2UgaXMgYSBTSE9VTEQgcmVxdWlyZW1lbnRzIGFuZCBu
b3QgTVVTVC4gVGhlIHJlYXNvbiBmb3IgTGFiZWwgDQogIFJhbmdlIGlzIG1haW5seSBmb3IgUEhZ
IGNoaXBzIHRoYXQgZG9uJ3QgaGF2ZSBsYXJnZSBtZW1vcnkgYW5kIGNhbid0IHN0b3JlIGEgDQog
IGxvdCBvZiBMYWJlbHMuIE90aGVyd2lzZSB0aGUgUFRQIExTUCBpcyBzZXR1cCB2aWEgc2lnbmFs
aW5nIHRoYXQgc3BlY2lmaWVzIHRoZSANCiAgTFNQIGFzIGNhcnJ5aW5nIDE1ODguPC9ESVY+DQog
IDxESVY+PEJSPjwvRElWPg0KICA8RElWPlNvIHRoZSBhbnN3ZXIgaXMgdGhhdCBpZiBhIExhYmVs
IHJhbmdlIGlzIHVzZWQgaXQgbXVzdCBiZSBhIEdsb2JhbCByYW5nZSANCiAgd2l0aGluIGEgbmV0
d29yayBhbmQgc2hvdWxkIG5vdCBiZSB1c2VkIGJ5IGFueSByb3V0ZXIgZm9yIG90aGVyIA0KICBh
cHBsaWNhdGlvbnMuPC9ESVY+DQogIDxESVY+PEJSPjwvRElWPg0KICA8RElWPlRoYW5rcyw8L0RJ
Vj4NCiAgPERJVj5TaGFocmFtPC9ESVY+DQogIDxESVYgDQogIHN0eWxlPSJGT05ULVNJWkU6IDEy
cHQ7IEZPTlQtRkFNSUxZOiBDb3VyaWVyIE5ldywgY291cmllciwgbW9uYWNvLCBtb25vc3BhY2Us
IHNhbnMtc2VyaWYiPjxCUj4NCiAgPERJViANCiAgc3R5bGU9IkZPTlQtU0laRTogMTJwdDsgRk9O
VC1GQU1JTFk6IHRpbWVzIG5ldyByb21hbiwgbmV3IHlvcmssIHRpbWVzLCBzZXJpZiI+PEZPTlQg
DQogIGZhY2U9VGFob21hIHNpemU9Mj4NCiAgPEhSIFNJWkU9MT4NCiAgPEI+PFNQQU4gc3R5bGU9
IkZPTlQtV0VJR0hUOiBib2xkIj5Gcm9tOjwvU1BBTj48L0I+IEppYSBIRSAmbHQ7PEEgDQogIGhy
ZWY9Im1haWx0bzpoZWppYUBodWF3ZWkuY29tIj5oZWppYUBodWF3ZWkuY29tPC9BPiZndDs8QlI+
PEI+PFNQQU4gDQogIHN0eWxlPSJGT05ULVdFSUdIVDogYm9sZCI+VG86PC9TUEFOPjwvQj4gU2hh
aHJhbSBEYXZhcmkgJmx0OzxBIA0KICBocmVmPSJtYWlsdG86ZGF2YXJpQGJyb2FkY29tLmNvbSI+
ZGF2YXJpQGJyb2FkY29tLmNvbTwvQT4mZ3Q7PEJSPjxCPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1X
RUlHSFQ6IGJvbGQiPkNjOjwvU1BBTj48L0I+IDxBIA0KICBocmVmPSJtYWlsdG86bXBsc0BpZXRm
Lm9yZyI+bXBsc0BpZXRmLm9yZzwvQT47IDxBIA0KICBocmVmPSJtYWlsdG86cHdlM0BpZXRmLm9y
ZyI+cHdlM0BpZXRmLm9yZzwvQT47IDxBIA0KICBocmVmPSJtYWlsdG86dGljY3RvY0BpZXRmLm9y
ZyI+dGljY3RvY0BpZXRmLm9yZzwvQT47IDxBIA0KICBocmVmPSJtYWlsdG86bXBscy10cEBpZXRm
Lm9yZyI+bXBscy10cEBpZXRmLm9yZzwvQT48QlI+PEI+PFNQQU4gDQogIHN0eWxlPSJGT05ULVdF
SUdIVDogYm9sZCI+U2VudDo8L1NQQU4+PC9CPiBUdWUsIEp1bHkgMTMsIDIwMTAgOTo1MDozNyAN
CiAgUE08QlI+PEI+PFNQQU4gc3R5bGU9IkZPTlQtV0VJR0hUOiBib2xkIj5TdWJqZWN0OjwvU1BB
Tj48L0I+IFJlOiBbbXBsc10gW1BXRTNdIA0KICAxNTg4IG92ZXIgTVBMUyBkcmFmdDxCUj48L0ZP
TlQ+PEJSPg0KICA8U1RZTEU+IF9maWx0ZXJlZCB7CmZvbnQtZmFtaWx5OkNhbWJyaWEgTWF0aDsK
fQogX2ZpbHRlcmVkIHsKZm9udC1mYW1pbHk6Q2FsaWJyaTsKfQogX2ZpbHRlcmVkIHttYXJnaW46
MS4waW4gMS4waW4gMS4waW4gMS4waW47fQpQLk1zb05vcm1hbCB7CkZPTlQtU0laRToxMXB0O01B
UkdJTjowaW4gMGluIDBwdDtGT05ULUZBTUlMWToic2Fucy1zZXJpZiI7fQpMSS5Nc29Ob3JtYWwg
ewpGT05ULVNJWkU6MTFwdDtNQVJHSU46MGluIDBpbiAwcHQ7Rk9OVC1GQU1JTFk6InNhbnMtc2Vy
aWYiO30KRElWLk1zb05vcm1hbCB7CkZPTlQtU0laRToxMXB0O01BUkdJTjowaW4gMGluIDBwdDtG
T05ULUZBTUlMWToic2Fucy1zZXJpZiI7fQpBOmxpbmsgewpDT0xPUjpibHVlO1RFWFQtREVDT1JB
VElPTjp1bmRlcmxpbmU7fQpTUEFOLk1zb0h5cGVybGluayB7CkNPTE9SOmJsdWU7VEVYVC1ERUNP
UkFUSU9OOnVuZGVybGluZTt9CkE6dmlzaXRlZCB7CkNPTE9SOnB1cnBsZTtURVhULURFQ09SQVRJ
T046dW5kZXJsaW5lO30KU1BBTi5Nc29IeXBlcmxpbmtGb2xsb3dlZCB7CkNPTE9SOnB1cnBsZTtU
RVhULURFQ09SQVRJT046dW5kZXJsaW5lO30KU1BBTi5FbWFpbFN0eWxlMTcgewpDT0xPUjp3aW5k
b3d0ZXh0O0ZPTlQtRkFNSUxZOiJzYW5zLXNlcmlmIjt9Ci5Nc29DaHBEZWZhdWx0IHsKfQpESVYu
U2VjdGlvbjEgewp9CjwvU1RZTEU+DQoNCiAgPERJVj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+
SGkgU2hhaHJhbSw8L0ZPTlQ+PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT3lrovkvZMgc2l6ZT0y
PjwvRk9OVD4mbmJzcDs8L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+T25l
IHF1ZXN0aW9uIGFib3V0ICJQVFAgTGFiZWwgUmFuZ2UiOjwvRk9OVD48L0RJVj4NCiAgPERJVj48
Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KICA8RElWPjxGT05U
IGZhY2U95a6L5L2TIHNpemU9Mj5UbyBteSBrbm93bGVkZ2UsIGxhYmVsIGluIE1QTFMgbmV0d29y
ayBpcyBhIGxvY2FsIA0KICBtYXR0ZXIuIEZvciBleGFtcGxlLCB3ZSBtYXkgaGF2ZSBwZXItaW50
ZXJmYWNlIG9yIHBlci1wbGF0Zm9ybSBsYWJlbCBzcGFjZS4gDQogIFdpbGwgdGhpcyBzcGVjaWZp
Y2VkICJQVFAgTGFiZWwgUmFuZ2UiIGNvbmZsaWN0IHdpdGggdGhlIGN1cnJlbnQgDQogIGluLXVz
ZSZuYnNwO2xhYmVscyBmb3IgY29tbW9uIExTUHM/IDwvRk9OVD48Rk9OVCBmYWNlPeWui+S9kyBz
aXplPTI+PC9GT05UPjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U95a6L5L2TIHNpemU9Mj48L0ZP
TlQ+Jm5ic3A7PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT3lrovkvZMgc2l6ZT0yPkIuUi48L0ZP
TlQ+PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT3lrovkvZMgc2l6ZT0yPkppYTwvRk9OVD48L0RJ
Vj4NCiAgPERJVj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0K
ICA8QkxPQ0tRVU9URSANCiAgc3R5bGU9IlBBRERJTkctUklHSFQ6IDBweDsgUEFERElORy1MRUZU
OiA1cHg7IE1BUkdJTi1MRUZUOiA1cHg7IEJPUkRFUi1MRUZUOiAjMDAwMDAwIDJweCBzb2xpZDsg
TUFSR0lOLVJJR0hUOiAwcHgiPg0KICAgIDxESVYgDQogICAgc3R5bGU9IkZPTlQtV0VJR0hUOiBu
b3JtYWw7IEZPTlQtU0laRTogOXB0OyBMSU5FLUhFSUdIVDogbm9ybWFsOyBGT05ULVNUWUxFOiBu
b3JtYWw7IEZPTlQtVkFSSUFOVDogbm9ybWFsIj4tLS0tLSANCiAgICBPcmlnaW5hbCBNZXNzYWdl
IC0tLS0tIDwvRElWPg0KICAgIDxESVYgDQogICAgc3R5bGU9IkZPTlQtV0VJR0hUOiBub3JtYWw7
IEZPTlQtU0laRTogOXB0OyBCQUNLR1JPVU5EOiAjZTRlNGU0OyBMSU5FLUhFSUdIVDogbm9ybWFs
OyBGT05ULVNUWUxFOiBub3JtYWw7IEZPTlQtVkFSSUFOVDogbm9ybWFsIj48Qj5Gcm9tOjwvQj4g
DQogICAgPEEgdGl0bGU9ZGF2YXJpQGJyb2FkY29tLmNvbSBocmVmPSJtYWlsdG86ZGF2YXJpQGJy
b2FkY29tLmNvbSIgdGFyZ2V0PV9ibGFuayANCiAgICByZWw9bm9mb2xsb3cgeW1haWx0bz0ibWFp
bHRvOmRhdmFyaUBicm9hZGNvbS5jb20iPlNoYWhyYW0gRGF2YXJpPC9BPiA8L0RJVj4NCiAgICA8
RElWIA0KICAgIHN0eWxlPSJGT05ULVdFSUdIVDogbm9ybWFsOyBGT05ULVNJWkU6IDlwdDsgTElO
RS1IRUlHSFQ6IG5vcm1hbDsgRk9OVC1TVFlMRTogbm9ybWFsOyBGT05ULVZBUklBTlQ6IG5vcm1h
bCI+PEI+VG86PC9CPiANCiAgICA8QSB0aXRsZT10aWNjdG9jQGlldGYub3JnIGhyZWY9Im1haWx0
bzp0aWNjdG9jQGlldGYub3JnIiB0YXJnZXQ9X2JsYW5rIA0KICAgIHJlbD1ub2ZvbGxvdyB5bWFp
bHRvPSJtYWlsdG86dGljY3RvY0BpZXRmLm9yZyI+dGljY3RvY0BpZXRmLm9yZzwvQT4gOyA8QSAN
CiAgICB0aXRsZT1tcGxzQGlldGYub3JnIGhyZWY9Im1haWx0bzptcGxzQGlldGYub3JnIiB0YXJn
ZXQ9X2JsYW5rIHJlbD1ub2ZvbGxvdyANCiAgICB5bWFpbHRvPSJtYWlsdG86bXBsc0BpZXRmLm9y
ZyI+bXBsc0BpZXRmLm9yZzwvQT4gOyA8QSB0aXRsZT1tcGxzLXRwQGlldGYub3JnIA0KICAgIGhy
ZWY9Im1haWx0bzptcGxzLXRwQGlldGYub3JnIiB0YXJnZXQ9X2JsYW5rIHJlbD1ub2ZvbGxvdyAN
CiAgICB5bWFpbHRvPSJtYWlsdG86bXBscy10cEBpZXRmLm9yZyI+bXBscy10cEBpZXRmLm9yZzwv
QT4gOyA8QSANCiAgICB0aXRsZT1wd2UzQGlldGYub3JnIGhyZWY9Im1haWx0bzpwd2UzQGlldGYu
b3JnIiB0YXJnZXQ9X2JsYW5rIHJlbD1ub2ZvbGxvdyANCiAgICB5bWFpbHRvPSJtYWlsdG86cHdl
M0BpZXRmLm9yZyI+cHdlM0BpZXRmLm9yZzwvQT4gPC9ESVY+DQogICAgPERJViANCiAgICBzdHls
ZT0iRk9OVC1XRUlHSFQ6IG5vcm1hbDsgRk9OVC1TSVpFOiA5cHQ7IExJTkUtSEVJR0hUOiBub3Jt
YWw7IEZPTlQtU1RZTEU6IG5vcm1hbDsgRk9OVC1WQVJJQU5UOiBub3JtYWwiPjxCPlNlbnQ6PC9C
PiANCiAgICBUaHVyc2RheSwgSnVseSAwOCwgMjAxMCAzOjEyIEFNPC9ESVY+DQogICAgPERJViAN
CiAgICBzdHlsZT0iRk9OVC1XRUlHSFQ6IG5vcm1hbDsgRk9OVC1TSVpFOiA5cHQ7IExJTkUtSEVJ
R0hUOiBub3JtYWw7IEZPTlQtU1RZTEU6IG5vcm1hbDsgRk9OVC1WQVJJQU5UOiBub3JtYWwiPjxC
PlN1YmplY3Q6PC9CPiANCiAgICBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQ8L0RJVj4NCiAg
ICA8RElWPjxCUj48L0RJVj4NCiAgICA8RElWIGNsYXNzPVNlY3Rpb24xPg0KICAgIDxQIGNsYXNz
PU1zb05vcm1hbD5IaSBBbGwsPC9QPg0KICAgIDxQIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8L1A+
DQogICAgPFAgY2xhc3M9TXNvTm9ybWFsPlBsZWFzZSBmaW5kIGF0dGFjaGVkIG91ciBmaXJzdCBk
cmFmdCBvZiAxNTg4IG92ZXIgTVBMUy4gDQogICAgU2luY2Ugd2UgaGF2ZSBzb21lIHRlY2huaWNh
bCBpc3N1ZXMgY29udmVydGluZyB0aGUgV29yZCBmb3JtYXQgdG8gVHh0IHdlIA0KICAgIGNvdWxk
buKAmXQgJm5ic3A7dXBsb2FkIHRoZSBkcmFmdCBiZWZvcmUgdGhlIGN1dC1vZmYgZGF0ZS4gSG93
ZXZlciB3ZSB3aWxsIA0KICAgIHByZXNlbnQgdGhlIGRyYWZ0IGluIHRoZSBuZXh0IElFVEYgbWVl
dGluZyBhbmQgd2lsbCB1cGxvYWQgdGhlIGRyYWZ0IGFmdGVyIA0KICAgIHRoZSBtZWV0aW5nLjwv
UD4NCiAgICA8UCBjbGFzcz1Nc29Ob3JtYWw+Jm5ic3A7PC9QPg0KICAgIDxQIGNsYXNzPU1zb05v
cm1hbD5Ob3RlIHRoYXQgdGhlIG1haW4gV0cgaXMgVGljVG9jIGJ1dCBtYXkgcmVxdWlyZSANCiAg
ICBjb25zdWx0YXRpb24gd2l0aCBNUExTIGFuZCBQV0UzIFdHcy48L1A+DQogICAgPFAgY2xhc3M9
TXNvTm9ybWFsPiZuYnNwOzwvUD4NCiAgICA8UCBjbGFzcz1Nc29Ob3JtYWw+VGhhbmtzLDwvUD4N
CiAgICA8UCBjbGFzcz1Nc29Ob3JtYWw+U2hhaHJhbSBEYXZhcmk8L1A+PC9ESVY+DQogICAgPFA+
PC9QPg0KICAgIDxIUj4NCg0KICAgIDxQPjwvUD5fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXzxCUj5wd2UzIG1haWxpbmcgDQogICAgbGlzdDxCUj48QSBocmVm
PSJtYWlsdG86cHdlM0BpZXRmLm9yZyIgdGFyZ2V0PV9ibGFuayByZWw9bm9mb2xsb3cgDQogICAg
eW1haWx0bz0ibWFpbHRvOnB3ZTNAaWV0Zi5vcmciPnB3ZTNAaWV0Zi5vcmc8L0E+PEJSPjxBIA0K
ICAgIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHdlMyIgdGFy
Z2V0PV9ibGFuayANCiAgICByZWw9bm9mb2xsb3c+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9wd2UzPC9BPjxCUj48L0JMT0NLUVVPVEU+PC9ESVY+PC9ESVY+DQogIDxESVYg
c3R5bGU9IlBPU0lUSU9OOiBmaXhlZCI+PC9ESVY+PC9ESVY+PEJSPjwvQkxPQ0tRVU9URT48L0JP
RFk+PC9IVE1MPg0K

--Boundary_(ID_Q4723r3ARmAyP+mq2Atcaw)--

From lucyyong@huawei.com  Thu Jul 15 08:09:02 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E777E3A6AA3; Thu, 15 Jul 2010 08:09:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.091
X-Spam-Level: 
X-Spam-Status: No, score=-2.091 tagged_above=-999 required=5 tests=[AWL=0.508,  BAYES_00=-2.599]
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 ouKOqXclVMD5; Thu, 15 Jul 2010 08:09:02 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id EEA173A6A1D; Thu, 15 Jul 2010 08:09:01 -0700 (PDT)
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 <0L5L006M4U38SF@szxga04-in.huawei.com>; Thu, 15 Jul 2010 23:09:08 +0800 (CST)
Received: from 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 <0L5L00I38U38AQ@szxga04-in.huawei.com>; Thu, 15 Jul 2010 23:09:08 +0800 (CST)
Received: from y736742 ([10.124.12.56]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5L00KF3U345U@szxml04-in.huawei.com>; Thu, 15 Jul 2010 23:09:08 +0800 (CST)
Date: Thu, 15 Jul 2010 10:09:04 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <201007141707.o6EH7R2W045708@harbor.orleans.occnc.com>
To: curtis@occnc.com
Message-id: <00bb01cb242f$ac034770$380c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsjdyR2M7rOulnzQ6eqsFmwYj43/QAtYtyw
References: "Your message of Sun, 11 Jul 2010 14:01:44 CDT." <005601cb212b$88c87520$6901a8c0@china.huawei.com> <201007141707.o6EH7R2W045708@harbor.orleans.occnc.com>
Cc: mpls@ietf.org, 'pwe3' <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] FW: New Version Notification for draft-yong-pwe3-lfc-fat-pw-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 15:09:03 -0000

Hi Curtis,

We discussed this in IETF 77. There are quite comments on this. We have sent
out the response to address comments and revise the draft based on the
comments.

The main change on this draft is to move enhanced ECMP section to Appendix
and make draft to focus on large flow classification in flow aware
transport. Appendix just gives one example how large flow classification can
benefit load balance over ECMP. 

IETF is the community to voice different opinions on a subject. We hope that
we can reasonably address different opinions and get the community support
it eventually.

Regards,
Lucy 



> -----Original Message-----
> From: curtis@occnc.com [mailto:curtis@occnc.com]
> Sent: Wednesday, July 14, 2010 12:07 PM
> To: Yong Lucy
> Cc: 'pwe3'; mpls@ietf.org
> Subject: Re: [PWE3] FW: New Version Notification for draft-yong-pwe3-lfc-
> fat-pw-01
> 
> 
> In message <005601cb212b$88c87520$6901a8c0@china.huawei.com>
> Yong Lucy writes:
> >
> > Look forward to hearing your feedbacks on this in Maastricht. -Lucy
> >
> > A new version of I-D, draft-yong-pwe3-lfc-fat-pw-01.txt has been
> > successfully submitted by Lucy Yong and posted to the IETF repository.
> 
> 
> I thought this was presented and soundly rejected at the prior meeting.
> 
> Curtis


From davari@broadcom.com  Thu Jul 15 10:41:32 2010
Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 591CE3A6A98; Thu, 15 Jul 2010 10:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599]
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 gvbYwq4FzO0n; Thu, 15 Jul 2010 10:41:25 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by core3.amsl.com (Postfix) with ESMTP id 412E73A6A36; Thu, 15 Jul 2010 10:41:25 -0700 (PDT)
Received: from [10.16.192.232] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 15 Jul 2010 10:41:27 -0700
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Thu, 15 Jul 2010 10:41:27 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Mach Chen" <mach@huawei.com>, "S. Davari" <davarish@yahoo.com>, "Jia HE" <hejia@huawei.com>
Date: Thu, 15 Jul 2010 10:41:25 -0700
Thread-Topic: [mpls] [PWE3] 1588 over MPLS draft
Thread-Index: AcsjxCM1rOph+74IT5mHQDQF7xAtOQAgKobw
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F3@SJEXCHCCR02.corp.ad.broadcom.com>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c>
In-Reply-To: <6862C24AB1F4468D8F3265AE705925C6@m55527c>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 602197CD10031887566-01-01
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 17:41:32 -0000

SGkgTWFjaCwNCg0KWW91ciBzdWdnZXN0aW9uIGlzIHZhbGlkLiBUaGlzIGNvdWxkIGFsc28gYmUg
ZG9uZSB3aXRob3V0IGFueSBnbG9iYWwgbGFiZWwgcmFuZ2UuIEEgbG9jYWwgbGFiZWwgcmFuZ2Ug
YmV0d2VlbiB0d28gbm9kZXMgd2lsbCBhbHNvIHdvcmsuDQoNClRoeA0KU2hhaHJhbQ0KDQotLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogTWFjaCBDaGVuIFttYWlsdG86bWFjaEBodWF3
ZWkuY29tXSANClNlbnQ6IFdlZG5lc2RheSwgSnVseSAxNCwgMjAxMCA3OjE5IFBNDQpUbzogU2hh
aHJhbSBEYXZhcmk7IFMuIERhdmFyaTsgSmlhIEhFDQpDYzogbXBsc0BpZXRmLm9yZzsgcHdlM0Bp
ZXRmLm9yZzsgdGljY3RvY0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KU3ViamVjdDogUmU6
IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCg0KSGkgU2hhaHJhbSwNCg0KSSBh
Z3JlZSB0aGF0IHRoZSBsYWJlbCByYW5nZSBpZGVhIGlzIGFuIGVmZmljaWVudCB3YXkgdGhhdCBj
b3VsZCByZWR1Y2UgdGhlIA0Kc3RvcmFnZSByZXF1aXJlbWVudCBvZiBQSFkgY2hpcHMuDQoNCkl0
J3MgZWFzeSB0byByZXF1aXJlIG9uZSBvciBsaW1pdGVkIG5vZGVzIHRvIHJlc2VydmUgYSBsYWJl
bCByYW5nZSwgYnV0IA0KSU1ITywgaXQgdmVyeSBkaWZmaWN1dCB0byByZXF1aXJlIGFsbCBub2Rl
cyBvZiBhIGxhcmdlIG5ldHdvcmsgdG8gZG8gdGhpcyANCmFuZCBldmVuIHdvcnNlIHdoZW4gc29t
ZSBsYWJlbHMgYXJlIGFscmVhZHkgdXNlZCBieSBvdGhlciBMU1BzLCB1bmxlc3MgdGhlcmUgDQph
cmUgc29tZSBtZWNoYW5pc21zIHRvIG5lZ290aWF0ZS9hZHZlcnRpc2UoZS5nLiwgZmxvb2Rpbmcg
dGhlIGxhYmVsIHJhbmdlIGJ5IA0KSUdQIHdpdGhpbiB0aGUgbmV0d29yaykgdGhlIHByb3BlciBs
YWJlbCByYW5nZSBoZW5jZSB0byBhdmlvZCBsYWJlbCANCmNvbGxpc2lvbi4NCg0KQmVzdCByZWdh
cmRzLA0KTWFjaA0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KRnJvbTogIlNoYWhyYW0gRGF2YXJpIiA8ZGF2YXJpQGJyb2FkY29tLmNvbT4NClNl
bnQ6IFRodXJzZGF5LCBKdWx5IDE1LCAyMDEwIDE6NTggQU0NClRvOiAiTWFjaCBDaGVuIiA8bWFj
aEBodWF3ZWkuY29tPjsgIlMuIERhdmFyaSIgPGRhdmFyaXNoQHlhaG9vLmNvbT47ICJKaWEgDQpI
RSIgPGhlamlhQGh1YXdlaS5jb20+DQpDYzogPG1wbHNAaWV0Zi5vcmc+OyA8cHdlM0BpZXRmLm9y
Zz47IDx0aWNjdG9jQGlldGYub3JnPjsgPG1wbHMtdHBAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSRTog
W21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KDQo+IEhpIE1hY2gsDQo+DQo+IFdo
ZW4gYSBzZXJ2aWNlIHByb3ZpZGVyIHdhbnRzIHRvIGNyZWF0ZSB0aGVzZSBQVFAgTFNQcywgd2hh
dCBpcyB3cm9uZyB3aXRoIA0KPiBhbGxvY2F0aW5nIGEgcmFuZ2Ugb2YgbGFiZWxzIGZvciB0aGlz
IHB1cnBvc2U/IFRoaXMgaXMgcHVyZWx5IGEgc29mdHdhcmUgDQo+IGV4ZXJjaXNlLiBUaGVyZSBh
cmUgMiBtaWxsaW9uIGxhYmVscyBhdmFpbGFibGUgdG8gZWFjaCBub2RlLCB3aHkgY2FuJ3QgDQo+
IHNvbWUgb2YgdGhlbSBiZSBhbGxvY2F0ZWQgYnkgc29mdHdhcmUgdG8gUFRQPw0KPg0KPiBJbiB0
aGVvcnkgd2hhdCB5b3Ugc2F5IGlzIGNvcnJlY3QgYW5kIHNob3VsZCB3b3JrLCBidXQgaW4gcHJh
Y3RpY2UgdGhlcmUgDQo+IGlzIGEgZnVuY3Rpb24gY2FsbGVkIDEtc3RlcCBUcmFuc3BhcmVudCBj
bG9ja2luZyB0aGF0IHJlcXVpcmVzIHRpbWUgDQo+IHN0YW1waW5nIGF0IHRoZSBQSFkgKGltbWVk
aWF0ZWx5IHdoZW4gdGhlIHBhY2tldCBpcyByZWNlaXZlZCBvciANCj4gdHJhbnNtaXR0ZWQpLiBQ
SFkgY2hpcHMgZG9uJ3QgaGF2ZSBDQU0gb3IgbG90cyBvZiBtZW1vcnkgdG8gc3RvcmUgYSBmZXcg
DQo+IHRob3VzYW5kIHJhbmRvbSBsYWJlbHMuIFRoZSBsYWJlbCByYW5nZSB3aWxsIHNvbHZlIHRo
YXQgcHJvYmxlbSBhbmQgaXMgDQo+IGNvbnNpc3RlbnQgd2l0aCBNUExTIGFyY2hpdGVjdHVyZS4N
Cj4NCj4gVGhhbmtzLA0KPiBTaGFocmFtDQo+DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQo+IEZyb206IE1hY2ggQ2hlbiBbbWFpbHRvOm1hY2hAaHVhd2VpLmNvbV0NCj4gU2VudDogV2Vk
bmVzZGF5LCBKdWx5IDE0LCAyMDEwIDE6NTMgQU0NCj4gVG86IFMuIERhdmFyaTsgSmlhIEhFOyBT
aGFocmFtIERhdmFyaQ0KPiBDYzogbXBsc0BpZXRmLm9yZzsgcHdlM0BpZXRmLm9yZzsgdGljY3Rv
Y0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW21wbHNdIFtQV0Uz
XSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPg0KPiBIaSBTaGFocmFtLA0KPg0KPiBGcm9tIHRoZSB2
aWV3IG9mIGltcGxlbWVudGF0aW9uLCB0aGVyZSBpcyBubyBtb3JlIGRpZmZlcmVuY2UgYmV0d2Vl
biANCj4gU0hPVUxEDQo+IGFuZCBNVVNUIDotKQ0KPiBGb3IgbWUsIHRoZSBMYWJlbCBSYW5nZSBp
cyBtb3JlIGxpa2UgYSBtZWNoYW5pbSB0byBub3RpZnkgcmVsYXRlZCBub2RlcyANCj4gdGhhdA0K
PiBzb21lIExTUHMgYXJlIGRlZGljYXRlZCBmb3IgUFRQIG1lc3NhZ2VzIG90aGVyIHRoYW4gdGhl
IGNoaXBzIG1lbW9yeQ0KPiBsaW1pdGF0aW9uLCBiZWNhdXNlIHRoZSBtZW1vcnkgcmVzdHJpY3Rp
b24gaXMgYWx3YXlzIHRoZXJlIHdoYXRldmVyIHlvdSANCj4gdXNlDQo+IExhYmVsIFJhbmdlIG9y
IG5vdC4NCj4gSU1ITywgc2luY2UgdGhlIG9iamVjdGl2ZSBpcyB0byB0ZWxsIHJlbGF0ZWQgTVBM
UyBub2RlcyB3aGljaCBMU1BzIGFyZSBQVFANCj4gTFNQcywgYW4gaW5kaWNhdGlvbiBpbiB0aGUg
c2lnbmFsaW5nKFJTVlAtVEUvR01QTFMvTERQKSBpcyBlbm91Z2ggYW5kIA0KPiBzZWVtcw0KPiBt
b3JlIGNvbW1vbi4gQW5kIGl0IHdpbGwgYXZvaWQgdGhlIHN0cmljdCByZXF1aXJlbWVudCBvZiAi
dGhlIG5ldHdvcmsgYW5kDQo+IGFsbCBub2RlcyByZXF1aXJlZCB0byBzdXBwb3J0IHRoZSBMYWJl
bCByYW5nZSIuDQo+IEluIGFkZGl0aW9uLCB0aGVyZSBzaG91bGQgYmUgc29tZSBtZWNoYW5pbXMo
ZS5nLiwgSVNJUy9PU1BGIGV4dGVuc2lvbnMpIA0KPiBmb3INCj4gbm9kZXMgdG8gYWR2ZXJ0aXNl
IHRoZWlyIFBUUCBjYXBhYmlsaXR5IGhlbmNlIHRvIGhlbHAgUFRQIExTUHMgDQo+IGNvbXB1dGF0
aW9uLg0KPg0KPiBCZXN0IHJlZ2FyZHMsDQo+IE1hY2gNCj4NCj4NCj4gLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gRnJvbTogIlMuIERhdmFyaSIg
PGRhdmFyaXNoQHlhaG9vLmNvbT4NCj4gU2VudDogV2VkbmVzZGF5LCBKdWx5IDE0LCAyMDEwIDI6
MzEgUE0NCj4gVG86ICJKaWEgSEUiIDxoZWppYUBodWF3ZWkuY29tPjsgIlNoYWhyYW0gRGF2YXJp
IiA8ZGF2YXJpQGJyb2FkY29tLmNvbT4NCj4gQ2M6IDxtcGxzQGlldGYub3JnPjsgPHB3ZTNAaWV0
Zi5vcmc+OyA8dGljY3RvY0BpZXRmLm9yZz47IA0KPiA8bXBscy10cEBpZXRmLm9yZz4NCj4gU3Vi
amVjdDogUmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCj4NCj4+IEhpIEpp
YSwNCj4+DQo+PiBMYWJlbCByYW5nZSBpcyBhIFNIT1VMRCByZXF1aXJlbWVudHMgYW5kIG5vdCBN
VVNULiBUaGUgcmVhc29uIGZvciBMYWJlbA0KPj4gUmFuZ2UgaXMNCj4+IG1haW5seSBmb3IgUEhZ
IGNoaXBzIHRoYXQgZG9uJ3QgaGF2ZSBsYXJnZSBtZW1vcnkgYW5kIGNhbid0IHN0b3JlIGEgbG90
IA0KPj4gb2YNCj4+IExhYmVscy4gT3RoZXJ3aXNlIHRoZSBQVFAgTFNQIGlzIHNldHVwIHZpYSBz
aWduYWxpbmcgdGhhdCBzcGVjaWZpZXMgdGhlDQo+PiBMU1AgYXMNCj4+IGNhcnJ5aW5nIDE1ODgu
DQo+Pg0KPj4gU28gdGhlIGFuc3dlciBpcyB0aGF0IGlmIGEgTGFiZWwgcmFuZ2UgaXMgdXNlZCBp
dCBtdXN0IGJlIGEgR2xvYmFsIHJhbmdlDQo+PiB3aXRoaW4NCj4+IGEgbmV0d29yayBhbmQgc2hv
dWxkIG5vdCBiZSB1c2VkIGJ5IGFueSByb3V0ZXIgZm9yIG90aGVyIGFwcGxpY2F0aW9ucy4NCj4+
DQo+PiBUaGFua3MsDQo+PiBTaGFocmFtDQo+Pg0KPj4NCj4+DQo+PiBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KPj4gRnJvbTogSmlhIEhFIDxoZWppYUBodWF3ZWkuY29tPg0KPj4g
VG86IFNoYWhyYW0gRGF2YXJpIDxkYXZhcmlAYnJvYWRjb20uY29tPg0KPj4gQ2M6IG1wbHNAaWV0
Zi5vcmc7IHB3ZTNAaWV0Zi5vcmc7IHRpY2N0b2NAaWV0Zi5vcmc7IG1wbHMtdHBAaWV0Zi5vcmcN
Cj4+IFNlbnQ6IFR1ZSwgSnVseSAxMywgMjAxMCA5OjUwOjM3IFBNDQo+PiBTdWJqZWN0OiBSZTog
W21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPj4NCj4+DQo+PiBIaSBTaGFocmFt
LA0KPj4NCj4+IE9uZSBxdWVzdGlvbiBhYm91dCAiUFRQIExhYmVsIFJhbmdlIjoNCj4+DQo+PiBU
byBteSBrbm93bGVkZ2UsIGxhYmVsIGluIE1QTFMgbmV0d29yayBpcyBhIGxvY2FsICBtYXR0ZXIu
IEZvciBleGFtcGxlLCANCj4+IHdlDQo+PiBtYXkNCj4+IGhhdmUgcGVyLWludGVyZmFjZSBvciBw
ZXItcGxhdGZvcm0gbGFiZWwgc3BhY2UuIFdpbGwgIHRoaXMgc3BlY2lmaWNlZCANCj4+ICJQVFAN
Cj4+IExhYmVsDQo+PiBSYW5nZSIgY29uZmxpY3Qgd2l0aCB0aGUgY3VycmVudCBpbi11c2UgbGFi
ZWxzICBmb3IgY29tbW9uIExTUHM/DQo+Pg0KPj4NCj4+IEIuUi4NCj4+IEppYQ0KPj4NCj4+IC0t
LS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQo+Pj5Gcm9tOiBTaGFocmFtICAgIERhdmFyaQ0K
Pj4+VG86IHRpY2N0b2NAaWV0Zi5vcmcgOyBtcGxzQGlldGYub3JnIDsgbXBscy10cEBpZXRmLm9y
ZyA7IHB3ZTNAaWV0Zi5vcmcNCj4+PlNlbnQ6IFRodXJzZGF5LCBKdWx5IDA4LCAyMDEwIDM6MTIg
QU0NCj4+PlN1YmplY3Q6IFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPj4+DQo+Pj4NCj4+
PkhpIEFsbCwNCj4+Pg0KPj4+UGxlYXNlIGZpbmQgYXR0YWNoZWQgb3VyIGZpcnN0IGRyYWZ0IG9m
IDE1ODggb3ZlciBNUExTLiAgICBTaW5jZSB3ZSBoYXZlDQo+Pj5zb21lDQo+Pj50ZWNobmljYWwg
aXNzdWVzIGNvbnZlcnRpbmcgdGhlIFdvcmQgZm9ybWF0IHRvIFR4dCB3ZSAgICBjb3VsZG7igJl0
IA0KPj4+dXBsb2FkDQo+Pj50aGUNCj4+PmRyYWZ0IGJlZm9yZSB0aGUgY3V0LW9mZiBkYXRlLiBI
b3dldmVyIHdlIHdpbGwgICAgcHJlc2VudCB0aGUgZHJhZnQgaW4gDQo+Pj50aGUNCj4+Pm5leHQN
Cj4+PklFVEYgbWVldGluZyBhbmQgd2lsbCB1cGxvYWQgdGhlIGRyYWZ0IGFmdGVyIHRoZSAgICBt
ZWV0aW5nLg0KPj4+DQo+Pj5Ob3RlIHRoYXQgdGhlIG1haW4gV0cgaXMgVGljVG9jIGJ1dCBtYXkg
cmVxdWlyZSAgICBjb25zdWx0YXRpb24gd2l0aCBNUExTDQo+Pj5hbmQNCj4+PlBXRTMgV0dzLg0K
Pj4+DQo+Pj5UaGFua3MsDQo+Pj5TaGFocmFtIERhdmFyaQ0KPj4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+Pj5wd2UzIG1haWxpbmcgICAgbGlzdA0KPj4+cHdlM0BpZXRmLm9yZw0KPj4+
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wd2UzDQo+Pj4NCj4+DQo+Pg0K
Pg0KPg0KPg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4+IG1wbHMgbWFpbGluZyBsaXN0DQo+PiBtcGxzQGlldGYub3JnDQo+PiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMNCj4+DQo+DQo+DQo+IA0KDQoNCg==


From davari@broadcom.com  Thu Jul 15 10:46:29 2010
Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F22AE3A6A70; Thu, 15 Jul 2010 10:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level: 
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599]
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 Uufgzw01TDxY; Thu, 15 Jul 2010 10:46:27 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by core3.amsl.com (Postfix) with ESMTP id 5CBC83A6AB4; Thu, 15 Jul 2010 10:46:26 -0700 (PDT)
Received: from [10.16.192.224] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 15 Jul 2010 10:46:24 -0700
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Thu, 15 Jul 2010 10:46:24 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "Mach Chen" <mach@huawei.com>
Date: Thu, 15 Jul 2010 10:46:22 -0700
Thread-Topic: [mpls] [PWE3] 1588 over MPLS draft
Thread-Index: AcsjzL+tuZ17f0tmSyC7yLZ0piwa1wAeDfPg
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c> <4C3E7E83.9080603@joelhalpern.com>
In-Reply-To: <4C3E7E83.9080603@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 602196FA10031891565-01-01
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 17:46:29 -0000

SGkgSm9lbCwNCg0KSSBhZ3JlZSB3aXRoIHlvdXIgbG9naWMsIGJ1dCB0aGUgaWRlYSBpcyBhIGJp
dCBkaWZmZXJlbnQ6DQoNCkFsbCB3ZSBuZWVkIGlzIGEgbGFiZWwgcmFuZ2UsIGl0IGRvZXMgbm90
IG5lZWQgdG8gYmUgZ2xvYmFsbHkgdW5pcXVlIGluIHRoZSBuZXR3b3JrIGFuZCBpdCBkb2VzIG5v
dCBldmVuIG5lZWQgdG8gYmUgdGhlIHNhbWUgb24gdGhlIFR4IGFuZCBSeCBkaXJlY3Rpb24gb2Yg
dGhlIHNhbWUgbGluay4gQWx0aG91Z2ggd2UgbmVlZCB0aW1lIHN0YW1waW5nIGJvdGggb24gUngg
YW5kIG9uIFR4LCBidXQgb24gUnggYSBub2RlIGlzIGluIGNvbnRyb2wgb2YgaXRzIG93biBsYWJl
bCBhbmQgb24gVHggdGhlIGRvd25zdHJlYW0gbm9kZSBzaG91bGQgYWR2ZXJ0aXNlIHNvbWUgbGFi
ZWwgcmFuZ2UuIFdoYXQgd2UgZG9uJ3Qgd2FudCBpcyB0aGF0IHRoZSBkb3duc3RyZWFtIG5vZGUg
dG8gYWR2ZXJ0aXNlIHJhbmRvbSBsYWJlbHMgZm9yIGVhY2ggTFNQIGNhcnJ5aW5nIFBUUC4NCg0K
SSB3aWxsIHVwZGF0ZSB0aGUgZHJhZnQgdG8gbWVudGlvbiB0aGF0IHRoZSBsYWJlbCByYW5nZSBk
b2VzIG5vdCByZXF1aXJlIHRvIGJlIGdsb2JhbCBidXQgaXQgY2FuIGJlIHBlci1wbGF0Zm9ybSBv
ciBldmVuIHBlci1pbnRlcmZhY2UuDQoNClRoYW5rcywNClNoYWhyYW0NCg0KLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCkZyb206IEpvZWwgTS4gSGFscGVybiBbbWFpbHRvOmptaEBqb2VsaGFs
cGVybi5jb21dIA0KU2VudDogV2VkbmVzZGF5LCBKdWx5IDE0LCAyMDEwIDg6MjEgUE0NClRvOiBN
YWNoIENoZW4NCkNjOiBTaGFocmFtIERhdmFyaTsgUy4gRGF2YXJpOyBKaWEgSEU7IG1wbHNAaWV0
Zi5vcmc7IHB3ZTNAaWV0Zi5vcmc7IHRpY2N0b2NAaWV0Zi5vcmc7IG1wbHMtdHBAaWV0Zi5vcmcN
ClN1YmplY3Q6IFJlOiBbbXBsc10gW1BXRTNdIDE1ODggb3ZlciBNUExTIGRyYWZ0DQoNClJlbWVt
YmVyIHRoYXQgaWYgd2hhdCBpcyByZXF1aXJlZCBpcyB0aGF0IHRoZSBtZXNzYWdlIGFycml2aW5n
IGF0IHRoZSANCjE1ODggc3VwcG9ydGluZyBkZXZpY2UgaGF2ZSBhIGNlcnRhaW4gbGFiZWwgcmFu
Z2UsIHRoYXQgaXMgYSBwdXJlbHkgDQpsb2NhbCBtYXR0ZXIuICBBcyBsb25nIGFzIHRoZSBzaW5n
YWxpbmcgY2FycmllcyB0aGUgaW5kaWNhdGlvbiB0aGF0IHRoZSANCkxTUCBpcyB0byBiZSBkZWRp
Y2F0ZWQgdG8gMTU4OCB0cmFmZmljIChhIHJlYXNvbmFibGUgZXh0ZW5zaW9uIHRvIHRoZSANCnNp
Z25hbGluZyksIHRoZSBkb3duc3RyZWFtIHN3aXRjaCBjYW4gcGljayB3aGF0IGxhYmVsIHRvIGFz
c2lnbiB0byB0aGF0IExTUC4NCg0KSWYgdGhlIGdvYWwgaXMgdG8gaGF2ZSB0aGUgb3V0Z29pbmcg
bGFiZWwgYmUgZnJvbSBhIHNwZWNpZmljIHJhbmdlLCB0aGF0IA0KaXMgZXNzZW50aWFsbHkgaW1w
b3NzaWJsZSBpbiB0aGUgcHJvcG9zZWQgYXJjaGl0ZWN0dXJlLiAgVGhlIHByb3Bvc2VkIA0KYXJj
aGl0ZWN0dXJlIGlzIG9uZSBpbiB3aGljaCAxNTg4IHN3aXRjaGVzIGFyZSBwZWVycyB3aXRoIGV4
aXN0aW5nIExTUnMgDQp1c2luZyBNUExTLiAgQXMgc3VjaCwgaW4gb3JkZXIgdG8gaGF2ZSBhIGxh
YmVsIHJhbmdlIGZvciBvdXRnb2luZyANCmxhYmVscywgdGhlIGV4aXN0aW5nIE1QTFMgTFNSIHdv
dWxkIHNvbWVob3cgaGF2ZSB0byBrbm93IGFib3V0IHRoaXMgDQpyZXNlcnZlZCBsYWJlbCByYW5n
ZSwgbm90IHVzZSB0aG9zZSBsYWJlbHMgZm9yIG90aGVyIHB1cnBvc2VzLCBhbmQgDQphc3NpZ24g
dGhvc2UgbGFiZWxzIHRvIDE1ODggTFNQcy4gIEFsbCBvZiB3aGljaCBpcyANCm5vbi1iYWNrd2Fy
ZHMtY29tcGF0aWJsZS4gIElmIHRoZSAxNTg4IExTUHMgd2VyZSBhY3R1YWxseSBwc2V1ZG93aXJl
cywgDQp0dW5uZWxlZCBvdmVyIExTUHMsIHRoZW4gYW55IG51bWJlciBvZiB0aGluZ3MgYXJlIHBv
c3NpYmxlLg0KDQpZb3VycywNCkpvZWwgTS4gSGFscGVybg0KDQpNYWNoIENoZW4gd3JvdGU6DQo+
IEhpIFNoYWhyYW0sDQo+IA0KPiBJIGFncmVlIHRoYXQgdGhlIGxhYmVsIHJhbmdlIGlkZWEgaXMg
YW4gZWZmaWNpZW50IHdheSB0aGF0IGNvdWxkIHJlZHVjZSANCj4gdGhlIHN0b3JhZ2UgcmVxdWly
ZW1lbnQgb2YgUEhZIGNoaXBzLg0KPiANCj4gSXQncyBlYXN5IHRvIHJlcXVpcmUgb25lIG9yIGxp
bWl0ZWQgbm9kZXMgdG8gcmVzZXJ2ZSBhIGxhYmVsIHJhbmdlLCBidXQgDQo+IElNSE8sIGl0IHZl
cnkgZGlmZmljdXQgdG8gcmVxdWlyZSBhbGwgbm9kZXMgb2YgYSBsYXJnZSBuZXR3b3JrIHRvIGRv
IA0KPiB0aGlzIGFuZCBldmVuIHdvcnNlIHdoZW4gc29tZSBsYWJlbHMgYXJlIGFscmVhZHkgdXNl
ZCBieSBvdGhlciBMU1BzLCANCj4gdW5sZXNzIHRoZXJlIGFyZSBzb21lIG1lY2hhbmlzbXMgdG8g
bmVnb3RpYXRlL2FkdmVydGlzZShlLmcuLCBmbG9vZGluZyANCj4gdGhlIGxhYmVsIHJhbmdlIGJ5
IElHUCB3aXRoaW4gdGhlIG5ldHdvcmspIHRoZSBwcm9wZXIgbGFiZWwgcmFuZ2UgaGVuY2UgDQo+
IHRvIGF2aW9kIGxhYmVsIGNvbGxpc2lvbi4NCj4gDQo+IEJlc3QgcmVnYXJkcywNCj4gTWFjaA0K
PiANCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N
Cj4gRnJvbTogIlNoYWhyYW0gRGF2YXJpIiA8ZGF2YXJpQGJyb2FkY29tLmNvbT4NCj4gU2VudDog
VGh1cnNkYXksIEp1bHkgMTUsIDIwMTAgMTo1OCBBTQ0KPiBUbzogIk1hY2ggQ2hlbiIgPG1hY2hA
aHVhd2VpLmNvbT47ICJTLiBEYXZhcmkiIDxkYXZhcmlzaEB5YWhvby5jb20+OyANCj4gIkppYSBI
RSIgPGhlamlhQGh1YXdlaS5jb20+DQo+IENjOiA8bXBsc0BpZXRmLm9yZz47IDxwd2UzQGlldGYu
b3JnPjsgPHRpY2N0b2NAaWV0Zi5vcmc+OyANCj4gPG1wbHMtdHBAaWV0Zi5vcmc+DQo+IFN1Ympl
Y3Q6IFJFOiBbbXBsc10gW1BXRTNdIDE1ODggb3ZlciBNUExTIGRyYWZ0DQo+IA0KPj4gSGkgTWFj
aCwNCj4+DQo+PiBXaGVuIGEgc2VydmljZSBwcm92aWRlciB3YW50cyB0byBjcmVhdGUgdGhlc2Ug
UFRQIExTUHMsIHdoYXQgaXMgd3JvbmcgDQo+PiB3aXRoIGFsbG9jYXRpbmcgYSByYW5nZSBvZiBs
YWJlbHMgZm9yIHRoaXMgcHVycG9zZT8gVGhpcyBpcyBwdXJlbHkgYSANCj4+IHNvZnR3YXJlIGV4
ZXJjaXNlLiBUaGVyZSBhcmUgMiBtaWxsaW9uIGxhYmVscyBhdmFpbGFibGUgdG8gZWFjaCBub2Rl
LCANCj4+IHdoeSBjYW4ndCBzb21lIG9mIHRoZW0gYmUgYWxsb2NhdGVkIGJ5IHNvZnR3YXJlIHRv
IFBUUD8NCj4+DQo+PiBJbiB0aGVvcnkgd2hhdCB5b3Ugc2F5IGlzIGNvcnJlY3QgYW5kIHNob3Vs
ZCB3b3JrLCBidXQgaW4gcHJhY3RpY2UgDQo+PiB0aGVyZSBpcyBhIGZ1bmN0aW9uIGNhbGxlZCAx
LXN0ZXAgVHJhbnNwYXJlbnQgY2xvY2tpbmcgdGhhdCByZXF1aXJlcyANCj4+IHRpbWUgc3RhbXBp
bmcgYXQgdGhlIFBIWSAoaW1tZWRpYXRlbHkgd2hlbiB0aGUgcGFja2V0IGlzIHJlY2VpdmVkIG9y
IA0KPj4gdHJhbnNtaXR0ZWQpLiBQSFkgY2hpcHMgZG9uJ3QgaGF2ZSBDQU0gb3IgbG90cyBvZiBt
ZW1vcnkgdG8gc3RvcmUgYSANCj4+IGZldyB0aG91c2FuZCByYW5kb20gbGFiZWxzLiBUaGUgbGFi
ZWwgcmFuZ2Ugd2lsbCBzb2x2ZSB0aGF0IHByb2JsZW0gDQo+PiBhbmQgaXMgY29uc2lzdGVudCB3
aXRoIE1QTFMgYXJjaGl0ZWN0dXJlLg0KPj4NCj4+IFRoYW5rcywNCj4+IFNoYWhyYW0NCj4+DQo+
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4gRnJvbTogTWFjaCBDaGVuIFttYWlsdG86
bWFjaEBodWF3ZWkuY29tXQ0KPj4gU2VudDogV2VkbmVzZGF5LCBKdWx5IDE0LCAyMDEwIDE6NTMg
QU0NCj4+IFRvOiBTLiBEYXZhcmk7IEppYSBIRTsgU2hhaHJhbSBEYXZhcmkNCj4+IENjOiBtcGxz
QGlldGYub3JnOyBwd2UzQGlldGYub3JnOyB0aWNjdG9jQGlldGYub3JnOyBtcGxzLXRwQGlldGYu
b3JnDQo+PiBTdWJqZWN0OiBSZTogW21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0K
Pj4NCj4+IEhpIFNoYWhyYW0sDQo+Pg0KPj4gRnJvbSB0aGUgdmlldyBvZiBpbXBsZW1lbnRhdGlv
biwgdGhlcmUgaXMgbm8gbW9yZSBkaWZmZXJlbmNlIGJldHdlZW4gDQo+PiBTSE9VTEQNCj4+IGFu
ZCBNVVNUIDotKQ0KPj4gRm9yIG1lLCB0aGUgTGFiZWwgUmFuZ2UgaXMgbW9yZSBsaWtlIGEgbWVj
aGFuaW0gdG8gbm90aWZ5IHJlbGF0ZWQgDQo+PiBub2RlcyB0aGF0DQo+PiBzb21lIExTUHMgYXJl
IGRlZGljYXRlZCBmb3IgUFRQIG1lc3NhZ2VzIG90aGVyIHRoYW4gdGhlIGNoaXBzIG1lbW9yeQ0K
Pj4gbGltaXRhdGlvbiwgYmVjYXVzZSB0aGUgbWVtb3J5IHJlc3RyaWN0aW9uIGlzIGFsd2F5cyB0
aGVyZSB3aGF0ZXZlciANCj4+IHlvdSB1c2UNCj4+IExhYmVsIFJhbmdlIG9yIG5vdC4NCj4+IElN
SE8sIHNpbmNlIHRoZSBvYmplY3RpdmUgaXMgdG8gdGVsbCByZWxhdGVkIE1QTFMgbm9kZXMgd2hp
Y2ggTFNQcyBhcmUgDQo+PiBQVFANCj4+IExTUHMsIGFuIGluZGljYXRpb24gaW4gdGhlIHNpZ25h
bGluZyhSU1ZQLVRFL0dNUExTL0xEUCkgaXMgZW5vdWdoIGFuZCANCj4+IHNlZW1zDQo+PiBtb3Jl
IGNvbW1vbi4gQW5kIGl0IHdpbGwgYXZvaWQgdGhlIHN0cmljdCByZXF1aXJlbWVudCBvZiAidGhl
IG5ldHdvcmsgYW5kDQo+PiBhbGwgbm9kZXMgcmVxdWlyZWQgdG8gc3VwcG9ydCB0aGUgTGFiZWwg
cmFuZ2UiLg0KPj4gSW4gYWRkaXRpb24sIHRoZXJlIHNob3VsZCBiZSBzb21lIG1lY2hhbmltcyhl
LmcuLCBJU0lTL09TUEYgDQo+PiBleHRlbnNpb25zKSBmb3INCj4+IG5vZGVzIHRvIGFkdmVydGlz
ZSB0aGVpciBQVFAgY2FwYWJpbGl0eSBoZW5jZSB0byBoZWxwIFBUUCBMU1BzIA0KPj4gY29tcHV0
YXRpb24uDQo+Pg0KPj4gQmVzdCByZWdhcmRzLA0KPj4gTWFjaA0KPj4NCj4+DQo+PiAtLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPj4gRnJvbTogIlMu
IERhdmFyaSIgPGRhdmFyaXNoQHlhaG9vLmNvbT4NCj4+IFNlbnQ6IFdlZG5lc2RheSwgSnVseSAx
NCwgMjAxMCAyOjMxIFBNDQo+PiBUbzogIkppYSBIRSIgPGhlamlhQGh1YXdlaS5jb20+OyAiU2hh
aHJhbSBEYXZhcmkiIDxkYXZhcmlAYnJvYWRjb20uY29tPg0KPj4gQ2M6IDxtcGxzQGlldGYub3Jn
PjsgPHB3ZTNAaWV0Zi5vcmc+OyA8dGljY3RvY0BpZXRmLm9yZz47IA0KPj4gPG1wbHMtdHBAaWV0
Zi5vcmc+DQo+PiBTdWJqZWN0OiBSZTogW21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFm
dA0KPj4NCj4+PiBIaSBKaWEsDQo+Pj4NCj4+PiBMYWJlbCByYW5nZSBpcyBhIFNIT1VMRCByZXF1
aXJlbWVudHMgYW5kIG5vdCBNVVNULiBUaGUgcmVhc29uIGZvciBMYWJlbA0KPj4+IFJhbmdlIGlz
DQo+Pj4gbWFpbmx5IGZvciBQSFkgY2hpcHMgdGhhdCBkb24ndCBoYXZlIGxhcmdlIG1lbW9yeSBh
bmQgY2FuJ3Qgc3RvcmUgYSANCj4+PiBsb3Qgb2YNCj4+PiBMYWJlbHMuIE90aGVyd2lzZSB0aGUg
UFRQIExTUCBpcyBzZXR1cCB2aWEgc2lnbmFsaW5nIHRoYXQgc3BlY2lmaWVzIHRoZQ0KPj4+IExT
UCBhcw0KPj4+IGNhcnJ5aW5nIDE1ODguDQo+Pj4NCj4+PiBTbyB0aGUgYW5zd2VyIGlzIHRoYXQg
aWYgYSBMYWJlbCByYW5nZSBpcyB1c2VkIGl0IG11c3QgYmUgYSBHbG9iYWwgcmFuZ2UNCj4+PiB3
aXRoaW4NCj4+PiBhIG5ldHdvcmsgYW5kIHNob3VsZCBub3QgYmUgdXNlZCBieSBhbnkgcm91dGVy
IGZvciBvdGhlciBhcHBsaWNhdGlvbnMuDQo+Pj4NCj4+PiBUaGFua3MsDQo+Pj4gU2hhaHJhbQ0K
Pj4+DQo+Pj4NCj4+Pg0KPj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4g
RnJvbTogSmlhIEhFIDxoZWppYUBodWF3ZWkuY29tPg0KPj4+IFRvOiBTaGFocmFtIERhdmFyaSA8
ZGF2YXJpQGJyb2FkY29tLmNvbT4NCj4+PiBDYzogbXBsc0BpZXRmLm9yZzsgcHdlM0BpZXRmLm9y
ZzsgdGljY3RvY0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KPj4+IFNlbnQ6IFR1ZSwgSnVs
eSAxMywgMjAxMCA5OjUwOjM3IFBNDQo+Pj4gU3ViamVjdDogUmU6IFttcGxzXSBbUFdFM10gMTU4
OCBvdmVyIE1QTFMgZHJhZnQNCj4+Pg0KPj4+DQo+Pj4gSGkgU2hhaHJhbSwNCj4+Pg0KPj4+IE9u
ZSBxdWVzdGlvbiBhYm91dCAiUFRQIExhYmVsIFJhbmdlIjoNCj4+Pg0KPj4+IFRvIG15IGtub3ds
ZWRnZSwgbGFiZWwgaW4gTVBMUyBuZXR3b3JrIGlzIGEgbG9jYWwgIG1hdHRlci4gRm9yIA0KPj4+
IGV4YW1wbGUsIHdlDQo+Pj4gbWF5DQo+Pj4gaGF2ZSBwZXItaW50ZXJmYWNlIG9yIHBlci1wbGF0
Zm9ybSBsYWJlbCBzcGFjZS4gV2lsbCAgdGhpcyBzcGVjaWZpY2VkIA0KPj4+ICJQVFANCj4+PiBM
YWJlbA0KPj4+IFJhbmdlIiBjb25mbGljdCB3aXRoIHRoZSBjdXJyZW50IGluLXVzZSBsYWJlbHMg
IGZvciBjb21tb24gTFNQcz8NCj4+Pg0KPj4+DQo+Pj4gQi5SLg0KPj4+IEppYQ0KPj4+DQo+Pj4g
LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KPj4+PiBGcm9tOiBTaGFocmFtICAgIERhdmFy
aQ0KPj4+PiBUbzogdGljY3RvY0BpZXRmLm9yZyA7IG1wbHNAaWV0Zi5vcmcgOyBtcGxzLXRwQGll
dGYub3JnIDsgcHdlM0BpZXRmLm9yZw0KPj4+PiBTZW50OiBUaHVyc2RheSwgSnVseSAwOCwgMjAx
MCAzOjEyIEFNDQo+Pj4+IFN1YmplY3Q6IFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPj4+
Pg0KPj4+Pg0KPj4+PiBIaSBBbGwsDQo+Pj4+DQo+Pj4+IFBsZWFzZSBmaW5kIGF0dGFjaGVkIG91
ciBmaXJzdCBkcmFmdCBvZiAxNTg4IG92ZXIgTVBMUy4gICAgU2luY2Ugd2UgDQo+Pj4+IGhhdmUN
Cj4+Pj4gc29tZQ0KPj4+PiB0ZWNobmljYWwgaXNzdWVzIGNvbnZlcnRpbmcgdGhlIFdvcmQgZm9y
bWF0IHRvIFR4dCB3ZSAgICBjb3VsZG7igJl0IA0KPj4+PiB1cGxvYWQNCj4+Pj4gdGhlDQo+Pj4+
IGRyYWZ0IGJlZm9yZSB0aGUgY3V0LW9mZiBkYXRlLiBIb3dldmVyIHdlIHdpbGwgICAgcHJlc2Vu
dCB0aGUgZHJhZnQgDQo+Pj4+IGluIHRoZQ0KPj4+PiBuZXh0DQo+Pj4+IElFVEYgbWVldGluZyBh
bmQgd2lsbCB1cGxvYWQgdGhlIGRyYWZ0IGFmdGVyIHRoZSAgICBtZWV0aW5nLg0KPj4+Pg0KPj4+
PiBOb3RlIHRoYXQgdGhlIG1haW4gV0cgaXMgVGljVG9jIGJ1dCBtYXkgcmVxdWlyZSAgICBjb25z
dWx0YXRpb24gd2l0aCANCj4+Pj4gTVBMUw0KPj4+PiBhbmQNCj4+Pj4gUFdFMyBXR3MuDQo+Pj4+
DQo+Pj4+IFRoYW5rcywNCj4+Pj4gU2hhaHJhbSBEYXZhcmkNCj4+PiBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KPj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+Pj4+IHB3ZTMgbWFpbGluZyAgICBsaXN0DQo+Pj4+IHB3ZTNAaWV0Zi5v
cmcNCj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wd2UzDQo+Pj4+
DQo+Pj4NCj4+Pg0KPj4NCj4+DQo+Pg0KPj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+Pj4gbXBscyBtYWlsaW5nIGxpc3QNCj4+PiBtcGxzQGlldGYu
b3JnDQo+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQo+Pj4N
Cj4+DQo+Pg0KPj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4gbXBscyBtYWlsaW5nIGxpc3QNCj4gbXBsc0BpZXRmLm9yZw0KPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMNCg0K


From jmh@joelhalpern.com  Thu Jul 15 12:06:13 2010
Return-Path: <jmh@joelhalpern.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 800A13A6AA5; Thu, 15 Jul 2010 12:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599]
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 pFCXiMT-7b2J; Thu, 15 Jul 2010 12:06:12 -0700 (PDT)
Received: from hgblob.mail.tigertech.net (hgblob.mail.tigertech.net [64.62.209.71]) by core3.amsl.com (Postfix) with ESMTP id 298C03A6971; Thu, 15 Jul 2010 12:06:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 9D74732365DE; Thu, 15 Jul 2010 12:06:19 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-61.clppva.btas.verizon.net [71.161.50.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id B5AC632365DA; Thu, 15 Jul 2010 12:06:17 -0700 (PDT)
Message-ID: <4C3F5C24.4070505@joelhalpern.com>
Date: Thu, 15 Jul 2010 15:06:12 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Shahram Davari <davari@broadcom.com>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c> <4C3E7E83.9080603@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 19:06:13 -0000

Architecturally, as I understand the draft, the downstream neighbor of a 
1588 supporting device (on the PTP carrying LSP) may not itself be a 
1588 supporting device.  Is that correct?  If that is not correct, if 
instead the structure is that PTP supporting LSPs are established 
between adjacent enhanced devices, then I can see how some sort of a 
label range might make sense.

If however, the downstream node you refer to may be an existing LSR, 
then I do not see how you can ask an existing LSR to allocate a label 
range for a function it does not understand.

Yours,
Joel

Shahram Davari wrote:
> Hi Joel,
> 
> I agree with your logic, but the idea is a bit different:
> 
> All we need is a label range, it does not need to be globally unique in the network and it does
 >not even need to be the same on the Tx and Rx direction of the same 
link. Although we need time
 >stamping both on Rx and on Tx, but on Rx a node is in control of its 
own label and on Tx the
 >downstream node should advertise some label range. What we don't want 
is that the downstream
 >node to advertise random labels for each LSP carrying PTP.
> 
> I will update the draft to mention that the label range does not require to be global but it can
 >be per-platform or even per-interface.
> 
> Thanks,
> Shahram
> 
> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 
> Sent: Wednesday, July 14, 2010 8:21 PM
> To: Mach Chen
> Cc: Shahram Davari; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> 
> Remember that if what is required is that the message arriving at the 
> 1588 supporting device have a certain label range, that is a purely 
> local matter.  As long as the singaling carries the indication that the 
> LSP is to be dedicated to 1588 traffic (a reasonable extension to the 
> signaling), the downstream switch can pick what label to assign to that LSP.
> 
> If the goal is to have the outgoing label be from a specific range, that 
> is essentially impossible in the proposed architecture.  The proposed 
> architecture is one in which 1588 switches are peers with existing LSRs 
> using MPLS.  As such, in order to have a label range for outgoing 
> labels, the existing MPLS LSR would somehow have to know about this 
> reserved label range, not use those labels for other purposes, and 
> assign those labels to 1588 LSPs.  All of which is 
> non-backwards-compatible.  If the 1588 LSPs were actually pseudowires, 
> tunneled over LSPs, then any number of things are possible.
> 
> Yours,
> Joel M. Halpern
> 
> Mach Chen wrote:
>> Hi Shahram,
>>
>> I agree that the label range idea is an efficient way that could reduce 
>> the storage requirement of PHY chips.
>>
>> It's easy to require one or limited nodes to reserve a label range, but 
>> IMHO, it very difficut to require all nodes of a large network to do 
>> this and even worse when some labels are already used by other LSPs, 
>> unless there are some mechanisms to negotiate/advertise(e.g., flooding 
>> the label range by IGP within the network) the proper label range hence 
>> to aviod label collision.
>>
>> Best regards,
>> Mach
>>
>> --------------------------------------------------
>> From: "Shahram Davari" <davari@broadcom.com>
>> Sent: Thursday, July 15, 2010 1:58 AM
>> To: "Mach Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>; 
>> "Jia HE" <hejia@huawei.com>
>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
>> <mpls-tp@ietf.org>
>> Subject: RE: [mpls] [PWE3] 1588 over MPLS draft
>>
>>> Hi Mach,
>>>
>>> When a service provider wants to create these PTP LSPs, what is wrong 
>>> with allocating a range of labels for this purpose? This is purely a 
>>> software exercise. There are 2 million labels available to each node, 
>>> why can't some of them be allocated by software to PTP?
>>>
>>> In theory what you say is correct and should work, but in practice 
>>> there is a function called 1-step Transparent clocking that requires 
>>> time stamping at the PHY (immediately when the packet is received or 
>>> transmitted). PHY chips don't have CAM or lots of memory to store a 
>>> few thousand random labels. The label range will solve that problem 
>>> and is consistent with MPLS architecture.
>>>
>>> Thanks,
>>> Shahram
>>>
>>> -----Original Message-----
>>> From: Mach Chen [mailto:mach@huawei.com]
>>> Sent: Wednesday, July 14, 2010 1:53 AM
>>> To: S. Davari; Jia HE; Shahram Davari
>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>
>>> Hi Shahram,
>>>
>>> From the view of implementation, there is no more difference between 
>>> SHOULD
>>> and MUST :-)
>>> For me, the Label Range is more like a mechanim to notify related 
>>> nodes that
>>> some LSPs are dedicated for PTP messages other than the chips memory
>>> limitation, because the memory restriction is always there whatever 
>>> you use
>>> Label Range or not.
>>> IMHO, since the objective is to tell related MPLS nodes which LSPs are 
>>> PTP
>>> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and 
>>> seems
>>> more common. And it will avoid the strict requirement of "the network and
>>> all nodes required to support the Label range".
>>> In addition, there should be some mechanims(e.g., ISIS/OSPF 
>>> extensions) for
>>> nodes to advertise their PTP capability hence to help PTP LSPs 
>>> computation.
>>>
>>> Best regards,
>>> Mach
>>>
>>>
>>> --------------------------------------------------
>>> From: "S. Davari" <davarish@yahoo.com>
>>> Sent: Wednesday, July 14, 2010 2:31 PM
>>> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" <davari@broadcom.com>
>>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
>>> <mpls-tp@ietf.org>
>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>
>>>> Hi Jia,
>>>>
>>>> Label range is a SHOULD requirements and not MUST. The reason for Label
>>>> Range is
>>>> mainly for PHY chips that don't have large memory and can't store a 
>>>> lot of
>>>> Labels. Otherwise the PTP LSP is setup via signaling that specifies the
>>>> LSP as
>>>> carrying 1588.
>>>>
>>>> So the answer is that if a Label range is used it must be a Global range
>>>> within
>>>> a network and should not be used by any router for other applications.
>>>>
>>>> Thanks,
>>>> Shahram
>>>>
>>>>
>>>>
>>>> ________________________________
>>>> From: Jia HE <hejia@huawei.com>
>>>> To: Shahram Davari <davari@broadcom.com>
>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>>>> Sent: Tue, July 13, 2010 9:50:37 PM
>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>
>>>>
>>>> Hi Shahram,
>>>>
>>>> One question about "PTP Label Range":
>>>>
>>>> To my knowledge, label in MPLS network is a local  matter. For 
>>>> example, we
>>>> may
>>>> have per-interface or per-platform label space. Will  this specificed 
>>>> "PTP
>>>> Label
>>>> Range" conflict with the current in-use labels  for common LSPs?
>>>>
>>>>
>>>> B.R.
>>>> Jia
>>>>
>>>> ----- Original Message -----
>>>>> From: Shahram    Davari
>>>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org
>>>>> Sent: Thursday, July 08, 2010 3:12 AM
>>>>> Subject: [PWE3] 1588 over MPLS draft
>>>>>
>>>>>
>>>>> Hi All,
>>>>>
>>>>> Please find attached our first draft of 1588 over MPLS.    Since we 
>>>>> have
>>>>> some
>>>>> technical issues converting the Word format to Txt we    couldnâ€™t 
>>>>> upload
>>>>> the
>>>>> draft before the cut-off date. However we will    present the draft 
>>>>> in the
>>>>> next
>>>>> IETF meeting and will upload the draft after the    meeting.
>>>>>
>>>>> Note that the main WG is TicToc but may require    consultation with 
>>>>> MPLS
>>>>> and
>>>>> PWE3 WGs.
>>>>>
>>>>> Thanks,
>>>>> Shahram Davari
>>>> ________________________________
>>>> _______________________________________________
>>>>> pwe3 mailing    list
>>>>> pwe3@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>>
>>>>
>>>
>>>
>>>> _______________________________________________
>>>> mpls mailing list
>>>> mpls@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>>
>>>
>>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
> 

From davari@broadcom.com  Thu Jul 15 12:52:25 2010
Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48B083A6826; Thu, 15 Jul 2010 12:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599]
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 WeEbcj6H3JGM; Thu, 15 Jul 2010 12:52:24 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by core3.amsl.com (Postfix) with ESMTP id D1EDD3A6B8F; Thu, 15 Jul 2010 12:52:23 -0700 (PDT)
Received: from [10.16.192.224] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 15 Jul 2010 12:52:20 -0700
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Thu, 15 Jul 2010 12:52:20 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Date: Thu, 15 Jul 2010 12:52:19 -0700
Thread-Topic: [mpls] [PWE3] 1588 over MPLS draft
Thread-Index: AcskUNegGxJjmTexTKWKRS9v54XDBQABalNg
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6940EC2911E@SJEXCHCCR02.corp.ad.broadcom.com>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c> <4C3E7E83.9080603@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F5C24.4070505@joelhalpern.com>
In-Reply-To: <4C3F5C24.4070505@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6021B97E37O24568613-01-01
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 19:52:25 -0000

SGkgSm9lbCwNCg0KVGhlcmUgYXJlIDIgYXNwZWN0cyB0byB0aGlzIHB1enpsZToNCg0KMSkgSGFy
ZHdhcmUgc3VwcG9ydCBmb3IgMTU4OCBpbiBhIGRldmljZS4gDQoyKSBTb2Z0d2FyZSBzdXBwb3J0
IGZvciAxNTg4IGluIHRoZSBmb3JtIG9mIGFsbG9jYXRpbmcgbGFiZWxzIHRvIFBUUCBMU1BzDQoN
CkEgcm91dGVyIHRoYXQgd2FudHMgdG8gcGVyZm9ybSAxNTg4IHRpbWUgc3RhbXBpbmcgbXVzdCBo
YXZlIGJvdGggKDEpIGFuZCAoMikgZnVuY3Rpb25hbGl0eS4gV2hpbGUgYSByb3V0ZXIgaW4gdGhl
IHBhdGggb2YgYSBQVFAgTFNQIHRoYXQgZG9lcyBub3Qgc3VwcG9ydCAoMSkgc2hvdWxkIHN1cHBv
cnQgKDIpIGFuZCBhZHZlcnRpc2UgbGFiZWxzIGZyb20gc29tZSBhcmJpdHJhcnkgcmFuZ2UgZm9y
IFBUUCBMU1AuIA0KDQpJdCBpcyBxdWl0ZSBlYXN5IHRvIHVwZ3JhZGUgYSByb3V0ZXIgc29mdHdh
cmUgc28gdGhhdCB3aGVuIGl0IHJlY2VpdmVzIFJTVlAtVEUgbGFiZWwgcmVxdWVzdCB0byBhc3Np
Z24gbGFiZWwgZnJvbSBhbiBhcmJpdHJhcnkgbG9jYWwgcmFuZ2UuIA0KDQpTbyBJIGRvbid0IHNl
ZSBhbnkgaXNzdWUgaGVyZS4NCg0KVGhhbmtzLA0KU2hhaHJhbQ0KDQoNCg0KLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCkZyb206IEpvZWwgTS4gSGFscGVybiBbbWFpbHRvOmptaEBqb2VsaGFs
cGVybi5jb21dIA0KU2VudDogVGh1cnNkYXksIEp1bHkgMTUsIDIwMTAgMTI6MDYgUE0NClRvOiBT
aGFocmFtIERhdmFyaQ0KQ2M6IE1hY2ggQ2hlbjsgUy4gRGF2YXJpOyBKaWEgSEU7IG1wbHNAaWV0
Zi5vcmc7IHB3ZTNAaWV0Zi5vcmc7IHRpY2N0b2NAaWV0Zi5vcmc7IG1wbHMtdHBAaWV0Zi5vcmcN
ClN1YmplY3Q6IFJlOiBbbXBsc10gW1BXRTNdIDE1ODggb3ZlciBNUExTIGRyYWZ0DQoNCkFyY2hp
dGVjdHVyYWxseSwgYXMgSSB1bmRlcnN0YW5kIHRoZSBkcmFmdCwgdGhlIGRvd25zdHJlYW0gbmVp
Z2hib3Igb2YgYSANCjE1ODggc3VwcG9ydGluZyBkZXZpY2UgKG9uIHRoZSBQVFAgY2Fycnlpbmcg
TFNQKSBtYXkgbm90IGl0c2VsZiBiZSBhIA0KMTU4OCBzdXBwb3J0aW5nIGRldmljZS4gIElzIHRo
YXQgY29ycmVjdD8gIElmIHRoYXQgaXMgbm90IGNvcnJlY3QsIGlmIA0KaW5zdGVhZCB0aGUgc3Ry
dWN0dXJlIGlzIHRoYXQgUFRQIHN1cHBvcnRpbmcgTFNQcyBhcmUgZXN0YWJsaXNoZWQgDQpiZXR3
ZWVuIGFkamFjZW50IGVuaGFuY2VkIGRldmljZXMsIHRoZW4gSSBjYW4gc2VlIGhvdyBzb21lIHNv
cnQgb2YgYSANCmxhYmVsIHJhbmdlIG1pZ2h0IG1ha2Ugc2Vuc2UuDQoNCklmIGhvd2V2ZXIsIHRo
ZSBkb3duc3RyZWFtIG5vZGUgeW91IHJlZmVyIHRvIG1heSBiZSBhbiBleGlzdGluZyBMU1IsIA0K
dGhlbiBJIGRvIG5vdCBzZWUgaG93IHlvdSBjYW4gYXNrIGFuIGV4aXN0aW5nIExTUiB0byBhbGxv
Y2F0ZSBhIGxhYmVsIA0KcmFuZ2UgZm9yIGEgZnVuY3Rpb24gaXQgZG9lcyBub3QgdW5kZXJzdGFu
ZC4NCg0KWW91cnMsDQpKb2VsDQoNClNoYWhyYW0gRGF2YXJpIHdyb3RlOg0KPiBIaSBKb2VsLA0K
PiANCj4gSSBhZ3JlZSB3aXRoIHlvdXIgbG9naWMsIGJ1dCB0aGUgaWRlYSBpcyBhIGJpdCBkaWZm
ZXJlbnQ6DQo+IA0KPiBBbGwgd2UgbmVlZCBpcyBhIGxhYmVsIHJhbmdlLCBpdCBkb2VzIG5vdCBu
ZWVkIHRvIGJlIGdsb2JhbGx5IHVuaXF1ZSBpbiB0aGUgbmV0d29yayBhbmQgaXQgZG9lcw0KID5u
b3QgZXZlbiBuZWVkIHRvIGJlIHRoZSBzYW1lIG9uIHRoZSBUeCBhbmQgUnggZGlyZWN0aW9uIG9m
IHRoZSBzYW1lIA0KbGluay4gQWx0aG91Z2ggd2UgbmVlZCB0aW1lDQogPnN0YW1waW5nIGJvdGgg
b24gUnggYW5kIG9uIFR4LCBidXQgb24gUnggYSBub2RlIGlzIGluIGNvbnRyb2wgb2YgaXRzIA0K
b3duIGxhYmVsIGFuZCBvbiBUeCB0aGUNCiA+ZG93bnN0cmVhbSBub2RlIHNob3VsZCBhZHZlcnRp
c2Ugc29tZSBsYWJlbCByYW5nZS4gV2hhdCB3ZSBkb24ndCB3YW50IA0KaXMgdGhhdCB0aGUgZG93
bnN0cmVhbQ0KID5ub2RlIHRvIGFkdmVydGlzZSByYW5kb20gbGFiZWxzIGZvciBlYWNoIExTUCBj
YXJyeWluZyBQVFAuDQo+IA0KPiBJIHdpbGwgdXBkYXRlIHRoZSBkcmFmdCB0byBtZW50aW9uIHRo
YXQgdGhlIGxhYmVsIHJhbmdlIGRvZXMgbm90IHJlcXVpcmUgdG8gYmUgZ2xvYmFsIGJ1dCBpdCBj
YW4NCiA+YmUgcGVyLXBsYXRmb3JtIG9yIGV2ZW4gcGVyLWludGVyZmFjZS4NCj4gDQo+IFRoYW5r
cywNCj4gU2hhaHJhbQ0KPiANCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTog
Sm9lbCBNLiBIYWxwZXJuIFttYWlsdG86am1oQGpvZWxoYWxwZXJuLmNvbV0gDQo+IFNlbnQ6IFdl
ZG5lc2RheSwgSnVseSAxNCwgMjAxMCA4OjIxIFBNDQo+IFRvOiBNYWNoIENoZW4NCj4gQ2M6IFNo
YWhyYW0gRGF2YXJpOyBTLiBEYXZhcmk7IEppYSBIRTsgbXBsc0BpZXRmLm9yZzsgcHdlM0BpZXRm
Lm9yZzsgdGljY3RvY0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTog
W21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPiANCj4gUmVtZW1iZXIgdGhhdCBp
ZiB3aGF0IGlzIHJlcXVpcmVkIGlzIHRoYXQgdGhlIG1lc3NhZ2UgYXJyaXZpbmcgYXQgdGhlIA0K
PiAxNTg4IHN1cHBvcnRpbmcgZGV2aWNlIGhhdmUgYSBjZXJ0YWluIGxhYmVsIHJhbmdlLCB0aGF0
IGlzIGEgcHVyZWx5IA0KPiBsb2NhbCBtYXR0ZXIuICBBcyBsb25nIGFzIHRoZSBzaW5nYWxpbmcg
Y2FycmllcyB0aGUgaW5kaWNhdGlvbiB0aGF0IHRoZSANCj4gTFNQIGlzIHRvIGJlIGRlZGljYXRl
ZCB0byAxNTg4IHRyYWZmaWMgKGEgcmVhc29uYWJsZSBleHRlbnNpb24gdG8gdGhlIA0KPiBzaWdu
YWxpbmcpLCB0aGUgZG93bnN0cmVhbSBzd2l0Y2ggY2FuIHBpY2sgd2hhdCBsYWJlbCB0byBhc3Np
Z24gdG8gdGhhdCBMU1AuDQo+IA0KPiBJZiB0aGUgZ29hbCBpcyB0byBoYXZlIHRoZSBvdXRnb2lu
ZyBsYWJlbCBiZSBmcm9tIGEgc3BlY2lmaWMgcmFuZ2UsIHRoYXQgDQo+IGlzIGVzc2VudGlhbGx5
IGltcG9zc2libGUgaW4gdGhlIHByb3Bvc2VkIGFyY2hpdGVjdHVyZS4gIFRoZSBwcm9wb3NlZCAN
Cj4gYXJjaGl0ZWN0dXJlIGlzIG9uZSBpbiB3aGljaCAxNTg4IHN3aXRjaGVzIGFyZSBwZWVycyB3
aXRoIGV4aXN0aW5nIExTUnMgDQo+IHVzaW5nIE1QTFMuICBBcyBzdWNoLCBpbiBvcmRlciB0byBo
YXZlIGEgbGFiZWwgcmFuZ2UgZm9yIG91dGdvaW5nIA0KPiBsYWJlbHMsIHRoZSBleGlzdGluZyBN
UExTIExTUiB3b3VsZCBzb21laG93IGhhdmUgdG8ga25vdyBhYm91dCB0aGlzIA0KPiByZXNlcnZl
ZCBsYWJlbCByYW5nZSwgbm90IHVzZSB0aG9zZSBsYWJlbHMgZm9yIG90aGVyIHB1cnBvc2VzLCBh
bmQgDQo+IGFzc2lnbiB0aG9zZSBsYWJlbHMgdG8gMTU4OCBMU1BzLiAgQWxsIG9mIHdoaWNoIGlz
IA0KPiBub24tYmFja3dhcmRzLWNvbXBhdGlibGUuICBJZiB0aGUgMTU4OCBMU1BzIHdlcmUgYWN0
dWFsbHkgcHNldWRvd2lyZXMsIA0KPiB0dW5uZWxlZCBvdmVyIExTUHMsIHRoZW4gYW55IG51bWJl
ciBvZiB0aGluZ3MgYXJlIHBvc3NpYmxlLg0KPiANCj4gWW91cnMsDQo+IEpvZWwgTS4gSGFscGVy
bg0KPiANCj4gTWFjaCBDaGVuIHdyb3RlOg0KPj4gSGkgU2hhaHJhbSwNCj4+DQo+PiBJIGFncmVl
IHRoYXQgdGhlIGxhYmVsIHJhbmdlIGlkZWEgaXMgYW4gZWZmaWNpZW50IHdheSB0aGF0IGNvdWxk
IHJlZHVjZSANCj4+IHRoZSBzdG9yYWdlIHJlcXVpcmVtZW50IG9mIFBIWSBjaGlwcy4NCj4+DQo+
PiBJdCdzIGVhc3kgdG8gcmVxdWlyZSBvbmUgb3IgbGltaXRlZCBub2RlcyB0byByZXNlcnZlIGEg
bGFiZWwgcmFuZ2UsIGJ1dCANCj4+IElNSE8sIGl0IHZlcnkgZGlmZmljdXQgdG8gcmVxdWlyZSBh
bGwgbm9kZXMgb2YgYSBsYXJnZSBuZXR3b3JrIHRvIGRvIA0KPj4gdGhpcyBhbmQgZXZlbiB3b3Jz
ZSB3aGVuIHNvbWUgbGFiZWxzIGFyZSBhbHJlYWR5IHVzZWQgYnkgb3RoZXIgTFNQcywgDQo+PiB1
bmxlc3MgdGhlcmUgYXJlIHNvbWUgbWVjaGFuaXNtcyB0byBuZWdvdGlhdGUvYWR2ZXJ0aXNlKGUu
Zy4sIGZsb29kaW5nIA0KPj4gdGhlIGxhYmVsIHJhbmdlIGJ5IElHUCB3aXRoaW4gdGhlIG5ldHdv
cmspIHRoZSBwcm9wZXIgbGFiZWwgcmFuZ2UgaGVuY2UgDQo+PiB0byBhdmlvZCBsYWJlbCBjb2xs
aXNpb24uDQo+Pg0KPj4gQmVzdCByZWdhcmRzLA0KPj4gTWFjaA0KPj4NCj4+IC0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+PiBGcm9tOiAiU2hhaHJh
bSBEYXZhcmkiIDxkYXZhcmlAYnJvYWRjb20uY29tPg0KPj4gU2VudDogVGh1cnNkYXksIEp1bHkg
MTUsIDIwMTAgMTo1OCBBTQ0KPj4gVG86ICJNYWNoIENoZW4iIDxtYWNoQGh1YXdlaS5jb20+OyAi
Uy4gRGF2YXJpIiA8ZGF2YXJpc2hAeWFob28uY29tPjsgDQo+PiAiSmlhIEhFIiA8aGVqaWFAaHVh
d2VpLmNvbT4NCj4+IENjOiA8bXBsc0BpZXRmLm9yZz47IDxwd2UzQGlldGYub3JnPjsgPHRpY2N0
b2NAaWV0Zi5vcmc+OyANCj4+IDxtcGxzLXRwQGlldGYub3JnPg0KPj4gU3ViamVjdDogUkU6IFtt
cGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCj4+DQo+Pj4gSGkgTWFjaCwNCj4+Pg0K
Pj4+IFdoZW4gYSBzZXJ2aWNlIHByb3ZpZGVyIHdhbnRzIHRvIGNyZWF0ZSB0aGVzZSBQVFAgTFNQ
cywgd2hhdCBpcyB3cm9uZyANCj4+PiB3aXRoIGFsbG9jYXRpbmcgYSByYW5nZSBvZiBsYWJlbHMg
Zm9yIHRoaXMgcHVycG9zZT8gVGhpcyBpcyBwdXJlbHkgYSANCj4+PiBzb2Z0d2FyZSBleGVyY2lz
ZS4gVGhlcmUgYXJlIDIgbWlsbGlvbiBsYWJlbHMgYXZhaWxhYmxlIHRvIGVhY2ggbm9kZSwgDQo+
Pj4gd2h5IGNhbid0IHNvbWUgb2YgdGhlbSBiZSBhbGxvY2F0ZWQgYnkgc29mdHdhcmUgdG8gUFRQ
Pw0KPj4+DQo+Pj4gSW4gdGhlb3J5IHdoYXQgeW91IHNheSBpcyBjb3JyZWN0IGFuZCBzaG91bGQg
d29yaywgYnV0IGluIHByYWN0aWNlIA0KPj4+IHRoZXJlIGlzIGEgZnVuY3Rpb24gY2FsbGVkIDEt
c3RlcCBUcmFuc3BhcmVudCBjbG9ja2luZyB0aGF0IHJlcXVpcmVzIA0KPj4+IHRpbWUgc3RhbXBp
bmcgYXQgdGhlIFBIWSAoaW1tZWRpYXRlbHkgd2hlbiB0aGUgcGFja2V0IGlzIHJlY2VpdmVkIG9y
IA0KPj4+IHRyYW5zbWl0dGVkKS4gUEhZIGNoaXBzIGRvbid0IGhhdmUgQ0FNIG9yIGxvdHMgb2Yg
bWVtb3J5IHRvIHN0b3JlIGEgDQo+Pj4gZmV3IHRob3VzYW5kIHJhbmRvbSBsYWJlbHMuIFRoZSBs
YWJlbCByYW5nZSB3aWxsIHNvbHZlIHRoYXQgcHJvYmxlbSANCj4+PiBhbmQgaXMgY29uc2lzdGVu
dCB3aXRoIE1QTFMgYXJjaGl0ZWN0dXJlLg0KPj4+DQo+Pj4gVGhhbmtzLA0KPj4+IFNoYWhyYW0N
Cj4+Pg0KPj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4gRnJvbTogTWFjaCBDaGVu
IFttYWlsdG86bWFjaEBodWF3ZWkuY29tXQ0KPj4+IFNlbnQ6IFdlZG5lc2RheSwgSnVseSAxNCwg
MjAxMCAxOjUzIEFNDQo+Pj4gVG86IFMuIERhdmFyaTsgSmlhIEhFOyBTaGFocmFtIERhdmFyaQ0K
Pj4+IENjOiBtcGxzQGlldGYub3JnOyBwd2UzQGlldGYub3JnOyB0aWNjdG9jQGlldGYub3JnOyBt
cGxzLXRwQGlldGYub3JnDQo+Pj4gU3ViamVjdDogUmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVy
IE1QTFMgZHJhZnQNCj4+Pg0KPj4+IEhpIFNoYWhyYW0sDQo+Pj4NCj4+PiBGcm9tIHRoZSB2aWV3
IG9mIGltcGxlbWVudGF0aW9uLCB0aGVyZSBpcyBubyBtb3JlIGRpZmZlcmVuY2UgYmV0d2VlbiAN
Cj4+PiBTSE9VTEQNCj4+PiBhbmQgTVVTVCA6LSkNCj4+PiBGb3IgbWUsIHRoZSBMYWJlbCBSYW5n
ZSBpcyBtb3JlIGxpa2UgYSBtZWNoYW5pbSB0byBub3RpZnkgcmVsYXRlZCANCj4+PiBub2RlcyB0
aGF0DQo+Pj4gc29tZSBMU1BzIGFyZSBkZWRpY2F0ZWQgZm9yIFBUUCBtZXNzYWdlcyBvdGhlciB0
aGFuIHRoZSBjaGlwcyBtZW1vcnkNCj4+PiBsaW1pdGF0aW9uLCBiZWNhdXNlIHRoZSBtZW1vcnkg
cmVzdHJpY3Rpb24gaXMgYWx3YXlzIHRoZXJlIHdoYXRldmVyIA0KPj4+IHlvdSB1c2UNCj4+PiBM
YWJlbCBSYW5nZSBvciBub3QuDQo+Pj4gSU1ITywgc2luY2UgdGhlIG9iamVjdGl2ZSBpcyB0byB0
ZWxsIHJlbGF0ZWQgTVBMUyBub2RlcyB3aGljaCBMU1BzIGFyZSANCj4+PiBQVFANCj4+PiBMU1Bz
LCBhbiBpbmRpY2F0aW9uIGluIHRoZSBzaWduYWxpbmcoUlNWUC1URS9HTVBMUy9MRFApIGlzIGVu
b3VnaCBhbmQgDQo+Pj4gc2VlbXMNCj4+PiBtb3JlIGNvbW1vbi4gQW5kIGl0IHdpbGwgYXZvaWQg
dGhlIHN0cmljdCByZXF1aXJlbWVudCBvZiAidGhlIG5ldHdvcmsgYW5kDQo+Pj4gYWxsIG5vZGVz
IHJlcXVpcmVkIHRvIHN1cHBvcnQgdGhlIExhYmVsIHJhbmdlIi4NCj4+PiBJbiBhZGRpdGlvbiwg
dGhlcmUgc2hvdWxkIGJlIHNvbWUgbWVjaGFuaW1zKGUuZy4sIElTSVMvT1NQRiANCj4+PiBleHRl
bnNpb25zKSBmb3INCj4+PiBub2RlcyB0byBhZHZlcnRpc2UgdGhlaXIgUFRQIGNhcGFiaWxpdHkg
aGVuY2UgdG8gaGVscCBQVFAgTFNQcyANCj4+PiBjb21wdXRhdGlvbi4NCj4+Pg0KPj4+IEJlc3Qg
cmVnYXJkcywNCj4+PiBNYWNoDQo+Pj4NCj4+Pg0KPj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+Pj4gRnJvbTogIlMuIERhdmFyaSIgPGRhdmFy
aXNoQHlhaG9vLmNvbT4NCj4+PiBTZW50OiBXZWRuZXNkYXksIEp1bHkgMTQsIDIwMTAgMjozMSBQ
TQ0KPj4+IFRvOiAiSmlhIEhFIiA8aGVqaWFAaHVhd2VpLmNvbT47ICJTaGFocmFtIERhdmFyaSIg
PGRhdmFyaUBicm9hZGNvbS5jb20+DQo+Pj4gQ2M6IDxtcGxzQGlldGYub3JnPjsgPHB3ZTNAaWV0
Zi5vcmc+OyA8dGljY3RvY0BpZXRmLm9yZz47IA0KPj4+IDxtcGxzLXRwQGlldGYub3JnPg0KPj4+
IFN1YmplY3Q6IFJlOiBbbXBsc10gW1BXRTNdIDE1ODggb3ZlciBNUExTIGRyYWZ0DQo+Pj4NCj4+
Pj4gSGkgSmlhLA0KPj4+Pg0KPj4+PiBMYWJlbCByYW5nZSBpcyBhIFNIT1VMRCByZXF1aXJlbWVu
dHMgYW5kIG5vdCBNVVNULiBUaGUgcmVhc29uIGZvciBMYWJlbA0KPj4+PiBSYW5nZSBpcw0KPj4+
PiBtYWlubHkgZm9yIFBIWSBjaGlwcyB0aGF0IGRvbid0IGhhdmUgbGFyZ2UgbWVtb3J5IGFuZCBj
YW4ndCBzdG9yZSBhIA0KPj4+PiBsb3Qgb2YNCj4+Pj4gTGFiZWxzLiBPdGhlcndpc2UgdGhlIFBU
UCBMU1AgaXMgc2V0dXAgdmlhIHNpZ25hbGluZyB0aGF0IHNwZWNpZmllcyB0aGUNCj4+Pj4gTFNQ
IGFzDQo+Pj4+IGNhcnJ5aW5nIDE1ODguDQo+Pj4+DQo+Pj4+IFNvIHRoZSBhbnN3ZXIgaXMgdGhh
dCBpZiBhIExhYmVsIHJhbmdlIGlzIHVzZWQgaXQgbXVzdCBiZSBhIEdsb2JhbCByYW5nZQ0KPj4+
PiB3aXRoaW4NCj4+Pj4gYSBuZXR3b3JrIGFuZCBzaG91bGQgbm90IGJlIHVzZWQgYnkgYW55IHJv
dXRlciBmb3Igb3RoZXIgYXBwbGljYXRpb25zLg0KPj4+Pg0KPj4+PiBUaGFua3MsDQo+Pj4+IFNo
YWhyYW0NCj4+Pj4NCj4+Pj4NCj4+Pj4NCj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4+Pj4gRnJvbTogSmlhIEhFIDxoZWppYUBodWF3ZWkuY29tPg0KPj4+PiBUbzogU2hh
aHJhbSBEYXZhcmkgPGRhdmFyaUBicm9hZGNvbS5jb20+DQo+Pj4+IENjOiBtcGxzQGlldGYub3Jn
OyBwd2UzQGlldGYub3JnOyB0aWNjdG9jQGlldGYub3JnOyBtcGxzLXRwQGlldGYub3JnDQo+Pj4+
IFNlbnQ6IFR1ZSwgSnVseSAxMywgMjAxMCA5OjUwOjM3IFBNDQo+Pj4+IFN1YmplY3Q6IFJlOiBb
bXBsc10gW1BXRTNdIDE1ODggb3ZlciBNUExTIGRyYWZ0DQo+Pj4+DQo+Pj4+DQo+Pj4+IEhpIFNo
YWhyYW0sDQo+Pj4+DQo+Pj4+IE9uZSBxdWVzdGlvbiBhYm91dCAiUFRQIExhYmVsIFJhbmdlIjoN
Cj4+Pj4NCj4+Pj4gVG8gbXkga25vd2xlZGdlLCBsYWJlbCBpbiBNUExTIG5ldHdvcmsgaXMgYSBs
b2NhbCAgbWF0dGVyLiBGb3IgDQo+Pj4+IGV4YW1wbGUsIHdlDQo+Pj4+IG1heQ0KPj4+PiBoYXZl
IHBlci1pbnRlcmZhY2Ugb3IgcGVyLXBsYXRmb3JtIGxhYmVsIHNwYWNlLiBXaWxsICB0aGlzIHNw
ZWNpZmljZWQgDQo+Pj4+ICJQVFANCj4+Pj4gTGFiZWwNCj4+Pj4gUmFuZ2UiIGNvbmZsaWN0IHdp
dGggdGhlIGN1cnJlbnQgaW4tdXNlIGxhYmVscyAgZm9yIGNvbW1vbiBMU1BzPw0KPj4+Pg0KPj4+
Pg0KPj4+PiBCLlIuDQo+Pj4+IEppYQ0KPj4+Pg0KPj4+PiAtLS0tLSBPcmlnaW5hbCBNZXNzYWdl
IC0tLS0tDQo+Pj4+PiBGcm9tOiBTaGFocmFtICAgIERhdmFyaQ0KPj4+Pj4gVG86IHRpY2N0b2NA
aWV0Zi5vcmcgOyBtcGxzQGlldGYub3JnIDsgbXBscy10cEBpZXRmLm9yZyA7IHB3ZTNAaWV0Zi5v
cmcNCj4+Pj4+IFNlbnQ6IFRodXJzZGF5LCBKdWx5IDA4LCAyMDEwIDM6MTIgQU0NCj4+Pj4+IFN1
YmplY3Q6IFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPj4+Pj4NCj4+Pj4+DQo+Pj4+PiBI
aSBBbGwsDQo+Pj4+Pg0KPj4+Pj4gUGxlYXNlIGZpbmQgYXR0YWNoZWQgb3VyIGZpcnN0IGRyYWZ0
IG9mIDE1ODggb3ZlciBNUExTLiAgICBTaW5jZSB3ZSANCj4+Pj4+IGhhdmUNCj4+Pj4+IHNvbWUN
Cj4+Pj4+IHRlY2huaWNhbCBpc3N1ZXMgY29udmVydGluZyB0aGUgV29yZCBmb3JtYXQgdG8gVHh0
IHdlICAgIGNvdWxkbuKAmXQgDQo+Pj4+PiB1cGxvYWQNCj4+Pj4+IHRoZQ0KPj4+Pj4gZHJhZnQg
YmVmb3JlIHRoZSBjdXQtb2ZmIGRhdGUuIEhvd2V2ZXIgd2Ugd2lsbCAgICBwcmVzZW50IHRoZSBk
cmFmdCANCj4+Pj4+IGluIHRoZQ0KPj4+Pj4gbmV4dA0KPj4+Pj4gSUVURiBtZWV0aW5nIGFuZCB3
aWxsIHVwbG9hZCB0aGUgZHJhZnQgYWZ0ZXIgdGhlICAgIG1lZXRpbmcuDQo+Pj4+Pg0KPj4+Pj4g
Tm90ZSB0aGF0IHRoZSBtYWluIFdHIGlzIFRpY1RvYyBidXQgbWF5IHJlcXVpcmUgICAgY29uc3Vs
dGF0aW9uIHdpdGggDQo+Pj4+PiBNUExTDQo+Pj4+PiBhbmQNCj4+Pj4+IFBXRTMgV0dzLg0KPj4+
Pj4NCj4+Pj4+IFRoYW5rcywNCj4+Pj4+IFNoYWhyYW0gRGF2YXJpDQo+Pj4+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+Pj4+PiBwd2UzIG1haWxpbmcgICAgbGlzdA0KPj4+Pj4gcHdl
M0BpZXRmLm9yZw0KPj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9w
d2UzDQo+Pj4+Pg0KPj4+Pg0KPj4+DQo+Pj4NCj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4gbXBscyBtYWlsaW5nIGxpc3QNCj4+Pj4gbXBs
c0BpZXRmLm9yZw0KPj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21w
bHMNCj4+Pj4NCj4+Pg0KPj4+DQo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KPj4gbXBscyBtYWlsaW5nIGxpc3QNCj4+IG1wbHNAaWV0Zi5vcmcNCj4+
IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0KPiANCg0K


From jmh@joelhalpern.com  Thu Jul 15 13:31:56 2010
Return-Path: <jmh@joelhalpern.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B6A73A6BA1; Thu, 15 Jul 2010 13:31:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599]
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 2MaC9ez3dFyR; Thu, 15 Jul 2010 13:31:53 -0700 (PDT)
Received: from hgblob.mail.tigertech.net (hgblob.mail.tigertech.net [64.62.209.71]) by core3.amsl.com (Postfix) with ESMTP id 428663A6B84; Thu, 15 Jul 2010 13:31:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id CFC8B32365D1; Thu, 15 Jul 2010 13:31:43 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-61.clppva.btas.verizon.net [71.161.50.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id E254632365DA; Thu, 15 Jul 2010 13:31:41 -0700 (PDT)
Message-ID: <4C3F702B.5090704@joelhalpern.com>
Date: Thu, 15 Jul 2010 16:31:39 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Shahram Davari <davari@broadcom.com>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c> <4C3E7E83.9080603@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F5C24.4070505@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC2911E@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6940EC2911E@SJEXCHCCR02.corp.ad.broadcom.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 20:31:56 -0000

I am sorry, but requiring every LSR in the infrastructure to get a 
software upgrade in order to allow for the presence of 1588-supporting 
devices is a MAJOR issue.  It is NOT backwards compatible.  Operators 
(wether service provider or enterprise IT) do NOT like being told they 
ahve to upgrade the software on all devices in their network in order to 
add a capability that those devices are not engaging in.

While one can argue about the "ease" of the specific software change, 
there is from an operational perspective no such thing as an easy 
upgrade of any device, and there is definitely no such thing as an easy 
upgrade of all the devices in the network.

Yours,
Joel

Shahram Davari wrote:
> Hi Joel,
> 
> There are 2 aspects to this puzzle:
> 
> 1) Hardware support for 1588 in a device. 
> 2) Software support for 1588 in the form of allocating labels to PTP LSPs
> 
> A router that wants to perform 1588 time stamping must have both (1) and (2) functionality. While a router in 
 >the path of a PTP LSP that does not support (1) should support (2) and 
advertise labels from some arbitrary
 >range for PTP LSP.
> 
> It is quite easy to upgrade a router software so that when it receives RSVP-TE label request to assign label 
 >from an arbitrary local range.
> 
> So I don't see any issue here.
> 
> Thanks,
> Shahram
> 
> 
> 
> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 
> Sent: Thursday, July 15, 2010 12:06 PM
> To: Shahram Davari
> Cc: Mach Chen; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> 
> Architecturally, as I understand the draft, the downstream neighbor of a 
> 1588 supporting device (on the PTP carrying LSP) may not itself be a 
> 1588 supporting device.  Is that correct?  If that is not correct, if 
> instead the structure is that PTP supporting LSPs are established 
> between adjacent enhanced devices, then I can see how some sort of a 
> label range might make sense.
> 
> If however, the downstream node you refer to may be an existing LSR, 
> then I do not see how you can ask an existing LSR to allocate a label 
> range for a function it does not understand.
> 
> Yours,
> Joel
> 
> Shahram Davari wrote:
>> Hi Joel,
>>
>> I agree with your logic, but the idea is a bit different:
>>
>> All we need is a label range, it does not need to be globally unique in the network and it does
>  >not even need to be the same on the Tx and Rx direction of the same 
> link. Although we need time
>  >stamping both on Rx and on Tx, but on Rx a node is in control of its 
> own label and on Tx the
>  >downstream node should advertise some label range. What we don't want 
> is that the downstream
>  >node to advertise random labels for each LSP carrying PTP.
>> I will update the draft to mention that the label range does not require to be global but it can
>  >be per-platform or even per-interface.
>> Thanks,
>> Shahram
>>
>> -----Original Message-----
>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 
>> Sent: Wednesday, July 14, 2010 8:21 PM
>> To: Mach Chen
>> Cc: Shahram Davari; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>
>> Remember that if what is required is that the message arriving at the 
>> 1588 supporting device have a certain label range, that is a purely 
>> local matter.  As long as the singaling carries the indication that the 
>> LSP is to be dedicated to 1588 traffic (a reasonable extension to the 
>> signaling), the downstream switch can pick what label to assign to that LSP.
>>
>> If the goal is to have the outgoing label be from a specific range, that 
>> is essentially impossible in the proposed architecture.  The proposed 
>> architecture is one in which 1588 switches are peers with existing LSRs 
>> using MPLS.  As such, in order to have a label range for outgoing 
>> labels, the existing MPLS LSR would somehow have to know about this 
>> reserved label range, not use those labels for other purposes, and 
>> assign those labels to 1588 LSPs.  All of which is 
>> non-backwards-compatible.  If the 1588 LSPs were actually pseudowires, 
>> tunneled over LSPs, then any number of things are possible.
>>
>> Yours,
>> Joel M. Halpern
>>
>> Mach Chen wrote:
>>> Hi Shahram,
>>>
>>> I agree that the label range idea is an efficient way that could reduce 
>>> the storage requirement of PHY chips.
>>>
>>> It's easy to require one or limited nodes to reserve a label range, but 
>>> IMHO, it very difficut to require all nodes of a large network to do 
>>> this and even worse when some labels are already used by other LSPs, 
>>> unless there are some mechanisms to negotiate/advertise(e.g., flooding 
>>> the label range by IGP within the network) the proper label range hence 
>>> to aviod label collision.
>>>
>>> Best regards,
>>> Mach
>>>
>>> --------------------------------------------------
>>> From: "Shahram Davari" <davari@broadcom.com>
>>> Sent: Thursday, July 15, 2010 1:58 AM
>>> To: "Mach Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>; 
>>> "Jia HE" <hejia@huawei.com>
>>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
>>> <mpls-tp@ietf.org>
>>> Subject: RE: [mpls] [PWE3] 1588 over MPLS draft
>>>
>>>> Hi Mach,
>>>>
>>>> When a service provider wants to create these PTP LSPs, what is wrong 
>>>> with allocating a range of labels for this purpose? This is purely a 
>>>> software exercise. There are 2 million labels available to each node, 
>>>> why can't some of them be allocated by software to PTP?
>>>>
>>>> In theory what you say is correct and should work, but in practice 
>>>> there is a function called 1-step Transparent clocking that requires 
>>>> time stamping at the PHY (immediately when the packet is received or 
>>>> transmitted). PHY chips don't have CAM or lots of memory to store a 
>>>> few thousand random labels. The label range will solve that problem 
>>>> and is consistent with MPLS architecture.
>>>>
>>>> Thanks,
>>>> Shahram
>>>>
>>>> -----Original Message-----
>>>> From: Mach Chen [mailto:mach@huawei.com]
>>>> Sent: Wednesday, July 14, 2010 1:53 AM
>>>> To: S. Davari; Jia HE; Shahram Davari
>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>
>>>> Hi Shahram,
>>>>
>>>> From the view of implementation, there is no more difference between 
>>>> SHOULD
>>>> and MUST :-)
>>>> For me, the Label Range is more like a mechanim to notify related 
>>>> nodes that
>>>> some LSPs are dedicated for PTP messages other than the chips memory
>>>> limitation, because the memory restriction is always there whatever 
>>>> you use
>>>> Label Range or not.
>>>> IMHO, since the objective is to tell related MPLS nodes which LSPs are 
>>>> PTP
>>>> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and 
>>>> seems
>>>> more common. And it will avoid the strict requirement of "the network and
>>>> all nodes required to support the Label range".
>>>> In addition, there should be some mechanims(e.g., ISIS/OSPF 
>>>> extensions) for
>>>> nodes to advertise their PTP capability hence to help PTP LSPs 
>>>> computation.
>>>>
>>>> Best regards,
>>>> Mach
>>>>
>>>>
>>>> --------------------------------------------------
>>>> From: "S. Davari" <davarish@yahoo.com>
>>>> Sent: Wednesday, July 14, 2010 2:31 PM
>>>> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" <davari@broadcom.com>
>>>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
>>>> <mpls-tp@ietf.org>
>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>
>>>>> Hi Jia,
>>>>>
>>>>> Label range is a SHOULD requirements and not MUST. The reason for Label
>>>>> Range is
>>>>> mainly for PHY chips that don't have large memory and can't store a 
>>>>> lot of
>>>>> Labels. Otherwise the PTP LSP is setup via signaling that specifies the
>>>>> LSP as
>>>>> carrying 1588.
>>>>>
>>>>> So the answer is that if a Label range is used it must be a Global range
>>>>> within
>>>>> a network and should not be used by any router for other applications.
>>>>>
>>>>> Thanks,
>>>>> Shahram
>>>>>
>>>>>
>>>>>
>>>>> ________________________________
>>>>> From: Jia HE <hejia@huawei.com>
>>>>> To: Shahram Davari <davari@broadcom.com>
>>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>>>>> Sent: Tue, July 13, 2010 9:50:37 PM
>>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>>
>>>>>
>>>>> Hi Shahram,
>>>>>
>>>>> One question about "PTP Label Range":
>>>>>
>>>>> To my knowledge, label in MPLS network is a local  matter. For 
>>>>> example, we
>>>>> may
>>>>> have per-interface or per-platform label space. Will  this specificed 
>>>>> "PTP
>>>>> Label
>>>>> Range" conflict with the current in-use labels  for common LSPs?
>>>>>
>>>>>
>>>>> B.R.
>>>>> Jia
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: Shahram    Davari
>>>>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org
>>>>>> Sent: Thursday, July 08, 2010 3:12 AM
>>>>>> Subject: [PWE3] 1588 over MPLS draft
>>>>>>
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Please find attached our first draft of 1588 over MPLS.    Since we 
>>>>>> have
>>>>>> some
>>>>>> technical issues converting the Word format to Txt we    couldnâ€™t 
>>>>>> upload
>>>>>> the
>>>>>> draft before the cut-off date. However we will    present the draft 
>>>>>> in the
>>>>>> next
>>>>>> IETF meeting and will upload the draft after the    meeting.
>>>>>>
>>>>>> Note that the main WG is TicToc but may require    consultation with 
>>>>>> MPLS
>>>>>> and
>>>>>> PWE3 WGs.
>>>>>>
>>>>>> Thanks,
>>>>>> Shahram Davari
>>>>> ________________________________
>>>>> _______________________________________________
>>>>>> pwe3 mailing    list
>>>>>> pwe3@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>>>
>>>>
>>>>> _______________________________________________
>>>>> mpls mailing list
>>>>> mpls@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>>>
>>>>
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
> 

From jdrake@juniper.net  Thu Jul 15 13:34:14 2010
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99CFA3A6B80; Thu, 15 Jul 2010 13:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.309
X-Spam-Level: 
X-Spam-Status: No, score=-6.309 tagged_above=-999 required=5 tests=[AWL=0.290,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 pgdvGqTZGBLH; Thu, 15 Jul 2010 13:34:13 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with ESMTP id CA3FD3A6A89; Thu, 15 Jul 2010 13:34:11 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKTD9wzeE+DWFVXoXOdnnRSm97XGD5iFy/@postini.com; Thu, 15 Jul 2010 13:34:23 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Thu, 15 Jul 2010 13:26:54 -0700
From: John E Drake <jdrake@juniper.net>
To: Shahram Davari <davari@broadcom.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Date: Thu, 15 Jul 2010 13:26:52 -0700
Thread-Topic: [mpls] [PWE3] 1588 over MPLS draft
Thread-Index: AcskUNegGxJjmTexTKWKRS9v54XDBQABalNgAAFaQ9A=
Message-ID: <5E893DB832F57341992548CDBB3331639844311567@EMBX01-HQ.jnpr.net>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c> <4C3E7E83.9080603@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F5C24.4070505@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC2911E@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6940EC2911E@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 20:34:14 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogbXBscy10cC1ib3VuY2Vz
QGlldGYub3JnIFttYWlsdG86bXBscy10cC1ib3VuY2VzQGlldGYub3JnXSBPbg0KPiBCZWhhbGYg
T2YgU2hhaHJhbSBEYXZhcmkNCj4gU2VudDogVGh1cnNkYXksIEp1bHkgMTUsIDIwMTAgMTI6NTIg
UE0NCj4gVG86IEpvZWwgTS4gSGFscGVybg0KPiBDYzogbXBsc0BpZXRmLm9yZzsgdGljY3RvY0Bp
ZXRmLm9yZzsgUy4gRGF2YXJpOyBwd2UzQGlldGYub3JnOyBtcGxzLQ0KPiB0cEBpZXRmLm9yZw0K
PiBTdWJqZWN0OiBSZTogW21wbHMtdHBdIFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJh
ZnQNCj4gDQo+IEhpIEpvZWwsDQo+IA0KPiBUaGVyZSBhcmUgMiBhc3BlY3RzIHRvIHRoaXMgcHV6
emxlOg0KPiANCj4gMSkgSGFyZHdhcmUgc3VwcG9ydCBmb3IgMTU4OCBpbiBhIGRldmljZS4NCj4g
MikgU29mdHdhcmUgc3VwcG9ydCBmb3IgMTU4OCBpbiB0aGUgZm9ybSBvZiBhbGxvY2F0aW5nIGxh
YmVscyB0byBQVFANCj4gTFNQcw0KPiANCj4gQSByb3V0ZXIgdGhhdCB3YW50cyB0byBwZXJmb3Jt
IDE1ODggdGltZSBzdGFtcGluZyBtdXN0IGhhdmUgYm90aCAoMSkNCj4gYW5kICgyKSBmdW5jdGlv
bmFsaXR5LiBXaGlsZSBhIHJvdXRlciBpbiB0aGUgcGF0aCBvZiBhIFBUUCBMU1AgdGhhdA0KPiBk
b2VzIG5vdCBzdXBwb3J0ICgxKSBzaG91bGQgc3VwcG9ydCAoMikgYW5kIGFkdmVydGlzZSBsYWJl
bHMgZnJvbSBzb21lDQo+IGFyYml0cmFyeSByYW5nZSBmb3IgUFRQIExTUC4NCj4gDQo+IEl0IGlz
IHF1aXRlIGVhc3kgdG8gdXBncmFkZSBhIHJvdXRlciBzb2Z0d2FyZSBzbyB0aGF0IHdoZW4gaXQg
cmVjZWl2ZXMNCj4gUlNWUC1URSBsYWJlbCByZXF1ZXN0IHRvIGFzc2lnbiBsYWJlbCBmcm9tIGFu
IGFyYml0cmFyeSBsb2NhbCByYW5nZS4NCg0KSkQ6ICBXaGF0IGhhcHBlbnMgaW4gdGhlIGNhc2Ug
d2hlcmUgYSByb3V0ZXIncyBzb2Z0d2FyZSBoYXMgbm90IGJlZW4gdXBncmFkZWQ/DQoNCj4gDQo+
IFNvIEkgZG9uJ3Qgc2VlIGFueSBpc3N1ZSBoZXJlLg0KPiANCj4gVGhhbmtzLA0KPiBTaGFocmFt
DQo+IA0KPiANCj4gDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEpvZWwg
TS4gSGFscGVybiBbbWFpbHRvOmptaEBqb2VsaGFscGVybi5jb21dDQo+IFNlbnQ6IFRodXJzZGF5
LCBKdWx5IDE1LCAyMDEwIDEyOjA2IFBNDQo+IFRvOiBTaGFocmFtIERhdmFyaQ0KPiBDYzogTWFj
aCBDaGVuOyBTLiBEYXZhcmk7IEppYSBIRTsgbXBsc0BpZXRmLm9yZzsgcHdlM0BpZXRmLm9yZzsN
Cj4gdGljY3RvY0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW21w
bHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPiANCj4gQXJjaGl0ZWN0dXJhbGx5LCBh
cyBJIHVuZGVyc3RhbmQgdGhlIGRyYWZ0LCB0aGUgZG93bnN0cmVhbSBuZWlnaGJvciBvZg0KPiBh
DQo+IDE1ODggc3VwcG9ydGluZyBkZXZpY2UgKG9uIHRoZSBQVFAgY2FycnlpbmcgTFNQKSBtYXkg
bm90IGl0c2VsZiBiZSBhDQo+IDE1ODggc3VwcG9ydGluZyBkZXZpY2UuICBJcyB0aGF0IGNvcnJl
Y3Q/ICBJZiB0aGF0IGlzIG5vdCBjb3JyZWN0LCBpZg0KPiBpbnN0ZWFkIHRoZSBzdHJ1Y3R1cmUg
aXMgdGhhdCBQVFAgc3VwcG9ydGluZyBMU1BzIGFyZSBlc3RhYmxpc2hlZA0KPiBiZXR3ZWVuIGFk
amFjZW50IGVuaGFuY2VkIGRldmljZXMsIHRoZW4gSSBjYW4gc2VlIGhvdyBzb21lIHNvcnQgb2Yg
YQ0KPiBsYWJlbCByYW5nZSBtaWdodCBtYWtlIHNlbnNlLg0KPiANCj4gSWYgaG93ZXZlciwgdGhl
IGRvd25zdHJlYW0gbm9kZSB5b3UgcmVmZXIgdG8gbWF5IGJlIGFuIGV4aXN0aW5nIExTUiwNCj4g
dGhlbiBJIGRvIG5vdCBzZWUgaG93IHlvdSBjYW4gYXNrIGFuIGV4aXN0aW5nIExTUiB0byBhbGxv
Y2F0ZSBhIGxhYmVsDQo+IHJhbmdlIGZvciBhIGZ1bmN0aW9uIGl0IGRvZXMgbm90IHVuZGVyc3Rh
bmQuDQo+IA0KPiBZb3VycywNCj4gSm9lbA0KPiANCj4gU2hhaHJhbSBEYXZhcmkgd3JvdGU6DQo+
ID4gSGkgSm9lbCwNCj4gPg0KPiA+IEkgYWdyZWUgd2l0aCB5b3VyIGxvZ2ljLCBidXQgdGhlIGlk
ZWEgaXMgYSBiaXQgZGlmZmVyZW50Og0KPiA+DQo+ID4gQWxsIHdlIG5lZWQgaXMgYSBsYWJlbCBy
YW5nZSwgaXQgZG9lcyBub3QgbmVlZCB0byBiZSBnbG9iYWxseSB1bmlxdWUNCj4gaW4gdGhlIG5l
dHdvcmsgYW5kIGl0IGRvZXMNCj4gID5ub3QgZXZlbiBuZWVkIHRvIGJlIHRoZSBzYW1lIG9uIHRo
ZSBUeCBhbmQgUnggZGlyZWN0aW9uIG9mIHRoZSBzYW1lDQo+IGxpbmsuIEFsdGhvdWdoIHdlIG5l
ZWQgdGltZQ0KPiAgPnN0YW1waW5nIGJvdGggb24gUnggYW5kIG9uIFR4LCBidXQgb24gUnggYSBu
b2RlIGlzIGluIGNvbnRyb2wgb2YgaXRzDQo+IG93biBsYWJlbCBhbmQgb24gVHggdGhlDQo+ICA+
ZG93bnN0cmVhbSBub2RlIHNob3VsZCBhZHZlcnRpc2Ugc29tZSBsYWJlbCByYW5nZS4gV2hhdCB3
ZSBkb24ndCB3YW50DQo+IGlzIHRoYXQgdGhlIGRvd25zdHJlYW0NCj4gID5ub2RlIHRvIGFkdmVy
dGlzZSByYW5kb20gbGFiZWxzIGZvciBlYWNoIExTUCBjYXJyeWluZyBQVFAuDQo+ID4NCj4gPiBJ
IHdpbGwgdXBkYXRlIHRoZSBkcmFmdCB0byBtZW50aW9uIHRoYXQgdGhlIGxhYmVsIHJhbmdlIGRv
ZXMgbm90DQo+IHJlcXVpcmUgdG8gYmUgZ2xvYmFsIGJ1dCBpdCBjYW4NCj4gID5iZSBwZXItcGxh
dGZvcm0gb3IgZXZlbiBwZXItaW50ZXJmYWNlLg0KPiA+DQo+ID4gVGhhbmtzLA0KPiA+IFNoYWhy
YW0NCj4gPg0KPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4gRnJvbTogSm9lbCBN
LiBIYWxwZXJuIFttYWlsdG86am1oQGpvZWxoYWxwZXJuLmNvbV0NCj4gPiBTZW50OiBXZWRuZXNk
YXksIEp1bHkgMTQsIDIwMTAgODoyMSBQTQ0KPiA+IFRvOiBNYWNoIENoZW4NCj4gPiBDYzogU2hh
aHJhbSBEYXZhcmk7IFMuIERhdmFyaTsgSmlhIEhFOyBtcGxzQGlldGYub3JnOyBwd2UzQGlldGYu
b3JnOw0KPiB0aWNjdG9jQGlldGYub3JnOyBtcGxzLXRwQGlldGYub3JnDQo+ID4gU3ViamVjdDog
UmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCj4gPg0KPiA+IFJlbWVtYmVy
IHRoYXQgaWYgd2hhdCBpcyByZXF1aXJlZCBpcyB0aGF0IHRoZSBtZXNzYWdlIGFycml2aW5nIGF0
IHRoZQ0KPiA+IDE1ODggc3VwcG9ydGluZyBkZXZpY2UgaGF2ZSBhIGNlcnRhaW4gbGFiZWwgcmFu
Z2UsIHRoYXQgaXMgYSBwdXJlbHkNCj4gPiBsb2NhbCBtYXR0ZXIuICBBcyBsb25nIGFzIHRoZSBz
aW5nYWxpbmcgY2FycmllcyB0aGUgaW5kaWNhdGlvbiB0aGF0DQo+IHRoZQ0KPiA+IExTUCBpcyB0
byBiZSBkZWRpY2F0ZWQgdG8gMTU4OCB0cmFmZmljIChhIHJlYXNvbmFibGUgZXh0ZW5zaW9uIHRv
IHRoZQ0KPiA+IHNpZ25hbGluZyksIHRoZSBkb3duc3RyZWFtIHN3aXRjaCBjYW4gcGljayB3aGF0
IGxhYmVsIHRvIGFzc2lnbiB0bw0KPiB0aGF0IExTUC4NCj4gPg0KPiA+IElmIHRoZSBnb2FsIGlz
IHRvIGhhdmUgdGhlIG91dGdvaW5nIGxhYmVsIGJlIGZyb20gYSBzcGVjaWZpYyByYW5nZSwNCj4g
dGhhdA0KPiA+IGlzIGVzc2VudGlhbGx5IGltcG9zc2libGUgaW4gdGhlIHByb3Bvc2VkIGFyY2hp
dGVjdHVyZS4gIFRoZSBwcm9wb3NlZA0KPiA+IGFyY2hpdGVjdHVyZSBpcyBvbmUgaW4gd2hpY2gg
MTU4OCBzd2l0Y2hlcyBhcmUgcGVlcnMgd2l0aCBleGlzdGluZw0KPiBMU1JzDQo+ID4gdXNpbmcg
TVBMUy4gIEFzIHN1Y2gsIGluIG9yZGVyIHRvIGhhdmUgYSBsYWJlbCByYW5nZSBmb3Igb3V0Z29p
bmcNCj4gPiBsYWJlbHMsIHRoZSBleGlzdGluZyBNUExTIExTUiB3b3VsZCBzb21laG93IGhhdmUg
dG8ga25vdyBhYm91dCB0aGlzDQo+ID4gcmVzZXJ2ZWQgbGFiZWwgcmFuZ2UsIG5vdCB1c2UgdGhv
c2UgbGFiZWxzIGZvciBvdGhlciBwdXJwb3NlcywgYW5kDQo+ID4gYXNzaWduIHRob3NlIGxhYmVs
cyB0byAxNTg4IExTUHMuICBBbGwgb2Ygd2hpY2ggaXMNCj4gPiBub24tYmFja3dhcmRzLWNvbXBh
dGlibGUuICBJZiB0aGUgMTU4OCBMU1BzIHdlcmUgYWN0dWFsbHkNCj4gcHNldWRvd2lyZXMsDQo+
ID4gdHVubmVsZWQgb3ZlciBMU1BzLCB0aGVuIGFueSBudW1iZXIgb2YgdGhpbmdzIGFyZSBwb3Nz
aWJsZS4NCj4gPg0KPiA+IFlvdXJzLA0KPiA+IEpvZWwgTS4gSGFscGVybg0KPiA+DQo+ID4gTWFj
aCBDaGVuIHdyb3RlOg0KPiA+PiBIaSBTaGFocmFtLA0KPiA+Pg0KPiA+PiBJIGFncmVlIHRoYXQg
dGhlIGxhYmVsIHJhbmdlIGlkZWEgaXMgYW4gZWZmaWNpZW50IHdheSB0aGF0IGNvdWxkDQo+IHJl
ZHVjZQ0KPiA+PiB0aGUgc3RvcmFnZSByZXF1aXJlbWVudCBvZiBQSFkgY2hpcHMuDQo+ID4+DQo+
ID4+IEl0J3MgZWFzeSB0byByZXF1aXJlIG9uZSBvciBsaW1pdGVkIG5vZGVzIHRvIHJlc2VydmUg
YSBsYWJlbCByYW5nZSwNCj4gYnV0DQo+ID4+IElNSE8sIGl0IHZlcnkgZGlmZmljdXQgdG8gcmVx
dWlyZSBhbGwgbm9kZXMgb2YgYSBsYXJnZSBuZXR3b3JrIHRvIGRvDQo+ID4+IHRoaXMgYW5kIGV2
ZW4gd29yc2Ugd2hlbiBzb21lIGxhYmVscyBhcmUgYWxyZWFkeSB1c2VkIGJ5IG90aGVyIExTUHMs
DQo+ID4+IHVubGVzcyB0aGVyZSBhcmUgc29tZSBtZWNoYW5pc21zIHRvIG5lZ290aWF0ZS9hZHZl
cnRpc2UoZS5nLiwNCj4gZmxvb2RpbmcNCj4gPj4gdGhlIGxhYmVsIHJhbmdlIGJ5IElHUCB3aXRo
aW4gdGhlIG5ldHdvcmspIHRoZSBwcm9wZXIgbGFiZWwgcmFuZ2UNCj4gaGVuY2UNCj4gPj4gdG8g
YXZpb2QgbGFiZWwgY29sbGlzaW9uLg0KPiA+Pg0KPiA+PiBCZXN0IHJlZ2FyZHMsDQo+ID4+IE1h
Y2gNCj4gPj4NCj4gPj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCj4gPj4gRnJvbTogIlNoYWhyYW0gRGF2YXJpIiA8ZGF2YXJpQGJyb2FkY29tLmNv
bT4NCj4gPj4gU2VudDogVGh1cnNkYXksIEp1bHkgMTUsIDIwMTAgMTo1OCBBTQ0KPiA+PiBUbzog
Ik1hY2ggQ2hlbiIgPG1hY2hAaHVhd2VpLmNvbT47ICJTLiBEYXZhcmkiIDxkYXZhcmlzaEB5YWhv
by5jb20+Ow0KPiA+PiAiSmlhIEhFIiA8aGVqaWFAaHVhd2VpLmNvbT4NCj4gPj4gQ2M6IDxtcGxz
QGlldGYub3JnPjsgPHB3ZTNAaWV0Zi5vcmc+OyA8dGljY3RvY0BpZXRmLm9yZz47DQo+ID4+IDxt
cGxzLXRwQGlldGYub3JnPg0KPiA+PiBTdWJqZWN0OiBSRTogW21wbHNdIFtQV0UzXSAxNTg4IG92
ZXIgTVBMUyBkcmFmdA0KPiA+Pg0KPiA+Pj4gSGkgTWFjaCwNCj4gPj4+DQo+ID4+PiBXaGVuIGEg
c2VydmljZSBwcm92aWRlciB3YW50cyB0byBjcmVhdGUgdGhlc2UgUFRQIExTUHMsIHdoYXQgaXMN
Cj4gd3JvbmcNCj4gPj4+IHdpdGggYWxsb2NhdGluZyBhIHJhbmdlIG9mIGxhYmVscyBmb3IgdGhp
cyBwdXJwb3NlPyBUaGlzIGlzIHB1cmVseQ0KPiBhDQo+ID4+PiBzb2Z0d2FyZSBleGVyY2lzZS4g
VGhlcmUgYXJlIDIgbWlsbGlvbiBsYWJlbHMgYXZhaWxhYmxlIHRvIGVhY2gNCj4gbm9kZSwNCj4g
Pj4+IHdoeSBjYW4ndCBzb21lIG9mIHRoZW0gYmUgYWxsb2NhdGVkIGJ5IHNvZnR3YXJlIHRvIFBU
UD8NCj4gPj4+DQo+ID4+PiBJbiB0aGVvcnkgd2hhdCB5b3Ugc2F5IGlzIGNvcnJlY3QgYW5kIHNo
b3VsZCB3b3JrLCBidXQgaW4gcHJhY3RpY2UNCj4gPj4+IHRoZXJlIGlzIGEgZnVuY3Rpb24gY2Fs
bGVkIDEtc3RlcCBUcmFuc3BhcmVudCBjbG9ja2luZyB0aGF0DQo+IHJlcXVpcmVzDQo+ID4+PiB0
aW1lIHN0YW1waW5nIGF0IHRoZSBQSFkgKGltbWVkaWF0ZWx5IHdoZW4gdGhlIHBhY2tldCBpcyBy
ZWNlaXZlZA0KPiBvcg0KPiA+Pj4gdHJhbnNtaXR0ZWQpLiBQSFkgY2hpcHMgZG9uJ3QgaGF2ZSBD
QU0gb3IgbG90cyBvZiBtZW1vcnkgdG8gc3RvcmUgYQ0KPiA+Pj4gZmV3IHRob3VzYW5kIHJhbmRv
bSBsYWJlbHMuIFRoZSBsYWJlbCByYW5nZSB3aWxsIHNvbHZlIHRoYXQgcHJvYmxlbQ0KPiA+Pj4g
YW5kIGlzIGNvbnNpc3RlbnQgd2l0aCBNUExTIGFyY2hpdGVjdHVyZS4NCj4gPj4+DQo+ID4+PiBU
aGFua3MsDQo+ID4+PiBTaGFocmFtDQo+ID4+Pg0KPiA+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj4gPj4+IEZyb206IE1hY2ggQ2hlbiBbbWFpbHRvOm1hY2hAaHVhd2VpLmNvbV0NCj4g
Pj4+IFNlbnQ6IFdlZG5lc2RheSwgSnVseSAxNCwgMjAxMCAxOjUzIEFNDQo+ID4+PiBUbzogUy4g
RGF2YXJpOyBKaWEgSEU7IFNoYWhyYW0gRGF2YXJpDQo+ID4+PiBDYzogbXBsc0BpZXRmLm9yZzsg
cHdlM0BpZXRmLm9yZzsgdGljY3RvY0BpZXRmLm9yZzsgbXBscy0NCj4gdHBAaWV0Zi5vcmcNCj4g
Pj4+IFN1YmplY3Q6IFJlOiBbbXBsc10gW1BXRTNdIDE1ODggb3ZlciBNUExTIGRyYWZ0DQo+ID4+
Pg0KPiA+Pj4gSGkgU2hhaHJhbSwNCj4gPj4+DQo+ID4+PiBGcm9tIHRoZSB2aWV3IG9mIGltcGxl
bWVudGF0aW9uLCB0aGVyZSBpcyBubyBtb3JlIGRpZmZlcmVuY2UNCj4gYmV0d2Vlbg0KPiA+Pj4g
U0hPVUxEDQo+ID4+PiBhbmQgTVVTVCA6LSkNCj4gPj4+IEZvciBtZSwgdGhlIExhYmVsIFJhbmdl
IGlzIG1vcmUgbGlrZSBhIG1lY2hhbmltIHRvIG5vdGlmeSByZWxhdGVkDQo+ID4+PiBub2RlcyB0
aGF0DQo+ID4+PiBzb21lIExTUHMgYXJlIGRlZGljYXRlZCBmb3IgUFRQIG1lc3NhZ2VzIG90aGVy
IHRoYW4gdGhlIGNoaXBzDQo+IG1lbW9yeQ0KPiA+Pj4gbGltaXRhdGlvbiwgYmVjYXVzZSB0aGUg
bWVtb3J5IHJlc3RyaWN0aW9uIGlzIGFsd2F5cyB0aGVyZSB3aGF0ZXZlcg0KPiA+Pj4geW91IHVz
ZQ0KPiA+Pj4gTGFiZWwgUmFuZ2Ugb3Igbm90Lg0KPiA+Pj4gSU1ITywgc2luY2UgdGhlIG9iamVj
dGl2ZSBpcyB0byB0ZWxsIHJlbGF0ZWQgTVBMUyBub2RlcyB3aGljaCBMU1BzDQo+IGFyZQ0KPiA+
Pj4gUFRQDQo+ID4+PiBMU1BzLCBhbiBpbmRpY2F0aW9uIGluIHRoZSBzaWduYWxpbmcoUlNWUC1U
RS9HTVBMUy9MRFApIGlzIGVub3VnaA0KPiBhbmQNCj4gPj4+IHNlZW1zDQo+ID4+PiBtb3JlIGNv
bW1vbi4gQW5kIGl0IHdpbGwgYXZvaWQgdGhlIHN0cmljdCByZXF1aXJlbWVudCBvZiAidGhlDQo+
IG5ldHdvcmsgYW5kDQo+ID4+PiBhbGwgbm9kZXMgcmVxdWlyZWQgdG8gc3VwcG9ydCB0aGUgTGFi
ZWwgcmFuZ2UiLg0KPiA+Pj4gSW4gYWRkaXRpb24sIHRoZXJlIHNob3VsZCBiZSBzb21lIG1lY2hh
bmltcyhlLmcuLCBJU0lTL09TUEYNCj4gPj4+IGV4dGVuc2lvbnMpIGZvcg0KPiA+Pj4gbm9kZXMg
dG8gYWR2ZXJ0aXNlIHRoZWlyIFBUUCBjYXBhYmlsaXR5IGhlbmNlIHRvIGhlbHAgUFRQIExTUHMN
Cj4gPj4+IGNvbXB1dGF0aW9uLg0KPiA+Pj4NCj4gPj4+IEJlc3QgcmVnYXJkcywNCj4gPj4+IE1h
Y2gNCj4gPj4+DQo+ID4+Pg0KPiA+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCj4gPj4+IEZyb206ICJTLiBEYXZhcmkiIDxkYXZhcmlzaEB5YWhv
by5jb20+DQo+ID4+PiBTZW50OiBXZWRuZXNkYXksIEp1bHkgMTQsIDIwMTAgMjozMSBQTQ0KPiA+
Pj4gVG86ICJKaWEgSEUiIDxoZWppYUBodWF3ZWkuY29tPjsgIlNoYWhyYW0gRGF2YXJpIg0KPiA8
ZGF2YXJpQGJyb2FkY29tLmNvbT4NCj4gPj4+IENjOiA8bXBsc0BpZXRmLm9yZz47IDxwd2UzQGll
dGYub3JnPjsgPHRpY2N0b2NAaWV0Zi5vcmc+Ow0KPiA+Pj4gPG1wbHMtdHBAaWV0Zi5vcmc+DQo+
ID4+PiBTdWJqZWN0OiBSZTogW21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPiA+
Pj4NCj4gPj4+PiBIaSBKaWEsDQo+ID4+Pj4NCj4gPj4+PiBMYWJlbCByYW5nZSBpcyBhIFNIT1VM
RCByZXF1aXJlbWVudHMgYW5kIG5vdCBNVVNULiBUaGUgcmVhc29uIGZvcg0KPiBMYWJlbA0KPiA+
Pj4+IFJhbmdlIGlzDQo+ID4+Pj4gbWFpbmx5IGZvciBQSFkgY2hpcHMgdGhhdCBkb24ndCBoYXZl
IGxhcmdlIG1lbW9yeSBhbmQgY2FuJ3Qgc3RvcmUNCj4gYQ0KPiA+Pj4+IGxvdCBvZg0KPiA+Pj4+
IExhYmVscy4gT3RoZXJ3aXNlIHRoZSBQVFAgTFNQIGlzIHNldHVwIHZpYSBzaWduYWxpbmcgdGhh
dA0KPiBzcGVjaWZpZXMgdGhlDQo+ID4+Pj4gTFNQIGFzDQo+ID4+Pj4gY2FycnlpbmcgMTU4OC4N
Cj4gPj4+Pg0KPiA+Pj4+IFNvIHRoZSBhbnN3ZXIgaXMgdGhhdCBpZiBhIExhYmVsIHJhbmdlIGlz
IHVzZWQgaXQgbXVzdCBiZSBhIEdsb2JhbA0KPiByYW5nZQ0KPiA+Pj4+IHdpdGhpbg0KPiA+Pj4+
IGEgbmV0d29yayBhbmQgc2hvdWxkIG5vdCBiZSB1c2VkIGJ5IGFueSByb3V0ZXIgZm9yIG90aGVy
DQo+IGFwcGxpY2F0aW9ucy4NCj4gPj4+Pg0KPiA+Pj4+IFRoYW5rcywNCj4gPj4+PiBTaGFocmFt
DQo+ID4+Pj4NCj4gPj4+Pg0KPiA+Pj4+DQo+ID4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4gPj4+PiBGcm9tOiBKaWEgSEUgPGhlamlhQGh1YXdlaS5jb20+DQo+ID4+Pj4g
VG86IFNoYWhyYW0gRGF2YXJpIDxkYXZhcmlAYnJvYWRjb20uY29tPg0KPiA+Pj4+IENjOiBtcGxz
QGlldGYub3JnOyBwd2UzQGlldGYub3JnOyB0aWNjdG9jQGlldGYub3JnOyBtcGxzLQ0KPiB0cEBp
ZXRmLm9yZw0KPiA+Pj4+IFNlbnQ6IFR1ZSwgSnVseSAxMywgMjAxMCA5OjUwOjM3IFBNDQo+ID4+
Pj4gU3ViamVjdDogUmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCj4gPj4+
Pg0KPiA+Pj4+DQo+ID4+Pj4gSGkgU2hhaHJhbSwNCj4gPj4+Pg0KPiA+Pj4+IE9uZSBxdWVzdGlv
biBhYm91dCAiUFRQIExhYmVsIFJhbmdlIjoNCj4gPj4+Pg0KPiA+Pj4+IFRvIG15IGtub3dsZWRn
ZSwgbGFiZWwgaW4gTVBMUyBuZXR3b3JrIGlzIGEgbG9jYWwgIG1hdHRlci4gRm9yDQo+ID4+Pj4g
ZXhhbXBsZSwgd2UNCj4gPj4+PiBtYXkNCj4gPj4+PiBoYXZlIHBlci1pbnRlcmZhY2Ugb3IgcGVy
LXBsYXRmb3JtIGxhYmVsIHNwYWNlLiBXaWxsICB0aGlzDQo+IHNwZWNpZmljZWQNCj4gPj4+PiAi
UFRQDQo+ID4+Pj4gTGFiZWwNCj4gPj4+PiBSYW5nZSIgY29uZmxpY3Qgd2l0aCB0aGUgY3VycmVu
dCBpbi11c2UgbGFiZWxzICBmb3IgY29tbW9uIExTUHM/DQo+ID4+Pj4NCj4gPj4+Pg0KPiA+Pj4+
IEIuUi4NCj4gPj4+PiBKaWENCj4gPj4+Pg0KPiA+Pj4+IC0tLS0tIE9yaWdpbmFsIE1lc3NhZ2Ug
LS0tLS0NCj4gPj4+Pj4gRnJvbTogU2hhaHJhbSAgICBEYXZhcmkNCj4gPj4+Pj4gVG86IHRpY2N0
b2NAaWV0Zi5vcmcgOyBtcGxzQGlldGYub3JnIDsgbXBscy10cEBpZXRmLm9yZyA7DQo+IHB3ZTNA
aWV0Zi5vcmcNCj4gPj4+Pj4gU2VudDogVGh1cnNkYXksIEp1bHkgMDgsIDIwMTAgMzoxMiBBTQ0K
PiA+Pj4+PiBTdWJqZWN0OiBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCj4gPj4+Pj4NCj4g
Pj4+Pj4NCj4gPj4+Pj4gSGkgQWxsLA0KPiA+Pj4+Pg0KPiA+Pj4+PiBQbGVhc2UgZmluZCBhdHRh
Y2hlZCBvdXIgZmlyc3QgZHJhZnQgb2YgMTU4OCBvdmVyIE1QTFMuICAgIFNpbmNlDQo+IHdlDQo+
ID4+Pj4+IGhhdmUNCj4gPj4+Pj4gc29tZQ0KPiA+Pj4+PiB0ZWNobmljYWwgaXNzdWVzIGNvbnZl
cnRpbmcgdGhlIFdvcmQgZm9ybWF0IHRvIFR4dCB3ZSAgICBjb3VsZG7igJl0DQo+ID4+Pj4+IHVw
bG9hZA0KPiA+Pj4+PiB0aGUNCj4gPj4+Pj4gZHJhZnQgYmVmb3JlIHRoZSBjdXQtb2ZmIGRhdGUu
IEhvd2V2ZXIgd2Ugd2lsbCAgICBwcmVzZW50IHRoZQ0KPiBkcmFmdA0KPiA+Pj4+PiBpbiB0aGUN
Cj4gPj4+Pj4gbmV4dA0KPiA+Pj4+PiBJRVRGIG1lZXRpbmcgYW5kIHdpbGwgdXBsb2FkIHRoZSBk
cmFmdCBhZnRlciB0aGUgICAgbWVldGluZy4NCj4gPj4+Pj4NCj4gPj4+Pj4gTm90ZSB0aGF0IHRo
ZSBtYWluIFdHIGlzIFRpY1RvYyBidXQgbWF5IHJlcXVpcmUgICAgY29uc3VsdGF0aW9uDQo+IHdp
dGgNCj4gPj4+Pj4gTVBMUw0KPiA+Pj4+PiBhbmQNCj4gPj4+Pj4gUFdFMyBXR3MuDQo+ID4+Pj4+
DQo+ID4+Pj4+IFRoYW5rcywNCj4gPj4+Pj4gU2hhaHJhbSBEYXZhcmkNCj4gPj4+PiBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+Pj4+IHB3ZTMgbWFpbGluZyAgICBsaXN0DQo+
ID4+Pj4+IHB3ZTNAaWV0Zi5vcmcNCj4gPj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9wd2UzDQo+ID4+Pj4+DQo+ID4+Pj4NCj4gPj4+DQo+ID4+Pg0KPiA+Pj4+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+Pj4gbXBs
cyBtYWlsaW5nIGxpc3QNCj4gPj4+PiBtcGxzQGlldGYub3JnDQo+ID4+Pj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQo+ID4+Pj4NCj4gPj4+DQo+ID4+Pg0KPiA+
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+PiBt
cGxzIG1haWxpbmcgbGlzdA0KPiA+PiBtcGxzQGlldGYub3JnDQo+ID4+IGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0KPiA+DQo+IA0KPiBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBtcGxzLXRwIG1haWxpbmcgbGlzdA0K
PiBtcGxzLXRwQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vbXBscy10cA0K

From davari@broadcom.com  Thu Jul 15 13:37:50 2010
Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 055D43A69EC; Thu, 15 Jul 2010 13:37:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.501
X-Spam-Level: 
X-Spam-Status: No, score=-2.501 tagged_above=-999 required=5 tests=[AWL=0.098,  BAYES_00=-2.599]
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 Ky-kaIJLRKOp; Thu, 15 Jul 2010 13:37:48 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by core3.amsl.com (Postfix) with ESMTP id 382E33A698E; Thu, 15 Jul 2010 13:37:48 -0700 (PDT)
Received: from [10.16.192.224] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 15 Jul 2010 13:37:46 -0700
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Thu, 15 Jul 2010 13:37:46 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Date: Thu, 15 Jul 2010 13:37:45 -0700
Thread-Topic: [mpls] [PWE3] 1588 over MPLS draft
Thread-Index: AcskXMX/x6YXLiSDTEicZ0o1M1AOVwAAMPoQ
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6940EC29128@SJEXCHCCR02.corp.ad.broadcom.com>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c> <4C3E7E83.9080603@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F5C24.4070505@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC2911E@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F702B.5090704@joelhalpern.com>
In-Reply-To: <4C3F702B.5090704@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6021AE1010032025148-01-01
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 20:37:50 -0000

SGkgSm9lbCwNCg0KT0ssIGRvIHlvdSBoYXZlIGEgYmV0dGVyIHByb3Bvc2FsPw0KDQpUaHgNClNo
YWhyYW0NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEpvZWwgTS4gSGFscGVy
biBbbWFpbHRvOmptaEBqb2VsaGFscGVybi5jb21dIA0KU2VudDogVGh1cnNkYXksIEp1bHkgMTUs
IDIwMTAgMTozMiBQTQ0KVG86IFNoYWhyYW0gRGF2YXJpDQpDYzogbXBsc0BpZXRmLm9yZzsgcHdl
M0BpZXRmLm9yZzsgdGljY3RvY0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KU3ViamVjdDog
UmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCg0KSSBhbSBzb3JyeSwgYnV0
IHJlcXVpcmluZyBldmVyeSBMU1IgaW4gdGhlIGluZnJhc3RydWN0dXJlIHRvIGdldCBhIA0Kc29m
dHdhcmUgdXBncmFkZSBpbiBvcmRlciB0byBhbGxvdyBmb3IgdGhlIHByZXNlbmNlIG9mIDE1ODgt
c3VwcG9ydGluZyANCmRldmljZXMgaXMgYSBNQUpPUiBpc3N1ZS4gIEl0IGlzIE5PVCBiYWNrd2Fy
ZHMgY29tcGF0aWJsZS4gIE9wZXJhdG9ycyANCih3ZXRoZXIgc2VydmljZSBwcm92aWRlciBvciBl
bnRlcnByaXNlIElUKSBkbyBOT1QgbGlrZSBiZWluZyB0b2xkIHRoZXkgDQphaHZlIHRvIHVwZ3Jh
ZGUgdGhlIHNvZnR3YXJlIG9uIGFsbCBkZXZpY2VzIGluIHRoZWlyIG5ldHdvcmsgaW4gb3JkZXIg
dG8gDQphZGQgYSBjYXBhYmlsaXR5IHRoYXQgdGhvc2UgZGV2aWNlcyBhcmUgbm90IGVuZ2FnaW5n
IGluLg0KDQpXaGlsZSBvbmUgY2FuIGFyZ3VlIGFib3V0IHRoZSAiZWFzZSIgb2YgdGhlIHNwZWNp
ZmljIHNvZnR3YXJlIGNoYW5nZSwgDQp0aGVyZSBpcyBmcm9tIGFuIG9wZXJhdGlvbmFsIHBlcnNw
ZWN0aXZlIG5vIHN1Y2ggdGhpbmcgYXMgYW4gZWFzeSANCnVwZ3JhZGUgb2YgYW55IGRldmljZSwg
YW5kIHRoZXJlIGlzIGRlZmluaXRlbHkgbm8gc3VjaCB0aGluZyBhcyBhbiBlYXN5IA0KdXBncmFk
ZSBvZiBhbGwgdGhlIGRldmljZXMgaW4gdGhlIG5ldHdvcmsuDQoNCllvdXJzLA0KSm9lbA0KDQpT
aGFocmFtIERhdmFyaSB3cm90ZToNCj4gSGkgSm9lbCwNCj4gDQo+IFRoZXJlIGFyZSAyIGFzcGVj
dHMgdG8gdGhpcyBwdXp6bGU6DQo+IA0KPiAxKSBIYXJkd2FyZSBzdXBwb3J0IGZvciAxNTg4IGlu
IGEgZGV2aWNlLiANCj4gMikgU29mdHdhcmUgc3VwcG9ydCBmb3IgMTU4OCBpbiB0aGUgZm9ybSBv
ZiBhbGxvY2F0aW5nIGxhYmVscyB0byBQVFAgTFNQcw0KPiANCj4gQSByb3V0ZXIgdGhhdCB3YW50
cyB0byBwZXJmb3JtIDE1ODggdGltZSBzdGFtcGluZyBtdXN0IGhhdmUgYm90aCAoMSkgYW5kICgy
KSBmdW5jdGlvbmFsaXR5LiBXaGlsZSBhIHJvdXRlciBpbiANCiA+dGhlIHBhdGggb2YgYSBQVFAg
TFNQIHRoYXQgZG9lcyBub3Qgc3VwcG9ydCAoMSkgc2hvdWxkIHN1cHBvcnQgKDIpIGFuZCANCmFk
dmVydGlzZSBsYWJlbHMgZnJvbSBzb21lIGFyYml0cmFyeQ0KID5yYW5nZSBmb3IgUFRQIExTUC4N
Cj4gDQo+IEl0IGlzIHF1aXRlIGVhc3kgdG8gdXBncmFkZSBhIHJvdXRlciBzb2Z0d2FyZSBzbyB0
aGF0IHdoZW4gaXQgcmVjZWl2ZXMgUlNWUC1URSBsYWJlbCByZXF1ZXN0IHRvIGFzc2lnbiBsYWJl
bCANCiA+ZnJvbSBhbiBhcmJpdHJhcnkgbG9jYWwgcmFuZ2UuDQo+IA0KPiBTbyBJIGRvbid0IHNl
ZSBhbnkgaXNzdWUgaGVyZS4NCj4gDQo+IFRoYW5rcywNCj4gU2hhaHJhbQ0KPiANCj4gDQo+IA0K
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBKb2VsIE0uIEhhbHBlcm4gW21h
aWx0bzpqbWhAam9lbGhhbHBlcm4uY29tXSANCj4gU2VudDogVGh1cnNkYXksIEp1bHkgMTUsIDIw
MTAgMTI6MDYgUE0NCj4gVG86IFNoYWhyYW0gRGF2YXJpDQo+IENjOiBNYWNoIENoZW47IFMuIERh
dmFyaTsgSmlhIEhFOyBtcGxzQGlldGYub3JnOyBwd2UzQGlldGYub3JnOyB0aWNjdG9jQGlldGYu
b3JnOyBtcGxzLXRwQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbbXBsc10gW1BXRTNdIDE1ODgg
b3ZlciBNUExTIGRyYWZ0DQo+IA0KPiBBcmNoaXRlY3R1cmFsbHksIGFzIEkgdW5kZXJzdGFuZCB0
aGUgZHJhZnQsIHRoZSBkb3duc3RyZWFtIG5laWdoYm9yIG9mIGEgDQo+IDE1ODggc3VwcG9ydGlu
ZyBkZXZpY2UgKG9uIHRoZSBQVFAgY2FycnlpbmcgTFNQKSBtYXkgbm90IGl0c2VsZiBiZSBhIA0K
PiAxNTg4IHN1cHBvcnRpbmcgZGV2aWNlLiAgSXMgdGhhdCBjb3JyZWN0PyAgSWYgdGhhdCBpcyBu
b3QgY29ycmVjdCwgaWYgDQo+IGluc3RlYWQgdGhlIHN0cnVjdHVyZSBpcyB0aGF0IFBUUCBzdXBw
b3J0aW5nIExTUHMgYXJlIGVzdGFibGlzaGVkIA0KPiBiZXR3ZWVuIGFkamFjZW50IGVuaGFuY2Vk
IGRldmljZXMsIHRoZW4gSSBjYW4gc2VlIGhvdyBzb21lIHNvcnQgb2YgYSANCj4gbGFiZWwgcmFu
Z2UgbWlnaHQgbWFrZSBzZW5zZS4NCj4gDQo+IElmIGhvd2V2ZXIsIHRoZSBkb3duc3RyZWFtIG5v
ZGUgeW91IHJlZmVyIHRvIG1heSBiZSBhbiBleGlzdGluZyBMU1IsIA0KPiB0aGVuIEkgZG8gbm90
IHNlZSBob3cgeW91IGNhbiBhc2sgYW4gZXhpc3RpbmcgTFNSIHRvIGFsbG9jYXRlIGEgbGFiZWwg
DQo+IHJhbmdlIGZvciBhIGZ1bmN0aW9uIGl0IGRvZXMgbm90IHVuZGVyc3RhbmQuDQo+IA0KPiBZ
b3VycywNCj4gSm9lbA0KPiANCj4gU2hhaHJhbSBEYXZhcmkgd3JvdGU6DQo+PiBIaSBKb2VsLA0K
Pj4NCj4+IEkgYWdyZWUgd2l0aCB5b3VyIGxvZ2ljLCBidXQgdGhlIGlkZWEgaXMgYSBiaXQgZGlm
ZmVyZW50Og0KPj4NCj4+IEFsbCB3ZSBuZWVkIGlzIGEgbGFiZWwgcmFuZ2UsIGl0IGRvZXMgbm90
IG5lZWQgdG8gYmUgZ2xvYmFsbHkgdW5pcXVlIGluIHRoZSBuZXR3b3JrIGFuZCBpdCBkb2VzDQo+
ICA+bm90IGV2ZW4gbmVlZCB0byBiZSB0aGUgc2FtZSBvbiB0aGUgVHggYW5kIFJ4IGRpcmVjdGlv
biBvZiB0aGUgc2FtZSANCj4gbGluay4gQWx0aG91Z2ggd2UgbmVlZCB0aW1lDQo+ICA+c3RhbXBp
bmcgYm90aCBvbiBSeCBhbmQgb24gVHgsIGJ1dCBvbiBSeCBhIG5vZGUgaXMgaW4gY29udHJvbCBv
ZiBpdHMgDQo+IG93biBsYWJlbCBhbmQgb24gVHggdGhlDQo+ICA+ZG93bnN0cmVhbSBub2RlIHNo
b3VsZCBhZHZlcnRpc2Ugc29tZSBsYWJlbCByYW5nZS4gV2hhdCB3ZSBkb24ndCB3YW50IA0KPiBp
cyB0aGF0IHRoZSBkb3duc3RyZWFtDQo+ICA+bm9kZSB0byBhZHZlcnRpc2UgcmFuZG9tIGxhYmVs
cyBmb3IgZWFjaCBMU1AgY2FycnlpbmcgUFRQLg0KPj4gSSB3aWxsIHVwZGF0ZSB0aGUgZHJhZnQg
dG8gbWVudGlvbiB0aGF0IHRoZSBsYWJlbCByYW5nZSBkb2VzIG5vdCByZXF1aXJlIHRvIGJlIGds
b2JhbCBidXQgaXQgY2FuDQo+ICA+YmUgcGVyLXBsYXRmb3JtIG9yIGV2ZW4gcGVyLWludGVyZmFj
ZS4NCj4+IFRoYW5rcywNCj4+IFNoYWhyYW0NCj4+DQo+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KPj4gRnJvbTogSm9lbCBNLiBIYWxwZXJuIFttYWlsdG86am1oQGpvZWxoYWxwZXJuLmNv
bV0gDQo+PiBTZW50OiBXZWRuZXNkYXksIEp1bHkgMTQsIDIwMTAgODoyMSBQTQ0KPj4gVG86IE1h
Y2ggQ2hlbg0KPj4gQ2M6IFNoYWhyYW0gRGF2YXJpOyBTLiBEYXZhcmk7IEppYSBIRTsgbXBsc0Bp
ZXRmLm9yZzsgcHdlM0BpZXRmLm9yZzsgdGljY3RvY0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9y
Zw0KPj4gU3ViamVjdDogUmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCj4+
DQo+PiBSZW1lbWJlciB0aGF0IGlmIHdoYXQgaXMgcmVxdWlyZWQgaXMgdGhhdCB0aGUgbWVzc2Fn
ZSBhcnJpdmluZyBhdCB0aGUgDQo+PiAxNTg4IHN1cHBvcnRpbmcgZGV2aWNlIGhhdmUgYSBjZXJ0
YWluIGxhYmVsIHJhbmdlLCB0aGF0IGlzIGEgcHVyZWx5IA0KPj4gbG9jYWwgbWF0dGVyLiAgQXMg
bG9uZyBhcyB0aGUgc2luZ2FsaW5nIGNhcnJpZXMgdGhlIGluZGljYXRpb24gdGhhdCB0aGUgDQo+
PiBMU1AgaXMgdG8gYmUgZGVkaWNhdGVkIHRvIDE1ODggdHJhZmZpYyAoYSByZWFzb25hYmxlIGV4
dGVuc2lvbiB0byB0aGUgDQo+PiBzaWduYWxpbmcpLCB0aGUgZG93bnN0cmVhbSBzd2l0Y2ggY2Fu
IHBpY2sgd2hhdCBsYWJlbCB0byBhc3NpZ24gdG8gdGhhdCBMU1AuDQo+Pg0KPj4gSWYgdGhlIGdv
YWwgaXMgdG8gaGF2ZSB0aGUgb3V0Z29pbmcgbGFiZWwgYmUgZnJvbSBhIHNwZWNpZmljIHJhbmdl
LCB0aGF0IA0KPj4gaXMgZXNzZW50aWFsbHkgaW1wb3NzaWJsZSBpbiB0aGUgcHJvcG9zZWQgYXJj
aGl0ZWN0dXJlLiAgVGhlIHByb3Bvc2VkIA0KPj4gYXJjaGl0ZWN0dXJlIGlzIG9uZSBpbiB3aGlj
aCAxNTg4IHN3aXRjaGVzIGFyZSBwZWVycyB3aXRoIGV4aXN0aW5nIExTUnMgDQo+PiB1c2luZyBN
UExTLiAgQXMgc3VjaCwgaW4gb3JkZXIgdG8gaGF2ZSBhIGxhYmVsIHJhbmdlIGZvciBvdXRnb2lu
ZyANCj4+IGxhYmVscywgdGhlIGV4aXN0aW5nIE1QTFMgTFNSIHdvdWxkIHNvbWVob3cgaGF2ZSB0
byBrbm93IGFib3V0IHRoaXMgDQo+PiByZXNlcnZlZCBsYWJlbCByYW5nZSwgbm90IHVzZSB0aG9z
ZSBsYWJlbHMgZm9yIG90aGVyIHB1cnBvc2VzLCBhbmQgDQo+PiBhc3NpZ24gdGhvc2UgbGFiZWxz
IHRvIDE1ODggTFNQcy4gIEFsbCBvZiB3aGljaCBpcyANCj4+IG5vbi1iYWNrd2FyZHMtY29tcGF0
aWJsZS4gIElmIHRoZSAxNTg4IExTUHMgd2VyZSBhY3R1YWxseSBwc2V1ZG93aXJlcywgDQo+PiB0
dW5uZWxlZCBvdmVyIExTUHMsIHRoZW4gYW55IG51bWJlciBvZiB0aGluZ3MgYXJlIHBvc3NpYmxl
Lg0KPj4NCj4+IFlvdXJzLA0KPj4gSm9lbCBNLiBIYWxwZXJuDQo+Pg0KPj4gTWFjaCBDaGVuIHdy
b3RlOg0KPj4+IEhpIFNoYWhyYW0sDQo+Pj4NCj4+PiBJIGFncmVlIHRoYXQgdGhlIGxhYmVsIHJh
bmdlIGlkZWEgaXMgYW4gZWZmaWNpZW50IHdheSB0aGF0IGNvdWxkIHJlZHVjZSANCj4+PiB0aGUg
c3RvcmFnZSByZXF1aXJlbWVudCBvZiBQSFkgY2hpcHMuDQo+Pj4NCj4+PiBJdCdzIGVhc3kgdG8g
cmVxdWlyZSBvbmUgb3IgbGltaXRlZCBub2RlcyB0byByZXNlcnZlIGEgbGFiZWwgcmFuZ2UsIGJ1
dCANCj4+PiBJTUhPLCBpdCB2ZXJ5IGRpZmZpY3V0IHRvIHJlcXVpcmUgYWxsIG5vZGVzIG9mIGEg
bGFyZ2UgbmV0d29yayB0byBkbyANCj4+PiB0aGlzIGFuZCBldmVuIHdvcnNlIHdoZW4gc29tZSBs
YWJlbHMgYXJlIGFscmVhZHkgdXNlZCBieSBvdGhlciBMU1BzLCANCj4+PiB1bmxlc3MgdGhlcmUg
YXJlIHNvbWUgbWVjaGFuaXNtcyB0byBuZWdvdGlhdGUvYWR2ZXJ0aXNlKGUuZy4sIGZsb29kaW5n
IA0KPj4+IHRoZSBsYWJlbCByYW5nZSBieSBJR1Agd2l0aGluIHRoZSBuZXR3b3JrKSB0aGUgcHJv
cGVyIGxhYmVsIHJhbmdlIGhlbmNlIA0KPj4+IHRvIGF2aW9kIGxhYmVsIGNvbGxpc2lvbi4NCj4+
Pg0KPj4+IEJlc3QgcmVnYXJkcywNCj4+PiBNYWNoDQo+Pj4NCj4+PiAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPj4+IEZyb206ICJTaGFocmFtIERh
dmFyaSIgPGRhdmFyaUBicm9hZGNvbS5jb20+DQo+Pj4gU2VudDogVGh1cnNkYXksIEp1bHkgMTUs
IDIwMTAgMTo1OCBBTQ0KPj4+IFRvOiAiTWFjaCBDaGVuIiA8bWFjaEBodWF3ZWkuY29tPjsgIlMu
IERhdmFyaSIgPGRhdmFyaXNoQHlhaG9vLmNvbT47IA0KPj4+ICJKaWEgSEUiIDxoZWppYUBodWF3
ZWkuY29tPg0KPj4+IENjOiA8bXBsc0BpZXRmLm9yZz47IDxwd2UzQGlldGYub3JnPjsgPHRpY2N0
b2NAaWV0Zi5vcmc+OyANCj4+PiA8bXBscy10cEBpZXRmLm9yZz4NCj4+PiBTdWJqZWN0OiBSRTog
W21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPj4+DQo+Pj4+IEhpIE1hY2gsDQo+
Pj4+DQo+Pj4+IFdoZW4gYSBzZXJ2aWNlIHByb3ZpZGVyIHdhbnRzIHRvIGNyZWF0ZSB0aGVzZSBQ
VFAgTFNQcywgd2hhdCBpcyB3cm9uZyANCj4+Pj4gd2l0aCBhbGxvY2F0aW5nIGEgcmFuZ2Ugb2Yg
bGFiZWxzIGZvciB0aGlzIHB1cnBvc2U/IFRoaXMgaXMgcHVyZWx5IGEgDQo+Pj4+IHNvZnR3YXJl
IGV4ZXJjaXNlLiBUaGVyZSBhcmUgMiBtaWxsaW9uIGxhYmVscyBhdmFpbGFibGUgdG8gZWFjaCBu
b2RlLCANCj4+Pj4gd2h5IGNhbid0IHNvbWUgb2YgdGhlbSBiZSBhbGxvY2F0ZWQgYnkgc29mdHdh
cmUgdG8gUFRQPw0KPj4+Pg0KPj4+PiBJbiB0aGVvcnkgd2hhdCB5b3Ugc2F5IGlzIGNvcnJlY3Qg
YW5kIHNob3VsZCB3b3JrLCBidXQgaW4gcHJhY3RpY2UgDQo+Pj4+IHRoZXJlIGlzIGEgZnVuY3Rp
b24gY2FsbGVkIDEtc3RlcCBUcmFuc3BhcmVudCBjbG9ja2luZyB0aGF0IHJlcXVpcmVzIA0KPj4+
PiB0aW1lIHN0YW1waW5nIGF0IHRoZSBQSFkgKGltbWVkaWF0ZWx5IHdoZW4gdGhlIHBhY2tldCBp
cyByZWNlaXZlZCBvciANCj4+Pj4gdHJhbnNtaXR0ZWQpLiBQSFkgY2hpcHMgZG9uJ3QgaGF2ZSBD
QU0gb3IgbG90cyBvZiBtZW1vcnkgdG8gc3RvcmUgYSANCj4+Pj4gZmV3IHRob3VzYW5kIHJhbmRv
bSBsYWJlbHMuIFRoZSBsYWJlbCByYW5nZSB3aWxsIHNvbHZlIHRoYXQgcHJvYmxlbSANCj4+Pj4g
YW5kIGlzIGNvbnNpc3RlbnQgd2l0aCBNUExTIGFyY2hpdGVjdHVyZS4NCj4+Pj4NCj4+Pj4gVGhh
bmtzLA0KPj4+PiBTaGFocmFtDQo+Pj4+DQo+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQo+Pj4+IEZyb206IE1hY2ggQ2hlbiBbbWFpbHRvOm1hY2hAaHVhd2VpLmNvbV0NCj4+Pj4gU2Vu
dDogV2VkbmVzZGF5LCBKdWx5IDE0LCAyMDEwIDE6NTMgQU0NCj4+Pj4gVG86IFMuIERhdmFyaTsg
SmlhIEhFOyBTaGFocmFtIERhdmFyaQ0KPj4+PiBDYzogbXBsc0BpZXRmLm9yZzsgcHdlM0BpZXRm
Lm9yZzsgdGljY3RvY0BpZXRmLm9yZzsgbXBscy10cEBpZXRmLm9yZw0KPj4+PiBTdWJqZWN0OiBS
ZTogW21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPj4+Pg0KPj4+PiBIaSBTaGFo
cmFtLA0KPj4+Pg0KPj4+PiBGcm9tIHRoZSB2aWV3IG9mIGltcGxlbWVudGF0aW9uLCB0aGVyZSBp
cyBubyBtb3JlIGRpZmZlcmVuY2UgYmV0d2VlbiANCj4+Pj4gU0hPVUxEDQo+Pj4+IGFuZCBNVVNU
IDotKQ0KPj4+PiBGb3IgbWUsIHRoZSBMYWJlbCBSYW5nZSBpcyBtb3JlIGxpa2UgYSBtZWNoYW5p
bSB0byBub3RpZnkgcmVsYXRlZCANCj4+Pj4gbm9kZXMgdGhhdA0KPj4+PiBzb21lIExTUHMgYXJl
IGRlZGljYXRlZCBmb3IgUFRQIG1lc3NhZ2VzIG90aGVyIHRoYW4gdGhlIGNoaXBzIG1lbW9yeQ0K
Pj4+PiBsaW1pdGF0aW9uLCBiZWNhdXNlIHRoZSBtZW1vcnkgcmVzdHJpY3Rpb24gaXMgYWx3YXlz
IHRoZXJlIHdoYXRldmVyIA0KPj4+PiB5b3UgdXNlDQo+Pj4+IExhYmVsIFJhbmdlIG9yIG5vdC4N
Cj4+Pj4gSU1ITywgc2luY2UgdGhlIG9iamVjdGl2ZSBpcyB0byB0ZWxsIHJlbGF0ZWQgTVBMUyBu
b2RlcyB3aGljaCBMU1BzIGFyZSANCj4+Pj4gUFRQDQo+Pj4+IExTUHMsIGFuIGluZGljYXRpb24g
aW4gdGhlIHNpZ25hbGluZyhSU1ZQLVRFL0dNUExTL0xEUCkgaXMgZW5vdWdoIGFuZCANCj4+Pj4g
c2VlbXMNCj4+Pj4gbW9yZSBjb21tb24uIEFuZCBpdCB3aWxsIGF2b2lkIHRoZSBzdHJpY3QgcmVx
dWlyZW1lbnQgb2YgInRoZSBuZXR3b3JrIGFuZA0KPj4+PiBhbGwgbm9kZXMgcmVxdWlyZWQgdG8g
c3VwcG9ydCB0aGUgTGFiZWwgcmFuZ2UiLg0KPj4+PiBJbiBhZGRpdGlvbiwgdGhlcmUgc2hvdWxk
IGJlIHNvbWUgbWVjaGFuaW1zKGUuZy4sIElTSVMvT1NQRiANCj4+Pj4gZXh0ZW5zaW9ucykgZm9y
DQo+Pj4+IG5vZGVzIHRvIGFkdmVydGlzZSB0aGVpciBQVFAgY2FwYWJpbGl0eSBoZW5jZSB0byBo
ZWxwIFBUUCBMU1BzIA0KPj4+PiBjb21wdXRhdGlvbi4NCj4+Pj4NCj4+Pj4gQmVzdCByZWdhcmRz
LA0KPj4+PiBNYWNoDQo+Pj4+DQo+Pj4+DQo+Pj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+Pj4+IEZyb206ICJTLiBEYXZhcmkiIDxkYXZhcmlz
aEB5YWhvby5jb20+DQo+Pj4+IFNlbnQ6IFdlZG5lc2RheSwgSnVseSAxNCwgMjAxMCAyOjMxIFBN
DQo+Pj4+IFRvOiAiSmlhIEhFIiA8aGVqaWFAaHVhd2VpLmNvbT47ICJTaGFocmFtIERhdmFyaSIg
PGRhdmFyaUBicm9hZGNvbS5jb20+DQo+Pj4+IENjOiA8bXBsc0BpZXRmLm9yZz47IDxwd2UzQGll
dGYub3JnPjsgPHRpY2N0b2NAaWV0Zi5vcmc+OyANCj4+Pj4gPG1wbHMtdHBAaWV0Zi5vcmc+DQo+
Pj4+IFN1YmplY3Q6IFJlOiBbbXBsc10gW1BXRTNdIDE1ODggb3ZlciBNUExTIGRyYWZ0DQo+Pj4+
DQo+Pj4+PiBIaSBKaWEsDQo+Pj4+Pg0KPj4+Pj4gTGFiZWwgcmFuZ2UgaXMgYSBTSE9VTEQgcmVx
dWlyZW1lbnRzIGFuZCBub3QgTVVTVC4gVGhlIHJlYXNvbiBmb3IgTGFiZWwNCj4+Pj4+IFJhbmdl
IGlzDQo+Pj4+PiBtYWlubHkgZm9yIFBIWSBjaGlwcyB0aGF0IGRvbid0IGhhdmUgbGFyZ2UgbWVt
b3J5IGFuZCBjYW4ndCBzdG9yZSBhIA0KPj4+Pj4gbG90IG9mDQo+Pj4+PiBMYWJlbHMuIE90aGVy
d2lzZSB0aGUgUFRQIExTUCBpcyBzZXR1cCB2aWEgc2lnbmFsaW5nIHRoYXQgc3BlY2lmaWVzIHRo
ZQ0KPj4+Pj4gTFNQIGFzDQo+Pj4+PiBjYXJyeWluZyAxNTg4Lg0KPj4+Pj4NCj4+Pj4+IFNvIHRo
ZSBhbnN3ZXIgaXMgdGhhdCBpZiBhIExhYmVsIHJhbmdlIGlzIHVzZWQgaXQgbXVzdCBiZSBhIEds
b2JhbCByYW5nZQ0KPj4+Pj4gd2l0aGluDQo+Pj4+PiBhIG5ldHdvcmsgYW5kIHNob3VsZCBub3Qg
YmUgdXNlZCBieSBhbnkgcm91dGVyIGZvciBvdGhlciBhcHBsaWNhdGlvbnMuDQo+Pj4+Pg0KPj4+
Pj4gVGhhbmtzLA0KPj4+Pj4gU2hhaHJhbQ0KPj4+Pj4NCj4+Pj4+DQo+Pj4+Pg0KPj4+Pj4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4+IEZyb206IEppYSBIRSA8aGVqaWFA
aHVhd2VpLmNvbT4NCj4+Pj4+IFRvOiBTaGFocmFtIERhdmFyaSA8ZGF2YXJpQGJyb2FkY29tLmNv
bT4NCj4+Pj4+IENjOiBtcGxzQGlldGYub3JnOyBwd2UzQGlldGYub3JnOyB0aWNjdG9jQGlldGYu
b3JnOyBtcGxzLXRwQGlldGYub3JnDQo+Pj4+PiBTZW50OiBUdWUsIEp1bHkgMTMsIDIwMTAgOTo1
MDozNyBQTQ0KPj4+Pj4gU3ViamVjdDogUmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMg
ZHJhZnQNCj4+Pj4+DQo+Pj4+Pg0KPj4+Pj4gSGkgU2hhaHJhbSwNCj4+Pj4+DQo+Pj4+PiBPbmUg
cXVlc3Rpb24gYWJvdXQgIlBUUCBMYWJlbCBSYW5nZSI6DQo+Pj4+Pg0KPj4+Pj4gVG8gbXkga25v
d2xlZGdlLCBsYWJlbCBpbiBNUExTIG5ldHdvcmsgaXMgYSBsb2NhbCAgbWF0dGVyLiBGb3IgDQo+
Pj4+PiBleGFtcGxlLCB3ZQ0KPj4+Pj4gbWF5DQo+Pj4+PiBoYXZlIHBlci1pbnRlcmZhY2Ugb3Ig
cGVyLXBsYXRmb3JtIGxhYmVsIHNwYWNlLiBXaWxsICB0aGlzIHNwZWNpZmljZWQgDQo+Pj4+PiAi
UFRQDQo+Pj4+PiBMYWJlbA0KPj4+Pj4gUmFuZ2UiIGNvbmZsaWN0IHdpdGggdGhlIGN1cnJlbnQg
aW4tdXNlIGxhYmVscyAgZm9yIGNvbW1vbiBMU1BzPw0KPj4+Pj4NCj4+Pj4+DQo+Pj4+PiBCLlIu
DQo+Pj4+PiBKaWENCj4+Pj4+DQo+Pj4+PiAtLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tDQo+
Pj4+Pj4gRnJvbTogU2hhaHJhbSAgICBEYXZhcmkNCj4+Pj4+PiBUbzogdGljY3RvY0BpZXRmLm9y
ZyA7IG1wbHNAaWV0Zi5vcmcgOyBtcGxzLXRwQGlldGYub3JnIDsgcHdlM0BpZXRmLm9yZw0KPj4+
Pj4+IFNlbnQ6IFRodXJzZGF5LCBKdWx5IDA4LCAyMDEwIDM6MTIgQU0NCj4+Pj4+PiBTdWJqZWN0
OiBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCj4+Pj4+Pg0KPj4+Pj4+DQo+Pj4+Pj4gSGkg
QWxsLA0KPj4+Pj4+DQo+Pj4+Pj4gUGxlYXNlIGZpbmQgYXR0YWNoZWQgb3VyIGZpcnN0IGRyYWZ0
IG9mIDE1ODggb3ZlciBNUExTLiAgICBTaW5jZSB3ZSANCj4+Pj4+PiBoYXZlDQo+Pj4+Pj4gc29t
ZQ0KPj4+Pj4+IHRlY2huaWNhbCBpc3N1ZXMgY29udmVydGluZyB0aGUgV29yZCBmb3JtYXQgdG8g
VHh0IHdlICAgIGNvdWxkbuKAmXQgDQo+Pj4+Pj4gdXBsb2FkDQo+Pj4+Pj4gdGhlDQo+Pj4+Pj4g
ZHJhZnQgYmVmb3JlIHRoZSBjdXQtb2ZmIGRhdGUuIEhvd2V2ZXIgd2Ugd2lsbCAgICBwcmVzZW50
IHRoZSBkcmFmdCANCj4+Pj4+PiBpbiB0aGUNCj4+Pj4+PiBuZXh0DQo+Pj4+Pj4gSUVURiBtZWV0
aW5nIGFuZCB3aWxsIHVwbG9hZCB0aGUgZHJhZnQgYWZ0ZXIgdGhlICAgIG1lZXRpbmcuDQo+Pj4+
Pj4NCj4+Pj4+PiBOb3RlIHRoYXQgdGhlIG1haW4gV0cgaXMgVGljVG9jIGJ1dCBtYXkgcmVxdWly
ZSAgICBjb25zdWx0YXRpb24gd2l0aCANCj4+Pj4+PiBNUExTDQo+Pj4+Pj4gYW5kDQo+Pj4+Pj4g
UFdFMyBXR3MuDQo+Pj4+Pj4NCj4+Pj4+PiBUaGFua3MsDQo+Pj4+Pj4gU2hhaHJhbSBEYXZhcmkN
Cj4+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4+PiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+Pj4+IHB3ZTMgbWFpbGlu
ZyAgICBsaXN0DQo+Pj4+Pj4gcHdlM0BpZXRmLm9yZw0KPj4+Pj4+IGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vcHdlMw0KPj4+Pj4+DQo+Pj4+DQo+Pj4+PiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+Pj4gbXBscyBtYWlsaW5n
IGxpc3QNCj4+Pj4+IG1wbHNAaWV0Zi5vcmcNCj4+Pj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vbXBscw0KPj4+Pj4NCj4+Pj4NCj4+PiBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+IG1wbHMgbWFpbGluZyBsaXN0DQo+Pj4g
bXBsc0BpZXRmLm9yZw0KPj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
bXBscw0KPiANCg0K


From davari@broadcom.com  Thu Jul 15 13:44:44 2010
Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 045BF3A698E; Thu, 15 Jul 2010 13:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599]
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 3aB1NYcH+qYA; Thu, 15 Jul 2010 13:44:42 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id 622CE3A6A94; Thu, 15 Jul 2010 13:44:42 -0700 (PDT)
Received: from [10.16.192.232] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 15 Jul 2010 13:44:43 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Thu, 15 Jul 2010 13:44:43 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Date: Thu, 15 Jul 2010 13:44:42 -0700
Thread-Topic: [mpls] [PWE3] 1588 over MPLS draft
Thread-Index: AcskXMX/x6YXLiSDTEicZ0o1M1AOVwAAXvpg
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6940EC2912A@SJEXCHCCR02.corp.ad.broadcom.com>
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c> <4C3E7E83.9080603@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F5C24.4070505@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC2911E@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F702B.5090704@joelhalpern.com>
In-Reply-To: <4C3F702B.5090704@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6021ACB13KC40601931-01-01
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 20:44:44 -0000

QnkgdGhlIHdheSB0aGVyZSBpcyBubyBuZWVkIHRvIHVwZ3JhZGUgdGhlIHNvZnR3YXJlIGZvciBh
bGwgcm91dGVycyBpbiB0aGUgbmV0d29yaywganVzdCB0aGUgcm91dGVycyBkaXJlY3RseSBhZGph
Y2VudCB0byBhIFBUUC1hd2FyZSByb3V0ZXIuDQoNClRoeA0KU2hhaHJhbQ0KDQotLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSm9lbCBNLiBIYWxwZXJuIFttYWlsdG86am1oQGpvZWxo
YWxwZXJuLmNvbV0gDQpTZW50OiBUaHVyc2RheSwgSnVseSAxNSwgMjAxMCAxOjMyIFBNDQpUbzog
U2hhaHJhbSBEYXZhcmkNCkNjOiBtcGxzQGlldGYub3JnOyBwd2UzQGlldGYub3JnOyB0aWNjdG9j
QGlldGYub3JnOyBtcGxzLXRwQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW21wbHNdIFtQV0UzXSAx
NTg4IG92ZXIgTVBMUyBkcmFmdA0KDQpJIGFtIHNvcnJ5LCBidXQgcmVxdWlyaW5nIGV2ZXJ5IExT
UiBpbiB0aGUgaW5mcmFzdHJ1Y3R1cmUgdG8gZ2V0IGEgDQpzb2Z0d2FyZSB1cGdyYWRlIGluIG9y
ZGVyIHRvIGFsbG93IGZvciB0aGUgcHJlc2VuY2Ugb2YgMTU4OC1zdXBwb3J0aW5nIA0KZGV2aWNl
cyBpcyBhIE1BSk9SIGlzc3VlLiAgSXQgaXMgTk9UIGJhY2t3YXJkcyBjb21wYXRpYmxlLiAgT3Bl
cmF0b3JzIA0KKHdldGhlciBzZXJ2aWNlIHByb3ZpZGVyIG9yIGVudGVycHJpc2UgSVQpIGRvIE5P
VCBsaWtlIGJlaW5nIHRvbGQgdGhleSANCmFodmUgdG8gdXBncmFkZSB0aGUgc29mdHdhcmUgb24g
YWxsIGRldmljZXMgaW4gdGhlaXIgbmV0d29yayBpbiBvcmRlciB0byANCmFkZCBhIGNhcGFiaWxp
dHkgdGhhdCB0aG9zZSBkZXZpY2VzIGFyZSBub3QgZW5nYWdpbmcgaW4uDQoNCldoaWxlIG9uZSBj
YW4gYXJndWUgYWJvdXQgdGhlICJlYXNlIiBvZiB0aGUgc3BlY2lmaWMgc29mdHdhcmUgY2hhbmdl
LCANCnRoZXJlIGlzIGZyb20gYW4gb3BlcmF0aW9uYWwgcGVyc3BlY3RpdmUgbm8gc3VjaCB0aGlu
ZyBhcyBhbiBlYXN5IA0KdXBncmFkZSBvZiBhbnkgZGV2aWNlLCBhbmQgdGhlcmUgaXMgZGVmaW5p
dGVseSBubyBzdWNoIHRoaW5nIGFzIGFuIGVhc3kgDQp1cGdyYWRlIG9mIGFsbCB0aGUgZGV2aWNl
cyBpbiB0aGUgbmV0d29yay4NCg0KWW91cnMsDQpKb2VsDQoNClNoYWhyYW0gRGF2YXJpIHdyb3Rl
Og0KPiBIaSBKb2VsLA0KPiANCj4gVGhlcmUgYXJlIDIgYXNwZWN0cyB0byB0aGlzIHB1enpsZToN
Cj4gDQo+IDEpIEhhcmR3YXJlIHN1cHBvcnQgZm9yIDE1ODggaW4gYSBkZXZpY2UuIA0KPiAyKSBT
b2Z0d2FyZSBzdXBwb3J0IGZvciAxNTg4IGluIHRoZSBmb3JtIG9mIGFsbG9jYXRpbmcgbGFiZWxz
IHRvIFBUUCBMU1BzDQo+IA0KPiBBIHJvdXRlciB0aGF0IHdhbnRzIHRvIHBlcmZvcm0gMTU4OCB0
aW1lIHN0YW1waW5nIG11c3QgaGF2ZSBib3RoICgxKSBhbmQgKDIpIGZ1bmN0aW9uYWxpdHkuIFdo
aWxlIGEgcm91dGVyIGluIA0KID50aGUgcGF0aCBvZiBhIFBUUCBMU1AgdGhhdCBkb2VzIG5vdCBz
dXBwb3J0ICgxKSBzaG91bGQgc3VwcG9ydCAoMikgYW5kIA0KYWR2ZXJ0aXNlIGxhYmVscyBmcm9t
IHNvbWUgYXJiaXRyYXJ5DQogPnJhbmdlIGZvciBQVFAgTFNQLg0KPiANCj4gSXQgaXMgcXVpdGUg
ZWFzeSB0byB1cGdyYWRlIGEgcm91dGVyIHNvZnR3YXJlIHNvIHRoYXQgd2hlbiBpdCByZWNlaXZl
cyBSU1ZQLVRFIGxhYmVsIHJlcXVlc3QgdG8gYXNzaWduIGxhYmVsIA0KID5mcm9tIGFuIGFyYml0
cmFyeSBsb2NhbCByYW5nZS4NCj4gDQo+IFNvIEkgZG9uJ3Qgc2VlIGFueSBpc3N1ZSBoZXJlLg0K
PiANCj4gVGhhbmtzLA0KPiBTaGFocmFtDQo+IA0KPiANCj4gDQo+IC0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+IEZyb206IEpvZWwgTS4gSGFscGVybiBbbWFpbHRvOmptaEBqb2VsaGFscGVy
bi5jb21dIA0KPiBTZW50OiBUaHVyc2RheSwgSnVseSAxNSwgMjAxMCAxMjowNiBQTQ0KPiBUbzog
U2hhaHJhbSBEYXZhcmkNCj4gQ2M6IE1hY2ggQ2hlbjsgUy4gRGF2YXJpOyBKaWEgSEU7IG1wbHNA
aWV0Zi5vcmc7IHB3ZTNAaWV0Zi5vcmc7IHRpY2N0b2NAaWV0Zi5vcmc7IG1wbHMtdHBAaWV0Zi5v
cmcNCj4gU3ViamVjdDogUmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCj4g
DQo+IEFyY2hpdGVjdHVyYWxseSwgYXMgSSB1bmRlcnN0YW5kIHRoZSBkcmFmdCwgdGhlIGRvd25z
dHJlYW0gbmVpZ2hib3Igb2YgYSANCj4gMTU4OCBzdXBwb3J0aW5nIGRldmljZSAob24gdGhlIFBU
UCBjYXJyeWluZyBMU1ApIG1heSBub3QgaXRzZWxmIGJlIGEgDQo+IDE1ODggc3VwcG9ydGluZyBk
ZXZpY2UuICBJcyB0aGF0IGNvcnJlY3Q/ICBJZiB0aGF0IGlzIG5vdCBjb3JyZWN0LCBpZiANCj4g
aW5zdGVhZCB0aGUgc3RydWN0dXJlIGlzIHRoYXQgUFRQIHN1cHBvcnRpbmcgTFNQcyBhcmUgZXN0
YWJsaXNoZWQgDQo+IGJldHdlZW4gYWRqYWNlbnQgZW5oYW5jZWQgZGV2aWNlcywgdGhlbiBJIGNh
biBzZWUgaG93IHNvbWUgc29ydCBvZiBhIA0KPiBsYWJlbCByYW5nZSBtaWdodCBtYWtlIHNlbnNl
Lg0KPiANCj4gSWYgaG93ZXZlciwgdGhlIGRvd25zdHJlYW0gbm9kZSB5b3UgcmVmZXIgdG8gbWF5
IGJlIGFuIGV4aXN0aW5nIExTUiwgDQo+IHRoZW4gSSBkbyBub3Qgc2VlIGhvdyB5b3UgY2FuIGFz
ayBhbiBleGlzdGluZyBMU1IgdG8gYWxsb2NhdGUgYSBsYWJlbCANCj4gcmFuZ2UgZm9yIGEgZnVu
Y3Rpb24gaXQgZG9lcyBub3QgdW5kZXJzdGFuZC4NCj4gDQo+IFlvdXJzLA0KPiBKb2VsDQo+IA0K
PiBTaGFocmFtIERhdmFyaSB3cm90ZToNCj4+IEhpIEpvZWwsDQo+Pg0KPj4gSSBhZ3JlZSB3aXRo
IHlvdXIgbG9naWMsIGJ1dCB0aGUgaWRlYSBpcyBhIGJpdCBkaWZmZXJlbnQ6DQo+Pg0KPj4gQWxs
IHdlIG5lZWQgaXMgYSBsYWJlbCByYW5nZSwgaXQgZG9lcyBub3QgbmVlZCB0byBiZSBnbG9iYWxs
eSB1bmlxdWUgaW4gdGhlIG5ldHdvcmsgYW5kIGl0IGRvZXMNCj4gID5ub3QgZXZlbiBuZWVkIHRv
IGJlIHRoZSBzYW1lIG9uIHRoZSBUeCBhbmQgUnggZGlyZWN0aW9uIG9mIHRoZSBzYW1lIA0KPiBs
aW5rLiBBbHRob3VnaCB3ZSBuZWVkIHRpbWUNCj4gID5zdGFtcGluZyBib3RoIG9uIFJ4IGFuZCBv
biBUeCwgYnV0IG9uIFJ4IGEgbm9kZSBpcyBpbiBjb250cm9sIG9mIGl0cyANCj4gb3duIGxhYmVs
IGFuZCBvbiBUeCB0aGUNCj4gID5kb3duc3RyZWFtIG5vZGUgc2hvdWxkIGFkdmVydGlzZSBzb21l
IGxhYmVsIHJhbmdlLiBXaGF0IHdlIGRvbid0IHdhbnQgDQo+IGlzIHRoYXQgdGhlIGRvd25zdHJl
YW0NCj4gID5ub2RlIHRvIGFkdmVydGlzZSByYW5kb20gbGFiZWxzIGZvciBlYWNoIExTUCBjYXJy
eWluZyBQVFAuDQo+PiBJIHdpbGwgdXBkYXRlIHRoZSBkcmFmdCB0byBtZW50aW9uIHRoYXQgdGhl
IGxhYmVsIHJhbmdlIGRvZXMgbm90IHJlcXVpcmUgdG8gYmUgZ2xvYmFsIGJ1dCBpdCBjYW4NCj4g
ID5iZSBwZXItcGxhdGZvcm0gb3IgZXZlbiBwZXItaW50ZXJmYWNlLg0KPj4gVGhhbmtzLA0KPj4g
U2hhaHJhbQ0KPj4NCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiBGcm9tOiBKb2Vs
IE0uIEhhbHBlcm4gW21haWx0bzpqbWhAam9lbGhhbHBlcm4uY29tXSANCj4+IFNlbnQ6IFdlZG5l
c2RheSwgSnVseSAxNCwgMjAxMCA4OjIxIFBNDQo+PiBUbzogTWFjaCBDaGVuDQo+PiBDYzogU2hh
aHJhbSBEYXZhcmk7IFMuIERhdmFyaTsgSmlhIEhFOyBtcGxzQGlldGYub3JnOyBwd2UzQGlldGYu
b3JnOyB0aWNjdG9jQGlldGYub3JnOyBtcGxzLXRwQGlldGYub3JnDQo+PiBTdWJqZWN0OiBSZTog
W21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPj4NCj4+IFJlbWVtYmVyIHRoYXQg
aWYgd2hhdCBpcyByZXF1aXJlZCBpcyB0aGF0IHRoZSBtZXNzYWdlIGFycml2aW5nIGF0IHRoZSAN
Cj4+IDE1ODggc3VwcG9ydGluZyBkZXZpY2UgaGF2ZSBhIGNlcnRhaW4gbGFiZWwgcmFuZ2UsIHRo
YXQgaXMgYSBwdXJlbHkgDQo+PiBsb2NhbCBtYXR0ZXIuICBBcyBsb25nIGFzIHRoZSBzaW5nYWxp
bmcgY2FycmllcyB0aGUgaW5kaWNhdGlvbiB0aGF0IHRoZSANCj4+IExTUCBpcyB0byBiZSBkZWRp
Y2F0ZWQgdG8gMTU4OCB0cmFmZmljIChhIHJlYXNvbmFibGUgZXh0ZW5zaW9uIHRvIHRoZSANCj4+
IHNpZ25hbGluZyksIHRoZSBkb3duc3RyZWFtIHN3aXRjaCBjYW4gcGljayB3aGF0IGxhYmVsIHRv
IGFzc2lnbiB0byB0aGF0IExTUC4NCj4+DQo+PiBJZiB0aGUgZ29hbCBpcyB0byBoYXZlIHRoZSBv
dXRnb2luZyBsYWJlbCBiZSBmcm9tIGEgc3BlY2lmaWMgcmFuZ2UsIHRoYXQgDQo+PiBpcyBlc3Nl
bnRpYWxseSBpbXBvc3NpYmxlIGluIHRoZSBwcm9wb3NlZCBhcmNoaXRlY3R1cmUuICBUaGUgcHJv
cG9zZWQgDQo+PiBhcmNoaXRlY3R1cmUgaXMgb25lIGluIHdoaWNoIDE1ODggc3dpdGNoZXMgYXJl
IHBlZXJzIHdpdGggZXhpc3RpbmcgTFNScyANCj4+IHVzaW5nIE1QTFMuICBBcyBzdWNoLCBpbiBv
cmRlciB0byBoYXZlIGEgbGFiZWwgcmFuZ2UgZm9yIG91dGdvaW5nIA0KPj4gbGFiZWxzLCB0aGUg
ZXhpc3RpbmcgTVBMUyBMU1Igd291bGQgc29tZWhvdyBoYXZlIHRvIGtub3cgYWJvdXQgdGhpcyAN
Cj4+IHJlc2VydmVkIGxhYmVsIHJhbmdlLCBub3QgdXNlIHRob3NlIGxhYmVscyBmb3Igb3RoZXIg
cHVycG9zZXMsIGFuZCANCj4+IGFzc2lnbiB0aG9zZSBsYWJlbHMgdG8gMTU4OCBMU1BzLiAgQWxs
IG9mIHdoaWNoIGlzIA0KPj4gbm9uLWJhY2t3YXJkcy1jb21wYXRpYmxlLiAgSWYgdGhlIDE1ODgg
TFNQcyB3ZXJlIGFjdHVhbGx5IHBzZXVkb3dpcmVzLCANCj4+IHR1bm5lbGVkIG92ZXIgTFNQcywg
dGhlbiBhbnkgbnVtYmVyIG9mIHRoaW5ncyBhcmUgcG9zc2libGUuDQo+Pg0KPj4gWW91cnMsDQo+
PiBKb2VsIE0uIEhhbHBlcm4NCj4+DQo+PiBNYWNoIENoZW4gd3JvdGU6DQo+Pj4gSGkgU2hhaHJh
bSwNCj4+Pg0KPj4+IEkgYWdyZWUgdGhhdCB0aGUgbGFiZWwgcmFuZ2UgaWRlYSBpcyBhbiBlZmZp
Y2llbnQgd2F5IHRoYXQgY291bGQgcmVkdWNlIA0KPj4+IHRoZSBzdG9yYWdlIHJlcXVpcmVtZW50
IG9mIFBIWSBjaGlwcy4NCj4+Pg0KPj4+IEl0J3MgZWFzeSB0byByZXF1aXJlIG9uZSBvciBsaW1p
dGVkIG5vZGVzIHRvIHJlc2VydmUgYSBsYWJlbCByYW5nZSwgYnV0IA0KPj4+IElNSE8sIGl0IHZl
cnkgZGlmZmljdXQgdG8gcmVxdWlyZSBhbGwgbm9kZXMgb2YgYSBsYXJnZSBuZXR3b3JrIHRvIGRv
IA0KPj4+IHRoaXMgYW5kIGV2ZW4gd29yc2Ugd2hlbiBzb21lIGxhYmVscyBhcmUgYWxyZWFkeSB1
c2VkIGJ5IG90aGVyIExTUHMsIA0KPj4+IHVubGVzcyB0aGVyZSBhcmUgc29tZSBtZWNoYW5pc21z
IHRvIG5lZ290aWF0ZS9hZHZlcnRpc2UoZS5nLiwgZmxvb2RpbmcgDQo+Pj4gdGhlIGxhYmVsIHJh
bmdlIGJ5IElHUCB3aXRoaW4gdGhlIG5ldHdvcmspIHRoZSBwcm9wZXIgbGFiZWwgcmFuZ2UgaGVu
Y2UgDQo+Pj4gdG8gYXZpb2QgbGFiZWwgY29sbGlzaW9uLg0KPj4+DQo+Pj4gQmVzdCByZWdhcmRz
LA0KPj4+IE1hY2gNCj4+Pg0KPj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tDQo+Pj4gRnJvbTogIlNoYWhyYW0gRGF2YXJpIiA8ZGF2YXJpQGJyb2Fk
Y29tLmNvbT4NCj4+PiBTZW50OiBUaHVyc2RheSwgSnVseSAxNSwgMjAxMCAxOjU4IEFNDQo+Pj4g
VG86ICJNYWNoIENoZW4iIDxtYWNoQGh1YXdlaS5jb20+OyAiUy4gRGF2YXJpIiA8ZGF2YXJpc2hA
eWFob28uY29tPjsgDQo+Pj4gIkppYSBIRSIgPGhlamlhQGh1YXdlaS5jb20+DQo+Pj4gQ2M6IDxt
cGxzQGlldGYub3JnPjsgPHB3ZTNAaWV0Zi5vcmc+OyA8dGljY3RvY0BpZXRmLm9yZz47IA0KPj4+
IDxtcGxzLXRwQGlldGYub3JnPg0KPj4+IFN1YmplY3Q6IFJFOiBbbXBsc10gW1BXRTNdIDE1ODgg
b3ZlciBNUExTIGRyYWZ0DQo+Pj4NCj4+Pj4gSGkgTWFjaCwNCj4+Pj4NCj4+Pj4gV2hlbiBhIHNl
cnZpY2UgcHJvdmlkZXIgd2FudHMgdG8gY3JlYXRlIHRoZXNlIFBUUCBMU1BzLCB3aGF0IGlzIHdy
b25nIA0KPj4+PiB3aXRoIGFsbG9jYXRpbmcgYSByYW5nZSBvZiBsYWJlbHMgZm9yIHRoaXMgcHVy
cG9zZT8gVGhpcyBpcyBwdXJlbHkgYSANCj4+Pj4gc29mdHdhcmUgZXhlcmNpc2UuIFRoZXJlIGFy
ZSAyIG1pbGxpb24gbGFiZWxzIGF2YWlsYWJsZSB0byBlYWNoIG5vZGUsIA0KPj4+PiB3aHkgY2Fu
J3Qgc29tZSBvZiB0aGVtIGJlIGFsbG9jYXRlZCBieSBzb2Z0d2FyZSB0byBQVFA/DQo+Pj4+DQo+
Pj4+IEluIHRoZW9yeSB3aGF0IHlvdSBzYXkgaXMgY29ycmVjdCBhbmQgc2hvdWxkIHdvcmssIGJ1
dCBpbiBwcmFjdGljZSANCj4+Pj4gdGhlcmUgaXMgYSBmdW5jdGlvbiBjYWxsZWQgMS1zdGVwIFRy
YW5zcGFyZW50IGNsb2NraW5nIHRoYXQgcmVxdWlyZXMgDQo+Pj4+IHRpbWUgc3RhbXBpbmcgYXQg
dGhlIFBIWSAoaW1tZWRpYXRlbHkgd2hlbiB0aGUgcGFja2V0IGlzIHJlY2VpdmVkIG9yIA0KPj4+
PiB0cmFuc21pdHRlZCkuIFBIWSBjaGlwcyBkb24ndCBoYXZlIENBTSBvciBsb3RzIG9mIG1lbW9y
eSB0byBzdG9yZSBhIA0KPj4+PiBmZXcgdGhvdXNhbmQgcmFuZG9tIGxhYmVscy4gVGhlIGxhYmVs
IHJhbmdlIHdpbGwgc29sdmUgdGhhdCBwcm9ibGVtIA0KPj4+PiBhbmQgaXMgY29uc2lzdGVudCB3
aXRoIE1QTFMgYXJjaGl0ZWN0dXJlLg0KPj4+Pg0KPj4+PiBUaGFua3MsDQo+Pj4+IFNoYWhyYW0N
Cj4+Pj4NCj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+Pj4gRnJvbTogTWFjaCBD
aGVuIFttYWlsdG86bWFjaEBodWF3ZWkuY29tXQ0KPj4+PiBTZW50OiBXZWRuZXNkYXksIEp1bHkg
MTQsIDIwMTAgMTo1MyBBTQ0KPj4+PiBUbzogUy4gRGF2YXJpOyBKaWEgSEU7IFNoYWhyYW0gRGF2
YXJpDQo+Pj4+IENjOiBtcGxzQGlldGYub3JnOyBwd2UzQGlldGYub3JnOyB0aWNjdG9jQGlldGYu
b3JnOyBtcGxzLXRwQGlldGYub3JnDQo+Pj4+IFN1YmplY3Q6IFJlOiBbbXBsc10gW1BXRTNdIDE1
ODggb3ZlciBNUExTIGRyYWZ0DQo+Pj4+DQo+Pj4+IEhpIFNoYWhyYW0sDQo+Pj4+DQo+Pj4+IEZy
b20gdGhlIHZpZXcgb2YgaW1wbGVtZW50YXRpb24sIHRoZXJlIGlzIG5vIG1vcmUgZGlmZmVyZW5j
ZSBiZXR3ZWVuIA0KPj4+PiBTSE9VTEQNCj4+Pj4gYW5kIE1VU1QgOi0pDQo+Pj4+IEZvciBtZSwg
dGhlIExhYmVsIFJhbmdlIGlzIG1vcmUgbGlrZSBhIG1lY2hhbmltIHRvIG5vdGlmeSByZWxhdGVk
IA0KPj4+PiBub2RlcyB0aGF0DQo+Pj4+IHNvbWUgTFNQcyBhcmUgZGVkaWNhdGVkIGZvciBQVFAg
bWVzc2FnZXMgb3RoZXIgdGhhbiB0aGUgY2hpcHMgbWVtb3J5DQo+Pj4+IGxpbWl0YXRpb24sIGJl
Y2F1c2UgdGhlIG1lbW9yeSByZXN0cmljdGlvbiBpcyBhbHdheXMgdGhlcmUgd2hhdGV2ZXIgDQo+
Pj4+IHlvdSB1c2UNCj4+Pj4gTGFiZWwgUmFuZ2Ugb3Igbm90Lg0KPj4+PiBJTUhPLCBzaW5jZSB0
aGUgb2JqZWN0aXZlIGlzIHRvIHRlbGwgcmVsYXRlZCBNUExTIG5vZGVzIHdoaWNoIExTUHMgYXJl
IA0KPj4+PiBQVFANCj4+Pj4gTFNQcywgYW4gaW5kaWNhdGlvbiBpbiB0aGUgc2lnbmFsaW5nKFJT
VlAtVEUvR01QTFMvTERQKSBpcyBlbm91Z2ggYW5kIA0KPj4+PiBzZWVtcw0KPj4+PiBtb3JlIGNv
bW1vbi4gQW5kIGl0IHdpbGwgYXZvaWQgdGhlIHN0cmljdCByZXF1aXJlbWVudCBvZiAidGhlIG5l
dHdvcmsgYW5kDQo+Pj4+IGFsbCBub2RlcyByZXF1aXJlZCB0byBzdXBwb3J0IHRoZSBMYWJlbCBy
YW5nZSIuDQo+Pj4+IEluIGFkZGl0aW9uLCB0aGVyZSBzaG91bGQgYmUgc29tZSBtZWNoYW5pbXMo
ZS5nLiwgSVNJUy9PU1BGIA0KPj4+PiBleHRlbnNpb25zKSBmb3INCj4+Pj4gbm9kZXMgdG8gYWR2
ZXJ0aXNlIHRoZWlyIFBUUCBjYXBhYmlsaXR5IGhlbmNlIHRvIGhlbHAgUFRQIExTUHMgDQo+Pj4+
IGNvbXB1dGF0aW9uLg0KPj4+Pg0KPj4+PiBCZXN0IHJlZ2FyZHMsDQo+Pj4+IE1hY2gNCj4+Pj4N
Cj4+Pj4NCj4+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0NCj4+Pj4gRnJvbTogIlMuIERhdmFyaSIgPGRhdmFyaXNoQHlhaG9vLmNvbT4NCj4+Pj4g
U2VudDogV2VkbmVzZGF5LCBKdWx5IDE0LCAyMDEwIDI6MzEgUE0NCj4+Pj4gVG86ICJKaWEgSEUi
IDxoZWppYUBodWF3ZWkuY29tPjsgIlNoYWhyYW0gRGF2YXJpIiA8ZGF2YXJpQGJyb2FkY29tLmNv
bT4NCj4+Pj4gQ2M6IDxtcGxzQGlldGYub3JnPjsgPHB3ZTNAaWV0Zi5vcmc+OyA8dGljY3RvY0Bp
ZXRmLm9yZz47IA0KPj4+PiA8bXBscy10cEBpZXRmLm9yZz4NCj4+Pj4gU3ViamVjdDogUmU6IFtt
cGxzXSBbUFdFM10gMTU4OCBvdmVyIE1QTFMgZHJhZnQNCj4+Pj4NCj4+Pj4+IEhpIEppYSwNCj4+
Pj4+DQo+Pj4+PiBMYWJlbCByYW5nZSBpcyBhIFNIT1VMRCByZXF1aXJlbWVudHMgYW5kIG5vdCBN
VVNULiBUaGUgcmVhc29uIGZvciBMYWJlbA0KPj4+Pj4gUmFuZ2UgaXMNCj4+Pj4+IG1haW5seSBm
b3IgUEhZIGNoaXBzIHRoYXQgZG9uJ3QgaGF2ZSBsYXJnZSBtZW1vcnkgYW5kIGNhbid0IHN0b3Jl
IGEgDQo+Pj4+PiBsb3Qgb2YNCj4+Pj4+IExhYmVscy4gT3RoZXJ3aXNlIHRoZSBQVFAgTFNQIGlz
IHNldHVwIHZpYSBzaWduYWxpbmcgdGhhdCBzcGVjaWZpZXMgdGhlDQo+Pj4+PiBMU1AgYXMNCj4+
Pj4+IGNhcnJ5aW5nIDE1ODguDQo+Pj4+Pg0KPj4+Pj4gU28gdGhlIGFuc3dlciBpcyB0aGF0IGlm
IGEgTGFiZWwgcmFuZ2UgaXMgdXNlZCBpdCBtdXN0IGJlIGEgR2xvYmFsIHJhbmdlDQo+Pj4+PiB3
aXRoaW4NCj4+Pj4+IGEgbmV0d29yayBhbmQgc2hvdWxkIG5vdCBiZSB1c2VkIGJ5IGFueSByb3V0
ZXIgZm9yIG90aGVyIGFwcGxpY2F0aW9ucy4NCj4+Pj4+DQo+Pj4+PiBUaGFua3MsDQo+Pj4+PiBT
aGFocmFtDQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+DQo+Pj4+PiBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPj4+Pj4gRnJvbTogSmlhIEhFIDxoZWppYUBodWF3ZWkuY29tPg0KPj4+Pj4g
VG86IFNoYWhyYW0gRGF2YXJpIDxkYXZhcmlAYnJvYWRjb20uY29tPg0KPj4+Pj4gQ2M6IG1wbHNA
aWV0Zi5vcmc7IHB3ZTNAaWV0Zi5vcmc7IHRpY2N0b2NAaWV0Zi5vcmc7IG1wbHMtdHBAaWV0Zi5v
cmcNCj4+Pj4+IFNlbnQ6IFR1ZSwgSnVseSAxMywgMjAxMCA5OjUwOjM3IFBNDQo+Pj4+PiBTdWJq
ZWN0OiBSZTogW21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0KPj4+Pj4NCj4+Pj4+
DQo+Pj4+PiBIaSBTaGFocmFtLA0KPj4+Pj4NCj4+Pj4+IE9uZSBxdWVzdGlvbiBhYm91dCAiUFRQ
IExhYmVsIFJhbmdlIjoNCj4+Pj4+DQo+Pj4+PiBUbyBteSBrbm93bGVkZ2UsIGxhYmVsIGluIE1Q
TFMgbmV0d29yayBpcyBhIGxvY2FsICBtYXR0ZXIuIEZvciANCj4+Pj4+IGV4YW1wbGUsIHdlDQo+
Pj4+PiBtYXkNCj4+Pj4+IGhhdmUgcGVyLWludGVyZmFjZSBvciBwZXItcGxhdGZvcm0gbGFiZWwg
c3BhY2UuIFdpbGwgIHRoaXMgc3BlY2lmaWNlZCANCj4+Pj4+ICJQVFANCj4+Pj4+IExhYmVsDQo+
Pj4+PiBSYW5nZSIgY29uZmxpY3Qgd2l0aCB0aGUgY3VycmVudCBpbi11c2UgbGFiZWxzICBmb3Ig
Y29tbW9uIExTUHM/DQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+IEIuUi4NCj4+Pj4+IEppYQ0KPj4+Pj4N
Cj4+Pj4+IC0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCj4+Pj4+PiBGcm9tOiBTaGFocmFt
ICAgIERhdmFyaQ0KPj4+Pj4+IFRvOiB0aWNjdG9jQGlldGYub3JnIDsgbXBsc0BpZXRmLm9yZyA7
IG1wbHMtdHBAaWV0Zi5vcmcgOyBwd2UzQGlldGYub3JnDQo+Pj4+Pj4gU2VudDogVGh1cnNkYXks
IEp1bHkgMDgsIDIwMTAgMzoxMiBBTQ0KPj4+Pj4+IFN1YmplY3Q6IFtQV0UzXSAxNTg4IG92ZXIg
TVBMUyBkcmFmdA0KPj4+Pj4+DQo+Pj4+Pj4NCj4+Pj4+PiBIaSBBbGwsDQo+Pj4+Pj4NCj4+Pj4+
PiBQbGVhc2UgZmluZCBhdHRhY2hlZCBvdXIgZmlyc3QgZHJhZnQgb2YgMTU4OCBvdmVyIE1QTFMu
ICAgIFNpbmNlIHdlIA0KPj4+Pj4+IGhhdmUNCj4+Pj4+PiBzb21lDQo+Pj4+Pj4gdGVjaG5pY2Fs
IGlzc3VlcyBjb252ZXJ0aW5nIHRoZSBXb3JkIGZvcm1hdCB0byBUeHQgd2UgICAgY291bGRu4oCZ
dCANCj4+Pj4+PiB1cGxvYWQNCj4+Pj4+PiB0aGUNCj4+Pj4+PiBkcmFmdCBiZWZvcmUgdGhlIGN1
dC1vZmYgZGF0ZS4gSG93ZXZlciB3ZSB3aWxsICAgIHByZXNlbnQgdGhlIGRyYWZ0IA0KPj4+Pj4+
IGluIHRoZQ0KPj4+Pj4+IG5leHQNCj4+Pj4+PiBJRVRGIG1lZXRpbmcgYW5kIHdpbGwgdXBsb2Fk
IHRoZSBkcmFmdCBhZnRlciB0aGUgICAgbWVldGluZy4NCj4+Pj4+Pg0KPj4+Pj4+IE5vdGUgdGhh
dCB0aGUgbWFpbiBXRyBpcyBUaWNUb2MgYnV0IG1heSByZXF1aXJlICAgIGNvbnN1bHRhdGlvbiB3
aXRoIA0KPj4+Pj4+IE1QTFMNCj4+Pj4+PiBhbmQNCj4+Pj4+PiBQV0UzIFdHcy4NCj4+Pj4+Pg0K
Pj4+Pj4+IFRoYW5rcywNCj4+Pj4+PiBTaGFocmFtIERhdmFyaQ0KPj4+Pj4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+Pj4+Pj4gcHdlMyBtYWlsaW5nICAgIGxpc3QNCj4+Pj4+PiBw
d2UzQGlldGYub3JnDQo+Pj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9wd2UzDQo+Pj4+Pj4NCj4+Pj4NCj4+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+Pj4+PiBtcGxzIG1haWxpbmcgbGlzdA0KPj4+Pj4gbXBsc0Bp
ZXRmLm9yZw0KPj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxz
DQo+Pj4+Pg0KPj4+Pg0KPj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+Pj4gbXBscyBtYWlsaW5nIGxpc3QNCj4+PiBtcGxzQGlldGYub3JnDQo+Pj4g
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQo+IA0KDQo=


From ben@niven-jenkins.co.uk  Thu Jul 15 14:14:30 2010
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C58C3A6831; Thu, 15 Jul 2010 14:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.975
X-Spam-Level: 
X-Spam-Status: No, score=-2.975 tagged_above=-999 required=5 tests=[AWL=0.624,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 8EIv6fNZ87fd; Thu, 15 Jul 2010 14:14:27 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.62]) by core3.amsl.com (Postfix) with ESMTP id 9C6B83A6AD4; Thu, 15 Jul 2010 14:14:26 -0700 (PDT)
Received: from host86-141-37-226.range86-141.btcentralplus.com ([86.141.37.226] helo=unknown-00-22-43-25-f9-66.home) by mail7.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1OZVlL-0001He-46; Thu, 15 Jul 2010 22:14:36 +0100
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c> <4C3E7E83.9080603@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F5C24.4070505@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC2911E@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F702B.5090704@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC29128@SJEXCHCCR02.corp.ad.broadcom.com>
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6940EC29128@SJEXCHCCR02.corp.ad.broadcom.com>
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=windows-1252
Message-Id: <2E480B43-FABD-4D10-A8D4-F950CDEC00CB@niven-jenkins.co.uk>
Content-Transfer-Encoding: quoted-printable
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Thu, 15 Jul 2010 22:14:31 +0100
To: "Shahram Davari" <davari@broadcom.com>
X-Mailer: Apple Mail (2.1078)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [mpls-tp]  [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 21:14:30 -0000

Sharam,

I am not sure there is a requirement for all devices to be upgraded. My =
thinking is as follows:

We have 3 types of 1588 MPLS devices:
1) Those that do not support 1588
2) Those that can terminate 1588 but do not support boundary clock
3) Those that can terminate 1588 and do support boundary clock.

For the purpose of this discussion (2) & (3) can probably be lumped =
together.

The requirement (to avoid more complex hardware processing) is that 1588 =
packets arrive at device types (2) & (3) with a label out of a "1588 =
label range". A label from the 1588 label range has no special meaning =
with respect to forwarding behaviour it simply carries an extra semantic =
that indicates that the packet is a 1588 packet, such a semantic is only =
required if the LSP is terminating on device types (2) & (3) or =
transiting device type (3).

Therefore the 1588 LSP does not need to use a label from a 1588 specific =
label range at every hop in the path, it only needs such a label as the =
incoming label to device types (2) & (3).

If labels are downstream assigned then the downstream device provides =
the label mapping for the incoming label for itself and so device types =
(2) & (3) can assign labels out of their 1588 label range, there is no =
requirement for the upstream device to realise such a label has an =
additional semantic and therefore there is no need to upgrade devices =
except those directly participating in the 1588 session (either as =
terminating devices or as boundary devices).

If labels are upstream assigned then the upstream device will need to =
assign a label from the 1588 label range and so the upstream device, =
even if it is of type (1), needs to realise it has to assign a label =
with 1588 semantics. The upstream (as well as downstream) device will =
require upgrading although context labels may provide some level of =
support already (I would have to think more about the applicability of =
context labels to this problem space).

The key thing to remember is that the semantic that the LSP is a 1588 =
LSP needs to be carried End to End when signalling the LSP but does not =
need to exist within the forwarding machinery for each device in the =
path unless that device is participating in the 1588 session in some way =
(including upstream allocation of 1588 labels).

Ben



On 15 Jul 2010, at 21:37, Shahram Davari wrote:

> Hi Joel,
>=20
> OK, do you have a better proposal?
>=20
> Thx
> Shahram
>=20
> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]=20
> Sent: Thursday, July 15, 2010 1:32 PM
> To: Shahram Davari
> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>=20
> I am sorry, but requiring every LSR in the infrastructure to get a=20
> software upgrade in order to allow for the presence of 1588-supporting=20=

> devices is a MAJOR issue.  It is NOT backwards compatible.  Operators=20=

> (wether service provider or enterprise IT) do NOT like being told they=20=

> ahve to upgrade the software on all devices in their network in order =
to=20
> add a capability that those devices are not engaging in.
>=20
> While one can argue about the "ease" of the specific software change,=20=

> there is from an operational perspective no such thing as an easy=20
> upgrade of any device, and there is definitely no such thing as an =
easy=20
> upgrade of all the devices in the network.
>=20
> Yours,
> Joel
>=20
> Shahram Davari wrote:
>> Hi Joel,
>>=20
>> There are 2 aspects to this puzzle:
>>=20
>> 1) Hardware support for 1588 in a device.=20
>> 2) Software support for 1588 in the form of allocating labels to PTP =
LSPs
>>=20
>> A router that wants to perform 1588 time stamping must have both (1) =
and (2) functionality. While a router in=20
>> the path of a PTP LSP that does not support (1) should support (2) =
and=20
> advertise labels from some arbitrary
>> range for PTP LSP.
>>=20
>> It is quite easy to upgrade a router software so that when it =
receives RSVP-TE label request to assign label=20
>> from an arbitrary local range.
>>=20
>> So I don't see any issue here.
>>=20
>> Thanks,
>> Shahram
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]=20
>> Sent: Thursday, July 15, 2010 12:06 PM
>> To: Shahram Davari
>> Cc: Mach Chen; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; =
ticctoc@ietf.org; mpls-tp@ietf.org
>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>=20
>> Architecturally, as I understand the draft, the downstream neighbor =
of a=20
>> 1588 supporting device (on the PTP carrying LSP) may not itself be a=20=

>> 1588 supporting device.  Is that correct?  If that is not correct, if=20=

>> instead the structure is that PTP supporting LSPs are established=20
>> between adjacent enhanced devices, then I can see how some sort of a=20=

>> label range might make sense.
>>=20
>> If however, the downstream node you refer to may be an existing LSR,=20=

>> then I do not see how you can ask an existing LSR to allocate a label=20=

>> range for a function it does not understand.
>>=20
>> Yours,
>> Joel
>>=20
>> Shahram Davari wrote:
>>> Hi Joel,
>>>=20
>>> I agree with your logic, but the idea is a bit different:
>>>=20
>>> All we need is a label range, it does not need to be globally unique =
in the network and it does
>>> not even need to be the same on the Tx and Rx direction of the same=20=

>> link. Although we need time
>>> stamping both on Rx and on Tx, but on Rx a node is in control of its=20=

>> own label and on Tx the
>>> downstream node should advertise some label range. What we don't =
want=20
>> is that the downstream
>>> node to advertise random labels for each LSP carrying PTP.
>>> I will update the draft to mention that the label range does not =
require to be global but it can
>>> be per-platform or even per-interface.
>>> Thanks,
>>> Shahram
>>>=20
>>> -----Original Message-----
>>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]=20
>>> Sent: Wednesday, July 14, 2010 8:21 PM
>>> To: Mach Chen
>>> Cc: Shahram Davari; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; =
ticctoc@ietf.org; mpls-tp@ietf.org
>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>=20
>>> Remember that if what is required is that the message arriving at =
the=20
>>> 1588 supporting device have a certain label range, that is a purely=20=

>>> local matter.  As long as the singaling carries the indication that =
the=20
>>> LSP is to be dedicated to 1588 traffic (a reasonable extension to =
the=20
>>> signaling), the downstream switch can pick what label to assign to =
that LSP.
>>>=20
>>> If the goal is to have the outgoing label be from a specific range, =
that=20
>>> is essentially impossible in the proposed architecture.  The =
proposed=20
>>> architecture is one in which 1588 switches are peers with existing =
LSRs=20
>>> using MPLS.  As such, in order to have a label range for outgoing=20
>>> labels, the existing MPLS LSR would somehow have to know about this=20=

>>> reserved label range, not use those labels for other purposes, and=20=

>>> assign those labels to 1588 LSPs.  All of which is=20
>>> non-backwards-compatible.  If the 1588 LSPs were actually =
pseudowires,=20
>>> tunneled over LSPs, then any number of things are possible.
>>>=20
>>> Yours,
>>> Joel M. Halpern
>>>=20
>>> Mach Chen wrote:
>>>> Hi Shahram,
>>>>=20
>>>> I agree that the label range idea is an efficient way that could =
reduce=20
>>>> the storage requirement of PHY chips.
>>>>=20
>>>> It's easy to require one or limited nodes to reserve a label range, =
but=20
>>>> IMHO, it very difficut to require all nodes of a large network to =
do=20
>>>> this and even worse when some labels are already used by other =
LSPs,=20
>>>> unless there are some mechanisms to negotiate/advertise(e.g., =
flooding=20
>>>> the label range by IGP within the network) the proper label range =
hence=20
>>>> to aviod label collision.
>>>>=20
>>>> Best regards,
>>>> Mach
>>>>=20
>>>> --------------------------------------------------
>>>> From: "Shahram Davari" <davari@broadcom.com>
>>>> Sent: Thursday, July 15, 2010 1:58 AM
>>>> To: "Mach Chen" <mach@huawei.com>; "S. Davari" =
<davarish@yahoo.com>;=20
>>>> "Jia HE" <hejia@huawei.com>
>>>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>;=20
>>>> <mpls-tp@ietf.org>
>>>> Subject: RE: [mpls] [PWE3] 1588 over MPLS draft
>>>>=20
>>>>> Hi Mach,
>>>>>=20
>>>>> When a service provider wants to create these PTP LSPs, what is =
wrong=20
>>>>> with allocating a range of labels for this purpose? This is purely =
a=20
>>>>> software exercise. There are 2 million labels available to each =
node,=20
>>>>> why can't some of them be allocated by software to PTP?
>>>>>=20
>>>>> In theory what you say is correct and should work, but in practice=20=

>>>>> there is a function called 1-step Transparent clocking that =
requires=20
>>>>> time stamping at the PHY (immediately when the packet is received =
or=20
>>>>> transmitted). PHY chips don't have CAM or lots of memory to store =
a=20
>>>>> few thousand random labels. The label range will solve that =
problem=20
>>>>> and is consistent with MPLS architecture.
>>>>>=20
>>>>> Thanks,
>>>>> Shahram
>>>>>=20
>>>>> -----Original Message-----
>>>>> From: Mach Chen [mailto:mach@huawei.com]
>>>>> Sent: Wednesday, July 14, 2010 1:53 AM
>>>>> To: S. Davari; Jia HE; Shahram Davari
>>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; =
mpls-tp@ietf.org
>>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>>=20
>>>>> Hi Shahram,
>>>>>=20
>>>>> =46rom the view of implementation, there is no more difference =
between=20
>>>>> SHOULD
>>>>> and MUST :-)
>>>>> For me, the Label Range is more like a mechanim to notify related=20=

>>>>> nodes that
>>>>> some LSPs are dedicated for PTP messages other than the chips =
memory
>>>>> limitation, because the memory restriction is always there =
whatever=20
>>>>> you use
>>>>> Label Range or not.
>>>>> IMHO, since the objective is to tell related MPLS nodes which LSPs =
are=20
>>>>> PTP
>>>>> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough =
and=20
>>>>> seems
>>>>> more common. And it will avoid the strict requirement of "the =
network and
>>>>> all nodes required to support the Label range".
>>>>> In addition, there should be some mechanims(e.g., ISIS/OSPF=20
>>>>> extensions) for
>>>>> nodes to advertise their PTP capability hence to help PTP LSPs=20
>>>>> computation.
>>>>>=20
>>>>> Best regards,
>>>>> Mach
>>>>>=20
>>>>>=20
>>>>> --------------------------------------------------
>>>>> From: "S. Davari" <davarish@yahoo.com>
>>>>> Sent: Wednesday, July 14, 2010 2:31 PM
>>>>> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" =
<davari@broadcom.com>
>>>>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>;=20
>>>>> <mpls-tp@ietf.org>
>>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>>=20
>>>>>> Hi Jia,
>>>>>>=20
>>>>>> Label range is a SHOULD requirements and not MUST. The reason for =
Label
>>>>>> Range is
>>>>>> mainly for PHY chips that don't have large memory and can't store =
a=20
>>>>>> lot of
>>>>>> Labels. Otherwise the PTP LSP is setup via signaling that =
specifies the
>>>>>> LSP as
>>>>>> carrying 1588.
>>>>>>=20
>>>>>> So the answer is that if a Label range is used it must be a =
Global range
>>>>>> within
>>>>>> a network and should not be used by any router for other =
applications.
>>>>>>=20
>>>>>> Thanks,
>>>>>> Shahram
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> ________________________________
>>>>>> From: Jia HE <hejia@huawei.com>
>>>>>> To: Shahram Davari <davari@broadcom.com>
>>>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; =
mpls-tp@ietf.org
>>>>>> Sent: Tue, July 13, 2010 9:50:37 PM
>>>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>>>=20
>>>>>>=20
>>>>>> Hi Shahram,
>>>>>>=20
>>>>>> One question about "PTP Label Range":
>>>>>>=20
>>>>>> To my knowledge, label in MPLS network is a local  matter. For=20
>>>>>> example, we
>>>>>> may
>>>>>> have per-interface or per-platform label space. Will  this =
specificed=20
>>>>>> "PTP
>>>>>> Label
>>>>>> Range" conflict with the current in-use labels  for common LSPs?
>>>>>>=20
>>>>>>=20
>>>>>> B.R.
>>>>>> Jia
>>>>>>=20
>>>>>> ----- Original Message -----
>>>>>>> From: Shahram    Davari
>>>>>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; =
pwe3@ietf.org
>>>>>>> Sent: Thursday, July 08, 2010 3:12 AM
>>>>>>> Subject: [PWE3] 1588 over MPLS draft
>>>>>>>=20
>>>>>>>=20
>>>>>>> Hi All,
>>>>>>>=20
>>>>>>> Please find attached our first draft of 1588 over MPLS.    Since =
we=20
>>>>>>> have
>>>>>>> some
>>>>>>> technical issues converting the Word format to Txt we    =
couldn=92t=20
>>>>>>> upload
>>>>>>> the
>>>>>>> draft before the cut-off date. However we will    present the =
draft=20
>>>>>>> in the
>>>>>>> next
>>>>>>> IETF meeting and will upload the draft after the    meeting.
>>>>>>>=20
>>>>>>> Note that the main WG is TicToc but may require    consultation =
with=20
>>>>>>> MPLS
>>>>>>> and
>>>>>>> PWE3 WGs.
>>>>>>>=20
>>>>>>> Thanks,
>>>>>>> Shahram Davari
>>>>>> ________________________________
>>>>>> _______________________________________________
>>>>>>> pwe3 mailing    list
>>>>>>> pwe3@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>>>>=20
>>>>>=20
>>>>>> _______________________________________________
>>>>>> mpls mailing list
>>>>>> mpls@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>>>>=20
>>>>>=20
>>>> _______________________________________________
>>>> mpls mailing list
>>>> mpls@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mpls
>>=20
>=20
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp


From mach@huawei.com  Thu Jul 15 18:35:35 2010
Return-Path: <mach@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F8B13A6869; Thu, 15 Jul 2010 18:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.702
X-Spam-Level: 
X-Spam-Status: No, score=-1.702 tagged_above=-999 required=5 tests=[AWL=0.896,  BAYES_00=-2.599, STOX_REPLY_TYPE=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 jyX6ykFpyDVy; Thu, 15 Jul 2010 18:35:34 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id AD52B3A63D3; Thu, 15 Jul 2010 18:35:33 -0700 (PDT)
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 <0L5M006WPN3KSQ@szxga04-in.huawei.com>; Fri, 16 Jul 2010 09:35:44 +0800 (CST)
Received: from m55527c ([10.110.98.169]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5M009VNN3JQB@szxga04-in.huawei.com>; Fri, 16 Jul 2010 09:35:44 +0800 (CST)
Date: Fri, 16 Jul 2010 09:35:43 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <2C2F1EBA8050E74EA81502D5740B4BD6940EC29128@SJEXCHCCR02.corp.ad.broadcom.com>
To: Shahram Davari <davari@broadcom.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Message-id: <586F9EE3D73B4060AAD7C6CEEA261E38@m55527c>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206
X-Mailer: Microsoft Windows Live Mail 14.0.8064.206
Content-type: text/plain; format=flowed; charset=utf-8; reply-type=original
Content-transfer-encoding: 8BIT
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com> <F8A42E669722437AB6CD24CFD4586300@m55527c> <2C2F1EBA8050E74EA81502D5740B4BD6940EC28FAD@SJEXCHCCR02.corp.ad.broadcom.com> <6862C24AB1F4468D8F3265AE705925C6@m55527c> <4C3E7E83.9080603@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F5C24.4070505@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC2911E@SJEXCHCCR02.corp.ad.broadcom.com> <4C3F702B.5090704@joelhalpern.com> <2C2F1EBA8050E74EA81502D5740B4BD6940EC29128@SJEXCHCCR02.corp.ad.broadcom.com>
Cc: mpls@ietf.org, pwe3@ietf.org, ticctoc@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2010 01:35:35 -0000

Hi Shahram,

If the 1588-capability router does downstream (for Rx direction) and 
upstream (for Tx direction) label distribution respectively, it may not 
require its adjacent routers to upgrade.

Best regards,
Mach

--------------------------------------------------
From: "Shahram Davari" <davari@broadcom.com>
Sent: Friday, July 16, 2010 4:37 AM
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft

> Hi Joel,
>
> OK, do you have a better proposal?
>
> Thx
> Shahram
>
> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: Thursday, July 15, 2010 1:32 PM
> To: Shahram Davari
> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>
> I am sorry, but requiring every LSR in the infrastructure to get a
> software upgrade in order to allow for the presence of 1588-supporting
> devices is a MAJOR issue.  It is NOT backwards compatible.  Operators
> (wether service provider or enterprise IT) do NOT like being told they
> ahve to upgrade the software on all devices in their network in order to
> add a capability that those devices are not engaging in.
>
> While one can argue about the "ease" of the specific software change,
> there is from an operational perspective no such thing as an easy
> upgrade of any device, and there is definitely no such thing as an easy
> upgrade of all the devices in the network.
>
> Yours,
> Joel
>
> Shahram Davari wrote:
>> Hi Joel,
>>
>> There are 2 aspects to this puzzle:
>>
>> 1) Hardware support for 1588 in a device.
>> 2) Software support for 1588 in the form of allocating labels to PTP LSPs
>>
>> A router that wants to perform 1588 time stamping must have both (1) and 
>> (2) functionality. While a router in
> >the path of a PTP LSP that does not support (1) should support (2) and
> advertise labels from some arbitrary
> >range for PTP LSP.
>>
>> It is quite easy to upgrade a router software so that when it receives 
>> RSVP-TE label request to assign label
> >from an arbitrary local range.
>>
>> So I don't see any issue here.
>>
>> Thanks,
>> Shahram
>>
>>
>>
>> -----Original Message-----
>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
>> Sent: Thursday, July 15, 2010 12:06 PM
>> To: Shahram Davari
>> Cc: Mach Chen; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; 
>> ticctoc@ietf.org; mpls-tp@ietf.org
>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>
>> Architecturally, as I understand the draft, the downstream neighbor of a
>> 1588 supporting device (on the PTP carrying LSP) may not itself be a
>> 1588 supporting device.  Is that correct?  If that is not correct, if
>> instead the structure is that PTP supporting LSPs are established
>> between adjacent enhanced devices, then I can see how some sort of a
>> label range might make sense.
>>
>> If however, the downstream node you refer to may be an existing LSR,
>> then I do not see how you can ask an existing LSR to allocate a label
>> range for a function it does not understand.
>>
>> Yours,
>> Joel
>>
>> Shahram Davari wrote:
>>> Hi Joel,
>>>
>>> I agree with your logic, but the idea is a bit different:
>>>
>>> All we need is a label range, it does not need to be globally unique in 
>>> the network and it does
>>  >not even need to be the same on the Tx and Rx direction of the same
>> link. Although we need time
>>  >stamping both on Rx and on Tx, but on Rx a node is in control of its
>> own label and on Tx the
>>  >downstream node should advertise some label range. What we don't want
>> is that the downstream
>>  >node to advertise random labels for each LSP carrying PTP.
>>> I will update the draft to mention that the label range does not require 
>>> to be global but it can
>>  >be per-platform or even per-interface.
>>> Thanks,
>>> Shahram
>>>
>>> -----Original Message-----
>>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
>>> Sent: Wednesday, July 14, 2010 8:21 PM
>>> To: Mach Chen
>>> Cc: Shahram Davari; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; 
>>> ticctoc@ietf.org; mpls-tp@ietf.org
>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>
>>> Remember that if what is required is that the message arriving at the
>>> 1588 supporting device have a certain label range, that is a purely
>>> local matter.  As long as the singaling carries the indication that the
>>> LSP is to be dedicated to 1588 traffic (a reasonable extension to the
>>> signaling), the downstream switch can pick what label to assign to that 
>>> LSP.
>>>
>>> If the goal is to have the outgoing label be from a specific range, that
>>> is essentially impossible in the proposed architecture.  The proposed
>>> architecture is one in which 1588 switches are peers with existing LSRs
>>> using MPLS.  As such, in order to have a label range for outgoing
>>> labels, the existing MPLS LSR would somehow have to know about this
>>> reserved label range, not use those labels for other purposes, and
>>> assign those labels to 1588 LSPs.  All of which is
>>> non-backwards-compatible.  If the 1588 LSPs were actually pseudowires,
>>> tunneled over LSPs, then any number of things are possible.
>>>
>>> Yours,
>>> Joel M. Halpern
>>>
>>> Mach Chen wrote:
>>>> Hi Shahram,
>>>>
>>>> I agree that the label range idea is an efficient way that could reduce
>>>> the storage requirement of PHY chips.
>>>>
>>>> It's easy to require one or limited nodes to reserve a label range, but
>>>> IMHO, it very difficut to require all nodes of a large network to do
>>>> this and even worse when some labels are already used by other LSPs,
>>>> unless there are some mechanisms to negotiate/advertise(e.g., flooding
>>>> the label range by IGP within the network) the proper label range hence
>>>> to aviod label collision.
>>>>
>>>> Best regards,
>>>> Mach
>>>>
>>>> --------------------------------------------------
>>>> From: "Shahram Davari" <davari@broadcom.com>
>>>> Sent: Thursday, July 15, 2010 1:58 AM
>>>> To: "Mach Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>;
>>>> "Jia HE" <hejia@huawei.com>
>>>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>;
>>>> <mpls-tp@ietf.org>
>>>> Subject: RE: [mpls] [PWE3] 1588 over MPLS draft
>>>>
>>>>> Hi Mach,
>>>>>
>>>>> When a service provider wants to create these PTP LSPs, what is wrong
>>>>> with allocating a range of labels for this purpose? This is purely a
>>>>> software exercise. There are 2 million labels available to each node,
>>>>> why can't some of them be allocated by software to PTP?
>>>>>
>>>>> In theory what you say is correct and should work, but in practice
>>>>> there is a function called 1-step Transparent clocking that requires
>>>>> time stamping at the PHY (immediately when the packet is received or
>>>>> transmitted). PHY chips don't have CAM or lots of memory to store a
>>>>> few thousand random labels. The label range will solve that problem
>>>>> and is consistent with MPLS architecture.
>>>>>
>>>>> Thanks,
>>>>> Shahram
>>>>>
>>>>> -----Original Message-----
>>>>> From: Mach Chen [mailto:mach@huawei.com]
>>>>> Sent: Wednesday, July 14, 2010 1:53 AM
>>>>> To: S. Davari; Jia HE; Shahram Davari
>>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>>
>>>>> Hi Shahram,
>>>>>
>>>>> From the view of implementation, there is no more difference between
>>>>> SHOULD
>>>>> and MUST :-)
>>>>> For me, the Label Range is more like a mechanim to notify related
>>>>> nodes that
>>>>> some LSPs are dedicated for PTP messages other than the chips memory
>>>>> limitation, because the memory restriction is always there whatever
>>>>> you use
>>>>> Label Range or not.
>>>>> IMHO, since the objective is to tell related MPLS nodes which LSPs are
>>>>> PTP
>>>>> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and
>>>>> seems
>>>>> more common. And it will avoid the strict requirement of "the network 
>>>>> and
>>>>> all nodes required to support the Label range".
>>>>> In addition, there should be some mechanims(e.g., ISIS/OSPF
>>>>> extensions) for
>>>>> nodes to advertise their PTP capability hence to help PTP LSPs
>>>>> computation.
>>>>>
>>>>> Best regards,
>>>>> Mach
>>>>>
>>>>>
>>>>> --------------------------------------------------
>>>>> From: "S. Davari" <davarish@yahoo.com>
>>>>> Sent: Wednesday, July 14, 2010 2:31 PM
>>>>> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" 
>>>>> <davari@broadcom.com>
>>>>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>;
>>>>> <mpls-tp@ietf.org>
>>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>>
>>>>>> Hi Jia,
>>>>>>
>>>>>> Label range is a SHOULD requirements and not MUST. The reason for 
>>>>>> Label
>>>>>> Range is
>>>>>> mainly for PHY chips that don't have large memory and can't store a
>>>>>> lot of
>>>>>> Labels. Otherwise the PTP LSP is setup via signaling that specifies 
>>>>>> the
>>>>>> LSP as
>>>>>> carrying 1588.
>>>>>>
>>>>>> So the answer is that if a Label range is used it must be a Global 
>>>>>> range
>>>>>> within
>>>>>> a network and should not be used by any router for other 
>>>>>> applications.
>>>>>>
>>>>>> Thanks,
>>>>>> Shahram
>>>>>>
>>>>>>
>>>>>>
>>>>>> ________________________________
>>>>>> From: Jia HE <hejia@huawei.com>
>>>>>> To: Shahram Davari <davari@broadcom.com>
>>>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>>>>>> Sent: Tue, July 13, 2010 9:50:37 PM
>>>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>>>>
>>>>>>
>>>>>> Hi Shahram,
>>>>>>
>>>>>> One question about "PTP Label Range":
>>>>>>
>>>>>> To my knowledge, label in MPLS network is a local  matter. For
>>>>>> example, we
>>>>>> may
>>>>>> have per-interface or per-platform label space. Will  this specificed
>>>>>> "PTP
>>>>>> Label
>>>>>> Range" conflict with the current in-use labels  for common LSPs?
>>>>>>
>>>>>>
>>>>>> B.R.
>>>>>> Jia
>>>>>>
>>>>>> ----- Original Message -----
>>>>>>> From: Shahram    Davari
>>>>>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; 
>>>>>>> pwe3@ietf.org
>>>>>>> Sent: Thursday, July 08, 2010 3:12 AM
>>>>>>> Subject: [PWE3] 1588 over MPLS draft
>>>>>>>
>>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Please find attached our first draft of 1588 over MPLS.    Since we
>>>>>>> have
>>>>>>> some
>>>>>>> technical issues converting the Word format to Txt we    couldnâ€™t
>>>>>>> upload
>>>>>>> the
>>>>>>> draft before the cut-off date. However we will    present the draft
>>>>>>> in the
>>>>>>> next
>>>>>>> IETF meeting and will upload the draft after the    meeting.
>>>>>>>
>>>>>>> Note that the main WG is TicToc but may require    consultation with
>>>>>>> MPLS
>>>>>>> and
>>>>>>> PWE3 WGs.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Shahram Davari
>>>>>> ________________________________
>>>>>> _______________________________________________
>>>>>>> pwe3 mailing    list
>>>>>>> pwe3@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>>>>
>>>>>
>>>>>> _______________________________________________
>>>>>> mpls mailing list
>>>>>> mpls@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/mpls
>>>>>>
>>>>>
>>>> _______________________________________________
>>>> mpls mailing list
>>>> mpls@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mpls
>>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 

From lizhong.jin@zte.com.cn  Thu Jul 15 20:23:16 2010
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5DA73A6876; Thu, 15 Jul 2010 20:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.238
X-Spam-Level: 
X-Spam-Status: No, score=-101.238 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_61=0.6, RCVD_DOUBLE_IP_LOOSE=0.76, 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 K8qh+gl3M1ZK; Thu, 15 Jul 2010 20:23:13 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 52B513A67B8; Thu, 15 Jul 2010 20:23:12 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 552345089591617; Fri, 16 Jul 2010 11:22:34 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 83990.5509893102; Fri, 16 Jul 2010 11:23:21 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o6G3MUMr006117; Fri, 16 Jul 2010 11:22:30 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <mailman.2710.1279228822.4795.pwe3@ietf.org>
To: davari@broadcom.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFDF87540D.B8FEE033-ON48257762.001003D6-48257762.00128656@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Fri, 16 Jul 2010 11:22:19 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2010-07-16 11:22:20, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2010-07-16 11:22:20, Serialize complete at 2010-07-16 11:22:20, S/MIME Sign failed at 2010-07-16 11:22:20: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-16 11:22:24, Serialize complete at 2010-07-16 11:22:24
Content-Type: multipart/alternative; boundary="=_alternative 0012865348257762_="
X-MAIL: mse2.zte.com.cn o6G3MUMr006117
Cc: mpls@ietf.org, pwe3@ietf.org, ticctoc@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3]   1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2010 03:23:16 -0000

This is a multipart message in MIME format.
--=_alternative 0012865348257762_=
Content-Type: text/plain; charset="US-ASCII"

Hi Sharam,
The label should not be per-platform or per-interface, but more general 
concept, context specific label space, see RFC5331 for detail.

BR
Lizhong
 
> ------------------------------
> 
> Message: 3
> Date: Thu, 15 Jul 2010 10:46:22 -0700
> From: "Shahram Davari" <davari@broadcom.com>
> Subject: Re: [PWE3] [mpls]  1588 over MPLS draft
> To: "Joel M. Halpern" <jmh@joelhalpern.com>,   "Mach Chen"
>    <mach@huawei.com>
> Cc: "mpls@ietf.org" <mpls@ietf.org>, "ticctoc@ietf.org"
>    <ticctoc@ietf.org>,   "mpls-tp@ietf.org" <mpls-tp@ietf.org>,
>    "pwe3@ietf.org" <pwe3@ietf.org>,   "S. Davari" <davarish@yahoo.com>
> Message-ID:
>    <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.
> broadcom.com>
> 
> Content-Type: text/plain; charset=utf-8
> 
> Hi Joel,
> 
> I agree with your logic, but the idea is a bit different:
> 
> All we need is a label range, it does not need to be globally unique
> in the network and it does not even need to be the same on the Tx 
> and Rx direction of the same link. Although we need time stamping 
> both on Rx and on Tx, but on Rx a node is in control of its own 
> label and on Tx the downstream node should advertise some label 
> range. What we don't want is that the downstream node to advertise 
> random labels for each LSP carrying PTP.
> 
> I will update the draft to mention that the label range does not 
> require to be global but it can be per-platform or even per-interface.
> 
> Thanks,
> Shahram
> 
> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 
> Sent: Wednesday, July 14, 2010 8:21 PM
> To: Mach Chen
> Cc: Shahram Davari; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org;
> ticctoc@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> 
> Remember that if what is required is that the message arriving at the 
> 1588 supporting device have a certain label range, that is a purely 
> local matter.  As long as the singaling carries the indication that the 
> LSP is to be dedicated to 1588 traffic (a reasonable extension to the 
> signaling), the downstream switch can pick what label to assign to that 
LSP.
> 
> If the goal is to have the outgoing label be from a specific range, that 

> is essentially impossible in the proposed architecture.  The proposed 
> architecture is one in which 1588 switches are peers with existing LSRs 
> using MPLS.  As such, in order to have a label range for outgoing 
> labels, the existing MPLS LSR would somehow have to know about this 
> reserved label range, not use those labels for other purposes, and 
> assign those labels to 1588 LSPs.  All of which is 
> non-backwards-compatible.  If the 1588 LSPs were actually pseudowires, 
> tunneled over LSPs, then any number of things are possible.
> 
> Yours,
> Joel M. Halpern
> 
> Mach Chen wrote:
> > Hi Shahram,
> > 
> > I agree that the label range idea is an efficient way that could 
reduce 
> > the storage requirement of PHY chips.
> > 
> > It's easy to require one or limited nodes to reserve a label range, 
but 
> > IMHO, it very difficut to require all nodes of a large network to do 
> > this and even worse when some labels are already used by other LSPs, 
> > unless there are some mechanisms to negotiate/advertise(e.g., flooding 

> > the label range by IGP within the network) the proper label range 
hence 
> > to aviod label collision.
> > 
> > Best regards,
> > Mach
> > 
> > --------------------------------------------------
> > From: "Shahram Davari" <davari@broadcom.com>
> > Sent: Thursday, July 15, 2010 1:58 AM
> > To: "Mach Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>; 
> > "Jia HE" <hejia@huawei.com>
> > Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
> > <mpls-tp@ietf.org>
> > Subject: RE: [mpls] [PWE3] 1588 over MPLS draft
> > 
> >> Hi Mach,
> >>
> >> When a service provider wants to create these PTP LSPs, what is wrong 

> >> with allocating a range of labels for this purpose? This is purely a 
> >> software exercise. There are 2 million labels available to each node, 

> >> why can't some of them be allocated by software to PTP?
> >>
> >> In theory what you say is correct and should work, but in practice 
> >> there is a function called 1-step Transparent clocking that requires 
> >> time stamping at the PHY (immediately when the packet is received or 
> >> transmitted). PHY chips don't have CAM or lots of memory to store a 
> >> few thousand random labels. The label range will solve that problem 
> >> and is consistent with MPLS architecture.
> >>
> >> Thanks,
> >> Shahram
> >>
> >> -----Original Message-----
> >> From: Mach Chen [mailto:mach@huawei.com]
> >> Sent: Wednesday, July 14, 2010 1:53 AM
> >> To: S. Davari; Jia HE; Shahram Davari
> >> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> >> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> >>
> >> Hi Shahram,
> >>
> >> From the view of implementation, there is no more difference between 
> >> SHOULD
> >> and MUST :-)
> >> For me, the Label Range is more like a mechanim to notify related 
> >> nodes that
> >> some LSPs are dedicated for PTP messages other than the chips memory
> >> limitation, because the memory restriction is always there whatever 
> >> you use
> >> Label Range or not.
> >> IMHO, since the objective is to tell related MPLS nodes which LSPs 
are 
> >> PTP
> >> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and 

> >> seems
> >> more common. And it will avoid the strict requirement of "the network 
and
> >> all nodes required to support the Label range".
> >> In addition, there should be some mechanims(e.g., ISIS/OSPF 
> >> extensions) for
> >> nodes to advertise their PTP capability hence to help PTP LSPs 
> >> computation.
> >>
> >> Best regards,
> >> Mach
> >>
> >>
> >> --------------------------------------------------
> >> From: "S. Davari" <davarish@yahoo.com>
> >> Sent: Wednesday, July 14, 2010 2:31 PM
> >> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" 
<davari@broadcom.com>
> >> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
> >> <mpls-tp@ietf.org>
> >> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> >>
> >>> Hi Jia,
> >>>
> >>> Label range is a SHOULD requirements and not MUST. The reason for 
Label
> >>> Range is
> >>> mainly for PHY chips that don't have large memory and can't store a 
> >>> lot of
> >>> Labels. Otherwise the PTP LSP is setup via signaling that specifies 
the
> >>> LSP as
> >>> carrying 1588.
> >>>
> >>> So the answer is that if a Label range is used it must be a Global 
range
> >>> within
> >>> a network and should not be used by any router for other 
applications.
> >>>
> >>> Thanks,
> >>> Shahram
> >>>
> >>>
> >>>
> >>> ________________________________
> >>> From: Jia HE <hejia@huawei.com>
> >>> To: Shahram Davari <davari@broadcom.com>
> >>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> >>> Sent: Tue, July 13, 2010 9:50:37 PM
> >>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> >>>
> >>>
> >>> Hi Shahram,
> >>>
> >>> One question about "PTP Label Range":
> >>>
> >>> To my knowledge, label in MPLS network is a local  matter. For 
> >>> example, we
> >>> may
> >>> have per-interface or per-platform label space. Will  this 
specificed 
> >>> "PTP
> >>> Label
> >>> Range" conflict with the current in-use labels  for common LSPs?
> >>>
> >>>
> >>> B.R.
> >>> Jia
> >>>
> >>> ----- Original Message -----
> >>>> From: Shahram    Davari
> >>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; 
pwe3@ietf.org
> >>>> Sent: Thursday, July 08, 2010 3:12 AM
> >>>> Subject: [PWE3] 1588 over MPLS draft
> >>>>
> >>>>
> >>>> Hi All,
> >>>>
> >>>> Please find attached our first draft of 1588 over MPLS.    Since we 

> >>>> have
> >>>> some
> >>>> technical issues converting the Word format to Txt we    couldn?t 
> >>>> upload
> >>>> the
> >>>> draft before the cut-off date. However we will    present the draft 

> >>>> in the
> >>>> next
> >>>> IETF meeting and will upload the draft after the    meeting.
> >>>>
> >>>> Note that the main WG is TicToc but may require    consultation 
with 
> >>>> MPLS
> >>>> and
> >>>> PWE3 WGs.
> >>>>
> >>>> Thanks,
> >>>> Shahram Davari
> >>> ________________________________
> >>> _______________________________________________
> >>>> pwe3 mailing    list
> >>>> pwe3@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/pwe3
> >>>>
> >>>
> >>>
> >>
> >>

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 0012865348257762_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Sharam,</font>
<br><font size=2 face="sans-serif">The label should not be </font><tt><font size=2>per-platform
or per-interface, but more general concept, context specific label space,
see RFC5331 for detail.</font></tt>
<br>
<br><font size=2 face="sans-serif">BR</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br><tt><font size=2>&gt; ------------------------------<br>
&gt; <br>
&gt; Message: 3<br>
&gt; Date: Thu, 15 Jul 2010 10:46:22 -0700<br>
&gt; From: &quot;Shahram Davari&quot; &lt;davari@broadcom.com&gt;<br>
&gt; Subject: Re: [PWE3] [mpls] &nbsp;1588 over MPLS draft<br>
&gt; To: &quot;Joel M. Halpern&quot; &lt;jmh@joelhalpern.com&gt;, &nbsp;
&quot;Mach Chen&quot;<br>
&gt; &nbsp; &nbsp;&lt;mach@huawei.com&gt;</font></tt>
<br><tt><font size=2>&gt; Cc: &quot;mpls@ietf.org&quot; &lt;mpls@ietf.org&gt;,
&quot;ticctoc@ietf.org&quot;<br>
&gt; &nbsp; &nbsp;&lt;ticctoc@ietf.org&gt;, &nbsp; &quot;mpls-tp@ietf.org&quot;
&lt;mpls-tp@ietf.org&gt;,<br>
&gt; &nbsp; &nbsp;&quot;pwe3@ietf.org&quot; &lt;pwe3@ietf.org&gt;, &nbsp;
&quot;S. Davari&quot; &lt;davarish@yahoo.com&gt;<br>
&gt; Message-ID:<br>
&gt; &nbsp; &nbsp;&lt;2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.<br>
&gt; broadcom.com&gt;<br>
&gt; &nbsp; &nbsp;<br>
&gt; Content-Type: text/plain; charset=utf-8<br>
&gt; <br>
&gt; Hi Joel,<br>
&gt; <br>
&gt; I agree with your logic, but the idea is a bit different:<br>
&gt; <br>
&gt; All we need is a label range, it does not need to be globally unique<br>
&gt; in the network and it does not even need to be the same on the Tx
<br>
&gt; and Rx direction of the same link. Although we need time stamping
<br>
&gt; both on Rx and on Tx, but on Rx a node is in control of its own <br>
&gt; label and on Tx the downstream node should advertise some label <br>
&gt; range. What we don't want is that the downstream node to advertise
<br>
&gt; random labels for each LSP carrying PTP.<br>
&gt; <br>
&gt; I will update the draft to mention that the label range does not <br>
&gt; require to be global but it can be per-platform or even per-interface.<br>
&gt; <br>
&gt; Thanks,<br>
&gt; Shahram<br>
&gt; <br>
&gt; -----Original Message-----<br>
&gt; From: Joel M. Halpern [mailto:jmh@joelhalpern.com] <br>
&gt; Sent: Wednesday, July 14, 2010 8:21 PM<br>
&gt; To: Mach Chen<br>
&gt; Cc: Shahram Davari; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org;<br>
&gt; ticctoc@ietf.org; mpls-tp@ietf.org<br>
&gt; Subject: Re: [mpls] [PWE3] 1588 over MPLS draft<br>
&gt; <br>
&gt; Remember that if what is required is that the message arriving at
the <br>
&gt; 1588 supporting device have a certain label range, that is a purely
<br>
&gt; local matter. &nbsp;As long as the singaling carries the indication
that the <br>
&gt; LSP is to be dedicated to 1588 traffic (a reasonable extension to
the <br>
&gt; signaling), the downstream switch can pick what label to assign to
that LSP.<br>
&gt; <br>
&gt; If the goal is to have the outgoing label be from a specific range,
that <br>
&gt; is essentially impossible in the proposed architecture. &nbsp;The
proposed <br>
&gt; architecture is one in which 1588 switches are peers with existing
LSRs <br>
&gt; using MPLS. &nbsp;As such, in order to have a label range for outgoing
<br>
&gt; labels, the existing MPLS LSR would somehow have to know about this
<br>
&gt; reserved label range, not use those labels for other purposes, and
<br>
&gt; assign those labels to 1588 LSPs. &nbsp;All of which is <br>
&gt; non-backwards-compatible. &nbsp;If the 1588 LSPs were actually pseudowires,
<br>
&gt; tunneled over LSPs, then any number of things are possible.<br>
&gt; <br>
&gt; Yours,<br>
&gt; Joel M. Halpern<br>
&gt; <br>
&gt; Mach Chen wrote:<br>
&gt; &gt; Hi Shahram,<br>
&gt; &gt; <br>
&gt; &gt; I agree that the label range idea is an efficient way that could
reduce <br>
&gt; &gt; the storage requirement of PHY chips.<br>
&gt; &gt; <br>
&gt; &gt; It's easy to require one or limited nodes to reserve a label
range, but <br>
&gt; &gt; IMHO, it very difficut to require all nodes of a large network
to do <br>
&gt; &gt; this and even worse when some labels are already used by other
LSPs, <br>
&gt; &gt; unless there are some mechanisms to negotiate/advertise(e.g.,
flooding <br>
&gt; &gt; the label range by IGP within the network) the proper label range
hence <br>
&gt; &gt; to aviod label collision.<br>
&gt; &gt; <br>
&gt; &gt; Best regards,<br>
&gt; &gt; Mach<br>
&gt; &gt; <br>
&gt; &gt; --------------------------------------------------<br>
&gt; &gt; From: &quot;Shahram Davari&quot; &lt;davari@broadcom.com&gt;<br>
&gt; &gt; Sent: Thursday, July 15, 2010 1:58 AM<br>
&gt; &gt; To: &quot;Mach Chen&quot; &lt;mach@huawei.com&gt;; &quot;S. Davari&quot;
&lt;davarish@yahoo.com&gt;; <br>
&gt; &gt; &quot;Jia HE&quot; &lt;hejia@huawei.com&gt;<br>
&gt; &gt; Cc: &lt;mpls@ietf.org&gt;; &lt;pwe3@ietf.org&gt;; &lt;ticctoc@ietf.org&gt;;
<br>
&gt; &gt; &lt;mpls-tp@ietf.org&gt;<br>
&gt; &gt; Subject: RE: [mpls] [PWE3] 1588 over MPLS draft<br>
&gt; &gt; <br>
&gt; &gt;&gt; Hi Mach,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; When a service provider wants to create these PTP LSPs, what
is wrong <br>
&gt; &gt;&gt; with allocating a range of labels for this purpose? This
is purely a <br>
&gt; &gt;&gt; software exercise. There are 2 million labels available to
each node, <br>
&gt; &gt;&gt; why can't some of them be allocated by software to PTP?<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; In theory what you say is correct and should work, but in
practice <br>
&gt; &gt;&gt; there is a function called 1-step Transparent clocking that
requires <br>
&gt; &gt;&gt; time stamping at the PHY (immediately when the packet is
received or <br>
&gt; &gt;&gt; transmitted). PHY chips don't have CAM or lots of memory
to store a <br>
&gt; &gt;&gt; few thousand random labels. The label range will solve that
problem <br>
&gt; &gt;&gt; and is consistent with MPLS architecture.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Thanks,<br>
&gt; &gt;&gt; Shahram<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt; From: Mach Chen [mailto:mach@huawei.com]<br>
&gt; &gt;&gt; Sent: Wednesday, July 14, 2010 1:53 AM<br>
&gt; &gt;&gt; To: S. Davari; Jia HE; Shahram Davari<br>
&gt; &gt;&gt; Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org<br>
&gt; &gt;&gt; Subject: Re: [mpls] [PWE3] 1588 over MPLS draft<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Hi Shahram,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; From the view of implementation, there is no more difference
between <br>
&gt; &gt;&gt; SHOULD<br>
&gt; &gt;&gt; and MUST :-)<br>
&gt; &gt;&gt; For me, the Label Range is more like a mechanim to notify
related <br>
&gt; &gt;&gt; nodes that<br>
&gt; &gt;&gt; some LSPs are dedicated for PTP messages other than the chips
memory<br>
&gt; &gt;&gt; limitation, because the memory restriction is always there
whatever <br>
&gt; &gt;&gt; you use<br>
&gt; &gt;&gt; Label Range or not.<br>
&gt; &gt;&gt; IMHO, since the objective is to tell related MPLS nodes which
LSPs are <br>
&gt; &gt;&gt; PTP<br>
&gt; &gt;&gt; LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is
enough and <br>
&gt; &gt;&gt; seems<br>
&gt; &gt;&gt; more common. And it will avoid the strict requirement of
&quot;the network and<br>
&gt; &gt;&gt; all nodes required to support the Label range&quot;.<br>
&gt; &gt;&gt; In addition, there should be some mechanims(e.g., ISIS/OSPF
<br>
&gt; &gt;&gt; extensions) for<br>
&gt; &gt;&gt; nodes to advertise their PTP capability hence to help PTP
LSPs <br>
&gt; &gt;&gt; computation.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Best regards,<br>
&gt; &gt;&gt; Mach<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; --------------------------------------------------<br>
&gt; &gt;&gt; From: &quot;S. Davari&quot; &lt;davarish@yahoo.com&gt;<br>
&gt; &gt;&gt; Sent: Wednesday, July 14, 2010 2:31 PM<br>
&gt; &gt;&gt; To: &quot;Jia HE&quot; &lt;hejia@huawei.com&gt;; &quot;Shahram
Davari&quot; &lt;davari@broadcom.com&gt;<br>
&gt; &gt;&gt; Cc: &lt;mpls@ietf.org&gt;; &lt;pwe3@ietf.org&gt;; &lt;ticctoc@ietf.org&gt;;
<br>
&gt; &gt;&gt; &lt;mpls-tp@ietf.org&gt;<br>
&gt; &gt;&gt; Subject: Re: [mpls] [PWE3] 1588 over MPLS draft<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; Hi Jia,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Label range is a SHOULD requirements and not MUST. The
reason for Label<br>
&gt; &gt;&gt;&gt; Range is<br>
&gt; &gt;&gt;&gt; mainly for PHY chips that don't have large memory and
can't store a <br>
&gt; &gt;&gt;&gt; lot of<br>
&gt; &gt;&gt;&gt; Labels. Otherwise the PTP LSP is setup via signaling
that specifies the<br>
&gt; &gt;&gt;&gt; LSP as<br>
&gt; &gt;&gt;&gt; carrying 1588.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; So the answer is that if a Label range is used it must
be a Global range<br>
&gt; &gt;&gt;&gt; within<br>
&gt; &gt;&gt;&gt; a network and should not be used by any router for other
applications.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt; Shahram<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; ________________________________<br>
&gt; &gt;&gt;&gt; From: Jia HE &lt;hejia@huawei.com&gt;<br>
&gt; &gt;&gt;&gt; To: Shahram Davari &lt;davari@broadcom.com&gt;<br>
&gt; &gt;&gt;&gt; Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org<br>
&gt; &gt;&gt;&gt; Sent: Tue, July 13, 2010 9:50:37 PM<br>
&gt; &gt;&gt;&gt; Subject: Re: [mpls] [PWE3] 1588 over MPLS draft<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Hi Shahram,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; One question about &quot;PTP Label Range&quot;:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; To my knowledge, label in MPLS network is a local &nbsp;matter.
For <br>
&gt; &gt;&gt;&gt; example, we<br>
&gt; &gt;&gt;&gt; may<br>
&gt; &gt;&gt;&gt; have per-interface or per-platform label space. Will
&nbsp;this specificed <br>
&gt; &gt;&gt;&gt; &quot;PTP<br>
&gt; &gt;&gt;&gt; Label<br>
&gt; &gt;&gt;&gt; Range&quot; conflict with the current in-use labels &nbsp;for
common LSPs?<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; B.R.<br>
&gt; &gt;&gt;&gt; Jia<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; ----- Original Message -----<br>
&gt; &gt;&gt;&gt;&gt; From: Shahram &nbsp; &nbsp;Davari<br>
&gt; &gt;&gt;&gt;&gt; To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org
; pwe3@ietf.org<br>
&gt; &gt;&gt;&gt;&gt; Sent: Thursday, July 08, 2010 3:12 AM<br>
&gt; &gt;&gt;&gt;&gt; Subject: [PWE3] 1588 over MPLS draft<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Hi All,<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Please find attached our first draft of 1588 over
MPLS. &nbsp; &nbsp;Since we <br>
&gt; &gt;&gt;&gt;&gt; have<br>
&gt; &gt;&gt;&gt;&gt; some<br>
&gt; &gt;&gt;&gt;&gt; technical issues converting the Word format to Txt
we &nbsp; &nbsp;couldn?t <br>
&gt; &gt;&gt;&gt;&gt; upload<br>
&gt; &gt;&gt;&gt;&gt; the<br>
&gt; &gt;&gt;&gt;&gt; draft before the cut-off date. However we will &nbsp;
&nbsp;present the draft <br>
&gt; &gt;&gt;&gt;&gt; in the<br>
&gt; &gt;&gt;&gt;&gt; next<br>
&gt; &gt;&gt;&gt;&gt; IETF meeting and will upload the draft after the
&nbsp; &nbsp;meeting.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Note that the main WG is TicToc but may require &nbsp;
&nbsp;consultation with <br>
&gt; &gt;&gt;&gt;&gt; MPLS<br>
&gt; &gt;&gt;&gt;&gt; and<br>
&gt; &gt;&gt;&gt;&gt; PWE3 WGs.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;&gt; Shahram Davari<br>
&gt; &gt;&gt;&gt; ________________________________<br>
&gt; &gt;&gt;&gt; _______________________________________________<br>
&gt; &gt;&gt;&gt;&gt; pwe3 mailing &nbsp; &nbsp;list<br>
&gt; &gt;&gt;&gt;&gt; pwe3@ietf.org<br>
&gt; &gt;&gt;&gt;&gt; https://www.ietf.org/mailman/listinfo/pwe3<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;</font></tt><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 0012865348257762_=--


From davarish@yahoo.com  Thu Jul 15 20:51:45 2010
Return-Path: <davarish@yahoo.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FA6F3A6822 for <mpls@core3.amsl.com>; Thu, 15 Jul 2010 20:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SvOPUgvMmdlF for <mpls@core3.amsl.com>; Thu, 15 Jul 2010 20:51:43 -0700 (PDT)
Received: from n15.bullet.mail.mud.yahoo.com (n15.bullet.mail.mud.yahoo.com [68.142.206.42]) by core3.amsl.com (Postfix) with SMTP id 4F1493A67EA for <mpls@ietf.org>; Thu, 15 Jul 2010 20:51:43 -0700 (PDT)
Received: from [68.142.200.227] by n15.bullet.mail.mud.yahoo.com with NNFMP; 16 Jul 2010 03:51:52 -0000
Received: from [66.196.97.152] by t8.bullet.mud.yahoo.com with NNFMP; 16 Jul 2010 03:51:51 -0000
Received: from [127.0.0.1] by omp205.mail.re3.yahoo.com with NNFMP; 16 Jul 2010 03:51:51 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 860575.10397.bm@omp205.mail.re3.yahoo.com
Received: (qmail 52842 invoked by uid 60001); 16 Jul 2010 03:51:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1279252311; bh=vCaLWYHh1oZj7NwI917l9VVZMZmzXjJSJRMJcskjYUI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=DArt+W+l95PBL+qxWzRQWV1nxeDw9aDV6WGU2BzSMxN4L+e6lcriCxrZxe//MhUwC2KT5J9MBriJEfQHLcd+9zutYVGAsBw1tyLXv3McwVF8iISxLoasjoj/K4cL6SoAcSzMgd4igvG706LRdfg6GdtwfiBplR26RgKpdGQPzBE=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=vewhnNHr98d35NwuIp4QoBkJydbffa2VQWGNuDhIM1r2vJ2xU6WQZD8UkWESfi1BOjMbdieJQ92/PLdfB7rda4jBN0YkW3t/IlTlBExcdXYK34MElz5IUKMC8JDHWdc3W6TES9SIFBsgyhdhniLW2BjEdk3wwjrkQOiG5S5+54s=;
Message-ID: <629665.45604.qm@web88412.mail.re1.yahoo.com>
X-YMail-OSG: Za7wlhgVM1nC1F39Cmhh.pUo2lyTo8SKPTn5M.JuJuImxBm h_LBYLyr4kkaLG_E_oMl9Z.tly6hUkQYICuFRV1u.rIr8ljcI.0tIfiSBnsc 3wmXzZG2jQa4e5XL4YTlTNovBpK9Koe6sA0mGkUHFa7KwlE4jkj107yRx.hk fQybALf5E.nkYQqFBJe4hhkmd8LABdpCDQNIABrJ540fnY.CCxJHwWFDMXCo uhh.T_xcBqYeKycykMmo56waZaGdI0dSacmHp7ksWRNxmZQUVlhosKELHbFQ weyK.Ay4A9Q.VgCToQDN479_Pv8xyqAczvxF4jFFRZ8C0ZpClWa8eAIO9QAt Tfv6DlJbw1shvMTXn
Received: from [166.134.150.116] by web88412.mail.re1.yahoo.com via HTTP; Thu, 15 Jul 2010 20:51:51 PDT
X-Mailer: YahooMailWebService/0.8.104.276605
Date: Thu, 15 Jul 2010 20:51:51 -0700 (PDT)
From: Shahram Davari <davarish@yahoo.com>
To: Mach Chen <mach@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2010 03:51:45 -0000

Mach=0A=0AIs this supported by RSVP-TE?=0A=0ABest Regards,=0AShahram=0A=0A=
=0AOn Jul 15, 2010, at 6:35 PM, Mach Chen <mach@huawei.com> wrote:=0A=0AHi =
Shahram,=0A=0AIf the 1588-capability router does downstream (for Rx directi=
on) and upstream (for Tx direction) label distribution respectively, it may=
 not require its adjacent routers to upgrade.=0A=0ABest regards,=0AMach=0A=
=0A--------------------------------------------------=0AFrom: "Shahram Dava=
ri" <davari@broadcom.com>=0ASent: Friday, July 16, 2010 4:37 AM=0ATo: "Joel=
 M. Halpern" <jmh@joelhalpern.com>=0ACc: <mpls@ietf.org>; <pwe3@ietf.org>; =
<ticctoc@ietf.org>; <mpls-tp@ietf.org>=0ASubject: Re: [mpls] [PWE3] 1588 ov=
er MPLS draft=0A=0AHi Joel,=0A=0AOK, do you have a better proposal?=0A=0ATh=
x=0AShahram=0A=0A-----Original Message-----=0AFrom: Joel M. Halpern [mailto=
:jmh@joelhalpern.com]=0ASent: Thursday, July 15, 2010 1:32 PM=0ATo: Shahram=
 Davari=0ACc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.=
org=0ASubject: Re: [mpls] [PWE3] 1588 over MPLS draft=0A=0AI am sorry, but =
requiring every LSR in the infrastructure to get a=0Asoftware upgrade in or=
der to allow for the presence of 1588-supporting=0Adevices is a MAJOR issue=
.  It is NOT backwards compatible.  Operators=0A(wether service provider or=
 enterprise IT) do NOT like being told they=0Aahve to upgrade the software =
on all devices in their network in order to=0Aadd a capability that those d=
evices are not engaging in.=0A=0AWhile one can argue about the "ease" of th=
e specific software change,=0Athere is from an operational perspective no s=
uch thing as an easy=0Aupgrade of any device, and there is definitely no su=
ch thing as an easy=0Aupgrade of all the devices in the network.=0A=0AYours=
,=0AJoel=0A=0AShahram Davari wrote:=0AHi Joel,=0A=0AThere are 2 aspects to =
this puzzle:=0A=0A1) Hardware support for 1588 in a device.=0A2) Software s=
upport for 1588 in the form of allocating labels to PTP LSPs=0A=0AA router =
that wants to perform 1588 time stamping must have both (1) and (2) functio=
nality. While a router in=0A>the path of a PTP LSP that does not support (1=
) should support (2) and=0Aadvertise labels from some arbitrary=0A>range fo=
r PTP LSP.=0A=0AIt is quite easy to upgrade a router software so that when =
it receives RSVP-TE label request to assign label=0A>from an arbitrary loca=
l range.=0A=0ASo I don't see any issue here.=0A=0AThanks,=0AShahram=0A=0A=
=0A=0A-----Original Message-----=0AFrom: Joel M. Halpern [mailto:jmh@joelha=
lpern.com]=0ASent: Thursday, July 15, 2010 12:06 PM=0ATo: Shahram Davari=0A=
Cc: Mach Chen; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; ticctoc@iet=
f.org; mpls-tp@ietf.org=0ASubject: Re: [mpls] [PWE3] 1588 over MPLS draft=
=0A=0AArchitecturally, as I understand the draft, the downstream neighbor o=
f a=0A1588 supporting device (on the PTP carrying LSP) may not itself be a=
=0A1588 supporting device.  Is that correct?  If that is not correct, if=0A=
instead the structure is that PTP supporting LSPs are established=0Abetween=
 adjacent enhanced devices, then I can see how some sort of a=0Alabel range=
 might make sense.=0A=0AIf however, the downstream node you refer to may be=
 an existing LSR,=0Athen I do not see how you can ask an existing LSR to al=
locate a label=0Arange for a function it does not understand.=0A=0AYours,=
=0AJoel=0A=0AShahram Davari wrote:=0AHi Joel,=0A=0AI agree with your logic,=
 but the idea is a bit different:=0A=0AAll we need is a label range, it doe=
s not need to be globally unique in the network and it does=0A>not even nee=
d to be the same on the Tx and Rx direction of the same=0Alink. Although we=
 need time=0A>stamping both on Rx and on Tx, but on Rx a node is in control=
 of its=0Aown label and on Tx the=0A>downstream node should advertise some =
label range. What we don't want=0Ais that the downstream=0A>node to adverti=
se random labels for each LSP carrying PTP.=0AI will update the draft to me=
ntion that the label range does not require to be global but it can=0A>be p=
er-platform or even per-interface.=0AThanks,=0AShahram=0A=0A-----Original M=
essage-----=0AFrom: Joel M. Halpern [mailto:jmh@joelhalpern.com]=0ASent: We=
dnesday, July 14, 2010 8:21 PM=0ATo: Mach Chen=0ACc: Shahram Davari; S. Dav=
ari; Jia HE; mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.o=
rg=0ASubject: Re: [mpls] [PWE3] 1588 over MPLS draft=0A=0ARemember that if =
what is required is that the message arriving at the=0A1588 supporting devi=
ce have a certain label range, that is a purely=0Alocal matter.  As long as=
 the singaling carries the indication that the=0ALSP is to be dedicated to =
1588 traffic (a reasonable extension to the=0Asignaling), the downstream sw=
itch can pick what label to assign to that LSP.=0A=0AIf the goal is to have=
 the outgoing label be from a specific range, that=0Ais essentially impossi=
ble in the proposed architecture.  The proposed=0Aarchitecture is one in wh=
ich 1588 switches are peers with existing LSRs=0Ausing MPLS.  As such, in o=
rder to have a label range for outgoing=0Alabels, the existing MPLS LSR wou=
ld somehow have to know about this=0Areserved label range, not use those la=
bels for other purposes, and=0Aassign those labels to 1588 LSPs.  All of wh=
ich is=0Anon-backwards-compatible.  If the 1588 LSPs were actually pseudowi=
res,=0Atunneled over LSPs, then any number of things are possible.=0A=0AYou=
rs,=0AJoel M. Halpern=0A=0AMach Chen wrote:=0AHi Shahram,=0A=0AI agree that=
 the label range idea is an efficient way that could reduce=0Athe storage r=
equirement of PHY chips.=0A=0AIt's easy to require one or limited nodes to =
reserve a label range, but=0AIMHO, it very difficut to require all nodes of=
 a large network to do=0Athis and even worse when some labels are already u=
sed by other LSPs,=0Aunless there are some mechanisms to negotiate/advertis=
e(e.g., flooding=0Athe label range by IGP within the network) the proper la=
bel range hence=0Ato aviod label collision.=0A=0ABest regards,=0AMach=0A=0A=
--------------------------------------------------=0AFrom: "Shahram Davari"=
 <davari@broadcom.com>=0ASent: Thursday, July 15, 2010 1:58 AM=0ATo: "Mach =
Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>;=0A"Jia HE" <heji=
a@huawei.com>=0ACc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>;=
=0A<mpls-tp@ietf.org>=0ASubject: RE: [mpls] [PWE3] 1588 over MPLS draft=0A=
=0AHi Mach,=0A=0AWhen a service provider wants to create these PTP LSPs, wh=
at is wrong=0Awith allocating a range of labels for this purpose? This is p=
urely a=0Asoftware exercise. There are 2 million labels available to each n=
ode,=0Awhy can't some of them be allocated by software to PTP?=0A=0AIn theo=
ry what you say is correct and should work, but in practice=0Athere is a fu=
nction called 1-step Transparent clocking that requires=0Atime stamping at =
the PHY (immediately when the packet is received or=0Atransmitted). PHY chi=
ps don't have CAM or lots of memory to store a=0Afew thousand random labels=
. The label range will solve that problem=0Aand is consistent with MPLS arc=
hitecture.=0A=0AThanks,=0AShahram=0A=0A-----Original Message-----=0AFrom: M=
ach Chen [mailto:mach@huawei.com]=0ASent: Wednesday, July 14, 2010 1:53 AM=
=0ATo: S. Davari; Jia HE; Shahram Davari=0ACc: mpls@ietf.org; pwe3@ietf.org=
; ticctoc@ietf.org; mpls-tp@ietf.org=0ASubject: Re: [mpls] [PWE3] 1588 over=
 MPLS draft=0A=0AHi Shahram,=0A=0AFrom the view of implementation, there is=
 no more difference between=0ASHOULD=0Aand MUST :-)=0AFor me, the Label Ran=
ge is more like a mechanim to notify related=0Anodes that=0Asome LSPs are d=
edicated for PTP messages other than the chips memory=0Alimitation, because=
 the memory restriction is always there whatever=0Ayou use=0ALabel Range or=
 not.=0AIMHO, since the objective is to tell related MPLS nodes which LSPs =
are=0APTP=0ALSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enou=
gh and=0Aseems=0Amore common. And it will avoid the strict requirement of "=
the network and=0Aall nodes required to support the Label range".=0AIn addi=
tion, there should be some mechanims(e.g., ISIS/OSPF=0Aextensions) for=0Ano=
des to advertise their PTP capability hence to help PTP LSPs=0Acomputation.=
=0A=0ABest regards,=0AMach=0A=0A=0A----------------------------------------=
----------=0AFrom: "S. Davari" <davarish@yahoo.com>=0ASent: Wednesday, July=
 14, 2010 2:31 PM=0ATo: "Jia HE" <hejia@huawei.com>; "Shahram Davari" <dava=
ri@broadcom.com>=0ACc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>=
;=0A<mpls-tp@ietf.org>=0ASubject: Re: [mpls] [PWE3] 1588 over MPLS draft=0A=
=0AHi Jia,=0A=0ALabel range is a SHOULD requirements and not MUST. The reas=
on for Label=0ARange is=0Amainly for PHY chips that don't have large memory=
 and can't store a=0Alot of=0ALabels. Otherwise the PTP LSP is setup via si=
gnaling that specifies the=0ALSP as=0Acarrying 1588.=0A=0ASo the answer is =
that if a Label range is used it must be a Global range=0Awithin=0Aa networ=
k and should not be used by any router for other applications.=0A=0AThanks,=
=0AShahram=0A=0A=0A=0A________________________________=0AFrom: Jia HE <heji=
a@huawei.com>=0ATo: Shahram Davari <davari@broadcom.com>=0ACc: mpls@ietf.or=
g; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org=0ASent: Tue, July 13, =
2010 9:50:37 PM=0ASubject: Re: [mpls] [PWE3] 1588 over MPLS draft=0A=0A=0AH=
i Shahram,=0A=0AOne question about "PTP Label Range":=0A=0ATo my knowledge,=
 label in MPLS network is a local  matter. For=0Aexample, we=0Amay=0Ahave p=
er-interface or per-platform label space. Will  this specificed=0A"PTP=0ALa=
bel=0ARange" conflict with the current in-use labels  for common LSPs?=0A=
=0A=0AB.R.=0AJia=0A=0A----- Original Message -----=0AFrom: Shahram    Davar=
i=0ATo: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org=
=0ASent: Thursday, July 08, 2010 3:12 AM=0ASubject: [PWE3] 1588 over MPLS d=
raft=0A=0A=0AHi All,=0A=0APlease find attached our first draft of 1588 over=
 MPLS.    Since we=0Ahave=0Asome=0Atechnical issues converting the Word for=
mat to Txt we    couldn=E2=80=99t=0Aupload=0Athe=0Adraft before the cut-off=
 date. However we will    present the draft=0Ain the=0Anext=0AIETF meeting =
and will upload the draft after the    meeting.=0A=0ANote that the main WG =
is TicToc but may require    consultation with=0AMPLS=0Aand=0APWE3 WGs.=0A=
=0AThanks,=0AShahram Davari=0A________________________________=0A__________=
_____________________________________=0Apwe3 mailing    list=0Apwe3@ietf.or=
g=0Ahttps://www.ietf.org/mailman/listinfo/pwe3=0A=0A=0A____________________=
___________________________=0Ampls mailing list=0Ampls@ietf.org=0Ahttps://w=
ww.ietf.org/mailman/listinfo/mpls=0A=0A=0A_________________________________=
______________=0Ampls mailing list=0Ampls@ietf.org=0Ahttps://www.ietf.org/m=
ailman/listinfo/mpls=0A=0A=0A______________________________________________=
_=0Ampls mailing list=0Ampls@ietf.org=0Ahttps://www.ietf.org/mailman/listin=
fo/mpls=0A_______________________________________________=0Ampls mailing li=
st=0Ampls@ietf.org=0Ahttps://www.ietf.org/mailman/listinfo/mpls=0A=0A=0A


From Adrian.Farrel@huawei.com  Fri Jul 16 03:33:49 2010
Return-Path: <Adrian.Farrel@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE6AD3A68B6 for <mpls@core3.amsl.com>; Fri, 16 Jul 2010 03:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599]
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 MidvGZd6o6uI for <mpls@core3.amsl.com>; Fri, 16 Jul 2010 03:33:47 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id CE17F3A6875 for <mpls@ietf.org>; Fri, 16 Jul 2010 03:33:47 -0700 (PDT)
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 <0L5N002NSC0M5I@usaga01-in.huawei.com> for mpls@ietf.org; Fri, 16 Jul 2010 03:33:59 -0700 (PDT)
Received: from your029b8cecfe (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 <0L5N00J1YC0LSY@usaga01-in.huawei.com> for mpls@ietf.org; Fri, 16 Jul 2010 03:33:58 -0700 (PDT)
Date: Fri, 16 Jul 2010 11:30:21 +0100
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: ccamp@ops.ietf.org, mpls@ietf.org
Message-id: <C90B27CF678D461D80071F944895A7A3@your029b8cecfe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Subject: [mpls] Fw: (another) WGLC started for "RSVP Security Groupkeying" ID
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <Adrian.Farrel@huawei.com>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2010 10:33:49 -0000

Heads up!

Send any comments to the TSVWG list or ask your WG chairs to forward them.

Adrian
----- Original Message ----- 
From: "James M. Polk" <jmpolk@cisco.com>
To: "tsvwg" <tsvwg@ietf.org>
Sent: Wednesday, July 14, 2010 5:48 PM
Subject: (another) WGLC started for "RSVP Security Groupkeying" ID


> TSVWG
>
> This is to let everyone know we've initiated a new WGLC for the "RSVP 
> Security Groupkeying" ID here.
>
> http://tools.ietf.org/wg/tsvwg/draft-ietf-tsvwg-rsvp-security-groupkeying/
>
> This ID has had some significant modifications based on the SecDir review 
> by Stephen Kent.  Please reread this ID to verify these changes are 
> appropriate, and do not introduce new issues or concerns.
>
> Once you have reviewed this version, please send a note to the list with 
> an indication whether or not this doc should proceed to the IESG for RFC 
> consideration. We chairs need to gauge WG interest before this (or any) 
> document progresses towards publication.
>
> Because of the IETF meeting so close, this is an extended WGLC, lasting 4 
> weeks - ending August 11th, 2010.
>
> Please do review this document and let us/the list know what you think.
>
> James & Gorry
> TSVWG chairs
>
> 


From loa@pi.nu  Fri Jul 16 04:26:26 2010
Return-Path: <loa@pi.nu>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D74F3A6947; Fri, 16 Jul 2010 04:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tY0xYq7pEcft; Fri, 16 Jul 2010 04:26:25 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id CD77B3A6944; Fri, 16 Jul 2010 04:26:24 -0700 (PDT)
Received: from [79.138.219.27] (79.138.219.27.bredband.tre.se [79.138.219.27]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id CCBDDD404F; Fri, 16 Jul 2010 13:26:31 +0200 (CEST)
Message-ID: <4C4041D3.6020407@pi.nu>
Date: Fri, 16 Jul 2010 13:26:11 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: mpls@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,  MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>
References: <4C2B111A.3000407@pi.nu>
In-Reply-To: <4C2B111A.3000407@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Dan Frost <danfrost@cisco.com>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [mpls] poll on draft-frost-mpls-tp-loss-delay-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2010 11:26:26 -0000

Working Group,

this poll has ended.


We have a new working group document, could the authors please
re-publish the document as draft-ietf-mpls-tp-loss-delay-00.txt
without any other changes than the file name and dates.

/Loa

On 2010-06-30 11:40, Loa Andersson wrote:
> Working Group,
>
> this email is to start a poll to adopt
> draft-frost-mpls-tp-loss-delay-02.txt
> as an MPLS working group draft.
>
> After recent experience, the chairs would like to remind you all
> what it means to conduct a poll to adopt a draft as a working group
> draft.
>
> - Please recall that the IETF does not "vote." Polls of a working
> group are to gather information to help the chairs make their
> decisions. Voting is not part of the normal working methods of
> an IETF working group.
>
> - The "rough consensus" process used in the working group assumes
> that people expressing opinions are also participating in the
> development of standards documents.
>
> - Subscription to the list specifically to express an opinion is
> noticed by the chairs who has access to information on the new list
> members. Such behavior is not part of the normal working methods.
>
> - The purpose of a poll for adoption is to help the chairs understand
> the level of support for a document (i.e. who has read it, who
> believes it is a good starting point for working group work, who
> will contribute to the work) and whether there are any significant
> technical issues. Statements of objection must be backed up by
> proper technical reasons.
>
> So please respond to this poll indicating whether you support the
> adoption of this draft or stating your technical issues.
>
> This poll ends eob July 15.
>
>
> Loa and George
> mpls wg co-chairs
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From wwwrun@core3.amsl.com  Fri Jul 16 06:30:29 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 638BA3A687D; Fri, 16 Jul 2010 06:30:28 -0700 (PDT)
From: Stewart Bryant(IETF RTG AREA) <stbryant@cisco.com>
To: tsbsg15@itu.int, greg.jones@itu.int
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100716133028.638BA3A687D@core3.amsl.com>
Date: Fri, 16 Jul 2010 06:30:28 -0700 (PDT)
Cc: mpls@ietf.org, steve.trowbridge@alcatel-lucent.com, stbryant@cisco.com, yoichi.maeda@ntt-at.co.jp, chair@ietf.org, hiroshi.ota@itu.int, iesg@ietf.org, rcallon@juniper.net, paf@cisco.com, ghani.abbas@ericsson.com, adrian.farrel@huawei.com
Subject: [mpls] New Liaison Statement, "Liaison Statement: LS214 - MPLS-TP survivability framework draft reviewed (ref # 28.05)"
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2010 13:30:29 -0000

Title: Liaison Statement: LS214 - MPLS-TP survivability framework draft reviewed (ref # 28.05)
Submission Date: 2010-07-16
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=923 

From: Stewart Bryant(IETF RTG AREA) <stbryant@cisco.com>
To: ITU-T SG 15(tsbsg15@itu.int, greg.jones@itu.int)
Cc: adrian.farrel@huawei.com
chair@ietf.org
ghani.abbas@ericsson.com
hiroshi.ota@itu.int
iesg@ietf.org
loa@pi.nu
mpls@ietf.org
paf@cisco.com
rcallon@juniper.net
steve.trowbridge@alcatel-lucent.com
swallow@cisco.com
yoichi.maeda@ntt-at.co.jp
Reponse Contact: stbryant@cisco.com
adrian.farrel@huawei.com
Technical Contact: stbryant@cisco.com
adrian.farrel@huawei.com
Purpose: In response 
Body: Thank you for your further liaison discussing our disposition of your 
comments on draft-ietf-mpls-tp-survive-fwk. As you
will be aware, this document is now in an advanced state in
the IETF process.

We have examined your comments and respond as follows:

Comment 1
No further action is required

Comment 2
(2.1) Similar text to that which you requested has been added to the 
end of Section 4.3.2
(2.2) No further action is required

Comment 3
(3.1) Text to clarify that this case applies only to linear 
protection has been added. A forward pointer to section 4.8 has been 
added for ring protection.

(3.2) The indicated document is present as an Informative reference
and is in accordance with normal IETF practice.
 
It is our understanding from reading A.5 and 
http://www.itu.int/dms_pub/itu-t/oth/3E/01/T3E010000010001MSWE.doc 
that you are able to make bibliographic reference to Internet-Drafts 
that are work in progress. Further, it  is our understanding that 
only Normative references are cascaded.

Comment 4
This substantial proposal of new text has been received too late 
in the IETF review cycle to be included. This text would need
to be introduced via a new Internet-Draft.

Comment 5
(5.1) No further action is required
(5.2) The current document shows RFC4427 as a Normative  reference 
and G.808.1 as an Informative reference. This is appropriate for 
how they are used in this document and this has been confirmed 
through IETF consensus.

If the ITU-T believe that there is a discrepancy between RFC4427 
and G.808.1, we suggest that this should be addressed by proposing 
revised a revised version of RFC4427.

Comment 6
No further action is required

Comment 7
No further action is required

Comment 8
Thank you for highlighting the continued confusion over the word 
"level". We think that your proposed change to "type" does not 
convey the different qualities of recovery, and may lead to 
confusion with "mechanism". We have changed to use the word "grade". 
This change can be seen in sections 1.4, 4, 4.1.1, 4.3, 4.3.2, 
4.4.1, 4.4.2, 4.4.3, 4.6, and 4.9.1.

Comment 9
No further action is required

Comment 10
Please see resolution for comment 3

Comment 11
This reference to draft-ietf-mpls-tp-linear-protection has been 
retained (see resolution for comment 3). This reference documents 
where the solution that will be described, but, within the IETF 
process, makes no pre-judgment about the explicit solution. 
Please note also that the solution documented in the 
draft-ietf-mpls-tp-linear-protection can be changed at any time 
by working group consensus.

Comment 12
No further action is required

General Comments
No further action is required

New Comment A
The current IETF consensus on this document is that the term "span" 
is as defined in this document and is distinct from a "link" as 
explained in this document.

We are therefore unable to make this change to this document at 
this stage in the process.

We hope that the Editors of draft-ietf-mpls-tp-rosetta-stone will 
bring that document into line with these definitions.

New Comment B
The change has been made as suggested.

New Comment C
The text has been changed to highlight that segment recovery 
(section 4.2.2) is not a form of span recovery.

New Comment D
Text has been added to section 4.3 along the lines of your suggestion.

New Comment E
This document is not a requirements document and sets no MPLS-TP
 requirements. There is, therefore, no need for any change. 
Also it is now too late in the IETF process to make any movement 
between normative and non-normative.

New Comment F
It looks as if the correct reference is to section 4.4.3. This 
text has been clarified.

New Comment G
This is not new text - it was present in the 00 version of this 
document. The text has been previously reviewed by the ITU-T 
experts and there is no scope for further review.

New Comment H
This proposal for the removal of a significant piece of text 
that has been present since the 00 version of the  document 
comes after IETF consensus and is therefore too late in the 
IETF process for this change to be considered.

Please note, however, that section 6.4 makes explicit, normative 
reference to OAM Framework, and that the removal of a section 
on OAM would give the impression  that the various functions 
can be performed through the management plane and the control 
plane, but not using  OAM. Such an impression would not be 
desirable.
Attachment(s):
No document has been attached



From lucyyong@huawei.com  Fri Jul 16 12:06:05 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E33CC3A69F8; Fri, 16 Jul 2010 12:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.734
X-Spam-Level: 
X-Spam-Status: No, score=-0.734 tagged_above=-999 required=5 tests=[AWL=-0.840, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, 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 c3cZii84r4XU; Fri, 16 Jul 2010 12:05:54 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id E49D93A6A61; Fri, 16 Jul 2010 12:05:50 -0700 (PDT)
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 <0L5N00B5WZPQWO@szxga03-in.huawei.com>; Sat, 17 Jul 2010 03:05:50 +0800 (CST)
Received: from 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 <0L5N00ALXZPPDA@szxga03-in.huawei.com>; Sat, 17 Jul 2010 03:05:50 +0800 (CST)
Received: from y736742 ([10.124.12.56]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5N00AIDZPNEE@szxml04-in.huawei.com>; Sat, 17 Jul 2010 03:05:49 +0800 (CST)
Date: Fri, 16 Jul 2010 14:05:46 -0500
From: Yong Lucy <lucyyong@huawei.com>
To: 'pwe3' <pwe3@ietf.org>, mpls@ietf.org
Message-id: <00d801cb2519$e6f16160$380c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/mixed; boundary="Boundary_(ID_teT5g/aMUM8qx/HeRzx9iA)"
Thread-index: AcrmWi5eElLekKb4TiG87Xlhyj4GaQ+vm/zA
Subject: [mpls] FW:  Large FLow Classificaiton in Flow Aware Transport
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2010 19:06:05 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_teT5g/aMUM8qx/HeRzx9iA)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_xZce9xxe4ArPMS5Wao+rzA)"


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

I like to post this e-mail again for reminding. We have changed the draft
title to draft-yong-pwe-lfc-fat-pw to focus on large flow classification,
not enhanced ECMP.

 

Look forward to discussing this at Maastricht.

 

Lucy

 

  _____  

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Yong
Lucy
Sent: Tuesday, April 27, 2010 5:37 PM
To: 'pwe3'; mpls@ietf.org
Subject: [mpls] Large FLow Classificaiton in Flow Aware Transport

 

Hi,
 
I recap the comments raised during IETF77 meeting. Some are from the PWE3
meeting and some from offline discussions. Hope this gives some
clarification and bring up further mailing discussion.
 
The draft proposal (draft-yong-pwe3-enhanced-ecmp-lfat-01) is to use one of
the TC bits in the flow label to indicate large flow. TC bits in flow label
described in FAT-PW are not used and are not interpreted by LSR. 
 
Comments and Responses:
          
1) No use for the proposal. would need to update all equipment to get this
to work.  A while ago we agreed to not standardize ECMP process. 
 
Lucy: Some carriers see the value of it. There is no need to update all
equipment to get this work. The backward compatibility is supported as
described in section 6. Partially upgrading can improve some segments while
keeping other segments remain the same. The intention of the draft is not
for standardizing ECMP process. It is about standardizing large flow
classification indication in PSN. The draft layout may lead this confusion.
We will modify the draft and move enhanced ECMP process description to
appendix as one implementation example to use large flow classification. We
will change the draft title to "large flow classification in flow aware
transport over PSN" and upload soon.
 
2) would need to go through MPLS WG for issue on standardizing ECMP. Label
stack is always MPLS label stack so MPLS WG would need to OK change of TC
semantics.  Needs a co-review in MPLS WG and they must approve.
 
Lucy: The draft is not for standardizing ECMP. (sorry for the confusion).
The draft does not change the semantics of a label stack entry defined by
RFC3032 because the flow label is never on the top of label stack. As FAT-PW
draft indicates that the interpretation of TC bits in the flow label by LSR
is undefined. This draft proposes one definition.
 
3) If you can get MPLS WG to agree, one of the issues is that you are
marking at a PE where the PE may or may not know what is or isn't a big
flow.  Limitations on PEs ability to determine what a big flow is. Would
need to tell easily and ubiquitously what a big flow is.
 
Lucy: In our proposal, large flows in this context are the top rate ranked
flows. It is relevant to other flows not the link capacity. Enhanced ECMP
process just needs a small set of large flows for load balancing, therefore,
it can pick by statistics, i.e. not necessary all the large flows. The
method works well even some large flows placed by hashing function. The
backward compatibility in the draft would deal with this.
          
4) we haven't standardized anything on ECMP. Many will look at bottom of
stack to look at IP address or anything else to hash on. If I'm a PE router
with lots of L3VPN traffic and some PWs, how do I know if this is a flow
label or VPN label.
 
Lucy: This is not for ECMP standardization. We propose one method to
differentiate the flow label from IP packet, PW label, and LSP label at the
bottom of label stack. This is: check the first nibble to separate IP and
MPLS packets; for MPLS packets, use TTL value (=0) to check the flow label
packets.  
 
5) this is addressing an important issue.  Simulations showed a lot of
traffic and the flows are large enough.  Cases in well engineered network
where situation is much worse than shown.  Drafts have been submitting in
past that gained no traction.  To use a method other than just hashing, but
may be ways to do this without changing label or MPLS.
 
Lucy: The simulation use Internet traffic pattern. For carrier network, it
has a lot of L2VPN traffic carried as single flow, so the situation is
worse. We work on additional simulation to include such type of traffic. It
confirms the statement. As Internet traffic grow with higher and higher bit
rate flows, the problem will become more and more severe. We need to aim on
this real problem.
 
6) there was a proposal to solve this 10 years ago with no protocol changes.
This is not needed.
 
Lucy: Need clarification which proposal refers to. If it is OMP, the draft
proposes the different method from OMP. OMP suggest using routing protocol
to advertise individual ECMP path TE information in the network. The draft
is about large flow classification indication so LSR can use a set of large
flows in performing load balance over ECMP paths effectively.
 
7) Changes too much about MPLS processing
 
Lucy: It is not that additional process. Gaining is obvious too. 
 
8) did the simulations deal with coming and going of flows? How to address
flow fluctuation?
 
Lucy: we are working on additional simulations. That will include flow
coming and going situation and include much higher bit rate flows, and a
"permanent flow" whose rate may change over time to make it as small flow at
a time or a large flow at another time. The latter case likes a VPWS as a
flow. Be glad to show some simulation result to the group.
 
9) Signaling can be used for this, why using marking?
 
Lucy: today, signaling a PW is used per a service basis such as VPWS or
VPLS. But one VPWS or VPLS may contain many flows, the draft address this
situation. It is hard for carrier to signal individual large flow within
VPLS over PSN networks.  
 
10) If there is incentive to enhanced ECMP, why not do large flow
recognition at local LSR for the purpose? PE based large flow recognition
and marking do not apply well at individual LSR.
 
Lucy: High bit rate flow is relevant to other flows. Operator can set large
flow criteria. Having each LSR performs larger flow recognition add complex
to each LSR and may impact the service performance. Large flow
classification is easier, we think. Today, DiffServ enables the network to
perform different service treatments. Large flow classification enables
network to perform different flow treatments over ECMP operation.
 
Comments and suggestion are welcome.
 
 
Regards,
Lucy
 
 
          
 

 

 


--Boundary_(ID_xZce9xxe4ArPMS5Wao+rzA)
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:st1="urn:schemas-microsoft-com:office:smarttags" 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 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'>I like to post this e-mail again for
reminding. We have changed the draft title to draft-yong-pwe-lfc-fat-pw to
focus on large flow classification, not enhanced ECMP.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'>Look forward to discussing this at <st1:City
w:st="on"><st1:place w:st="on">Maastricht</st1:place></st1:City>.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'>Lucy<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>

<hr size=2 width="100%" align=center tabindex=-1>

</span></font></div>

<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <b><span style='font-weight:
bold'>On Behalf Of </span></b>Yong Lucy<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, April 27, 2010 5:37
PM<br>
<b><span style='font-weight:bold'>To:</span></b> 'pwe3'; mpls@ietf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [mpls] Large FLow
Classificaiton in Flow Aware Transport</span></font><o:p></o:p></p>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<pre><font size=2 face="Courier New"><span style='font-size:10.0pt'>Hi,<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>I recap the comments raised during IETF77 meeting. Some are from the PWE3 meeting and some from offline discussions. Hope this gives some clarification and bring up further mailing discussion.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>The draft proposal (draft-yong-pwe3-enhanced-ecmp-lfat-01) is to use one of the TC bits in the flow label to indicate large flow. TC bits in flow label described in FAT-PW are not used and are not interpreted by LSR. <o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Comments and Responses:<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>1) No use for the proposal. would need to update all equipment to get this to work.&nbsp; A while ago we agreed to not standardize ECMP process. <o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy: Some carriers see the value of it. There is no need to update all equipment to get this work. The backward compatibility is supported as described in section 6. Partially upgrading can improve some segments while keeping other segments remain the same. The intention of the draft is not for standardizing ECMP process. It is about standardizing large flow classification indication in PSN. The draft layout may lead this confusion. We will modify the draft and move enhanced ECMP process description to appendix as one implementation example to use large flow classification. We will change the draft title to &#8220;large flow classification in flow aware transport over PSN&#8221; and upload soon.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>2) would need to go through MPLS WG for issue on standardizing ECMP. Label stack is always MPLS label stack so MPLS WG would need to OK change of TC semantics.&nbsp; Needs a co-review in MPLS WG and they must approve.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy: The draft is not for standardizing ECMP. (sorry for the confusion). The draft does not change the semantics of a label stack entry defined by RFC3032 because the flow label is never on the top of label stack. As FAT-PW draft indicates that the interpretation of TC bits in the flow label by LSR is undefined. This draft proposes one definition.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>3) If you can get MPLS WG to agree, one of the issues is that you are marking at a PE where the PE may or may not know what is or isn't a big flow.&nbsp; Limitations on PEs ability to determine what a big flow is. Would need to tell easily and ubiquitously what a big flow is.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy: In our proposal, large flows in this context are the top rate ranked flows. It is relevant to other flows not the link capacity. Enhanced ECMP process just needs a small set of large flows for load balancing, therefore, it can pick by statistics, i.e. not necessary all the large flows. The method works well even some large flows placed by hashing function. The backward compatibility in the draft would deal with this.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>4) we haven't standardized anything on ECMP. Many will look at bottom of stack to look at IP address or anything else to hash on. If I'm a PE router with lots of L3VPN traffic and some PWs, how do I know if this is a flow label or VPN label.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy: This is not for ECMP standardization. We propose one method to differentiate the flow label from IP packet, PW label, and LSP label at the bottom of label stack. This is: check the first nibble to separate IP and MPLS packets; for MPLS packets, use TTL value (=0) to check the flow label packets. &nbsp;<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>5) this is addressing an important issue.&nbsp; Simulations showed a lot of traffic and the flows are large enough.&nbsp; Cases in well engineered network where situation is much worse than shown.&nbsp; Drafts have been submitting in past that gained no traction.&nbsp; To use a method other than just hashing, but may be ways to do this without changing label or MPLS.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy: The simulation use Internet traffic pattern. For carrier network, it has a lot of L2VPN traffic carried as single flow, so the situation is worse. We work on additional simulation to include such type of traffic. It confirms the statement. As Internet traffic grow with higher and higher bit rate flows, the problem will become more and more severe. We need to aim on this real problem.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>6) there was a proposal to solve this 10 years ago with no protocol changes.&nbsp; This is not needed.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy: Need clarification which proposal refers to. If it is OMP, the draft proposes the different method from OMP. OMP suggest using routing protocol to advertise individual ECMP path TE information in the network. The draft is about large flow classification indication so LSR can use a set of large flows in performing load balance over ECMP paths effectively.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>7) Changes too much about MPLS processing<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy: It is not that additional process. Gaining is obvious too. <o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>8) did the simulations deal with coming and going of flows? How to address flow fluctuation?<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy: we are working on additional simulations. That will include flow coming and going situation and include much higher bit rate flows, and a &#8220;permanent flow&#8221; whose rate may change over time to make it as small flow at a time or a large flow at another time. The latter case likes a VPWS as a flow. Be glad to show some simulation result to the group.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>9) Signaling can be used for this, why using marking?<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy: today, signaling a PW is used per a service basis such as VPWS or VPLS. But one VPWS or VPLS may contain many flows, the draft address this situation. It is hard for carrier to signal individual large flow within VPLS over PSN networks. &nbsp;<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>10) If there is incentive to enhanced ECMP, why not do large flow recognition at local LSR for the purpose? PE based large flow recognition and marking do not apply well at individual LSR.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy: High bit rate flow is relevant to other flows. Operator can set large flow criteria. Having each LSR performs larger flow recognition add complex to each LSR and may impact the service performance. Large flow classification is easier, we think. Today, DiffServ enables the network to perform different service treatments. Large flow classification enables network to perform different flow treatments over ECMP operation.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Comments and suggestion are welcome.<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Regards,<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>Lucy<o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></pre><pre><font
size=2 face="Courier New"><span style='font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_xZce9xxe4ArPMS5Wao+rzA)--

--Boundary_(ID_teT5g/aMUM8qx/HeRzx9iA)
Content-type: text/plain; name=ATT00183.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=ATT00183.txt

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

--Boundary_(ID_teT5g/aMUM8qx/HeRzx9iA)--

From davari@broadcom.com  Fri Jul 16 16:48:56 2010
Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78FAD3A65A5; Fri, 16 Jul 2010 16:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.21
X-Spam-Level: 
X-Spam-Status: No, score=-2.21 tagged_above=-999 required=5 tests=[AWL=-0.211,  BAYES_00=-2.599, J_CHICKENPOX_42=0.6]
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 jfoGLh6EMBmi; Fri, 16 Jul 2010 16:48:51 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id EDDD63A6407; Fri, 16 Jul 2010 16:48:50 -0700 (PDT)
Received: from [10.16.192.232] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Fri, 16 Jul 2010 16:48:52 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Fri, 16 Jul 2010 16:48:52 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "curtis@occnc.com" <curtis@occnc.com>
Date: Fri, 16 Jul 2010 16:48:51 -0700
Thread-Topic: [PWE3] 1588 over MPLS draft
Thread-Index: AcsjdqeBK5kQ5GQWSx+iGBw4iS9MLABypdZQ
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6940EC2928C@SJEXCHCCR02.corp.ad.broadcom.com>
References: Your message of "Wed, 07 Jul 2010 12:12:04 PDT." <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <201007141704.o6EH4T2I045662@harbor.orleans.occnc.com>
In-Reply-To: <201007141704.o6EH4T2I045662@harbor.orleans.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 605E306E3KC41789859-01-01
Content-Type: multipart/mixed; boundary=_002_2C2F1EBA8050E74EA81502D5740B4BD6940EC2928CSJEXCHCCR02co_
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2010 23:48:57 -0000

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

Hi,

Please find the txt format of 1588 over mpls draft. There has been some dis=
cussion over the mailing list. I will update it based on the consensus.

Thanks,
Shahram

-----Original Message-----
From: curtis@occnc.com [mailto:curtis@occnc.com]=20
Sent: Wednesday, July 14, 2010 10:04 AM
To: Shahram Davari
Cc: ticctoc@ietf.org; mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
Subject: Re: [PWE3] 1588 over MPLS draft


In message <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.=
broadcom.com>
"Shahram Davari" writes:
> =20
> =20
> Hi All,
> =20
> Please find attached our first draft of 1588 over MPLS. Since we have som=
e =3D
> technical issues converting the Word format to Txt we couldn't  upload th=
e =3D
> draft before the cut-off date. However we will present the draft in the n=
ex=3D
> t IETF meeting and will upload the draft after the meeting.
> =20
> Note that the main WG is TicToc but may require consultation with MPLS an=
d =3D
> PWE3 WGs.
> =20
> Thanks,
> Shahram Davari


IMO Attaching a word doc and asking for a slot at the meeting is
unacceptable.  At least convert the document to text or don't bother
and submit the draft after the meeting.  In any case, the cutoffs are
there for a reason and this should be given low priority at the
meeting (presented if there is time left over).

Curtis


--_002_2C2F1EBA8050E74EA81502D5740B4BD6940EC2928CSJEXCHCCR02co_
Content-Type: text/plain;
 name=draft-davari-tictoc-1588-over-mpls-00.txt
Content-Description: draft-davari-tictoc-1588-over-mpls-00.txt
Content-Disposition: attachment;
 filename=draft-davari-tictoc-1588-over-mpls-00.txt;
 size=24112;
 creation-date="Wed, 14 Jul 2010 17:47:15 GMT";
 modification-date="Wed, 14 Jul 2010 17:47:15 GMT"
Content-Transfer-Encoding: base64

VElUT0MgV29ya2luZyBHcm91cCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBTLiBEYXZhcmkNCkludGVybmV0IERyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgQS4gT3Jlbg0KSW50ZW5kZWQgc3RhdHVzOiBTdGFuZGFyZHMg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBCcm9hZGNvbQ0KRXhwaXJlczogSmFu
IDEsIDIwMTEgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBMLiBNYXJ0
aW5pDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgQ2lzY28NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIEp1bHkgMSwgMjAxMA0KDQoNCg0KICAgICAgICAgICAgVHJhbnNw
b3J0aW5nIFBUUCBtZXNzYWdlcyAoMTU4OCkgb3ZlciBNUExTIE5ldHdvcmtzDQogICAgICAgICAg
ICAgICAgICBkcmFmdC1kYXZhcmktdGljdG9jLTE1ODhvdmVybXBscy0wMC50eHQNCg0KDQpTdGF0
dXMgb2YgdGhpcyBNZW1vDQoNCiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgaXMgc3VibWl0dGVkIGlu
IGZ1bGwgY29uZm9ybWFuY2Ugd2l0aCB0aGUNCiAgIHByb3Zpc2lvbnMgb2YgQkNQIDc4IGFuZCBC
Q1AgNzkuDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhl
IEludGVybmV0IEVuZ2luZWVyaW5nDQogICBUYXNrIEZvcmNlIChJRVRGKSwgaXRzIGFyZWFzLCBh
bmQgaXRzIHdvcmtpbmcgZ3JvdXBzLiAgTm90ZSB0aGF0DQogICBvdGhlciBncm91cHMgbWF5IGFs
c28gZGlzdHJpYnV0ZSB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuDQoNCiAg
IEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0g
b2Ygc2l4IG1vbnRocw0KICAgYW5kIG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xl
dGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnkNCiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJp
YXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlDQogICBtYXRlcmlhbCBvciB0
byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iDQoNCiAgIFRoZSBs
aXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtRHJhZnRzIGNhbiBiZSBhY2Nlc3NlZCBhdA0KICAgaHR0
cDovL3d3dy5pZXRmLm9yZy9pZXRmLzFpZC1hYnN0cmFjdHMudHh0DQoNCiAgIFRoZSBsaXN0IG9m
IEludGVybmV0LURyYWZ0IFNoYWRvdyBEaXJlY3RvcmllcyBjYW4gYmUgYWNjZXNzZWQgYXQNCiAg
IGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwNCg0KICAgVGhpcyBJbnRlcm5ldC1EcmFm
dCB3aWxsIGV4cGlyZSBvbiBKYW51YXJ5IDE1LCAyMDA5Lg0KDQpDb3B5cmlnaHQgTm90aWNlDQoN
CiAgIENvcHlyaWdodCAoYykgMjAxMCBJRVRGIFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVudGlm
aWVkIGFzIHRoZQ0KICAgZG9jdW1lbnQgYXV0aG9ycy4gQWxsIHJpZ2h0cyByZXNlcnZlZC4NCg0K
ICAgVGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIEJDUCA3OCBhbmQgdGhlIElFVEYgVHJ1c3Qn
cyBMZWdhbA0KICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50cw0KICAgKGh0
dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vuc2UtaW5mbykgaW4gZWZmZWN0IG9uIHRoZSBkYXRl
IG9mDQogICBwdWJsaWNhdGlvbiBvZiB0aGlzIGRvY3VtZW50LiBQbGVhc2UgcmV2aWV3IHRoZXNl
IGRvY3VtZW50cyBjYXJlZnVsbHksDQogICBhcyB0aGV5IGRlc2NyaWJlIHlvdXIgcmlnaHRzIGFu
ZCByZXN0cmljdGlvbnMgd2l0aCByZXNwZWN0IHRvIHRoaXMNCiAgIGRvY3VtZW50Lg0KDQoNCg0K
DQpEYXZhcmkgZXQgYWwuICAgICAgICAgIEV4cGlyZXMgSmFudWFyeSA3LCAyMDExICAgICAgICAg
ICAgICAgIFtQYWdlIDFdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAxNTg4IG92ZXIg
TVBMUyAgICAgICAgICAgICAgICAgICAgSnVseSAyMDEwDQoNCg0KQWJzdHJhY3QNCg0KICAgVGhp
cyBkb2N1bWVudCBkZWZpbmVzIHRoZSBtZXRob2QgZm9yIHRyYW5zcG9ydGluZyBQVFAgbWVzc2Fn
ZXMgKFBEVXMpDQogICBvdmVyIGFuIE1QTFMgbmV0d29yayB0byBlbmFibGUgdG8gZW5hYmxlIGEg
cHJvcGVyIGhhbmRsaW5nIG9mIHRoZXNlDQogICBwYWNrZXRzIChlLmcuIGltcGxlbWVudGF0aW9u
IG9mIFRyYW5zcGFyZW50IENsb2NrcyAoVEMpKSBpbiBMU1JzLg0KDQogICBUaGUgYmFzaWMgaWRl
YSBpcyB0byB0cmFuc3BvcnQgUFRQIG1lc3NhZ2VzIGluc2lkZSBkZWRpY2F0ZWQgTVBMUw0KICAg
TFNQcy4gVGhlc2UgTFNQcyBvbmx5IGNhcnJ5IFBUUCBtZXNzYWdlcyBhbmQgcG9zc2libHkgQ29u
dHJvbCBhbmQNCiAgIE1hbmFnZW1lbnQgcGFja2V0cywgYW5kIGRvIG5vdCBjYXJyeSBjdXN0b21l
ciB0cmFmZmljLg0KDQogICBUd28gbWV0aG9kcyBmb3IgdHJhbnNwb3J0aW5nIDE1ODggb3ZlciBN
UExTIGFyZSBkZWZpbmVkLiBUaGUgZmlyc3QNCiAgIG1ldGhvZCBpcyB0byB0cmFuc3BvcnQgUFRQ
IG1lc3NhZ2VzIGRpcmVjdGx5IG92ZXIgdGhlIGRlZGljYXRlZCBNUExTDQogICBMU1AgdmlhIFVE
UC9JUCBlbmNhcHN1bGF0aW9uLCB3aGljaCBpcyBzdWl0YWJsZSBmb3IgSVAvTVBMUyBuZXR3b3Jr
cy4NCiAgIFRoZSBzZWNvbmQgbWV0aG9kIGlzIHRvIHRyYW5zcG9ydCBQVFAgbWVzc2FnZXMgaW5z
aWRlIGEgUFcgdmlhDQogICBFdGhlcm5ldCBlbmNhcHN1bGF0aW9uLCB3aGljaCBpcyBtb3JlIHN1
aXRhYmxlIGZvciBNUExTLVRQIG5ldHdvcmtzLg0KDQpUYWJsZSBvZiBDb250ZW50cw0KDQoNCiAg
IDEuIEludHJvZHVjdGlvbi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLjINCiAgIDIuIENvbnZlbnRpb25zIHVzZWQgaW4gdGhpcyBkb2N1bWVudC4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi40DQogICAzLiBUZXJtaW5vbG9neS4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi40DQogICA0LiBQcm9ibGVtIFN0YXRlbWVu
dC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi41DQogICA1LiBEZWRp
Y2F0ZWQgTFNQcyBmb3IgUFRQIG1lc3NhZ2VzLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
NQ0KICAgNi4gMTU4OCBvdmVyIE1QTFMgRW5jYXBzdWxhdGlvbi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLjYNCiAgICAgIDYuMS4gMTU4OCBvdmVyIExTUCBFbmNhcHN1bGF0aW9uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi42DQogICAgICA2LjIuIDE1ODggb3ZlciBQVyBFbmNh
cHN1bGF0aW9uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uNw0KICAgNy4gMTU4OCBNZXNz
YWdlIFRyYW5zcG9ydC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjgNCiAg
IDguIFByb3RlY3Rpb24gYW5kIFJlZHVuZGFuY3kuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi45DQogICA5LiBFQ01QIGFuZCBMQUcuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi45DQogICAxMC4gT0FNLCBDb250cm9sIGFuZCBNYW5hZ2VtZW50
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4xMA0KICAgMTEuIEZDUyBSZWNhbGN1bGF0
aW9uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4xMA0KICAgMTIuIFJT
VlAtVEUvR01QTFMgRXh0ZW5zaW9ucyBmb3Igc3VwcG9ydCBvZiAxNTg4Li4uLi4uLi4uLi4uLi4u
MTANCiAgIDEzLiBTZWN1cml0eSBDb25zaWRlcmF0aW9ucy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLjEwDQogICAxNC4gSUFOQSBDb25zaWRlcmF0aW9ucy4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4xMA0KICAgMTUuIFJlZmVyZW5jZXMuLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4xMQ0KICAgICAgMTUuMS4gTm9y
bWF0aXZlIFJlZmVyZW5jZXMuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uMTENCiAg
ICAgIDE1LjIuIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLjExDQogICAxNi4gQWNrbm93bGVkZ21lbnRzLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLjEyDQoNCjEuIEludHJvZHVjdGlvbg0KDQogICBUaGUgb2JqZWN0
aXZlIG9mIFByZWNpc2lvbiBUaW1lIFByb3RvY29sIChQVFApIGlzIHRvIHN5bmNocm9uaXplDQog
ICBpbmRlcGVuZGVudCBjbG9ja3MgcnVubmluZyBvbiBzZXBhcmF0ZSBub2RlcyBvZiBhIGRpc3Ry
aWJ1dGVkIHN5c3RlbS4NCiAgIFtJRUVFMTU4OF0gZGVmaW5lcyBQVFAgbWVzc2FnZXMgZm9yIGNs
b2NrIGFuZCB0aW1lIHN5bmNocm9uaXphdGlvbi4NCiAgIFRoZSBQVFAgbWVzc2FnZXMgaW5jbHVk
ZSBQVFAgUERVcyBvdmVyIFVEUC9JUCAoQW5uZXggRCAmIEUgb2YNCiAgIFtJRUVFMTU4OF0pIGFu
ZCBQVFAgUERVcyBvdmVyIEV0aGVybmV0IChBbm5leCBGIG9mIFtJRUVFMTU4OF0pLiAgVGhpcw0K
DQoNCkRhdmFyaSBldCBhbC4gICAgICAgICBFeHBpcmVzIEphbnVhcnkgMTUsIDIwMTEgICAgICAg
ICAgICAgICAgW1BhZ2UgMl0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgIDE1ODggb3Zl
ciBNUExTICAgICAgICAgICAgICAgICAgICBKdWx5IDIwMTANCg0KDQogICBkb2N1bWVudCBkZWZp
bmVzIG1hcHBpbmcgYW5kIHRyYW5zcG9ydCBvZiB0aGUgUFRQIG1lc3NhZ2VzIGRlZmluZWQgaW4N
CiAgIFtJRUVFMTU4OF0gb3ZlciBNUExTIG5ldHdvcmtzLg0KDQogICBQVFAgZGVmaW5lcyBpbnRl
cm1lZGlhdGUgY2xvY2sgZnVuY3Rpb25zIChjYWxsZWQgdHJhbnNwYXJlbnQgY2xvY2tzKQ0KICAg
YmV0d2VlbiB0aGUgc291cmNlIG9mIHRpbWUgKE1hc3RlcikgYW5kIHRoZSBTbGF2ZSBjbG9ja3Mu
IEJvdW5kYXJ5DQogICBDbG9ja3MgKEJDKSBmb3JtIE1hc3Rlci1TbGF2ZSBoaWVyYXJjaHkgd2l0
aCB0aGUgTWFzdGVyIGNsb2NrIGFzIHJvb3QuDQogICBUaGUgbWVzc2FnZXMgcmVsYXRlZCB0byBz
eW5jaHJvbml6YXRpb24sIGVzdGFibGlzaGluZyB0aGUgTWFzdGVyLQ0KICAgU2xhdmUgaGllcmFy
Y2h5LCBhbmQgc2lnbmFsaW5nLCB0ZXJtaW5hdGUgaW4gdGhlIHByb3RvY29sIGVuZ2luZSBvZiBh
DQogICBib3VuZGFyeSBjbG9jayBhbmQgYXJlIG5vdCBmb3J3YXJkZWQuICBNYW5hZ2VtZW50IG1l
c3NhZ2VzIGhvd2V2ZXIsDQogICBhcmUgZm9yd2FyZGVkIHRvIG90aGVyIHBvcnRzIG9uIHRoZSBi
b3VuZGFyeSBjbG9jay4NCg0KICAgVHJhbnNwYXJlbnQgY2xvY2tzIG1vZGlmeSBhICJjb3JyZWN0
aW9uIGZpZWxkIiAoQ0YpIHdpdGhpbiB0aGUNCiAgIHN5bmNocm9uaXphdGlvbiBtZXNzYWdlcyB0
byBjb21wZW5zYXRlIGZvciByZXNpZGVuY2UgYW5kIHByb3BhZ2F0aW9uDQogICBkZWxheXMuICBU
cmFuc3BhcmVudCBjbG9ja3MgZG8gbm90IHRlcm1pbmF0ZSBzeW5jaHJvbml6YXRpb24sIE1hc3Rl
ci0NCiAgIFNsYXZlIGhpZXJhcmNoeSBjb250cm9sIG1lc3NhZ2VzIG9yIHNpZ25hbGluZyBtZXNz
YWdlcy4NCg0KICAgVGhlcmUgaXMgYSBuZWVkIHRvIHRyYW5zcG9ydCBQVFAgbWVzc2FnZXMgb3Zl
ciBNUExTIG5ldHdvcmtzLiBUaGUNCiAgIE1QTFMgbmV0d29yayBjb3VsZCBiZSBhIHRyYW5zaXQg
bmV0d29yayBiZXR3ZWVuIDE1ODggTWFzdGVycyBhbmQNCiAgIFNsYXZlcy4gVGhlIGFjY3VyYWN5
IG9mIHRoZSByZWNvdmVyZWQgY2xvY2sgaW1wcm92ZXMgYW5kIHRoZSBTbGF2ZQ0KICAgbG9naWMg
c2ltcGxpZmllcyB3aGVuIGludGVybWVkaWF0ZSBub2RlcyAoZS5nLiBMU1JzKSBwcm9wZXJseSBo
YW5kbGUNCiAgIFBUUCBtZXNzYWdlcyAoZS5nLiBwZXJmb3JtIFRDKS4NCg0KICAgVGhpcyBkb2N1
bWVudCByZXF1aXJlcyB0aGF0IE1QTFMgbm9kZXMgKExTUnMpIFNIT1VMRCBiZSBhYmxlIHRvDQog
ICBzdXBwb3J0IHRoZSBUcmFuc3BhcmVudCBDbG9jayAoVEMpIGZ1bmN0aW9uLCBtZWFuaW5nIHRo
YXQgdGhleSBzaG91bGQNCiAgIGJlIGFibGUgdG8gbW9kaWZ5IHRoZSBDRiBvZiB0aGUgcHJvcGVy
IFBUUCBtZXNzYWdlcywgdmlhIGEgMS1zdGVwIG9yDQogICAyLXN0ZXAgcHJvY2Vzcy4NCg0KICAg
VEMgcmVxdWlyZXMgYW4gTFNSIGluIHRoZSBtaWRkbGUgb2YgYW4gTFNQIHRvIGlkZW50aWZ5IHRo
ZSBQVFANCiAgIG1lc3NhZ2VzIGFuZCBwZXJmb3JtIHByb3BlciB1cGRhdGUgb2YgdGhlIENGLg0K
DQogICBNb3JlIGdlbmVyYWxseSB0aGlzIGRvY3VtZW50IHJlcXVpcmVzIHRoYXQgTVBMUyBub2Rl
cyBTSE9VTEQgYmUgYWJsZQ0KICAgdG8gcHJvcGVybHkgaGFuZGxlIHRoZSBQVFAgbWVzc2FnZXMu
IEZvciBpbnN0YW5jZSBmb3IgdGhvc2UgY2FzZXMNCiAgIHdoZW4gdGhlIFRDIGZ1bmN0aW9uIGlz
IG5vdCB2aWFibGUgKGUuZy4gZHVlIHRvIGxheWVyIHZpb2xhdGlvbikgYXMNCiAgIGFuIGFsdGVy
bmF0aXZlIGl0IHNob3VsZCBiZSBwb3NzaWJsZSB0byBpbnN0ZWFkIGNvbnRyb2wgdGhlIGRlbGF5
IGZvcg0KICAgdGhlc2UgbWVzc2FnZXMgb24gYm90aCBkaXJlY3Rpb25zIGFjcm9zcyB0aGUgbm9k
ZS4NCg0KICAgSW4gdGhlIGFib3ZlIGNhc2VzIGl0IGlzIGJlbmVmaWNpYWwgdGhhdCBQVFAgcGFj
a2V0cyBjYW4gYmUgZWFzaWx5DQogICBpZGVudGlmaWVkIHdoZW4gY2FycmllZCBvdmVyIE1QTFMu
DQoNCiAgIFRoaXMgZG9jdW1lbnQgcHJvdmlkZXMgdHdvIG1ldGhvZHMgZm9yIHRyYW5zcG9ydGlu
ZyBQVFAgbWVzc2FnZXMgb3Zlcg0KICAgTVBMUy4gVGhlIG1haW4gb2JqZWN0aXZlcyBhcmUgZm9y
IExTUnMgdG8gYmUgYWJsZSB0bw0KICAgZGV0ZXJtaW5pc3RpY2FsbHkgZGV0ZWN0IGFuZCBpZGVu
dGlmeSB0aGUgUFRQIG1lc3NhZ2VzLg0KDQoNCg0KDQoNCg0KDQpEYXZhcmkgZXQgYWwuICAgICAg
ICAgRXhwaXJlcyBKYW51YXJ5IDE1LCAyMDExICAgICAgICAgICAgICAgIFtQYWdlIDNdDQoMDQpJ
bnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAxNTg4IG92ZXIgTVBMUyAgICAgICAgICAgICAgICAg
ICAgSnVseSAyMDEwDQoNCg0KMi4gQ29udmVudGlvbnMgdXNlZCBpbiB0aGlzIGRvY3VtZW50DQoN
CiAgIFRoZSBrZXkgd29yZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwi
LCAiU0hBTEwgTk9UIiwNCiAgICJTSE9VTEQiLCAiU0hPVUxEIE5PVCIsICJSRUNPTU1FTkRFRCIs
ICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbiB0aGlzDQogICBkb2N1bWVudCBhcmUgdG8gYmUgaW50
ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFJGQy0yMTE5IFtSRkMyMTE5XS4NCg0KDQoNCiAgIDE1
ODg6ICAgVGhlIHRpbWluZyBhbmQgc3luY2hyb25pemF0aW9uIGFzIGRlZmluZWQgYnkgSUVFRSAx
NTg4DQoNCiAgIFBUUDogICBUaGUgdGltaW5nIGFuZCBzeW5jaHJvbml6YXRpb24gcHJvdG9jb2wg
dXNlZCBieSAxNTg4DQoNCiAgIE1hc3RlcjogIFRoZSBTb3VyY2Ugb2YgMTU4OCBUaW1pbmcgYW5k
IGNsb2NrDQoNCiAgIFNsYXZlOiAgICAgICAgICAgICAgICAgICBUaGUgRGVzdGluYXRpb24gb2Yg
MTU4OCBUaW1pbmcgYW5kIGNsb2NrIHRoYXQNCnRyaWVzIHRvDQogICAgICAgICAgICBmb2xsb3cg
dGhlIE1hc3RlciBjbG9jay4NCg0KICAgT0M6ICAgIE9yZGluYXJ5IENsb2NrDQoNCiAgIFRDOiAg
ICAgICAgICAgICAgICAgICAgIFRyYW5zcGFyZW50IENsb2NraW5nLCBhIHRpbWUgc3RhbXBpbmcg
bWV0aG9kDQphcHBsaWVkIGJ5DQogICAgICAgICAgICBpbnRlcm1lZGlhdGUgbm9kZXMgYmV0d2Vl
biBNYXN0ZXIgYW5kIFNsYXZlDQoNCiAgIEJDOiAgICAgICAgICAgICAgICAgICAgIEJvcmRlciBD
bG9jaywgaXMgYSBub2RlIHRoYXQgcmVjb3ZlcnMgdGhlIE1hc3Rlcg0KY2xvY2sgdmlhIGENCiAg
ICAgICAgICAgIFNsYXZlIGZ1bmN0aW9uIGFuZCB1c2VzIHRoYXQgY2xvY2sgYXMgdGhlIE1hc3Rl
ciBmb3Igb3RoZXINCiAgICAgICAgICAgIFNsYXZlcy4NCg0KICAgUFRQIExTUDogQW4gTFNQIGRl
ZGljYXRlZCB0byBjYXJyeSBQVFAgbWVzc2FnZXMNCg0KICAgUFRQIFBXOiBBIFBXIHdpdGhpbiBh
IFBUUCBMU1AgdGhhdCBNQVkgY29ycmVzcG9uZCB0byBhIE1hc3Rlci9TbGF2ZQ0KICAgICAgICAg
ICAgZmxvdy4NCg0KICAgQ1c6ICAgIFBzZXVkbyB3aXJlIENvbnRyb2wgV29yZA0KDQogICBIVzog
ICAgSGFyZHdhcmUNCg0KICAgTEFHOiAgIExpbmsgQWdncmVnYXRpb24NCg0KICAgRUNNUDogICBF
cXVhbCBDb3N0IE11bHRpcGF0aA0KDQogICBDRjogICAgICAgICAgICAgICAgICAgICBDb3JyZWN0
aW9uIEZpZWxkLCBhIGZpZWxkIGluc2lkZSBjZXJ0YWluIFBUUA0KbWVzc2FnZXMNCiAgICAgICAg
ICAgIChtZXNzYWdlIHR5cGUgMC0zKXRoYXQgaG9sZHMgdGhlIGFjY3VtdWxhdGl2ZSB0cmFuc2l0
IHRpbWUNCiAgICAgICAgICAgIGluc2lkZSBpbnRlcm1lZGlhdGUgc3dpdGNoZXMNCg0KDQoNCg0K
DQoNCg0KRGF2YXJpIGV0IGFsLiAgICAgICAgIEV4cGlyZXMgSmFudWFyeSAxNSwgMjAxMSAgICAg
ICAgICAgICAgICBbUGFnZSA0XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgMTU4OCBv
dmVyIE1QTFMgICAgICAgICAgICAgICAgICAgIEp1bHkgMjAxMA0KDQoNCjQuIFByb2JsZW0gU3Rh
dGVtZW50DQoNCiAgIFdoZW4gUFRQIG1lc3NhZ2VzIGFyZSB0cmFuc3BvcnRlZCBvdmVyIE1QTFMg
bmV0d29ya3MsIHRoZXJlIGlzIGEgbmVlZA0KICAgZm9yIGludGVybWVkaWF0ZSBMU1JzIHRvIGRl
dGVjdCBzdWNoIG1lc3NhZ2VzIGFuZCBwZXJmb3JtIHByb3Blcg0KICAgcHJvY2Vzc2luZyAoZS5n
LiBUcmFuc3BhcmVudCBDbG9jayAoVEMpKS4gTm90ZSB0aGUgVEMgcHJvY2Vzc2luZw0KICAgY291
bGQgYmUgaW4gdGhlIGZvcm0gb2YgMS1TdGVwIG9yIDItU3RlcCB0aW1lIHN0YW1waW5nLg0KDQog
ICBQVFAgbWVzc2FnZXMgb3ZlciBFdGhlcm5ldCBvciBJUCBjYW4gYWx3YXlzIGJlIHR1bm5lbGVk
IG92ZXIgTVBMUy4NCiAgIEhvd2V2ZXIgdGhlIDE1ODggb3ZlciBNUExTIG1hcHBpbmcgZGVmaW5l
ZCBpbiB0aGlzIGRvY3VtZW50IGlzDQogICBhcHBsaWNhYmxlIHdoZW5ldmVyIE1QTFMgTFNScyBh
cmUgMTU4OCBhd2FyZSBhbmQgdGhlIGludGVudGlvbiBpcyBmb3INCiAgIHRob3NlIExTUnMgdG8g
cGVyZm9ybSBwcm9wZXIgcHJvY2Vzc2luZyBvbiB0aGVzZSBwYWNrZXRzLg0KDQogICBXaGVuIDE1
ODggYXdhcmVuZXNzIGlzIG5lZWRlZCBQVFAgbWVzc2FnZXMgc2hvdWxkIG5vdCBiZSB0cmFuc3Bv
cnRlZA0KICAgb3ZlciBMU1BzIG9yIFBXcyB0aGF0IGFyZSBjYXJyeWluZyBjdXN0b21lciB0cmFm
ZmljIGJlY2F1c2UgTFNScw0KICAgcGVyZm9ybSBMYWJlbCBzd2l0Y2hpbmcgYmFzZWQgb24gdGhl
IHRvcCBsYWJlbCBpbiB0aGUgc3RhY2suIFRvDQogICBkZXRlY3QgUFRQIG1lc3NhZ2VzIGluc2lk
ZSBzdWNoIExTUHMgcmVxdWlyZSBzcGVjaWFsIEhhcmR3YXJlIChIVykgdG8NCiAgIGRvIGRlZXAg
cGFja2V0IGluc3BlY3Rpb24gYXQgbGluZSByYXRlLiBFdmVuIGlmIG9uZSBhc3N1bWVzIGEgZGVl
cA0KICAgcGFja2V0IGluc3BlY3Rpb24gSFcgYXQgbGluZSByYXRlIGV4aXN0cywgdGhlIHBheWxv
YWQgY2FuJ3QgYmUNCiAgIGRldGVybWluaXN0aWNhbGx5IGlkZW50aWZpZWQgYnkgTFNScyBiZWNh
dXNlIHRoZSBwYXlsb2FkIHR5cGUgaXMgYQ0KICAgY29udGV4dCBvZiB0aGUgUFcgbGFiZWwgYW5k
IHRoZSBQVyBsYWJlbCBhbmQgaXRzIGNvbnRleHQgYXJlIG9ubHkNCiAgIGtub3duIHRvIHRoZSBF
ZGdlIHJvdXRlcnMgKFBFcykgYW5kIExTUnMgZG9uJ3Qga25vdyB3aGF0IGlzIGEgUFcncw0KICAg
cGF5bG9hZCAoRXRoZXJuZXQsIEFUTSwgRlIsIENFUywgZXRjKS4gRXZlbiBpZiBvbmUgYXNzdW1l
cyBvbmx5DQogICBFdGhlcm5ldCBQV3MgYXJlIHBlcm1pdHRlZCBpbiBhbiBMU1AsIHRoZSBMU1Jz
IGRvbid0IGhhdmUgdGhlDQogICBrbm93bGVkZ2Ugb2Ygd2hldGhlciBQVyBDb250cm9sIFdvcmQg
KENXKSBpcyBwcmVzZW50IG9yIG5vdCBhbmQNCiAgIHRoZXJlZm9yZSBjYW4ndCBkZXRlcm1pbmlz
dGljYWxseSBpZGVudGlmeSB0aGUgcGF5bG9hZC4NCg0KICAgVGhlcmVmb3JlIGEgZ2VuZXJpYyBt
ZXRob2QgaXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IHRoYXQgZG9lcyBub3QNCiAgIHJlcXVp
cmUgZGVlcCBwYWNrZXQgaW5zcGVjdGlvbiBhdCBsaW5lIHJhdGUsIGFuZCBjYW4NCiAgIGRldGVy
bWluaXN0aWNhbGx5IGlkZW50aWZ5IFBUUCBtZXNzYWdlcy4gVGhlIGRlZmluZWQgbWV0aG9kIGlz
DQogICBhcHBsaWNhYmxlIHRvIGJvdGggTVBMUyBhbmQgTVBMUy1UUCBuZXR3b3Jrcy4NCg0KNS4g
RGVkaWNhdGVkIExTUHMgZm9yIFBUUCBtZXNzYWdlcw0KDQogICBUaGUgbWV0aG9kIGRlZmluZWQg
aW4gdGhpcyBkb2N1bWVudCBjYW4gYmUgdXNlZCBieSBMU1JzIHRvIGlkZW50aWZ5DQogICBQVFAg
bWVzc2FnZXMgaW4gTVBMUyB0dW5uZWxzIGJ5IHVzaW5nIGRlZGljYXRlZCBMU1BzIHRvIGNhcnJ5
IFBUUA0KICAgbWVzc2FnZXMuDQoNCiAgIENvbXBsaWFudCBpbXBsZW1lbnRhdGlvbnMgTVVTVCB1
c2UgZGVkaWNhdGVkIExTUHMgdG8gY2FycnkgUFRQDQogICBtZXNzYWdlcyBvdmVyIE1QTFMuIExl
dCdzIGNhbGwgdGhlc2UgTFNQcyBhcyB0aGUgIlBUUCBMU1BzIiBhbmQgdGhlDQogICBsYWJlbHMg
YXNzb2NpYXRlZCB3aXRoIHRoZXNlIExTUHMgYXMgIlBUUCBsYWJlbHMiLiBUaGVzZSBMU1BzIGNv
dWxkDQogICBiZSBQMlAgb3IgUDJNUCBMU1BzLiBUaGUgUFRQIExTUCBiZXR3ZWVuIE1hc3RlciBh
bmQgU2xhdmVzIE1BWSBiZQ0KICAgUDJNUCBvciBQMlAgTFNQIHdoaWxlIHRoZSBQVFAgTFNQIGJl
dHdlZW4gZWFjaCBTbGF2ZSBhbmQgTWFzdGVyDQogICBTSE9VTEQgYmUgUDJQIExTUC4gVGhlIFBU
UCBMU1AgYmV0d2VlbiBhIE1hc3RlciBhbmQgYSBTbGF2ZSBhbmQgdGhlDQogICBQVFAgTFNQIGJl
dHdlZW4gdGhlIHNhbWUgU2xhdmUgYW5kIE1hc3RlciBNVVNUIGJlIGNvLXJvdXRlZC4gVGhlIFBU
UA0KICAgTFNQIE1BWSBiZSBNUExTIExTUCBvciBNUExTLVRQIExTUC4NCg0KDQoNCg0KRGF2YXJp
IGV0IGFsLiAgICAgICAgIEV4cGlyZXMgSmFudWFyeSAxNSwgMjAxMSAgICAgICAgICAgICAgICBb
UGFnZSA1XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgMTU4OCBvdmVyIE1QTFMgICAg
ICAgICAgICAgICAgICAgIEp1bHkgMjAxMA0KDQoNCiAgIFRoZSBQVFAgTFNQcyBjb3VsZCBiZSBj
b25maWd1cmVkIG9yIHNpZ25hbGVkIHZpYSBSU1ZQLVRFL0dNUExTLiBOZXcNCiAgIFJTVlAtVEUv
R01QTFMgVExWcyBhcmUgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IHRvIGluZGljYXRlIHRoYXQN
CiAgIHRoZXNlIExTUHMgYXJlIFBUUCBMU1BzLg0KDQogICBJbiBvcmRlciB0byBzaW1wbGlmeSBI
VyBpbXBsZW1lbnRhdGlvbnMsIHRoZSAiUFRQIGxhYmVscyIgU0hPVUxEIGJlDQogICBzZWxlY3Rl
ZCBmcm9tIGEgbGFiZWwgcmFuZ2UgY2FsbGVkICJQVFAgTGFiZWwgUmFuZ2UiLiBUaGUgIlBUUCBM
YWJlbCINCiAgIFJhbmdlIE1BWSBiZSBiZSBnbG9iYWwsIG1lYW5pbmcgdGhhdCBhbGwgbm9kZXMg
YW5kIGxpbmtzIGluIGFuIE1QTFMNCiAgIG5ldHdvcmsgc3VwcG9ydCB0aGUgc2FtZSBQVFAgTGFi
ZWwgUmFuZ2U7IG9yIE1BWSBiZSBMb2NhbCwgbWVhbmluZw0KICAgdGhhdCBlYWNoIGxpbmsgZGly
ZWN0aW9uIGluIGFuIE1QTFMgbmV0d29yayBtYXkgaGF2ZSBpdHMgb3duIFBUUA0KICAgTGFiZWwg
UmFuZ2UuDQoNCiAgIFdoZW4gUFRQIExhYmVsIFJhbmdlIGlzIHN1cHBvcnRlZCBhdCBsZWFzdCBv
bmUgUFRQIExhYmVsIFJhbmdlIE1VU1QNCiAgIGJlIHN1cHBvcnRlZC4gT3B0aW9uYWxseSB0d28g
b3IgbW9yZSBQVFAgbGFiZWwgUmFuZ2VzIE1BWSBiZQ0KICAgc3VwcG9ydGVkLg0KDQogICBOb3Rl
IHRoYXQgdGhlIFBUUCBMU1BzIE1VU1Qgb25seSBjYXJyeSBQVFAgbWVzc2FnZXMgYW5kIE1BWSBj
YXJyeQ0KICAgTVBMUy9NUExTLVRQIGNvbnRyb2wgYW5kIG1hbmFnZW1lbnQgbWVzc2FnZXMgc3Vj
aCBhcyBCRkQgYW5kIExTUC1QaW5nLg0KDQo2LiAxNTg4IG92ZXIgTVBMUyBFbmNhcHN1bGF0aW9u
DQoNCiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyB0d28gbWV0aG9kcyBmb3IgY2FycnlpbmcgUFRQ
IG1lc3NhZ2VzIG92ZXIgTVBMUy4NCiAgIFRoZSBmaXJzdCBtZXRob2QgaXMgY2FycnlpbmcgUFRQ
IG1lc3NhZ2VzIG92ZXIgUFRQIExTUHMgYW5kIHRoZQ0KICAgc2Vjb25kIG1ldGhvZCBpcyB0byBj
YXJyeSBQVFAgbWVzc2FnZXMgb3ZlciBkZWRpY2F0ZWQgRXRoZXJuZXQgUFdzDQogICAoY2FsbGVk
IFBUUCBQV3MpIGluc2lkZSBQVFAgTFNQcy4NCg0KNi4xLiAxNTg4IG92ZXIgTFNQIEVuY2Fwc3Vs
YXRpb24NCg0KICAgVGhlIHNpbXBsZXN0IG1ldGhvZCBvZiB0cmFuc3BvcnRpbmcgUFRQIG1lc3Nh
Z2VzIG92ZXIgTVBMUyBpcyB0bw0KICAgZW5jYXBzdWxhdGUgUFRQIFBEVXMgaW4gVURQL0lQIGFu
ZCB0aGVuIGVuY2Fwc3VsYXRlIHRoZW0gaW4gUFRQIExTUC4NCiAgIFRoZSAxNTg4IG92ZXIgTFNQ
IGZvcm1hdCBpcyBzaG93biBpbiBGaWd1cmUgMS4NCg0KICAgICAgICAgICAgICAgICArLS0tLS0t
LS0tLS0tLS0tLSsNCiAgICAgICAgICAgICAgICAgfFBUUCBUdW5uZWwgTGFiZWx8DQogICAgICAg
ICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tKw0KICAgICAgICAgICAgICAgICB8ICAgICBJUFY0
L1Y2ICAgIHwNCiAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0rDQogICAgICAgICAg
ICAgICAgIHwgICAgICAgVURQICAgICAgfA0KICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0t
LS0tLSsNCiAgICAgICAgICAgICAgICAgfCAgICAgUFRQIFBEVSAgICB8DQogICAgICAgICAgICAg
ICAgICstLS0tLS0tLS0tLS0tLS0tKw0KDQoNCiAgICAgICAgICAgICAgICAgIEZpZ3VyZSAxIC0g
MTU4OCBvdmVyIExTUCBFbmNhcHN1bGF0aW9uDQoNCiAgIFRoaXMgZW5jYXBzdWxhdGlvbiBpcyB2
ZXJ5IHNpbXBsZSBhbmQgaXMgdXNlZnVsIHdoZW4gdGhlIG5ldHdvcmtzDQogICBiZXR3ZWVuIDE1
ODggTWFzdGVyIGFuZCBTbGF2ZSBhcmUgSVAvTVBMUyBuZXR3b3Jrcy4NCg0KDQoNCkRhdmFyaSBl
dCBhbC4gICAgICAgICBFeHBpcmVzIEphbnVhcnkgMTUsIDIwMTEgICAgICAgICAgICAgICAgW1Bh
Z2UgNl0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgIDE1ODggb3ZlciBNUExTICAgICAg
ICAgICAgICAgICAgICBKdWx5IDIwMTANCg0KDQogICBJbiBvcmRlciBmb3IgYW4gTFNSIHRvIHBy
b2Nlc3MgUFRQIG1lc3NhZ2VzLCB0aGUgUFRQIExhYmVsIE1VU1QgYmUNCiAgIHRoZSB0b3AgbGFi
ZWwgb2YgdGhlIGxhYmVsIHN0YWNrLg0KDQogICBUaGUgVURQL0lQIGVuY2Fwc3VsYXRpb24gb2Yg
UFRQIE1VU1QgZm9sbG93IEFubmV4IEQgYW5kIEUgb2YNCiAgIFtJRUVFMTU4OF0uDQoNCjYuMi4g
MTU4OCBvdmVyIFBXIEVuY2Fwc3VsYXRpb24NCg0KICAgQW5vdGhlciBtZXRob2Qgb2YgdHJhbnNw
b3J0aW5nIDE1ODggb3ZlciBNUExTIG5ldHdvcmtzIGlzIGJ5DQogICBlbmNhcHN1bGF0aW5nIFBU
UCBQRFVzIGluIEV0aGVybmV0IGFuZCB0aGVuIHRyYW5zcG9ydGluZyB0aGVtIG92ZXINCiAgIEV0
aGVybmV0IFBXIChQVFAgUFcpIGFzIGRlZmluZWQgaW4gW1JGQzQ0NDhdICwgd2hpY2ggaW4gdHVy
biBpcw0KICAgdHJhbnNwb3J0ZWQgb3ZlciBQVFAgTFNQcy4gQWx0ZXJuYXRpdmVseSBQVFAgUERV
cyBNQVkgYmUgZW5jYXBzdWxhdGVkDQogICBpbiBVRFAvSVAvRXRoZXJuZXQgYW5kIHRoZW4gdHJh
bnNwb3J0ZWQgb3ZlciBFdGhlcm5ldCBQVy4NCg0KICAgQm90aCBSYXcgYW5kIFRhZ2dlZCBtb2Rl
cyBmb3IgRXRoZXJuZXQgUFcgYXJlIHBlcm1pdHRlZC4gVGhlIDE1ODgNCiAgIG92ZXIgUFcgZm9y
bWF0IGlzIHNob3duIGluIEZpZ3VyZSAyLg0KDQoNCg0KICAgICAgICAgICAgICAgICArLS0tLS0t
LS0tLS0tLS0tLSsNCiAgICAgICAgICAgICAgICAgfFBUUCBUdW5uZWwgTGFiZWx8DQogICAgICAg
ICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tKw0KICAgICAgICAgICAgICAgICB8ICAgIFBXIExh
YmVsICAgIHwNCiAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0rDQogICAgICAgICAg
ICAgICAgIHwgIEVudHJvcHkgTGFiZWwgfA0KICAgICAgICAgICAgICAgICB8ICAgIChvcHRpb25h
bCkgIHwNCiAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0rDQogICAgICAgICAgICAg
ICAgIHwgIENvbnRyb2wgV29yZCAgfA0KICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0t
LSsNCiAgICAgICAgICAgICAgICAgfCAgICAgRXRoZXJuZXQgICB8DQogICAgICAgICAgICAgICAg
IHwgICAgICBIZWFkZXIgICAgfA0KICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tLSsN
CiAgICAgICAgICAgICAgICAgfCAgICAgICBWTEFOcyAgICB8DQogICAgICAgICAgICAgICAgIHwg
ICAgIChvcHRpb25hbCkgfA0KICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tLSsNCiAg
ICAgICAgICAgICAgICAgfCAgICAgIElQVjQvVjYgICB8DQogICAgICAgICAgICAgICAgIHwgICAg
IChvcHRpb25hbCkgfA0KICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAg
ICAgICAgICAgICAgfCAgICAgICBVRFAgICAgICB8DQogICAgICAgICAgICAgICAgIHwgICAgIChv
cHRpb25hbCkgfA0KICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAgICAg
ICAgICAgICAgfCAgICBQVFAgUERVICAgICB8DQogICAgICAgICAgICAgICAgICstLS0tLS0tLS0t
LS0tLS0tKw0KDQoNCiAgICAgICAgICAgICAgICAgICBGaWd1cmUgMiAtIDE1ODggb3ZlciBQVyBF
bmNhcHN1bGF0aW9uDQoNCg0KDQpEYXZhcmkgZXQgYWwuICAgICAgICAgRXhwaXJlcyBKYW51YXJ5
IDE1LCAyMDExICAgICAgICAgICAgICAgIFtQYWdlIDddDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAg
ICAgICAgICAxNTg4IG92ZXIgTVBMUyAgICAgICAgICAgICAgICAgICAgSnVseSAyMDEwDQoNCg0K
ICAgVGhlIHVzZSBvZiBDb250cm9sIFdvcmQgKENXKSBhcyBzcGVjaWZpZWQgaW4gW1JGQzQ0NDhd
IGlzIG1hbmRhdG9yeQ0KICAgdG8gZW5zdXJlIGRldGVybWluaXN0aWMgZGV0ZWN0aW9uIG9mIFBU
UCBtZXNzYWdlcyBpbnNpZGUgdGhlIE1QTFMNCiAgIHBhY2tldC4gSG93ZXZlciB0aGUgdXNlIG9m
IFNlcXVlbmNlIG51bWJlciBpcyBvcHRpb25hbC4NCg0KICAgVGhlIHVzZSBvZiBWTEFOIGFuZCBV
RFAvSVAgYXJlIG9wdGlvbmFsLiBOb3RlIHRoYXQgMSBvciAyIFZMQU5zIE1BWQ0KICAgZXhpc3Qg
aW4gdGhlIFBXIHBheWxvYWQuDQoNCiAgIEluIG9yZGVyIGZvciBhbiBMU1IgdG8gcHJvY2VzcyBQ
VFAgbWVzc2FnZXMsIHRoZSB0b3AgbGFiZWwgb2YgdGhlDQogICBsYWJlbCBzdGFjayAodGhlIFR1
bm5lbCBMYWJlbCkgTVVTVCBiZSBmcm9tIFBUUCBsYWJlbCByYW5nZS4gSG93ZXZlcg0KICAgaW4g
c29tZSBhcHBsaWNhdGlvbnMgdGhlIFBXIGxhYmVsIG1heSBiZSB0aGUgdG9wIGxhYmVsIGluIHRo
ZSBzdGFjaywNCiAgIHN1Y2ggYXMgY2FzZXMgd2hlcmUgdGhlcmUgaXMgb25seSBvbmUtaG9wIGJl
dHdlZW4gUEVzLiBJbiBzdWNoIGNhc2VzLA0KICAgdGhlIFBXIGxhYmVsIFNIT1VMRCBiZSBjaG9z
ZW4gZnJvbSB0aGUgUFRQIExhYmVsIHJhbmdlLg0KDQogICBBbiBFbnRyb3B5IGxhYmVsIFtGYXQg
UFddIE1BWSBiZSBwcmVzZW50IGF0IHRoZSBib3R0b20gb2Ygc3RhY2suDQoNCiAgIFRoZSBFdGhl
cm5ldCBlbmNhcHN1bGF0aW9uIG9mIFBUUCBNVVNUIGZvbGxvdyBBbm5leCBGIG9mIFtJRUVFMTU4
OF0NCiAgIGFuZCB0aGUgVURQL0lQIGVuY2Fwc3VsYXRpb24gb2YgUFRQIE1VU1QgZm9sbG93IEFu
bmV4IEQgYW5kIEUgb2YNCiAgIFsxRUVFMTU4OF0uDQoNCjcuIDE1ODggTWVzc2FnZSBUcmFuc3Bv
cnQNCg0KICAgMTU4OCBwcm90b2NvbCBjb21wcmlzZXMgb2YgYSBudW1iZXIgb2YgbWVzc2FnZSB0
eXBlcy4gQSBzdWJzZXQgb2YgUFRQDQogICBtZXNzYWdlcyB0aGF0IHJlcXVpcmUgVEMgcHJvY2Vz
c2luZyBhcmU6DQoNCiAgICAgICAgU1lOQw0KDQogICAgICAgIEZPTExPV19VUA0KDQogICAgICAg
IERFTEFZX1JFUSAoRGVsYXkgUmVxdWVzdCkNCg0KICAgICAgICBERUxBWV9SRVMgKERlbGF5IFJl
c3BvbnNlKQ0KDQogICAgICAgIFBERUxBWV9SRVEgKFBlZXIgRGVsYXkgUmVxdWVzdCkNCg0KICAg
ICAgICBQREVMQVlfUkVTUCAoUGVlciBEZWxheSBSZXNwb25zZSkNCg0KICAgICAgICBQREVMQVlf
UkVTUF9GT0xMT1dfVVAgKFBlZXIgRGVsYXkgUmVzcG9uc2UgRm9sbG93IHVwKQ0KDQogICBTWU5D
LCBGT0xMT1dfVVAsIERFTEFZX1JFUSBhbmQgREVMQVlfUkVTUCBhcmUgZXhjaGFuZ2VkIGJldHdl
ZW4NCiAgIE1hc3RlciBhbmQgU2xhdmUgYW5kIE1VU1QgYmUgdHJhbnNwb3J0ZWQgb3ZlciBQVFAg
TFNQcy4NCg0KICAgUERFTEFZX1JFUSwgUERFTEFZX1JFU1AsIGFuZCBQREVMQVlfUkVTUF9GT0xM
T1dfVVAgYXJlIGV4Y2hhbmdlZA0KICAgYmV0d2VlbiBhZGphY2VudCByb3V0ZXJzLiBUaGVzZSBN
ZXNzYWdlcyBpZiB0cmFuc3BvcnRlZCBvdmVyDQogICBNUExTL01QTFMtVFAgTVVTVCBhbHNvIGJl
IHRyYW5zcG9ydGVkIG92ZXIgUFRQIExTUHMuIFRoZXNlIFBUUCBMU1BzDQogICBNQVkgYmUgb25l
LWhvcCBMU1BzIGVzdGFibGlzaGVkIGJldHdlZW4gdHdvIGFkamFjZW50IHJvdXRlcnMgb3IgTUFZ
DQogICBiZSBvbmUgb2YgdGhlIFBUUCBMU1BzIGNhcnJ5aW5nIFNZTkMsIEZPTExPV19VUCwgREVM
QVlfUkVRIG9yDQogICBERUxBWV9SRVNQLg0KDQoNCkRhdmFyaSBldCBhbC4gICAgICAgICBFeHBp
cmVzIEphbnVhcnkgMTUsIDIwMTEgICAgICAgICAgICAgICAgW1BhZ2UgOF0NCgwNCkludGVybmV0
LURyYWZ0ICAgICAgICAgICAgIDE1ODggb3ZlciBNUExTICAgICAgICAgICAgICAgICAgICBKdWx5
IDIwMTANCg0KDQogICBGb3IgYSBnaXZlbiBpbnN0YW5jZSBvZiAxNTg4IHByb3RvY29sIFNZTkMs
IEZPTExPV19VUCwgYW5kIERFTEFZX1JFU1ANCiAgIE1VU1QgYmUgdHJhbnNwb3J0ZWQgb3ZlciB0
aGUgc2FtZSBQVFAgTFNQIGluIHRoZSBkaXJlY3Rpb24gZnJvbQ0KICAgTWFzdGVyIHRvIFNsYXZl
LCB3aGlsZSBERUxBWV9SRVEgTVVTVCBiZSB0cmFuc3BvcnRlZCBvdmVyIGFub3RoZXIgUFRQDQog
ICBMU1AgaW4gdGhlIHJldmVyc2UgZGlyZWN0aW9uIG1lYW5pbmcgaW4gdGhlIGRpcmVjdGlvbiBm
cm9tIFNsYXZlIHRvDQogICBNYXN0ZXIuIFRoZXNlIFBUUCBMU1BzLCB3aGljaCBhcmUgaW4gb3Bw
b3NpdGUgZGlyZWN0aW9ucyBNVVNUIGJlDQogICBjb25ncnVlbnQgYW5kIGNvLXJvdXRlZC4NCg0K
ICAgT3RoZXIgUFRQIG1lc3NhZ2UgdHlwZXMgYXJlIGVuZC10by1lbmQgbWVzc2FnZXMgYmV0d2Vl
biBNYXN0ZXIgYW5kDQogICBTbGF2ZSB0aGF0IGRvbid0IG5lZWQgdG8gYmUgcHJvY2Vzc2VkIGJ5
IGludGVybWVkaWF0ZSByb3V0ZXJzLiBUaGVzZQ0KICAgbWVzc2FnZSB0eXBlcyBNQVkgYmUgY2Fy
cmllZCBpbiBQVFAgVHVubmVsIExTUHMgb3IgYW55IG90aGVyIExTUC4NCiAgIFdoZW4gdGhlc2Ug
UFRQIG1lc3NhZ2VzIGFyZSBjYXJyaWVkIGluIFBUUCBMU1BzIHRoZXJlIGlzIG5vIG5lZWQgdG8N
CiAgIGRpc3Rpbmd1aXNoIGJldHdlZW4gdGhlIFBUUCBtZXNzYWdlIHR5cGVzLCBzaW5jZSB0aGUg
Q0Ygb2YgdGhlc2UNCiAgIG1lc3NhZ2VzIHdpbGwgYmUgaWdub3JlZCBieSBTbGF2ZSBjbG9jay4N
Cg0KOC4gUHJvdGVjdGlvbiBhbmQgUmVkdW5kYW5jeQ0KDQogICBJbiBvcmRlciB0byBlbnN1cmUg
Y29udGludW91cyB1bmludGVycnVwdGVkIG9wZXJhdGlvbiBvZiAxNTg4IFNsYXZlcywNCiAgIHVz
dWFsbHkgUmVkdW5kYW50IE1hc3RlcnMgYXJlIHRyYWNrZWQgYnkgZWFjaCBTbGF2ZS4gSXQgaXMg
dGhlDQogICByZXNwb25zaWJpbGl0eSBvZiB0aGUgbmV0d29yayBvcGVyYXRvciB0byBlbnN1cmUg
dGhhdCBwaHlzaWNhbGx5DQogICBkaXNqb2ludCBQVFAgdHVubmVscyB0aGF0IGRvbid0IHNoYXJl
IGFueSBsaW5rIGFyZSB1c2VkIGJldHdlZW4gdGhlDQogICByZWR1bmRhbnQgTWFzdGVycyBhbmQg
dGhlIFNsYXZlLg0KDQogICBXaGVuIHJlZHVuZGFudCBNYXN0ZXJzIGFyZSB0cmFja2VkIGJ5IGEg
U2xhdmUsIGFueSBQVFAgTFNQIG9yIFBUUCBQVw0KICAgZmFpbHVyZSB3aWxsIHRyaWdnZXIgdGhl
IHNsYXZlIHRvIHN3aXRjaCB0byB0aGUgUmVkdW5kYW50IE1hc3RlciwNCiAgIGV2ZW4gaWYgdGhl
IExTUC9QVyBpcyBwcm90ZWN0ZWQgYXQgdGhlIE1QTFMgbGF5ZXIuIEhvd2V2ZXIgTFNQL1BXDQog
ICBwcm90ZWN0aW9uIHN1Y2ggYXMgTGluZWFyIFByb3RlY3Rpb24gU3dpdGNoaW5nICgxOjEsIDEr
MSksIFJpbmcNCiAgIHByb3RlY3Rpb24gc3dpdGNoaW5nIG9yIE1QTFMgRmFzdCBSZXJvdXRlIChG
UlIpIE1BWSBzdGlsbCBiZSB1c2VkIHRvDQogICBlbnN1cmUgdGhlIExTUC9QVyBpcyByZWFkeSBm
b3IgcG9zc2libGUgZnV0dXJlIGZhaWx1cmUgb2YgdGhlDQogICBjb21tdW5pY2F0aW9uIHBhdGgg
YmV0d2VlbiBSZWR1bmRhbnQgTWFzdGVyIGFuZCBTbGF2ZS4NCg0KICAgTm90ZSB0aGF0IGFueSBw
cm90ZWN0aW9uIG9yIHJlcm91dGUgbWVjaGFuaXNtIHRoYXQgYWRkcyBhZGRpdGlvbmFsDQogICBs
YWJlbCB0byB0aGUgbGFiZWwgc3RhY2ssIHN1Y2ggYXMgRmFjaWxpdHkgQmFja3VwIEZSUiwgaXMg
bm90DQogICByZWNvbW1lbmRlZCBzaW5jZSB0aGUgTFNScyBpbiB0aGUgYmFja3VwIHBhdGggd29u
J3QgYmUgYWJsZSB0bw0KICAgcHJvcGVybHkgcHJvY2VzcyBQVFAgbWVzc2FnZXMgZm9yIFRyYW5z
cGFyZW50IENsb2NraW5nLg0KDQo5LiBFQ01QIGFuZCBMQUcNCg0KICAgVG8gZW5zdXJlIHRoZSBw
cm9wZXIgb3BlcmF0aW9uIG9mIDE1ODggU2xhdmVzLCB0aGUgcGh5c2ljYWwgcGF0aCBmb3INCiAg
IFBUUCBtZXNzYWdlcyBmcm9tIE1hc3RlciB0byBTbGF2ZSBhbmQgdmljZSB2ZXJzYSBNVVNUIGJl
IHRoZSBzYW1lIGZvcg0KICAgYWxsIFBUUCBtZXNzYWdlcyBsaXN0ZWQgaW4gc2VjdGlvbiA3IGFu
ZCBNVVNUIG5vdCBjaGFuZ2UgZXZlbiBpbg0KICAgcHJlc2VuY2Ugb2YgRUNNUCBhbmQgTEFHIGlu
IHRoZSBNUExTIG5ldHdvcmsuDQoNCiAgIFRoZSBuZXR3b3JrIG9wZXJhdG9yIE1VU1QgZWl0aGVy
IGVuc3VyZSB0aGF0IHRoZSBFQ01QIG9yIExBRyBoYXNoaW5nDQogICBhbGdvcml0aG1zIGtlZXAg
dGhlIFBUUCBtZXNzYWdlcyBkZXNjcmliZWQgaW4gc2VjdGlvbiA3IGFuZCBiZWxvbmdpbmcNCiAg
IHRvIHRoZSBzYW1lIDE1ODggZmxvdyBvbiB0aGUgc2FtZSBsaW5rIGFuZCBwYXRoLCBvciBNVVNU
IGRpc2FibGUgTEFHDQogICBhbmQvb3IgRUNNUCBmb3IgdGhlIFBUUCBMU1BzIGFuZC9vciBQV3Mu
DQoNCg0KDQpEYXZhcmkgZXQgYWwuICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDE1LCAyMDExICAg
ICAgICAgICAgICAgIFtQYWdlIDldDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAxNTg4
IG92ZXIgTVBMUyAgICAgICAgICAgICAgICAgICAgSnVseSAyMDEwDQoNCg0KMTAuIE9BTSwgQ29u
dHJvbCBhbmQgTWFuYWdlbWVudA0KDQogICBJbiBvcmRlciB0byBtYW5hZ2UgUFRQIExTUHMgYW5k
IFBUUCBQV3MsIHRoZXkgTUFZIGNhcnJ5IE9BTSwgQ29udHJvbA0KICAgYW5kIE1hbmFnZW1lbnQg
bWVzc2FnZXMuIFRoZSBtYW5kYXRvcnkgcHJlc2VuY2Ugb2YgQ1cgaW4gZWFjaCBQVFAgUFcNCiAg
IGVuc3VyZXMgdGhhdCBzdWNoIE9BTSwgQ29udHJvbCBhbmQgTWFuYWdlbWVudCBtZXNzYWdlcyBj
b3VsZCBiZQ0KICAgZWFzaWx5IHBhcnNlZCBhbmQgZGlmZmVyZW50aWF0ZWQgZnJvbSB0aGUgUFRQ
IG1lc3NhZ2VzLg0KDQogICBJbiBwYXJ0aWN1bGFyIEJGRCBbUkZDNTg4MF0sIFtSRkM1ODg0XSBh
bmQgTFNQLVBpbmcgW1JGQzQzODldIE1BWSBydW4NCiAgIG92ZXIgUFRQIExTUHMgdmlhIFVEUC9J
UCBlbmNhcHN1bGF0aW9uIG9yIHZpYSBHQUwvRy1BQ0guIFRoZXNlDQogICBNYW5hZ2VtZW50IHBy
b3RvY29scyBhcmUgZWFzaWx5IGlkZW50aWZpZWQgYnkgdGhlIFVEUCBEZXN0aW5hdGlvbg0KICAg
UG9ydCBudW1iZXIgb3IgYnkgR0FML0FDSCByZXNwZWN0aXZlbHkuDQoNCiAgIEFsc28gQkZELCBM
U1AtUGluZyBhbmQgb3RoZXIgTWFuYWdlbWVudCBtZXNzYWdlcyBNQVkgcnVuIG92ZXIgUFRQIFBX
DQogICB2aWEgb25lIG9mIHRoZSBkZWZpbmVkIFZDQ1ZzIChUeXBlIDEsIDIgb3IgMykgW1JGQzUw
ODVdLiBJbiB0aGlzIGNhc2UNCiAgIEctQUNILCBSb3V0ZXIgQWxlcnQgTGFiZWwgKFJBTCksIG9y
IFBXIGxhYmVsIChUVEw9MSkgYXJlIHVzZWQgdG8NCiAgIGlkZW50aWZ5IHN1Y2ggTWFuYWdlbWVu
dCBtZXNzYWdlcy4NCg0KMTEuIEZDUyBSZWNhbGN1bGF0aW9uDQoNCiAgIEV0aGVybmV0IEZDUyBN
VVNUIGJlIHJlY2FsY3VsYXRlZCBhdCBldmVyeSBMU1IgdGhhdCBwZXJmb3JtcyB0aGUgVEMNCiAg
IHByb2Nlc3NpbmcgYW5kIEZDUyByZXRlbnRpb24gZGVzY3JpYmVkIGluIFtSRkM0NzIwXSBNVVNU
IG5vdCBiZSB1c2VkLg0KDQoNCg0KMTIuIFJTVlAtVEUvR01QTFMgRXh0ZW5zaW9ucyBmb3Igc3Vw
cG9ydCBvZiAxNTg4DQoNCiAgIFJTVlAtVEUvR01QTFMgc2lnbmFsaW5nIE1BWSBiZSB1c2VkIHRv
IHNldHVwIHRoZSBQVFAgTFNQcy4gQSBuZXcgVExWDQogICBpcyByZXF1aXJlZCB0byBzaWduYWwg
dGhhdCB0aGlzIGlzIGEgUFRQIExTUC4gVGhlIE9GRlNFVCBmcm9tIGJvdHRvbQ0KICAgb2YgbGFi
ZWwgc3RhY2sgdG8gdGhlIHN0YXJ0IG9mIHRoZSBQVFAgUERVIE1BWSBiZSBzaWduYWxlZC4gVGhl
IExTUnMNCiAgIHRoYXQgcmVjZWl2ZSBhbmQgcHJvY2VzcyB0aGUgUlNWUC1URS9HTVBMUyBtZXNz
YWdlcyBNQVkgdXNlIHRoZQ0KICAgT0ZGU0VUIHRvIGxvY2F0ZSB0aGUgUFRQICdjb3JyZWN0aW9u
IGZpZWxkJy4NCg0KMTMuIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zDQoNCiAgIE1QTFMgUFcgc2Vj
dXJpdHkgY29uc2lkZXJhdGlvbnMgaW4gZ2VuZXJhbCBhcmUgZGlzY3Vzc2VkIGluIFtSRkMzOTg1
XQ0KICAgYW5kIFtSRkM0NDQ3XSwgYW5kIHRob3NlIGNvbnNpZGVyYXRpb25zIGFsc28gYXBwbHkg
dG8gdGhpcyBkb2N1bWVudC4NCg0KDQogICBBbiBleHBlcmltZW50YWwgc2VjdXJpdHkgcHJvdG9j
b2wgaXMgZGVmaW5lZCBpbiBbMV0uICBUaGUgUFRQDQogICBzZWN1cml0eSBleHRlbnNpb24gYW5k
IHByb3RvY29sIHByb3ZpZGUgZ3JvdXAgc291cmNlIGF1dGhlbnRpY2F0aW9uLA0KICAgbWVzc2Fn
ZSBpbnRlZ3JpdHksIGFuZCByZXBsYXkgYXR0YWNrIHByb3RlY3Rpb24gZm9yIFBUUCBtZXNzYWdl
cy4NCg0KMTQuIElBTkEgQ29uc2lkZXJhdGlvbnMNCg0KICAgQSBuZXcgVExWIGlzIHJlcXVpcmVk
IHRvIHNpZ25hbCB0aGF0IFBUUCBMU1BzLiBJQU5BIG5lZWRzIHRvIGFzc2lnbg0KICAgdGhlIG5l
dyBUTFYgVHlwZS4NCg0KDQpEYXZhcmkgZXQgYWwuICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDE1
LCAyMDExICAgICAgICAgICAgICAgW1BhZ2UgMTBdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAg
ICAgICAxNTg4IG92ZXIgTVBMUyAgICAgICAgICAgICAgICAgICAgSnVseSAyMDEwDQoNCg0KDQoN
CjE1LjEuIE5vcm1hdGl2ZSBSZWZlcmVuY2VzDQoNCiAgIFtJRUVFMTU4OF0gSUVFRSBTdGFuZGFy
ZCBmb3IgYSBQcmVjaXNpb24gQ2xvY2sgU3luY2hyb25pemF0aW9uDQogICAgICAgICAgICAgICBQ
cm90b2NvbCBmb3IgTmV0d29ya2VkIE1lYXN1cmVtZW50IGFuZCBDb250cm9sIFN5c3RlbXMsDQog
ICAgICAgICAgICAgICBJRUVFIDE1ODgtMjAwOA0KDQogICBbUkZDNDQ0OF0gIE1hcnRpbmksIEwu
LCBSb3NlbiwgRS4sIEVsLUFhd2FyLCBhbmQgRy5IZXJvbiwNCiAgICAgICAgICAgICAgICJFbmNh
cHN1bGF0aW9uIE1ldGhvZHMgZm9yIFRyYW5zcG9ydCBvZiBFdGhlcm5ldCBvdmVyDQogICAgICAg
ICAgICAgICBNUExTIE5ldHdvcmtzIiwgQXByaWwgMjAwNi4NCg0KICAgW1JGQzQzODldICBLLiBL
b21wZWxsYSwgRy4gU3dhbGxvdywgIkRldGVjdGluZyBNdWx0aS1Qcm90b2NvbCBMYWJlbA0KICAg
ICAgICAgICAgICAgU3dpdGNoZWQgKE1QTFMpIERhdGEgUGxhbmUgRmFpbHVyZXMiLCBGZWJydWFy
eSAyMDA2DQoNCiAgIFtSRkM1MDg1XSAgVC4gTmFkZWF1LCBDLiBQaWduYXRhcm8gIlBzZXVkb3dp
cmUgVmlydHVhbCBDaXJjdWl0DQogICAgICAgICAgICAgICBDb25uZWN0aXZpdHkgVmVyaWZpY2F0
aW9uIChWQ0NWKTpBIENvbnRyb2wgQ2hhbm5lbCBmb3INCiAgICAgICAgICAgICAgIFBzZXVkb3dp
cmVzIiwgRGVjZW1iZXIgMjAwNw0KDQogICBbUkZDNTg4MF0gICBELiBLYXR6LCBELiBXYXJkLCAi
QmlkaXJlY3Rpb25hbCBGb3J3YXJkaW5nIERldGVjdGlvbiIsDQogICAgICAgICAgICAgICBKdW5l
IDIwMTANCg0KICAgW1JGQzM5ODVdICBCcnlhbnQsIFMuIGFuZCBQLiBQYXRlLCAiUHNldWRvIFdp
cmUgRW11bGF0aW9uIEVkZ2UtdG8tDQogICAgICAgICAgICAgICBFZGdlIChQV0UzKSBBcmNoaXRl
Y3R1cmUiLCBNYXJjaCAyMDA1DQoNCiAgIFtSRkM0NDQ3XSAgTWFydGluaSwgTC4sIFJvc2VuLCBF
LiwgRWwtQWF3YXIsIE4uLCBTbWl0aCwgVC4sIGFuZCBHLg0KICAgICAgICAgICAgICAgSGVyb24s
ICJQc2V1ZG8gd2lyZSBTZXR1cCBhbmQgTWFpbnRlbmFuY2UgVXNpbmcgdGhlIExhYmVsDQogICAg
ICAgICAgICAgICBEaXN0cmlidXRpb24gUHJvdG9jb2wgKExEUCkiLCBBcHJpbCAyMDA2Lg0KDQog
ICBbUkZDNTg4NF0gICAgUi4gQWdnYXJ3YWwsIEsuIEtvbXBlbGxhLCBULiBOYWRlYXUsIEcuIFN3
YWxsb3csDQogICAgICAgICAgICAgICAiQmlkaXJlY3Rpb25hbCBGb3J3YXJkaW5nIERldGVjdGlv
biBmb3IgTVBMUyIsDQogICAgICAgICAgICAgICBKdW5lIDIwMTANCg0KICAgW1JGQzQ3MjBdICBB
LiBNYWxpcywgRC5BbGxhbixOLiBEZWwgUmVnbm8sICJQc2V1ZG93aXJlIEVtdWxhdGlvbg0KICAg
ICAgICAgICAgICAgRWRnZS10by1FZGdlIChQV0UzKUZyYW1lIENoZWNrIFNlcXVlbmNlIFJldGVu
dGlvbiIsDQogICAgICAgICAgICAgICBOb3ZlbWJlciAyMDA2DQoNCg0KDQoxNS4yLiBJbmZvcm1h
dGl2ZSBSZWZlcmVuY2VzDQoNCiAgICBbRmF0IFBXXSAgIFMuIEJyeWFudCwgIkZsb3cgQXdhcmUg
VHJhbnNwb3J0IG9mIFBzZXVkb3dpcmVzIG92ZXIgYW4NCiAgICAgICAgICAgICAgIE1QTFMgUFNO
IiwgSmFudWFyeSAyMDEwDQoNCg0KDQoNCg0KDQpEYXZhcmkgZXQgYWwuICAgICAgICAgRXhwaXJl
cyBKYW51YXJ5IDE1LCAyMDExICAgICAgICAgICAgICAgW1BhZ2UgMTFdDQoMDQpJbnRlcm5ldC1E
cmFmdCAgICAgICAgICAgICAxNTg4IG92ZXIgTVBMUyAgICAgICAgICAgICAgICAgICAgSnVseSAy
MDEwDQoNCg0KMTYuIEFja25vd2xlZGdtZW50cw0KDQoNCg0KQXV0aG9ycycgQWRkcmVzc2VzDQoN
CiAgIFNoYWhyYW0gRGF2YXJpDQogICBCcm9hZGNvbSBDb3JwLg0KICAgMzE1MSBaYW5rZXIgUm9h
ZA0KICAgU2FuIEpvc2UsIENBIDk1MTM0DQoNCiAgIEVtYWlsOiBkYXZhcmlAaWVlZS5vcmcNCiAg
ICAgICAgICBkYXZhcmlAYm9hZGNvbS5jb20NCg0KDQogICBBbWl0IE9yZW4NCiAgIEJyb2FkY29t
IENvcnAuDQogICAzMTUxIFphbmtlciBSb2FkDQogICBTYW4gSm9zZSwgQ0EgOTUxMzQNCg0KICAg
RW1haWw6IGFtaXRvQGJyb2FkY29tLmNvbQ0KDQogICBMdWNhIE1hcnRpbmkNCiAgIENpc2NvIFN5
c3RlbXMNCiAgIFNhbiBKb3NlLENBDQoNCiAgIEVtYWlsOiBMbWFydGluaUBjaXNjby5jb20NCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkRhdmFyaSBldCBhbC4gICAg
ICAgICBFeHBpcmVzIEphbnVhcnkgMTUsIDIwMTEgICAgICAgICAgICAgICBbUGFnZSAxMl0NCgwN
Cg==

--_002_2C2F1EBA8050E74EA81502D5740B4BD6940EC2928CSJEXCHCCR02co_--


From Adrian.Farrel@huawei.com  Sun Jul 18 03:48:39 2010
Return-Path: <Adrian.Farrel@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C28733A683E; Sun, 18 Jul 2010 03:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.466
X-Spam-Level: 
X-Spam-Status: No, score=-1.466 tagged_above=-999 required=5 tests=[AWL=-0.727, BAYES_20=-0.74, STOX_REPLY_TYPE=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 acubYW-F2bZ5; Sun, 18 Jul 2010 03:48:38 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 496733A67F7; Sun, 18 Jul 2010 03:48:38 -0700 (PDT)
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 <0L5R00BJ521F1I@usaga01-in.huawei.com>; Sun, 18 Jul 2010 03:48:51 -0700 (PDT)
Received: from your029b8cecfe (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 <0L5R006SS21D26@usaga01-in.huawei.com>; Sun, 18 Jul 2010 03:48:51 -0700 (PDT)
Date: Sun, 18 Jul 2010 11:38:05 +0100
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: mpls@ietf.org, mpls-tp@ietf.org
Message-id: <446D99C21015471B814C41435E3086FA@your029b8cecfe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; format=flowed; charset=utf-8; reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Cc: mpls-ads@tools.ietf.org, mpls-chairs@tools.ietf.org, draft-ietf-mpls-tp-fault@tools.ietf.org
Subject: [mpls] Fw: [IANA #351929] Request for Early Allocation for an ACH Code Point for Fault OAM
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <Adrian.Farrel@huawei.com>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Jul 2010 10:48:40 -0000

Hi,

In order to facilitate interoperability testing of early implementations of 
draft-ietf-mpls-tp-fault, the WG chairs applied to IANA for an early code 
point allocation of the ACH type value for Fault OAM.

The IESG recently approved this early allocation per RFC 4020, and the note 
below shows the resulting allocation.

Thanks,
Adrian

----- Original Message ----- 
From: "Amanda Baber via RT" <iana-prot-param@iana.org>
To: <Adrian.Farrel@huawei.com>
Sent: Friday, July 16, 2010 10:33 PM
Subject: [IANA #351929] Request for Early Allocation for an ACH Code Point 
for Fault OAM


> Hi all,
>
> We've assigned the following Pseudowire Associated Channel Type:
>
> Value   Description                     TLV Follows  Reference
> ------  ------------------------------  -----------  ---------
> 0x0058  Fault OAM (TEMPORARY - expires 2011-07-16)  No
> [draft-ietf-mpls-tp-fault]
>
> Please see
> http://www.iana.org/assignments/pwe3-parameters
>
> We'll remove the "TEMPORARY" designation after the IESG approves the
> document for publication.
>
> Best regards,
>
> Amanda Baber
> IANA



From hhelvoort@chello.nl  Mon Jul 19 06:03:14 2010
Return-Path: <hhelvoort@chello.nl>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AA833A6850; Mon, 19 Jul 2010 06:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[AWL=0.700,  BAYES_00=-2.599]
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 dNemquA4XxQ5; Mon, 19 Jul 2010 06:03:09 -0700 (PDT)
Received: from fep12.mx.upcmail.net (fep12.mx.upcmail.net [62.179.121.32]) by core3.amsl.com (Postfix) with ESMTP id 25F183A67AF; Mon, 19 Jul 2010 06:03:08 -0700 (PDT)
Received: from edge01.upcmail.net ([192.168.13.236]) by viefep12-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100719130321.RRXN20209.viefep12-int.chello.at@edge01.upcmail.net>; Mon, 19 Jul 2010 15:03:21 +0200
Received: from McAsterix.local ([77.250.51.60]) by edge01.upcmail.net with edge id jp3K1e03N1Hw6VZ01p3LkC; Mon, 19 Jul 2010 15:03:21 +0200
X-SourceIP: 77.250.51.60
Message-ID: <4C444D17.40904@chello.nl>
Date: Mon, 19 Jul 2010 15:03:19 +0200
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: Nitin Bahadur <nitinb@juniper.net>
References: <C85B7799.12744%nitinb@juniper.net>
In-Reply-To: <C85B7799.12744%nitinb@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Cloudmark-Analysis: v=1.1 cv=K3uBg944YaUT+Qsu6bWO0a0V3uPy4DQNslbdoMCD4tw= c=1 sm=0 a=BtkJuX86MzcA:10 a=8nJEP1OIZ-IA:10 a=FPig4UQT7IWdttPdGMEA:9 a=Iio9IfRCGOi_DhPfs_rdmlWKYz4A:4 a=wPNLvfGTeEIA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] comment to draft-nitinb-mpls-tp-on-demand-cv
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jul 2010 13:03:14 -0000

Hello Nitin,

You replied:

>> It does not document how this tool can be used in transport
>> environment where tools are enabled/disabled static (compared
>> to the dynamic set-up of LSP-ping.
>
> LSP-Ping is indeed dynamic in the request/response sense. However, the LSP
> by itself can be setup statically or using RSVP-TE. If it is setup
> statically, then section 2.4 applies. Can you clarify your comment.

Section 2.4 describes how to identify a static LSP.

My question concerns the activation/enabling/instantiation of
the tool.
In transport networks when tools are enabled the appropriate
parameters are set (e.g. periodicity, MEL, thresholds, etc.)
and it is expected that no negotiation between the end-points
takes place after this provisioning. If one of the end-points
gets an unexpected result this is reported to the NMS.
This enabling is considered to be static.
I cannot find any description of this expected behaviour in
transport netwroks in the draft.

Regards, Huub.

-- 
================================================================
Always remember that you are unique...just like everyone else...

From martin.vigoureux@alcatel-lucent.com  Mon Jul 19 09:02:20 2010
Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 462B03A6944; Mon, 19 Jul 2010 09:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 ZWoGRzTT1sjl; Mon, 19 Jul 2010 09:02:19 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 6B9D63A6937; Mon, 19 Jul 2010 09:02:18 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o6JG2VWa030006 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 19 Jul 2010 18:02:31 +0200
Received: from FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com ([135.120.45.38]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Mon, 19 Jul 2010 18:02:31 +0200
From: "VIGOUREUX, MARTIN (MARTIN)" <martin.vigoureux@alcatel-lucent.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Content-Class: 
Date: Mon, 19 Jul 2010 18:02:31 +0200
Thread-Topic: IETF 78 agenda uploaded - start to send slides
Thread-Index: AcsnW8s4k9baFV0pTu6rmBgeLxSMNA==
Message-ID: <CCBFBB7025DF984494DEC3285C058152125E227B3A@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR, en-US
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="_23E72599-4642-C626-F7E6-7A8BE58E2EA8_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: [mpls] IETF 78 agenda uploaded - start to send slides
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jul 2010 16:02:21 -0000

--_23E72599-4642-C626-F7E6-7A8BE58E2EA8_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

All,

Sorry for the delay we had quite a lot of slot requests.
The agenda is available at:
http://www.ietf.org/proceedings/78/agenda/mpls.txt

Please start sending me your slides. Similarly to the agenda, if I do not r=
ecieve the slides in time such that I can upload them before the session yo=
u take the risk of not being able to present.

Thank you.
martin=

--_23E72599-4642-C626-F7E6-7A8BE58E2EA8_
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIHxTCCB8Ew
ggapoAMCAQICCkw1m98AAAAABFcwDQYJKoZIhvcNAQEFBQAwgYkxEzARBgoJkiaJk/IsZAEZFgNj
b20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQK
Ew5BbGNhdGVsIEx1Y2VudDErMCkGA1UEAxMiQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgU1NMIFN1
YiBDQTAeFw0wOTExMjgxODU1MThaFw0xMTExMjgxODU1MThaMIG0MRMwEQYKCZImiZPyLGQBGRYD
Y29tMRYwFAYKCZImiZPyLGQBGRYGbHVjZW50MRQwEgYKCZImiZPyLGQBGRYEZW1lYTEVMBMGA1UE
CxMMRG9tYWluIFVzZXJzMREwDwYDVQQLEwhQZXJzb25hbDERMA8GA1UEAxMIbXZpZ291cmUxMjAw
BgkqhkiG9w0BCQEWI21hcnRpbi52aWdvdXJldXhAYWxjYXRlbC1sdWNlbnQuY29tMIGfMA0GCSqG
SIb3DQEBAQUAA4GNADCBiQKBgQCh50j+Yh4E7CPCPvLVZ4Suq4tY5pKAC1wxxtMrcY/JHjhev0sB
oKlvPykmrmhTxVipwGmxwvZu+MLiVWH5J1btbW3GR5evzpxWSdth6HQ577/htb5x1fjjNtBQ9mAt
PJo9dlpdPCIMVND9Wj/5lgt9Q75f5rFJWK5RmEWjGDjr3wIDAQABo4IEgDCCBHwwHQYDVR0OBBYE
FNDObvGf7D9xijVps//xID6wIwGgMB8GA1UdIwQYMBaAFGTRUS1b/OnwI/TfZOp1xh75BBizMIIB
aAYDVR0fBIIBXzCCAVswggFXoIIBU6CCAU+Ggd9sZGFwOi8vL0NOPUFsY2F0ZWwlMjBMdWNlbnQl
MjBJbnRlcm5hbCUyMFNTTCUyMFN1YiUyMENBLENOPXVzbmF2c3BraTAycCxDTj1DRFAsQ049UHVi
bGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFk
LERDPWx1Y2VudCxEQz1jb20/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENs
YXNzPWNSTERpc3RyaWJ1dGlvblBvaW50hi5odHRwOi8vd3d3LmFsY2F0ZWwtbHVjZW50LmNvbS9Q
S0kvU1NMc3ViQ0EuY3JshjtodHRwOi8vc2VydmljZXMuc3VwcG9ydC5hbGNhdGVsLWx1Y2VudC5j
b20vUEtJL1NTTHN1YkNBLmNybDCCAWwGCCsGAQUFBwEBBIIBXjCCAVowgdIGCCsGAQUFBzAChoHF
bGRhcDovLy9DTj1BbGNhdGVsJTIwTHVjZW50JTIwSW50ZXJuYWwlMjBTU0wlMjBTdWIlMjBDQSxD
Tj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJh
dGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdENs
YXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwOgYIKwYBBQUHMAKGLmh0dHA6Ly93d3cuYWxjYXRl
bC1sdWNlbnQuY29tL1BLSS9TU0xzdWJDQS5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9zZXJ2aWNl
cy5zdXBwb3J0LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kvU1NMc3ViQ0EuY3J0MAwGA1UdEwEB/wQC
MAAwCwYDVR0PBAQDAgSwMD4GCSsGAQQBgjcVBwQxMC8GJysGAQQBgjcVCIW9xVmD47E5h6WBKoa/
w0KFlJgZgQuDmcNjg7nVWQIBZAIBEjApBgNVHSUEIjAgBggrBgEFBQcDAgYIKwYBBQUHAwQGCisG
AQQBgjcKAwQwNQYJKwYBBAGCNxUKBCgwJjAKBggrBgEFBQcDAjAKBggrBgEFBQcDBDAMBgorBgEE
AYI3CgMEMFsGA1UdEQRUMFKgKwYKKwYBBAGCNxQCA6AdDBttdmlnb3VyZUBBbGNhdGVsLUx1Y2Vu
dC5jb22BI21hcnRpbi52aWdvdXJldXhAYWxjYXRlbC1sdWNlbnQuY29tMEQGCSqGSIb3DQEJDwQ3
MDUwDgYIKoZIhvcNAwICAgCAMA4GCCqGSIb3DQMEAgIAgDAHBgUrDgMCBzAKBggqhkiG9w0DBzAN
BgkqhkiG9w0BAQUFAAOCAQEAUJRi5CEGA4geDPYhfZfnta/rrKb2mGBsAwRADaCgrIkdcK0Pk+n9
FpKlFLi4VAyERE74HJ7fuVs9hzViocXfjKDdb/1J49QFv1TfDpvhXCh0j+odazhbjq1DOX5JPrXC
C9X2OIXMU18XE7zh/aspIGDj+cRgJfk1XxTOnnn3TAAWdZMnIg78yA9HbszKSogjFRHhpHRJGg/s
c3KC9J7bac1tzZuSdEkMv/VX8VF3NNw+srIrVqbjzTqu5tAu5UXXIqHIhTfx2s3j0ZGrHNgHWpQT
wKFQTgX/Eu+vmV0rlZjvmlmTGsFQqdMRIQj7IdyCu6AtjJdyEWzY5Le81nj4jTGCAZ4wggGaAgEB
MIGYMIGJMRMwEQYKCZImiZPyLGQBGRYDY29tMRYwFAYKCZImiZPyLGQBGRYGbHVjZW50MRQwEgYK
CZImiZPyLGQBGRYEbmEwMjEXMBUGA1UEChMOQWxjYXRlbCBMdWNlbnQxKzApBgNVBAMTIkFsY2F0
ZWwgTHVjZW50IEludGVybmFsIFNTTCBTdWIgQ0ECCkw1m98AAAAABFcwCQYFKw4DAhoFAKBdMBgG
CSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEwMDcxOTE2MDIyNlowIwYJ
KoZIhvcNAQkEMRYEFI5Qm80Dwn2SuZJUq36pOr8Ies61MA0GCSqGSIb3DQEBAQUABIGANTX0efFM
wTkQNckJyFkPNjJWYNOAvFgQAwXqwW0yyUfL/QZFMP8pkI3OdwgAaNQ204reX4cGI2KKxb+3sArN
hZkmHV7Pi6S4v/Kcrj0ZTZWT9OGl0f4llIWIUd4u6M10SVOVBElIpYgtYmf12nuoZU/fCm9IAxHv
5QQ+Kf5fDw4AAAAAAAA=

--_23E72599-4642-C626-F7E6-7A8BE58E2EA8_--

From dongjie_dj@huawei.com  Mon Jul 19 19:07:53 2010
Return-Path: <dongjie_dj@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B0703A6BD3 for <mpls@core3.amsl.com>; Mon, 19 Jul 2010 19:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 CNURTZ8j48ND for <mpls@core3.amsl.com>; Mon, 19 Jul 2010 19:07:51 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 413D93A69BE for <mpls@ietf.org>; Mon, 19 Jul 2010 19:07:47 -0700 (PDT)
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 <0L5U0052V393P1@szxga04-in.huawei.com> for mpls@ietf.org; Tue, 20 Jul 2010 10:07:51 +0800 (CST)
Received: from 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 <0L5U00ANO3933A@szxga04-in.huawei.com> for mpls@ietf.org; Tue, 20 Jul 2010 10:07:51 +0800 (CST)
Received: from d65110 ([10.110.98.130]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5U000KX392DU@szxml06-in.huawei.com> for mpls@ietf.org; Tue, 20 Jul 2010 10:07:51 +0800 (CST)
Date: Tue, 20 Jul 2010 10:07:50 +0800
From: Jie Dong <dongjie_dj@huawei.com>
To: mpls@ietf.org
Message-id: <007101cb27b0$5b3c58c0$82626e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsnsFr3kanbqkaITHy/LcJr9EZCNg==
Subject: [mpls] New Draft Notification: draft-dong-mpls-rsvp-te-plr-designation-00
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 02:07:53 -0000

Dear all, 

We have submitted a new internet draft "Designation of PLRs in RSVP-TE Fast
Reroute"

The URL is:
http://tools.ietf.org/html/draft-dong-mpls-rsvp-te-plr-designation-00

The abstract is as follows: 

This document defines RSVP-TE extensions which enable the ingress node to
designate particular LSRs along the path as Points of Local Repair (PLRs) of
the protected LSP, and further indicate the protection type of each PLR.
These mechanisms could enhance the control over the establishment of backup
LSPs, and also could save the resources needed for establishing and
maintaining unnecessary backup LSPs.

Any comments and suggestions are appreciated.


Best regards,
Jie


From venkatflex@gmail.com  Tue Jul 20 04:59:34 2010
Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 093333A68F1 for <mpls@core3.amsl.com>; Tue, 20 Jul 2010 04:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 EdP4LK3oL7yh for <mpls@core3.amsl.com>; Tue, 20 Jul 2010 04:59:33 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 225A53A6872 for <mpls@ietf.org>; Tue, 20 Jul 2010 04:59:33 -0700 (PDT)
Received: by pvd12 with SMTP id 12so3085393pvd.31 for <mpls@ietf.org>; Tue, 20 Jul 2010 04:59:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=3cr8N9gWh0zuTLu1S2Df3ZqblX6rB6YKEt3JEnIiAlM=; b=kWZ2ZtPPMfweauIrU4l5wEXPGrF0l4E29MhDbSeCacHuvzg4TcqM8N0E6g383I0Hzj jAYhi6U4sNvmDN2U5iuBffU+VLnwk2WS5vMAvTMIpFOTkdemO78pY1XsnnS5sq0Nkc2s jXAsR/JT4C9w7apNCAdMNlynIde1fYdw1ji7Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VnPSImPlaImXY+NX91bCVhZ5c9F7IBErA7rbVKU7+b+TuHdpAS1ZlrJw5jU12PLTkq 016YcHURKFsYwvfjBf+DQ1XZ4KIxJeFdgoshvKLV3gNv/zFxGWi1x7FTshe/1E62A+WN rgUgq4GWR0yyYLZMWGbl+iCoKMtnu1QJZMgpI=
MIME-Version: 1.0
Received: by 10.142.215.7 with SMTP id n7mr6577190wfg.194.1279627188210; Tue,  20 Jul 2010 04:59:48 -0700 (PDT)
Received: by 10.142.77.1 with HTTP; Tue, 20 Jul 2010 04:59:48 -0700 (PDT)
In-Reply-To: <007101cb27b0$5b3c58c0$82626e0a@china.huawei.com>
References: <007101cb27b0$5b3c58c0$82626e0a@china.huawei.com>
Date: Tue, 20 Jul 2010 17:29:48 +0530
Message-ID: <AANLkTim7PAn8b-K0dq-i-k6Qx3LJkm5HwaV02QHDFFQo@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: Jie Dong <dongjie_dj@huawei.com>, mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary=000e0cd3039effab4b048bd06bb0
Subject: Re: [mpls] New Draft Notification: draft-dong-mpls-rsvp-te-plr-designation-00
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 11:59:34 -0000

--000e0cd3039effab4b048bd06bb0
Content-Type: text/plain; charset=ISO-8859-1

Hi,
This draft is good in selecting the PLRs in the initial LSP setup itself.
But can this draft handle the dynamic PLR node change?
Do you have any thought on constrcuting the new TLVs to send the new EROs in
the established LSP to indicate the new PLR nodes?

Do you really think that administrator should know about all the transit
nodes of the LSP? I think, this is possible with the help of CSPF but
collecting the informations about transit node's resources and other
informations may be tough.

Thanks,
Venkat.
On Tue, Jul 20, 2010 at 7:37 AM, Jie Dong <dongjie_dj@huawei.com> wrote:

>
> Dear all,
>
> We have submitted a new internet draft "Designation of PLRs in RSVP-TE Fast
> Reroute"
>
> The URL is:
> http://tools.ietf.org/html/draft-dong-mpls-rsvp-te-plr-designation-00
>
> The abstract is as follows:
>
> This document defines RSVP-TE extensions which enable the ingress node to
> designate particular LSRs along the path as Points of Local Repair (PLRs)
> of
> the protected LSP, and further indicate the protection type of each PLR.
> These mechanisms could enhance the control over the establishment of backup
> LSPs, and also could save the resources needed for establishing and
> maintaining unnecessary backup LSPs.
>
> Any comments and suggestions are appreciated.
>
>
> Best regards,
> Jie
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>



-- 
Best Regards,
Venkatesan Mahalingam.

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

<div>Hi,</div>
<div>This draft is good in selecting the PLRs in the initial LSP setup itse=
lf. But can this draft handle the dynamic PLR node change?</div>
<div>Do you have any thought on constrcuting the new TLVs to send the new E=
ROs in the established LSP to indicate the new PLR nodes?</div>
<div>=A0</div>
<div>Do you really think that administrator should know about all the trans=
it nodes of the LSP? I think, this is possible with the help of CSPF but co=
llecting the informations about transit node&#39;s resources and other info=
rmations may be tough.</div>

<div>=A0</div>
<div>Thanks,</div>
<div>Venkat.<br>On Tue, Jul 20, 2010 at 7:37 AM, Jie Dong <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:dongjie_dj@huawei.com">dongjie_dj@huawei.com</a>&gt;=
</span> wrote:<br></div>
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>Dear all,<br><br>We have sub=
mitted a new internet draft &quot;Designation of PLRs in RSVP-TE Fast<br>Re=
route&quot;<br>
<br>The URL is:<br><a href=3D"http://tools.ietf.org/html/draft-dong-mpls-rs=
vp-te-plr-designation-00" target=3D"_blank">http://tools.ietf.org/html/draf=
t-dong-mpls-rsvp-te-plr-designation-00</a><br><br>The abstract is as follow=
s:<br>
<br>This document defines RSVP-TE extensions which enable the ingress node =
to<br>designate particular LSRs along the path as Points of Local Repair (P=
LRs) of<br>the protected LSP, and further indicate the protection type of e=
ach PLR.<br>
These mechanisms could enhance the control over the establishment of backup=
<br>LSPs, and also could save the resources needed for establishing and<br>=
maintaining unnecessary backup LSPs.<br><br>Any comments and suggestions ar=
e appreciated.<br>
<br><br>Best regards,<br>Jie<br><br>_______________________________________=
________<br>mpls mailing list<br><a href=3D"mailto:mpls@ietf.org">mpls@ietf=
.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Best Regards,<br>Venkat=
esan Mahalingam.<br>

--000e0cd3039effab4b048bd06bb0--

From curtis@occnc.com  Tue Jul 20 07:43:19 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B264B3A6BF6; Tue, 20 Jul 2010 07:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level: 
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599]
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 zdGjNqdVByPD; Tue, 20 Jul 2010 07:43:18 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 34A823A6BDA; Tue, 20 Jul 2010 07:43:18 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6KEhUPh062225; Tue, 20 Jul 2010 10:43:30 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007201443.o6KEhUPh062225@harbor.orleans.occnc.com>
To: "Shahram Davari" <davari@broadcom.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Fri, 16 Jul 2010 16:48:51 PDT." <2C2F1EBA8050E74EA81502D5740B4BD6940EC2928C@SJEXCHCCR02.corp.ad.broadcom.com>
Date: Tue, 20 Jul 2010 10:43:30 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 14:43:19 -0000

In message <2C2F1EBA8050E74EA81502D5740B4BD6940EC2928C@SJEXCHCCR02.corp.ad.broadcom.com>
"Shahram Davari" writes:
>  
>  
> Hi,
>  
> Please find the txt format of 1588 over mpls draft. There has been some dis=
> cussion over the mailing list. I will update it based on the consensus.
>  
> Thanks,
> Shahram


Shahram,

Thanks for converting to XML and producing a text version.  BTW - you
should call this one 00-preview since it has yet to be accepted by RFC
editor programs and may change slightly due to nits - unless of
course, you got it past the nits.

Some general comments.

Why IEEE-1588 and not NTP as the basis of the clock sync.  They are
very similar, except that NTP does a better job of compensating for
any jitter.  A modification to NTP as payload would yield better
accuracy.  NTP format may have to be modified to make it more hardware
parsible and easier for the low order bits of the time stamp to be
added by the forwarding hardware.

In most cases the precision of even the CF is going to depend on how
much effort has been put into compensating for the outgoing packet.

Ideally the exact time when the start of the currently transmitted
packet could be saved and with that and the byte count of all of the
packets currently in the queue ahead of the IEEE-1588 or NTP packet
would yield precision to roughly a bit time.  In practice though I
doubt that most IEEE-1588 capable hardware can attain this accuracy
and may be accurate only to within one packet time (no way to
determine which byte of the packet is currently being sent and no
saved timestamp on the first byte send time).

A lot of hardware can only provide a count of what is in the queue and
the timestamp.  If the CF is applied by SW without locking the queue
(somehow), then packets can sneak in between the time of reading the
queue occupancy, applying the time stamp, and queueing the PTP PDU.
That would yield worse than one packet time uncertainty on the time
stamping process.

On the receive side, accuracy can be acheived if the hardware saves a
timestamp with the first (or last) bit arrival or at some
deterministic time after first bit arrival (for example, in some NP
handoff to a ME may occur within a narrow window of time relative to
first bit arrival).  If a timestamp is saved by hardware it throws it
out in most cases.  If this is not done by the receive side hardware,
furthern inaccuracy is introduced.

Given that precision is likely to be within one packet time or worse,
the compensation in NTP will yield a better result than the lack of
compensation in IEEE-1588.  Of course that was the "complicated thing"
in NTP that IEEE-1588 was trying to avoid, but it does work well.

Could you remind me how it is signaled on the LSP whether a PW is
underneath, and if so, whether CW is used.  Or are we assuming that if
PW is being used only the PW PE or MS-PW *-PE modify CF?  Of course
with adjacent LSR, there are no mid hops.  Is the offset that is
signaled intended to avoid encapsulation checks?

btw- This seems like requirements only since no signaling is
specified, just the need for signaling in section 12.

Second, it would be best to provide a subsection which enumerates all
of the places that forwarding has to look when processing such an
LSP.  For example:

    1.  Check the LSP range.  If not just forward.

    2.  Check for no BOS and GAL (13) or OAM (14) beneath the label.
	If so just forward.

    3.  If PW and CW is being used:

	  a.  Check for no BOS, then BOS (PW) and CW indicating OAM
	      beneath the label.  If so just forward.

	  b.  Check for no BOS, then BOS (PW) and if so modify CF and
	      forward.

	  c.  Else if BOS (no PW, or GAL) then error.  (?)

	Else

	  a.  Check for BOS.  If so then modify CF and forward.

	  b.  Else (more labels, unexpected) error.  (?)

  Note: modify CF means find IPv4 or IPv6, then UDP then PTP.  Then
  modify any checksums and FCS.

If this is wrong, then I missed something.  Note that this is quite a
bit more than the usual look at label, then forward.

Also, not having looked at IEEE-1588 in quite a while, doesn't just
the sending and recieving node modify CF at around the point of
forwarding?  Please correct me if I'm wrong on that and I'll relook.

Note that neither NTP or IEEE-1588 is highly accurate if there are any
forwarding nodes between the two nodes that are synchronizing clocks.
In that case NTP is considerably less inaccurate.  If the two are
adjacent and the time stamping hardware is in place, in theory,
stamping precision could be to within a bit time, and with
compensation of NTP clock precision could be to within well under a
bit time.

Maybe this sort of comment about expected accuracy would be helpful.

Nits: you have a reference to 1EEE1588 and a reference to [1].  These
seem to be leftovers from the ms-word version.

For completeness it probably wouldn't hurt to specify what the CF
modification is (which bits and what to put in them) without repeating
all of IEEE-1588.  This would be a standalone full specification of
what the hardware needs to do if software then takes over and does the
clock adjustment.

Curtis

From curtis@occnc.com  Tue Jul 20 09:51:12 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC1C63A6B24; Tue, 20 Jul 2010 09:51:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.453
X-Spam-Level: 
X-Spam-Status: No, score=-2.453 tagged_above=-999 required=5 tests=[AWL=0.146,  BAYES_00=-2.599]
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 AnOeq8HzZbuD; Tue, 20 Jul 2010 09:51:11 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id F23F53A68ED; Tue, 20 Jul 2010 09:51:10 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6KGpJ9B063875; Tue, 20 Jul 2010 12:51:19 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007201651.o6KGpJ9B063875@harbor.orleans.occnc.com>
To: John E Drake <jdrake@juniper.net>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 15 Jul 2010 13:26:52 PDT." <5E893DB832F57341992548CDBB3331639844311567@EMBX01-HQ.jnpr.net> 
Date: Tue, 20 Jul 2010 12:51:19 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls] [mpls-tp]  [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 16:51:12 -0000

A section on backwards compatibility with non-compliant LSR would be
helpful.  It might be as simple as a bit of RSVP-TE signaling that
indicates capability and actions to take when a non-compliant LSR is
found in a path.  Normally IEEE-1588 (or very high precision NTP)
would be with adjacent LSR so non-compliance would mean no peering
would be attempted.

Curtis


In message <5E893DB832F57341992548CDBB3331639844311567@EMBX01-HQ.jnpr.net>
John E Drake writes:
>  
> > -----Original Message-----
> > From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On
> > Behalf Of Shahram Davari
> > Sent: Thursday, July 15, 2010 12:52 PM
> > To: Joel M. Halpern
> > Cc: mpls@ietf.org; ticctoc@ietf.org; S. Davari; pwe3@ietf.org; mpls-
> > tp@ietf.org
> > Subject: Re: [mpls-tp] [mpls] [PWE3] 1588 over MPLS draft
> > 
> > Hi Joel,
> > 
> > There are 2 aspects to this puzzle:
> > 
> > 1) Hardware support for 1588 in a device.
> > 2) Software support for 1588 in the form of allocating labels to PTP
> > LSPs
> > 
> > A router that wants to perform 1588 time stamping must have both (1)
> > and (2) functionality. While a router in the path of a PTP LSP that
> > does not support (1) should support (2) and advertise labels from some
> > arbitrary range for PTP LSP.
> > 
> > It is quite easy to upgrade a router software so that when it receives
> > RSVP-TE label request to assign label from an arbitrary local range.
>  
> JD:  What happens in the case where a router's software has not been upgraded?
>  
> > 
> > So I don't see any issue here.
> > 
> > Thanks,
> > Shahram
> > 
> > 
> > 
> > -----Original Message-----
> > From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> > Sent: Thursday, July 15, 2010 12:06 PM
> > To: Shahram Davari
> > Cc: Mach Chen; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org;
> > ticctoc@ietf.org; mpls-tp@ietf.org
> > Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> > 
> > Architecturally, as I understand the draft, the downstream neighbor of
> > a
> > 1588 supporting device (on the PTP carrying LSP) may not itself be a
> > 1588 supporting device.  Is that correct?  If that is not correct, if
> > instead the structure is that PTP supporting LSPs are established
> > between adjacent enhanced devices, then I can see how some sort of a
> > label range might make sense.
> > 
> > If however, the downstream node you refer to may be an existing LSR,
> > then I do not see how you can ask an existing LSR to allocate a label
> > range for a function it does not understand.
> > 
> > Yours,
> > Joel
> > 
> > Shahram Davari wrote:
> > > Hi Joel,
> > >
> > > I agree with your logic, but the idea is a bit different:
> > >
> > > All we need is a label range, it does not need to be globally unique
> > in the network and it does
> >  >not even need to be the same on the Tx and Rx direction of the same
> > link. Although we need time
> >  >stamping both on Rx and on Tx, but on Rx a node is in control of its
> > own label and on Tx the
> >  >downstream node should advertise some label range. What we don't want
> > is that the downstream
> >  >node to advertise random labels for each LSP carrying PTP.
> > >
> > > I will update the draft to mention that the label range does not
> > require to be global but it can
> >  >be per-platform or even per-interface.
> > >
> > > Thanks,
> > > Shahram
> > >
> > > -----Original Message-----
> > > From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> > > Sent: Wednesday, July 14, 2010 8:21 PM
> > > To: Mach Chen
> > > Cc: Shahram Davari; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org;
> > ticctoc@ietf.org; mpls-tp@ietf.org
> > > Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> > >
> > > Remember that if what is required is that the message arriving at the
> > > 1588 supporting device have a certain label range, that is a purely
> > > local matter.  As long as the singaling carries the indication that
> > the
> > > LSP is to be dedicated to 1588 traffic (a reasonable extension to the
> > > signaling), the downstream switch can pick what label to assign to
> > that LSP.
> > >
> > > If the goal is to have the outgoing label be from a specific range,
> > that
> > > is essentially impossible in the proposed architecture.  The proposed
> > > architecture is one in which 1588 switches are peers with existing
> > LSRs
> > > using MPLS.  As such, in order to have a label range for outgoing
> > > labels, the existing MPLS LSR would somehow have to know about this
> > > reserved label range, not use those labels for other purposes, and
> > > assign those labels to 1588 LSPs.  All of which is
> > > non-backwards-compatible.  If the 1588 LSPs were actually
> > pseudowires,
> > > tunneled over LSPs, then any number of things are possible.
> > >
> > > Yours,
> > > Joel M. Halpern
> > >
> > > Mach Chen wrote:
> > >> Hi Shahram,
> > >>
> > >> I agree that the label range idea is an efficient way that could
> > reduce
> > >> the storage requirement of PHY chips.
> > >>
> > >> It's easy to require one or limited nodes to reserve a label range,
> > but
> > >> IMHO, it very difficut to require all nodes of a large network to do
> > >> this and even worse when some labels are already used by other LSPs,
> > >> unless there are some mechanisms to negotiate/advertise(e.g.,
> > flooding
> > >> the label range by IGP within the network) the proper label range
> > hence
> > >> to aviod label collision.
> > >>
> > >> Best regards,
> > >> Mach
> > >>
> > >> --------------------------------------------------
> > >> From: "Shahram Davari" <davari@broadcom.com>
> > >> Sent: Thursday, July 15, 2010 1:58 AM
> > >> To: "Mach Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>;
> > >> "Jia HE" <hejia@huawei.com>
> > >> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>;
> > >> <mpls-tp@ietf.org>
> > >> Subject: RE: [mpls] [PWE3] 1588 over MPLS draft
> > >>
> > >>> Hi Mach,
> > >>>
> > >>> When a service provider wants to create these PTP LSPs, what is
> > wrong
> > >>> with allocating a range of labels for this purpose? This is purely
> > a
> > >>> software exercise. There are 2 million labels available to each
> > node,
> > >>> why can't some of them be allocated by software to PTP?
> > >>>
> > >>> In theory what you say is correct and should work, but in practice
> > >>> there is a function called 1-step Transparent clocking that
> > requires
> > >>> time stamping at the PHY (immediately when the packet is received
> > or
> > >>> transmitted). PHY chips don't have CAM or lots of memory to store a
> > >>> few thousand random labels. The label range will solve that problem
> > >>> and is consistent with MPLS architecture.
> > >>>
> > >>> Thanks,
> > >>> Shahram
> > >>>
> > >>> -----Original Message-----
> > >>> From: Mach Chen [mailto:mach@huawei.com]
> > >>> Sent: Wednesday, July 14, 2010 1:53 AM
> > >>> To: S. Davari; Jia HE; Shahram Davari
> > >>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-
> > tp@ietf.org
> > >>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> > >>>
> > >>> Hi Shahram,
> > >>>
> > >>> From the view of implementation, there is no more difference
> > between
> > >>> SHOULD
> > >>> and MUST :-)
> > >>> For me, the Label Range is more like a mechanim to notify related
> > >>> nodes that
> > >>> some LSPs are dedicated for PTP messages other than the chips
> > memory
> > >>> limitation, because the memory restriction is always there whatever
> > >>> you use
> > >>> Label Range or not.
> > >>> IMHO, since the objective is to tell related MPLS nodes which LSPs
> > are
> > >>> PTP
> > >>> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough
> > and
> > >>> seems
> > >>> more common. And it will avoid the strict requirement of "the
> > network and
> > >>> all nodes required to support the Label range".
> > >>> In addition, there should be some mechanims(e.g., ISIS/OSPF
> > >>> extensions) for
> > >>> nodes to advertise their PTP capability hence to help PTP LSPs
> > >>> computation.
> > >>>
> > >>> Best regards,
> > >>> Mach
> > >>>
> > >>>
> > >>> --------------------------------------------------
> > >>> From: "S. Davari" <davarish@yahoo.com>
> > >>> Sent: Wednesday, July 14, 2010 2:31 PM
> > >>> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari"
> > <davari@broadcom.com>
> > >>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>;
> > >>> <mpls-tp@ietf.org>
> > >>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> > >>>
> > >>>> Hi Jia,
> > >>>>
> > >>>> Label range is a SHOULD requirements and not MUST. The reason for
> > Label
> > >>>> Range is
> > >>>> mainly for PHY chips that don't have large memory and can't store
> > a
> > >>>> lot of
> > >>>> Labels. Otherwise the PTP LSP is setup via signaling that
> > specifies the
> > >>>> LSP as
> > >>>> carrying 1588.
> > >>>>
> > >>>> So the answer is that if a Label range is used it must be a Global
> > range
> > >>>> within
> > >>>> a network and should not be used by any router for other
> > applications.
> > >>>>
> > >>>> Thanks,
> > >>>> Shahram
> > >>>>
> > >>>>
> > >>>>
> > >>>> ________________________________
> > >>>> From: Jia HE <hejia@huawei.com>
> > >>>> To: Shahram Davari <davari@broadcom.com>
> > >>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-
> > tp@ietf.org
> > >>>> Sent: Tue, July 13, 2010 9:50:37 PM
> > >>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> > >>>>
> > >>>>
> > >>>> Hi Shahram,
> > >>>>
> > >>>> One question about "PTP Label Range":
> > >>>>
> > >>>> To my knowledge, label in MPLS network is a local  matter. For
> > >>>> example, we
> > >>>> may
> > >>>> have per-interface or per-platform label space. Will  this
> > specificed
> > >>>> "PTP
> > >>>> Label
> > >>>> Range" conflict with the current in-use labels  for common LSPs?
> > >>>>
> > >>>>
> > >>>> B.R.
> > >>>> Jia
> > >>>>
> > >>>> ----- Original Message -----
> > >>>>> From: Shahram    Davari
> > >>>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ;
> > pwe3@ietf.org
> > >>>>> Sent: Thursday, July 08, 2010 3:12 AM
> > >>>>> Subject: [PWE3] 1588 over MPLS draft
> > >>>>>
> > >>>>>
> > >>>>> Hi All,
> > >>>>>
> > >>>>> Please find attached our first draft of 1588 over MPLS.    Since
> > we
> > >>>>> have
> > >>>>> some
> > >>>>> technical issues converting the Word format to Txt we    couldnâ€™t
> > >>>>> upload
> > >>>>> the
> > >>>>> draft before the cut-off date. However we will    present the
> > draft
> > >>>>> in the
> > >>>>> next
> > >>>>> IETF meeting and will upload the draft after the    meeting.
> > >>>>>
> > >>>>> Note that the main WG is TicToc but may require    consultation
> > with
> > >>>>> MPLS
> > >>>>> and
> > >>>>> PWE3 WGs.
> > >>>>>
> > >>>>> Thanks,
> > >>>>> Shahram Davari

From curtis@occnc.com  Tue Jul 20 10:29:09 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F0873A6992; Tue, 20 Jul 2010 10:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.457
X-Spam-Level: 
X-Spam-Status: No, score=-2.457 tagged_above=-999 required=5 tests=[AWL=0.142,  BAYES_00=-2.599]
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 VGjCxw7cKplJ; Tue, 20 Jul 2010 10:29:07 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id F117F3A693E; Tue, 20 Jul 2010 10:29:06 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6KHTJmM064320; Tue, 20 Jul 2010 13:29:19 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007201729.o6KHTJmM064320@harbor.orleans.occnc.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 15 Jul 2010 22:14:31 BST." <2E480B43-FABD-4D10-A8D4-F950CDEC00CB@niven-jenkins.co.uk> 
Date: Tue, 20 Jul 2010 13:29:19 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls] [mpls-tp]  [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 17:29:09 -0000

LSR today can already run NTP using TC bits set at the priority of
control plane traffic (for CS service that is CS6 - CS7 could be used
for slightly better accuracy), Some may soon have hardware support in
addition to the prioritization (for more than just IEEE-1588).
Providers already run NTP, often among adjacent LSR to get good clock
precision, if for no other reason to be able to correlate logs (or
traps, etc) among devices.

NTP is only inaccurate if you try to peer with some random NTP server
that is far far away.  Among adjacent peers it can be quite accurate
even without hardware support and should be highly accurate with
hardware support.

So it doesn't make much sense to even consider devices that don't
support IEEE-1588 boundary clock.  The goal of this work should be to
*improve* the available accuracy of the clock in LSR.  We should not
use IEEE-1588 over MPLS solely for the sake of the Ethernet religious
even if it makes the clock accuracy worse.

We are talking about more than software change here.  This requires
hardware change.  If we are going to require hardware change we should
specify something which provides the best outcome possible.  That may
be NTP and not IEEE-1588.  For Ethernet devices outside of the LSR
domain that do not support NTP (and may not even support IP or MPLS),
IEEE-1588 can be used.

Curtis


In message <2E480B43-FABD-4D10-A8D4-F950CDEC00CB@niven-jenkins.co.uk>
Ben Niven-Jenkins writes:
>  
> Sharam,
>  
> I am not sure there is a requirement for all devices to be upgraded. My thinking is as follows:
>  
> We have 3 types of 1588 MPLS devices:
> 1) Those that do not support 1588
> 2) Those that can terminate 1588 but do not support boundary clock
> 3) Those that can terminate 1588 and do support boundary clock.
>  
> For the purpose of this discussion (2) & (3) can probably be lumped together.
>  
> The requirement (to avoid more complex hardware processing) is that 1588 packets arrive at device types (2) & (3) with a label out of a "1588 label range". A label from the 1588 label range has no special meaning with respect to forwarding behaviour it simply carries an extra semantic that indicates that the packet is a 1588 packet, such a semantic is only required if the LSP is terminating on device types (2) & (3) or transiting device type (3).
>  
> Therefore the 1588 LSP does not need to use a label from a 1588 specific label range at every hop in the path, it only needs such a label as the incoming label to device types (2) & (3).
>  
> If labels are downstream assigned then the downstream device provides the label mapping for the incoming label for itself and so device types (2) & (3) can assign labels out of their 1588 label range, there is no requirement for the upstream device to realise such a label has an additional semantic and therefore there is no need to upgrade devices except those directly participating in the 1588 session (either as terminating devices or as boundary devices).
>  
> If labels are upstream assigned then the upstream device will need to assign a label from the 1588 label range and so the upstream device, even if it is of type (1), needs to realise it has to assign a label with 1588 semantics. The upstream (as well as downstream) device will require upgrading although context labels may provide some level of support already (I would have to think more about the applicability of context labels to this problem space).
>  
> The key thing to remember is that the semantic that the LSP is a 1588 LSP needs to be carried End to End when signalling the LSP but does not need to exist within the forwarding machinery for each device in the path unless that device is participating in the 1588 session in some way (including upstream allocation of 1588 labels).
>  
> Ben
>  
>  
>  
> On 15 Jul 2010, at 21:37, Shahram Davari wrote:
>  
> > Hi Joel,
> > 
> > OK, do you have a better proposal?
> > 
> > Thx
> > Shahram
> > 
> > -----Original Message-----
> > From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 
> > Sent: Thursday, July 15, 2010 1:32 PM
> > To: Shahram Davari
> > Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> > Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> > 
> > I am sorry, but requiring every LSR in the infrastructure to get a 
> > software upgrade in order to allow for the presence of 1588-supporting 
> > devices is a MAJOR issue.  It is NOT backwards compatible.  Operators 
> > (wether service provider or enterprise IT) do NOT like being told they 
> > ahve to upgrade the software on all devices in their network in order to 
> > add a capability that those devices are not engaging in.
> > 
> > While one can argue about the "ease" of the specific software change, 
> > there is from an operational perspective no such thing as an easy 
> > upgrade of any device, and there is definitely no such thing as an easy 
> > upgrade of all the devices in the network.
> > 
> > Yours,
> > Joel
> > 
> > Shahram Davari wrote:
> >> Hi Joel,
> >> 
> >> There are 2 aspects to this puzzle:
> >> 
> >> 1) Hardware support for 1588 in a device. 
> >> 2) Software support for 1588 in the form of allocating labels to PTP LSPs
> >> 
> >> A router that wants to perform 1588 time stamping must have both (1) and (2) functionality. While a router in 
> >> the path of a PTP LSP that does not support (1) should support (2) and 
> > advertise labels from some arbitrary
> >> range for PTP LSP.
> >> 
> >> It is quite easy to upgrade a router software so that when it receives RSVP-TE label request to assign label 
> >> from an arbitrary local range.
> >> 
> >> So I don't see any issue here.
> >> 
> >> Thanks,
> >> Shahram
> >> 
> >> 
> >> 
> >> -----Original Message-----
> >> From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 
> >> Sent: Thursday, July 15, 2010 12:06 PM
> >> To: Shahram Davari
> >> Cc: Mach Chen; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> >> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> >> 
> >> Architecturally, as I understand the draft, the downstream neighbor of a 
> >> 1588 supporting device (on the PTP carrying LSP) may not itself be a 
> >> 1588 supporting device.  Is that correct?  If that is not correct, if 
> >> instead the structure is that PTP supporting LSPs are established 
> >> between adjacent enhanced devices, then I can see how some sort of a 
> >> label range might make sense.
> >> 
> >> If however, the downstream node you refer to may be an existing LSR, 
> >> then I do not see how you can ask an existing LSR to allocate a label 
> >> range for a function it does not understand.
> >> 
> >> Yours,
> >> Joel
> >> 
> >> Shahram Davari wrote:
> >>> Hi Joel,
> >>> 
> >>> I agree with your logic, but the idea is a bit different:
> >>> 
> >>> All we need is a label range, it does not need to be globally unique in the network and it does
> >>> not even need to be the same on the Tx and Rx direction of the same 
> >> link. Although we need time
> >>> stamping both on Rx and on Tx, but on Rx a node is in control of its 
> >> own label and on Tx the
> >>> downstream node should advertise some label range. What we don't want 
> >> is that the downstream
> >>> node to advertise random labels for each LSP carrying PTP.
> >>> I will update the draft to mention that the label range does not require to be global but it can
> >>> be per-platform or even per-interface.
> >>> Thanks,
> >>> Shahram
> >>> 
> >>> -----Original Message-----
> >>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 
> >>> Sent: Wednesday, July 14, 2010 8:21 PM
> >>> To: Mach Chen
> >>> Cc: Shahram Davari; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> >>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> >>> 
> >>> Remember that if what is required is that the message arriving at the 
> >>> 1588 supporting device have a certain label range, that is a purely 
> >>> local matter.  As long as the singaling carries the indication that the 
> >>> LSP is to be dedicated to 1588 traffic (a reasonable extension to the 
> >>> signaling), the downstream switch can pick what label to assign to that LSP.
> >>> 
> >>> If the goal is to have the outgoing label be from a specific range, that 
> >>> is essentially impossible in the proposed architecture.  The proposed 
> >>> architecture is one in which 1588 switches are peers with existing LSRs 
> >>> using MPLS.  As such, in order to have a label range for outgoing 
> >>> labels, the existing MPLS LSR would somehow have to know about this 
> >>> reserved label range, not use those labels for other purposes, and 
> >>> assign those labels to 1588 LSPs.  All of which is 
> >>> non-backwards-compatible.  If the 1588 LSPs were actually pseudowires, 
> >>> tunneled over LSPs, then any number of things are possible.
> >>> 
> >>> Yours,
> >>> Joel M. Halpern
> >>> 
> >>> Mach Chen wrote:
> >>>> Hi Shahram,
> >>>> 
> >>>> I agree that the label range idea is an efficient way that could reduce 
> >>>> the storage requirement of PHY chips.
> >>>> 
> >>>> It's easy to require one or limited nodes to reserve a label range, but 
> >>>> IMHO, it very difficut to require all nodes of a large network to do 
> >>>> this and even worse when some labels are already used by other LSPs, 
> >>>> unless there are some mechanisms to negotiate/advertise(e.g., flooding 
> >>>> the label range by IGP within the network) the proper label range hence 
> >>>> to aviod label collision.
> >>>> 
> >>>> Best regards,
> >>>> Mach
> >>>> 
> >>>> --------------------------------------------------
> >>>> From: "Shahram Davari" <davari@broadcom.com>
> >>>> Sent: Thursday, July 15, 2010 1:58 AM
> >>>> To: "Mach Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>; 
> >>>> "Jia HE" <hejia@huawei.com>
> >>>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
> >>>> <mpls-tp@ietf.org>
> >>>> Subject: RE: [mpls] [PWE3] 1588 over MPLS draft
> >>>> 
> >>>>> Hi Mach,
> >>>>> 
> >>>>> When a service provider wants to create these PTP LSPs, what is wrong 
> >>>>> with allocating a range of labels for this purpose? This is purely a 
> >>>>> software exercise. There are 2 million labels available to each node, 
> >>>>> why can't some of them be allocated by software to PTP?
> >>>>> 
> >>>>> In theory what you say is correct and should work, but in practice 
> >>>>> there is a function called 1-step Transparent clocking that requires 
> >>>>> time stamping at the PHY (immediately when the packet is received or 
> >>>>> transmitted). PHY chips don't have CAM or lots of memory to store a 
> >>>>> few thousand random labels. The label range will solve that problem 
> >>>>> and is consistent with MPLS architecture.
> >>>>> 
> >>>>> Thanks,
> >>>>> Shahram
> >>>>> 
> >>>>> -----Original Message-----
> >>>>> From: Mach Chen [mailto:mach@huawei.com]
> >>>>> Sent: Wednesday, July 14, 2010 1:53 AM
> >>>>> To: S. Davari; Jia HE; Shahram Davari
> >>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> >>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> >>>>> 
> >>>>> Hi Shahram,
> >>>>> 
> >>>>> From the view of implementation, there is no more difference between 
> >>>>> SHOULD
> >>>>> and MUST :-)
> >>>>> For me, the Label Range is more like a mechanim to notify related 
> >>>>> nodes that
> >>>>> some LSPs are dedicated for PTP messages other than the chips memory
> >>>>> limitation, because the memory restriction is always there whatever 
> >>>>> you use
> >>>>> Label Range or not.
> >>>>> IMHO, since the objective is to tell related MPLS nodes which LSPs are 
> >>>>> PTP
> >>>>> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and 
> >>>>> seems
> >>>>> more common. And it will avoid the strict requirement of "the network and
> >>>>> all nodes required to support the Label range".
> >>>>> In addition, there should be some mechanims(e.g., ISIS/OSPF 
> >>>>> extensions) for
> >>>>> nodes to advertise their PTP capability hence to help PTP LSPs 
> >>>>> computation.
> >>>>> 
> >>>>> Best regards,
> >>>>> Mach
> >>>>> 
> >>>>> 
> >>>>> --------------------------------------------------
> >>>>> From: "S. Davari" <davarish@yahoo.com>
> >>>>> Sent: Wednesday, July 14, 2010 2:31 PM
> >>>>> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" <davari@broadcom.com>
> >>>>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
> >>>>> <mpls-tp@ietf.org>
> >>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> >>>>> 
> >>>>>> Hi Jia,
> >>>>>> 
> >>>>>> Label range is a SHOULD requirements and not MUST. The reason for Label
> >>>>>> Range is
> >>>>>> mainly for PHY chips that don't have large memory and can't store a 
> >>>>>> lot of
> >>>>>> Labels. Otherwise the PTP LSP is setup via signaling that specifies the
> >>>>>> LSP as
> >>>>>> carrying 1588.
> >>>>>> 
> >>>>>> So the answer is that if a Label range is used it must be a Global range
> >>>>>> within
> >>>>>> a network and should not be used by any router for other applications.
> >>>>>> 
> >>>>>> Thanks,
> >>>>>> Shahram
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>>> ________________________________
> >>>>>> From: Jia HE <hejia@huawei.com>
> >>>>>> To: Shahram Davari <davari@broadcom.com>
> >>>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
> >>>>>> Sent: Tue, July 13, 2010 9:50:37 PM
> >>>>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
> >>>>>> 
> >>>>>> 
> >>>>>> Hi Shahram,
> >>>>>> 
> >>>>>> One question about "PTP Label Range":
> >>>>>> 
> >>>>>> To my knowledge, label in MPLS network is a local  matter. For 
> >>>>>> example, we
> >>>>>> may
> >>>>>> have per-interface or per-platform label space. Will  this specificed 
> >>>>>> "PTP
> >>>>>> Label
> >>>>>> Range" conflict with the current in-use labels  for common LSPs?
> >>>>>> 
> >>>>>> 
> >>>>>> B.R.
> >>>>>> Jia
> >>>>>> 
> >>>>>> ----- Original Message -----
> >>>>>>> From: Shahram    Davari
> >>>>>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org
> >>>>>>> Sent: Thursday, July 08, 2010 3:12 AM
> >>>>>>> Subject: [PWE3] 1588 over MPLS draft
> >>>>>>> 
> >>>>>>> 
> >>>>>>> Hi All,
> >>>>>>> 
> >>>>>>> Please find attached our first draft of 1588 over MPLS.    Since we 
> >>>>>>> have
> >>>>>>> some
> >>>>>>> technical issues converting the Word format to Txt we    couldn’t 
> >>>>>>> upload
> >>>>>>> the
> >>>>>>> draft before the cut-off date. However we will    present the draft 
> >>>>>>> in the
> >>>>>>> next
> >>>>>>> IETF meeting and will upload the draft after the    meeting.
> >>>>>>> 
> >>>>>>> Note that the main WG is TicToc but may require    consultation with 
> >>>>>>> MPLS
> >>>>>>> and
> >>>>>>> PWE3 WGs.
> >>>>>>> 
> >>>>>>> Thanks,
> >>>>>>> Shahram Davari

From curtis@occnc.com  Tue Jul 20 11:07:13 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE4DF3A6B3E; Tue, 20 Jul 2010 11:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.461
X-Spam-Level: 
X-Spam-Status: No, score=-2.461 tagged_above=-999 required=5 tests=[AWL=0.138,  BAYES_00=-2.599]
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 2FHnOYExY+67; Tue, 20 Jul 2010 11:07:12 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id A15A73A6B32; Tue, 20 Jul 2010 11:07:11 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6KI7Dvb064816; Tue, 20 Jul 2010 14:07:14 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007201807.o6KI7Dvb064816@harbor.orleans.occnc.com>
To: "Shahram Davari" <davari@broadcom.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 15 Jul 2010 10:46:22 PDT." <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com>
Date: Tue, 20 Jul 2010 14:07:13 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3]  1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 18:07:13 -0000

Is there really an issue at all?  If an LSR is tictoc capable, it
provides the upstream with a label in that range.  That is the way
RSVP-TE works.  At forwarding time that is the label that will be used
at that hop.  If an LSR is not tictoc capable, then it provides any
label it choses and it sees that label but it wouldn't have done
anything different no matter what label it picked.

It is still highly questionable whether there is any utility in
running over a LSP with a midpoint LSR in the path.  For high clock
accuracy, either NTP or IEEE-1588 have to be run among adjacent LSR
only.

BTW- If one hop IP is available for the control plane, the use of NTP
over IP is a good practical choice and I would be very surprised if it
were not the most common choice today among LSR.

It might be easier for the tictoc group to simply specify that the NTP
timestamping should be supported in hardware.

Curtis


In message <2C2F1EBA8050E74EA81502D5740B4BD6940EC290F5@SJEXCHCCR02.corp.ad.broadcom.com>
"Shahram Davari" writes:

Hi Joel,

I agree with your logic, but the idea is a bit different:

All we need is a label range, it does not need to be globally unique in the network and it does not even need to be the same on the Tx and Rx direction of the same link. Although we need time stamping both on Rx and on Tx, but on Rx a node is in control of its own label and on Tx the downstream node should advertise some label range. What we don't want is that the downstream node to advertise random labels for each LSP carrying PTP.

I will update the draft to mention that the label range does not require to be global but it can be per-platform or even per-interface.

Thanks,
Shahram

-----Original Message-----
From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 
Sent: Wednesday, July 14, 2010 8:21 PM
To: Mach Chen
Cc: Shahram Davari; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft

Remember that if what is required is that the message arriving at the 
1588 supporting device have a certain label range, that is a purely 
local matter.  As long as the singaling carries the indication that the 
LSP is to be dedicated to 1588 traffic (a reasonable extension to the 
signaling), the downstream switch can pick what label to assign to that LSP.

If the goal is to have the outgoing label be from a specific range, that 
is essentially impossible in the proposed architecture.  The proposed 
architecture is one in which 1588 switches are peers with existing LSRs 
using MPLS.  As such, in order to have a label range for outgoing 
labels, the existing MPLS LSR would somehow have to know about this 
reserved label range, not use those labels for other purposes, and 
assign those labels to 1588 LSPs.  All of which is 
non-backwards-compatible.  If the 1588 LSPs were actually pseudowires, 
tunneled over LSPs, then any number of things are possible.

Yours,
Joel M. Halpern

Mach Chen wrote:
> Hi Shahram,
> 
> I agree that the label range idea is an efficient way that could reduce 
> the storage requirement of PHY chips.
> 
> It's easy to require one or limited nodes to reserve a label range, but 
> IMHO, it very difficut to require all nodes of a large network to do 
> this and even worse when some labels are already used by other LSPs, 
> unless there are some mechanisms to negotiate/advertise(e.g., flooding 
> the label range by IGP within the network) the proper label range hence 
> to aviod label collision.
> 
> Best regards,
> Mach
> 
> --------------------------------------------------
> From: "Shahram Davari" <davari@broadcom.com>
> Sent: Thursday, July 15, 2010 1:58 AM
> To: "Mach Chen" <mach@huawei.com>; "S. Davari" <davarish@yahoo.com>; 
> "Jia HE" <hejia@huawei.com>
> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
> <mpls-tp@ietf.org>
> Subject: RE: [mpls] [PWE3] 1588 over MPLS draft
> 
>> Hi Mach,
>>
>> When a service provider wants to create these PTP LSPs, what is wrong 
>> with allocating a range of labels for this purpose? This is purely a 
>> software exercise. There are 2 million labels available to each node, 
>> why can't some of them be allocated by software to PTP?
>>
>> In theory what you say is correct and should work, but in practice 
>> there is a function called 1-step Transparent clocking that requires 
>> time stamping at the PHY (immediately when the packet is received or 
>> transmitted). PHY chips don't have CAM or lots of memory to store a 
>> few thousand random labels. The label range will solve that problem 
>> and is consistent with MPLS architecture.
>>
>> Thanks,
>> Shahram
>>
>> -----Original Message-----
>> From: Mach Chen [mailto:mach@huawei.com]
>> Sent: Wednesday, July 14, 2010 1:53 AM
>> To: S. Davari; Jia HE; Shahram Davari
>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>
>> Hi Shahram,
>>
>> From the view of implementation, there is no more difference between 
>> SHOULD
>> and MUST :-)
>> For me, the Label Range is more like a mechanim to notify related 
>> nodes that
>> some LSPs are dedicated for PTP messages other than the chips memory
>> limitation, because the memory restriction is always there whatever 
>> you use
>> Label Range or not.
>> IMHO, since the objective is to tell related MPLS nodes which LSPs are 
>> PTP
>> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and 
>> seems
>> more common. And it will avoid the strict requirement of "the network and
>> all nodes required to support the Label range".
>> In addition, there should be some mechanims(e.g., ISIS/OSPF 
>> extensions) for
>> nodes to advertise their PTP capability hence to help PTP LSPs 
>> computation.
>>
>> Best regards,
>> Mach
>>
>>
>> --------------------------------------------------
>> From: "S. Davari" <davarish@yahoo.com>
>> Sent: Wednesday, July 14, 2010 2:31 PM
>> To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" <davari@broadcom.com>
>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; 
>> <mpls-tp@ietf.org>
>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>
>>> Hi Jia,
>>>
>>> Label range is a SHOULD requirements and not MUST. The reason for Label
>>> Range is
>>> mainly for PHY chips that don't have large memory and can't store a 
>>> lot of
>>> Labels. Otherwise the PTP LSP is setup via signaling that specifies the
>>> LSP as
>>> carrying 1588.
>>>
>>> So the answer is that if a Label range is used it must be a Global range
>>> within
>>> a network and should not be used by any router for other applications.
>>>
>>> Thanks,
>>> Shahram
>>>
>>>
>>>
>>> ________________________________
>>> From: Jia HE <hejia@huawei.com>
>>> To: Shahram Davari <davari@broadcom.com>
>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
>>> Sent: Tue, July 13, 2010 9:50:37 PM
>>> Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
>>>
>>>
>>> Hi Shahram,
>>>
>>> One question about "PTP Label Range":
>>>
>>> To my knowledge, label in MPLS network is a local  matter. For 
>>> example, we
>>> may
>>> have per-interface or per-platform label space. Will  this specificed 
>>> "PTP
>>> Label
>>> Range" conflict with the current in-use labels  for common LSPs?
>>>
>>>
>>> B.R.
>>> Jia
>>>
>>> ----- Original Message -----
>>>> From: Shahram    Davari
>>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org
>>>> Sent: Thursday, July 08, 2010 3:12 AM
>>>> Subject: [PWE3] 1588 over MPLS draft
>>>>
>>>>
>>>> Hi All,
>>>>
>>>> Please find attached our first draft of 1588 over MPLS.    Since we 
>>>> have
>>>> some
>>>> technical issues converting the Word format to Txt we    couldnâ€™t 
>>>> upload
>>>> the
>>>> draft before the cut-off date. However we will    present the draft 
>>>> in the
>>>> next
>>>> IETF meeting and will upload the draft after the    meeting.
>>>>
>>>> Note that the main WG is TicToc but may require    consultation with 
>>>> MPLS
>>>> and
>>>> PWE3 WGs.
>>>>
>>>> Thanks,
>>>> Shahram Davari
>>> ________________________________
>>> _______________________________________________
>>>> pwe3 mailing    list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>>
>>>
>>>
>>
>>
>>
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>>>
>>
>>
>>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

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



From davari@broadcom.com  Tue Jul 20 11:17:08 2010
Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29F193A6B47; Tue, 20 Jul 2010 11:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level: 
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599]
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 EZM16UGXhEtx; Tue, 20 Jul 2010 11:17:06 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id 35A743A687D; Tue, 20 Jul 2010 11:17:04 -0700 (PDT)
Received: from [10.16.192.232] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Tue, 20 Jul 2010 11:17:08 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Tue, 20 Jul 2010 11:17:08 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "'curtis@occnc.com'" <curtis@occnc.com>
Date: Tue, 20 Jul 2010 11:17:06 -0700
Thread-Topic: [PWE3] [mpls] 1588 over MPLS draft
Thread-Index: AcsoNnYocqg1OBbPQ56imTU5r7mg6QAAUwVq
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6940E9CF65C@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 605B37AE3KC45299152-01-01
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: "'mpls@ietf.org'" <mpls@ietf.org>, "'ticctoc@ietf.org'" <ticctoc@ietf.org>, "'mpls-tp@ietf.org'" <mpls-tp@ietf.org>, "'pwe3@ietf.org'" <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3]  1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 18:17:08 -0000

Q29ycmVjdCB0aGVyZSBpcyBubyBpc3N1ZSBhbmQgZWFjaCBMU1IgaXMgaW4gY29udHJvbCBvZiBp
dHMgbGFiZWxzDQoNClRIWA0KU0QNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KRnJv
bTogY3VydGlzQG9jY25jLmNvbSA8Y3VydGlzQG9jY25jLmNvbT4NClRvOiBTaGFocmFtIERhdmFy
aQ0KQ2M6IEpvZWwgTS4gSGFscGVybiA8am1oQGpvZWxoYWxwZXJuLmNvbT47IE1hY2ggQ2hlbiA8
bWFjaEBodWF3ZWkuY29tPjsgbXBsc0BpZXRmLm9yZyA8bXBsc0BpZXRmLm9yZz47IHRpY2N0b2NA
aWV0Zi5vcmcgPHRpY2N0b2NAaWV0Zi5vcmc+OyBtcGxzLXRwQGlldGYub3JnIDxtcGxzLXRwQGll
dGYub3JnPjsgcHdlM0BpZXRmLm9yZyA8cHdlM0BpZXRmLm9yZz47IFMuIERhdmFyaSA8ZGF2YXJp
c2hAeWFob28uY29tPg0KU2VudDogVHVlIEp1bCAyMCAxMTowNzoxMyAyMDEwClN1YmplY3Q6IFJl
OiBbUFdFM10gW21wbHNdIDE1ODggb3ZlciBNUExTIGRyYWZ0DQoNCg0KSXMgdGhlcmUgcmVhbGx5
IGFuIGlzc3VlIGF0IGFsbD8gIElmIGFuIExTUiBpcyB0aWN0b2MgY2FwYWJsZSwgaXQNCnByb3Zp
ZGVzIHRoZSB1cHN0cmVhbSB3aXRoIGEgbGFiZWwgaW4gdGhhdCByYW5nZS4gIFRoYXQgaXMgdGhl
IHdheQ0KUlNWUC1URSB3b3Jrcy4gIEF0IGZvcndhcmRpbmcgdGltZSB0aGF0IGlzIHRoZSBsYWJl
bCB0aGF0IHdpbGwgYmUgdXNlZA0KYXQgdGhhdCBob3AuICBJZiBhbiBMU1IgaXMgbm90IHRpY3Rv
YyBjYXBhYmxlLCB0aGVuIGl0IHByb3ZpZGVzIGFueQ0KbGFiZWwgaXQgY2hvc2VzIGFuZCBpdCBz
ZWVzIHRoYXQgbGFiZWwgYnV0IGl0IHdvdWxkbid0IGhhdmUgZG9uZQ0KYW55dGhpbmcgZGlmZmVy
ZW50IG5vIG1hdHRlciB3aGF0IGxhYmVsIGl0IHBpY2tlZC4NCg0KSXQgaXMgc3RpbGwgaGlnaGx5
IHF1ZXN0aW9uYWJsZSB3aGV0aGVyIHRoZXJlIGlzIGFueSB1dGlsaXR5IGluDQpydW5uaW5nIG92
ZXIgYSBMU1Agd2l0aCBhIG1pZHBvaW50IExTUiBpbiB0aGUgcGF0aC4gIEZvciBoaWdoIGNsb2Nr
DQphY2N1cmFjeSwgZWl0aGVyIE5UUCBvciBJRUVFLTE1ODggaGF2ZSB0byBiZSBydW4gYW1vbmcg
YWRqYWNlbnQgTFNSDQpvbmx5Lg0KDQpCVFctIElmIG9uZSBob3AgSVAgaXMgYXZhaWxhYmxlIGZv
ciB0aGUgY29udHJvbCBwbGFuZSwgdGhlIHVzZSBvZiBOVFANCm92ZXIgSVAgaXMgYSBnb29kIHBy
YWN0aWNhbCBjaG9pY2UgYW5kIEkgd291bGQgYmUgdmVyeSBzdXJwcmlzZWQgaWYgaXQNCndlcmUg
bm90IHRoZSBtb3N0IGNvbW1vbiBjaG9pY2UgdG9kYXkgYW1vbmcgTFNSLg0KDQpJdCBtaWdodCBi
ZSBlYXNpZXIgZm9yIHRoZSB0aWN0b2MgZ3JvdXAgdG8gc2ltcGx5IHNwZWNpZnkgdGhhdCB0aGUg
TlRQDQp0aW1lc3RhbXBpbmcgc2hvdWxkIGJlIHN1cHBvcnRlZCBpbiBoYXJkd2FyZS4NCg0KQ3Vy
dGlzDQoNCg0KSW4gbWVzc2FnZSA8MkMyRjFFQkE4MDUwRTc0RUE4MTUwMkQ1NzQwQjRCRDY5NDBF
QzI5MEY1QFNKRVhDSENDUjAyLmNvcnAuYWQuYnJvYWRjb20uY29tPg0KIlNoYWhyYW0gRGF2YXJp
IiB3cml0ZXM6DQoNCkhpIEpvZWwsDQoNCkkgYWdyZWUgd2l0aCB5b3VyIGxvZ2ljLCBidXQgdGhl
IGlkZWEgaXMgYSBiaXQgZGlmZmVyZW50Og0KDQpBbGwgd2UgbmVlZCBpcyBhIGxhYmVsIHJhbmdl
LCBpdCBkb2VzIG5vdCBuZWVkIHRvIGJlIGdsb2JhbGx5IHVuaXF1ZSBpbiB0aGUgbmV0d29yayBh
bmQgaXQgZG9lcyBub3QgZXZlbiBuZWVkIHRvIGJlIHRoZSBzYW1lIG9uIHRoZSBUeCBhbmQgUngg
ZGlyZWN0aW9uIG9mIHRoZSBzYW1lIGxpbmsuIEFsdGhvdWdoIHdlIG5lZWQgdGltZSBzdGFtcGlu
ZyBib3RoIG9uIFJ4IGFuZCBvbiBUeCwgYnV0IG9uIFJ4IGEgbm9kZSBpcyBpbiBjb250cm9sIG9m
IGl0cyBvd24gbGFiZWwgYW5kIG9uIFR4IHRoZSBkb3duc3RyZWFtIG5vZGUgc2hvdWxkIGFkdmVy
dGlzZSBzb21lIGxhYmVsIHJhbmdlLiBXaGF0IHdlIGRvbid0IHdhbnQgaXMgdGhhdCB0aGUgZG93
bnN0cmVhbSBub2RlIHRvIGFkdmVydGlzZSByYW5kb20gbGFiZWxzIGZvciBlYWNoIExTUCBjYXJy
eWluZyBQVFAuDQoNCkkgd2lsbCB1cGRhdGUgdGhlIGRyYWZ0IHRvIG1lbnRpb24gdGhhdCB0aGUg
bGFiZWwgcmFuZ2UgZG9lcyBub3QgcmVxdWlyZSB0byBiZSBnbG9iYWwgYnV0IGl0IGNhbiBiZSBw
ZXItcGxhdGZvcm0gb3IgZXZlbiBwZXItaW50ZXJmYWNlLg0KDQpUaGFua3MsDQpTaGFocmFtDQoN
Ci0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBKb2VsIE0uIEhhbHBlcm4gW21haWx0
bzpqbWhAam9lbGhhbHBlcm4uY29tXSANClNlbnQ6IFdlZG5lc2RheSwgSnVseSAxNCwgMjAxMCA4
OjIxIFBNDQpUbzogTWFjaCBDaGVuDQpDYzogU2hhaHJhbSBEYXZhcmk7IFMuIERhdmFyaTsgSmlh
IEhFOyBtcGxzQGlldGYub3JnOyBwd2UzQGlldGYub3JnOyB0aWNjdG9jQGlldGYub3JnOyBtcGxz
LXRwQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBk
cmFmdA0KDQpSZW1lbWJlciB0aGF0IGlmIHdoYXQgaXMgcmVxdWlyZWQgaXMgdGhhdCB0aGUgbWVz
c2FnZSBhcnJpdmluZyBhdCB0aGUgDQoxNTg4IHN1cHBvcnRpbmcgZGV2aWNlIGhhdmUgYSBjZXJ0
YWluIGxhYmVsIHJhbmdlLCB0aGF0IGlzIGEgcHVyZWx5IA0KbG9jYWwgbWF0dGVyLiAgQXMgbG9u
ZyBhcyB0aGUgc2luZ2FsaW5nIGNhcnJpZXMgdGhlIGluZGljYXRpb24gdGhhdCB0aGUgDQpMU1Ag
aXMgdG8gYmUgZGVkaWNhdGVkIHRvIDE1ODggdHJhZmZpYyAoYSByZWFzb25hYmxlIGV4dGVuc2lv
biB0byB0aGUgDQpzaWduYWxpbmcpLCB0aGUgZG93bnN0cmVhbSBzd2l0Y2ggY2FuIHBpY2sgd2hh
dCBsYWJlbCB0byBhc3NpZ24gdG8gdGhhdCBMU1AuDQoNCklmIHRoZSBnb2FsIGlzIHRvIGhhdmUg
dGhlIG91dGdvaW5nIGxhYmVsIGJlIGZyb20gYSBzcGVjaWZpYyByYW5nZSwgdGhhdCANCmlzIGVz
c2VudGlhbGx5IGltcG9zc2libGUgaW4gdGhlIHByb3Bvc2VkIGFyY2hpdGVjdHVyZS4gIFRoZSBw
cm9wb3NlZCANCmFyY2hpdGVjdHVyZSBpcyBvbmUgaW4gd2hpY2ggMTU4OCBzd2l0Y2hlcyBhcmUg
cGVlcnMgd2l0aCBleGlzdGluZyBMU1JzIA0KdXNpbmcgTVBMUy4gIEFzIHN1Y2gsIGluIG9yZGVy
IHRvIGhhdmUgYSBsYWJlbCByYW5nZSBmb3Igb3V0Z29pbmcgDQpsYWJlbHMsIHRoZSBleGlzdGlu
ZyBNUExTIExTUiB3b3VsZCBzb21laG93IGhhdmUgdG8ga25vdyBhYm91dCB0aGlzIA0KcmVzZXJ2
ZWQgbGFiZWwgcmFuZ2UsIG5vdCB1c2UgdGhvc2UgbGFiZWxzIGZvciBvdGhlciBwdXJwb3Nlcywg
YW5kIA0KYXNzaWduIHRob3NlIGxhYmVscyB0byAxNTg4IExTUHMuICBBbGwgb2Ygd2hpY2ggaXMg
DQpub24tYmFja3dhcmRzLWNvbXBhdGlibGUuICBJZiB0aGUgMTU4OCBMU1BzIHdlcmUgYWN0dWFs
bHkgcHNldWRvd2lyZXMsIA0KdHVubmVsZWQgb3ZlciBMU1BzLCB0aGVuIGFueSBudW1iZXIgb2Yg
dGhpbmdzIGFyZSBwb3NzaWJsZS4NCg0KWW91cnMsDQpKb2VsIE0uIEhhbHBlcm4NCg0KTWFjaCBD
aGVuIHdyb3RlOg0KPiBIaSBTaGFocmFtLA0KPiANCj4gSSBhZ3JlZSB0aGF0IHRoZSBsYWJlbCBy
YW5nZSBpZGVhIGlzIGFuIGVmZmljaWVudCB3YXkgdGhhdCBjb3VsZCByZWR1Y2UgDQo+IHRoZSBz
dG9yYWdlIHJlcXVpcmVtZW50IG9mIFBIWSBjaGlwcy4NCj4gDQo+IEl0J3MgZWFzeSB0byByZXF1
aXJlIG9uZSBvciBsaW1pdGVkIG5vZGVzIHRvIHJlc2VydmUgYSBsYWJlbCByYW5nZSwgYnV0IA0K
PiBJTUhPLCBpdCB2ZXJ5IGRpZmZpY3V0IHRvIHJlcXVpcmUgYWxsIG5vZGVzIG9mIGEgbGFyZ2Ug
bmV0d29yayB0byBkbyANCj4gdGhpcyBhbmQgZXZlbiB3b3JzZSB3aGVuIHNvbWUgbGFiZWxzIGFy
ZSBhbHJlYWR5IHVzZWQgYnkgb3RoZXIgTFNQcywgDQo+IHVubGVzcyB0aGVyZSBhcmUgc29tZSBt
ZWNoYW5pc21zIHRvIG5lZ290aWF0ZS9hZHZlcnRpc2UoZS5nLiwgZmxvb2RpbmcgDQo+IHRoZSBs
YWJlbCByYW5nZSBieSBJR1Agd2l0aGluIHRoZSBuZXR3b3JrKSB0aGUgcHJvcGVyIGxhYmVsIHJh
bmdlIGhlbmNlIA0KPiB0byBhdmlvZCBsYWJlbCBjb2xsaXNpb24uDQo+IA0KPiBCZXN0IHJlZ2Fy
ZHMsDQo+IE1hY2gNCj4gDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQo+IEZyb206ICJTaGFocmFtIERhdmFyaSIgPGRhdmFyaUBicm9hZGNvbS5j
b20+DQo+IFNlbnQ6IFRodXJzZGF5LCBKdWx5IDE1LCAyMDEwIDE6NTggQU0NCj4gVG86ICJNYWNo
IENoZW4iIDxtYWNoQGh1YXdlaS5jb20+OyAiUy4gRGF2YXJpIiA8ZGF2YXJpc2hAeWFob28uY29t
PjsgDQo+ICJKaWEgSEUiIDxoZWppYUBodWF3ZWkuY29tPg0KPiBDYzogPG1wbHNAaWV0Zi5vcmc+
OyA8cHdlM0BpZXRmLm9yZz47IDx0aWNjdG9jQGlldGYub3JnPjsgDQo+IDxtcGxzLXRwQGlldGYu
b3JnPg0KPiBTdWJqZWN0OiBSRTogW21wbHNdIFtQV0UzXSAxNTg4IG92ZXIgTVBMUyBkcmFmdA0K
PiANCj4+IEhpIE1hY2gsDQo+Pg0KPj4gV2hlbiBhIHNlcnZpY2UgcHJvdmlkZXIgd2FudHMgdG8g
Y3JlYXRlIHRoZXNlIFBUUCBMU1BzLCB3aGF0IGlzIHdyb25nIA0KPj4gd2l0aCBhbGxvY2F0aW5n
IGEgcmFuZ2Ugb2YgbGFiZWxzIGZvciB0aGlzIHB1cnBvc2U/IFRoaXMgaXMgcHVyZWx5IGEgDQo+
PiBzb2Z0d2FyZSBleGVyY2lzZS4gVGhlcmUgYXJlIDIgbWlsbGlvbiBsYWJlbHMgYXZhaWxhYmxl
IHRvIGVhY2ggbm9kZSwgDQo+PiB3aHkgY2FuJ3Qgc29tZSBvZiB0aGVtIGJlIGFsbG9jYXRlZCBi
eSBzb2Z0d2FyZSB0byBQVFA/DQo+Pg0KPj4gSW4gdGhlb3J5IHdoYXQgeW91IHNheSBpcyBjb3Jy
ZWN0IGFuZCBzaG91bGQgd29yaywgYnV0IGluIHByYWN0aWNlIA0KPj4gdGhlcmUgaXMgYSBmdW5j
dGlvbiBjYWxsZWQgMS1zdGVwIFRyYW5zcGFyZW50IGNsb2NraW5nIHRoYXQgcmVxdWlyZXMgDQo+
PiB0aW1lIHN0YW1waW5nIGF0IHRoZSBQSFkgKGltbWVkaWF0ZWx5IHdoZW4gdGhlIHBhY2tldCBp
cyByZWNlaXZlZCBvciANCj4+IHRyYW5zbWl0dGVkKS4gUEhZIGNoaXBzIGRvbid0IGhhdmUgQ0FN
IG9yIGxvdHMgb2YgbWVtb3J5IHRvIHN0b3JlIGEgDQo+PiBmZXcgdGhvdXNhbmQgcmFuZG9tIGxh
YmVscy4gVGhlIGxhYmVsIHJhbmdlIHdpbGwgc29sdmUgdGhhdCBwcm9ibGVtIA0KPj4gYW5kIGlz
IGNvbnNpc3RlbnQgd2l0aCBNUExTIGFyY2hpdGVjdHVyZS4NCj4+DQo+PiBUaGFua3MsDQo+PiBT
aGFocmFtDQo+Pg0KPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+IEZyb206IE1hY2gg
Q2hlbiBbbWFpbHRvOm1hY2hAaHVhd2VpLmNvbV0NCj4+IFNlbnQ6IFdlZG5lc2RheSwgSnVseSAx
NCwgMjAxMCAxOjUzIEFNDQo+PiBUbzogUy4gRGF2YXJpOyBKaWEgSEU7IFNoYWhyYW0gRGF2YXJp
DQo+PiBDYzogbXBsc0BpZXRmLm9yZzsgcHdlM0BpZXRmLm9yZzsgdGljY3RvY0BpZXRmLm9yZzsg
bXBscy10cEBpZXRmLm9yZw0KPj4gU3ViamVjdDogUmU6IFttcGxzXSBbUFdFM10gMTU4OCBvdmVy
IE1QTFMgZHJhZnQNCj4+DQo+PiBIaSBTaGFocmFtLA0KPj4NCj4+IEZyb20gdGhlIHZpZXcgb2Yg
aW1wbGVtZW50YXRpb24sIHRoZXJlIGlzIG5vIG1vcmUgZGlmZmVyZW5jZSBiZXR3ZWVuIA0KPj4g
U0hPVUxEDQo+PiBhbmQgTVVTVCA6LSkNCj4+IEZvciBtZSwgdGhlIExhYmVsIFJhbmdlIGlzIG1v
cmUgbGlrZSBhIG1lY2hhbmltIHRvIG5vdGlmeSByZWxhdGVkIA0KPj4gbm9kZXMgdGhhdA0KPj4g
c29tZSBMU1BzIGFyZSBkZWRpY2F0ZWQgZm9yIFBUUCBtZXNzYWdlcyBvdGhlciB0aGFuIHRoZSBj
aGlwcyBtZW1vcnkNCj4+IGxpbWl0YXRpb24sIGJlY2F1c2UgdGhlIG1lbW9yeSByZXN0cmljdGlv
biBpcyBhbHdheXMgdGhlcmUgd2hhdGV2ZXIgDQo+PiB5b3UgdXNlDQo+PiBMYWJlbCBSYW5nZSBv
ciBub3QuDQo+PiBJTUhPLCBzaW5jZSB0aGUgb2JqZWN0aXZlIGlzIHRvIHRlbGwgcmVsYXRlZCBN
UExTIG5vZGVzIHdoaWNoIExTUHMgYXJlIA0KPj4gUFRQDQo+PiBMU1BzLCBhbiBpbmRpY2F0aW9u
IGluIHRoZSBzaWduYWxpbmcoUlNWUC1URS9HTVBMUy9MRFApIGlzIGVub3VnaCBhbmQgDQo+PiBz
ZWVtcw0KPj4gbW9yZSBjb21tb24uIEFuZCBpdCB3aWxsIGF2b2lkIHRoZSBzdHJpY3QgcmVxdWly
ZW1lbnQgb2YgInRoZSBuZXR3b3JrIGFuZA0KPj4gYWxsIG5vZGVzIHJlcXVpcmVkIHRvIHN1cHBv
cnQgdGhlIExhYmVsIHJhbmdlIi4NCj4+IEluIGFkZGl0aW9uLCB0aGVyZSBzaG91bGQgYmUgc29t
ZSBtZWNoYW5pbXMoZS5nLiwgSVNJUy9PU1BGIA0KPj4gZXh0ZW5zaW9ucykgZm9yDQo+PiBub2Rl
cyB0byBhZHZlcnRpc2UgdGhlaXIgUFRQIGNhcGFiaWxpdHkgaGVuY2UgdG8gaGVscCBQVFAgTFNQ
cyANCj4+IGNvbXB1dGF0aW9uLg0KPj4NCj4+IEJlc3QgcmVnYXJkcywNCj4+IE1hY2gNCj4+DQo+
Pg0KPj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N
Cj4+IEZyb206ICJTLiBEYXZhcmkiIDxkYXZhcmlzaEB5YWhvby5jb20+DQo+PiBTZW50OiBXZWRu
ZXNkYXksIEp1bHkgMTQsIDIwMTAgMjozMSBQTQ0KPj4gVG86ICJKaWEgSEUiIDxoZWppYUBodWF3
ZWkuY29tPjsgIlNoYWhyYW0gRGF2YXJpIiA8ZGF2YXJpQGJyb2FkY29tLmNvbT4NCj4+IENjOiA8
bXBsc0BpZXRmLm9yZz47IDxwd2UzQGlldGYub3JnPjsgPHRpY2N0b2NAaWV0Zi5vcmc+OyANCj4+
IDxtcGxzLXRwQGlldGYub3JnPg0KPj4gU3ViamVjdDogUmU6IFttcGxzXSBbUFdFM10gMTU4OCBv
dmVyIE1QTFMgZHJhZnQNCj4+DQo+Pj4gSGkgSmlhLA0KPj4+DQo+Pj4gTGFiZWwgcmFuZ2UgaXMg
YSBTSE9VTEQgcmVxdWlyZW1lbnRzIGFuZCBub3QgTVVTVC4gVGhlIHJlYXNvbiBmb3IgTGFiZWwN
Cj4+PiBSYW5nZSBpcw0KPj4+IG1haW5seSBmb3IgUEhZIGNoaXBzIHRoYXQgZG9uJ3QgaGF2ZSBs
YXJnZSBtZW1vcnkgYW5kIGNhbid0IHN0b3JlIGEgDQo+Pj4gbG90IG9mDQo+Pj4gTGFiZWxzLiBP
dGhlcndpc2UgdGhlIFBUUCBMU1AgaXMgc2V0dXAgdmlhIHNpZ25hbGluZyB0aGF0IHNwZWNpZmll
cyB0aGUNCj4+PiBMU1AgYXMNCj4+PiBjYXJyeWluZyAxNTg4Lg0KPj4+DQo+Pj4gU28gdGhlIGFu
c3dlciBpcyB0aGF0IGlmIGEgTGFiZWwgcmFuZ2UgaXMgdXNlZCBpdCBtdXN0IGJlIGEgR2xvYmFs
IHJhbmdlDQo+Pj4gd2l0aGluDQo+Pj4gYSBuZXR3b3JrIGFuZCBzaG91bGQgbm90IGJlIHVzZWQg
YnkgYW55IHJvdXRlciBmb3Igb3RoZXIgYXBwbGljYXRpb25zLg0KPj4+DQo+Pj4gVGhhbmtzLA0K
Pj4+IFNoYWhyYW0NCj4+Pg0KPj4+DQo+Pj4NCj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPj4+IEZyb206IEppYSBIRSA8aGVqaWFAaHVhd2VpLmNvbT4NCj4+PiBUbzogU2hh
aHJhbSBEYXZhcmkgPGRhdmFyaUBicm9hZGNvbS5jb20+DQo+Pj4gQ2M6IG1wbHNAaWV0Zi5vcmc7
IHB3ZTNAaWV0Zi5vcmc7IHRpY2N0b2NAaWV0Zi5vcmc7IG1wbHMtdHBAaWV0Zi5vcmcNCj4+PiBT
ZW50OiBUdWUsIEp1bHkgMTMsIDIwMTAgOTo1MDozNyBQTQ0KPj4+IFN1YmplY3Q6IFJlOiBbbXBs
c10gW1BXRTNdIDE1ODggb3ZlciBNUExTIGRyYWZ0DQo+Pj4NCj4+Pg0KPj4+IEhpIFNoYWhyYW0s
DQo+Pj4NCj4+PiBPbmUgcXVlc3Rpb24gYWJvdXQgIlBUUCBMYWJlbCBSYW5nZSI6DQo+Pj4NCj4+
PiBUbyBteSBrbm93bGVkZ2UsIGxhYmVsIGluIE1QTFMgbmV0d29yayBpcyBhIGxvY2FsICBtYXR0
ZXIuIEZvciANCj4+PiBleGFtcGxlLCB3ZQ0KPj4+IG1heQ0KPj4+IGhhdmUgcGVyLWludGVyZmFj
ZSBvciBwZXItcGxhdGZvcm0gbGFiZWwgc3BhY2UuIFdpbGwgIHRoaXMgc3BlY2lmaWNlZCANCj4+
PiAiUFRQDQo+Pj4gTGFiZWwNCj4+PiBSYW5nZSIgY29uZmxpY3Qgd2l0aCB0aGUgY3VycmVudCBp
bi11c2UgbGFiZWxzICBmb3IgY29tbW9uIExTUHM/DQo+Pj4NCj4+Pg0KPj4+IEIuUi4NCj4+PiBK
aWENCj4+Pg0KPj4+IC0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCj4+Pj4gRnJvbTogU2hh
aHJhbSAgICBEYXZhcmkNCj4+Pj4gVG86IHRpY2N0b2NAaWV0Zi5vcmcgOyBtcGxzQGlldGYub3Jn
IDsgbXBscy10cEBpZXRmLm9yZyA7IHB3ZTNAaWV0Zi5vcmcNCj4+Pj4gU2VudDogVGh1cnNkYXks
IEp1bHkgMDgsIDIwMTAgMzoxMiBBTQ0KPj4+PiBTdWJqZWN0OiBbUFdFM10gMTU4OCBvdmVyIE1Q
TFMgZHJhZnQNCj4+Pj4NCj4+Pj4NCj4+Pj4gSGkgQWxsLA0KPj4+Pg0KPj4+PiBQbGVhc2UgZmlu
ZCBhdHRhY2hlZCBvdXIgZmlyc3QgZHJhZnQgb2YgMTU4OCBvdmVyIE1QTFMuICAgIFNpbmNlIHdl
IA0KPj4+PiBoYXZlDQo+Pj4+IHNvbWUNCj4+Pj4gdGVjaG5pY2FsIGlzc3VlcyBjb252ZXJ0aW5n
IHRoZSBXb3JkIGZvcm1hdCB0byBUeHQgd2UgICAgY291bGRuw6LigqzihKJ0IA0KPj4+PiB1cGxv
YWQNCj4+Pj4gdGhlDQo+Pj4+IGRyYWZ0IGJlZm9yZSB0aGUgY3V0LW9mZiBkYXRlLiBIb3dldmVy
IHdlIHdpbGwgICAgcHJlc2VudCB0aGUgZHJhZnQgDQo+Pj4+IGluIHRoZQ0KPj4+PiBuZXh0DQo+
Pj4+IElFVEYgbWVldGluZyBhbmQgd2lsbCB1cGxvYWQgdGhlIGRyYWZ0IGFmdGVyIHRoZSAgICBt
ZWV0aW5nLg0KPj4+Pg0KPj4+PiBOb3RlIHRoYXQgdGhlIG1haW4gV0cgaXMgVGljVG9jIGJ1dCBt
YXkgcmVxdWlyZSAgICBjb25zdWx0YXRpb24gd2l0aCANCj4+Pj4gTVBMUw0KPj4+PiBhbmQNCj4+
Pj4gUFdFMyBXR3MuDQo+Pj4+DQo+Pj4+IFRoYW5rcywNCj4+Pj4gU2hhaHJhbSBEYXZhcmkNCj4+
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+IF9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4+IHB3ZTMgbWFpbGluZyAgICBsaXN0
DQo+Pj4+IHB3ZTNAaWV0Zi5vcmcNCj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9wd2UzDQo+Pj4+DQo+Pj4NCj4+Pg0KPj4NCj4+DQo+Pg0KPj4+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4gbXBscyBtYWlsaW5nIGxp
c3QNCj4+PiBtcGxzQGlldGYub3JnDQo+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9tcGxzDQo+Pj4NCj4+DQo+Pg0KPj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4gbXBscyBtYWlsaW5nIGxpc3QNCj4gbXBsc0BpZXRm
Lm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMNCg0KX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnB3ZTMgbWFpbGlu
ZyBsaXN0DQpwd2UzQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL3B3ZTMNCg0KDQoNCg==


From curtis@occnc.com  Tue Jul 20 11:32:27 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 95FD33A6821; Tue, 20 Jul 2010 11:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.167
X-Spam-Level: 
X-Spam-Status: No, score=-2.167 tagged_above=-999 required=5 tests=[AWL=-0.168, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 hqMSUkcrpmQ2; Tue, 20 Jul 2010 11:32:24 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id F34063A67A7; Tue, 20 Jul 2010 11:32:22 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6KIWZtg065155; Tue, 20 Jul 2010 14:32:35 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007201832.o6KIWZtg065155@harbor.orleans.occnc.com>
To: Yong Lucy <lucyyong@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Fri, 16 Jul 2010 14:05:46 CDT." <00d801cb2519$e6f16160$380c7c0a@china.huawei.com> 
Date: Tue, 20 Jul 2010 14:32:35 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org, 'pwe3' <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware Transport
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 18:32:27 -0000

In message <00d801cb2519$e6f16160$380c7c0a@china.huawei.com>
Yong Lucy writes:
>  
>  
> I like to post this e-mail again for reminding. We have changed the draft
> title to draft-yong-pwe-lfc-fat-pw to focus on large flow classification,
> not enhanced ECMP.
>  
> Look forward to discussing this at Maastricht.
>  
> Lucy


Lucy,

Any modifications to the use of the TC bits is almost certainly a
non-starter.  I thought that was also mentioned in the last meeting.
We'll see what comments come out of the meeting this time.

Curtis


>   _____  
>  
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Yong
> Lucy
> Sent: Tuesday, April 27, 2010 5:37 PM
> To: 'pwe3'; mpls@ietf.org
> Subject: [mpls] Large FLow Classificaiton in Flow Aware Transport
>  
>  
>  
> Hi,
>  
> I recap the comments raised during IETF77 meeting. Some are from the PWE3
> meeting and some from offline discussions. Hope this gives some
> clarification and bring up further mailing discussion.
>  
> The draft proposal (draft-yong-pwe3-enhanced-ecmp-lfat-01) is to use one of
> the TC bits in the flow label to indicate large flow. TC bits in flow label
> described in FAT-PW are not used and are not interpreted by LSR. 
>  
> Comments and Responses:
>           
> 1) No use for the proposal. would need to update all equipment to get this
> to work.  A while ago we agreed to not standardize ECMP process. 
>  
> Lucy: Some carriers see the value of it. There is no need to update all
> equipment to get this work. The backward compatibility is supported as
> described in section 6. Partially upgrading can improve some segments while
> keeping other segments remain the same. The intention of the draft is not
> for standardizing ECMP process. It is about standardizing large flow
> classification indication in PSN. The draft layout may lead this confusion.
> We will modify the draft and move enhanced ECMP process description to
> appendix as one implementation example to use large flow classification. We
> will change the draft title to "large flow classification in flow aware
> transport over PSN" and upload soon.
>  
> 2) would need to go through MPLS WG for issue on standardizing ECMP. Label
> stack is always MPLS label stack so MPLS WG would need to OK change of TC
> semantics.  Needs a co-review in MPLS WG and they must approve.
>  
> Lucy: The draft is not for standardizing ECMP. (sorry for the confusion).
> The draft does not change the semantics of a label stack entry defined by
> RFC3032 because the flow label is never on the top of label stack. As FAT-PW
> draft indicates that the interpretation of TC bits in the flow label by LSR
> is undefined. This draft proposes one definition.
>  
> 3) If you can get MPLS WG to agree, one of the issues is that you are
> marking at a PE where the PE may or may not know what is or isn't a big
> flow.  Limitations on PEs ability to determine what a big flow is. Would
> need to tell easily and ubiquitously what a big flow is.
>  
> Lucy: In our proposal, large flows in this context are the top rate ranked
> flows. It is relevant to other flows not the link capacity. Enhanced ECMP
> process just needs a small set of large flows for load balancing, therefore,
> it can pick by statistics, i.e. not necessary all the large flows. The
> method works well even some large flows placed by hashing function. The
> backward compatibility in the draft would deal with this.
>           
> 4) we haven't standardized anything on ECMP. Many will look at bottom of
> stack to look at IP address or anything else to hash on. If I'm a PE router
> with lots of L3VPN traffic and some PWs, how do I know if this is a flow
> label or VPN label.
>  
> Lucy: This is not for ECMP standardization. We propose one method to
> differentiate the flow label from IP packet, PW label, and LSP label at the
> bottom of label stack. This is: check the first nibble to separate IP and
> MPLS packets; for MPLS packets, use TTL value (=0) to check the flow label
> packets.  
>  
> 5) this is addressing an important issue.  Simulations showed a lot of
> traffic and the flows are large enough.  Cases in well engineered network
> where situation is much worse than shown.  Drafts have been submitting in
> past that gained no traction.  To use a method other than just hashing, but
> may be ways to do this without changing label or MPLS.
>  
> Lucy: The simulation use Internet traffic pattern. For carrier network, it
> has a lot of L2VPN traffic carried as single flow, so the situation is
> worse. We work on additional simulation to include such type of traffic. It
> confirms the statement. As Internet traffic grow with higher and higher bit
> rate flows, the problem will become more and more severe. We need to aim on
> this real problem.
>  
> 6) there was a proposal to solve this 10 years ago with no protocol changes.
> This is not needed.
>  
> Lucy: Need clarification which proposal refers to. If it is OMP, the draft
> proposes the different method from OMP. OMP suggest using routing protocol
> to advertise individual ECMP path TE information in the network. The draft
> is about large flow classification indication so LSR can use a set of large
> flows in performing load balance over ECMP paths effectively.
>  
> 7) Changes too much about MPLS processing
>  
> Lucy: It is not that additional process. Gaining is obvious too. 
>  
> 8) did the simulations deal with coming and going of flows? How to address
> flow fluctuation?
>  
> Lucy: we are working on additional simulations. That will include flow
> coming and going situation and include much higher bit rate flows, and a
> "permanent flow" whose rate may change over time to make it as small flow at
> a time or a large flow at another time. The latter case likes a VPWS as a
> flow. Be glad to show some simulation result to the group.
>  
> 9) Signaling can be used for this, why using marking?
>  
> Lucy: today, signaling a PW is used per a service basis such as VPWS or
> VPLS. But one VPWS or VPLS may contain many flows, the draft address this
> situation. It is hard for carrier to signal individual large flow within
> VPLS over PSN networks.  
>  
> 10) If there is incentive to enhanced ECMP, why not do large flow
> recognition at local LSR for the purpose? PE based large flow recognition
> and marking do not apply well at individual LSR.
>  
> Lucy: High bit rate flow is relevant to other flows. Operator can set large
> flow criteria. Having each LSR performs larger flow recognition add complex
> to each LSR and may impact the service performance. Large flow
> classification is easier, we think. Today, DiffServ enables the network to
> perform different service treatments. Large flow classification enables
> network to perform different flow treatments over ECMP operation.
>  
> Comments and suggestion are welcome.
>  
>  
> Regards,
> Lucy

From jdrake@juniper.net  Tue Jul 20 12:19:25 2010
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 292B13A6893; Tue, 20 Jul 2010 12:19:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.005
X-Spam-Level: 
X-Spam-Status: No, score=-6.005 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
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 GlwCXyeNWusg; Tue, 20 Jul 2010 12:19:23 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by core3.amsl.com (Postfix) with ESMTP id 2FF5D3A682A; Tue, 20 Jul 2010 12:19:23 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKTEX2w2DLQcwhOZaPzdaME/v1Nq0O+Tev@postini.com; Tue, 20 Jul 2010 12:19:39 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Tue, 20 Jul 2010 11:43:57 -0700
From: John E Drake <jdrake@juniper.net>
To: "curtis@occnc.com" <curtis@occnc.com>, Yong Lucy <lucyyong@huawei.com>
Date: Tue, 20 Jul 2010 11:43:56 -0700
Thread-Topic: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware Transport
Thread-Index: AcsoOhgYXyrbBhBYRfO6Kq+DEv5LGgAAMQxg
Message-ID: <5E893DB832F57341992548CDBB333163984487C7AE@EMBX01-HQ.jnpr.net>
References: Your message of "Fri, 16 Jul 2010 14:05:46 CDT." <00d801cb2519$e6f16160$380c7c0a@china.huawei.com> <201007201832.o6KIWZtg065155@harbor.orleans.occnc.com>
In-Reply-To: <201007201832.o6KIWZtg065155@harbor.orleans.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, 'pwe3' <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware	Transport
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 19:19:25 -0000

Lucy,

As Curtis points out in section 4.1.2 of http://datatracker.ietf.org/doc/dr=
aft-villamizar-mpls-tp-multipath/, the issue your I-D purports to solve has=
 been already been solved by clever implementation many years ago, with no =
changes to protocols or packet formats.

Thanks,

John

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Curtis Villamizar
> Sent: Tuesday, July 20, 2010 11:33 AM
> To: Yong Lucy
> Cc: mpls@ietf.org; 'pwe3'
> Subject: Re: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware
> Transport
>=20
>=20
> In message <00d801cb2519$e6f16160$380c7c0a@china.huawei.com>
> Yong Lucy writes:
> >
> >
> > I like to post this e-mail again for reminding. We have changed the
> draft
> > title to draft-yong-pwe-lfc-fat-pw to focus on large flow
> classification,
> > not enhanced ECMP.
> >
> > Look forward to discussing this at Maastricht.
> >
> > Lucy
>=20
>=20
> Lucy,
>=20
> Any modifications to the use of the TC bits is almost certainly a
> non-starter.  I thought that was also mentioned in the last meeting.
> We'll see what comments come out of the meeting this time.
>=20
> Curtis
>=20
>=20
> >   _____
> >
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of Yong
> > Lucy
> > Sent: Tuesday, April 27, 2010 5:37 PM
> > To: 'pwe3'; mpls@ietf.org
> > Subject: [mpls] Large FLow Classificaiton in Flow Aware Transport
> >
> >
> >
> > Hi,
> >
> > I recap the comments raised during IETF77 meeting. Some are from the
> PWE3
> > meeting and some from offline discussions. Hope this gives some
> > clarification and bring up further mailing discussion.
> >
> > The draft proposal (draft-yong-pwe3-enhanced-ecmp-lfat-01) is to use
> one of
> > the TC bits in the flow label to indicate large flow. TC bits in flow
> label
> > described in FAT-PW are not used and are not interpreted by LSR.
> >
> > Comments and Responses:
> >
> > 1) No use for the proposal. would need to update all equipment to get
> this
> > to work.  A while ago we agreed to not standardize ECMP process.
> >
> > Lucy: Some carriers see the value of it. There is no need to update
> all
> > equipment to get this work. The backward compatibility is supported
> as
> > described in section 6. Partially upgrading can improve some segments
> while
> > keeping other segments remain the same. The intention of the draft is
> not
> > for standardizing ECMP process. It is about standardizing large flow
> > classification indication in PSN. The draft layout may lead this
> confusion.
> > We will modify the draft and move enhanced ECMP process description
> to
> > appendix as one implementation example to use large flow
> classification. We
> > will change the draft title to "large flow classification in flow
> aware
> > transport over PSN" and upload soon.
> >
> > 2) would need to go through MPLS WG for issue on standardizing ECMP.
> Label
> > stack is always MPLS label stack so MPLS WG would need to OK change
> of TC
> > semantics.  Needs a co-review in MPLS WG and they must approve.
> >
> > Lucy: The draft is not for standardizing ECMP. (sorry for the
> confusion).
> > The draft does not change the semantics of a label stack entry
> defined by
> > RFC3032 because the flow label is never on the top of label stack. As
> FAT-PW
> > draft indicates that the interpretation of TC bits in the flow label
> by LSR
> > is undefined. This draft proposes one definition.
> >
> > 3) If you can get MPLS WG to agree, one of the issues is that you are
> > marking at a PE where the PE may or may not know what is or isn't a
> big
> > flow.  Limitations on PEs ability to determine what a big flow is.
> Would
> > need to tell easily and ubiquitously what a big flow is.
> >
> > Lucy: In our proposal, large flows in this context are the top rate
> ranked
> > flows. It is relevant to other flows not the link capacity. Enhanced
> ECMP
> > process just needs a small set of large flows for load balancing,
> therefore,
> > it can pick by statistics, i.e. not necessary all the large flows.
> The
> > method works well even some large flows placed by hashing function.
> The
> > backward compatibility in the draft would deal with this.
> >
> > 4) we haven't standardized anything on ECMP. Many will look at bottom
> of
> > stack to look at IP address or anything else to hash on. If I'm a PE
> router
> > with lots of L3VPN traffic and some PWs, how do I know if this is a
> flow
> > label or VPN label.
> >
> > Lucy: This is not for ECMP standardization. We propose one method to
> > differentiate the flow label from IP packet, PW label, and LSP label
> at the
> > bottom of label stack. This is: check the first nibble to separate IP
> and
> > MPLS packets; for MPLS packets, use TTL value (=3D0) to check the flow
> label
> > packets.
> >
> > 5) this is addressing an important issue.  Simulations showed a lot
> of
> > traffic and the flows are large enough.  Cases in well engineered
> network
> > where situation is much worse than shown.  Drafts have been
> submitting in
> > past that gained no traction.  To use a method other than just
> hashing, but
> > may be ways to do this without changing label or MPLS.
> >
> > Lucy: The simulation use Internet traffic pattern. For carrier
> network, it
> > has a lot of L2VPN traffic carried as single flow, so the situation
> is
> > worse. We work on additional simulation to include such type of
> traffic. It
> > confirms the statement. As Internet traffic grow with higher and
> higher bit
> > rate flows, the problem will become more and more severe. We need to
> aim on
> > this real problem.
> >
> > 6) there was a proposal to solve this 10 years ago with no protocol
> changes.
> > This is not needed.
> >
> > Lucy: Need clarification which proposal refers to. If it is OMP, the
> draft
> > proposes the different method from OMP. OMP suggest using routing
> protocol
> > to advertise individual ECMP path TE information in the network. The
> draft
> > is about large flow classification indication so LSR can use a set of
> large
> > flows in performing load balance over ECMP paths effectively.
> >
> > 7) Changes too much about MPLS processing
> >
> > Lucy: It is not that additional process. Gaining is obvious too.
> >
> > 8) did the simulations deal with coming and going of flows? How to
> address
> > flow fluctuation?
> >
> > Lucy: we are working on additional simulations. That will include
> flow
> > coming and going situation and include much higher bit rate flows,
> and a
> > "permanent flow" whose rate may change over time to make it as small
> flow at
> > a time or a large flow at another time. The latter case likes a VPWS
> as a
> > flow. Be glad to show some simulation result to the group.
> >
> > 9) Signaling can be used for this, why using marking?
> >
> > Lucy: today, signaling a PW is used per a service basis such as VPWS
> or
> > VPLS. But one VPWS or VPLS may contain many flows, the draft address
> this
> > situation. It is hard for carrier to signal individual large flow
> within
> > VPLS over PSN networks.
> >
> > 10) If there is incentive to enhanced ECMP, why not do large flow
> > recognition at local LSR for the purpose? PE based large flow
> recognition
> > and marking do not apply well at individual LSR.
> >
> > Lucy: High bit rate flow is relevant to other flows. Operator can set
> large
> > flow criteria. Having each LSR performs larger flow recognition add
> complex
> > to each LSR and may impact the service performance. Large flow
> > classification is easier, we think. Today, DiffServ enables the
> network to
> > perform different service treatments. Large flow classification
> enables
> > network to perform different flow treatments over ECMP operation.
> >
> > Comments and suggestion are welcome.
> >
> >
> > Regards,
> > Lucy
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From davarish@yahoo.com  Tue Jul 20 13:19:43 2010
Return-Path: <davarish@yahoo.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A97123A67B1 for <mpls@core3.amsl.com>; Tue, 20 Jul 2010 13:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, REPTO_QUOTE_YAHOO=2.599]
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 q+9K8uA6YUUd for <mpls@core3.amsl.com>; Tue, 20 Jul 2010 13:19:41 -0700 (PDT)
Received: from n23.bullet.mail.mud.yahoo.com (n23.bullet.mail.mud.yahoo.com [68.142.206.162]) by core3.amsl.com (Postfix) with SMTP id 3030C3A67BD for <mpls@ietf.org>; Tue, 20 Jul 2010 13:19:41 -0700 (PDT)
Received: from [209.191.108.96] by n23.bullet.mail.mud.yahoo.com with NNFMP; 20 Jul 2010 20:19:54 -0000
Received: from [66.196.97.153] by t3.bullet.mud.yahoo.com with NNFMP; 20 Jul 2010 20:19:53 -0000
Received: from [127.0.0.1] by omp206.mail.re3.yahoo.com with NNFMP; 20 Jul 2010 20:19:53 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 693193.65517.bm@omp206.mail.re3.yahoo.com
Received: (qmail 12237 invoked by uid 60001); 20 Jul 2010 20:19:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1279657193; bh=VXY1BtsDcGL6BHZfT6PTyLHwwb8+TZUSnplLM7l9NhQ=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=yKntxKzGzXFZCQbVVGhwt55F5htpbqXTTMNr0HalkPtdwmCM/LhMlZlHz7jbKg4Pr8KEBrDlVqYkkFuoZvKDm3b2bv/Nt8Z2hxHyaG6c7nrID2GBaCTEskXFpzt4uKfyQj+eal0q9gJBeh9vWQ9XzNyx+LR990xgKf8tS12kpaI=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=AD4Xm4vd73NEybBbWwrmCPOd2CZuLdquoLGoyo08GCqZXHhD1ZiZFj5RUWnGgAns8uYgfptULHM7p9ei47kFKqhHlwY+pSIMbcdywQ/901wuwHhvAoH3ATRm1uu58jmVJ2ktcmEbkj491gshmOGFCtcEQQyUoMI/TGoXMrjc608=;
Message-ID: <485512.11753.qm@web88403.mail.re1.yahoo.com>
X-YMail-OSG: bCIvYh8VM1nYTNY9_8pV8P0Ia3Hd795z4PpQZG5e4h.4KIp qhNC66mX.xTywcQwxJ1fAngPHw7N4_MQUKwMgmrSNvDGh66LDBihsa6pJfJn .AraE6_addBnWQ8kHgM5dASMaEyxFOyWLsxafk2P7b32XxgGlltEZU.xEEAq XHP2Y0rxlJhZlEmMQf5MxISz_iyDpHOKzivAa7ANPLPTM6ZKmX8rCYcE80ku rbVfAzlds0OXnmu_D4HoYpTtBYOJsQaH6H8rbG53GLQkiGB03Fg2NLnnxxcx 9lD8.pL_CfyKavjdOEhbEFmrOkoIr0tILpM9RiWK18_WXBUf3L4uQltta6NJ 11Uj236wAdL_IG5AM
Received: from [216.123.155.199] by web88403.mail.re1.yahoo.com via HTTP; Tue, 20 Jul 2010 13:19:53 PDT
X-Mailer: YahooMailRC/420.4 YahooMailWebService/0.8.104.276605
References: <201007201651.o6KGpJ9B063875@harbor.orleans.occnc.com>
Date: Tue, 20 Jul 2010 13:19:53 -0700 (PDT)
From: "S. Davari" <davarish@yahoo.com>
To: curtis@occnc.com, John E Drake <jdrake@juniper.net>
In-Reply-To: <201007201651.o6KGpJ9B063875@harbor.orleans.occnc.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1708473949-1279657193=:11753"
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ticctoc@ietf.org" <ticctoc@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls] [mpls-tp]  [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "S. Davari" <davarish@yahoo.com>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 20:19:43 -0000

--0-1708473949-1279657193=:11753
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Good suggestion. I will add a new section.=0A=0AThx=0AShahram=0A=0A=0A=0A=
=0A=0A________________________________=0AFrom: Curtis Villamizar <curtis@oc=
cnc.com>=0ATo: John E Drake <jdrake@juniper.net>=0ACc: Shahram Davari <dava=
ri@broadcom.com>; Joel M. Halpern <jmh@joelhalpern.com>; =0A"mpls@ietf.org"=
 <mpls@ietf.org>; "mpls-tp@ietf.org" <mpls-tp@ietf.org>; =0A"pwe3@ietf.org"=
 <pwe3@ietf.org>; "ticctoc@ietf.org" <ticctoc@ietf.org>; S. =0ADavari <dava=
rish@yahoo.com>=0ASent: Tue, July 20, 2010 9:51:19 AM=0ASubject: Re: [mpls-=
tp] [mpls] [PWE3] 1588 over MPLS draft =0A=0A=0AA section on backwards comp=
atibility with non-compliant LSR would be=0Ahelpful.  It might be as simple=
 as a bit of RSVP-TE signaling that=0Aindicates capability and actions to t=
ake when a non-compliant LSR is=0Afound in a path.  Normally IEEE-1588 (or =
very high precision NTP)=0Awould be with adjacent LSR so non-compliance wou=
ld mean no peering=0Awould be attempted.=0A=0ACurtis=0A=0A=0AIn message <5E=
893DB832F57341992548CDBB3331639844311567@EMBX01-HQ.jnpr.net>=0AJohn E Drake=
 writes:=0A>  =0A> > -----Original Message-----=0A> > From: mpls-tp-bounces=
@ietf.org [mailto:mpls-tp-bounces@ietf.org] On=0A> > Behalf Of Shahram Dava=
ri=0A> > Sent: Thursday, July 15, 2010 12:52 PM=0A> > To: Joel M. Halpern=
=0A> > Cc: mpls@ietf.org; ticctoc@ietf.org; S. Davari; pwe3@ietf.org; mpls-=
=0A> > tp@ietf.org=0A> > Subject: Re: [mpls-tp] [mpls] [PWE3] 1588 over MPL=
S draft=0A> > =0A> > Hi Joel,=0A> > =0A> > There are 2 aspects to this puzz=
le:=0A> > =0A> > 1) Hardware support for 1588 in a device.=0A> > 2) Softwar=
e support for 1588 in the form of allocating labels to PTP=0A> > LSPs=0A> >=
 =0A> > A router that wants to perform 1588 time stamping must have both (1=
)=0A> > and (2) functionality. While a router in the path of a PTP LSP that=
=0A> > does not support (1) should support (2) and advertise labels from so=
me=0A> > arbitrary range for PTP LSP.=0A> > =0A> > It is quite easy to upgr=
ade a router software so that when it receives=0A> > RSVP-TE label request =
to assign label from an arbitrary local range.=0A>  =0A> JD:  What happens =
in the case where a router's software has not been upgraded?=0A>  =0A> > =
=0A> > So I don't see any issue here.=0A> > =0A> > Thanks,=0A> > Shahram=0A=
> > =0A> > =0A> > =0A> > -----Original Message-----=0A> > From: Joel M. Hal=
pern [mailto:jmh@joelhalpern.com]=0A> > Sent: Thursday, July 15, 2010 12:06=
 PM=0A> > To: Shahram Davari=0A> > Cc: Mach Chen; S. Davari; Jia HE; mpls@i=
etf.org; pwe3@ietf.org;=0A> > ticctoc@ietf.org; mpls-tp@ietf.org=0A> > Subj=
ect: Re: [mpls] [PWE3] 1588 over MPLS draft=0A> > =0A> > Architecturally, a=
s I understand the draft, the downstream neighbor of=0A> > a=0A> > 1588 sup=
porting device (on the PTP carrying LSP) may not itself be a=0A> > 1588 sup=
porting device.  Is that correct?  If that is not correct, if=0A> > instead=
 the structure is that PTP supporting LSPs are established=0A> > between ad=
jacent enhanced devices, then I can see how some sort of a=0A> > label rang=
e might make sense.=0A> > =0A> > If however, the downstream node you refer =
to may be an existing LSR,=0A> > then I do not see how you can ask an exist=
ing LSR to allocate a label=0A> > range for a function it does not understa=
nd.=0A> > =0A> > Yours,=0A> > Joel=0A> > =0A> > Shahram Davari wrote:=0A> >=
 > Hi Joel,=0A> > >=0A> > > I agree with your logic, but the idea is a bit =
different:=0A> > >=0A> > > All we need is a label range, it does not need t=
o be globally unique=0A> > in the network and it does=0A> >  >not even need=
 to be the same on the Tx and Rx direction of the same=0A> > link. Although=
 we need time=0A> >  >stamping both on Rx and on Tx, but on Rx a node is in=
 control of its=0A> > own label and on Tx the=0A> >  >downstream node shoul=
d advertise some label range. What we don't want=0A> > is that the downstre=
am=0A> >  >node to advertise random labels for each LSP carrying PTP.=0A> >=
 >=0A> > > I will update the draft to mention that the label range does not=
=0A> > require to be global but it can=0A> >  >be per-platform or even per-=
interface.=0A> > >=0A> > > Thanks,=0A> > > Shahram=0A> > >=0A> > > -----Ori=
ginal Message-----=0A> > > From: Joel M. Halpern [mailto:jmh@joelhalpern.co=
m]=0A> > > Sent: Wednesday, July 14, 2010 8:21 PM=0A> > > To: Mach Chen=0A>=
 > > Cc: Shahram Davari; S. Davari; Jia HE; mpls@ietf.org; pwe3@ietf.org;=
=0A> > ticctoc@ietf.org; mpls-tp@ietf.org=0A> > > Subject: Re: [mpls] [PWE3=
] 1588 over MPLS draft=0A> > >=0A> > > Remember that if what is required is=
 that the message arriving at the=0A> > > 1588 supporting device have a cer=
tain label range, that is a purely=0A> > > local matter.  As long as the si=
ngaling carries the indication that=0A> > the=0A> > > LSP is to be dedicate=
d to 1588 traffic (a reasonable extension to the=0A> > > signaling), the do=
wnstream switch can pick what label to assign to=0A> > that LSP.=0A> > >=0A=
> > > If the goal is to have the outgoing label be from a specific range,=
=0A> > that=0A> > > is essentially impossible in the proposed architecture.=
  The proposed=0A> > > architecture is one in which 1588 switches are peers=
 with existing=0A> > LSRs=0A> > > using MPLS.  As such, in order to have a =
label range for outgoing=0A> > > labels, the existing MPLS LSR would someho=
w have to know about this=0A> > > reserved label range, not use those label=
s for other purposes, and=0A> > > assign those labels to 1588 LSPs.  All of=
 which is=0A> > > non-backwards-compatible.  If the 1588 LSPs were actually=
=0A> > pseudowires,=0A> > > tunneled over LSPs, then any number of things a=
re possible.=0A> > >=0A> > > Yours,=0A> > > Joel M. Halpern=0A> > >=0A> > >=
 Mach Chen wrote:=0A> > >> Hi Shahram,=0A> > >>=0A> > >> I agree that the l=
abel range idea is an efficient way that could=0A> > reduce=0A> > >> the st=
orage requirement of PHY chips.=0A> > >>=0A> > >> It's easy to require one =
or limited nodes to reserve a label range,=0A> > but=0A> > >> IMHO, it very=
 difficut to require all nodes of a large network to do=0A> > >> this and e=
ven worse when some labels are already used by other LSPs,=0A> > >> unless =
there are some mechanisms to negotiate/advertise(e.g.,=0A> > flooding=0A> >=
 >> the label range by IGP within the network) the proper label range=0A> >=
 hence=0A> > >> to aviod label collision.=0A> > >>=0A> > >> Best regards,=
=0A> > >> Mach=0A> > >>=0A> > >> ------------------------------------------=
--------=0A> > >> From: "Shahram Davari" <davari@broadcom.com>=0A> > >> Sen=
t: Thursday, July 15, 2010 1:58 AM=0A> > >> To: "Mach Chen" <mach@huawei.co=
m>; "S. Davari" <davarish@yahoo.com>;=0A> > >> "Jia HE" <hejia@huawei.com>=
=0A> > >> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>;=0A> > >=
> <mpls-tp@ietf.org>=0A> > >> Subject: RE: [mpls] [PWE3] 1588 over MPLS dra=
ft=0A> > >>=0A> > >>> Hi Mach,=0A> > >>>=0A> > >>> When a service provider =
wants to create these PTP LSPs, what is=0A> > wrong=0A> > >>> with allocati=
ng a range of labels for this purpose? This is purely=0A> > a=0A> > >>> sof=
tware exercise. There are 2 million labels available to each=0A> > node,=0A=
> > >>> why can't some of them be allocated by software to PTP?=0A> > >>>=
=0A> > >>> In theory what you say is correct and should work, but in practi=
ce=0A> > >>> there is a function called 1-step Transparent clocking that=0A=
> > requires=0A> > >>> time stamping at the PHY (immediately when the packe=
t is received=0A> > or=0A> > >>> transmitted). PHY chips don't have CAM or =
lots of memory to store a=0A> > >>> few thousand random labels. The label r=
ange will solve that problem=0A> > >>> and is consistent with MPLS architec=
ture.=0A> > >>>=0A> > >>> Thanks,=0A> > >>> Shahram=0A> > >>>=0A> > >>> ---=
--Original Message-----=0A> > >>> From: Mach Chen [mailto:mach@huawei.com]=
=0A> > >>> Sent: Wednesday, July 14, 2010 1:53 AM=0A> > >>> To: S. Davari; =
Jia HE; Shahram Davari=0A> > >>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@=
ietf.org; mpls-=0A> > tp@ietf.org=0A> > >>> Subject: Re: [mpls] [PWE3] 1588=
 over MPLS draft=0A> > >>>=0A> > >>> Hi Shahram,=0A> > >>>=0A> > >>> From t=
he view of implementation, there is no more difference=0A> > between=0A> > =
>>> SHOULD=0A> > >>> and MUST :-)=0A> > >>> For me, the Label Range is more=
 like a mechanim to notify related=0A> > >>> nodes that=0A> > >>> some LSPs=
 are dedicated for PTP messages other than the chips=0A> > memory=0A> > >>>=
 limitation, because the memory restriction is always there whatever=0A> > =
>>> you use=0A> > >>> Label Range or not.=0A> > >>> IMHO, since the objecti=
ve is to tell related MPLS nodes which LSPs=0A> > are=0A> > >>> PTP=0A> > >=
>> LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough=0A> > =
and=0A> > >>> seems=0A> > >>> more common. And it will avoid the strict req=
uirement of "the=0A> > network and=0A> > >>> all nodes required to support =
the Label range".=0A> > >>> In addition, there should be some mechanims(e.g=
., ISIS/OSPF=0A> > >>> extensions) for=0A> > >>> nodes to advertise their P=
TP capability hence to help PTP LSPs=0A> > >>> computation.=0A> > >>>=0A> >=
 >>> Best regards,=0A> > >>> Mach=0A> > >>>=0A> > >>>=0A> > >>> -----------=
---------------------------------------=0A> > >>> From: "S. Davari" <davari=
sh@yahoo.com>=0A> > >>> Sent: Wednesday, July 14, 2010 2:31 PM=0A> > >>> To=
: "Jia HE" <hejia@huawei.com>; "Shahram Davari"=0A> > <davari@broadcom.com>=
=0A> > >>> Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>;=0A> > =
>>> <mpls-tp@ietf.org>=0A> > >>> Subject: Re: [mpls] [PWE3] 1588 over MPLS =
draft=0A> > >>>=0A> > >>>> Hi Jia,=0A> > >>>>=0A> > >>>> Label range is a S=
HOULD requirements and not MUST. The reason for=0A> > Label=0A> > >>>> Rang=
e is=0A> > >>>> mainly for PHY chips that don't have large memory and can't=
 store=0A> > a=0A> > >>>> lot of=0A> > >>>> Labels. Otherwise the PTP LSP i=
s setup via signaling that=0A> > specifies the=0A> > >>>> LSP as=0A> > >>>>=
 carrying 1588.=0A> > >>>>=0A> > >>>> So the answer is that if a Label rang=
e is used it must be a Global=0A> > range=0A> > >>>> within=0A> > >>>> a ne=
twork and should not be used by any router for other=0A> > applications.=0A=
> > >>>>=0A> > >>>> Thanks,=0A> > >>>> Shahram=0A> > >>>>=0A> > >>>>=0A> > =
>>>>=0A> > >>>> ________________________________=0A> > >>>> From: Jia HE <h=
ejia@huawei.com>=0A> > >>>> To: Shahram Davari <davari@broadcom.com>=0A> > =
>>>> Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-=0A> > tp@iet=
f.org=0A> > >>>> Sent: Tue, July 13, 2010 9:50:37 PM=0A> > >>>> Subject: Re=
: [mpls] [PWE3] 1588 over MPLS draft=0A> > >>>>=0A> > >>>>=0A> > >>>> Hi Sh=
ahram,=0A> > >>>>=0A> > >>>> One question about "PTP Label Range":=0A> > >>=
>>=0A> > >>>> To my knowledge, label in MPLS network is a local  matter. Fo=
r=0A> > >>>> example, we=0A> > >>>> may=0A> > >>>> have per-interface or pe=
r-platform label space. Will  this=0A> > specificed=0A> > >>>> "PTP=0A> > >=
>>> Label=0A> > >>>> Range" conflict with the current in-use labels  for co=
mmon LSPs?=0A> > >>>>=0A> > >>>>=0A> > >>>> B.R.=0A> > >>>> Jia=0A> > >>>>=
=0A> > >>>> ----- Original Message -----=0A> > >>>>> From: Shahram    Davar=
i=0A> > >>>>> To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ;=0A>=
 > pwe3@ietf.org=0A> > >>>>> Sent: Thursday, July 08, 2010 3:12 AM=0A> > >>=
>>> Subject: [PWE3] 1588 over MPLS draft=0A> > >>>>>=0A> > >>>>>=0A> > >>>>=
> Hi All,=0A> > >>>>>=0A> > >>>>> Please find attached our first draft of 1=
588 over MPLS.    Since=0A> > we=0A> > >>>>> have=0A> > >>>>> some=0A> > >>=
>>> technical issues converting the Word format to Txt we    couldn=E2=80=
=99t=0A> > >>>>> upload=0A> > >>>>> the=0A> > >>>>> draft before the cut-of=
f date. However we will    present the=0A> > draft=0A> > >>>>> in the=0A> >=
 >>>>> next=0A> > >>>>> IETF meeting and will upload the draft after the   =
 meeting.=0A> > >>>>>=0A> > >>>>> Note that the main WG is TicToc but may r=
equire    consultation=0A> > with=0A> > >>>>> MPLS=0A> > >>>>> and=0A> > >>=
>>> PWE3 WGs.=0A> > >>>>>=0A> > >>>>> Thanks,=0A> > >>>>> Shahram Davari=0A=
=0A=0A
--0-1708473949-1279657193=:11753
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:bookman old style,new york,times,serif;f=
ont-size:12pt">Good suggestion. I will add a new section.<br><br>Thx<br>Sha=
hram<br><div><br></div><div style=3D"font-family: bookman old style,new yor=
k,times,serif; font-size: 12pt;"><br><div style=3D"font-family: arial,helve=
tica,sans-serif; font-size: 13px;"><font size=3D"2" face=3D"Tahoma"><hr siz=
e=3D"1"><b><span style=3D"font-weight: bold;">From:</span></b> Curtis Villa=
mizar &lt;curtis@occnc.com&gt;<br><b><span style=3D"font-weight: bold;">To:=
</span></b> John E Drake &lt;jdrake@juniper.net&gt;<br><b><span style=3D"fo=
nt-weight: bold;">Cc:</span></b> Shahram Davari &lt;davari@broadcom.com&gt;=
; Joel M. Halpern &lt;jmh@joelhalpern.com&gt;; "mpls@ietf.org" &lt;mpls@iet=
f.org&gt;; "mpls-tp@ietf.org" &lt;mpls-tp@ietf.org&gt;; "pwe3@ietf.org" &lt=
;pwe3@ietf.org&gt;; "ticctoc@ietf.org" &lt;ticctoc@ietf.org&gt;; S. Davari
 &lt;davarish@yahoo.com&gt;<br><b><span style=3D"font-weight: bold;">Sent:<=
/span></b> Tue, July 20, 2010 9:51:19 AM<br><b><span style=3D"font-weight: =
bold;">Subject:</span></b> Re: [mpls-tp] [mpls] [PWE3] 1588 over MPLS draft=
 <br></font><br><br>A section on backwards compatibility with non-compliant=
 LSR would be<br>helpful.&nbsp; It might be as simple as a bit of RSVP-TE s=
ignaling that<br>indicates capability and actions to take when a non-compli=
ant LSR is<br>found in a path.&nbsp; Normally IEEE-1588 (or very high preci=
sion NTP)<br>would be with adjacent LSR so non-compliance would mean no pee=
ring<br>would be attempted.<br><br>Curtis<br><br><br>In message &lt;<a ymai=
lto=3D"mailto:5E893DB832F57341992548CDBB3331639844311567@EMBX01-HQ.jnpr.net=
" href=3D"mailto:5E893DB832F57341992548CDBB3331639844311567@EMBX01-HQ.jnpr.=
net">5E893DB832F57341992548CDBB3331639844311567@EMBX01-HQ.jnpr.net</a>&gt;<=
br>John E Drake writes:<br>&gt;&nbsp; <br>&gt; &gt; -----Original
 Message-----<br>&gt; &gt; From: <a ymailto=3D"mailto:mpls-tp-bounces@ietf.=
org" href=3D"mailto:mpls-tp-bounces@ietf.org">mpls-tp-bounces@ietf.org</a> =
[mailto:<a ymailto=3D"mailto:mpls-tp-bounces@ietf.org" href=3D"mailto:mpls-=
tp-bounces@ietf.org">mpls-tp-bounces@ietf.org</a>] On<br>&gt; &gt; Behalf O=
f Shahram Davari<br>&gt; &gt; Sent: Thursday, July 15, 2010 12:52 PM<br>&gt=
; &gt; To: Joel M. Halpern<br>&gt; &gt; Cc: <a ymailto=3D"mailto:mpls@ietf.=
org" href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a ymailto=3D"mailto:=
ticctoc@ietf.org" href=3D"mailto:ticctoc@ietf.org">ticctoc@ietf.org</a>; S.=
 Davari; <a ymailto=3D"mailto:pwe3@ietf.org" href=3D"mailto:pwe3@ietf.org">=
pwe3@ietf.org</a>; mpls-<br>&gt; &gt; <a ymailto=3D"mailto:tp@ietf.org" hre=
f=3D"mailto:tp@ietf.org">tp@ietf.org</a><br>&gt; &gt; Subject: Re: [mpls-tp=
] [mpls] [PWE3] 1588 over MPLS draft<br>&gt; &gt; <br>&gt; &gt; Hi Joel,<br=
>&gt; &gt; <br>&gt; &gt; There are 2 aspects to this puzzle:<br>&gt; &gt; <=
br>&gt; &gt; 1)
 Hardware support for 1588 in a device.<br>&gt; &gt; 2) Software support fo=
r 1588 in the form of allocating labels to PTP<br>&gt; &gt; LSPs<br>&gt; &g=
t; <br>&gt; &gt; A router that wants to perform 1588 time stamping must hav=
e both (1)<br>&gt; &gt; and (2) functionality. While a router in the path o=
f a PTP LSP that<br>&gt; &gt; does not support (1) should support (2) and a=
dvertise labels from some<br>&gt; &gt; arbitrary range for PTP LSP.<br>&gt;=
 &gt; <br>&gt; &gt; It is quite easy to upgrade a router software so that w=
hen it receives<br>&gt; &gt; RSVP-TE label request to assign label from an =
arbitrary local range.<br>&gt;&nbsp; <br>&gt; JD:&nbsp; What happens in the=
 case where a router's software has not been upgraded?<br>&gt;&nbsp; <br>&g=
t; &gt; <br>&gt; &gt; So I don't see any issue here.<br>&gt; &gt; <br>&gt; =
&gt; Thanks,<br>&gt; &gt; Shahram<br>&gt; &gt; <br>&gt; &gt; <br>&gt; &gt; =
<br>&gt; &gt; -----Original Message-----<br>&gt; &gt; From: Joel M.
 Halpern [mailto:<a ymailto=3D"mailto:jmh@joelhalpern.com" href=3D"mailto:j=
mh@joelhalpern.com">jmh@joelhalpern.com</a>]<br>&gt; &gt; Sent: Thursday, J=
uly 15, 2010 12:06 PM<br>&gt; &gt; To: Shahram Davari<br>&gt; &gt; Cc: Mach=
 Chen; S. Davari; Jia HE; <a ymailto=3D"mailto:mpls@ietf.org" href=3D"mailt=
o:mpls@ietf.org">mpls@ietf.org</a>; <a ymailto=3D"mailto:pwe3@ietf.org" hre=
f=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a>;<br>&gt; &gt; <a ymailto=3D"ma=
ilto:ticctoc@ietf.org" href=3D"mailto:ticctoc@ietf.org">ticctoc@ietf.org</a=
>; <a ymailto=3D"mailto:mpls-tp@ietf.org" href=3D"mailto:mpls-tp@ietf.org">=
mpls-tp@ietf.org</a><br>&gt; &gt; Subject: Re: [mpls] [PWE3] 1588 over MPLS=
 draft<br>&gt; &gt; <br>&gt; &gt; Architecturally, as I understand the draf=
t, the downstream neighbor of<br>&gt; &gt; a<br>&gt; &gt; 1588 supporting d=
evice (on the PTP carrying LSP) may not itself be a<br>&gt; &gt; 1588 suppo=
rting device.&nbsp; Is that correct?&nbsp; If that is not correct, if<br>&g=
t; &gt;
 instead the structure is that PTP supporting LSPs are established<br>&gt; =
&gt; between adjacent enhanced devices, then I can see how some sort of a<b=
r>&gt; &gt; label range might make sense.<br>&gt; &gt; <br>&gt; &gt; If how=
ever, the downstream node you refer to may be an existing LSR,<br>&gt; &gt;=
 then I do not see how you can ask an existing LSR to allocate a label<br>&=
gt; &gt; range for a function it does not understand.<br>&gt; &gt; <br>&gt;=
 &gt; Yours,<br>&gt; &gt; Joel<br>&gt; &gt; <br>&gt; &gt; Shahram Davari wr=
ote:<br>&gt; &gt; &gt; Hi Joel,<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; I agree=
 with your logic, but the idea is a bit different:<br>&gt; &gt; &gt;<br>&gt=
; &gt; &gt; All we need is a label range, it does not need to be globally u=
nique<br>&gt; &gt; in the network and it does<br>&gt; &gt;&nbsp; &gt;not ev=
en need to be the same on the Tx and Rx direction of the same<br>&gt; &gt; =
link. Although we need time<br>&gt; &gt;&nbsp; &gt;stamping both on
 Rx and on Tx, but on Rx a node is in control of its<br>&gt; &gt; own label=
 and on Tx the<br>&gt; &gt;&nbsp; &gt;downstream node should advertise some=
 label range. What we don't want<br>&gt; &gt; is that the downstream<br>&gt=
; &gt;&nbsp; &gt;node to advertise random labels for each LSP carrying PTP.=
<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; I will update the draft to mention tha=
t the label range does not<br>&gt; &gt; require to be global but it can<br>=
&gt; &gt;&nbsp; &gt;be per-platform or even per-interface.<br>&gt; &gt; &gt=
;<br>&gt; &gt; &gt; Thanks,<br>&gt; &gt; &gt; Shahram<br>&gt; &gt; &gt;<br>=
&gt; &gt; &gt; -----Original Message-----<br>&gt; &gt; &gt; From: Joel M. H=
alpern [mailto:<a ymailto=3D"mailto:jmh@joelhalpern.com" href=3D"mailto:jmh=
@joelhalpern.com">jmh@joelhalpern.com</a>]<br>&gt; &gt; &gt; Sent: Wednesda=
y, July 14, 2010 8:21 PM<br>&gt; &gt; &gt; To: Mach Chen<br>&gt; &gt; &gt; =
Cc: Shahram Davari; S. Davari; Jia HE; <a ymailto=3D"mailto:mpls@ietf.org"
 href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a ymailto=3D"mailto:pwe3=
@ietf.org" href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a>;<br>&gt; &gt; <a=
 ymailto=3D"mailto:ticctoc@ietf.org" href=3D"mailto:ticctoc@ietf.org">ticct=
oc@ietf.org</a>; <a ymailto=3D"mailto:mpls-tp@ietf.org" href=3D"mailto:mpls=
-tp@ietf.org">mpls-tp@ietf.org</a><br>&gt; &gt; &gt; Subject: Re: [mpls] [P=
WE3] 1588 over MPLS draft<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; Remember that=
 if what is required is that the message arriving at the<br>&gt; &gt; &gt; =
1588 supporting device have a certain label range, that is a purely<br>&gt;=
 &gt; &gt; local matter.&nbsp; As long as the singaling carries the indicat=
ion that<br>&gt; &gt; the<br>&gt; &gt; &gt; LSP is to be dedicated to 1588 =
traffic (a reasonable extension to the<br>&gt; &gt; &gt; signaling), the do=
wnstream switch can pick what label to assign to<br>&gt; &gt; that LSP.<br>=
&gt; &gt; &gt;<br>&gt; &gt; &gt; If the goal is to have the outgoing label =
be from
 a specific range,<br>&gt; &gt; that<br>&gt; &gt; &gt; is essentially impos=
sible in the proposed architecture.&nbsp; The proposed<br>&gt; &gt; &gt; ar=
chitecture is one in which 1588 switches are peers with existing<br>&gt; &g=
t; LSRs<br>&gt; &gt; &gt; using MPLS.&nbsp; As such, in order to have a lab=
el range for outgoing<br>&gt; &gt; &gt; labels, the existing MPLS LSR would=
 somehow have to know about this<br>&gt; &gt; &gt; reserved label range, no=
t use those labels for other purposes, and<br>&gt; &gt; &gt; assign those l=
abels to 1588 LSPs.&nbsp; All of which is<br>&gt; &gt; &gt; non-backwards-c=
ompatible.&nbsp; If the 1588 LSPs were actually<br>&gt; &gt; pseudowires,<b=
r>&gt; &gt; &gt; tunneled over LSPs, then any number of things are possible=
.<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; Yours,<br>&gt; &gt; &gt; Joel M. Halp=
ern<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; Mach Chen wrote:<br>&gt; &gt; &gt;&=
gt; Hi Shahram,<br>&gt; &gt; &gt;&gt;<br>&gt; &gt; &gt;&gt; I agree
 that the label range idea is an efficient way that could<br>&gt; &gt; redu=
ce<br>&gt; &gt; &gt;&gt; the storage requirement of PHY chips.<br>&gt; &gt;=
 &gt;&gt;<br>&gt; &gt; &gt;&gt; It's easy to require one or limited nodes t=
o reserve a label range,<br>&gt; &gt; but<br>&gt; &gt; &gt;&gt; IMHO, it ve=
ry difficut to require all nodes of a large network to do<br>&gt; &gt; &gt;=
&gt; this and even worse when some labels are already used by other LSPs,<b=
r>&gt; &gt; &gt;&gt; unless there are some mechanisms to negotiate/advertis=
e(e.g.,<br>&gt; &gt; flooding<br>&gt; &gt; &gt;&gt; the label range by IGP =
within the network) the proper label range<br>&gt; &gt; hence<br>&gt; &gt; =
&gt;&gt; to aviod label collision.<br>&gt; &gt; &gt;&gt;<br>&gt; &gt; &gt;&=
gt; Best regards,<br>&gt; &gt; &gt;&gt; Mach<br>&gt; &gt; &gt;&gt;<br>&gt; =
&gt; &gt;&gt; --------------------------------------------------<br>&gt; &g=
t; &gt;&gt; From: "Shahram Davari" &lt;<a
 ymailto=3D"mailto:davari@broadcom.com" href=3D"mailto:davari@broadcom.com"=
>davari@broadcom.com</a>&gt;<br>&gt; &gt; &gt;&gt; Sent: Thursday, July 15,=
 2010 1:58 AM<br>&gt; &gt; &gt;&gt; To: "Mach Chen" &lt;<a ymailto=3D"mailt=
o:mach@huawei.com" href=3D"mailto:mach@huawei.com">mach@huawei.com</a>&gt;;=
 "S. Davari" &lt;<a ymailto=3D"mailto:davarish@yahoo.com" href=3D"mailto:da=
varish@yahoo.com">davarish@yahoo.com</a>&gt;;<br>&gt; &gt; &gt;&gt; "Jia HE=
" &lt;<a ymailto=3D"mailto:hejia@huawei.com" href=3D"mailto:hejia@huawei.co=
m">hejia@huawei.com</a>&gt;<br>&gt; &gt; &gt;&gt; Cc: &lt;<a ymailto=3D"mai=
lto:mpls@ietf.org" href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;; &lt=
;<a ymailto=3D"mailto:pwe3@ietf.org" href=3D"mailto:pwe3@ietf.org">pwe3@iet=
f.org</a>&gt;; &lt;<a ymailto=3D"mailto:ticctoc@ietf.org" href=3D"mailto:ti=
cctoc@ietf.org">ticctoc@ietf.org</a>&gt;;<br>&gt; &gt; &gt;&gt; &lt;<a ymai=
lto=3D"mailto:mpls-tp@ietf.org" href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ie=
tf.org</a>&gt;<br>&gt;
 &gt; &gt;&gt; Subject: RE: [mpls] [PWE3] 1588 over MPLS draft<br>&gt; &gt;=
 &gt;&gt;<br>&gt; &gt; &gt;&gt;&gt; Hi Mach,<br>&gt; &gt; &gt;&gt;&gt;<br>&=
gt; &gt; &gt;&gt;&gt; When a service provider wants to create these PTP LSP=
s, what is<br>&gt; &gt; wrong<br>&gt; &gt; &gt;&gt;&gt; with allocating a r=
ange of labels for this purpose? This is purely<br>&gt; &gt; a<br>&gt; &gt;=
 &gt;&gt;&gt; software exercise. There are 2 million labels available to ea=
ch<br>&gt; &gt; node,<br>&gt; &gt; &gt;&gt;&gt; why can't some of them be a=
llocated by software to PTP?<br>&gt; &gt; &gt;&gt;&gt;<br>&gt; &gt; &gt;&gt=
;&gt; In theory what you say is correct and should work, but in practice<br=
>&gt; &gt; &gt;&gt;&gt; there is a function called 1-step Transparent clock=
ing that<br>&gt; &gt; requires<br>&gt; &gt; &gt;&gt;&gt; time stamping at t=
he PHY (immediately when the packet is received<br>&gt; &gt; or<br>&gt; &gt=
; &gt;&gt;&gt; transmitted). PHY chips don't have CAM or lots of
 memory to store a<br>&gt; &gt; &gt;&gt;&gt; few thousand random labels. Th=
e label range will solve that problem<br>&gt; &gt; &gt;&gt;&gt; and is cons=
istent with MPLS architecture.<br>&gt; &gt; &gt;&gt;&gt;<br>&gt; &gt; &gt;&=
gt;&gt; Thanks,<br>&gt; &gt; &gt;&gt;&gt; Shahram<br>&gt; &gt; &gt;&gt;&gt;=
<br>&gt; &gt; &gt;&gt;&gt; -----Original Message-----<br>&gt; &gt; &gt;&gt;=
&gt; From: Mach Chen [mailto:<a ymailto=3D"mailto:mach@huawei.com" href=3D"=
mailto:mach@huawei.com">mach@huawei.com</a>]<br>&gt; &gt; &gt;&gt;&gt; Sent=
: Wednesday, July 14, 2010 1:53 AM<br>&gt; &gt; &gt;&gt;&gt; To: S. Davari;=
 Jia HE; Shahram Davari<br>&gt; &gt; &gt;&gt;&gt; Cc: <a ymailto=3D"mailto:=
mpls@ietf.org" href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a ymailto=
=3D"mailto:pwe3@ietf.org" href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a>; =
<a ymailto=3D"mailto:ticctoc@ietf.org" href=3D"mailto:ticctoc@ietf.org">tic=
ctoc@ietf.org</a>; mpls-<br>&gt; &gt; <a ymailto=3D"mailto:tp@ietf.org"
 href=3D"mailto:tp@ietf.org">tp@ietf.org</a><br>&gt; &gt; &gt;&gt;&gt; Subj=
ect: Re: [mpls] [PWE3] 1588 over MPLS draft<br>&gt; &gt; &gt;&gt;&gt;<br>&g=
t; &gt; &gt;&gt;&gt; Hi Shahram,<br>&gt; &gt; &gt;&gt;&gt;<br>&gt; &gt; &gt=
;&gt;&gt; From the view of implementation, there is no more difference<br>&=
gt; &gt; between<br>&gt; &gt; &gt;&gt;&gt; SHOULD<br>&gt; &gt; &gt;&gt;&gt;=
 and MUST :-)<br>&gt; &gt; &gt;&gt;&gt; For me, the Label Range is more lik=
e a mechanim to notify related<br>&gt; &gt; &gt;&gt;&gt; nodes that<br>&gt;=
 &gt; &gt;&gt;&gt; some LSPs are dedicated for PTP messages other than the =
chips<br>&gt; &gt; memory<br>&gt; &gt; &gt;&gt;&gt; limitation, because the=
 memory restriction is always there whatever<br>&gt; &gt; &gt;&gt;&gt; you =
use<br>&gt; &gt; &gt;&gt;&gt; Label Range or not.<br>&gt; &gt; &gt;&gt;&gt;=
 IMHO, since the objective is to tell related MPLS nodes which LSPs<br>&gt;=
 &gt; are<br>&gt; &gt; &gt;&gt;&gt; PTP<br>&gt; &gt; &gt;&gt;&gt;
 LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough<br>&gt; =
&gt; and<br>&gt; &gt; &gt;&gt;&gt; seems<br>&gt; &gt; &gt;&gt;&gt; more com=
mon. And it will avoid the strict requirement of "the<br>&gt; &gt; network =
and<br>&gt; &gt; &gt;&gt;&gt; all nodes required to support the Label range=
".<br>&gt; &gt; &gt;&gt;&gt; In addition, there should be some mechanims(e.=
g., ISIS/OSPF<br>&gt; &gt; &gt;&gt;&gt; extensions) for<br>&gt; &gt; &gt;&g=
t;&gt; nodes to advertise their PTP capability hence to help PTP LSPs<br>&g=
t; &gt; &gt;&gt;&gt; computation.<br>&gt; &gt; &gt;&gt;&gt;<br>&gt; &gt; &g=
t;&gt;&gt; Best regards,<br>&gt; &gt; &gt;&gt;&gt; Mach<br>&gt; &gt; &gt;&g=
t;&gt;<br>&gt; &gt; &gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt; ----------------=
----------------------------------<br>&gt; &gt; &gt;&gt;&gt; From: "S. Dava=
ri" &lt;<a ymailto=3D"mailto:davarish@yahoo.com" href=3D"mailto:davarish@ya=
hoo.com">davarish@yahoo.com</a>&gt;<br>&gt; &gt; &gt;&gt;&gt; Sent:
 Wednesday, July 14, 2010 2:31 PM<br>&gt; &gt; &gt;&gt;&gt; To: "Jia HE" &l=
t;<a ymailto=3D"mailto:hejia@huawei.com" href=3D"mailto:hejia@huawei.com">h=
ejia@huawei.com</a>&gt;; "Shahram Davari"<br>&gt; &gt; &lt;<a ymailto=3D"ma=
ilto:davari@broadcom.com" href=3D"mailto:davari@broadcom.com">davari@broadc=
om.com</a>&gt;<br>&gt; &gt; &gt;&gt;&gt; Cc: &lt;<a ymailto=3D"mailto:mpls@=
ietf.org" href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;; &lt;<a ymail=
to=3D"mailto:pwe3@ietf.org" href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a>=
&gt;; &lt;<a ymailto=3D"mailto:ticctoc@ietf.org" href=3D"mailto:ticctoc@iet=
f.org">ticctoc@ietf.org</a>&gt;;<br>&gt; &gt; &gt;&gt;&gt; &lt;<a ymailto=
=3D"mailto:mpls-tp@ietf.org" href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.=
org</a>&gt;<br>&gt; &gt; &gt;&gt;&gt; Subject: Re: [mpls] [PWE3] 1588 over =
MPLS draft<br>&gt; &gt; &gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt; Hi Jia,<=
br>&gt; &gt; &gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt; Label range is =
a SHOULD
 requirements and not MUST. The reason for<br>&gt; &gt; Label<br>&gt; &gt; =
&gt;&gt;&gt;&gt; Range is<br>&gt; &gt; &gt;&gt;&gt;&gt; mainly for PHY chip=
s that don't have large memory and can't store<br>&gt; &gt; a<br>&gt; &gt; =
&gt;&gt;&gt;&gt; lot of<br>&gt; &gt; &gt;&gt;&gt;&gt; Labels. Otherwise the=
 PTP LSP is setup via signaling that<br>&gt; &gt; specifies the<br>&gt; &gt=
; &gt;&gt;&gt;&gt; LSP as<br>&gt; &gt; &gt;&gt;&gt;&gt; carrying 1588.<br>&=
gt; &gt; &gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt; So the answer is th=
at if a Label range is used it must be a Global<br>&gt; &gt; range<br>&gt; =
&gt; &gt;&gt;&gt;&gt; within<br>&gt; &gt; &gt;&gt;&gt;&gt; a network and sh=
ould not be used by any router for other<br>&gt; &gt; applications.<br>&gt;=
 &gt; &gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt; Thanks,<br>&gt; &gt; &=
gt;&gt;&gt;&gt; Shahram<br>&gt; &gt; &gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;=
&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt;
 ________________________________<br>&gt; &gt; &gt;&gt;&gt;&gt; From: Jia H=
E &lt;<a ymailto=3D"mailto:hejia@huawei.com" href=3D"mailto:hejia@huawei.co=
m">hejia@huawei.com</a>&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt; To: Shahram Davar=
i &lt;<a ymailto=3D"mailto:davari@broadcom.com" href=3D"mailto:davari@broad=
com.com">davari@broadcom.com</a>&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt; Cc: <a y=
mailto=3D"mailto:mpls@ietf.org" href=3D"mailto:mpls@ietf.org">mpls@ietf.org=
</a>; <a ymailto=3D"mailto:pwe3@ietf.org" href=3D"mailto:pwe3@ietf.org">pwe=
3@ietf.org</a>; <a ymailto=3D"mailto:ticctoc@ietf.org" href=3D"mailto:ticct=
oc@ietf.org">ticctoc@ietf.org</a>; mpls-<br>&gt; &gt; <a ymailto=3D"mailto:=
tp@ietf.org" href=3D"mailto:tp@ietf.org">tp@ietf.org</a><br>&gt; &gt; &gt;&=
gt;&gt;&gt; Sent: Tue, July 13, 2010 9:50:37 PM<br>&gt; &gt; &gt;&gt;&gt;&g=
t; Subject: Re: [mpls] [PWE3] 1588 over MPLS draft<br>&gt; &gt; &gt;&gt;&gt=
;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt; Hi Shahra=
m,<br>&gt; &gt;
 &gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt; One question about "PTP Lab=
el Range":<br>&gt; &gt; &gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt; To m=
y knowledge, label in MPLS network is a local&nbsp; matter. For<br>&gt; &gt=
; &gt;&gt;&gt;&gt; example, we<br>&gt; &gt; &gt;&gt;&gt;&gt; may<br>&gt; &g=
t; &gt;&gt;&gt;&gt; have per-interface or per-platform label space. Will&nb=
sp; this<br>&gt; &gt; specificed<br>&gt; &gt; &gt;&gt;&gt;&gt; "PTP<br>&gt;=
 &gt; &gt;&gt;&gt;&gt; Label<br>&gt; &gt; &gt;&gt;&gt;&gt; Range" conflict =
with the current in-use labels&nbsp; for common LSPs?<br>&gt; &gt; &gt;&gt;=
&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt; B.R.<b=
r>&gt; &gt; &gt;&gt;&gt;&gt; Jia<br>&gt; &gt; &gt;&gt;&gt;&gt;<br>&gt; &gt;=
 &gt;&gt;&gt;&gt; ----- Original Message -----<br>&gt; &gt; &gt;&gt;&gt;&gt=
;&gt; From: Shahram&nbsp; &nbsp; Davari<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; T=
o: <a ymailto=3D"mailto:ticctoc@ietf.org"
 href=3D"mailto:ticctoc@ietf.org">ticctoc@ietf.org</a> ; <a ymailto=3D"mail=
to:mpls@ietf.org" href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> ; <a ymai=
lto=3D"mailto:mpls-tp@ietf.org" href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ie=
tf.org</a> ;<br>&gt; &gt; <a ymailto=3D"mailto:pwe3@ietf.org" href=3D"mailt=
o:pwe3@ietf.org">pwe3@ietf.org</a><br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; Sent: =
Thursday, July 08, 2010 3:12 AM<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; Subject: =
[PWE3] 1588 over MPLS draft<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt;<br>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; Hi All,<br>&gt; &gt;=
 &gt;&gt;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; Please find attache=
d our first draft of 1588 over MPLS.&nbsp; &nbsp; Since<br>&gt; &gt; we<br>=
&gt; &gt; &gt;&gt;&gt;&gt;&gt; have<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; some<=
br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; technical issues converting the Word form=
at to Txt we&nbsp; &nbsp; couldn=E2=80=99t<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt=
;
 upload<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; the<br>&gt; &gt; &gt;&gt;&gt;&gt;=
&gt; draft before the cut-off date. However we will&nbsp; &nbsp; present th=
e<br>&gt; &gt; draft<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; in the<br>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; next<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; IETF meeting an=
d will upload the draft after the&nbsp; &nbsp; meeting.<br>&gt; &gt; &gt;&g=
t;&gt;&gt;&gt;<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; Note that the main WG is T=
icToc but may require&nbsp; &nbsp; consultation<br>&gt; &gt; with<br>&gt; &=
gt; &gt;&gt;&gt;&gt;&gt; MPLS<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; and<br>&gt;=
 &gt; &gt;&gt;&gt;&gt;&gt; PWE3 WGs.<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt;<br>&=
gt; &gt; &gt;&gt;&gt;&gt;&gt; Thanks,<br>&gt; &gt; &gt;&gt;&gt;&gt;&gt; Sha=
hram Davari<br></div></div>=0A</div><br></body></html>
--0-1708473949-1279657193=:11753--


From lberger@labn.net  Tue Jul 20 14:19:27 2010
Return-Path: <lberger@labn.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 525EA3A6C82 for <mpls@core3.amsl.com>; Tue, 20 Jul 2010 14:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=-0.253, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 kQE41PgKBEKf for <mpls@core3.amsl.com>; Tue, 20 Jul 2010 14:19:22 -0700 (PDT)
Received: from cpoproxy3-pub.bluehost.com (cpoproxy3-pub.bluehost.com [67.222.54.6]) by core3.amsl.com (Postfix) with SMTP id 5989B3A6809 for <mpls@ietf.org>; Tue, 20 Jul 2010 14:19:15 -0700 (PDT)
Received: (qmail 20661 invoked by uid 0); 20 Jul 2010 21:19:31 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 20 Jul 2010 21:19:31 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=HIdFrdVP+hpHK8LH+aTs5I+l4RXFS1pcgA0jJQ+ro6WyHXHDTPLMRo4iP+4tPy3jZDTh50nNhFQH2IyvKymwnCPupc7i6/siwEtTNQkogvmYb1nCEJFgGsTYrnfO9xUL;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1ObKDq-00017O-Tu; Tue, 20 Jul 2010 15:19:31 -0600
Message-ID: <4C4612F0.9050208@labn.net>
Date: Tue, 20 Jul 2010 17:19:44 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>
References: <D29E470202D67745B61059870F433B5402245F75@XMB-RCD-202.cisco.com>
In-Reply-To: <D29E470202D67745B61059870F433B5402245F75@XMB-RCD-202.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: mpls@ietf.org, ccamp@ietf.org, draft-ietf-ccamp-mpls-tp-cp-frameworks@tools.ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [CCAMP] Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 21:19:27 -0000

Eric,
	Thank you for the comments.  Please see below for in-line responses.

On 7/12/2010 10:33 AM, Eric Osborne (eosborne) wrote:
> I have a few questions.  Nothing major, as the draft is in general
> pretty solid.
>
>
>
> 1) Section 4.1 reviews existing GMPLS functionality and describes
> applicability to TP.  Section 4.1.8 defines LSP hierarchy but doesn't
> say anything about how it applies to TP.  It probably needs a line like
> "Hierarchical LSPs may be used in MPLS-TP at the discretion of the
> network operator" or something similar ot what's in other subsections of
> 4.1.
>

Good point!  Something along the lines of the following will be added:

   LSP hierarchy is expected to play an important role in MPLS-TP
   networks, particularly in the context of scaling and recovery.

>
> 2) Some of section 4.1.9 is out of sync with the surviveability
> framework (draft-ietf-mpls-tp-survive-fwk)
>
>   - survive-fwk draws a distinction between protection and restoration
> that  cp-framework lumps under 'recovery'.  It may be worth calling out
> both protection and restoration as separate things.

This is a carry over from GMPLS terminology, see [RFC4427], [RFC4426], 
[RFC4872], [RFC4873]

>
> - Section 4.1.9 lists five recovery types:
>
>       - 1+1 bidirectional protection for P2P LSPs
>       - 1+1 unidirectional protection for P2MP LSPs
>       - 1:n (including 1:1) protection with or without extra traffic
>       - Rerouting without extra traffic (sometimes known as soft
>         rerouting), including shared mesh restoration
>       - Full LSP rerouting
>
>
> I don't see where these five types come from.

from GMPLS.  The five types should be identified in that context and can 
be used to support [TP-SURVIVE].  The text should make this more clear.

> rfc5654 requirements R65
> and R67 list five MUST types (bidir 1+1 p2p, unidir 1+1 p2p, unidir 1+1
> p2mp, bidir 1:n p2p, unidir 1:n p2mp) and one optional (undir 1:n p2p).
> R68 requires 1:n (including 1:1) ahread mesh recovery.
>
> How do the five types in section 4.1. 9 map to the requirements in
> rfc5654?

I must be missing something.  This looks like a straightforward mapping. 
  (The table also shows mapping of requirements to mechanisms) for example:

At first glance I don't see unidir 1+1 p2p in sec. 4.1.9,

it's the second in the list.

> although perhaps it's implied in 'rerouting without extra traffic'.
> 'Full LSP rerouting' also seems like it may mean something specific to
> whomever wrote it but as far as I can tell there's no explicit
> definition of 'Full LSP rerouting' (as opposed to partial?  as opposed
> to something other than rerouting?) anywhere in rfc5654 or survive-fwk.
> And 'soft rerouting appears to be survive-fwk's 'soft restoration'.
>
> 3) Section 4.1.9, "it's use is not precluded" , s/it's/its/
>

Thanks!

>
> 4) Section 4.4.1 is entitled "MPLS to MPLS-TP Interworking".  The
> section talks about " interworking of MPLS-TE and GMPLS control plane",
> so shouldn't the section be "MPLS-TE to MPLS-TP Interworking"?  Unless
> things like LDP-to-TP interworking are in someone's plans, I think "TE
> to TP Interworking" is a better fit.

Agreed.  Changed to "MPLS-TE to MPLS-TP LSP Control Plane Interworking"

Thanks again!

Lou
>
>
>
>
>
>
>
> eric
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>
>
>

From venkatflex@gmail.com  Tue Jul 20 22:40:12 2010
Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D7E53A6B2E for <mpls@core3.amsl.com>; Tue, 20 Jul 2010 22:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, HTML_MESSAGE=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 UpcEWWJnwsx2 for <mpls@core3.amsl.com>; Tue, 20 Jul 2010 22:40:09 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 55EAF3A679F for <mpls@ietf.org>; Tue, 20 Jul 2010 22:40:09 -0700 (PDT)
Received: by pvd12 with SMTP id 12so3598060pvd.31 for <mpls@ietf.org>; Tue, 20 Jul 2010 22:40:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=Cd2GdssZ+Texvgm+V7oZuTA19LZz9CMj13c532vRCGE=; b=dlWwBVV+enUALUABAhj7xIH2BU1+KTynFsNVWDu29poGexrbJ+4AqYevn9/GEmPrmJ qIaEIxRJ2/GIKWvx2O1PQg155chN9XM/+uZB3sgZNrr0uJSeXN/nJnK4HV04SFYZ19/i nC5VxqwAnsjA95SW6hEJawLgTPMmYnyunQvA4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=h3lTofxr2duOrAEc++w7NIGEWdt0pjc2jga/gg/Z2A5l7Npo4rYNayxmxo1CqK6uXw 3wWTwkIpAzjAOpHEqOFvXj0tT1sXvL6wU778aF/EtDt+JwDwlFzAJixu4OTchTY7BBVx 1paf1ULHUUq5I94++JAqJwvO6IqNQizikpeTc=
MIME-Version: 1.0
Received: by 10.142.48.18 with SMTP id v18mr10902291wfv.101.1279690519659;  Tue, 20 Jul 2010 22:35:19 -0700 (PDT)
Received: by 10.142.77.1 with HTTP; Tue, 20 Jul 2010 22:35:19 -0700 (PDT)
In-Reply-To: <AANLkTim7PAn8b-K0dq-i-k6Qx3LJkm5HwaV02QHDFFQo@mail.gmail.com>
References: <007101cb27b0$5b3c58c0$82626e0a@china.huawei.com> <AANLkTim7PAn8b-K0dq-i-k6Qx3LJkm5HwaV02QHDFFQo@mail.gmail.com>
Date: Wed, 21 Jul 2010 11:05:19 +0530
Message-ID: <AANLkTimwbhGi0N3pY6pH3fYPqcTCtulz_q6jjY0XWHMo@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: Jie Dong <dongjie_dj@huawei.com>, mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary=000e0cd50aa8d8c633048bdf2a5a
Subject: Re: [mpls] New Draft Notification: draft-dong-mpls-rsvp-te-plr-designation-00
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jul 2010 05:40:12 -0000

--000e0cd50aa8d8c633048bdf2a5a
Content-Type: text/plain; charset=ISO-8859-1

>
> Hi,
> This draft is good in selecting the PLRs in the initial LSP setup itself.
> But can this draft handle the dynamic PLR node change?
> Do you have any thought on constrcuting the new TLVs to send the new EROs
> in the established LSP to indicate the new PLR nodes?
>
> Do you really think that administrator should know about all the transit
> nodes of the LSP? I think, this is possible with the help of CSPF but
> collecting the informations about transit node's resources and other
> informations may be tough.
>
> Thanks,
> Venkat.
>
> On Tue, Jul 20, 2010 at 7:37 AM, Jie Dong <dongjie_dj@huawei.com> wrote:
>
>>
>> Dear all,
>>
>> We have submitted a new internet draft "Designation of PLRs in RSVP-TE
>> Fast
>> Reroute"
>>
>> The URL is:
>> http://tools.ietf.org/html/draft-dong-mpls-rsvp-te-plr-designation-00
>>
>> The abstract is as follows:
>>
>> This document defines RSVP-TE extensions which enable the ingress node to
>> designate particular LSRs along the path as Points of Local Repair (PLRs)
>> of
>> the protected LSP, and further indicate the protection type of each PLR.
>> These mechanisms could enhance the control over the establishment of
>> backup
>> LSPs, and also could save the resources needed for establishing and
>> maintaining unnecessary backup LSPs.
>>
>> Any comments and suggestions are appreciated.
>>
>>
>> Best regards,
>> Jie
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>
>
>
> --
> Best Regards,
> Venkatesan Mahalingam.
>



-- 
Best Regards,
Venkatesan Mahalingam.

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

<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>Hi,</div>
<div>This draft is good in selecting the PLRs in the initial LSP setup itse=
lf. But can this draft handle the dynamic PLR node change?</div>
<div>Do you have any thought on constrcuting the new TLVs to send the new E=
ROs in the established LSP to indicate the new PLR nodes?</div>
<div>=A0</div>
<div>Do you really think that administrator should know about all the trans=
it nodes of the LSP? I think, this is possible with the help of CSPF but co=
llecting the informations about transit node&#39;s resources and other info=
rmations may be tough.</div>

<div>=A0</div>
<div>Thanks,</div>
<div>Venkat.=20
<div>
<div></div>
<div class=3D"h5"><br>On Tue, Jul 20, 2010 at 7:37 AM, Jie Dong <span dir=
=3D"ltr">&lt;<a href=3D"mailto:dongjie_dj@huawei.com" target=3D"_blank">don=
gjie_dj@huawei.com</a>&gt;</span> wrote:<br></div></div></div>
<div>
<div></div>
<div class=3D"h5">
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>Dear all,<br><br>We have sub=
mitted a new internet draft &quot;Designation of PLRs in RSVP-TE Fast<br>Re=
route&quot;<br>
<br>The URL is:<br><a href=3D"http://tools.ietf.org/html/draft-dong-mpls-rs=
vp-te-plr-designation-00" target=3D"_blank">http://tools.ietf.org/html/draf=
t-dong-mpls-rsvp-te-plr-designation-00</a><br><br>The abstract is as follow=
s:<br>
<br>This document defines RSVP-TE extensions which enable the ingress node =
to<br>designate particular LSRs along the path as Points of Local Repair (P=
LRs) of<br>the protected LSP, and further indicate the protection type of e=
ach PLR.<br>
These mechanisms could enhance the control over the establishment of backup=
<br>LSPs, and also could save the resources needed for establishing and<br>=
maintaining unnecessary backup LSPs.<br><br>Any comments and suggestions ar=
e appreciated.<br>
<br><br>Best regards,<br>Jie<br><br>_______________________________________=
________<br>mpls mailing list<br><a href=3D"mailto:mpls@ietf.org" target=3D=
"_blank">mpls@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listi=
nfo/mpls" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><=
br>
</blockquote></div><br><br clear=3D"all"><br></div></div>-- <br>Best Regard=
s,<br><font color=3D"#888888">Venkatesan Mahalingam.<br></font></blockquote=
></div><br><br clear=3D"all"><br>-- <br>Best Regards,<br>Venkatesan Mahalin=
gam.<br>

--000e0cd50aa8d8c633048bdf2a5a--

From dongjie_dj@huawei.com  Wed Jul 21 01:22:29 2010
Return-Path: <dongjie_dj@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E9CF33A6802 for <mpls@core3.amsl.com>; Wed, 21 Jul 2010 01:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.073
X-Spam-Level: 
X-Spam-Status: No, score=-4.073 tagged_above=-999 required=5 tests=[AWL=-1.474, BAYES_00=-2.599]
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 YELW-XBHs67c for <mpls@core3.amsl.com>; Wed, 21 Jul 2010 01:22:28 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 7C3C63A6B63 for <mpls@ietf.org>; Wed, 21 Jul 2010 01:22:28 -0700 (PDT)
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 <0L5W00MWIF75Z4@szxga04-in.huawei.com> for mpls@ietf.org; Wed, 21 Jul 2010 16:21:05 +0800 (CST)
Received: from 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 <0L5W0005SF75JD@szxga04-in.huawei.com> for mpls@ietf.org; Wed, 21 Jul 2010 16:21:05 +0800 (CST)
Received: from d65110 ([10.110.98.130]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5W002RHF74VY@szxml06-in.huawei.com> for mpls@ietf.org; Wed, 21 Jul 2010 16:21:05 +0800 (CST)
Date: Wed, 21 Jul 2010 16:21:04 +0800
From: Jie Dong <dongjie_dj@huawei.com>
In-reply-to: <AANLkTimwbhGi0N3pY6pH3fYPqcTCtulz_q6jjY0XWHMo@mail.gmail.com>
To: 'venkatesan mahalingam' <venkatflex@gmail.com>, 'mpls' <mpls@ietf.org>
Message-id: <019e01cb28ad$a9b1b4c0$82626e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsoloOzaPekVUGjS7e35GrGPLHH3QAEg/gw
References: <007101cb27b0$5b3c58c0$82626e0a@china.huawei.com> <AANLkTim7PAn8b-K0dq-i-k6Qx3LJkm5HwaV02QHDFFQo@mail.gmail.com> <AANLkTimwbhGi0N3pY6pH3fYPqcTCtulz_q6jjY0XWHMo@mail.gmail.com>
Subject: Re: [mpls] New Draft Notification: draft-dong-mpls-rsvp-te-plr-designation-00
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jul 2010 08:22:30 -0000

Dear Venkat,

Thanks for your comments, and please see my replies with [Jie].

                Hi,
                This draft is good in selecting the PLRs in the initial LSP
setup itself. But can this draft handle the dynamic PLR node change?
                Do you have any thought on constrcuting the new TLVs to send
the new EROs in the established LSP to indicate the new PLR nodes?

[Jie] Good question. In this version we mainly describes the PLR designation
during the initialization of LSP. For dynamic PLR change after setup, we
would like to hear some voice from operators. If they need this dynamic
function, we can provide it through some further extensions. Your
suggestions on this are really appreciated.
                
                Do you really think that administrator should know about all
the transit nodes of the LSP? I think, this is possible with the help of
CSPF but collecting the informations about transit node's resources and
other informations may be tough.

[Jie] In some scenarios the administrators may explicitly specify the entire
path of the LSP, in other cases they may explicitly specify a portion of the
path, and in both cases they can designate the PLRs based on their knowledge
about the network. So knowing all the transit nodes is not a MUST for PLR
designation. As long as they know some nodes along the path, they could
choose some of them as PLRs. The path may be determined using CSPF, or just
based on planning and policy. 


Best regards,
Jie





________________________________

        From: venkatesan mahalingam [mailto:venkatflex@gmail.com]
        Sent: Wednesday, July 21, 2010 1:35 PM
        To: Jie Dong; mpls
        Subject: Re: [mpls] New Draft Notification:
draft-dong-mpls-rsvp-te-plr-designation-00
       
       

                Hi,
                This draft is good in selecting the PLRs in the initial LSP
setup itself. But can this draft handle the dynamic PLR node change?
                Do you have any thought on constrcuting the new TLVs to send
the new EROs in the established LSP to indicate the new PLR nodes?
                
                Do you really think that administrator should know about all
the transit nodes of the LSP? I think, this is possible with the help of
CSPF but collecting the informations about transit node's resources and
other informations may be tough.
                
                Thanks,
                Venkat.

                On Tue, Jul 20, 2010 at 7:37 AM, Jie Dong
<dongjie_dj@huawei.com> wrote:
               


                        Dear all,
                       
                        We have submitted a new internet draft "Designation
of PLRs in RSVP-TE Fast
                        Reroute"
                       
                        The URL is:
 
http://tools.ietf.org/html/draft-dong-mpls-rsvp-te-plr-designation-00
                       
                        The abstract is as follows:
                       
                        This document defines RSVP-TE extensions which
enable the ingress node to
                        designate particular LSRs along the path as Points
of Local Repair (PLRs) of
                        the protected LSP, and further indicate the
protection type of each PLR.
                        These mechanisms could enhance the control over the
establishment of backup
                        LSPs, and also could save the resources needed for
establishing and
                        maintaining unnecessary backup LSPs.
                       
                        Any comments and suggestions are appreciated.
                       
                       
                        Best regards,
                        Jie
                       
                        _______________________________________________
                        mpls mailing list
                        mpls@ietf.org
                        https://www.ietf.org/mailman/listinfo/mpls
                       




                --
                Best Regards,
                Venkatesan Mahalingam.
               




        --
        Best Regards,
        Venkatesan Mahalingam.
       





From lucyyong@huawei.com  Wed Jul 21 08:27:34 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59C693A6359; Wed, 21 Jul 2010 08:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.633
X-Spam-Level: 
X-Spam-Status: No, score=-1.633 tagged_above=-999 required=5 tests=[AWL=0.366,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 WoymtF5SNl0X; Wed, 21 Jul 2010 08:27:33 -0700 (PDT)
Received: from szxga05-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 330AA3A683A; Wed, 21 Jul 2010 08:27:32 -0700 (PDT)
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 <0L5W003NCYY8CO@szxga05-in.huawei.com>; Wed, 21 Jul 2010 23:27:44 +0800 (CST)
Received: from 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 <0L5W00M9HYY75U@szxga05-in.huawei.com>; Wed, 21 Jul 2010 23:27:43 +0800 (CST)
Received: from y736742 ([10.124.12.56]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5W00DTQYY55D@szxml04-in.huawei.com>; Wed, 21 Jul 2010 23:27:43 +0800 (CST)
Date: Wed, 21 Jul 2010 10:27:39 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <201007201832.o6KIWZtg065155@harbor.orleans.occnc.com>
To: curtis@occnc.com
Message-id: <009e01cb28e9$42b76f80$380c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsoOnGk27Zkod03QvWtO+ld7ToVfAArjDQw
References: "Your message of Fri, 16 Jul 2010 14:05:46 CDT." <00d801cb2519$e6f16160$380c7c0a@china.huawei.com> <201007201832.o6KIWZtg065155@harbor.orleans.occnc.com>
Cc: mpls@ietf.org, 'pwe3' <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware Transport
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jul 2010 15:27:34 -0000

SNIP
> 
> 
> Lucy,
> 
> Any modifications to the use of the TC bits is almost certainly a
> non-starter.  I thought that was also mentioned in the last meeting.
> We'll see what comments come out of the meeting this time.
> 
> Curtis
> 
> 
[LY] We are glad to discuss the alternate solution. It is clear to me that
flow label serves different function than PW label and LSP label and its TC
bits are not defined yet.

Lucy
> >   _____
> >
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Yong
> > Lucy
> > Sent: Tuesday, April 27, 2010 5:37 PM
> > To: 'pwe3'; mpls@ietf.org
> > Subject: [mpls] Large FLow Classificaiton in Flow Aware Transport
> >
> >
> >
> > Hi,
> >
> > I recap the comments raised during IETF77 meeting. Some are from the
> PWE3
> > meeting and some from offline discussions. Hope this gives some
> > clarification and bring up further mailing discussion.
> >
> > The draft proposal (draft-yong-pwe3-enhanced-ecmp-lfat-01) is to use one
> of
> > the TC bits in the flow label to indicate large flow. TC bits in flow
> label
> > described in FAT-PW are not used and are not interpreted by LSR.
> >
> > Comments and Responses:
> >
> > 1) No use for the proposal. would need to update all equipment to get
> this
> > to work.  A while ago we agreed to not standardize ECMP process.
> >
> > Lucy: Some carriers see the value of it. There is no need to update all
> > equipment to get this work. The backward compatibility is supported as
> > described in section 6. Partially upgrading can improve some segments
> while
> > keeping other segments remain the same. The intention of the draft is
> not
> > for standardizing ECMP process. It is about standardizing large flow
> > classification indication in PSN. The draft layout may lead this
> confusion.
> > We will modify the draft and move enhanced ECMP process description to
> > appendix as one implementation example to use large flow classification.
> We
> > will change the draft title to "large flow classification in flow aware
> > transport over PSN" and upload soon.
> >
> > 2) would need to go through MPLS WG for issue on standardizing ECMP.
> Label
> > stack is always MPLS label stack so MPLS WG would need to OK change of
> TC
> > semantics.  Needs a co-review in MPLS WG and they must approve.
> >
> > Lucy: The draft is not for standardizing ECMP. (sorry for the
confusion).
> > The draft does not change the semantics of a label stack entry defined
> by
> > RFC3032 because the flow label is never on the top of label stack. As
> FAT-PW
> > draft indicates that the interpretation of TC bits in the flow label by
> LSR
> > is undefined. This draft proposes one definition.
> >
> > 3) If you can get MPLS WG to agree, one of the issues is that you are
> > marking at a PE where the PE may or may not know what is or isn't a big
> > flow.  Limitations on PEs ability to determine what a big flow is. Would
> > need to tell easily and ubiquitously what a big flow is.
> >
> > Lucy: In our proposal, large flows in this context are the top rate
> ranked
> > flows. It is relevant to other flows not the link capacity. Enhanced
> ECMP
> > process just needs a small set of large flows for load balancing,
> therefore,
> > it can pick by statistics, i.e. not necessary all the large flows. The
> > method works well even some large flows placed by hashing function. The
> > backward compatibility in the draft would deal with this.
> >
> > 4) we haven't standardized anything on ECMP. Many will look at bottom of
> > stack to look at IP address or anything else to hash on. If I'm a PE
> router
> > with lots of L3VPN traffic and some PWs, how do I know if this is a flow
> > label or VPN label.
> >
> > Lucy: This is not for ECMP standardization. We propose one method to
> > differentiate the flow label from IP packet, PW label, and LSP label at
> the
> > bottom of label stack. This is: check the first nibble to separate IP
> and
> > MPLS packets; for MPLS packets, use TTL value (=0) to check the flow
> label
> > packets.
> >
> > 5) this is addressing an important issue.  Simulations showed a lot of
> > traffic and the flows are large enough.  Cases in well engineered
> network
> > where situation is much worse than shown.  Drafts have been submitting
> in
> > past that gained no traction.  To use a method other than just hashing,
> but
> > may be ways to do this without changing label or MPLS.
> >
> > Lucy: The simulation use Internet traffic pattern. For carrier network,
> it
> > has a lot of L2VPN traffic carried as single flow, so the situation is
> > worse. We work on additional simulation to include such type of traffic.
> It
> > confirms the statement. As Internet traffic grow with higher and higher
> bit
> > rate flows, the problem will become more and more severe. We need to aim
> on
> > this real problem.
> >
> > 6) there was a proposal to solve this 10 years ago with no protocol
> changes.
> > This is not needed.
> >
> > Lucy: Need clarification which proposal refers to. If it is OMP, the
> draft
> > proposes the different method from OMP. OMP suggest using routing
> protocol
> > to advertise individual ECMP path TE information in the network. The
> draft
> > is about large flow classification indication so LSR can use a set of
> large
> > flows in performing load balance over ECMP paths effectively.
> >
> > 7) Changes too much about MPLS processing
> >
> > Lucy: It is not that additional process. Gaining is obvious too.
> >
> > 8) did the simulations deal with coming and going of flows? How to
> address
> > flow fluctuation?
> >
> > Lucy: we are working on additional simulations. That will include flow
> > coming and going situation and include much higher bit rate flows, and a
> > "permanent flow" whose rate may change over time to make it as small
> flow at
> > a time or a large flow at another time. The latter case likes a VPWS as
> a
> > flow. Be glad to show some simulation result to the group.
> >
> > 9) Signaling can be used for this, why using marking?
> >
> > Lucy: today, signaling a PW is used per a service basis such as VPWS or
> > VPLS. But one VPWS or VPLS may contain many flows, the draft address
> this
> > situation. It is hard for carrier to signal individual large flow within
> > VPLS over PSN networks.
> >
> > 10) If there is incentive to enhanced ECMP, why not do large flow
> > recognition at local LSR for the purpose? PE based large flow
> recognition
> > and marking do not apply well at individual LSR.
> >
> > Lucy: High bit rate flow is relevant to other flows. Operator can set
> large
> > flow criteria. Having each LSR performs larger flow recognition add
> complex
> > to each LSR and may impact the service performance. Large flow
> > classification is easier, we think. Today, DiffServ enables the network
> to
> > perform different service treatments. Large flow classification enables
> > network to perform different flow treatments over ECMP operation.
> >
> > Comments and suggestion are welcome.
> >
> >
> > Regards,
> > Lucy


From lucyyong@huawei.com  Wed Jul 21 08:32:34 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADC5E3A67F4; Wed, 21 Jul 2010 08:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.618
X-Spam-Level: 
X-Spam-Status: No, score=-0.618 tagged_above=-999 required=5 tests=[AWL=-0.723, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, 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 vpBD9GvSOGcj; Wed, 21 Jul 2010 08:32:32 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 5FAA53A6774; Wed, 21 Jul 2010 08:32:31 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5W00JE2Z6875@szxga02-in.huawei.com>; Wed, 21 Jul 2010 23:32:33 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5W00870Z68WG@szxga02-in.huawei.com>; Wed, 21 Jul 2010 23:32:32 +0800 (CST)
Received: from y736742 ([10.124.12.56]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5W00DBKZ655D@szxml04-in.huawei.com>; Wed, 21 Jul 2010 23:32:31 +0800 (CST)
Date: Wed, 21 Jul 2010 10:32:28 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <5E893DB832F57341992548CDBB333163984487C7AE@EMBX01-HQ.jnpr.net>
To: 'John E Drake' <jdrake@juniper.net>, curtis@occnc.com
Message-id: <00a501cb28e9$eeae1c30$380c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsoOhgYXyrbBhBYRfO6Kq+DEv5LGgAAMQxgACulKzA=
References: "Your message of Fri, 16 Jul 2010 14:05:46 CDT." <00d801cb2519$e6f16160$380c7c0a@china.huawei.com> <201007201832.o6KIWZtg065155@harbor.orleans.occnc.com> <5E893DB832F57341992548CDBB333163984487C7AE@EMBX01-HQ.jnpr.net>
Cc: mpls@ietf.org, 'pwe3' <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware	Transport
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jul 2010 15:32:34 -0000

Hi John,

Uneven load balance problems exist today. There are several drafts to target
this problem.

Thanks,
Lucy

> -----Original Message-----
> From: John E Drake [mailto:jdrake@juniper.net]
> Sent: Tuesday, July 20, 2010 1:44 PM
> To: curtis@occnc.com; Yong Lucy
> Cc: mpls@ietf.org; 'pwe3'
> Subject: RE: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware
> Transport
> 
> Lucy,
> 
> As Curtis points out in section 4.1.2 of
> http://datatracker.ietf.org/doc/draft-villamizar-mpls-tp-multipath/, the
> issue your I-D purports to solve has been already been solved by clever
> implementation many years ago, with no changes to protocols or packet
> formats.
> 
> Thanks,
> 
> John
> 
> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> > Curtis Villamizar
> > Sent: Tuesday, July 20, 2010 11:33 AM
> > To: Yong Lucy
> > Cc: mpls@ietf.org; 'pwe3'
> > Subject: Re: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware
> > Transport
> >
> >
> > In message <00d801cb2519$e6f16160$380c7c0a@china.huawei.com>
> > Yong Lucy writes:
> > >
> > >
> > > I like to post this e-mail again for reminding. We have changed the
> > draft
> > > title to draft-yong-pwe-lfc-fat-pw to focus on large flow
> > classification,
> > > not enhanced ECMP.
> > >
> > > Look forward to discussing this at Maastricht.
> > >
> > > Lucy
> >
> >
> > Lucy,
> >
> > Any modifications to the use of the TC bits is almost certainly a
> > non-starter.  I thought that was also mentioned in the last meeting.
> > We'll see what comments come out of the meeting this time.
> >
> > Curtis
> >
> >
> > >   _____
> > >
> > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> > Of Yong
> > > Lucy
> > > Sent: Tuesday, April 27, 2010 5:37 PM
> > > To: 'pwe3'; mpls@ietf.org
> > > Subject: [mpls] Large FLow Classificaiton in Flow Aware Transport
> > >
> > >
> > >
> > > Hi,
> > >
> > > I recap the comments raised during IETF77 meeting. Some are from the
> > PWE3
> > > meeting and some from offline discussions. Hope this gives some
> > > clarification and bring up further mailing discussion.
> > >
> > > The draft proposal (draft-yong-pwe3-enhanced-ecmp-lfat-01) is to use
> > one of
> > > the TC bits in the flow label to indicate large flow. TC bits in flow
> > label
> > > described in FAT-PW are not used and are not interpreted by LSR.
> > >
> > > Comments and Responses:
> > >
> > > 1) No use for the proposal. would need to update all equipment to get
> > this
> > > to work.  A while ago we agreed to not standardize ECMP process.
> > >
> > > Lucy: Some carriers see the value of it. There is no need to update
> > all
> > > equipment to get this work. The backward compatibility is supported
> > as
> > > described in section 6. Partially upgrading can improve some segments
> > while
> > > keeping other segments remain the same. The intention of the draft is
> > not
> > > for standardizing ECMP process. It is about standardizing large flow
> > > classification indication in PSN. The draft layout may lead this
> > confusion.
> > > We will modify the draft and move enhanced ECMP process description
> > to
> > > appendix as one implementation example to use large flow
> > classification. We
> > > will change the draft title to "large flow classification in flow
> > aware
> > > transport over PSN" and upload soon.
> > >
> > > 2) would need to go through MPLS WG for issue on standardizing ECMP.
> > Label
> > > stack is always MPLS label stack so MPLS WG would need to OK change
> > of TC
> > > semantics.  Needs a co-review in MPLS WG and they must approve.
> > >
> > > Lucy: The draft is not for standardizing ECMP. (sorry for the
> > confusion).
> > > The draft does not change the semantics of a label stack entry
> > defined by
> > > RFC3032 because the flow label is never on the top of label stack. As
> > FAT-PW
> > > draft indicates that the interpretation of TC bits in the flow label
> > by LSR
> > > is undefined. This draft proposes one definition.
> > >
> > > 3) If you can get MPLS WG to agree, one of the issues is that you are
> > > marking at a PE where the PE may or may not know what is or isn't a
> > big
> > > flow.  Limitations on PEs ability to determine what a big flow is.
> > Would
> > > need to tell easily and ubiquitously what a big flow is.
> > >
> > > Lucy: In our proposal, large flows in this context are the top rate
> > ranked
> > > flows. It is relevant to other flows not the link capacity. Enhanced
> > ECMP
> > > process just needs a small set of large flows for load balancing,
> > therefore,
> > > it can pick by statistics, i.e. not necessary all the large flows.
> > The
> > > method works well even some large flows placed by hashing function.
> > The
> > > backward compatibility in the draft would deal with this.
> > >
> > > 4) we haven't standardized anything on ECMP. Many will look at bottom
> > of
> > > stack to look at IP address or anything else to hash on. If I'm a PE
> > router
> > > with lots of L3VPN traffic and some PWs, how do I know if this is a
> > flow
> > > label or VPN label.
> > >
> > > Lucy: This is not for ECMP standardization. We propose one method to
> > > differentiate the flow label from IP packet, PW label, and LSP label
> > at the
> > > bottom of label stack. This is: check the first nibble to separate IP
> > and
> > > MPLS packets; for MPLS packets, use TTL value (=0) to check the flow
> > label
> > > packets.
> > >
> > > 5) this is addressing an important issue.  Simulations showed a lot
> > of
> > > traffic and the flows are large enough.  Cases in well engineered
> > network
> > > where situation is much worse than shown.  Drafts have been
> > submitting in
> > > past that gained no traction.  To use a method other than just
> > hashing, but
> > > may be ways to do this without changing label or MPLS.
> > >
> > > Lucy: The simulation use Internet traffic pattern. For carrier
> > network, it
> > > has a lot of L2VPN traffic carried as single flow, so the situation
> > is
> > > worse. We work on additional simulation to include such type of
> > traffic. It
> > > confirms the statement. As Internet traffic grow with higher and
> > higher bit
> > > rate flows, the problem will become more and more severe. We need to
> > aim on
> > > this real problem.
> > >
> > > 6) there was a proposal to solve this 10 years ago with no protocol
> > changes.
> > > This is not needed.
> > >
> > > Lucy: Need clarification which proposal refers to. If it is OMP, the
> > draft
> > > proposes the different method from OMP. OMP suggest using routing
> > protocol
> > > to advertise individual ECMP path TE information in the network. The
> > draft
> > > is about large flow classification indication so LSR can use a set of
> > large
> > > flows in performing load balance over ECMP paths effectively.
> > >
> > > 7) Changes too much about MPLS processing
> > >
> > > Lucy: It is not that additional process. Gaining is obvious too.
> > >
> > > 8) did the simulations deal with coming and going of flows? How to
> > address
> > > flow fluctuation?
> > >
> > > Lucy: we are working on additional simulations. That will include
> > flow
> > > coming and going situation and include much higher bit rate flows,
> > and a
> > > "permanent flow" whose rate may change over time to make it as small
> > flow at
> > > a time or a large flow at another time. The latter case likes a VPWS
> > as a
> > > flow. Be glad to show some simulation result to the group.
> > >
> > > 9) Signaling can be used for this, why using marking?
> > >
> > > Lucy: today, signaling a PW is used per a service basis such as VPWS
> > or
> > > VPLS. But one VPWS or VPLS may contain many flows, the draft address
> > this
> > > situation. It is hard for carrier to signal individual large flow
> > within
> > > VPLS over PSN networks.
> > >
> > > 10) If there is incentive to enhanced ECMP, why not do large flow
> > > recognition at local LSR for the purpose? PE based large flow
> > recognition
> > > and marking do not apply well at individual LSR.
> > >
> > > Lucy: High bit rate flow is relevant to other flows. Operator can set
> > large
> > > flow criteria. Having each LSR performs larger flow recognition add
> > complex
> > > to each LSR and may impact the service performance. Large flow
> > > classification is easier, we think. Today, DiffServ enables the
> > network to
> > > perform different service treatments. Large flow classification
> > enables
> > > network to perform different flow treatments over ECMP operation.
> > >
> > > Comments and suggestion are welcome.
> > >
> > >
> > > Regards,
> > > Lucy
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls


From jdrake@juniper.net  Wed Jul 21 09:12:03 2010
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C403C3A6A34; Wed, 21 Jul 2010 09:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.893
X-Spam-Level: 
X-Spam-Status: No, score=-5.893 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
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 eZwnPc7Z30YE; Wed, 21 Jul 2010 09:11:58 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by core3.amsl.com (Postfix) with ESMTP id BD7D93A6981; Wed, 21 Jul 2010 09:11:57 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKTEccUENbnmMZgA7E26PgT24o+I6MJbeO@postini.com; Wed, 21 Jul 2010 09:12:14 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Wed, 21 Jul 2010 09:10:20 -0700
From: John E Drake <jdrake@juniper.net>
To: Yong Lucy <lucyyong@huawei.com>, "curtis@occnc.com" <curtis@occnc.com>
Date: Wed, 21 Jul 2010 09:10:18 -0700
Thread-Topic: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware Transport
Thread-Index: AcsoOhgYXyrbBhBYRfO6Kq+DEv5LGgAAMQxgACulKzAAAUI/cA==
Message-ID: <5E893DB832F57341992548CDBB33316398448E12CA@EMBX01-HQ.jnpr.net>
References: "Your message of Fri, 16 Jul 2010 14:05:46 CDT." <00d801cb2519$e6f16160$380c7c0a@china.huawei.com> <201007201832.o6KIWZtg065155@harbor.orleans.occnc.com> <5E893DB832F57341992548CDBB333163984487C7AE@EMBX01-HQ.jnpr.net> <00a501cb28e9$eeae1c30$380c7c0a@china.huawei.com>
In-Reply-To: <00a501cb28e9$eeae1c30$380c7c0a@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, 'pwe3' <pwe3@ietf.org>
Subject: Re: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware	Transport
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jul 2010 16:12:03 -0000

Lucy,

I don't get the sense that you understood what I said, viz, according to th=
e I-D that Curtis wrote, this is a solved problem.

Thanks,

John

> -----Original Message-----
> From: Yong Lucy [mailto:lucyyong@huawei.com]
> Sent: Wednesday, July 21, 2010 8:32 AM
> To: John E Drake; curtis@occnc.com
> Cc: mpls@ietf.org; 'pwe3'
> Subject: RE: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow Aware
> Transport
>=20
> Hi John,
>=20
> Uneven load balance problems exist today. There are several drafts to
> target
> this problem.
>=20
> Thanks,
> Lucy
>=20
> > -----Original Message-----
> > From: John E Drake [mailto:jdrake@juniper.net]
> > Sent: Tuesday, July 20, 2010 1:44 PM
> > To: curtis@occnc.com; Yong Lucy
> > Cc: mpls@ietf.org; 'pwe3'
> > Subject: RE: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow
> Aware
> > Transport
> >
> > Lucy,
> >
> > As Curtis points out in section 4.1.2 of
> > http://datatracker.ietf.org/doc/draft-villamizar-mpls-tp-multipath/,
> the
> > issue your I-D purports to solve has been already been solved by
> clever
> > implementation many years ago, with no changes to protocols or packet
> > formats.
> >
> > Thanks,
> >
> > John
> >
> > > -----Original Message-----
> > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> Behalf Of
> > > Curtis Villamizar
> > > Sent: Tuesday, July 20, 2010 11:33 AM
> > > To: Yong Lucy
> > > Cc: mpls@ietf.org; 'pwe3'
> > > Subject: Re: [mpls] [PWE3] FW: Large FLow Classificaiton in Flow
> Aware
> > > Transport
> > >
> > >
> > > In message <00d801cb2519$e6f16160$380c7c0a@china.huawei.com>
> > > Yong Lucy writes:
> > > >
> > > >
> > > > I like to post this e-mail again for reminding. We have changed
> the
> > > draft
> > > > title to draft-yong-pwe-lfc-fat-pw to focus on large flow
> > > classification,
> > > > not enhanced ECMP.
> > > >
> > > > Look forward to discussing this at Maastricht.
> > > >
> > > > Lucy
> > >
> > >
> > > Lucy,
> > >
> > > Any modifications to the use of the TC bits is almost certainly a
> > > non-starter.  I thought that was also mentioned in the last
> meeting.
> > > We'll see what comments come out of the meeting this time.
> > >
> > > Curtis
> > >
> > >
> > > >   _____
> > > >
> > > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> Behalf
> > > Of Yong
> > > > Lucy
> > > > Sent: Tuesday, April 27, 2010 5:37 PM
> > > > To: 'pwe3'; mpls@ietf.org
> > > > Subject: [mpls] Large FLow Classificaiton in Flow Aware Transport
> > > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I recap the comments raised during IETF77 meeting. Some are from
> the
> > > PWE3
> > > > meeting and some from offline discussions. Hope this gives some
> > > > clarification and bring up further mailing discussion.
> > > >
> > > > The draft proposal (draft-yong-pwe3-enhanced-ecmp-lfat-01) is to
> use
> > > one of
> > > > the TC bits in the flow label to indicate large flow. TC bits in
> flow
> > > label
> > > > described in FAT-PW are not used and are not interpreted by LSR.
> > > >
> > > > Comments and Responses:
> > > >
> > > > 1) No use for the proposal. would need to update all equipment to
> get
> > > this
> > > > to work.  A while ago we agreed to not standardize ECMP process.
> > > >
> > > > Lucy: Some carriers see the value of it. There is no need to
> update
> > > all
> > > > equipment to get this work. The backward compatibility is
> supported
> > > as
> > > > described in section 6. Partially upgrading can improve some
> segments
> > > while
> > > > keeping other segments remain the same. The intention of the
> draft is
> > > not
> > > > for standardizing ECMP process. It is about standardizing large
> flow
> > > > classification indication in PSN. The draft layout may lead this
> > > confusion.
> > > > We will modify the draft and move enhanced ECMP process
> description
> > > to
> > > > appendix as one implementation example to use large flow
> > > classification. We
> > > > will change the draft title to "large flow classification in flow
> > > aware
> > > > transport over PSN" and upload soon.
> > > >
> > > > 2) would need to go through MPLS WG for issue on standardizing
> ECMP.
> > > Label
> > > > stack is always MPLS label stack so MPLS WG would need to OK
> change
> > > of TC
> > > > semantics.  Needs a co-review in MPLS WG and they must approve.
> > > >
> > > > Lucy: The draft is not for standardizing ECMP. (sorry for the
> > > confusion).
> > > > The draft does not change the semantics of a label stack entry
> > > defined by
> > > > RFC3032 because the flow label is never on the top of label
> stack. As
> > > FAT-PW
> > > > draft indicates that the interpretation of TC bits in the flow
> label
> > > by LSR
> > > > is undefined. This draft proposes one definition.
> > > >
> > > > 3) If you can get MPLS WG to agree, one of the issues is that you
> are
> > > > marking at a PE where the PE may or may not know what is or isn't
> a
> > > big
> > > > flow.  Limitations on PEs ability to determine what a big flow
> is.
> > > Would
> > > > need to tell easily and ubiquitously what a big flow is.
> > > >
> > > > Lucy: In our proposal, large flows in this context are the top
> rate
> > > ranked
> > > > flows. It is relevant to other flows not the link capacity.
> Enhanced
> > > ECMP
> > > > process just needs a small set of large flows for load balancing,
> > > therefore,
> > > > it can pick by statistics, i.e. not necessary all the large
> flows.
> > > The
> > > > method works well even some large flows placed by hashing
> function.
> > > The
> > > > backward compatibility in the draft would deal with this.
> > > >
> > > > 4) we haven't standardized anything on ECMP. Many will look at
> bottom
> > > of
> > > > stack to look at IP address or anything else to hash on. If I'm a
> PE
> > > router
> > > > with lots of L3VPN traffic and some PWs, how do I know if this is
> a
> > > flow
> > > > label or VPN label.
> > > >
> > > > Lucy: This is not for ECMP standardization. We propose one method
> to
> > > > differentiate the flow label from IP packet, PW label, and LSP
> label
> > > at the
> > > > bottom of label stack. This is: check the first nibble to
> separate IP
> > > and
> > > > MPLS packets; for MPLS packets, use TTL value (=3D0) to check the
> flow
> > > label
> > > > packets.
> > > >
> > > > 5) this is addressing an important issue.  Simulations showed a
> lot
> > > of
> > > > traffic and the flows are large enough.  Cases in well engineered
> > > network
> > > > where situation is much worse than shown.  Drafts have been
> > > submitting in
> > > > past that gained no traction.  To use a method other than just
> > > hashing, but
> > > > may be ways to do this without changing label or MPLS.
> > > >
> > > > Lucy: The simulation use Internet traffic pattern. For carrier
> > > network, it
> > > > has a lot of L2VPN traffic carried as single flow, so the
> situation
> > > is
> > > > worse. We work on additional simulation to include such type of
> > > traffic. It
> > > > confirms the statement. As Internet traffic grow with higher and
> > > higher bit
> > > > rate flows, the problem will become more and more severe. We need
> to
> > > aim on
> > > > this real problem.
> > > >
> > > > 6) there was a proposal to solve this 10 years ago with no
> protocol
> > > changes.
> > > > This is not needed.
> > > >
> > > > Lucy: Need clarification which proposal refers to. If it is OMP,
> the
> > > draft
> > > > proposes the different method from OMP. OMP suggest using routing
> > > protocol
> > > > to advertise individual ECMP path TE information in the network.
> The
> > > draft
> > > > is about large flow classification indication so LSR can use a
> set of
> > > large
> > > > flows in performing load balance over ECMP paths effectively.
> > > >
> > > > 7) Changes too much about MPLS processing
> > > >
> > > > Lucy: It is not that additional process. Gaining is obvious too.
> > > >
> > > > 8) did the simulations deal with coming and going of flows? How
> to
> > > address
> > > > flow fluctuation?
> > > >
> > > > Lucy: we are working on additional simulations. That will include
> > > flow
> > > > coming and going situation and include much higher bit rate
> flows,
> > > and a
> > > > "permanent flow" whose rate may change over time to make it as
> small
> > > flow at
> > > > a time or a large flow at another time. The latter case likes a
> VPWS
> > > as a
> > > > flow. Be glad to show some simulation result to the group.
> > > >
> > > > 9) Signaling can be used for this, why using marking?
> > > >
> > > > Lucy: today, signaling a PW is used per a service basis such as
> VPWS
> > > or
> > > > VPLS. But one VPWS or VPLS may contain many flows, the draft
> address
> > > this
> > > > situation. It is hard for carrier to signal individual large flow
> > > within
> > > > VPLS over PSN networks.
> > > >
> > > > 10) If there is incentive to enhanced ECMP, why not do large flow
> > > > recognition at local LSR for the purpose? PE based large flow
> > > recognition
> > > > and marking do not apply well at individual LSR.
> > > >
> > > > Lucy: High bit rate flow is relevant to other flows. Operator can
> set
> > > large
> > > > flow criteria. Having each LSR performs larger flow recognition
> add
> > > complex
> > > > to each LSR and may impact the service performance. Large flow
> > > > classification is easier, we think. Today, DiffServ enables the
> > > network to
> > > > perform different service treatments. Large flow classification
> > > enables
> > > > network to perform different flow treatments over ECMP operation.
> > > >
> > > > Comments and suggestion are welcome.
> > > >
> > > >
> > > > Regards,
> > > > Lucy
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls


From gregimirsky@gmail.com  Wed Jul 21 23:12:11 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C54C03A69A6; Wed, 21 Jul 2010 23:12:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.282
X-Spam-Level: 
X-Spam-Status: No, score=-1.282 tagged_above=-999 required=5 tests=[AWL=-0.544, BAYES_20=-0.74, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=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 4eVEU3rq2r0n; Wed, 21 Jul 2010 23:12:10 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 85CB03A67F1; Wed, 21 Jul 2010 23:12:10 -0700 (PDT)
Received: by yxj4 with SMTP id 4so2691130yxj.31 for <multiple recipients>; Wed, 21 Jul 2010 23:12:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=5QP8yuFJYZgN3Kz9ODueL3AdT2o71dwN8o7xL9MnIYk=; b=HYXJjFVDewdfp6lj98mFX9w2UXb1UwVDEclEbUcvCOWV8/d/WJXIlnIZMWZhJZ1Kur hkjq06b85luGyifZjb1ieVFLO6Z9AOVj4ZT3/BUV610S9BxEhWIo21B+eFFk1qBBXjQr GIM+fwQmtCAO6fc+x9mv+7MY2A8u0EdX1o0Lg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=BNa0F7p4tH42yOcHxhD8KWvh/Oq7CVjRVXUryuI1fuQ9ZHptvK1w6EcfR07IoywDar zk2x+TLpEG59lWD5wFFXpkD17Aa6offyRA1zc6VOxsjGHDQf6NPLNyAK6r0bPweEF5Et Yqx9kdQx6yu2NQIca4iZpIYh5f8dwhdG3CV5g=
MIME-Version: 1.0
Received: by 10.220.62.5 with SMTP id v5mr541718vch.81.1279779147112; Wed, 21  Jul 2010 23:12:27 -0700 (PDT)
Received: by 10.220.86.72 with HTTP; Wed, 21 Jul 2010 23:12:27 -0700 (PDT)
Date: Wed, 21 Jul 2010 23:12:27 -0700
Message-ID: <AANLkTimM750-lTglS8IpWQyFW6q_5KOGlPmutOsxm2Ju@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: David Allan I <david.i.allan@ericsson.com>, John E Drake <jdrake@juniper.net>, swallow@cisco.com,  annamaria.fulignoli@ericsson.com, Sami Boutros <sboutros@cisco.com>,  martin.vigoureux@alcatel-lucent.com,  "Siva Sivabalan(msiva)" <msiva@cisco.com>, David Ward <dward@juniper.net>, mpls-tp@ietf.org, mpls@ietf.org
Content-Type: multipart/alternative; boundary=e0cb4e887ee9746199048bf3cd06
Subject: [mpls] Comments on draft-ietf-mpls-tp-cc-cv-rdi-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2010 06:12:11 -0000

--e0cb4e887ee9746199048bf3cd06
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Dear Authors and All,
please find my comments to the document below:

=B7         Abstract, first paragraph s/are/the

=B7         Section 3. From description of CV mode it is not clear, as from
description of CC mode, whether RDI functionalities supported in CV mode.
Though description of RDI explicitly mentions that. Either mention RDI
functionality in connection to CV mode or remove it from CC for consistency=
.

=B7         Section 3.1 =93It's possible to run BFD in CC mode on some tran=
sport
paths and BFD in CV mode on other transport paths.=94 I think that this is
important to mention only for paths between the same pair of end nodes.

=B7         Section 3.4 =93A BFD session is enabled when the CC or proactiv=
e CV
functionality is enabled on a configured Maintenance Entity (ME) or in the
case of an associated bi-directional path, pair of Maintenance Entities=94
conflicts with =93A new BFD session is initiated when the operator enables =
or
re-enables the CC or CV functionality on the same ME=94 as the latter
statement refers to a single ME instance regardless whether bi-directional
path is co-routed or associated. I think that a BFD session is one-to-one
mapped with ME regardless number of MEs that used to monitor connectivity
and/or continuity of p2p bidirectional path.

=B7         Section 3.5, first paragraph. I think that even though BFD is
capable to change frequency of transmitting messages on a fly, in MPLS-TP
such action must go through Admin Down state as one BFD session is
effectively taken down and another, with different parameters, is enabled.

=B7         Section 3.5,  p.7. I think that there=92s another clarification=
 of
how MEP with zero transmit rate send its BFD control packets will be in
useful - how this MEP sends these packets. Perhaps use of ACH encapsulation
over reverse direction of the associated bi-directional path will be defaul=
t
behavior. But it could be over DCN with or without IP addressing.


Regards,

Greg

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

<span style=3D"font-family: arial,helvetica,sans-serif;">Dear Authors and A=
ll,</span><br style=3D"font-family: arial,helvetica,sans-serif;"><span styl=
e=3D"font-family: arial,helvetica,sans-serif;">please find my comments to t=
he document below:</span><br style=3D"font-family: arial,helvetica,sans-ser=
if;">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"><m=
eta name=3D"ProgId" content=3D"Word.Document"><meta name=3D"Generator" cont=
ent=3D"Microsoft Word 12"><meta name=3D"Originator" content=3D"Microsoft Wo=
rd 12"><link style=3D"font-family: arial,helvetica,sans-serif;" rel=3D"File=
-List" href=3D"file:///C:%5CDOCUME%7E1%5Cgmirsky%5CLOCALS%7E1%5CTemp%5Cmsoh=
tmlclip1%5C01%5Cclip_filelist.xml"><link style=3D"font-family: arial,helvet=
ica,sans-serif;" rel=3D"themeData" href=3D"file:///C:%5CDOCUME%7E1%5Cgmirsk=
y%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link styl=
e=3D"font-family: arial,helvetica,sans-serif;" rel=3D"colorSchemeMapping" h=
ref=3D"file:///C:%5CDOCUME%7E1%5Cgmirsky%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1=
%5C01%5Cclip_colorschememapping.xml"><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:1;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:variable;
	mso-font-signature:0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1073750139 0 0 159 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	mso-style-unhide:no;
	mso-style-qformat:yes;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:.5in;
	mso-add-space:auto;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParag=
raphCxSpFirst
	{mso-style-priority:34;
	mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListPar=
agraphCxSpMiddle
	{mso-style-priority:34;
	mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagra=
phCxSpLast
	{mso-style-priority:34;
	mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:.5in;
	mso-add-space:auto;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
.MsoPapDefault
	{mso-style-type:export-only;
	margin-bottom:10.0pt;
	line-height:115%;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1940285742;
	mso-list-type:hybrid;
	mso-list-template-ids:-1132550708 67698689 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

<p class=3D"MsoListParagraphCxSpFirst" style=3D"text-indent: -0.25in; font-=
family: arial,helvetica,sans-serif;"><span style=3D"">=C2=B7<span style=3D"=
font-style: normal; font-variant: normal; font-weight: normal; font-size: 7=
pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>Abstract, first paragraph s/are/the</p><p class=3D"MsoListPar=
agraphCxSpFirst" style=3D"text-indent: -0.25in; font-family: arial,helvetic=
a,sans-serif;"><span style=3D"">=C2=B7<span style=3D"font-style: normal; fo=
nt-variant: normal; font-weight: normal; font-size: 7pt; line-height: norma=
l; font-size-adjust: none; font-stretch: normal;">=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 </span></span>Section 3. From description of CV mo=
de it is not
clear, as from description of CC mode, whether RDI functionalities supporte=
d in
CV mode. Though description of RDI explicitly mentions that. Either mention=
 RDI
functionality in connection to CV mode or remove it from CC for consistency=
.</p>

<p class=3D"MsoListParagraphCxSpMiddle" style=3D"text-indent: -0.25in; font=
-family: arial,helvetica,sans-serif;"><span style=3D"">=C2=B7<span style=3D=
"font-style: normal; font-variant: normal; font-weight: normal; font-size: =
7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>Section 3.1 =E2=80=9CIt&#39;s possible to run BFD in CC mode
on some transport paths and BFD in CV mode on other transport paths.=E2=80=
=9D I think
that this is important to mention only for paths between the same pair of e=
nd
nodes.</p>

<p class=3D"MsoListParagraphCxSpMiddle" style=3D"text-indent: -0.25in; font=
-family: arial,helvetica,sans-serif;"><span style=3D"">=C2=B7<span style=3D=
"font-style: normal; font-variant: normal; font-weight: normal; font-size: =
7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>Section 3.4 =E2=80=9CA BFD session is enabled when the
CC or proactive CV functionality is enabled on a configured Maintenance Ent=
ity
(ME) or in the case of an associated bi-directional path, pair of Maintenan=
ce
Entities=E2=80=9D conflicts with =E2=80=9CA new BFD session is initiated wh=
en the operator
enables or re-enables the CC or CV functionality on the same ME=E2=80=9D as=
 the latter
statement refers to a single ME instance regardless whether bi-directional =
path
is co-routed or associated. I think that a BFD session is one-to-one mapped
with ME regardless number of MEs that used to monitor connectivity and/or
continuity of p2p bidirectional path.</p>

<p class=3D"MsoListParagraphCxSpMiddle" style=3D"text-indent: -0.25in; font=
-family: arial,helvetica,sans-serif;"><span style=3D"">=C2=B7<span style=3D=
"font-style: normal; font-variant: normal; font-weight: normal; font-size: =
7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>Section 3.5, first paragraph. I think that even
though BFD is capable to change frequency of transmitting messages on a fly=
, in MPLS-TP such
action must go through Admin Down state as one BFD session is effectively t=
aken down and
another, with different parameters, is enabled.</p>

<p class=3D"MsoListParagraphCxSpLast" style=3D"text-indent: -0.25in; font-f=
amily: arial,helvetica,sans-serif;"><span style=3D"">=C2=B7<span style=3D"f=
ont-style: normal; font-variant: normal; font-weight: normal; font-size: 7p=
t; line-height: normal; font-size-adjust: none; font-stretch: normal;">=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>Section 3.5,<span style=3D"">=C2=A0
</span>p.7. I think that there=E2=80=99s another clarification of how MEP w=
ith zero transmit
rate send its BFD control packets will be in useful - how this MEP sends th=
ese packets. Perhaps use of ACH encapsulation over
reverse direction of the associated bi-directional path will be default
behavior. But it could be over DCN with or without IP addressing.</p><p cla=
ss=3D"MsoListParagraphCxSpLast" style=3D"text-indent: -0.25in; font-family:=
 arial,helvetica,sans-serif;"><br></p><p class=3D"MsoListParagraphCxSpLast"=
 style=3D"text-indent: -0.25in; font-family: arial,helvetica,sans-serif;">
Regards,</p><p class=3D"MsoListParagraphCxSpLast" style=3D"text-indent: -0.=
25in; font-family: arial,helvetica,sans-serif;">Greg<br></p>

<br>

--e0cb4e887ee9746199048bf3cd06--

From david.i.allan@ericsson.com  Thu Jul 22 09:13:08 2010
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 972C73A684B; Thu, 22 Jul 2010 09:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.81
X-Spam-Level: 
X-Spam-Status: No, score=-1.81 tagged_above=-999 required=5 tests=[AWL=-1.812,  BAYES_50=0.001, HTML_MESSAGE=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 TY7OaDmuQNjN; Thu, 22 Jul 2010 09:13:02 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 2B7D03A67F4; Thu, 22 Jul 2010 09:13:02 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6MGD6wH010888 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 22 Jul 2010 11:13:06 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Thu, 22 Jul 2010 12:13:05 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Greg Mirsky <gregimirsky@gmail.com>, John E Drake <jdrake@juniper.net>, "swallow@cisco.com" <swallow@cisco.com>, Annamaria Fulignoli <annamaria.fulignoli@ericsson.com>, Sami Boutros <sboutros@cisco.com>, "martin.vigoureux@alcatel-lucent.com" <martin.vigoureux@alcatel-lucent.com>,  "Siva Sivabalan(msiva)" <msiva@cisco.com>, David Ward <dward@juniper.net>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,  "mpls@ietf.org" <mpls@ietf.org>
Date: Thu, 22 Jul 2010 12:13:02 -0400
Thread-Topic: Comments on draft-ietf-mpls-tp-cc-cv-rdi-01
Thread-Index: AcspZN3XkgM9MZEQRwy7ItPtTED18wAU0yyA
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51AE4666BA@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTimM750-lTglS8IpWQyFW6q_5KOGlPmutOsxm2Ju@mail.gmail.com>
In-Reply-To: <AANLkTimM750-lTglS8IpWQyFW6q_5KOGlPmutOsxm2Ju@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_60C093A41B5E45409A19D42CF7786DFD51AE4666BAEUSAACMS0703e_"
MIME-Version: 1.0
Subject: Re: [mpls] Comments on draft-ietf-mpls-tp-cc-cv-rdi-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2010 16:13:08 -0000

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

Hi Greg:

Thanks for the read of the document and the feedback....



Dear Authors and All,
please find my comments to the document below:

*         Abstract, first paragraph s/are/the

OK

*         Section 3. From description of CV mode it is not clear, as from d=
escription of CC mode, whether RDI functionalities supported in CV mode. Th=
ough description of RDI explicitly mentions that. Either mention RDI functi=
onality in connection to CV mode or remove it from CC for consistency.

We will clarify in the next version.

*         Section 3.1 "It's possible to run BFD in CC mode on some transpor=
t paths and BFD in CV mode on other transport paths." I think that this is =
important to mention only for paths between the same pair of end nodes.

It would be even clearer if the mode was MEG specific. MEs in a MEG need to=
 be homogenous in operation. If you agree we'll edit accordingly.

*         Section 3.4 "A BFD session is enabled when the CC or proactive CV=
 functionality is enabled on a configured Maintenance Entity (ME) or in the=
 case of an associated bi-directional path, pair of Maintenance Entities" c=
onflicts with "A new BFD session is initiated when the operator enables or =
re-enables the CC or CV functionality on the same ME" as the latter stateme=
nt refers to a single ME instance regardless whether bi-directional path is=
 co-routed or associated. I think that a BFD session is one-to-one mapped w=
ith ME regardless number of MEs that used to monitor connectivity and/or co=
ntinuity of p2p bidirectional path.

This has come up before, I believe the correct resolution is an associated =
bi-directional path is a single ME. We will edit accordingly.

*         Section 3.5, first paragraph. I think that even though BFD is cap=
able to change frequency of transmitting messages on a fly, in MPLS-TP such=
 action must go through Admin Down state as one BFD session is effectively =
taken down and another, with different parameters, is enabled.

I agree we do not want any changes on the fly. And we could say MUST for ad=
min down to change anything, but that also means there are likely existing =
implementations out there that may not respect this.

*         Section 3.5,  p.7. I think that there's another clarification of =
how MEP with zero transmit rate send its BFD control packets will be in use=
ful - how this MEP sends these packets. Perhaps use of ACH encapsulation ov=
er reverse direction of the associated bi-directional path will be default =
behavior. But it could be over DCN with or without IP addressing.

I'll take a look and see if this should be clarified.

cheers

Dave




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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18470" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D516470816-22072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Greg:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D516470816-22072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D516470816-22072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Thanks for the read of the document and the=20
feedback....</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft><FONT=
 face=3DTahoma=20
size=3D2></FONT><BR>&nbsp;</DIV>
<DIV></DIV><SPAN style=3D"FONT-FAMILY: arial,helvetica,sans-serif">Dear Aut=
hors=20
and All,</SPAN><BR style=3D"FONT-FAMILY: arial,helvetica,sans-serif"><SPAN=
=20
style=3D"FONT-FAMILY: arial,helvetica,sans-serif">please find my comments t=
o the=20
document below:</SPAN><BR style=3D"FONT-FAMILY: arial,helvetica,sans-serif"=
>
<META content=3DWord.Document name=3DProgId>
<META content=3D"Microsoft Word 12" name=3DGenerator>
<META content=3D"Microsoft Word 12" name=3DOriginator><LINK=20
style=3D"FONT-FAMILY: arial,helvetica,sans-serif"=20
href=3D"file:///C:%5CDOCUME%7E1%5Cgmirsky%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip=
1%5C01%5Cclip_filelist.xml"=20
rel=3DFile-List><LINK style=3D"FONT-FAMILY: arial,helvetica,sans-serif"=20
href=3D"file:///C:%5CDOCUME%7E1%5Cgmirsky%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip=
1%5C01%5Cclip_themedata.thmx"=20
rel=3DthemeData><LINK style=3D"FONT-FAMILY: arial,helvetica,sans-serif"=20
href=3D"file:///C:%5CDOCUME%7E1%5Cgmirsky%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip=
1%5C01%5Cclip_colorschememapping.xml"=20
rel=3DcolorSchemeMapping>
<STYLE>@font-face {
	font-family: Wingdings;
}
@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; ms=
o-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Ca=
libri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso-styl=
e-parent: ""; mso-pagination: widow-orphan; mso-ascii-font-family: Calibri;=
 mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-f=
areast-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-t=
heme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-t=
heme-font: minor-bidi
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Ca=
libri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso-styl=
e-parent: ""; mso-pagination: widow-orphan; mso-ascii-font-family: Calibri;=
 mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-f=
areast-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-t=
heme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-t=
heme-font: minor-bidi
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Ca=
libri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso-styl=
e-parent: ""; mso-pagination: widow-orphan; mso-ascii-font-family: Calibri;=
 mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-f=
areast-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-t=
heme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-t=
heme-font: minor-bidi
}
P.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMIL=
Y: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; ms=
o-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme=
-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-fon=
t: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor=
-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor=
-bidi; mso-style-priority: 34; mso-add-space: auto
}
LI.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMIL=
Y: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; ms=
o-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme=
-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-fon=
t: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor=
-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor=
-bidi; mso-style-priority: 34; mso-add-space: auto
}
DIV.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMIL=
Y: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; ms=
o-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme=
-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-fon=
t: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor=
-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor=
-bidi; mso-style-priority: 34; mso-add-space: auto
}
P.MsoListParagraphCxSpFirst {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMILY=
: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso=
-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme-=
font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font=
: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-=
latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor-=
bidi; mso-style-priority: 34; mso-add-space: auto; mso-style-type: export-o=
nly
}
LI.MsoListParagraphCxSpFirst {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMILY=
: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso=
-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme-=
font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font=
: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-=
latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor-=
bidi; mso-style-priority: 34; mso-add-space: auto; mso-style-type: export-o=
nly
}
DIV.MsoListParagraphCxSpFirst {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMILY=
: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso=
-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme-=
font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font=
: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-=
latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor-=
bidi; mso-style-priority: 34; mso-add-space: auto; mso-style-type: export-o=
nly
}
P.MsoListParagraphCxSpMiddle {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMILY=
: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso=
-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme-=
font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font=
: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-=
latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor-=
bidi; mso-style-priority: 34; mso-add-space: auto; mso-style-type: export-o=
nly
}
LI.MsoListParagraphCxSpMiddle {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMILY=
: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso=
-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme-=
font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font=
: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-=
latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor-=
bidi; mso-style-priority: 34; mso-add-space: auto; mso-style-type: export-o=
nly
}
DIV.MsoListParagraphCxSpMiddle {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMILY=
: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso=
-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme-=
font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font=
: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-=
latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor-=
bidi; mso-style-priority: 34; mso-add-space: auto; mso-style-type: export-o=
nly
}
P.MsoListParagraphCxSpLast {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMIL=
Y: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; ms=
o-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme=
-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-fon=
t: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor=
-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor=
-bidi; mso-style-priority: 34; mso-add-space: auto; mso-style-type: export-=
only
}
LI.MsoListParagraphCxSpLast {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMIL=
Y: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; ms=
o-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme=
-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-fon=
t: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor=
-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor=
-bidi; mso-style-priority: 34; mso-add-space: auto; mso-style-type: export-=
only
}
DIV.MsoListParagraphCxSpLast {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMIL=
Y: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; ms=
o-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme=
-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-fon=
t: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor=
-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor=
-bidi; mso-style-priority: 34; mso-add-space: auto; mso-style-type: export-=
only
}
.MsoChpDefault {
	mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-far=
east-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-f=
ont-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-famil=
y: "Times New Roman"; mso-bidi-theme-font: minor-bidi; mso-style-type: expo=
rt-only; mso-default-props: yes
}
.MsoPapDefault {
	MARGIN-BOTTOM: 10pt; LINE-HEIGHT: 115%; mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>

<P class=3DMsoListParagraphCxSpFirst=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN>&middot;<SPAN=20
style=3D"FONT-WEIGHT: normal; FONT-SIZE: 7pt; LINE-HEIGHT: normal; FONT-STY=
LE: normal; FONT-VARIANT: normal; font-size-adjust: none; font-stretch: nor=
mal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN>Abstract, first paragraph s/are/the<SPAN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>&nbsp;</FONT></SP=
AN></P>
<P class=3DMsoListParagraphCxSpFirst=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>OK</FONT>&nbsp;</=
SPAN></P>
<P class=3DMsoListParagraphCxSpFirst=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN>&middot;<SPAN=20
style=3D"FONT-WEIGHT: normal; FONT-SIZE: 7pt; LINE-HEIGHT: normal; FONT-STY=
LE: normal; FONT-VARIANT: normal; font-size-adjust: none; font-stretch: nor=
mal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN>Section 3. From description of CV mode it is not clear, as fr=
om=20
description of CC mode, whether RDI functionalities supported in CV mode. T=
hough=20
description of RDI explicitly mentions that. Either mention RDI functionali=
ty in=20
connection to CV mode or remove it from CC for consistency.<SPAN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>&nbsp;</FONT></SP=
AN></P>
<P class=3DMsoListParagraphCxSpFirst=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>We will clarify&n=
bsp;in the=20
next version.</FONT>&nbsp;</SPAN></P>
<P class=3DMsoListParagraphCxSpMiddle=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN>&middot;<SPAN=20
style=3D"FONT-WEIGHT: normal; FONT-SIZE: 7pt; LINE-HEIGHT: normal; FONT-STY=
LE: normal; FONT-VARIANT: normal; font-size-adjust: none; font-stretch: nor=
mal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN>Section 3.1 &#8220;It's possible to run BFD in CC mode on som=
e transport=20
paths and BFD in CV mode on other transport paths.&#8221; I think that this=
 is=20
important to mention only for paths between the same pair of end nodes.<SPA=
N=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>&nbsp;</FONT></SP=
AN></P>
<P class=3DMsoListParagraphCxSpMiddle=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>It would be even =
clearer if=20
the mode was MEG specific. MEs in a MEG need to be homogenous in operation.=
 If=20
you agree we'll edit&nbsp;accordingly.</FONT>&nbsp;</SPAN></P>
<P class=3DMsoListParagraphCxSpMiddle=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN>&middot;<SPAN=20
style=3D"FONT-WEIGHT: normal; FONT-SIZE: 7pt; LINE-HEIGHT: normal; FONT-STY=
LE: normal; FONT-VARIANT: normal; font-size-adjust: none; font-stretch: nor=
mal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN>Section 3.4 &#8220;A BFD session is enabled when the CC or pr=
oactive CV=20
functionality is enabled on a configured Maintenance Entity (ME) or in the =
case=20
of an associated bi-directional path, pair of Maintenance Entities&#8221; c=
onflicts=20
with &#8220;A new BFD session is initiated when the operator enables or re-=
enables the=20
CC or CV functionality on the same ME&#8221; as the latter statement refers=
 to a=20
single ME instance regardless whether bi-directional path is co-routed or=20
associated. I think that a BFD session is one-to-one mapped with ME regardl=
ess=20
number of MEs that used to monitor connectivity and/or continuity of p2p=20
bidirectional path.<SPAN class=3D516470816-22072010><FONT color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></P>
<P class=3DMsoListParagraphCxSpMiddle=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>This has come up =
before, I=20
believe the correct resolution is an associated bi-directional path is a si=
ngle=20
ME. We will edit accordingly.</FONT>&nbsp;</SPAN></P>
<P class=3DMsoListParagraphCxSpMiddle=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN>&middot;<SPAN=20
style=3D"FONT-WEIGHT: normal; FONT-SIZE: 7pt; LINE-HEIGHT: normal; FONT-STY=
LE: normal; FONT-VARIANT: normal; font-size-adjust: none; font-stretch: nor=
mal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN>Section 3.5, first paragraph. I think that even though BFD is=
=20
capable to change frequency of transmitting messages on a fly, in MPLS-TP s=
uch=20
action must go through Admin Down state as one BFD session is effectively t=
aken=20
down and another, with different parameters, is enabled.<SPAN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>&nbsp;</FONT></SP=
AN></P>
<P class=3DMsoListParagraphCxSpMiddle=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>I agree we do not=
 want any=20
changes on the fly. And we could say MUST for admin down to change anything=
, but=20
that also means there are likely existing implementations out there that ma=
y not=20
respect this.</FONT></SPAN></P>
<P class=3DMsoListParagraphCxSpLast=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN>&middot;<SPAN=20
style=3D"FONT-WEIGHT: normal; FONT-SIZE: 7pt; LINE-HEIGHT: normal; FONT-STY=
LE: normal; FONT-VARIANT: normal; font-size-adjust: none; font-stretch: nor=
mal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN>Section 3.5,<SPAN>&nbsp; </SPAN>p.7. I think that there&#8217=
;s another=20
clarification of how MEP with zero transmit rate send its BFD control packe=
ts=20
will be in useful - how this MEP sends these packets. Perhaps use of ACH=20
encapsulation over reverse direction of the associated bi-directional path =
will=20
be default behavior. But it could be over DCN with or without IP=20
addressing.<SPAN class=3D516470816-22072010><FONT color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></P>
<P class=3DMsoListParagraphCxSpLast=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>I'll take a look =
and see if=20
this should be clarified.</FONT></SPAN></P>
<P class=3DMsoListParagraphCxSpLast=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>cheers</FONT></SP=
AN></P>
<P class=3DMsoListParagraphCxSpLast=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif"><SP=
AN=20
class=3D516470816-22072010><FONT color=3D#0000ff size=3D2>Dave</FONT>&nbsp;=
</SPAN></P>
<P class=3DMsoListParagraphCxSpLast=20
style=3D"TEXT-INDENT: -0.25in; FONT-FAMILY: arial,helvetica,sans-serif">&nb=
sp;</P><BR></BODY></HTML>

--_000_60C093A41B5E45409A19D42CF7786DFD51AE4666BAEUSAACMS0703e_--

From wwwrun@core3.amsl.com  Thu Jul 22 11:40:06 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id A12643A68DE; Thu, 22 Jul 2010 11:40:06 -0700 (PDT)
From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: chair@ietf.org,swallow@cisco.com,loa@pi.nu
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100722184006.A12643A68DE@core3.amsl.com>
Date: Thu, 22 Jul 2010 11:40:06 -0700 (PDT)
Cc: mpls@ietf.org, hiroshi.ota@itu.int, greg.jones@itu.int, steve.trowbridge@alcatel-lucent.com, ghani.abbas@ericsson.com, yoichi.maeda@ntt-at.co.jp, paf@cisco.com, adrian.farrel@huawei.com, rcallon@juniper.net, tsbsg15@itu.int, stbryant@cisco.com, iesg@ietf.org
Subject: [mpls] New Liaison Statement, "LS217 - MPLS-TP Survivability Framework          (ref # 28.06)"
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tsbsg15@itu.int
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2010 18:40:07 -0000

Title: LS217 - MPLS-TP Survivability Framework (ref # 28.06)
Submission Date: 2010-07-22
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=937 
Please reply by 2010-08-31

From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: IETF IESG, IETF MPLS WG(chair@ietf.org,swallow@cisco.com,loa@pi.nu)
Cc: paf@cisco.com
iesg@ietf.org
stbryant@cisco.com
adrian.farrel@huawei.com
rcallon@juniper.net
mpls@ietf.org
yoichi.maeda@ntt-at.co.jp
steve.trowbridge@alcatel-lucent.com
Reponse Contact: tsbsg15@itu.int
greg.jones@itu.int
hiroshi.ota@itu.int
Technical Contact: ghani.abbas@ericsson.com
Purpose: For action 
Body: 
Attachment(s):
     LS217 - MPLS-TP Survivability Framework (ref # 28.06) - pdf body (https://datatracker.ietf.org/documents/LIAISON/file1086.pdf)




From lucyyong@huawei.com  Thu Jul 22 13:19:00 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F3E83A6900 for <mpls@core3.amsl.com>; Thu, 22 Jul 2010 13:19:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.527
X-Spam-Level: 
X-Spam-Status: No, score=0.527 tagged_above=-999 required=5 tests=[AWL=-1.579,  BAYES_50=0.001, 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 LkGxAlQExH3g for <mpls@core3.amsl.com>; Thu, 22 Jul 2010 13:18:59 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 6A2BA3A68F1 for <mpls@ietf.org>; Thu, 22 Jul 2010 13:18:59 -0700 (PDT)
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 <0L5Z0075N73UN3@szxga03-in.huawei.com> for mpls@ietf.org; Fri, 23 Jul 2010 04:19:06 +0800 (CST)
Received: from 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 <0L5Z00KSV73UOY@szxga03-in.huawei.com> for mpls@ietf.org; Fri, 23 Jul 2010 04:19:06 +0800 (CST)
Received: from y736742 ([10.124.12.56]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5Z00MXZ73SU7@szxml04-in.huawei.com> for mpls@ietf.org; Fri, 23 Jul 2010 04:19:06 +0800 (CST)
Date: Thu, 22 Jul 2010 15:19:03 -0500
From: Yong Lucy <lucyyong@huawei.com>
To: curtis@occnc.com, mpls@ietf.org
Message-id: <011101cb29db$22185df0$380c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_VZ/6EwCmn8Wm6b42jsHyxQ)"
Thread-index: Acsp2yCf3dZR3HqMRrK742qsMRUyRQ==
Subject: [mpls] draft-villamizar-mpls-tp-multipath
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2010 20:19:00 -0000

This is a multi-part message in MIME format.

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

Hi Curtis,

 

Thank you for summarizing hashing based multipath solution in this draft.
Share my opinion here.

   

Draft Text:

 

   An alternate simple multipath technique uses a table

   generally with a power of two size, and distributes the table entries

   proportionally among component links according to the capacity of

   each component link.

 

   An adaptive multipath technique is one where the traffic bound to

   each component link is measured and the load split is adjusted

   accordingly.   

 

End Text

 

Comment:

1) Adjusting load over component link may cause flow reordering. 

2) If a huge amount of micro flows mix with few large and long live flows,
the load per entry can be out of balance

3) Measure component link load does not provide the info. for table entry
mapping adjustment

 

Internet traffic pattern today is different from decade or more years ago.
Hashing works well under the condition 

1) # of flows is very large and flow IDs are statistically random; 2) flow
BWs are pretty balanced. 

 

Otherwise, hashing has a trouble to make even load balance.  Hashing +
bucket mapping brings a room to deal with the unbalance if each bucket load
is measured. 

 

If the equipment understands flows better rather than just flow ID, more
proactive way can apply to multipath load balance. This is why we suggest
having large flow classification (draft-yong-pwe3-lfc-fat-pw-01)

 

Regards,

Lucy

 

 


--Boundary_(ID_VZ/6EwCmn8Wm6b42jsHyxQ)
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="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 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Hi Curtis,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Thank you for summarizing hashing based multipath solution
in this draft. Share my opinion here.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Draft Text:<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>&nbsp;&nbsp; An alternate simple multipath technique uses a
table<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>&nbsp;&nbsp; generally with a power of two size, and
distributes the table entries<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>&nbsp;&nbsp; proportionally among component links according to
the capacity of<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>&nbsp;&nbsp; each component link.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>&nbsp;&nbsp; An adaptive multipath technique is one where the
traffic bound to<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>&nbsp;&nbsp; each component link is measured and the load
split is adjusted<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>&nbsp;&nbsp; accordingly.&nbsp; &nbsp;<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>End Text<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Comment:<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>1) Adjusting load over component link may cause flow
reordering. <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>2) If a huge amount of micro flows mix with few large
and long live flows, the load per entry can be out of balance<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>3) Measure component link load does not provide the
info. for table entry mapping adjustment<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Internet traffic pattern today is different from decade
or more years ago. &nbsp;Hashing works well under the condition <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>1) # of flows is very large and flow IDs are statistically
random; 2) flow BWs are pretty balanced. <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Otherwise, hashing has a trouble to make even load
balance. &nbsp;Hashing + bucket mapping brings a room to deal with the unbalance if each
bucket load is measured. <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>If the equipment understands flows better rather
than just flow ID, more proactive way can apply to multipath load balance. This
is why we suggest having large flow classification (draft-yong-pwe3-lfc-fat-pw-01)<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Regards,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Lucy<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_VZ/6EwCmn8Wm6b42jsHyxQ)--

From Lothar.Reith@detecon.com  Fri Jul 23 11:21:55 2010
Return-Path: <Lothar.Reith@detecon.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 634DF3A684D; Fri, 23 Jul 2010 11:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=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 TI86QcBrG9QK; Fri, 23 Jul 2010 11:21:54 -0700 (PDT)
Received: from dtc035.detecon.net (dtc035.detecon.net [194.25.60.135]) by core3.amsl.com (Postfix) with ESMTP id 9219D3A681C; Fri, 23 Jul 2010 11:21:53 -0700 (PDT)
Received: from unknown (HELO dc00357.detecon.com) ([172.16.10.107]) by relay.dtc035.detecon.net with ESMTP; 23 Jul 2010 20:21:57 +0200
Received: from dc302v.detecon.com ([172.16.10.41]) by dc00357.detecon.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 23 Jul 2010 20:21:58 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB2A93.EF993102"
Date: Fri, 23 Jul 2010 20:21:57 +0200
Message-ID: <8AAA8EFE7E4B594A86052935CF66E62E01845878@dc302v.detecon.com>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51AE4666BA@EUSAACMS0703.eamcs.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Comments on draft-ietf-mpls-tp-cc-cv-rdi-01
Thread-Index: AcspZN3XkgM9MZEQRwy7ItPtTED18wAU0yyAADUSMLA=
References: <AANLkTimM750-lTglS8IpWQyFW6q_5KOGlPmutOsxm2Ju@mail.gmail.com> <60C093A41B5E45409A19D42CF7786DFD51AE4666BA@EUSAACMS0703.eamcs.ericsson.se>
From: "Reith, Lothar" <Lothar.Reith@detecon.com>
To: "David Allan I" <david.i.allan@ericsson.com>, "Greg Mirsky" <gregimirsky@gmail.com>, "John E Drake" <jdrake@juniper.net>, <swallow@cisco.com>, "Annamaria Fulignoli" <annamaria.fulignoli@ericsson.com>, "Sami Boutros" <sboutros@cisco.com>, <martin.vigoureux@alcatel-lucent.com>, "Siva Sivabalan(msiva)" <msiva@cisco.com>, "David Ward" <dward@juniper.net>, <mpls-tp@ietf.org>, <mpls@ietf.org>
X-OriginalArrivalTime: 23 Jul 2010 18:21:58.0104 (UTC) FILETIME=[EFBF4580:01CB2A93]
Subject: Re: [mpls] Comments on draft-ietf-mpls-tp-cc-cv-rdi-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jul 2010 18:21:55 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB2A93.EF993102
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear Authors and All,

please find some comments below:

Issue 1:   inconsistent use of the abbreviation "CV"

 in the title the subject starts with "Proactive Connection
Verification..."=20

However, in the abstract the meaning of the abbreviation CV is
introduced as:

- Proactive Connectivity Verification (CV)

But in the section 2.1. Terminology the term CV is introduced as
follows:

CV: Connection Verification

Suggested resolution: The abbreviation CV should be used in an
unambiguous way throughout the document.

=20

Issue 2: Clarification of the difference between the terms
"Connectivity" and "Connection"

As the apparently ambigous use of the abbreviation "CV" shows, the terms
"connectivity" and "connection" may be used synonomously in some cases.
However, I believe the concepts "Connectivity" and "Connection" are
different.=20

Suggested Resolution: Provide a reference to where these terms are
defined, and double check if the usage of these terms is always aligned
with these definitions.

This should also help the reader in understanding the difference between
the terms "connectivity", "connection", and "path", which are all used
in the document, and perhaps also to the term "tunnel" in the meaning
"MPLS TP tunnel" as related to issue 3 below:

=20

Issue 3:  I am missing any mention of "MPLS-TP tunnels", even though an
important construct within MPLS_TP is a connection which is provided
across a working and a protection LSP.

Suggested Resolution: Consider adding a section "applicability to MPLS
TP tunnels",  or add some wording in some other way that explains, if cc
and cv are affected by the state of an MPLS TP tunnel being traversed,
e..g when the tunnel switches from the working LSP to the protection
LSP.

Best Regards, Lothar

	=20


------_=_NextPart_001_01CB2A93.EF993102
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.17063" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN lang=3DDE>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>Dear Authors and =
All,</SPAN></FONT></FONT></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D850222817-23072010>please=20
find some comments below:</SPAN></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>Issue 1:&nbsp; &nbsp;inconsistent use&nbsp;of =
the=20
abbreviation "CV"</SPAN></FONT></FONT></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>&nbsp;</SPAN>in the title the subject starts =
with=20
"Proactive Connection Verification..." </FONT></FONT></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>However, in the abstract =
the meaning of=20
the&nbsp;<SPAN class=3D850222817-23072010>abbreviation </SPAN>CV is =
introduced=20
as:</FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>- Proactive Connectivity =
Verification=20
(CV)</FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>But in the section 2.1. =
Terminology the=20
term CV is introduced as follows:</FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>CV: Connection =
Verification</FONT></P>
<P><SPAN class=3D850222817-23072010><FONT face=3DArial color=3D#0000ff=20
size=3D2>Suggested resolution: The abbreviation CV should be used in an=20
unambiguous way throughout the document.</FONT></SPAN></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</P>
<P><FONT><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>Issue 2: Clarification of the difference =
between the=20
terms "Connectivity" and =
"Connection"</SPAN></FONT></FONT></FONT></FONT></P>
<P><FONT><FONT><SPAN class=3D850222817-23072010></SPAN><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN class=3D850222817-23072010>As the =
apparently=20
ambigous use of the abbreviation "CV" shows, the terms "connectivity" =
and=20
"connection" may be used synonomously in some cases.&nbsp;&nbsp;However, =
I=20
believe the </SPAN>concepts "Connectivity" and "Connection" are =
different.=20
</FONT></FONT></FONT></FONT></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>Suggested Resolution:&nbsp;P</SPAN><SPAN=20
class=3D850222817-23072010>rovide a reference to where these terms are =
defined,=20
and double check if the usage of these terms is always aligned with =
these=20
definitions.</SPAN></FONT></FONT></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT =
size=3D2>This&nbsp;<SPAN=20
class=3D850222817-23072010>should also&nbsp;</SPAN>help the reader in=20
understanding the difference between the terms "connectivity", =
"connection", and=20
"path", which are all used in the document<SPAN =
class=3D850222817-23072010>, and=20
perhaps also to the term "tunnel" in the&nbsp;meaning "MPLS TP tunnel" =
as=20
related to issue 3 below:</SPAN></FONT></FONT></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010></SPAN></FONT></FONT></FONT>&nbsp;</P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>Issue 3:&nbsp; </SPAN>I&nbsp;<SPAN=20
class=3D850222817-23072010>am missing any mention of "MPLS-TP tunnels", =
even=20
though a</SPAN></FONT></FONT></FONT><FONT face=3DArial><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D850222817-23072010>n important construct within =
MPLS_TP is a=20
connection which is provided across a working and a protection=20
LSP.</SPAN></FONT></FONT></FONT></P>
<P><FONT><FONT><FONT face=3DArial><FONT color=3D#0000ff><FONT =
size=3D2><SPAN=20
class=3D850222817-23072010>Suggested Resolution: =
C</SPAN>onsider&nbsp;<SPAN=20
class=3D850222817-23072010>adding a</SPAN>&nbsp;section "applicability =
to MPLS TP=20
tunnels"<SPAN class=3D850222817-23072010>, </SPAN><SPAN=20
class=3D850222817-23072010>&nbsp;or&nbsp;add some wording in some other =
way that=20
explains, if cc and cv are affected by the state of an MPLS TP tunnel =
being=20
traversed, e..g when the tunnel switches from the working LSP to the =
protection=20
LSP.</SPAN></FONT></FONT></FONT></FONT></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>Best Regards,=20
Lothar</FONT></P></SPAN></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px"><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT>&nbsp;</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CB2A93.EF993102--

From david.i.allan@ericsson.com  Fri Jul 23 11:34:03 2010
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DA8E3A6A61; Fri, 23 Jul 2010 11:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level: 
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[AWL=1.747,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 8+-X5k+gvqSU; Fri, 23 Jul 2010 11:34:02 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 045C23A6A5A; Fri, 23 Jul 2010 11:34:01 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o6NIgJPa020225; Fri, 23 Jul 2010 13:42:39 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Fri, 23 Jul 2010 14:33:31 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "Reith, Lothar" <Lothar.Reith@detecon.com>, Greg Mirsky <gregimirsky@gmail.com>, John E Drake <jdrake@juniper.net>, "swallow@cisco.com" <swallow@cisco.com>, Annamaria Fulignoli <annamaria.fulignoli@ericsson.com>, Sami Boutros <sboutros@cisco.com>, "martin.vigoureux@alcatel-lucent.com" <martin.vigoureux@alcatel-lucent.com>,  "Siva Sivabalan(msiva)" <msiva@cisco.com>, David Ward <dward@juniper.net>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>,  "mpls@ietf.org" <mpls@ietf.org>
Date: Fri, 23 Jul 2010 14:33:29 -0400
Thread-Topic: [mpls] Comments on draft-ietf-mpls-tp-cc-cv-rdi-01
Thread-Index: AcspZN3XkgM9MZEQRwy7ItPtTED18wAU0yyAADUSMLAAAiLkkA==
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51AE51872A@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTimM750-lTglS8IpWQyFW6q_5KOGlPmutOsxm2Ju@mail.gmail.com> <60C093A41B5E45409A19D42CF7786DFD51AE4666BA@EUSAACMS0703.eamcs.ericsson.se> <8AAA8EFE7E4B594A86052935CF66E62E01845878@dc302v.detecon.com>
In-Reply-To: <8AAA8EFE7E4B594A86052935CF66E62E01845878@dc302v.detecon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_60C093A41B5E45409A19D42CF7786DFD51AE51872AEUSAACMS0703e_"
MIME-Version: 1.0
Subject: Re: [mpls] Comments on draft-ietf-mpls-tp-cc-cv-rdi-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jul 2010 18:34:03 -0000

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

hi Lothar:

Thanks for the suggested clarifications. We'll update the document accordin=
gly.

As for tunnel, we quite deliberately tended to steer away from any multiple=
 LSP constructs as we considered that out of scope of the document. That is=
 more of a survivability framework or draft-wiengarten topic. We are focuse=
d on the granularity of an LSP or bi-directional LSP pair (associated or co=
-routed). At the moment I do not see a reason to introduce tunnels into the=
 draft...

hope that helps
Dave



________________________________
From: Reith, Lothar [mailto:Lothar.Reith@detecon.com]
Sent: Friday, July 23, 2010 2:22 PM
To: David Allan I; Greg Mirsky; John E Drake; swallow@cisco.com; Annamaria =
Fulignoli; Sami Boutros; martin.vigoureux@alcatel-lucent.com; Siva Sivabala=
n(msiva); David Ward; mpls-tp@ietf.org; mpls@ietf.org
Subject: AW: [mpls] Comments on draft-ietf-mpls-tp-cc-cv-rdi-01


Dear Authors and All,

please find some comments below:

Issue 1:   inconsistent use of the abbreviation "CV"

 in the title the subject starts with "Proactive Connection Verification...=
"

However, in the abstract the meaning of the abbreviation CV is introduced a=
s:

- Proactive Connectivity Verification (CV)

But in the section 2.1. Terminology the term CV is introduced as follows:

CV: Connection Verification

Suggested resolution: The abbreviation CV should be used in an unambiguous =
way throughout the document.



Issue 2: Clarification of the difference between the terms "Connectivity" a=
nd "Connection"

As the apparently ambigous use of the abbreviation "CV" shows, the terms "c=
onnectivity" and "connection" may be used synonomously in some cases.  Howe=
ver, I believe the concepts "Connectivity" and "Connection" are different.

Suggested Resolution: Provide a reference to where these terms are defined,=
 and double check if the usage of these terms is always aligned with these =
definitions.

This should also help the reader in understanding the difference between th=
e terms "connectivity", "connection", and "path", which are all used in the=
 document, and perhaps also to the term "tunnel" in the meaning "MPLS TP tu=
nnel" as related to issue 3 below:



Issue 3:  I am missing any mention of "MPLS-TP tunnels", even though an imp=
ortant construct within MPLS_TP is a connection which is provided across a =
working and a protection LSP.

Suggested Resolution: Consider adding a section "applicability to MPLS TP t=
unnels",  or add some wording in some other way that explains, if cc and cv=
 are affected by the state of an MPLS TP tunnel being traversed, e..g when =
the tunnel switches from the working LSP to the protection LSP.

Best Regards, Lothar



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18470" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D980322918-23072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>hi Lothar:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D980322918-23072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D980322918-23072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Thanks for the suggested clarifications. We'll upd=
ate the=20
document accordingly.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D980322918-23072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D980322918-23072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>As for tunnel, we quite deliberately tended to ste=
er away=20
from any multiple LSP constructs as we considered that out of scope of the=
=20
document. That is more of a survivability framework or draft-wiengarten top=
ic.=20
We are focused on the granularity of an LSP or bi-directional LSP pair=20
(associated or co-routed). At the moment I do not see a reason to introduce=
=20
tunnels into the draft...</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D980322918-23072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D980322918-23072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>hope that helps</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D980322918-23072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Dave</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D980322918-23072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D980322918-23072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Reith, Lothar=20
[mailto:Lothar.Reith@detecon.com] <BR><B>Sent:</B> Friday, July 23, 2010 2:=
22=20
PM<BR><B>To:</B> David Allan I; Greg Mirsky; John E Drake; swallow@cisco.co=
m;=20
Annamaria Fulignoli; Sami Boutros; martin.vigoureux@alcatel-lucent.com; Siv=
a=20
Sivabalan(msiva); David Ward; mpls-tp@ietf.org; mpls@ietf.org<BR><B>Subject=
:</B>=20
AW: [mpls] Comments on draft-ietf-mpls-tp-cc-cv-rdi-01<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN lang=3DDE>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>Dear Authors and All,</SPAN></FONT></FONT></FONT=
></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D850222817-2307=
2010>please=20
find some comments below:</SPAN></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>Issue 1:&nbsp; &nbsp;inconsistent use&nbsp;of th=
e=20
abbreviation "CV"</SPAN></FONT></FONT></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>&nbsp;</SPAN>in the title the subject starts wit=
h=20
"Proactive Connection Verification..." </FONT></FONT></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>However, in the abstract the=
 meaning of=20
the&nbsp;<SPAN class=3D850222817-23072010>abbreviation </SPAN>CV is introdu=
ced=20
as:</FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>- Proactive Connectivity Ver=
ification=20
(CV)</FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>But in the section 2.1. Term=
inology the=20
term CV is introduced as follows:</FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>CV: Connection Verification<=
/FONT></P>
<P><SPAN class=3D850222817-23072010><FONT face=3DArial color=3D#0000ff=20
size=3D2>Suggested resolution: The abbreviation CV should be used in an=20
unambiguous way throughout the document.</FONT></SPAN></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</P>
<P><FONT size=3D+0><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2>=
<SPAN=20
class=3D850222817-23072010>Issue 2: Clarification of the difference between=
 the=20
terms "Connectivity" and "Connection"</SPAN></FONT></FONT></FONT></FONT></P=
>
<P><FONT size=3D+0><FONT size=3D+0><SPAN class=3D850222817-23072010></SPAN>=
<FONT=20
face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN class=3D850222817-2=
3072010>As=20
the apparently ambigous use of the abbreviation "CV" shows, the terms=20
"connectivity" and "connection" may be used synonomously in some=20
cases.&nbsp;&nbsp;However, I believe the </SPAN>concepts "Connectivity" and=
=20
"Connection" are different. </FONT></FONT></FONT></FONT></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>Suggested Resolution:&nbsp;P</SPAN><SPAN=20
class=3D850222817-23072010>rovide a reference to where these terms are defi=
ned,=20
and double check if the usage of these terms is always aligned with these=20
definitions.</SPAN></FONT></FONT></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2>This&nbsp;<SPAN=
=20
class=3D850222817-23072010>should also&nbsp;</SPAN>help the reader in=20
understanding the difference between the terms "connectivity", "connection"=
, and=20
"path", which are all used in the document<SPAN class=3D850222817-23072010>=
, and=20
perhaps also to the term "tunnel" in the&nbsp;meaning "MPLS TP tunnel" as=20
related to issue 3 below:</SPAN></FONT></FONT></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010></SPAN></FONT></FONT></FONT>&nbsp;</P>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D850222817-23072010>Issue 3:&nbsp; </SPAN>I&nbsp;<SPAN=20
class=3D850222817-23072010>am missing any mention of "MPLS-TP tunnels", eve=
n=20
though a</SPAN></FONT></FONT></FONT><FONT face=3DArial><FONT color=3D#0000f=
f><FONT=20
size=3D2><SPAN class=3D850222817-23072010>n important construct within MPLS=
_TP is a=20
connection which is provided across a working and a protection=20
LSP.</SPAN></FONT></FONT></FONT></P>
<P><FONT size=3D+0><FONT size=3D+0><FONT face=3DArial><FONT color=3D#0000ff=
><FONT=20
size=3D2><SPAN class=3D850222817-23072010>Suggested Resolution:=20
C</SPAN>onsider&nbsp;<SPAN class=3D850222817-23072010>adding a</SPAN>&nbsp;=
section=20
"applicability to MPLS TP tunnels"<SPAN class=3D850222817-23072010>, </SPAN=
><SPAN=20
class=3D850222817-23072010>&nbsp;or&nbsp;add some wording in some other way=
 that=20
explains, if cc and cv are affected by the state of an MPLS TP tunnel being=
=20
traversed, e..g when the tunnel switches from the working LSP to the protec=
tion=20
LSP.</SPAN></FONT></FONT></FONT></FONT></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>Best Regards,=20
Lothar</FONT></P></SPAN></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px"><FONT face=3DArial color=3D#0000ff=
=20
  size=3D2></FONT>&nbsp;</BLOCKQUOTE></BODY></HTML>

--_000_60C093A41B5E45409A19D42CF7786DFD51AE51872AEUSAACMS0703e_--

From wwwrun@core3.amsl.com  Fri Jul 23 14:31:30 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 22BA83A68D3; Fri, 23 Jul 2010 14:30:47 -0700 (PDT)
From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: lberger@labn.net, dbrungard@att.com, andrew.g.malis@verizon.com, matthew.bocci@alcatel-lucent.com, swallow@cisco.com, loa@pi.nu
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100723213112.22BA83A68D3@core3.amsl.com>
Date: Fri, 23 Jul 2010 14:30:48 -0700 (PDT)
Cc: mpls@ietf.org, hiroshi.ota@itu.int, greg.jones@itu.int, steve.trowbridge@alcatel-lucent.com, malcolm.betts@zte.com.cn, ccamp@ietf.org, yoichi.maeda@ntt-at.co.jp, pwe3@ietf.org, adrian.farrel@huawei.com, tsbsg15@itu.int, rcallon@juniper.net, paf@cisco.com, stbryant@cisco.com
Subject: [mpls] New Liaison Statement, "LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref # 036.02]"
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tsbsg15@itu.int
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jul 2010 21:31:31 -0000

Title: LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref # 036.02]
Submission Date: 2010-07-23
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=938 
Please reply by 2010-08-16

From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: IETF MPLS, CCAMP and PWE3  WGs(lberger@labn.net,dbrungard@att.com,andrew.g.malis@verizon.com,matthew.bocci@alcatel-lucent.com,swallow@cisco.com,loa@pi.nu)
Cc: paf@cisco.com
stbryant@cisco.com
adrian.farrel@huawei.com
rcallon@juniper.net
mpls@ietf.org
pwe3@ietf.org
ccamp@ietf.org
yoichi.maeda@ntt-at.co.jp
steve.trowbridge@alcatel-lucent.com
Reponse Contact: tsbsg15@itu.int
greg.jones@itu.int
hiroshi.ota@itu.int
Technical Contact: malcolm.betts@zte.com.cn
Kam.Lam@alcatel-lucent.com
Purpose: For action 
Body: 
Attachment(s):
     LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref # 036.02] - pdf body (https://datatracker.ietf.org/documents/LIAISON/file1087.pdf)
     LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref # 036.02] - pdf attach (https://datatracker.ietf.org/documents/LIAISON/file1088.pdf)




From cts@etri.re.kr  Mon Jul 26 01:31:06 2010
Return-Path: <cts@etri.re.kr>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 200B33A6AB8; Mon, 26 Jul 2010 01:31:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.41
X-Spam-Level: 
X-Spam-Status: No, score=-100.41 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, MPART_ALT_DIFF=0.739, 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 U1WHh5f2Dx1f; Mon, 26 Jul 2010 01:31:03 -0700 (PDT)
Received: from email1.etri.info (email1.etri.re.kr [129.254.16.131]) by core3.amsl.com (Postfix) with ESMTP id 2C8B93A6A8B; Mon, 26 Jul 2010 01:31:02 -0700 (PDT)
Received: from mail pickup service by email1.etri.info with Microsoft SMTPSVC;  Mon, 26 Jul 2010 17:31:21 +0900
priority: normal
thread-index: AcssnOzNaXabtMrrSeC6r5LEx1sJqg==
Thread-Topic: New Version Notification for draft-cheung-mpls-tp-mesh-protection-01 
From: "Taesik Cheung" <cts@etri.re.kr>
To: <mpls-tp@ietf.org>, <mpls@ietf.org>
Date: Mon, 26 Jul 2010 17:31:20 +0900
Comment: ??, ??, 
Message-ID: <C8CE7EEF373C43DD9AD854B245104CE2@etri.info>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_ABCE_01CB2CE8.5CB4AAD0"
X-Mailer: Microsoft CDO for Exchange 2000
Content-Class: urn:content-classes:message
Importance: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
X-OriginalArrivalTime: 26 Jul 2010 08:31:21.0160 (UTC) FILETIME=[ECEBFC80:01CB2C9C]
Subject: [mpls] FW: New Version Notification for draft-cheung-mpls-tp-mesh-protection-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Taesik Cheung <cts@etri.re.kr>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 08:31:06 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_ABCE_01CB2CE8.5CB4AAD0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64


------=_NextPart_000_ABCE_01CB2CE8.5CB4AAD0
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IEFyaWFsOyBGT05ULVNJWkU6IDEwcHQiIGlkPW1zZ2Jv
ZHk+DQo8RElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IOq1tOumvDsgRk9OVC1TSVpFOiAx
MHB0Ij48Rk9OVCBmYWNlPUFyaWFsPkRlYXIgTVBMUyBXRyw8L0ZPTlQ+PC9ESVY+DQo8RElWIHN0
eWxlPSJGT05ULUZBTUlMWTog6rW066a8OyBGT05ULVNJWkU6IDEwcHQiPjxGT05UIGZhY2U9QXJp
YWw+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IOq1tOumvDsg
Rk9OVC1TSVpFOiAxMHB0Ij48Rk9OVCBmYWNlPUFyaWFsPlBsZWFzZSBub3RlIHRoYXQgd2Ugc3Vi
bWl0dGVkIGEgbmV3IHZlcnNpb24mbmJzcDtvZiB0aGUgTVBMUy1UUCBzaGFyZWQgbWVzaCBwcm90
ZWN0aW9uLjwvRk9OVD48L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtRkFNSUxZOiDqtbTrprw7IEZP
TlQtU0laRTogMTBwdCI+PEZPTlQgZmFjZT1BcmlhbD5JbiB0aGlzIHZlcnNpb24sIHRoZSBtZWNo
YW5pc20gaGFzIGJlZW4gcmVmaW5lZCBhbmQgZGV0YWlsZWQsIGFuZCBzb21lIHRlY2huaWNhbCBp
c3N1ZXMgaW4gdGhlIHByZXZpb3VzIHZlcnNpb24gYXJlIHJlc29sdmVkLjwvRk9OVD48L0RJVj4N
CjxESVYgc3R5bGU9IkZPTlQtRkFNSUxZOiDqtbTrprw7IEZPTlQtU0laRTogMTBwdCI+PEZPTlQg
ZmFjZT1BcmlhbD48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTog
6rW066a8OyBGT05ULVNJWkU6IDEwcHQiPjxGT05UIGZhY2U9QXJpYWw+QSBVUkwgZm9yIHRoaXMm
bmJzcDtJLUQgaXM6PC9GT05UPjwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IOq1tOum
vDsgRk9OVC1TSVpFOiAxMHB0Ij48Rk9OVCBmYWNlPUFyaWFsPjxBIGhyZWY9Imh0dHA6Ly93d3cu
aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWNoZXVuZy1tcGxzLXRwLW1lc2gtcHJvdGVj
dGlvbi0wMS50eHQiIHRhcmdldD1fYmxhbms+aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1k
cmFmdHMvZHJhZnQtY2hldW5nLW1wbHMtdHAtbWVzaC1wcm90ZWN0aW9uLTAxLnR4dDwvQT48L0ZP
TlQ+PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTog6rW066a8OyBGT05ULVNJWkU6IDEw
cHQiPjxGT05UIGZhY2U9QXJpYWw+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJViBzdHlsZT0iRk9O
VC1GQU1JTFk6IOq1tOumvDsgRk9OVC1TSVpFOiAxMHB0Ij48Rk9OVCBmYWNlPUFyaWFsPldlIHdv
dWxkIGFwcHJlY2lhdGUgcmV2aWV3IGFuZCBjb21tZW50cyBmb3Igb3VyIGRvY3VtZW50LjwvRk9O
VD48L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtRkFNSUxZOiDqtbTrprw7IEZPTlQtU0laRTogMTBw
dCI+PEZPTlQgZmFjZT1BcmlhbD48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWIHN0eWxlPSJGT05U
LUZBTUlMWTog6rW066a8OyBGT05ULVNJWkU6IDEwcHQiPjxGT05UIGZhY2U9QXJpYWw+QmVzdCBy
ZWdhcmRzLDwvRk9OVD48L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtRkFNSUxZOiDqtbTrprw7IEZP
TlQtU0laRTogMTBwdCI+PEZPTlQgZmFjZT1BcmlhbD5UYWVzaWs8L0ZPTlQ+PC9ESVY+DQo8RElW
IHN0eWxlPSJGT05ULUZBTUlMWTog6rW066a8OyBGT05ULVNJWkU6IDEwcHQiPjxGT05UIGZhY2U9
QXJpYWw+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IOq1tOum
vDsgRk9OVC1TSVpFOiAxMHB0Ij48Rk9OVCBmYWNlPUFyaWFsPjwvRk9OVD4mbmJzcDs8L0RJVj4N
CjxESVY+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08QlI+PEI+RnJvbTo8L0I+ICJJRVRGIEkt
RCBTdWJtaXNzaW9uIFRvb2wiICZsdDtpZHN1Ym1pc3Npb25AaWV0Zi5vcmcmZ3Q7PEJSPjxCPkZy
b20gRGF0ZTo8L0I+IDIwMTAtMDctMjYgUE0gNTowNToyOTxCUj48Qj5Ubzo8L0I+ICJjdHNAZXRy
aS5yZS5rciIgJmx0O2N0c0BldHJpLnJlLmtyJmd0OzxCUj48Qj5DYzo8L0I+ICJyeW9vQGV0cmku
cmUua3IiICZsdDtyeW9vQGV0cmkucmUua3ImZ3Q7PEJSPjxCPlN1YmplY3Q6PC9CPiBOZXcgVmVy
c2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWNoZXVuZy1tcGxzLXRwLW1lc2gtcHJvdGVjdGlv
bi0wMSA8QlI+PCEtLSBDb252ZXJ0ZWQgZnJvbSB0ZXh0L3BsYWluIGZvcm1hdCAtLT48L0RJVj4N
CjxESVY+DQo8UD48Rk9OVCBzaXplPTI+QSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWNoZXVu
Zy1tcGxzLXRwLW1lc2gtcHJvdGVjdGlvbi0wMS50eHQgaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1
Ym1pdHRlZCBieSBUYWUtc2lrIENoZXVuZyBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRv
cnkuPEJSPjxCUj5GaWxlbmFtZTombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgZHJhZnQtY2hldW5nLW1wbHMtdHAtbWVzaC1wcm90ZWN0aW9uPEJSPlJldmlzaW9uOiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAwMTxCUj5UaXRsZTombmJz
cDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IE1QTFMt
VFAgU2hhcmVkIE1lc2ggUHJvdGVjdGlvbjxCUj5DcmVhdGlvbl9kYXRlOiZuYnNwOyZuYnNwOyAy
MDEwLTA3LTI2PEJSPldHIElEOiZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgSW5kZXBlbmRlbnQgU3VibWlzc2lvbjxCUj5OdW1iZXJfb2ZfcGFn
ZXM6IDE4PEJSPjxCUj5BYnN0cmFjdDo8QlI+VGhpcyBkb2N1bWVudCBkZXNjcmliZXMgYSBtZWNo
YW5pc20gdG8gYWRkcmVzcyB0aGUgcmVxdWlyZW1lbnQgZm9yPEJSPnByb3RlY3Rpb24gb2YgTGFi
ZWwgU3dpdGNoZWQgUGF0aHMgKExTUHMpIGluIGFuIE1QTFMgVHJhbnNwb3J0PEJSPlByb2ZpbGUg
KE1QTFMtVFApIG1lc2ggdG9wb2xvZ3kuIFRoZSBzaGFyZWQgbWVzaCBwcm90ZWN0aW9uIG1lY2hh
bmlzbTxCUj5lbmFibGVzIG11bHRpcGxlIHByb3RlY3Rpb24gcGF0aHMgd2l0aGluIGEgc2hhcmVk
IG1lc2ggcHJvdGVjdGlvbjxCUj5kb21haW4gdG8gc2hhcmUgcHJvdGVjdGlvbiByZXNvdXJjZXMg
Zm9yIHRoZSBwcm90ZWN0aW9uIG9mIHdvcmtpbmc8QlI+cGF0aHMgYnkgY29vcmRpbmF0aW5nIHBy
b3RlY3Rpb24gc3dpdGNoaW5nIG9wZXJhdGlvbnMgYWNjb3JkaW5nIHRvPEJSPnRoZSBwcmlvcml0
eSBhc3NpZ25lZCB0byBlYWNoIGVuZC10by1lbmQgbGluZWFyIHByb3RlY3Rpb24gZG9tYWluLjxC
Uj48QlI+VGhpcyBkb2N1bWVudCBpcyBhIHByb2R1Y3Qgb2YgYSBqb2ludCBJbnRlcm5ldCBFbmdp
bmVlcmluZyBUYXNrIEZvcmNlPEJSPihJRVRGKSAvIEludGVybmF0aW9uYWwgVGVsZWNvbW11bmlj
YXRpb24gVW5pb24gVGVsZWNvbW11bmljYXRpb248QlI+U3RhbmRhcmRpemF0aW9uIFNlY3RvciAo
SVRVLVQpIGVmZm9ydCB0byBpbmNsdWRlIGFuIE1QTFMgVHJhbnNwb3J0PEJSPlByb2ZpbGUgd2l0
aGluIHRoZSBJRVRGIE1QTFMgYW5kIFBXRTMgYXJjaGl0ZWN0dXJlcyB0byBzdXBwb3J0IHRoZTxC
Uj5jYXBhYmlsaXRpZXMgYW5kIGZ1bmN0aW9uYWxpdGllcyBvZiBhIHBhY2tldCB0cmFuc3BvcnQg
bmV0d29yay48QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PEJSPjxCUj48QlI+VGhl
IElFVEYgU2VjcmV0YXJpYXQuPEJSPjxCUj48QlI+PC9GT05UPjwvUD48L0RJVj48L0RJVj48L0RJ
Vj4=

------=_NextPart_000_ABCE_01CB2CE8.5CB4AAD0--

From root@core3.amsl.com  Mon Jul 26 02:15:07 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 33E593A6ADC; Mon, 26 Jul 2010 02:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100726091504.33E593A6ADC@core3.amsl.com>
Date: Mon, 26 Jul 2010 02:15:01 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-tp-on-demand-cv-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 09:15:14 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.


	Title           : MPLS on-demand Connectivity Verification, Route Tracing and Adjacency Verification
	Author(s)       : N. Bahadur, et al.
	Filename        : draft-ietf-mpls-tp-on-demand-cv-00.txt
	Pages           : 14
	Date            : 2010-07-26

LSP-Ping is an existing and widely deployed OAM mechanism for MPLS
LSPs.  This document describes extensions to LSP-Ping so that LSP-
Ping can be used to perform OAM on MPLS-TP LSPs.  It also clarifies
the procedures to be used for processing the OAM packets.  Further,
it describes how LSP-Ping can be used to perform Connectivity
Verification, Route Tracing and Adjacency functions in MPLS-TP
networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-on-demand-cv-00.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-mpls-tp-on-demand-cv-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-26020615.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Mon Jul 26 05:30:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 6D76C3A6AD5; Mon, 26 Jul 2010 05:30:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100726123002.6D76C3A6AD5@core3.amsl.com>
Date: Mon, 26 Jul 2010 05:30:02 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-tp-loss-delay-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 12:30:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.


	Title           : Packet Loss and Delay Measurement for the MPLS Transport Profile
	Author(s)       : D. Frost, S. Bryant
	Filename        : draft-ietf-mpls-tp-loss-delay-00.txt
	Pages           : 30
	Date            : 2010-07-26

An essential Operations, Administration and Maintenance requirement
of the MPLS Transport Profile (MPLS-TP) is the ability to monitor
performance metrics for packet loss and one-way and two-way delay for
MPLS-TP pseudowires, Label Switched Paths, and Sections.  This
document specifies protocol mechanisms to facilitate the efficient
and accurate measurement of these performance metrics.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-loss-delay-00.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-mpls-tp-loss-delay-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-26052910.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Mon Jul 26 07:45:03 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id E901A3A695A; Mon, 26 Jul 2010 07:45:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100726144502.E901A3A695A@core3.amsl.com>
Date: Mon, 26 Jul 2010 07:45:02 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-ldp-upstream-08.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 14: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 Multiprotocol Label Switching Working Group of the IETF.


	Title           : MPLS Upstream Label Assignment for LDP
	Author(s)       : R. Aggarwal, J. Le Roux
	Filename        : draft-ietf-mpls-ldp-upstream-08.txt
	Pages           : 14
	Date            : 2010-07-26

This document describes procedures for distributing upstream-assigned
labels for Label Distribution Protocol (LDP). It also describes how
these procedures can be used for avoiding branch Label Switching
Router (LSR) traffic replication on a LAN for LDP point-to-multipoint
(P2MP) Label Switched Paths (LSPs).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-upstream-08.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-mpls-ldp-upstream-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-26073612.I-D@ietf.org>


--NextPart--

From ice@cisco.com  Mon Jul 26 09:14:42 2010
Return-Path: <ice@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5E753A6C59 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 09:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N+OCUxoVozf3 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 09:14:36 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 3F5753A6C18 for <mpls@ietf.org>; Mon, 26 Jul 2010 09:14:36 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o6QGBB5n014236; Mon, 26 Jul 2010 18:11:11 +0200 (CEST)
Received: from dhcp-10-55-89-206.cisco.com (dhcp-10-55-89-206.cisco.com [10.55.89.206]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o6QGB9qO014196; Mon, 26 Jul 2010 18:11:10 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <OF9FACC9F5.C63E2CB7-ON48257746.004F0080-48257746.0052FF85@zte.com.cn>
Date: Mon, 26 Jul 2010 18:11:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E756ED44-CBFE-417F-BDDA-37913EAC4F8B@cisco.com>
References: <OF9FACC9F5.C63E2CB7-ON48257746.004F0080-48257746.0052FF85@zte.com.cn>
To: lizhong.jin@zte.com.cn
X-Mailer: Apple Mail (2.1077)
Cc: mpls@ietf.org
Subject: Re: [mpls] [MPLS] Next hop address in mLDP
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 16:14:42 -0000

Hi Lizhong,

About your comment at the mic.

I guess this is the question that did not get addressed in the latest =
revision, sorry about that.

I'll discuss with the c-authors and get back to you.

Thx,

Ice.


On 18 Jun 2010, at 17:06, lizhong.jin@zte.com.cn wrote:

> Hi Ice,
> For draft-ietf-mpls-ldp-p2mp-09, on a LAN, the procedures discussed=20
> supports that the upstream LSR can send a copy of the packet to each=20=

> receiver individually. The question is how to get the next hop address =
for=20
> each receiver? There maybe the following method:
> 1. upstream LSP gets an IP address A from the downstream receiver, =
either=20
> the hello packet source address or transport address;
> 2. looking up the local IP forwarding table for the address A, and =
check=20
> if the corresponding next hop address is in the LDP session address =
list.=20
> If it is, then the next hop address is found, if not, then next hop=20
> address found failure.
>=20
> I think some description is necessary in the draft about this.
>=20
> BR
> Lizhong
>=20
>=20
>=20
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this =
mail is solely property of the sender's organization. This mail =
communication is confidential. Recipients named above are obligated to =
maintain secrecy and are not permitted to disclose the contents of this =
communication to others.
> This email and any files transmitted with it are confidential and =
intended solely for the use of the individual or entity to whom they are =
addressed. If you have received this email in error please notify the =
originator of the message. Any views expressed in this message are those =
of the individual sender.
> This message has been scanned for viruses and Spam by ZTE Anti-Spam =
system.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From wwwrun@core3.amsl.com  Mon Jul 26 09:14:50 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id AE5CF3A6C62; Mon, 26 Jul 2010 09:14:50 -0700 (PDT)
From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: lberger@labn.net, dbrungard@att.com, andrew.g.malis@verizon.com, matthew.bocci@alcatel-lucent.com, swallow@cisco.com, loa@pi.nu
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100726161450.AE5CF3A6C62@core3.amsl.com>
Date: Mon, 26 Jul 2010 09:14:50 -0700 (PDT)
Cc: mpls@ietf.org, hiroshi.ota@itu.int, greg.jones@itu.int, steve.trowbridge@alcatel-lucent.com, malcolm.betts@zte.com.cn, ccamp@ietf.org, yoichi.maeda@ntt-at.co.jp, pwe3@ietf.org, adrian.farrel@huawei.com, tsbsg15@itu.int, rcallon@juniper.net, paf@cisco.com, stbryant@cisco.com
Subject: [mpls] Updated Liaison Statement, "LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref # 036.02]"
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tsbsg15@itu.int
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 16:14:51 -0000

Title: LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref # 036.02]
Submission Date: 2010-07-23
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=938 
Please reply by 2010-08-16

From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: IETF MPLS, CCAMP and PWE3  WGs(lberger@labn.net,dbrungard@att.com,andrew.g.malis@verizon.com,matthew.bocci@alcatel-lucent.com,swallow@cisco.com,loa@pi.nu)
Cc: paf@cisco.com
stbryant@cisco.com
adrian.farrel@huawei.com
rcallon@juniper.net
mpls@ietf.org
pwe3@ietf.org
ccamp@ietf.org
yoichi.maeda@ntt-at.co.jp
steve.trowbridge@alcatel-lucent.com
Reponse Contact: tsbsg15@itu.int
greg.jones@itu.int
hiroshi.ota@itu.int
Technical Contact: malcolm.betts@zte.com.cn
Kam.Lam@alcatel-lucent.com
Purpose: For action 
Body: 
Attachment(s):
     LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref # 036.02] - pdf body (https://datatracker.ietf.org/documents/LIAISON/file1087.pdf)
     LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref # 036.02] - pdf attach (https://datatracker.ietf.org/documents/LIAISON/file1089.pdf)




From lizhong.jin@zte.com.cn  Mon Jul 26 09:27:17 2010
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A7023A6908 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 09:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.655
X-Spam-Level: 
X-Spam-Status: No, score=-102.655 tagged_above=-999 required=5 tests=[AWL=-0.817, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, 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 hNXGvIvrVktW for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 09:27:15 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 4082A3A67B6 for <mpls@ietf.org>; Mon, 26 Jul 2010 09:27:14 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 3510806486374; Tue, 27 Jul 2010 00:26:51 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 96784.5546608072; Tue, 27 Jul 2010 00:19:17 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o6QGRhL9049744; Tue, 27 Jul 2010 00:27:44 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <E756ED44-CBFE-417F-BDDA-37913EAC4F8B@cisco.com>
To: IJsbrand Wijnands <ice@cisco.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF75B2DFDC.371F732E-ON4825776C.005A33A2-4825776C.005A6432@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Tue, 27 Jul 2010 00:26:33 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2010-07-27 00:27:19, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2010-07-27 00:27:19, Serialize complete at 2010-07-27 00:27:19, S/MIME Sign failed at 2010-07-27 00:27:19: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-27 00:27:25, Serialize complete at 2010-07-27 00:27:25
Content-Type: multipart/alternative; boundary="=_alternative 005A642F4825776C_="
X-MAIL: mse2.zte.com.cn o6QGRhL9049744
Cc: mpls@ietf.org
Subject: Re: [mpls] [MPLS] Next hop address in mLDP
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 16:27:17 -0000

This is a multipart message in MIME format.
--=_alternative 005A642F4825776C_=
Content-Type: text/plain; charset="US-ASCII"

Dear Ice,
Thank you for your reply. Just because I think this issue is important. 
That's great we will address this issue in the new version.

BR
Lizhong

 


IJsbrand Wijnands <ice@cisco.com> 
2010-07-27 00:11

To
lizhong.jin@zte.com.cn
cc
kireeti@juniper.net, bobthomas@alum.mit.edu, ina@juniper.net, 
mpls@ietf.org
Subject
Re: [mpls] [MPLS] Next hop address in mLDP






Hi Lizhong,

About your comment at the mic.

I guess this is the question that did not get addressed in the latest 
revision, sorry about that.

I'll discuss with the c-authors and get back to you.

Thx,

Ice.


On 18 Jun 2010, at 17:06, lizhong.jin@zte.com.cn wrote:

> Hi Ice,
> For draft-ietf-mpls-ldp-p2mp-09, on a LAN, the procedures discussed 
> supports that the upstream LSR can send a copy of the packet to each 
> receiver individually. The question is how to get the next hop address 
for 
> each receiver? There maybe the following method:
> 1. upstream LSP gets an IP address A from the downstream receiver, 
either 
> the hello packet source address or transport address;
> 2. looking up the local IP forwarding table for the address A, and check 

> if the corresponding next hop address is in the LDP session address 
list. 
> If it is, then the next hop address is found, if not, then next hop 
> address found failure.
> 
> I think some description is necessary in the draft about this.
> 
> BR
> Lizhong
> 
> 
> 
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail 
is solely property of the sender's organization. This mail communication 
is confidential. Recipients named above are obligated to maintain secrecy 
and are not permitted to disclose the contents of this communication to 
others.
> This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error please notify the 
originator of the message. Any views expressed in this message are those 
of the individual sender.
> This message has been scanned for viruses and Spam by ZTE Anti-Spam 
system.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls





--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 005A642F4825776C_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Dear Ice,</font>
<br><font size=2 face="sans-serif">Thank you for your reply. Just because
I think this issue is important. That's great we will address this issue
in the new version.</font>
<br>
<br><font size=2 face="sans-serif">BR</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=35%><font size=1 face="sans-serif"><b>IJsbrand Wijnands &lt;ice@cisco.com&gt;</b>
</font>
<p><font size=1 face="sans-serif">2010-07-27 00:11</font>
<td width=64%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">lizhong.jin@zte.com.cn</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">kireeti@juniper.net, bobthomas@alum.mit.edu,
ina@juniper.net, mpls@ietf.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [mpls] [MPLS] Next hop address in
mLDP</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Hi Lizhong,<br>
<br>
About your comment at the mic.<br>
<br>
I guess this is the question that did not get addressed in the latest revision,
sorry about that.<br>
<br>
I'll discuss with the c-authors and get back to you.<br>
<br>
Thx,<br>
<br>
Ice.<br>
<br>
<br>
On 18 Jun 2010, at 17:06, lizhong.jin@zte.com.cn wrote:<br>
<br>
&gt; Hi Ice,<br>
&gt; For draft-ietf-mpls-ldp-p2mp-09, on a LAN, the procedures discussed
<br>
&gt; supports that the upstream LSR can send a copy of the packet to each
<br>
&gt; receiver individually. The question is how to get the next hop address
for <br>
&gt; each receiver? There maybe the following method:<br>
&gt; 1. upstream LSP gets an IP address A from the downstream receiver,
either <br>
&gt; the hello packet source address or transport address;<br>
&gt; 2. looking up the local IP forwarding table for the address A, and
check <br>
&gt; if the corresponding next hop address is in the LDP session address
list. <br>
&gt; If it is, then the next hop address is found, if not, then next hop
<br>
&gt; address found failure.<br>
&gt; <br>
&gt; I think some description is necessary in the draft about this.<br>
&gt; <br>
&gt; BR<br>
&gt; Lizhong<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; --------------------------------------------------------<br>
&gt; ZTE Information Security Notice: The information contained in this
mail is solely property of the sender's organization. This mail communication
is confidential. Recipients named above are obligated to maintain secrecy
and are not permitted to disclose the contents of this communication to
others.<br>
&gt; This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the originator
of the message. Any views expressed in this message are those of the individual
sender.<br>
&gt; This message has been scanned for viruses and Spam by ZTE Anti-Spam
system.<br>
&gt; _______________________________________________<br>
&gt; mpls mailing list<br>
&gt; mpls@ietf.org<br>
&gt; https://www.ietf.org/mailman/listinfo/mpls<br>
<br>
<br>
</font></tt>
<br><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 005A642F4825776C_=--


From Martin.Vigoureux@alcatel-lucent.com  Mon Jul 26 09:29:08 2010
Return-Path: <Martin.Vigoureux@alcatel-lucent.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AD1B3A694D; Mon, 26 Jul 2010 09:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 F+DjPSDDKPm4; Mon, 26 Jul 2010 09:29:07 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 77F663A6BC3; Mon, 26 Jul 2010 09:29:07 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.dc-m.alcatel-lucent.com [155.132.6.78]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o6QGTR2A021823;  Mon, 26 Jul 2010 18:29:27 +0200
Received: from [135.244.37.153] ([135.244.37.153]) by FRVELSBHS06.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 26 Jul 2010 18:29:27 +0200
Message-ID: <4C4DB7E1.4060305@alcatel-lucent.com>
Date: Mon, 26 Jul 2010 18:29:21 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "MPLS @ IETF" <mpls@ietf.org>, mpls-tp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jul 2010 16:29:27.0498 (UTC) FILETIME=[B74FCAA0:01CB2CDF]
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Subject: [mpls] Important - slides for mpls sessions - please read
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 16:29:08 -0000

to all presenters of Wednesday session,

it appears that I have lost e-mails and so possibly your e-mail that 
contained your presentation.
To all of you that sent me such e-mail prior to today please resend.
Sorry for the inconvenience.

Thank you.
martin

From root@core3.amsl.com  Mon Jul 26 09:45:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id A4CE73A6C27; Mon, 26 Jul 2010 09:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100726164502.A4CE73A6C27@core3.amsl.com>
Date: Mon, 26 Jul 2010 09:45:01 -0700 (PDT)
Cc: mpls@ietf.org
Subject: [mpls] I-D Action:draft-ietf-mpls-tp-linear-protection-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 16: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 Multiprotocol Label Switching Working Group of the IETF.


	Title           : MPLS-TP Linear Protection
	Author(s)       : S. Bryant, et al.
	Filename        : draft-ietf-mpls-tp-linear-protection-02.txt
	Pages           : 30
	Date            : 2010-07-26

The Transport Profile for Multiprotocol Label Switching (MPLS-TP) is
being specified jointly by IETF and ITU-T.  This document addresses
the functionality described in the MPLS-TP Survivability Framework
document [SurvivFwk] and defines a protocol that may be used to
fulfill the function of the Protection State Coordination for linear
protection, as described in that document.

This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunications Union Telecommunications
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network as
defined by the ITU-T.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-linear-protection-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-mpls-tp-linear-protection-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-26094015.I-D@ietf.org>


--NextPart--

From Alexander.Vainshtein@ecitele.com  Mon Jul 26 09:56:46 2010
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83ABA3A6A69 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 09:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.183
X-Spam-Level: 
X-Spam-Status: No, score=-2.183 tagged_above=-999 required=5 tests=[AWL=0.415,  BAYES_00=-2.599, HTML_MESSAGE=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 p2LAFxU1QTef for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 09:56:45 -0700 (PDT)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 2361C3A6407 for <mpls@ietf.org>; Mon, 26 Jul 2010 09:56:44 -0700 (PDT)
Received: from DLP_bound_connection ( [147.234.242.234]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id B0.19.32431.06EBD4C4; Mon, 26 Jul 2010 19:57:04 +0300 (IDT)
X-AuditID: 93eaf2e7-b7c6dae000007eaf-41-4c4dbe609227
Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 80.19.32431.06EBD4C4; Mon, 26 Jul 2010 19:57:04 +0300 (IDT)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Mon, 26 Jul 2010 19:57:04 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "sriganesh.kini@ericsson.com" <sriganesh.kini@ericsson.com>
Date: Mon, 26 Jul 2010 19:57:21 +0300
Thread-Topic: Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUA==
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D5BB4A3ED3@ILPTMAIL02.ecitele.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A3C5DF08D38B6049839A6F553B331C76D5BB4A3ED3ILPTMAIL02eci_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 16:56:46 -0000

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

Sriganesh and all,
If I understood you correctly, your proposal requires a dedicated backup tu=
nnel for all LSPs with the given {head-end, tail-end} pair of LSRs in the r=
ing. (Regular facility FRR requires just two backup tunnels).
If this understanding is correct, this looks to like a serious scalability =
issue with your approach.

Regards,
     Sasha


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>Sriganesh and all,<o:=
p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>If I understood you
correctly, your proposal requires a dedicated backup tunnel for all LSPs wi=
th
the given {head-end, tail-end} pair of LSRs in the ring. (Regular facility =
FRR
requires just two backup tunnels).<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>If this understanding=
 is
correct, this looks to like a serious scalability issue with your approach.=
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></sp=
an></p>

<p class=3DMsoNormal>Regards,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

--_000_A3C5DF08D38B6049839A6F553B331C76D5BB4A3ED3ILPTMAIL02eci_--

From sriganesh.kini@ericsson.com  Mon Jul 26 09:59:31 2010
Return-Path: <sriganesh.kini@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D9F03A6A46 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 09:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nGbZRSdiBosE for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 09:59:30 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id BC4C93A67B6 for <mpls@ietf.org>; Mon, 26 Jul 2010 09:59:30 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o6QH8od4023623 for <mpls@ietf.org>; Mon, 26 Jul 2010 12:08:50 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Mon, 26 Jul 2010 12:59:51 -0400
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Date: Mon, 26 Jul 2010 12:59:49 -0400
Thread-Topic: Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
Thread-Index: Acss4/Ve0Jmier73QtOOGvuizH6grQ==
Message-ID: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80A69@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5A5E55DF96F73844AF7DFB0F48721F0F567DB80A69EUSAACMS0703e_"
MIME-Version: 1.0
Subject: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 16:59:31 -0000

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

FYI - These updated version of these drafts were presented today at IETF78.

http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-backup-01
http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01

Thanks

- Sri



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18470" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D400034416-26072010><FONT face=3DArial size=3D2>FYI - The=
se updated=20
version of these drafts were presented today at IETF78.</FONT></SPAN></DIV>
<DIV><SPAN class=3D400034416-26072010><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><A=20
href=3D"http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-backup=
-01">http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-backup-01=
</A></DIV>
<DIV><A=20
href=3D"http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01">http:=
//tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01</A></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D400034416-26072010><FONT face=3DArial=20
size=3D2>Thanks</FONT></SPAN></DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>- Sri</FONT></SPAN> </P>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

--_000_5A5E55DF96F73844AF7DFB0F48721F0F567DB80A69EUSAACMS0703e_--

From julien.meuric@orange-ftgroup.com  Mon Jul 26 10:41:32 2010
Return-Path: <julien.meuric@orange-ftgroup.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FBB93A68DB for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 10:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.568
X-Spam-Level: 
X-Spam-Status: No, score=-1.568 tagged_above=-999 required=5 tests=[AWL=0.681,  BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 PKP9-WiKdlWk for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 10:41:31 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 9554C3A696D for <mpls@ietf.org>; Mon, 26 Jul 2010 10:40:30 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id ABFFDFC4008; Mon, 26 Jul 2010 19:40:06 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id A228DFC4003; Mon, 26 Jul 2010 19:40:06 +0200 (CEST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 26 Jul 2010 19:40:06 +0200
Received: from [10.193.116.61] ([10.193.116.61]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 26 Jul 2010 19:40:06 +0200
Message-ID: <4C4DC874.6000502@orange-ftgroup.com>
Date: Mon, 26 Jul 2010 19:40:04 +0200
From: Julien Meuric <julien.meuric@orange-ftgroup.com>
Organization: France Telecom
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11pre) Gecko/20100626 Lightning/1.0b1 Shredder/3.0.6pre
MIME-Version: 1.0
To: "sriganesh.kini@ericsson.com" <sriganesh.kini@ericsson.com>
References: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80A69@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80A69@EUSAACMS0703.eamcs.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 26 Jul 2010 17:40:06.0092 (UTC) FILETIME=[95B5E8C0:01CB2CE9]
Cc: mpls@ietf.org
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 17:41:32 -0000

Hi Sriganesh.

The mechanism described in draft-kini-mpls-ring-frr-facility-backup 
reminds me of end to end recovery (or more specifically end to end 
protection), as enabled by RFC 4872. That is all the more similar 
because the association mechanism is already defined in there, with a 
dedicated RSVP-TE object. RFC 4872 is Standard Track: is there any 
rational for not considering it?

Regards,

Julien


Le 26/07/2010 18:59, Sriganesh Kini a écrit :
> FYI - These updated version of these drafts were presented today at 
> IETF78.
> http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-backup-01
> http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01
> Thanks
>
> - Sri
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>    

From sriganesh.kini@ericsson.com  Mon Jul 26 11:01:18 2010
Return-Path: <sriganesh.kini@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 774343A6BC6 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 11:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HTML_MESSAGE=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 pYwDfkNtX78t for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 11:01:17 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id A77D43A69FF for <mpls@ietf.org>; Mon, 26 Jul 2010 11:01:16 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6QI1W6A015140 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 26 Jul 2010 13:01:35 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Mon, 26 Jul 2010 14:01:30 -0400
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Date: Mon, 26 Jul 2010 14:01:28 -0400
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaA
Message-ID: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80AFB@EUSAACMS0703.eamcs.ericsson.se>
References: <A3C5DF08D38B6049839A6F553B331C76D5BB4A3ED3@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D5BB4A3ED3@ILPTMAIL02.ecitele.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5A5E55DF96F73844AF7DFB0F48721F0F567DB80AFBEUSAACMS0703e_"
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 18:01:18 -0000

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

Sasha,

As you noted the e-backup tunnel protects all LSPs that have a common {head=
-end, tail-end} pair. More precisely, the e-backup can be shared to protect=
 all LSPs that have a common {ring-ingress-LSR, ring-egress-LSR} pair (that=
 is path is disjoint with the e-backup).

If I understood correctly your concern is about the number of number of e-b=
ackup tunnels?

E-backup tunnels should be setup based on protected LSP's {ring-ingress, ri=
ng-egress} LSRs. Consider a typical case where in a ring, there is a 'ring-=
head-end' and LSPs are setup from other LSRs on the ring to the 'ring-head-=
end'. An e-backup should be setup from each LSR on the ring to the 'ring-he=
ad-end'. This is order(n).

Even for cases where protected LSPs have many possible combinations for {ri=
ng-ingress, ring-egress}, for typical ring sizes, the number of tunnels req=
uired should not be a concern for today's implementations.

Also, in many topologies an LSR that is purely a transit for protected LSPs=
, does not have to originate any e-backup.

Thanks

- Sri

PS: Regular facility FRR requires more that two backup tunnels, depending o=
n what is being protected.

________________________________
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Ale=
xander Vainshtein
Sent: Monday, July 26, 2010 9:57 AM
To: Sriganesh Kini
Cc: mpls@ietf.org
Subject: [mpls] Scalability of the "effective FRR" approach in draft-kini-m=
pls-ring-frr-facility-backup-00.txt

Sriganesh and all,
If I understood you correctly, your proposal requires a dedicated backup tu=
nnel for all LSPs with the given {head-end, tail-end} pair of LSRs in the r=
ing. (Regular facility FRR requires just two backup tunnels).
If this understanding is correct, this looks to like a serious scalability =
issue with your approach.

Regards,
     Sasha


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20
"urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20
"urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =3D=
=20
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =3D=20
"urn:schemas-microsoft-com:office:odc" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20
"http://www.w3.org/TR/REC-html40" xmlns:q =3D=20
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =3D=20
"http://microsoft.com/officenet/conferencing" XMLNS:D =3D "DAV:" XMLNS:Repl=
 =3D=20
"http://schemas.microsoft.com/repl/" xmlns:mt =3D=20
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =3D=20
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =3D=20
"http://www.passport.com/NameSpace.xsd" xmlns:ois =3D=20
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20
"http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20
"http://www.w3.org/2001/XMLSchema" xmlns:sub =3D=20
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =3D=
=20
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =3D=20
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =3D=20
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =3D=20
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =3D=20
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =3D=20
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =3D=20
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =3D=20
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =3D=20
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =3D=20
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mv=
er =3D=20
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
=3D=20
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =3D=20
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =3D=
=20
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
=3D=20
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =3D=
=20
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksServ=
ice"=20
XMLNS:Z =3D "urn:schemas-microsoft-com:" xmlns:st =3D "=01"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18470" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Calibri;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt 72.0pt 90.=
0pt; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: "=
Calibri","sans-serif"; mso-style-type: personal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D875270117-26072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Sasha,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D875270117-26072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D875270117-26072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>As you noted the&nbsp;e-backup tunnel protects all=
 LSPs=20
that have a common {head-end, tail-end} pair. More precisely, the e-backup =
can=20
be shared to protect&nbsp;all LSPs that have a common {ring-ingress-LSR,=20
ring-egress-LSR} pair&nbsp;(that is path&nbsp;is disjoint with the=20
e-backup).</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D875270117-26=
072010>If I=20
understood correctly your concern is about the number of number of e-backup=
=20
tunnels?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D875270117-26072010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D875270117-26=
072010><SPAN=20
class=3D875270117-26072010>E-backup tunnels should be setup based on protec=
ted=20
LSP's {ring-ingress, ring-egress} LSRs. </SPAN>Consider a typical case wher=
e in=20
a ring, there is a 'ring-head-end' and LSPs are setup from other LSRs on th=
e=20
ring to the 'ring-head-end'. An e-backup should be setup from each LSR on t=
he=20
ring to the 'ring-head-end'. This is order(n). </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D875270117-26072010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D875270117-26072010>Even&nbsp;for cases where protected=20
LSPs&nbsp;have&nbsp;many possible combinations&nbsp;for {ring-ingress,=20
ring-egress},&nbsp;for typical ring sizes, the number of&nbsp;tunnels=20
required&nbsp;should not be a concern=20
for&nbsp;today's&nbsp;implementations.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D875270117-26072010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D875270117-26=
072010>Also,=20
in many topologies&nbsp;an LSR that is purely a transit for protected=20
LSPs,&nbsp;does not have to originate any e-backup.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D875270117-26072010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D875270117-26072010>Thanks</SPAN></FONT></DIV><!-- Converted from te=
xt/rtf format -->
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>- Sri</FONT></SPAN> </P>
<DIV><SPAN class=3D875270117-26072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>PS:=20
Regular facility FRR requires more that two backup tunnels, depending on wh=
at is=20
being protected.</FONT></SPAN></DIV><FONT face=3DArial size=3D2></FONT><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> mpls-bounces@ietf.org=20
  [mailto:mpls-bounces@ietf.org] <B>On Behalf Of </B>Alexander=20
  Vainshtein<BR><B>Sent:</B> Monday, July 26, 2010 9:57 AM<BR><B>To:</B>=20
  Sriganesh Kini<BR><B>Cc:</B> mpls@ietf.org<BR><B>Subject:</B> [mpls]=20
  Scalability of the "effective FRR" approach in=20
  draft-kini-mpls-ring-frr-facility-backup-00.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DWordSection1>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 12pt">Sriganesh and=20
  all,<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 12pt">If I understood you=
=20
  correctly, your proposal requires a dedicated backup tunnel for all LSPs =
with=20
  the given {head-end, tail-end} pair of LSRs in the ring. (Regular facilit=
y FRR=20
  requires just two backup tunnels).<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 12pt">If this understandin=
g is=20
  correct, this looks to like a serious scalability issue with your=20
  approach.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></S=
PAN></P>
  <P class=3DMsoNormal>Regards,<o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

--_000_5A5E55DF96F73844AF7DFB0F48721F0F567DB80AFBEUSAACMS0703e_--

From autumn.liu@ericsson.com  Mon Jul 26 11:30:00 2010
Return-Path: <autumn.liu@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 618663A6841 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 11:30:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0cs3z0r554Q for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 11:29:58 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 782623A6881 for <mpls@ietf.org>; Mon, 26 Jul 2010 11:29:58 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6QIUI9e019506 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 26 Jul 2010 13:30:19 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Mon, 26 Jul 2010 14:30:18 -0400
From: Autumn Liu <autumn.liu@ericsson.com>
To: Julien Meuric <julien.meuric@orange-ftgroup.com>, Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Mon, 26 Jul 2010 14:30:17 -0400
Thread-Topic: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
Thread-Index: Acss6jnXN0/q+K7fRAS3+JrsJ29n5QABUD3A
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51AE518F86@EUSAACMS0703.eamcs.ericsson.se>
References: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80A69@EUSAACMS0703.eamcs.ericsson.se> <4C4DC874.6000502@orange-ftgroup.com>
In-Reply-To: <4C4DC874.6000502@orange-ftgroup.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 18:30:00 -0000

Hi Julien,

draft-kini-mpls-ring-frr-facility-backup describes a mechanism to let the p=
rimary LSP be aware of what the bypass LSP for corresponding protected faci=
lity. If my understanding is correct, the association mechanism defined in =
4872 is used to associate the primary and backup LSPs. This is not good eno=
ugh for the problem the draft is trying to address since each link/node alo=
ng the primary LSP may have different bypass LSPs.

Regards,
Autumn


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Jul=
ien Meuric
Sent: Monday, July 26, 2010 10:40 AM
To: Sriganesh Kini
Cc: mpls@ietf.org
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-back=
up, draft-kini-mpls-fast-lsp-alert

Hi Sriganesh.

The mechanism described in draft-kini-mpls-ring-frr-facility-backup
reminds me of end to end recovery (or more specifically end to end protecti=
on), as enabled by RFC 4872. That is all the more similar because the assoc=
iation mechanism is already defined in there, with a dedicated RSVP-TE obje=
ct. RFC 4872 is Standard Track: is there any rational for not considering i=
t?

Regards,

Julien


Le 26/07/2010 18:59, Sriganesh Kini a =E9crit :
> FYI - These updated version of these drafts were presented today at=20
> IETF78.
> http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-backup-01
> http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01
> Thanks
>
> - Sri
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>   =20
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From gregimirsky@gmail.com  Mon Jul 26 12:02:48 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B20653A6881 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 12:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.167
X-Spam-Level: 
X-Spam-Status: No, score=-2.167 tagged_above=-999 required=5 tests=[AWL=0.431,  BAYES_00=-2.599, HTML_MESSAGE=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 GS1ws6wbcAaR for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 12:02:47 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id B90533A68CB for <mpls@ietf.org>; Mon, 26 Jul 2010 12:02:46 -0700 (PDT)
Received: by vws10 with SMTP id 10so2923477vws.31 for <mpls@ietf.org>; Mon, 26 Jul 2010 12:03:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=DM1WTt0b7KhyDMUUnigIhP0z/I2oz7OxPbh7sCX1m0o=; b=d8hxfBKdinFRbqQouQ/4HMXG6xG3MqzuaxD03UgPvcWfle0QVuwWjsifOVhfBEsIVW ExUdI0UmzVj9yRTAza+iXZrY7UzjrI3ioiMbl/d1QFfNCMB446IvQsVd+s3fZND9CY2h yPqFnlv0RSpXQOtXt9u0bojhQoXUlwPki+e3Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=SRw/8KipuNOdPbUHalsQsVFjOSk40uzE6xCiOB+/JFtPqIg/FUQ42fPV9HW0jjb3vC GqzXB6luc9AAxAKsNW9DT4Enu1CgU6Q9eJvuq8G6BBqa3oOzRIdPKO+/oUF0nObzo9bJ Y4n5GgHgrRgHmnz12Vb8Qz+0o6zgkJL7pO3mk=
MIME-Version: 1.0
Received: by 10.220.88.152 with SMTP id a24mr4353623vcm.269.1280170987572;  Mon, 26 Jul 2010 12:03:07 -0700 (PDT)
Received: by 10.220.86.72 with HTTP; Mon, 26 Jul 2010 12:03:07 -0700 (PDT)
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51AE518F86@EUSAACMS0703.eamcs.ericsson.se>
References: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80A69@EUSAACMS0703.eamcs.ericsson.se> <4C4DC874.6000502@orange-ftgroup.com> <60C093A41B5E45409A19D42CF7786DFD51AE518F86@EUSAACMS0703.eamcs.ericsson.se>
Date: Mon, 26 Jul 2010 12:03:07 -0700
Message-ID: <AANLkTin+JgCSWxV-oY6_1dH5zeqLSM1Lr65LJUkDjX3s@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Autumn Liu <autumn.liu@ericsson.com>
Content-Type: multipart/alternative; boundary=00163628528cf74d96048c4f0875
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 19:02:48 -0000

--00163628528cf74d96048c4f0875
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Autumn,
I'm quite surprised to read your reply to Julien. My understanding of your
proposal is that all PLRs share the same u-PLR for given ring segment of
LSP. Please correct me if my understanding is different from authors
intention.
I'd like to add to Julien's comment that RFC 4873 seems relevant to your
solution as well as RFC 4872. And I'd ask the same question as Julien in
regard to not referencing RFC 4873.

Regards,
Greg

On Mon, Jul 26, 2010 at 11:30 AM, Autumn Liu <autumn.liu@ericsson.com>wrote=
:

> Hi Julien,
>
> draft-kini-mpls-ring-frr-facility-backup describes a mechanism to let the
> primary LSP be aware of what the bypass LSP for corresponding protected
> facility. If my understanding is correct, the association mechanism defin=
ed
> in 4872 is used to associate the primary and backup LSPs. This is not goo=
d
> enough for the problem the draft is trying to address since each link/nod=
e
> along the primary LSP may have different bypass LSPs.
>
> Regards,
> Autumn
>
>
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Julien Meuric
> Sent: Monday, July 26, 2010 10:40 AM
> To: Sriganesh Kini
> Cc: mpls@ietf.org
> Subject: Re: [mpls] Updated drafts -
> draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
>
> Hi Sriganesh.
>
> The mechanism described in draft-kini-mpls-ring-frr-facility-backup
> reminds me of end to end recovery (or more specifically end to end
> protection), as enabled by RFC 4872. That is all the more similar because
> the association mechanism is already defined in there, with a dedicated
> RSVP-TE object. RFC 4872 is Standard Track: is there any rational for not
> considering it?
>
> Regards,
>
> Julien
>
>
> Le 26/07/2010 18:59, Sriganesh Kini a =E9crit :
> > FYI - These updated version of these drafts were presented today at
> > IETF78.
> > http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-backup-01
> > http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01
> > Thanks
> >
> > - Sri
> >
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> >
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

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

Dear Autumn,<br>I&#39;m quite surprised to read your reply to Julien. My un=
derstanding of your proposal is that all PLRs share the same u-PLR for give=
n ring segment of LSP. Please correct me if my understanding is different f=
rom authors intention.<br>
I&#39;d like to add to Julien&#39;s comment that RFC 4873 seems relevant to=
 your solution as well as RFC 4872. And I&#39;d ask the same question as Ju=
lien in regard to not referencing RFC 4873.<br><br>Regards,<br>Greg<br>
<br><div class=3D"gmail_quote">On Mon, Jul 26, 2010 at 11:30 AM, Autumn Liu=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:autumn.liu@ericsson.com">autumn.li=
u@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204=
); padding-left: 1ex;">
Hi Julien,<br>
<br>
draft-kini-mpls-ring-frr-facility-backup describes a mechanism to let the p=
rimary LSP be aware of what the bypass LSP for corresponding protected faci=
lity. If my understanding is correct, the association mechanism defined in =
4872 is used to associate the primary and backup LSPs. This is not good eno=
ugh for the problem the draft is trying to address since each link/node alo=
ng the primary LSP may have different bypass LSPs.<br>

<br>
Regards,<br>
<font color=3D"#888888">Autumn<br>
</font><div><div></div><div class=3D"h5"><br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a>] O=
n Behalf Of Julien Meuric<br>
Sent: Monday, July 26, 2010 10:40 AM<br>
To: Sriganesh Kini<br>
Cc: <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-back=
up, draft-kini-mpls-fast-lsp-alert<br>
<br>
Hi Sriganesh.<br>
<br>
The mechanism described in draft-kini-mpls-ring-frr-facility-backup<br>
reminds me of end to end recovery (or more specifically end to end protecti=
on), as enabled by RFC 4872. That is all the more similar because the assoc=
iation mechanism is already defined in there, with a dedicated RSVP-TE obje=
ct. RFC 4872 is Standard Track: is there any rational for not considering i=
t?<br>

<br>
Regards,<br>
<br>
Julien<br>
<br>
<br>
Le 26/07/2010 18:59, Sriganesh Kini a =E9crit :<br>
&gt; FYI - These updated version of these drafts were presented today at<br=
>
&gt; IETF78.<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facilit=
y-backup-01" target=3D"_blank">http://tools.ietf.org/html/draft-kini-mpls-r=
ing-frr-facility-backup-01</a><br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-0=
1" target=3D"_blank">http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-al=
ert-01</a><br>
&gt; Thanks<br>
&gt;<br>
&gt; - Sri<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; mpls mailing list<br>
&gt; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/mpls</a><br>
&gt;<br>
_______________________________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>
_______________________________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>
</div></div></blockquote></div><br>

--00163628528cf74d96048c4f0875--

From autumn.liu@ericsson.com  Mon Jul 26 12:16:32 2010
Return-Path: <autumn.liu@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C0653A680E for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 12:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=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 bVRaSHsSElfJ for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 12:16:31 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 33AEA3A6841 for <mpls@ietf.org>; Mon, 26 Jul 2010 12:16:30 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6QJGoTa026673 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 26 Jul 2010 14:16:51 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Mon, 26 Jul 2010 15:16:49 -0400
From: Autumn Liu <autumn.liu@ericsson.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 26 Jul 2010 15:16:47 -0400
Thread-Topic: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
Thread-Index: Acss9TXD1BUT6GTOR/6YIWAuIEZjaAAAMY4g
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51AE519013@EUSAACMS0703.eamcs.ericsson.se>
References: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80A69@EUSAACMS0703.eamcs.ericsson.se> <4C4DC874.6000502@orange-ftgroup.com> <60C093A41B5E45409A19D42CF7786DFD51AE518F86@EUSAACMS0703.eamcs.ericsson.se> <AANLkTin+JgCSWxV-oY6_1dH5zeqLSM1Lr65LJUkDjX3s@mail.gmail.com>
In-Reply-To: <AANLkTin+JgCSWxV-oY6_1dH5zeqLSM1Lr65LJUkDjX3s@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_60C093A41B5E45409A19D42CF7786DFD51AE519013EUSAACMS0703e_"
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 19:16:32 -0000

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

Hi Greg,

 +-------L1--------L2---------L3--------L4-------+
  |                                                      |
 L10                                                  L5
  |                                                      |
 +-------L9--------L8---------L7--------L6-------+

Not all PLRs. Using the diagram in draft as an example.
Bypass 1 (to protect link between L8 and L7) : L8-L9-L10-L1-L2-L3-L4-L5-L6-=
L7
Bypass 2 (to protect node failure on L8) : L9-L10-L1-L2-L3-L4-L5-L6-L7

e-backup tunnel L10-L1-L2-L3-L4-L5 can be used instead for both cases witho=
ut getting traffic u-turned.

Regards,
Autumn



________________________________
From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: Monday, July 26, 2010 12:03 PM
To: Autumn Liu
Cc: Julien Meuric; Sriganesh Kini; mpls@ietf.org
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-back=
up, draft-kini-mpls-fast-lsp-alert

Dear Autumn,
I'm quite surprised to read your reply to Julien. My understanding of your =
proposal is that all PLRs share the same u-PLR for given ring segment of LS=
P. Please correct me if my understanding is different from authors intentio=
n.
I'd like to add to Julien's comment that RFC 4873 seems relevant to your so=
lution as well as RFC 4872. And I'd ask the same question as Julien in rega=
rd to not referencing RFC 4873.

Regards,
Greg

On Mon, Jul 26, 2010 at 11:30 AM, Autumn Liu <autumn.liu@ericsson.com<mailt=
o:autumn.liu@ericsson.com>> wrote:
Hi Julien,

draft-kini-mpls-ring-frr-facility-backup describes a mechanism to let the p=
rimary LSP be aware of what the bypass LSP for corresponding protected faci=
lity. If my understanding is correct, the association mechanism defined in =
4872 is used to associate the primary and backup LSPs. This is not good eno=
ugh for the problem the draft is trying to address since each link/node alo=
ng the primary LSP may have different bypass LSPs.

Regards,
Autumn


-----Original Message-----
From: mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org> [mailto:mpls-boun=
ces@ietf.org<mailto:mpls-bounces@ietf.org>] On Behalf Of Julien Meuric
Sent: Monday, July 26, 2010 10:40 AM
To: Sriganesh Kini
Cc: mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-back=
up, draft-kini-mpls-fast-lsp-alert

Hi Sriganesh.

The mechanism described in draft-kini-mpls-ring-frr-facility-backup
reminds me of end to end recovery (or more specifically end to end protecti=
on), as enabled by RFC 4872. That is all the more similar because the assoc=
iation mechanism is already defined in there, with a dedicated RSVP-TE obje=
ct. RFC 4872 is Standard Track: is there any rational for not considering i=
t?

Regards,

Julien


Le 26/07/2010 18:59, Sriganesh Kini a =E9crit :
> FYI - These updated version of these drafts were presented today at
> IETF78.
> http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-backup-01
> http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01
> Thanks
>
> - Sri
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org<mailto:mpls@ietf.org>
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.6001.18444" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>Hi Greg,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D638510819-26072010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>&nbsp;+-------L1--------L2---------L3--------L4-=
------+<BR>&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;|</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>&nbsp;L10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
L5</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>&nbsp;+-------L9--------L8---------L7--------L6-=
------+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>Not all PLRs. Using the diagram in draft as an=20
example.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>Bypass 1 (to protect link between L8 and L7) :=20
L8-L9-L10-L1-L2-L3-L4-L5-L6-L7 </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>Bypass 2 (to protect node failure on L8) :=20
L9-L10-L1-L2-L3-L4-L5-L6-L7</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>e-backup tunnel L10-L1-L2-L3-L4-L5&nbsp;can=20
be&nbsp;used instead for both cases without getting=20
traffic&nbsp;u-turned.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>Regards,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010>Autumn</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D638510819-26072010><BR>&nbsp;</DIV></SPAN></FONT><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Greg Mirsky [mailto:gregimirsky@g=
mail.com]=20
<BR><B>Sent:</B> Monday, July 26, 2010 12:03 PM<BR><B>To:</B> Autumn=20
Liu<BR><B>Cc:</B> Julien Meuric; Sriganesh Kini;=20
mpls@ietf.org<BR><B>Subject:</B> Re: [mpls] Updated drafts -=20
draft-kini-mpls-ring-frr-facility-backup,=20
draft-kini-mpls-fast-lsp-alert<BR></FONT><BR></DIV>
<DIV></DIV>Dear Autumn,<BR>I'm quite surprised to read your reply to Julien=
. My=20
understanding of your proposal is that all PLRs share the same u-PLR for gi=
ven=20
ring segment of LSP. Please correct me if my understanding is different fro=
m=20
authors intention.<BR>I'd like to add to Julien's comment that RFC 4873 see=
ms=20
relevant to your solution as well as RFC 4872. And I'd ask the same questio=
n as=20
Julien in regard to not referencing RFC 4873.<BR><BR>Regards,<BR>Greg<BR><B=
R>
<DIV class=3Dgmail_quote>On Mon, Jul 26, 2010 at 11:30 AM, Autumn Liu <SPAN=
=20
dir=3Dltr>&lt;<A=20
href=3D"mailto:autumn.liu@ericsson.com">autumn.liu@ericsson.com</A>&gt;</SP=
AN>=20
wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204=
,204,204) 1px solid">Hi=20
  Julien,<BR><BR>draft-kini-mpls-ring-frr-facility-backup describes a mecha=
nism=20
  to let the primary LSP be aware of what the bypass LSP for corresponding=
=20
  protected facility. If my understanding is correct, the association mecha=
nism=20
  defined in 4872 is used to associate the primary and backup LSPs. This is=
 not=20
  good enough for the problem the draft is trying to address since each=20
  link/node along the primary LSP may have different bypass=20
  LSPs.<BR><BR>Regards,<BR><FONT color=3D#888888>Autumn<BR></FONT>
  <DIV>
  <DIV></DIV>
  <DIV class=3Dh5><BR><BR>-----Original Message-----<BR>From: <A=20
  href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</A> [mailto:<=
A=20
  href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</A>] On Behal=
f Of=20
  Julien Meuric<BR>Sent: Monday, July 26, 2010 10:40 AM<BR>To: Sriganesh=20
  Kini<BR>Cc: <A href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A><BR>Subject=
: Re:=20
  [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup,=20
  draft-kini-mpls-fast-lsp-alert<BR><BR>Hi Sriganesh.<BR><BR>The mechanism=
=20
  described in draft-kini-mpls-ring-frr-facility-backup<BR>reminds me of en=
d to=20
  end recovery (or more specifically end to end protection), as enabled by =
RFC=20
  4872. That is all the more similar because the association mechanism is=20
  already defined in there, with a dedicated RSVP-TE object. RFC 4872 is=20
  Standard Track: is there any rational for not considering=20
  it?<BR><BR>Regards,<BR><BR>Julien<BR><BR><BR>Le 26/07/2010 18:59, Srigane=
sh=20
  Kini a =E9crit :<BR>&gt; FYI - These updated version of these drafts were=
=20
  presented today at<BR>&gt; IETF78.<BR>&gt; <A=20
  href=3D"http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-back=
up-01"=20
  target=3D_blank>http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facil=
ity-backup-01</A><BR>&gt;=20
  <A href=3D"http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01"=
=20
  target=3D_blank>http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert=
-01</A><BR>&gt;=20
  Thanks<BR>&gt;<BR>&gt; - Sri<BR>&gt;<BR>&gt;<BR>&gt;=20
  _______________________________________________<BR>&gt; mpls mailing=20
  list<BR>&gt; <A href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A><BR>&gt; <=
A=20
  href=3D"https://www.ietf.org/mailman/listinfo/mpls"=20
  target=3D_blank>https://www.ietf.org/mailman/listinfo/mpls</A><BR>&gt;<BR=
>_______________________________________________<BR>mpls=20
  mailing list<BR><A href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A><BR><A=
=20
  href=3D"https://www.ietf.org/mailman/listinfo/mpls"=20
  target=3D_blank>https://www.ietf.org/mailman/listinfo/mpls</A><BR>_______=
________________________________________<BR>mpls=20
  mailing list<BR><A href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A><BR><A=
=20
  href=3D"https://www.ietf.org/mailman/listinfo/mpls"=20
  target=3D_blank>https://www.ietf.org/mailman/listinfo/mpls</A><BR></DIV><=
/DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>

--_000_60C093A41B5E45409A19D42CF7786DFD51AE519013EUSAACMS0703e_--

From snortbsd@gmail.com  Mon Jul 26 13:07:37 2010
Return-Path: <snortbsd@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4F203A68C6 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 13:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=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 prXCDOhKeJMG for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 13:07:33 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 696463A6957 for <mpls@ietf.org>; Mon, 26 Jul 2010 13:07:20 -0700 (PDT)
Received: by ewy22 with SMTP id 22so1130626ewy.31 for <mpls@ietf.org>; Mon, 26 Jul 2010 13:07:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=yE1uze71s4EsVEMxXVNb0F+TizpxNZmzhv9Ml6ykg38=; b=KeP4bsJWhxUKxSXQtgdBXkZq58stpO+bpi9nq0+ZH5GaBwIYMdmEhUD3mn/kG0Dx+l PXqRQeoqvMXFyk4gu/z7CCXODMhsA7MOX2vwC2qpkJH2P0QDT5tYDHqkCBpnQy3QXaur HHE+WkWmqkJ17diJKLTkKwURbOoekeI3VBipQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=OyNoMhxmxElx/da/tA6m7ad8e1IgTLRzrKAiqKkqmLLet7su5pzmNT6fH9OmAfcsrk aiDlJ1quriqdgq+UDXYU7gB1uo0w7qNmSrsDjZWzHlhWW4j9hJ/PaRfEZdndDh1l9+g8 wUwGzwKVCoX4untBqxwPe44lfIdI9PQI50Z+o=
MIME-Version: 1.0
Received: by 10.213.25.145 with SMTP id z17mr3993674ebb.84.1280174861136; Mon,  26 Jul 2010 13:07:41 -0700 (PDT)
Received: by 10.14.37.67 with HTTP; Mon, 26 Jul 2010 13:07:40 -0700 (PDT)
Date: Mon, 26 Jul 2010 16:07:40 -0400
Message-ID: <AANLkTinUx5ciuC0z+Eb8jB6nZMmN2U7RFQzftb_Gnp59@mail.gmail.com>
From: rufino <snortbsd@gmail.com>
To: mpls@ietf.org
Content-Type: multipart/alternative; boundary=0015174c445cd93421048c4fef2e
Subject: [mpls] RFC4875 and Juniper implementation
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 20:07:37 -0000

--0015174c445cd93421048c4fef2e
Content-Type: text/plain; charset=ISO-8859-1

Hi All:

I am learning p2mp, using Juniper implementation so that I can have better
understanding of this RFC. But comparing to the juniper implementations, I
have some questions:

on RFC4875 page 10:

This section describes modifications made to the Path message format
as specified in [RFC3209] and [RFC3473]. The Path message is
enhanced to signal one or more S2L sub-LSPs.* This is done by
including the S2L sub-LSP descriptor list in the Path message* as
shown below.

<Path Message> ::= <Common Header> [ <INTEGRITY> ]
                               [ [<MESSAGE_ID_ACK> | <MESSAGE_ID_NACK>] ...]
                               [ <MESSAGE_ID> ]
                               <SESSION> <RSVP_HOP>
                               <TIME_VALUES>
                               [ <EXPLICIT_ROUTE> ]
                               <LABEL_REQUEST>
                               [ <PROTECTION> ]
                               [ <LABEL_SET> ... ]
                               [ <SESSION_ATTRIBUTE> ]
                               [ <NOTIFY_REQUEST> ]
                               [ <ADMIN_STATUS> ]
                               [ <POLICY_DATA> ... ]
                               <sender descriptor>
                               [<S2L sub-LSP descriptor list>]

The following is the format of the S2L sub-LSP descriptor list.

<S2L sub-LSP descriptor list> ::= <S2L sub-LSP descriptor>
                                                [ <S2L sub-LSP descriptor
list> ]

<S2L sub-LSP descriptor> ::= <S2L_SUB_LSP>
                                          [ <P2MP SECONDARY_EXPLICIT_ROUTE>
]

I set up three PE routers, PE1 (10.100.3.1), PE2 (10.100.3.2) and PE3
(10.100.3.7) and with few P routers

here are what i got from juniper boxes:

on a PE1 router:

Jul 26 15:56:52.175328 *RSVP send Path 10.100.3.1->10.100.3.2 Len=248
fe-0/0/0.10*
Jul 26 15:56:52.175490   MessageID Len 12 Msg_ID: 34 Epoch: 7781352 (Ack
Desired)
Jul 26 15:56:52.175555   *Session13 Len 16 10.100.3.1(port/tunnel ID 6155
Ext-ID 10.100.3.1) Proto 0*
Jul 26 15:56:52.175639   Hop      Len 12 10.100.0.1/0x08dd4490
Jul 26 15:56:52.175690   Time     Len  8 30000 ms
Jul 26 15:56:52.175755   SrcRoute Len 20  10.100.0.2 S 10.100.0.30 S
Jul 26 15:56:52.175807   LabelRequest Len  8 EtherType 0x800
Jul 26 15:56:52.175864   *Properties Len 24 Primary path p2mp->r2 p2mp-pvc
name*
Jul 26 15:56:52.175920   SessionAttribute Len 16 Prio (7,0) flag 0x4
"r1->r2"
Jul 26 15:56:52.175979   *Sender12 Len 20 P2MP Sender 10.100.3.1(port/lsp
ID  1, branch ID 10)    SubGrpOrg ID 0xa640301*
Jul 26 15:56:52.176033   *SubLsp   Len  8 Destination 10.100.3.2*
Jul 26 15:56:52.176116   Tspec    Len 36 rate 0bps size 0bps peak Infbps m
20 M 1500
Jul 26 15:56:52.176170   ADspec   Len 48 MTU 1500
Jul 26 15:56:52.176226   RecRoute Len 12  10.100.0.1

Jul 26 15:56:52.572218 *RSVP recv Resv 10.100.0.2->10.100.0.1 Len=156
fe-0/0/0.10*
Jul 26 15:56:52.572346   MessageID Len 12 Msg_ID: 53 Epoch: 7771538 (Ack
Desired)
Jul 26 15:56:52.572404   *Session13 Len 16 10.100.3.1(port/tunnel ID 6155
Ext-ID 10.100.3.1) Proto 0*
Jul 26 15:56:52.572462   Hop      Len 12 10.100.0.2/0x08dd4490
Jul 26 15:56:52.572526   Time     Len  8 30000 ms
Jul 26 15:56:52.572577   Style    Len  8 SE
Jul 26 15:56:52.572656   Flow     Len 36 rate 0bps size 0bps peak Infbps m
20 M 1500
Jul 26 15:56:52.572717   *Filter12 Len 20 P2MP Sender 10.100.3.1(port/lsp
ID  1, branch ID 10)    SubGrpOrg ID 0xa640301*
Jul 26 15:56:52.572768   Label    Len  8  300016
Jul 26 15:56:52.572830   RecRoute Len 20  10.100.0.2 10.100.0.30
Jul 26 15:56:52.572882   *SubLsp   Len  8 Destination 10.100.3.2*

Jul 26 15:56:54.621105 *RSVP send Path 10.100.3.1->10.100.3.7 Len=256
fe-0/0/0.10*
Jul 26 15:56:54.621279   MessageID Len 12 Msg_ID: 35 Epoch: 7781352 (Ack
Desired)
Jul 26 15:56:54.621345   *Session13 Len 16 10.100.3.1(port/tunnel ID 6156
Ext-ID 10.100.3.1) Proto 0*
Jul 26 15:56:54.621406   Hop      Len 12 10.100.0.1/0x08dd4490
Jul 26 15:56:54.621457   Time     Len  8 30000 ms
Jul 26 15:56:54.621526   SrcRoute Len 28  10.100.0.2 S 10.100.0.26 S
10.100.0.50 S
Jul 26 15:56:54.621579   LabelRequest Len  8 EtherType 0x800
Jul 26 15:56:54.621636   *Properties Len 24 Primary path p2mp->r7 p2mp-pvc
name*
Jul 26 15:56:54.621847   SessionAttribute Len 16 Prio (7,0) flag 0x4
"r1->r7"
Jul 26 15:56:54.621929   *Sender12 Len 20 P2MP Sender 10.100.3.1(port/lsp
ID  1, branch ID 10)    SubGrpOrg ID 0xa640301*
Jul 26 15:56:54.621986   *SubLsp   Len  8 Destination 10.100.3.7*
Jul 26 15:56:54.622071   Tspec    Len 36 rate 0bps size 0bps peak Infbps m
20 M 1500
Jul 26 15:56:54.622128   ADspec   Len 48 MTU 1500
Jul 26 15:56:54.622203   RecRoute Len 12  10.100.0.1

Jul 26 15:56:55.221811 *RSVP recv Resv 10.100.0.2->10.100.0.1 Len=164
fe-0/0/0.10*
Jul 26 15:56:55.221989   MessageID Len 12 Msg_ID: 55 Epoch: 7771538 (Ack
Desired)
Jul 26 15:56:55.222052   *Session13 Len 16 10.100.3.1(port/tunnel ID 6156
Ext-ID 10.100.3.1) Proto 0*
Jul 26 15:56:55.222129   Hop      Len 12 10.100.0.2/0x08dd4490
Jul 26 15:56:55.222182   Time     Len  8 30000 ms
Jul 26 15:56:55.222233   Style    Len  8 SE
Jul 26 15:56:55.222314   Flow     Len 36 rate 0bps size 0bps peak Infbps m
20 M 1500
Jul 26 15:56:55.222377   *Filter12 Len 20 P2MP Sender 10.100.3.1(port/lsp
ID  1, branch ID 10)    SubGrpOrg ID 0xa640301*
Jul 26 15:56:55.222430   Label    Len  8  300032
Jul 26 15:56:55.222498   RecRoute Len 28  10.100.0.2 10.100.0.26 10.100.0.50
Jul 26 15:56:55.222553   *SubLsp   Len  8 Destination 10.100.3.7*

where is the [<S2L sub-LSP descriptor list>]? this "*SubLsp   Len  8
Destination 10.100.3.2"?

*_Dave*
*

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

Hi All:<br><br>I am learning p2mp, using Juniper implementation so that I c=
an have better understanding of this RFC. But comparing to the juniper impl=
ementations, I have some questions:<br><br>on RFC4875 page 10:<br><br>This =
section describes modifications made to the Path message format<br>
as specified in [RFC3209] and [RFC3473]. The Path message is<br>enhanced to=
 signal one or more S2L sub-LSPs.<b> This is done by<br>including the S2L s=
ub-LSP descriptor list in the Path message</b> as<br>shown below.<br><br>
&lt;Path Message&gt; ::=3D &lt;Common Header&gt; [ &lt;INTEGRITY&gt; ]<br>=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 [ [&lt;MESSAGE_ID_ACK&gt; | &lt;MESSAGE_ID_NACK&gt;] ...]<b=
r>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 [ &lt;MESSAGE_ID&gt; ]<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 &lt;SESSION&gt; &lt;RSVP_HOP&gt;<br>=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 &lt;T=
IME_VALUES&gt;<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ &lt;EXPLICIT_ROUTE&gt; ]<br>=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 &lt;LABEL_REQUEST&gt;<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 [ &lt;PROTECTION&gt; ]<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ &lt;LABEL_SET&g=
t; ... ]<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ &lt;SESSION_ATTRIBUTE&gt; ]<br>=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 [ &lt;NOTIFY_REQUEST&gt; ]<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 [ &lt;ADMIN_STATUS&gt; ]<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ &lt;POLICY_D=
ATA&gt; ... ]<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 &lt;sender descriptor&gt;<br>=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 [&lt;S2L sub-LSP descriptor list&gt;]<br>
<br>The following is the format of the S2L sub-LSP descriptor list.<br><br>=
&lt;S2L sub-LSP descriptor list&gt; ::=3D &lt;S2L sub-LSP descriptor&gt;<br=
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ &lt=
;S2L sub-LSP descriptor list&gt; ]<br>
<br>&lt;S2L sub-LSP descriptor&gt; ::=3D &lt;S2L_SUB_LSP&gt;<br>=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ &lt;P2MP SECONDARY_EXPLICIT_ROUTE=
&gt; ]<br><br>I set up three PE routers, PE1 (10.100.3.1), PE2 (10.100.3.2)=
 and PE3 (10.100.3.7) and with few P routers<br>
<br>here are what i got from juniper boxes:<br><br>on a PE1 router:<br><br>=
Jul 26 15:56:52.175328 <b>RSVP send Path 10.100.3.1-&gt;10.100.3.2 Len=3D24=
8 fe-0/0/0.10</b><br>Jul 26 15:56:52.175490=A0=A0 MessageID Len 12 Msg_ID: =
34 Epoch: 7781352 (Ack Desired)<br>
Jul 26 15:56:52.175555=A0=A0 <b>Session13 Len 16 10.100.3.1(port/tunnel ID =
6155 Ext-ID 10.100.3.1) Proto 0</b><br>Jul 26 15:56:52.175639=A0=A0 Hop=A0=
=A0=A0=A0=A0 Len 12 <a href=3D"http://10.100.0.1/0x08dd4490">10.100.0.1/0x0=
8dd4490</a><br>Jul 26 15:56:52.175690=A0=A0 Time=A0=A0=A0=A0 Len=A0 8 30000=
 ms<br>
Jul 26 15:56:52.175755=A0=A0 SrcRoute Len 20=A0 10.100.0.2 S 10.100.0.30 S<=
br>Jul 26 15:56:52.175807=A0=A0 LabelRequest Len=A0 8 EtherType 0x800<br>Ju=
l 26 15:56:52.175864=A0=A0 <b>Properties Len 24 Primary path p2mp-&gt;r2 p2=
mp-pvc name</b><br>
Jul 26 15:56:52.175920=A0=A0 SessionAttribute Len 16 Prio (7,0) flag 0x4 &q=
uot;r1-&gt;r2&quot;<br>Jul 26 15:56:52.175979=A0=A0 <b>Sender12 Len 20 P2MP=
 Sender 10.100.3.1(port/lsp ID=A0 1, branch ID 10)=A0=A0=A0 SubGrpOrg ID 0x=
a640301</b><br>
Jul 26 15:56:52.176033=A0=A0 <b>SubLsp=A0=A0 Len=A0 8 Destination 10.100.3.=
2</b><br>Jul 26 15:56:52.176116=A0=A0 Tspec=A0=A0=A0 Len 36 rate 0bps size =
0bps peak Infbps m 20 M 1500<br>Jul 26 15:56:52.176170=A0=A0 ADspec=A0=A0 L=
en 48 MTU 1500<br>Jul 26 15:56:52.176226=A0=A0 RecRoute Len 12=A0 10.100.0.=
1<br>
<br>Jul 26 15:56:52.572218 <b>RSVP recv Resv 10.100.0.2-&gt;10.100.0.1 Len=
=3D156 fe-0/0/0.10</b><br>Jul 26 15:56:52.572346=A0=A0 MessageID Len 12 Msg=
_ID: 53 Epoch: 7771538 (Ack Desired)<br>Jul 26 15:56:52.572404=A0=A0 <b>Ses=
sion13 Len 16 10.100.3.1(port/tunnel ID 6155 Ext-ID 10.100.3.1) Proto 0</b>=
<br>
Jul 26 15:56:52.572462=A0=A0 Hop=A0=A0=A0=A0=A0 Len 12 <a href=3D"http://10=
.100.0.2/0x08dd4490">10.100.0.2/0x08dd4490</a><br>Jul 26 15:56:52.572526=A0=
=A0 Time=A0=A0=A0=A0 Len=A0 8 30000 ms<br>Jul 26 15:56:52.572577=A0=A0 Styl=
e=A0=A0=A0 Len=A0 8 SE<br>Jul 26 15:56:52.572656=A0=A0 Flow=A0=A0=A0=A0 Len=
 36 rate 0bps size 0bps peak Infbps m 20 M 1500<br>
Jul 26 15:56:52.572717=A0=A0 <b>Filter12 Len 20 P2MP Sender 10.100.3.1(port=
/lsp ID=A0 1, branch ID 10)=A0=A0=A0 SubGrpOrg ID 0xa640301</b><br>Jul 26 1=
5:56:52.572768=A0=A0 Label=A0=A0=A0 Len=A0 8=A0 300016<br>Jul 26 15:56:52.5=
72830=A0=A0 RecRoute Len 20=A0 10.100.0.2 10.100.0.30<br>
Jul 26 15:56:52.572882=A0=A0 <b>SubLsp=A0=A0 Len=A0 8 Destination 10.100.3.=
2</b><br><br>Jul 26 15:56:54.621105 <b>RSVP send Path 10.100.3.1-&gt;10.100=
.3.7 Len=3D256 fe-0/0/0.10</b><br>Jul 26 15:56:54.621279=A0=A0 MessageID Le=
n 12 Msg_ID: 35 Epoch: 7781352 (Ack Desired)<br>
Jul 26 15:56:54.621345=A0=A0 <b>Session13 Len 16 10.100.3.1(port/tunnel ID =
6156 Ext-ID 10.100.3.1) Proto 0</b><br>Jul 26 15:56:54.621406=A0=A0 Hop=A0=
=A0=A0=A0=A0 Len 12 <a href=3D"http://10.100.0.1/0x08dd4490">10.100.0.1/0x0=
8dd4490</a><br>Jul 26 15:56:54.621457=A0=A0 Time=A0=A0=A0=A0 Len=A0 8 30000=
 ms<br>
Jul 26 15:56:54.621526=A0=A0 SrcRoute Len 28=A0 10.100.0.2 S 10.100.0.26 S =
10.100.0.50 S<br>Jul 26 15:56:54.621579=A0=A0 LabelRequest Len=A0 8 EtherTy=
pe 0x800<br>Jul 26 15:56:54.621636=A0=A0 <b>Properties Len 24 Primary path =
p2mp-&gt;r7 p2mp-pvc name</b><br>
Jul 26 15:56:54.621847=A0=A0 SessionAttribute Len 16 Prio (7,0) flag 0x4 &q=
uot;r1-&gt;r7&quot;<br>Jul 26 15:56:54.621929=A0=A0 <b>Sender12 Len 20 P2MP=
 Sender 10.100.3.1(port/lsp ID=A0 1, branch ID 10)=A0=A0=A0 SubGrpOrg ID 0x=
a640301</b><br>
Jul 26 15:56:54.621986=A0=A0 <b>SubLsp=A0=A0 Len=A0 8 Destination 10.100.3.=
7</b><br>Jul 26 15:56:54.622071=A0=A0 Tspec=A0=A0=A0 Len 36 rate 0bps size =
0bps peak Infbps m 20 M 1500<br>Jul 26 15:56:54.622128=A0=A0 ADspec=A0=A0 L=
en 48 MTU 1500<br>Jul 26 15:56:54.622203=A0=A0 RecRoute Len 12=A0 10.100.0.=
1<br>
<br>Jul 26 15:56:55.221811 <b>RSVP recv Resv 10.100.0.2-&gt;10.100.0.1 Len=
=3D164 fe-0/0/0.10</b><br>Jul 26 15:56:55.221989=A0=A0 MessageID Len 12 Msg=
_ID: 55 Epoch: 7771538 (Ack Desired)<br>Jul 26 15:56:55.222052=A0=A0 <b>Ses=
sion13 Len 16 10.100.3.1(port/tunnel ID 6156 Ext-ID 10.100.3.1) Proto 0</b>=
<br>
Jul 26 15:56:55.222129=A0=A0 Hop=A0=A0=A0=A0=A0 Len 12 <a href=3D"http://10=
.100.0.2/0x08dd4490">10.100.0.2/0x08dd4490</a><br>Jul 26 15:56:55.222182=A0=
=A0 Time=A0=A0=A0=A0 Len=A0 8 30000 ms<br>Jul 26 15:56:55.222233=A0=A0 Styl=
e=A0=A0=A0 Len=A0 8 SE<br>Jul 26 15:56:55.222314=A0=A0 Flow=A0=A0=A0=A0 Len=
 36 rate 0bps size 0bps peak Infbps m 20 M 1500<br>
Jul 26 15:56:55.222377=A0=A0 <b>Filter12 Len 20 P2MP Sender 10.100.3.1(port=
/lsp ID=A0 1, branch ID 10)=A0=A0=A0 SubGrpOrg ID 0xa640301</b><br>Jul 26 1=
5:56:55.222430=A0=A0 Label=A0=A0=A0 Len=A0 8=A0 300032<br>Jul 26 15:56:55.2=
22498=A0=A0 RecRoute Len 28=A0 10.100.0.2 10.100.0.26 10.100.0.50<br>
Jul 26 15:56:55.222553=A0=A0 <b>SubLsp=A0=A0 Len=A0 8 Destination 10.100.3.=
7</b><br><br>where is the  [&lt;S2L sub-LSP descriptor list&gt;]? this &quo=
t;<b>SubLsp=A0=A0 Len=A0 8 Destination 10.100.3.2&quot;?<br><br></b>_Dave<b=
><br></b><br>
<br><br><br><br><br>

--0015174c445cd93421048c4fef2e--

From gregimirsky@gmail.com  Mon Jul 26 13:36:57 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 67A143A68B6 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 13:36:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 DTLYuZs9UBgV for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 13:36:56 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id EDB153A6866 for <mpls@ietf.org>; Mon, 26 Jul 2010 13:36:55 -0700 (PDT)
Received: by pvd12 with SMTP id 12so274910pvd.31 for <mpls@ietf.org>; Mon, 26 Jul 2010 13:37:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=HTII5od0lFGMPlY9ebb0InextzbNPoDqc6Dwwt9/xI8=; b=aWvqO5dxx5M+S7F0+ygjUz9lmVLD8ifkuKUVy2I6UkppEXO/YSunjSH15wKLIrv5ov F3uOS8dUHkpNjC/P/4Sum3PWu3bPwIGbE3hLUT+FFzRDapMBgDsDbllQHzthLWmu+x5s e8Lz5LD6Y4oiebbe/4pJb4oFrF3JJ0BU0SsnQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=RHEyQhT3YNl3qU2vRIBKRAUfALbZJlN7fOQvFDECGuPVYPnfgps8HT8mIgQgjH1fvf Nhxd5vve8bKhYkE/4vUMRd0gRJWEPoBKyqalO/mzctesXUXTFu9EyMAI9gcmNM8gfrji MVz+/Em551JEw1LD7Fgd2aCanoZO5glSUt8E0=
MIME-Version: 1.0
Received: by 10.114.109.15 with SMTP id h15mr12355584wac.105.1280176637317;  Mon, 26 Jul 2010 13:37:17 -0700 (PDT)
Received: by 10.220.86.72 with HTTP; Mon, 26 Jul 2010 13:37:16 -0700 (PDT)
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51AE519013@EUSAACMS0703.eamcs.ericsson.se>
References: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80A69@EUSAACMS0703.eamcs.ericsson.se> <4C4DC874.6000502@orange-ftgroup.com> <60C093A41B5E45409A19D42CF7786DFD51AE518F86@EUSAACMS0703.eamcs.ericsson.se> <AANLkTin+JgCSWxV-oY6_1dH5zeqLSM1Lr65LJUkDjX3s@mail.gmail.com> <60C093A41B5E45409A19D42CF7786DFD51AE519013@EUSAACMS0703.eamcs.ericsson.se>
Date: Mon, 26 Jul 2010 13:37:16 -0700
Message-ID: <AANLkTikQ50unSLTmg+4i5H==_z2pOHPeYqOrS3r5oygf@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Autumn Liu <autumn.liu@ericsson.com>
Content-Type: multipart/alternative; boundary=0016364588b4b79332048c50596f
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 20:36:57 -0000

--0016364588b4b79332048c50596f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Autumn,
thank you for adding specific case to our discussion. In my view protecting
segment L10-L1-L2-L3-L4-L5 (e-backup tunnel) is shared by all backup tunnel=
s
that traverse the ring through nodes L10-L9-L8-L7-L6-L5. This e-backup
tunnel is the e-backup tunnels for all working sections/segments (in case o=
f
link and node protection) of an LSP L10-...-L8-..-L5. I'd re-state my
question to authors whether they've considered re-using RSVP-TE objects and
subobjects defined in RFC 4873.  If mechanisms and objects defined in RFC
4873 not sufficient, why RFC 4873 not referenced in the draft Efficient
Facility Backup FRR.

Regards,
Greg

On Mon, Jul 26, 2010 at 12:16 PM, Autumn Liu <autumn.liu@ericsson.com>wrote=
:

>  Hi Greg,
>
>  +-------L1--------L2---------L3--------L4-------+
>   |                                                      |
>  L10                                                  L5
>   |                                                      |
>  +-------L9--------L8---------L7--------L6-------+
>
> Not all PLRs. Using the diagram in draft as an example.
> Bypass 1 (to protect link between L8 and L7) :
> L8-L9-L10-L1-L2-L3-L4-L5-L6-L7
> Bypass 2 (to protect node failure on L8) : L9-L10-L1-L2-L3-L4-L5-L6-L7
>
> e-backup tunnel L10-L1-L2-L3-L4-L5 can be used instead for both cases
> without getting traffic u-turned.
>
> Regards,
> Autumn
>
>
>
>  ------------------------------
> *From:* Greg Mirsky [mailto:gregimirsky@gmail.com]
> *Sent:* Monday, July 26, 2010 12:03 PM
> *To:* Autumn Liu
> *Cc:* Julien Meuric; Sriganesh Kini; mpls@ietf.org
>
> *Subject:* Re: [mpls] Updated drafts -
> draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
>
> Dear Autumn,
> I'm quite surprised to read your reply to Julien. My understanding of you=
r
> proposal is that all PLRs share the same u-PLR for given ring segment of
> LSP. Please correct me if my understanding is different from authors
> intention.
> I'd like to add to Julien's comment that RFC 4873 seems relevant to your
> solution as well as RFC 4872. And I'd ask the same question as Julien in
> regard to not referencing RFC 4873.
>
> Regards,
> Greg
>
> On Mon, Jul 26, 2010 at 11:30 AM, Autumn Liu <autumn.liu@ericsson.com>wro=
te:
>
>> Hi Julien,
>>
>> draft-kini-mpls-ring-frr-facility-backup describes a mechanism to let th=
e
>> primary LSP be aware of what the bypass LSP for corresponding protected
>> facility. If my understanding is correct, the association mechanism defi=
ned
>> in 4872 is used to associate the primary and backup LSPs. This is not go=
od
>> enough for the problem the draft is trying to address since each link/no=
de
>> along the primary LSP may have different bypass LSPs.
>>
>> Regards,
>> Autumn
>>
>>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
>> Julien Meuric
>> Sent: Monday, July 26, 2010 10:40 AM
>> To: Sriganesh Kini
>> Cc: mpls@ietf.org
>> Subject: Re: [mpls] Updated drafts -
>> draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
>>
>> Hi Sriganesh.
>>
>> The mechanism described in draft-kini-mpls-ring-frr-facility-backup
>> reminds me of end to end recovery (or more specifically end to end
>> protection), as enabled by RFC 4872. That is all the more similar becaus=
e
>> the association mechanism is already defined in there, with a dedicated
>> RSVP-TE object. RFC 4872 is Standard Track: is there any rational for no=
t
>> considering it?
>>
>> Regards,
>>
>> Julien
>>
>>
>> Le 26/07/2010 18:59, Sriganesh Kini a =E9crit :
>> > FYI - These updated version of these drafts were presented today at
>> > IETF78.
>> > http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-backup-01
>> > http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01
>> > Thanks
>> >
>> > - Sri
>> >
>> >
>> > _______________________________________________
>> > mpls mailing list
>> > mpls@ietf.org
>> > https://www.ietf.org/mailman/listinfo/mpls
>> >
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>
>

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

Dear Autumn,<br>thank you for adding specific case to our discussion. In my=
 view protecting segment <font face=3D"Arial" size=3D"2"><span>L10-L1-L2-L3=
-L4-L5 (e-backup tunnel) is shared by all backup tunnels that traverse the =
ring through nodes L10-L9-L8-L7-L6-L5. This e-backup tunnel is the e-backup=
 tunnels for all working sections/segments (in case of link and node protec=
tion) of an LSP L10-...-L8-..-L5. I&#39;d re-state my question to authors w=
hether they&#39;ve considered re-using RSVP-TE objects and subobjects defin=
ed in RFC 4873.=A0 If mechanisms and objects defined in RFC 4873 not suffic=
ient, why RFC 4873 not referenced in the draft Efficient Facility Backup FR=
R.</span></font><br>

<br>Regards,<br>Greg<br><br><div class=3D"gmail_quote">On Mon, Jul 26, 2010=
 at 12:16 PM, Autumn Liu <span dir=3D"ltr">&lt;<a href=3D"mailto:autumn.liu=
@ericsson.com" target=3D"_blank">autumn.liu@ericsson.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">




<div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>Hi Gr=
eg,</span></font></div>
<div dir=3D"ltr" align=3D"left"><font color=3D"#0000ff" face=3D"Arial" size=
=3D"2"><span></span></font>=A0</div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>=A0+-=
------L1--------L2---------L3--------L4-------+<br>=A0=A0|=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=20
=A0|</span></font></div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>=A0L1=
0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=20
L5</span></font></div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>=A0=
=A0|=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=20
|</span></font></div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>=A0+-=
------L9--------L8---------L7--------L6-------+<br>=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=20
</span></font></div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>Not a=
ll PLRs. Using the diagram in draft as an=20
example.</span></font></div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>Bypas=
s 1 (to protect link between L8 and L7) :=20
L8-L9-L10-L1-L2-L3-L4-L5-L6-L7 </span></font></div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>Bypas=
s 2 (to protect node failure on L8) :=20
L9-L10-L1-L2-L3-L4-L5-L6-L7</span></font></div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span></spa=
n></font>=A0</div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>e-bac=
kup tunnel L10-L1-L2-L3-L4-L5=A0can=20
be=A0used instead for both cases without getting=20
traffic=A0u-turned.</span></font></div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span></spa=
n></font>=A0</div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>Regar=
ds,</span></font></div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span>Autum=
n</span></font></div>
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" size=3D"2"><span><br>=
=A0</span></font></div><br>
<div dir=3D"ltr" align=3D"left" lang=3D"en-us">
<hr>
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Greg Mirsky [mailto:<a href=
=3D"mailto:gregimirsky@gmail.com" target=3D"_blank">gregimirsky@gmail.com</=
a>]=20
<br><b>Sent:</b> Monday, July 26, 2010 12:03 PM<br><b>To:</b> Autumn=20
Liu<br><b>Cc:</b> Julien Meuric; Sriganesh Kini;=20
<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a><div><d=
iv></div><div><br><b>Subject:</b> Re: [mpls] Updated drafts -=20
draft-kini-mpls-ring-frr-facility-backup,=20
draft-kini-mpls-fast-lsp-alert<br></div></div></font><br></div><div><div></=
div><div>
<div></div>Dear Autumn,<br>I&#39;m quite surprised to read your reply to Ju=
lien. My=20
understanding of your proposal is that all PLRs share the same u-PLR for gi=
ven=20
ring segment of LSP. Please correct me if my understanding is different fro=
m=20
authors intention.<br>I&#39;d like to add to Julien&#39;s comment that RFC =
4873 seems=20
relevant to your solution as well as RFC 4872. And I&#39;d ask the same que=
stion as=20
Julien in regard to not referencing RFC 4873.<br><br>Regards,<br>Greg<br><b=
r>
<div class=3D"gmail_quote">On Mon, Jul 26, 2010 at 11:30 AM, Autumn Liu <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:autumn.liu@ericsson.com" target=3D"_bl=
ank">autumn.liu@ericsson.com</a>&gt;</span>=20
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"padding-left: 1ex; margin: 0pt 0=
pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);">Hi=20
  Julien,<br><br>draft-kini-mpls-ring-frr-facility-backup describes a mecha=
nism=20
  to let the primary LSP be aware of what the bypass LSP for corresponding=
=20
  protected facility. If my understanding is correct, the association mecha=
nism=20
  defined in 4872 is used to associate the primary and backup LSPs. This is=
 not=20
  good enough for the problem the draft is trying to address since each=20
  link/node along the primary LSP may have different bypass=20
  LSPs.<br><br>Regards,<br><font color=3D"#888888">Autumn<br></font>
  <div>
  <div></div>
  <div><br><br>-----Original Message-----<br>From: <a href=3D"mailto:mpls-b=
ounces@ietf.org" target=3D"_blank">mpls-bounces@ietf.org</a> [mailto:<a hre=
f=3D"mailto:mpls-bounces@ietf.org" target=3D"_blank">mpls-bounces@ietf.org<=
/a>] On Behalf Of=20
  Julien Meuric<br>Sent: Monday, July 26, 2010 10:40 AM<br>To: Sriganesh=20
  Kini<br>Cc: <a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.=
org</a><br>Subject: Re:=20
  [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup,=20
  draft-kini-mpls-fast-lsp-alert<br><br>Hi Sriganesh.<br><br>The mechanism=
=20
  described in draft-kini-mpls-ring-frr-facility-backup<br>reminds me of en=
d to=20
  end recovery (or more specifically end to end protection), as enabled by =
RFC=20
  4872. That is all the more similar because the association mechanism is=
=20
  already defined in there, with a dedicated RSVP-TE object. RFC 4872 is=20
  Standard Track: is there any rational for not considering=20
  it?<br><br>Regards,<br><br>Julien<br><br><br>Le 26/07/2010 18:59, Srigane=
sh=20
  Kini a =E9crit :<br>&gt; FYI - These updated version of these drafts were=
=20
  presented today at<br>&gt; IETF78.<br>&gt; <a href=3D"http://tools.ietf.o=
rg/html/draft-kini-mpls-ring-frr-facility-backup-01" target=3D"_blank">http=
://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-backup-01</a><br>

&gt;=20
  <a href=3D"http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01" =
target=3D"_blank">http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert=
-01</a><br>&gt;=20
  Thanks<br>&gt;<br>&gt; - Sri<br>&gt;<br>&gt;<br>&gt;=20
  _______________________________________________<br>&gt; mpls mailing=20
  list<br>&gt; <a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf=
.org</a><br>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mpls" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>&gt;<br>__=
_____________________________________________<br>

mpls=20
  mailing list<br><a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@i=
etf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/mpls" targe=
t=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>____________=
___________________________________<br>

mpls=20
  mailing list<br><a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@i=
etf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/mpls" targe=
t=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br></div></div>=
</blockquote>

</div><br></div></div></div>
</blockquote></div><br>

--0016364588b4b79332048c50596f--

From gregimirsky@gmail.com  Mon Jul 26 13:52:59 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE0993A6937 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 13:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=0.398, BAYES_00=-2.599, HTML_MESSAGE=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 6J1CG9KwbAUI for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 13:52:59 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id DF8DB3A68B6 for <mpls@ietf.org>; Mon, 26 Jul 2010 13:52:58 -0700 (PDT)
Received: by vws10 with SMTP id 10so3024625vws.31 for <mpls@ietf.org>; Mon, 26 Jul 2010 13:53:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=+TcxIH9SGsfrxrwntlYe2QyPYpqCnwFKgiiVPWCh83U=; b=uUZex0/eYsY1QTXatFtZtWHpZ8Y3mb64uAs1r31fBKxsrZnm4UNxGZRHANxB4LvIdA 9L8GG6PPDc5yq1ka3YkqOmG0/KlylEj+P0NZmIe0rnW3WE0ckgjgiOc5pFYtH7scaRSO zydvIR2gkoeOs7nVc0EZS8R+DhlCc3txZQTKw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hKAP4EC/NFYDeiXgojTMwQGF+Jg3beSDe+vzJlpsZQcOeXW/CSzpM6qVGsOt7cG5tQ QNvmWXRU88QFmuoQ8h5fhCo6md90VXb1Nl5rM/8M5ZmHeDv7XlFEaUYyh9X9MNMMAoDG QgcXTALH0HTcsyNbtBcktB3G9o1IqmGWobqek=
MIME-Version: 1.0
Received: by 10.220.59.202 with SMTP id m10mr4265320vch.193.1280177599816;  Mon, 26 Jul 2010 13:53:19 -0700 (PDT)
Received: by 10.220.86.72 with HTTP; Mon, 26 Jul 2010 13:53:19 -0700 (PDT)
Date: Mon, 26 Jul 2010 13:53:19 -0700
Message-ID: <AANLkTinf_TdjCXfvZDhEMjrkuM3bowYwKe-2NsSftTrf@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Autumn Liu <autumn.liu@ericsson.com>, Sriganesh Kini <sriganesh.kini@ericsson.com>, mpls@ietf.org
Content-Type: multipart/alternative; boundary=e0cb4e8878271624e9048c5093ac
Subject: [mpls] Determining proper TTL of a tunnel in Fast LSP-alert Mechanism
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 20:52:59 -0000

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

Dear Authors,
the Section 3.2.2 states new requirement which ends with the sentence:
"An LSP label on the forwarded packet MUST continue to have TTL set to 1."
But at the same time, in Section 6 when outlining direction for future work,
it is said that in heterogeneous environment value of TTL must be determined
by each node that supports the Fast LSP-alert mechanism. Does that scenario
invalidates the requirement put forward in Section 3.2.2?

Regards,
Greg

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

Dear Authors,<br>the Section 3.2.2 states new requirement which ends with t=
he sentence:<br>&quot;An LSP label on the forwarded packet MUST continue to=
 have TTL set to 1.&quot;<br>But at the same time, in Section 6 when outlin=
ing direction for future work, it is said that in heterogeneous environment=
 value of TTL must be determined by each node that supports the Fast LSP-al=
ert mechanism. Does that scenario invalidates the requirement put forward i=
n Section 3.2.2?<br>
<br>Regards,<br>Greg<br>

--e0cb4e8878271624e9048c5093ac--

From vishwas.ietf@gmail.com  Mon Jul 26 14:38:54 2010
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB44A3A6A03 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 14:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BFWevcrG3MCn for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 14:38:52 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id C72833A69A8 for <mpls@ietf.org>; Mon, 26 Jul 2010 14:38:51 -0700 (PDT)
Received: by qwe5 with SMTP id 5so387454qwe.31 for <mpls@ietf.org>; Mon, 26 Jul 2010 14:39:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=KKjosZBiTkFYG2Hoa/1X0FOSti4mXsyLub/NiNJNhes=; b=TANiBou6GszcD6jG+zBHXrSD1TUNtzJE1r+BnpuN5q+Sdp0YeIIYamw7t1ZKhpMwtv X4D6x5OPEHcOCXcfrcdH/JOWQJmVpSk2Hf+DD9Ey9oVBdRbEjJJyhgp68TDfSdC27HJn goQXUSJWWpKexICwh20gx2udCjj+AQZBjzICI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=JD4CD0B7fiBFyZXheszKPSyXUirGcxO87bzPn9fd5XuToa9WJ1iabCNx/X7pnA9z7l Ii0ch3zf1gwOqz5Vqss+pwKEhnXXUkE64lS7UA2LSA8bOoH6tA2JYBNnYag6PFYTF1j1 RAxVl2XTYvVZO7ZbPdfEBBG/eBNJjkLLmVT+k=
MIME-Version: 1.0
Received: by 10.224.74.82 with SMTP id t18mr6669239qaj.165.1280180352677; Mon,  26 Jul 2010 14:39:12 -0700 (PDT)
Received: by 10.229.19.17 with HTTP; Mon, 26 Jul 2010 14:39:12 -0700 (PDT)
In-Reply-To: <v2s77ead0ec1004160659r93f30297k8e6f262bf9465a13@mail.gmail.com>
References: <h2g77ead0ec1004061223k7cc69585ncf8761efb0df2d33@mail.gmail.com> <4395962A7C18D84191B205AD7089698305CA00CA@S4DE9JSAAIB.ost.t-com.de> <r2h77ead0ec1004120755za2c9aadcw9184a1d56cd10c5b@mail.gmail.com> <q2s77ead0ec1004120940r875bc282y7edd293bd846c57@mail.gmail.com> <1E2FA684-E5E0-45FA-9885-0BA7C288AC08@eng.gxn.net> <alpine.DEB.1.10.1004150758320.6768@uplift.swm.pp.se> <x2k77ead0ec1004150817v5f2da373lce60f3827a5e00d7@mail.gmail.com> <o2r3c502ff41004160103qf32c87dbn9c9cfd67f057631a@mail.gmail.com> <v2s77ead0ec1004160659r93f30297k8e6f262bf9465a13@mail.gmail.com>
Date: Mon, 26 Jul 2010 14:39:12 -0700
Message-ID: <AANLkTinAGcPj2DUH8iUs0QxZTxoU9ikPdbwRq_Z1Pz7x@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: George Swallow <swallow@cisco.com>, Loa Andersson <loa@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Rob Shakir <rjs@eng.gxn.net>, mpls@ietf.org, faz@netfm.co.uk
Subject: [mpls] LDP IPv6
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 21:38:55 -0000

Hi Chairs,

We would like to request you to have a WG call to gauge support and
adopt the document LDP IPv6 as a working Group item.

The document is located at
http://tools.ietf.org/html/draft-manral-mpls-ldp-ipv6-03

The document in the past has got some review on the list.

Thanks,
Vishwas

On Fri, Apr 16, 2010 at 6:59 AM, Vishwas Manral <vishwas.ietf@gmail.com> wr=
ote:
> Hi Egor,
>
> 1. As Mikael brought out the question of what else is missing I
> brought up the MIB and RSVP-TE issues. I will bring the details out in
> another mail with the correct subject line.
> 2. I guess now that we have more knowledge of the draft we can
> actually try to push it further.
>
> Thanks,
> Vishwas
>
> On Fri, Apr 16, 2010 at 1:03 AM, Egor Zimin <lesnix@gmail.com> wrote:
>> Hi, Vishwas,
>>
>> 1. About RSVP-TE and IPv6 Router Alert option.
>> I do not quite understand your opinion.
>> Do you propose to remove Router Alert option for IPv6 ? Why ? Because of
>> lack of RSVP-TE IPv6 implementations alone ? Because of only RSVP TE use=
s
>> this option ? Also, what security issues do you mean ?
>> And... what does that have to LDPv6 draft discussion?
>>
>> 2. About draft-manral-mpls-ldp-ipv6-03:
>> I think, the changes and clarifications proposed in the draft are very
>> obvious and not so significant. In fact, the draft only clarifies peer
>> discovery and transport session establishment procedures for IPv6. I don=
't
>> understand why this draft has not yet become RFC.
>>
>> 2010/4/15 Vishwas Manral <vishwas.ietf@gmail.com>
>>>
>>> Hi Mikael/ Rob/ Farhan/ Egor,
>>>
>>> > Considering IPv4 runout I definitely see greenfield rollout in 1-2
>>> > years wanting to do this IPv6 only, and considering code usually
>>> > takes time to be finished the standards should definitely be done
>>> > by now.
>>> >
>>> > What else is missing?
>>> Let me begin by saying that most drafts/ RFC's have some IPv6
>>> component to them. This however is appended as an add-on in some
>>> cases. As most of these have not been looked at in detail there are
>>> some holes in the RFC for IPv6.
>>>
>>> I found similar holes a couple of years back and wrote this and the
>>> MPLS-TC IPv6 MIB draft. I also noticed that for RSVP-TE for IPv6 we do
>>> not have support for Router Alert in a lot of platforms. It also has
>>> all the security issues aside from that.
>>>
>>> As RSVP-TE seems to be carrying Router Alert as a legacy thing and as
>>> RSVP-TE IPv6 is not implemented on the field I think it would be good
>>> to do away, remove the use of Router Alert in RSVP for IPv6.
>>>
>>> What do folks on the list think?
>>>
>>> BTW, I had mails from a couple of more operators in private and have
>>> forwarded them to the chairs.
>>>
>>> Thanks,
>>> Vishwas
>>>
>>> On Wed, Apr 14, 2010 at 11:01 PM, Mikael Abrahamsson <swmike@swm.pp.se>
>>> wrote:
>>> > On Wed, 14 Apr 2010, Rob Shakir wrote:
>>> >
>>> >> I'd just like to speak up in support of this draft also. As an opera=
tor
>>> >> that is progressing an IPv6 rollout, we are finding that in a number=
 of
>>> >> places, the only need to utilise 6PE is in order to address the lack=
 of
>>> >> support for IPv6 in LDP.
>>> >
>>> > +1 from me as well, I'm actually surprised that there hasn't been mor=
e
>>> > work
>>> > in establishing feature parity between IPv4 and IPv6 in the control
>>> > plane.
>>> > I'd imagine that by now it would be possible to implement
>>> > standards-based
>>> > IPv6 only control plane with equal functionality as is today possible
>>> > with
>>> > IPv4.
>>> >
>>> >> Whilst I think it's unlikely that many operators are currently putti=
ng
>>> >> this down as a mandatory requirement, it's definitely something that=
 I
>>> >> believe is required.
>>> >
>>> > Considering IPv4 runout I definitely see greenfield rollout in 1-2 ye=
ars
>>> > wanting to do this IPv6 only, and considering code usually takes time=
 to
>>> > be
>>> > finished the standards should definitely be done by now.
>>> >
>>> > What else is missing?
>>> >
>>> > --
>>> > Mikael Abrahamsson =A0 =A0email: swmike@swm.pp.se
>>> >
>>
>>
>>
>> --
>> Best regards,
>> Egor Zimin
>>
>

From sriganesh.kini@ericsson.com  Mon Jul 26 14:43:14 2010
Return-Path: <sriganesh.kini@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48FC03A69B4 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 14:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, HTML_MESSAGE=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 5qaz7wb0Lgva for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 14:43:13 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 519C23A684E for <mpls@ietf.org>; Mon, 26 Jul 2010 14:43:13 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6QLhXe8015614 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 26 Jul 2010 16:43:33 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Mon, 26 Jul 2010 17:43:32 -0400
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
To: Greg Mirsky <gregimirsky@gmail.com>, Autumn Liu <autumn.liu@ericsson.com>,  "mpls@ietf.org" <mpls@ietf.org>
Date: Mon, 26 Jul 2010 17:43:31 -0400
Thread-Topic: Determining proper TTL of a tunnel in Fast LSP-alert Mechanism
Thread-Index: AcstBKXyP4QXzx89TaOowREeHFvMvwAArHig
Message-ID: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80D0D@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTinf_TdjCXfvZDhEMjrkuM3bowYwKe-2NsSftTrf@mail.gmail.com>
In-Reply-To: <AANLkTinf_TdjCXfvZDhEMjrkuM3bowYwKe-2NsSftTrf@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5A5E55DF96F73844AF7DFB0F48721F0F567DB80D0DEUSAACMS0703e_"
MIME-Version: 1.0
Subject: Re: [mpls] Determining proper TTL of a tunnel in Fast LSP-alert Mechanism
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 21:43:14 -0000

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

Greg,

I wouldn't interpret that as invalidating the requirement. Those are though=
ts on potential workarounds and should be considered only for scenarios tha=
t have LSRs that don't support the functionality.

Thanks

- Sri



________________________________
From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: Monday, July 26, 2010 1:53 PM
To: Autumn Liu; Sriganesh Kini; mpls@ietf.org
Subject: Determining proper TTL of a tunnel in Fast LSP-alert Mechanism

Dear Authors,
the Section 3.2.2 states new requirement which ends with the sentence:
"An LSP label on the forwarded packet MUST continue to have TTL set to 1."
But at the same time, in Section 6 when outlining direction for future work=
, it is said that in heterogeneous environment value of TTL must be determi=
ned by each node that supports the Fast LSP-alert mechanism. Does that scen=
ario invalidates the requirement put forward in Section 3.2.2?

Regards,
Greg

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18470" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D175071321-26072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Greg,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D175071321-26072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D175071321-26072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I wouldn't&nbsp;interpret that as invalidating the=
=20
requirement. Those are thoughts on potential workarounds and should be=20
considered only for scenarios that&nbsp;have&nbsp;LSRs that don't support t=
he=20
functionality. </FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D175071321-26072010><FONT face=3DArial color=3D#0000ff=20
size=3D2>Thanks</FONT></SPAN></DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>- Sri</FONT></SPAN> </P>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Greg Mirsky=20
  [mailto:gregimirsky@gmail.com] <BR><B>Sent:</B> Monday, July 26, 2010 1:5=
3=20
  PM<BR><B>To:</B> Autumn Liu; Sriganesh Kini; mpls@ietf.org<BR><B>Subject:=
</B>=20
  Determining proper TTL of a tunnel in Fast LSP-alert=20
  Mechanism<BR></FONT><BR></DIV>
  <DIV></DIV>Dear Authors,<BR>the Section 3.2.2 states new requirement whic=
h=20
  ends with the sentence:<BR>"An LSP label on the forwarded packet MUST con=
tinue=20
  to have TTL set to 1."<BR>But at the same time, in Section 6 when outlini=
ng=20
  direction for future work, it is said that in heterogeneous environment v=
alue=20
  of TTL must be determined by each node that supports the Fast LSP-alert=20
  mechanism. Does that scenario invalidates the requirement put forward in=
=20
  Section 3.2.2?<BR><BR>Regards,<BR>Greg<BR></BLOCKQUOTE></BODY></HTML>

--_000_5A5E55DF96F73844AF7DFB0F48721F0F567DB80D0DEUSAACMS0703e_--

From cts@etri.re.kr  Mon Jul 26 16:42:39 2010
Return-Path: <cts@etri.re.kr>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 905C83A6872; Mon, 26 Jul 2010 16:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.63
X-Spam-Level: 
X-Spam-Status: No, score=-100.63 tagged_above=-999 required=5 tests=[AWL=0.220, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 4ifIQ2tpUf3Q; Mon, 26 Jul 2010 16:42:33 -0700 (PDT)
Received: from email1.etri.info (email1.etri.re.kr [129.254.16.131]) by core3.amsl.com (Postfix) with ESMTP id 77EF83A6873; Mon, 26 Jul 2010 16:42:30 -0700 (PDT)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB2D1C.40588DB4"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 27 Jul 2010 08:42:36 +0900
Message-ID: <4E45B4AAC0E1F04CAADDC9B606BB198F01E8A892@email1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Version Notification for draft-cheung-mpls-tp-mesh-protection-01 
thread-index: AcssnOzNaXabtMrrSeC6r5LEx1sJqg==
From: =?utf-8?B?7KCV7YOc7Iud?= <cts@etri.re.kr>
To: <mpls-tp@ietf.org>, <mpls@ietf.org>
Subject: [mpls] FW: New Version Notification for draft-cheung-mpls-tp-mesh-protection-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: =?utf-8?B?7KCV7YOc7Iud?= <cts@etri.re.kr>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 23:42:40 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB2D1C.40588DB4
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

RGVhciBNUExTIFdHLA0KDQogDQoNClBsZWFzZSBub3RlIHRoYXQgd2Ugc3VibWl0dGVkIGEgbmV3
IHZlcnNpb24gb2YgdGhlIE1QTFMtVFAgc2hhcmVkIG1lc2ggcHJvdGVjdGlvbi4NCg0KSW4gdGhp
cyB2ZXJzaW9uLCB0aGUgbWVjaGFuaXNtIGhhcyBiZWVuIHJlZmluZWQgYW5kIGRldGFpbGVkLCBh
bmQgc29tZSB0ZWNobmljYWwgaXNzdWVzIGluIHRoZSBwcmV2aW91cyB2ZXJzaW9uIGFyZSByZXNv
bHZlZC4NCg0KIA0KDQpBIFVSTCBmb3IgdGhpcyBJLUQgaXM6DQoNCmh0dHA6Ly93d3cuaWV0Zi5v
cmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWNoZXVuZy1tcGxzLXRwLW1lc2gtcHJvdGVjdGlvbi0w
MS50eHQNCg0KIA0KDQpXZSB3b3VsZCBhcHByZWNpYXRlIHJldmlldyBhbmQgY29tbWVudHMgZm9y
IG91ciBkb2N1bWVudC4NCg0KIA0KDQpCZXN0IHJlZ2FyZHMsDQoNClRhZXNpaw0KDQogDQoNCiAN
Cg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206ICJJRVRGIEktRCBTdWJtaXNzaW9u
IFRvb2wiIDxpZHN1Ym1pc3Npb25AaWV0Zi5vcmc+DQpGcm9tIERhdGU6IDIwMTAtMDctMjYgUE0g
NTowNToyOQ0KVG86ICJjdHNAZXRyaS5yZS5rciIgPGN0c0BldHJpLnJlLmtyPg0KQ2M6ICJyeW9v
QGV0cmkucmUua3IiIDxyeW9vQGV0cmkucmUua3I+DQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3Rp
ZmljYXRpb24gZm9yIGRyYWZ0LWNoZXVuZy1tcGxzLXRwLW1lc2gtcHJvdGVjdGlvbi0wMSANCg0K
QSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWNoZXVuZy1tcGxzLXRwLW1lc2gtcHJvdGVjdGlv
bi0wMS50eHQgaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBUYWUtc2lrIENoZXVu
ZyBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOiAgICAgICAg
ZHJhZnQtY2hldW5nLW1wbHMtdHAtbWVzaC1wcm90ZWN0aW9uDQpSZXZpc2lvbjogICAgICAgIDAx
DQpUaXRsZTogICAgICAgICAgIE1QTFMtVFAgU2hhcmVkIE1lc2ggUHJvdGVjdGlvbg0KQ3JlYXRp
b25fZGF0ZTogICAyMDEwLTA3LTI2DQpXRyBJRDogICAgICAgICAgIEluZGVwZW5kZW50IFN1Ym1p
c3Npb24NCk51bWJlcl9vZl9wYWdlczogMTgNCg0KQWJzdHJhY3Q6DQpUaGlzIGRvY3VtZW50IGRl
c2NyaWJlcyBhIG1lY2hhbmlzbSB0byBhZGRyZXNzIHRoZSByZXF1aXJlbWVudCBmb3INCnByb3Rl
Y3Rpb24gb2YgTGFiZWwgU3dpdGNoZWQgUGF0aHMgKExTUHMpIGluIGFuIE1QTFMgVHJhbnNwb3J0
DQpQcm9maWxlIChNUExTLVRQKSBtZXNoIHRvcG9sb2d5LiBUaGUgc2hhcmVkIG1lc2ggcHJvdGVj
dGlvbiBtZWNoYW5pc20NCmVuYWJsZXMgbXVsdGlwbGUgcHJvdGVjdGlvbiBwYXRocyB3aXRoaW4g
YSBzaGFyZWQgbWVzaCBwcm90ZWN0aW9uDQpkb21haW4gdG8gc2hhcmUgcHJvdGVjdGlvbiByZXNv
dXJjZXMgZm9yIHRoZSBwcm90ZWN0aW9uIG9mIHdvcmtpbmcNCnBhdGhzIGJ5IGNvb3JkaW5hdGlu
ZyBwcm90ZWN0aW9uIHN3aXRjaGluZyBvcGVyYXRpb25zIGFjY29yZGluZyB0bw0KdGhlIHByaW9y
aXR5IGFzc2lnbmVkIHRvIGVhY2ggZW5kLXRvLWVuZCBsaW5lYXIgcHJvdGVjdGlvbiBkb21haW4u
DQoNClRoaXMgZG9jdW1lbnQgaXMgYSBwcm9kdWN0IG9mIGEgam9pbnQgSW50ZXJuZXQgRW5naW5l
ZXJpbmcgVGFzayBGb3JjZQ0KKElFVEYpIC8gSW50ZXJuYXRpb25hbCBUZWxlY29tbXVuaWNhdGlv
biBVbmlvbiBUZWxlY29tbXVuaWNhdGlvbg0KU3RhbmRhcmRpemF0aW9uIFNlY3RvciAoSVRVLVQp
IGVmZm9ydCB0byBpbmNsdWRlIGFuIE1QTFMgVHJhbnNwb3J0DQpQcm9maWxlIHdpdGhpbiB0aGUg
SUVURiBNUExTIGFuZCBQV0UzIGFyY2hpdGVjdHVyZXMgdG8gc3VwcG9ydCB0aGUNCmNhcGFiaWxp
dGllcyBhbmQgZnVuY3Rpb25hbGl0aWVzIG9mIGEgcGFja2V0IHRyYW5zcG9ydCBuZXR3b3JrLg0K
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQuDQoNCg0K
DQo=

------_=_NextPart_001_01CB2D1C.40588DB4
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQoNCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9R2VuZXJhdG9y
IGNvbnRlbnQ9Ik1pY3Jvc29mdCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT4N
CjwhLS0NCiAvKiBGb250IERlZmluaXRpb25zICovDQogQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTrqtbTrprw7DQoJcGFub3NlLTE6MiAxMSA2IDAgMCAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxA6rW066a8IjsNCglwYW5vc2UtMToy
IDExIDYgMCAwIDEgMSAxIDEgMTt9DQogLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCiBwLk1zb05v
cm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2lu
LWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk66rW066a8
O30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNw
YW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y
OnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnANCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt
c2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk66rW066a8O30NCnNwYW4uRW1haWxTdHlsZTE4DQoJ
e21zby1zdHlsZS10eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkFyaWFsIiwi
c2Fucy1zZXJpZiI7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9u
bHk7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdp
bjozLjBjbSA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6
V29yZFNlY3Rpb24xO30NCi0tPg0KPC9zdHlsZT4NCjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
IDxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48
IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCiA8bzpzaGFwZWxheW91dCB2OmV4
dD0iZWRpdCI+DQogIDxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KIDwvbzpzaGFw
ZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCg0KPGJvZHkgbGFuZz1LTyBsaW5r
PWJsdWUgdmxpbms9cHVycGxlPg0KDQo8ZGl2IGNsYXNzPVdvcmRTZWN0aW9uMT4NCg0KPGRpdiBp
ZD1tc2dib2R5Pg0KDQo8ZGl2Pg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4g
bGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQXJpYWwiLCJz
YW5zLXNlcmlmIic+RGVhcg0KTVBMUyBXRyw8L3NwYW4+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0n
Zm9udC1zaXplOjEwLjBwdCc+PG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8L2Rpdj4NCg0KPGRp
dj4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6
ZToxMC4wcHQnPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXY+
DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCIsInNhbnMtc2VyaWYiJz5QbGVhc2UNCm5vdGUgdGhh
dCB3ZSBzdWJtaXR0ZWQgYSBuZXcgdmVyc2lvbiZuYnNwO29mIHRoZSBNUExTLVRQIHNoYXJlZCBt
ZXNoDQpwcm90ZWN0aW9uLjwvc3Bhbj48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6
MTAuMHB0Jz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2Pg0KDQo8cCBj
bGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseToiQXJpYWwiLCJzYW5zLXNlcmlmIic+SW4NCnRoaXMgdmVyc2lvbiwgdGhlIG1l
Y2hhbmlzbSBoYXMgYmVlbiByZWZpbmVkIGFuZCBkZXRhaWxlZCwgYW5kIHNvbWUgdGVjaG5pY2Fs
DQppc3N1ZXMgaW4gdGhlIHByZXZpb3VzIHZlcnNpb24gYXJlIHJlc29sdmVkLjwvc3Bhbj48c3Bh
biBsYW5nPUVOLVVTDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdCc+PG86cD48L286cD48L3NwYW4+
PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdj4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9
RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQnPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCg0KPC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVO
LVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCIsInNhbnMtc2Vy
aWYiJz5BDQpVUkwgZm9yIHRoaXMmbmJzcDtJLUQgaXM6PC9zcGFuPjxzcGFuIGxhbmc9RU4tVVMg
c3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+
DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCIsInNhbnMtc2VyaWYiJz48YQ0KaHJl
Zj0iaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtY2hldW5nLW1wbHMt
dHAtbWVzaC1wcm90ZWN0aW9uLTAxLnR4dCINCnRhcmdldD0iX2JsYW5rIj5odHRwOi8vd3d3Lmll
dGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1jaGV1bmctbXBscy10cC1tZXNoLXByb3RlY3Rp
b24tMDEudHh0PC9hPjwvc3Bhbj48c3Bhbg0KbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEw
LjBwdCc+PG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdj4NCg0KPHAgY2xh
c3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQnPiZu
YnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNz
PU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiJBcmlhbCIsInNhbnMtc2VyaWYiJz5XZQ0Kd291bGQgYXBwcmVjaWF0ZSByZXZpZXcg
YW5kIGNvbW1lbnRzIGZvciBvdXIgZG9jdW1lbnQuPC9zcGFuPjxzcGFuIGxhbmc9RU4tVVMNCnN0
eWxlPSdmb250LXNpemU6MTAuMHB0Jz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjwvZGl2Pg0K
DQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9u
dC1zaXplOjEwLjBwdCc+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8L2Rpdj4NCg0K
PGRpdj4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJpZiInPkJlc3QNCnJlZ2Fy
ZHMsPC9zcGFuPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQnPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1h
bD48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJB
cmlhbCIsInNhbnMtc2VyaWYiJz5UYWVzaWs8L3NwYW4+PHNwYW4NCmxhbmc9RU4tVVMgc3R5bGU9
J2ZvbnQtc2l6ZToxMC4wcHQnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxk
aXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNp
emU6MTAuMHB0Jz4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2
Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXpl
OjEwLjBwdCc+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdj4N
Cg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJpZiInPi0tLS0tT3JpZ2luYWwNCk1l
c3NhZ2UtLS0tLTxicj4NCjxiPkZyb206PC9iPiAmcXVvdDtJRVRGIEktRCBTdWJtaXNzaW9uIFRv
b2wmcXVvdDsgJmx0O2lkc3VibWlzc2lvbkBpZXRmLm9yZyZndDs8YnI+DQo8Yj5Gcm9tIERhdGU6
PC9iPiAyMDEwLTA3LTI2IFBNIDU6MDU6Mjk8YnI+DQo8Yj5Ubzo8L2I+ICZxdW90O2N0c0BldHJp
LnJlLmtyJnF1b3Q7ICZsdDtjdHNAZXRyaS5yZS5rciZndDs8YnI+DQo8Yj5DYzo8L2I+ICZxdW90
O3J5b29AZXRyaS5yZS5rciZxdW90OyAmbHQ7cnlvb0BldHJpLnJlLmtyJmd0Ozxicj4NCjxiPlN1
YmplY3Q6PC9iPiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yDQpkcmFmdC1jaGV1bmctbXBs
cy10cC1tZXNoLXByb3RlY3Rpb24tMDEgPG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8L2Rpdj4N
Cg0KPGRpdj4NCg0KPHAgc3R5bGU9J21hcmdpbi1ib3R0b206MTIuMHB0Jz48c3BhbiBsYW5nPUVO
LVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0Ow0KZm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1z
ZXJpZiInPkEgbmV3IHZlcnNpb24gb2YgSS1ELA0KZHJhZnQtY2hldW5nLW1wbHMtdHAtbWVzaC1w
cm90ZWN0aW9uLTAxLnR4dCBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5DQpUYWUt
c2lrIENoZXVuZyBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuPGJyPg0KPGJyPg0K
RmlsZW5hbWU6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQpkcmFm
dC1jaGV1bmctbXBscy10cC1tZXNoLXByb3RlY3Rpb248YnI+DQpSZXZpc2lvbjombmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgMDE8YnI+DQpUaXRsZTombmJzcDsgJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IE1QTFMtVFAgU2hh
cmVkDQpNZXNoIFByb3RlY3Rpb248YnI+DQpDcmVhdGlvbl9kYXRlOiZuYnNwOyZuYnNwOyAyMDEw
LTA3LTI2PGJyPg0KV0cgSUQ6Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBJbmRlcGVuZGVudA0KU3VibWlzc2lvbjxicj4NCk51bWJlcl9vZl9w
YWdlczogMTg8YnI+DQo8YnI+DQpBYnN0cmFjdDo8YnI+DQpUaGlzIGRvY3VtZW50IGRlc2NyaWJl
cyBhIG1lY2hhbmlzbSB0byBhZGRyZXNzIHRoZSByZXF1aXJlbWVudCBmb3I8YnI+DQpwcm90ZWN0
aW9uIG9mIExhYmVsIFN3aXRjaGVkIFBhdGhzIChMU1BzKSBpbiBhbiBNUExTIFRyYW5zcG9ydDxi
cj4NClByb2ZpbGUgKE1QTFMtVFApIG1lc2ggdG9wb2xvZ3kuIFRoZSBzaGFyZWQgbWVzaCBwcm90
ZWN0aW9uIG1lY2hhbmlzbTxicj4NCmVuYWJsZXMgbXVsdGlwbGUgcHJvdGVjdGlvbiBwYXRocyB3
aXRoaW4gYSBzaGFyZWQgbWVzaCBwcm90ZWN0aW9uPGJyPg0KZG9tYWluIHRvIHNoYXJlIHByb3Rl
Y3Rpb24gcmVzb3VyY2VzIGZvciB0aGUgcHJvdGVjdGlvbiBvZiB3b3JraW5nPGJyPg0KcGF0aHMg
YnkgY29vcmRpbmF0aW5nIHByb3RlY3Rpb24gc3dpdGNoaW5nIG9wZXJhdGlvbnMgYWNjb3JkaW5n
IHRvPGJyPg0KdGhlIHByaW9yaXR5IGFzc2lnbmVkIHRvIGVhY2ggZW5kLXRvLWVuZCBsaW5lYXIg
cHJvdGVjdGlvbiBkb21haW4uPGJyPg0KPGJyPg0KVGhpcyBkb2N1bWVudCBpcyBhIHByb2R1Y3Qg
b2YgYSBqb2ludCBJbnRlcm5ldCBFbmdpbmVlcmluZyBUYXNrIEZvcmNlPGJyPg0KKElFVEYpIC8g
SW50ZXJuYXRpb25hbCBUZWxlY29tbXVuaWNhdGlvbiBVbmlvbiBUZWxlY29tbXVuaWNhdGlvbjxi
cj4NClN0YW5kYXJkaXphdGlvbiBTZWN0b3IgKElUVS1UKSBlZmZvcnQgdG8gaW5jbHVkZSBhbiBN
UExTIFRyYW5zcG9ydDxicj4NClByb2ZpbGUgd2l0aGluIHRoZSBJRVRGIE1QTFMgYW5kIFBXRTMg
YXJjaGl0ZWN0dXJlcyB0byBzdXBwb3J0IHRoZTxicj4NCmNhcGFiaWxpdGllcyBhbmQgZnVuY3Rp
b25hbGl0aWVzIG9mIGEgcGFja2V0IHRyYW5zcG9ydCBuZXR3b3JrLjxicj4NCiZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOzxicj4NCjxicj4NCjxicj4NClRoZSBJRVRGIFNlY3JldGFyaWF0
Ljxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjwvZGl2Pg0K
DQo8L2Rpdj4NCg0KPC9kaXY+DQoNCjwvYm9keT4NCg0KPC9odG1sPg0K

------_=_NextPart_001_01CB2D1C.40588DB4--

From Alexander.Vainshtein@ecitele.com  Mon Jul 26 23:55:53 2010
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D2EE3A68D7 for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 23:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.192
X-Spam-Level: 
X-Spam-Status: No, score=-2.192 tagged_above=-999 required=5 tests=[AWL=0.406,  BAYES_00=-2.599, HTML_MESSAGE=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 uTPJ7ws+9czv for <mpls@core3.amsl.com>; Mon, 26 Jul 2010 23:55:47 -0700 (PDT)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id DF5F93A67A2 for <mpls@ietf.org>; Mon, 26 Jul 2010 23:55:46 -0700 (PDT)
Received: from DLP_bound_connection ( [147.234.242.234]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 86.33.32431.7038E4C4; Tue, 27 Jul 2010 09:56:07 +0300 (IDT)
X-AuditID: 93eaf2e7-b7c6dae000007eaf-4a-4c4e82c70d66
Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 92.33.32431.7C28E4C4; Tue, 27 Jul 2010 09:55:03 +0300 (IDT)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Tue, 27 Jul 2010 09:55:02 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Tue, 27 Jul 2010 09:55:18 +0300
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaAABzm8kA=
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D5BB4A3F91@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C76D5BB4A3ED3@ILPTMAIL02.ecitele.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80AFB@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80AFB@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A3C5DF08D38B6049839A6F553B331C76D5BB4A3F91ILPTMAIL02eci_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 06:55:53 -0000

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

Sri,
Lots of thanks for a prompt response. It seems that we more or less agree o=
n the facts (proliferation of e-backup LSPs) but we differ in interpreting =
 the impact  of these facts  on the actual operational experience.

However, I'd like to notice that "BW effectiveness" of e-backup LSPs is als=
o somewhat problematic IMO.
Please note that both the regular backup and e-backup bypass tunnels cross =
multiple links that are not involved with the original set of LSPs they are=
 protecting. And they both consume BW on these links. The only difference i=
s that they are competing for BW with other LSPs, not with ones they are pr=
otecting. But the overall effect is exactly the same IMO.

My 2c,
     Sasha

From: Sriganesh Kini [mailto:sriganesh.kini@ericsson.com]
Sent: Monday, July 26, 2010 8:01 PM
To: Alexander Vainshtein
Cc: mpls@ietf.org
Subject: RE: [mpls] Scalability of the "effective FRR" approach in draft-ki=
ni-mpls-ring-frr-facility-backup-00.txt

Sasha,

As you noted the e-backup tunnel protects all LSPs that have a common {head=
-end, tail-end} pair. More precisely, the e-backup can be shared to protect=
 all LSPs that have a common {ring-ingress-LSR, ring-egress-LSR} pair (that=
 is path is disjoint with the e-backup).

If I understood correctly your concern is about the number of number of e-b=
ackup tunnels?

E-backup tunnels should be setup based on protected LSP's {ring-ingress, ri=
ng-egress} LSRs. Consider a typical case where in a ring, there is a 'ring-=
head-end' and LSPs are setup from other LSRs on the ring to the 'ring-head-=
end'. An e-backup should be setup from each LSR on the ring to the 'ring-he=
ad-end'. This is order(n).

Even for cases where protected LSPs have many possible combinations for {ri=
ng-ingress, ring-egress}, for typical ring sizes, the number of tunnels req=
uired should not be a concern for today's implementations.

Also, in many topologies an LSR that is purely a transit for protected LSPs=
, does not have to originate any e-backup.

Thanks

- Sri
PS: Regular facility FRR requires more that two backup tunnels, depending o=
n what is being protected.

________________________________
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Ale=
xander Vainshtein
Sent: Monday, July 26, 2010 9:57 AM
To: Sriganesh Kini
Cc: mpls@ietf.org
Subject: [mpls] Scalability of the "effective FRR" approach in draft-kini-m=
pls-ring-frr-facility-backup-00.txt
Sriganesh and all,
If I understood you correctly, your proposal requires a dedicated backup tu=
nnel for all LSPs with the given {head-end, tail-end} pair of LSRs in the r=
ing. (Regular facility FRR requires just two backup tunnels).
If this understanding is correct, this looks to like a serious scalability =
issue with your approach.

Regards,
     Sasha


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Sri,<o:p></o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Lots of thanks for a pro=
mpt
response. It seems that we more or less agree on the facts (proliferation o=
f
e-backup LSPs) but we differ in interpreting &nbsp;the impact &nbsp;of thes=
e
facts &nbsp;on the actual operational experience.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>However, I&#8217;d like =
to
notice that &#8220;BW effectiveness&#8221; of e-backup LSPs is also somewha=
t problematic
IMO.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Please note that both th=
e regular
backup and e-backup bypass tunnels cross multiple links that are not involv=
ed
with the original set of LSPs they are protecting. And they both consume BW=
 on
these links. The only difference is that they are competing for BW with oth=
er
LSPs, not with ones they are protecting. But the overall effect is exactly =
the
same IMO.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p>

<div>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>My 2c,<o:p></o:p></span>=
</p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;=
 Sasha<o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Sriganesh Kin=
i
[mailto:sriganesh.kini@ericsson.com] <br>
<b>Sent:</b> Monday, July 26, 2010 8:01 PM<br>
<b>To:</b> Alexander Vainshtein<br>
<b>Cc:</b> mpls@ietf.org<br>
<b>Subject:</b> RE: [mpls] Scalability of the &quot;effective FRR&quot;
approach in draft-kini-mpls-ring-frr-facility-backup-00.txt<o:p></o:p></spa=
n></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Sasha,</span><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New=
 Roman","serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>As you noted the&nbsp;e-backup tunnel protects all LSPs that ha=
ve a
common {head-end, tail-end} pair. More precisely, the e-backup can be share=
d to
protect&nbsp;all LSPs that have a common {ring-ingress-LSR, ring-egress-LSR=
}
pair&nbsp;(that is path&nbsp;is disjoint with the e-backup).</span><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p=
></span></p>

<div>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New=
 Roman","serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>If I understood correctly your concern is about the number of
number of e-backup tunnels?</span><span style=3D'font-size:12.0pt;font-fami=
ly:
"Times New Roman","serif"'><o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New=
 Roman","serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>E-backup tunnels should be setup based on protected LSP's
{ring-ingress, ring-egress} LSRs. Consider a typical case where in a ring,
there is a 'ring-head-end' and LSPs are setup from other LSRs on the ring t=
o
the 'ring-head-end'. An e-backup should be setup from each LSR on the ring =
to
the 'ring-head-end'. This is order(n). </span><span style=3D'font-size:12.0=
pt;
font-family:"Times New Roman","serif"'><o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New=
 Roman","serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Even&nbsp;for cases where protected LSPs&nbsp;have&nbsp;many
possible combinations&nbsp;for {ring-ingress, ring-egress},&nbsp;for typica=
l
ring sizes, the number of&nbsp;tunnels required&nbsp;should not be a concer=
n
for&nbsp;today's&nbsp;implementations.</span><span style=3D'font-size:12.0p=
t;
font-family:"Times New Roman","serif"'><o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New=
 Roman","serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Also, in many topologies&nbsp;an LSR that is purely a transit f=
or
protected LSPs,&nbsp;does not have to originate any e-backup.</span><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p=
></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New=
 Roman","serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Thanks</span><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman","serif"'><o:p></o:p></span></p>

</div>

<p><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>- Sri<=
/span>
<o:p></o:p></p>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>PS: Regular facility FRR requires more that two backup tunnels,
depending on what is being protected.</span><span style=3D'font-size:12.0pt=
;
font-family:"Times New Roman","serif"'><o:p></o:p></span></p>

</div>

<blockquote style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0=
cm 0cm 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New=
 Roman","serif"'><o:p>&nbsp;</o:p></span></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span style=3D'font-=
size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size=
:10.0pt;
font-family:"Tahoma","sans-serif"'> mpls-bounces@ietf.org
[mailto:mpls-bounces@ietf.org] <b>On Behalf Of </b>Alexander Vainshtein<br>
<b>Sent:</b> Monday, July 26, 2010 9:57 AM<br>
<b>To:</b> Sriganesh Kini<br>
<b>Cc:</b> mpls@ietf.org<br>
<b>Subject:</b> [mpls] Scalability of the &quot;effective FRR&quot; approac=
h in
draft-kini-mpls-ring-frr-facility-backup-00.txt</span><span style=3D'font-s=
ize:
12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>Sriganesh and all,<o:=
p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>If I understood you
correctly, your proposal requires a dedicated backup tunnel for all LSPs wi=
th
the given {head-end, tail-end} pair of LSRs in the ring. (Regular facility =
FRR
requires just two backup tunnels).<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'>If this understanding=
 is
correct, this looks to like a serious scalability issue with your approach.=
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></sp=
an></p>

<p class=3DMsoNormal>Regards,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</blockquote>

</div>

</body>

</html>

--_000_A3C5DF08D38B6049839A6F553B331C76D5BB4A3F91ILPTMAIL02eci_--

From david.i.allan@ericsson.com  Tue Jul 27 00:24:25 2010
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 327F13A69E7; Tue, 27 Jul 2010 00:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.07
X-Spam-Level: 
X-Spam-Status: No, score=-3.07 tagged_above=-999 required=5 tests=[AWL=-0.471,  BAYES_00=-2.599]
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 QYgah0bMlkOL; Tue, 27 Jul 2010 00:24:24 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 4F2F93A67B1; Tue, 27 Jul 2010 00:24:24 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6R7OjSf006703 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Jul 2010 02:24:45 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 27 Jul 2010 03:24:45 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Date: Tue, 27 Jul 2010 03:24:42 -0400
Thread-Topic: Issues with  draft-ietf-mplt-tp-cc-cv-rdi-01 relating to becoming a WG document...
Thread-Index: AcrxD6Z+vBOT7+WnQ7iJGHfUbfhhEwGXqMCwDXsq7UA=
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51AE5193C2@EUSAACMS0703.eamcs.ericsson.se>
References: <4BE95E75.9040406@pi.nu> <15740615FC9674499FBCE797B011623F0A42BBC0@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
In-Reply-To: <15740615FC9674499FBCE797B011623F0A42BBC0@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [mpls] Issues with draft-ietf-mplt-tp-cc-cv-rdi-01 relating to becoming a WG document...
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 07:24:25 -0000

Hi

The existence of unresolved comments was raised yesterday. I thought the co=
mments raised had been dealt with at the time by a post from co-author John=
 Drake.....

Apparently that must have been missed, Here is a reiteration....

The issues raised were:

1) running BFD at a fixed operator's configurable rate.
Nothing in the draft precludes this.

2) Unidirectional path support
It is noted as FFS and dependent on a uni-directional BFD solution which wo=
uld involve reviving the p2mp BFD draft. As adopting as a WG document is in=
dication of intent to progress and finish the work, not a statement of comp=
leteness, and use of BFD is consistent with existing agreements on how to p=
roceed, although a legit concern I'd assume it is not gating.=20

3) One mechanism that can work independently from the protection switching =
configuration.
This comment was addressed as the modes (BFD as it exists, and BFD as exten=
ded for TP) have been decoupled from any suggestion of use cases.

Based on comments yesterday at the mike and on the list in the past, I'd as=
sume the issue folks actually have is that BFD is a superset of the require=
d functionality. That comes with the territory. We will have a "profile" of=
 BFD just like we have a "profile" of MPLS. It is not clear to me that this=
 is well understood.

Is there anything else that was missed?
Cheers
Dave


From sriganesh.kini@ericsson.com  Tue Jul 27 00:28:05 2010
Return-Path: <sriganesh.kini@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBDC13A6A38 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 00:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.265
X-Spam-Level: 
X-Spam-Status: No, score=-3.265 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, HTML_MESSAGE=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 lh-PjO4ic2PO for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 00:27:59 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 1D0583A69F9 for <mpls@ietf.org>; Tue, 27 Jul 2010 00:27:59 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6R7S92N006787 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Jul 2010 02:28:14 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 27 Jul 2010 03:28:09 -0400
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Date: Tue, 27 Jul 2010 03:28:08 -0400
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaAABzm8kAAAGaFoA==
Message-ID: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80E82@EUSAACMS0703.eamcs.ericsson.se>
References: <A3C5DF08D38B6049839A6F553B331C76D5BB4A3ED3@ILPTMAIL02.ecitele.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80AFB@EUSAACMS0703.eamcs.ericsson.se> <A3C5DF08D38B6049839A6F553B331C76D5BB4A3F91@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D5BB4A3F91@ILPTMAIL02.ecitele.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5A5E55DF96F73844AF7DFB0F48721F0F567DB80E82EUSAACMS0703e_"
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 07:28:06 -0000

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

Sasha, you are welcome.

It should be noted that path computation for e-backup is trivial when route=
d along the backup. That should not impact operational experience. Setup/ma=
intenance of e-backup should be fairly straightforward. It would be helpful=
 if you can quantify a 'proliferation'.

Bandwidth can be shared between the e-backup and the backup tunnel. When th=
e e-backup is routed along the backup, there should not be any extra bandwi=
dth consumed compared to [MPLS-FRR]. The benefit is that the problematic U-=
turn goes away.

Thanks

- Sri



________________________________
From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
Sent: Monday, July 26, 2010 11:55 PM
To: Sriganesh Kini
Cc: mpls@ietf.org
Subject: RE: [mpls] Scalability of the "effective FRR" approach in draft-ki=
ni-mpls-ring-frr-facility-backup-00.txt

Sri,
Lots of thanks for a prompt response. It seems that we more or less agree o=
n the facts (proliferation of e-backup LSPs) but we differ in interpreting =
 the impact  of these facts  on the actual operational experience.

However, I'd like to notice that "BW effectiveness" of e-backup LSPs is als=
o somewhat problematic IMO.
Please note that both the regular backup and e-backup bypass tunnels cross =
multiple links that are not involved with the original set of LSPs they are=
 protecting. And they both consume BW on these links. The only difference i=
s that they are competing for BW with other LSPs, not with ones they are pr=
otecting. But the overall effect is exactly the same IMO.

My 2c,
     Sasha

From: Sriganesh Kini [mailto:sriganesh.kini@ericsson.com]
Sent: Monday, July 26, 2010 8:01 PM
To: Alexander Vainshtein
Cc: mpls@ietf.org
Subject: RE: [mpls] Scalability of the "effective FRR" approach in draft-ki=
ni-mpls-ring-frr-facility-backup-00.txt

Sasha,

As you noted the e-backup tunnel protects all LSPs that have a common {head=
-end, tail-end} pair. More precisely, the e-backup can be shared to protect=
 all LSPs that have a common {ring-ingress-LSR, ring-egress-LSR} pair (that=
 is path is disjoint with the e-backup).

If I understood correctly your concern is about the number of number of e-b=
ackup tunnels?

E-backup tunnels should be setup based on protected LSP's {ring-ingress, ri=
ng-egress} LSRs. Consider a typical case where in a ring, there is a 'ring-=
head-end' and LSPs are setup from other LSRs on the ring to the 'ring-head-=
end'. An e-backup should be setup from each LSR on the ring to the 'ring-he=
ad-end'. This is order(n).

Even for cases where protected LSPs have many possible combinations for {ri=
ng-ingress, ring-egress}, for typical ring sizes, the number of tunnels req=
uired should not be a concern for today's implementations.

Also, in many topologies an LSR that is purely a transit for protected LSPs=
, does not have to originate any e-backup.

Thanks

- Sri
PS: Regular facility FRR requires more that two backup tunnels, depending o=
n what is being protected.

________________________________
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Ale=
xander Vainshtein
Sent: Monday, July 26, 2010 9:57 AM
To: Sriganesh Kini
Cc: mpls@ietf.org
Subject: [mpls] Scalability of the "effective FRR" approach in draft-kini-m=
pls-ring-frr-facility-backup-00.txt
Sriganesh and all,
If I understood you correctly, your proposal requires a dedicated backup tu=
nnel for all LSPs with the given {head-end, tail-end} pair of LSRs in the r=
ing. (Regular facility FRR requires just two backup tunnels).
If this understanding is correct, this looks to like a serious scalability =
issue with your approach.

Regards,
     Sasha


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20
"urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20
"urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =3D=
=20
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =3D=20
"urn:schemas-microsoft-com:office:odc" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20
"http://www.w3.org/TR/REC-html40" xmlns:q =3D=20
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =3D=20
"http://microsoft.com/officenet/conferencing" XMLNS:D =3D "DAV:" XMLNS:Repl=
 =3D=20
"http://schemas.microsoft.com/repl/" xmlns:mt =3D=20
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =3D=20
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =3D=20
"http://www.passport.com/NameSpace.xsd" xmlns:ois =3D=20
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20
"http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20
"http://www.w3.org/2001/XMLSchema" xmlns:sub =3D=20
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =3D=
=20
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =3D=20
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =3D=20
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =3D=20
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =3D=20
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =3D=20
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =3D=20
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =3D=20
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =3D=20
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =3D=20
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mv=
er =3D=20
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
=3D=20
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =3D=20
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =3D=
=20
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
=3D=20
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =3D=
=20
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksServ=
ice"=20
XMLNS:Z =3D "urn:schemas-microsoft-com:" xmlns:st =3D "=01"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18470" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt 72.0pt 90.=
0pt; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: "Times =
New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: auto; mso-m=
argin-bottom-alt: auto
}
SPAN.EmailStyle17 {
	FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: "=
Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle19 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso=
nal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D306290007-27072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Sasha, you are welcome.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D306290007-27072010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>It=20
should be noted that path computation for e-backup is trivial when routed a=
long=20
the backup. That should not&nbsp;impact&nbsp;operational experience.=20
Setup/maintenance&nbsp;of e-backup should be&nbsp;fairly straightforward. I=
t=20
would be helpful if you can&nbsp;quantify a 'proliferation'.</FONT></SPAN><=
/DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D306290007-27072010><FONT face=3DArial color=3D#0000ff=20
size=3D2>Bandwidth&nbsp;can be&nbsp;shared between the e-backup and the bac=
kup=20
tunnel.&nbsp;When the e-backup is routed along the backup, there should not=
 be=20
any extra bandwidth consumed compared to [MPLS-FRR]. The benefit is that th=
e=20
problematic U-turn goes away.</FONT></SPAN></DIV>
<DIV><SPAN class=3D306290007-27072010><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D306290007-27072010><FONT face=3DArial color=3D#0000ff=20
size=3D2>Thanks</FONT></SPAN></DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>- Sri</FONT></SPAN> </P>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
  [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, July 2=
6,=20
  2010 11:55 PM<BR><B>To:</B> Sriganesh Kini<BR><B>Cc:</B>=20
  mpls@ietf.org<BR><B>Subject:</B> RE: [mpls] Scalability of the "effective=
 FRR"=20
  approach in=20
  draft-kini-mpls-ring-frr-facility-backup-00.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DWordSection1>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Sri,<o:p></o:p></SPAN=
></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Lots of thanks for a =
prompt=20
  response. It seems that we more or less agree on the facts (proliferation=
 of=20
  e-backup LSPs) but we differ in interpreting &nbsp;the impact &nbsp;of th=
ese=20
  facts &nbsp;on the actual operational experience.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p>&nbsp;</o:p></SP=
AN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">However, I&#8217;d li=
ke to notice=20
  that &#8220;BW effectiveness&#8221; of e-backup LSPs is also somewhat pro=
blematic=20
  IMO.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Please note that both=
 the=20
  regular backup and e-backup bypass tunnels cross multiple links that are =
not=20
  involved with the original set of LSPs they are protecting. And they both=
=20
  consume BW on these links. The only difference is that they are competing=
 for=20
  BW with other LSPs, not with ones they are protecting. But the overall ef=
fect=20
  is exactly the same IMO.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p>&nbsp;</o:p></SP=
AN></P>
  <DIV>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">My 2c,<o:p></o:p></SP=
AN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">&nbsp;&nbsp;&nbsp;&nb=
sp;=20
  Sasha<o:p></o:p></SPAN></P></DIV>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p>&nbsp;</o:p></SP=
AN></P>
  <DIV>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4=
df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium n=
one; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal><B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN=
></B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Sriganesh =
Kini=20
  [mailto:sriganesh.kini@ericsson.com] <BR><B>Sent:</B> Monday, July 26, 20=
10=20
  8:01 PM<BR><B>To:</B> Alexander Vainshtein<BR><B>Cc:</B>=20
  mpls@ietf.org<BR><B>Subject:</B> RE: [mpls] Scalability of the "effective=
 FRR"=20
  approach in=20
  draft-kini-mpls-ring-frr-facility-backup-00.txt<o:p></o:p></SPAN></P></DI=
V></DIV>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"=
>Sasha,</SPAN><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></=
o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">&nbsp;<=
o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"=
>As you=20
  noted the&nbsp;e-backup tunnel protects all LSPs that have a common {head=
-end,=20
  tail-end} pair. More precisely, the e-backup can be shared to protect&nbs=
p;all=20
  LSPs that have a common {ring-ingress-LSR, ring-egress-LSR} pair&nbsp;(th=
at is=20
  path&nbsp;is disjoint with the e-backup).</SPAN><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></=
o:p></SPAN></P>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">&nbsp;<=
o:p></o:p></SPAN></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"=
>If I=20
  understood correctly your concern is about the number of number of e-back=
up=20
  tunnels?</SPAN><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></=
o:p></SPAN></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">&nbsp;<=
o:p></o:p></SPAN></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"=
>E-backup=20
  tunnels should be setup based on protected LSP's {ring-ingress, ring-egre=
ss}=20
  LSRs. Consider a typical case where in a ring, there is a 'ring-head-end'=
 and=20
  LSPs are setup from other LSRs on the ring to the 'ring-head-end'. An e-b=
ackup=20
  should be setup from each LSR on the ring to the 'ring-head-end'. This is=
=20
  order(n). </SPAN><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></=
o:p></SPAN></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">&nbsp;<=
o:p></o:p></SPAN></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"=
>Even&nbsp;for=20
  cases where protected LSPs&nbsp;have&nbsp;many possible combinations&nbsp=
;for=20
  {ring-ingress, ring-egress},&nbsp;for typical ring sizes, the number=20
  of&nbsp;tunnels required&nbsp;should not be a concern=20
  for&nbsp;today's&nbsp;implementations.</SPAN><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></=
o:p></SPAN></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">&nbsp;<=
o:p></o:p></SPAN></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"=
>Also,=20
  in many topologies&nbsp;an LSR that is purely a transit for protected=20
  LSPs,&nbsp;does not have to originate any e-backup.</SPAN><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></=
o:p></SPAN></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">&nbsp;<=
o:p></o:p></SPAN></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"=
>Thanks</SPAN><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></=
o:p></SPAN></P></DIV>
  <P><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">-=20
  Sri</SPAN> <o:p></o:p></P>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"=
>PS:=20
  Regular facility FRR requires more that two backup tunnels, depending on =
what=20
  is being protected.</SPAN><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></=
o:p></SPAN></P></DIV>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: mediu=
m none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0cm; MARGIN: 5pt 0cm 5pt 3.75pt;=
 BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0cm; BORDER-BOTTOM: medium non=
e">
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p>=
&nbsp;</o:p></SPAN></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><SPA=
N=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
    <HR align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SP=
AN></B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
    mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <B>On Behalf Of=20
    </B>Alexander Vainshtein<BR><B>Sent:</B> Monday, July 26, 2010 9:57=20
    AM<BR><B>To:</B> Sriganesh Kini<BR><B>Cc:</B>=20
    mpls@ietf.org<BR><B>Subject:</B> [mpls] Scalability of the "effective F=
RR"=20
    approach in draft-kini-mpls-ring-frr-facility-backup-00.txt</SPAN><SPAN=
=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p>=
</o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 12pt">Sriganesh and=20
    all,<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 12pt">If I understood yo=
u=20
    correctly, your proposal requires a dedicated backup tunnel for all LSP=
s=20
    with the given {head-end, tail-end} pair of LSRs in the ring. (Regular=
=20
    facility FRR requires just two backup tunnels).<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 12pt">If this understand=
ing is=20
    correct, this looks to like a serious scalability issue with your=20
    approach.<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></P>
    <P class=3DMsoNormal>Regards,<o:p></o:p></P>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o:p></o:p></P>
    <P=20
class=3DMsoNormal><o:p>&nbsp;</o:p></P></BLOCKQUOTE></DIV></BLOCKQUOTE></BO=
DY></HTML>

--_000_5A5E55DF96F73844AF7DFB0F48721F0F567DB80E82EUSAACMS0703e_--

From sboutros@cisco.com  Tue Jul 27 00:39:44 2010
Return-Path: <sboutros@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B95D83A6A38 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 00:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.374
X-Spam-Level: 
X-Spam-Status: No, score=-9.374 tagged_above=-999 required=5 tests=[AWL=1.225,  BAYES_00=-2.599, 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 JwZArUY9d94j for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 00:39:39 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id DF2273A6AB1 for <mpls@ietf.org>; Tue, 27 Jul 2010 00:39:38 -0700 (PDT)
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: Av0EAKcqTkyrR7Hu/2dsb2JhbACGMZk0caVhm0KFNgSECYcZ
X-IronPort-AV: E=Sophos;i="4.55,266,1278288000"; d="scan'208";a="163348036"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 27 Jul 2010 07:39:47 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o6R7dlcG002733; Tue, 27 Jul 2010 07:39:47 GMT
Received: from xfe-sjc-232.amer.cisco.com ([128.107.191.79]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 27 Jul 2010 00:39:46 -0700
Received: from sboutros-wxp02.ciswco.com ([10.21.127.172]) by xfe-sjc-232.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 27 Jul 2010 00:39:45 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 27 Jul 2010 00:39:11 -0700
To: "BUSI ITALO" <Italo.Busi@alcatel-lucent.com>
From: Sami Boutros <sboutros@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <XFE-SJC-232YoaT0fLG0000004a@xfe-sjc-232.amer.cisco.com>
X-OriginalArrivalTime: 27 Jul 2010 07:39:46.0324 (UTC) FILETIME=[E2AB3D40:01CB2D5E]
Cc: mpls@ietf.org
Subject: [mpls] Your comment to the draft-boutros-mpls-lsp-ping-ttl-tlv presentation yesterday in the MPLS WG.
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 07:39:44 -0000

Hi Italo,

The draft is about a new LSP Ping TLV that can be used to allow the 
verification of a segment of a MS-PW or a bidir co-routed LSP.

The mechanisms will be used for LSP Ping on demand CV only, i.e. this 
is not going to be used by all OAM functions.

Given that, if the # of hops in a given segment change due to FRR, 
then there will either be no reply for the LSP Ping echo request, or 
a reply will come from the wrong node, in either case the user 
issuing the on demand CV can simply re-send the request with the TTL 
TLV specifying the new # of hops.

Thanks,

Sami


From eosborne@cisco.com  Tue Jul 27 01:18:38 2010
Return-Path: <eosborne@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7E283A6B8C for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 01:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 PGGbYjv7CzWS for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 01:18:37 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 651413A6AB1 for <mpls@ietf.org>; Tue, 27 Jul 2010 01:18:37 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEABczTkytJV2Y/2dsb2JhbACfZXGlOJtFhTYEhAmHGQwB
X-IronPort-AV: E=Sophos;i="4.55,266,1278288000"; d="scan'208";a="139635680"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rtp-iport-2.cisco.com with ESMTP; 27 Jul 2010 08:18:58 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id o6R8IwfC002577;  Tue, 27 Jul 2010 08:18:58 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 27 Jul 2010 03:18:58 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Jul 2010 03:18:56 -0500
Message-ID: <D29E470202D67745B61059870F433B5402511686@XMB-RCD-202.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Scalability of the "effective FRR" approach indraft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaAABzm8kAAAGaFoAAB6yoA
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Sriganesh Kini" <sriganesh.kini@ericsson.com>, "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 27 Jul 2010 08:18:58.0417 (UTC) FILETIME=[5CA02610:01CB2D64]
Cc: mpls@ietf.org
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 08:18:38 -0000

I'm afraid I don't quite see the severity of the u-turn.  Yes, it's
suboptimal.  But how long does the condition last?  All implementations
I'm familiar with will rebuild the new primary LSP (the L9->L6 LSP, in
your example) in O(seconds), so the suboptimal condition is pretty
transient.  Your solution seems like quite a lot of work (BFD, e-backup
tunnels) for a few seconds of gain.

Also, it's not clear to me what happens in the time after the failure
but before fast-alert messages are processed at the u-PLR.  Does the PLR
drop traffic until then?  Does it do inefficient backup?  Is this an
implementations-specific decision? =20

Thirdly, I'm not sure how generalizable this solution is to a mesh
topology.  While it will certainly work just as well there as in a ring,
it is entirely possible (and in my experience quite common) that the
backup tunnel does not overlap with many of the tunnels which it is
protecting, and thus you do not have a problem to solve.  As you are
solving a problem that is IMHO predominant only in ring topologies, this
mechanism is more of a specialized, ring-optimized tool than a
general-purpose thing.



eric


> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
Of
> Sriganesh Kini
> Sent: Tuesday, July 27, 2010 9:28 AM
> To: Alexander Vainshtein
> Cc: mpls@ietf.org
> Subject: Re: [mpls] Scalability of the "effective FRR" approach in
draft-kini-
> mpls-ring-frr-facility-backup-00.txt
>=20
> Sasha, you are welcome.
>=20
> It should be noted that path computation for e-backup is trivial when
routed
> along the backup. That should not impact operational experience.
> Setup/maintenance of e-backup should be fairly straightforward. It
would be
> helpful if you can quantify a 'proliferation'.
>=20
> Bandwidth can be shared between the e-backup and the backup tunnel.
> When the e-backup is routed along the backup, there should not be any
> extra bandwidth consumed compared to [MPLS-FRR]. The benefit is that
the
> problematic U-turn goes away.
>=20
> Thanks
>=20
> - Sri
>=20
>=20
>=20
>=20
> ________________________________
>=20
> 	From: Alexander Vainshtein
> [mailto:Alexander.Vainshtein@ecitele.com]
> 	Sent: Monday, July 26, 2010 11:55 PM
> 	To: Sriganesh Kini
> 	Cc: mpls@ietf.org
> 	Subject: RE: [mpls] Scalability of the "effective FRR" approach
in
> draft-kini-mpls-ring-frr-facility-backup-00.txt
>=20
>=20
>=20
> 	Sri,
>=20
> 	Lots of thanks for a prompt response. It seems that we more or
less
> agree on the facts (proliferation of e-backup LSPs) but we differ in
> interpreting  the impact  of these facts  on the actual operational
experience.
>=20
>=20
>=20
> 	However, I'd like to notice that "BW effectiveness" of e-backup
LSPs
> is also somewhat problematic IMO.
>=20
> 	Please note that both the regular backup and e-backup bypass
> tunnels cross multiple links that are not involved with the original
set of LSPs
> they are protecting. And they both consume BW on these links. The only
> difference is that they are competing for BW with other LSPs, not with
ones
> they are protecting. But the overall effect is exactly the same IMO.
>=20
>=20
>=20
> 	My 2c,
>=20
> 	     Sasha
>=20
>=20
>=20
> 	From: Sriganesh Kini [mailto:sriganesh.kini@ericsson.com]
> 	Sent: Monday, July 26, 2010 8:01 PM
> 	To: Alexander Vainshtein
> 	Cc: mpls@ietf.org
> 	Subject: RE: [mpls] Scalability of the "effective FRR" approach
in
> draft-kini-mpls-ring-frr-facility-backup-00.txt
>=20
>=20
>=20
> 	Sasha,
>=20
>=20
>=20
> 	As you noted the e-backup tunnel protects all LSPs that have a
> common {head-end, tail-end} pair. More precisely, the e-backup can be
> shared to protect all LSPs that have a common {ring-ingress-LSR,
ring-egress-
> LSR} pair (that is path is disjoint with the e-backup).
>=20
>=20
>=20
> 	If I understood correctly your concern is about the number of
> number of e-backup tunnels?
>=20
>=20
>=20
> 	E-backup tunnels should be setup based on protected LSP's {ring-
> ingress, ring-egress} LSRs. Consider a typical case where in a ring,
there is a
> 'ring-head-end' and LSPs are setup from other LSRs on the ring to the
'ring-
> head-end'. An e-backup should be setup from each LSR on the ring to
the
> 'ring-head-end'. This is order(n).
>=20
>=20
>=20
> 	Even for cases where protected LSPs have many possible
> combinations for {ring-ingress, ring-egress}, for typical ring sizes,
the number
> of tunnels required should not be a concern for today's
implementations.
>=20
>=20
>=20
> 	Also, in many topologies an LSR that is purely a transit for
protected
> LSPs, does not have to originate any e-backup.
>=20
>=20
>=20
> 	Thanks
>=20
> 	- Sri
>=20
> 	PS: Regular facility FRR requires more that two backup tunnels,
> depending on what is being protected.
>=20
>=20
>=20
>=20
> ________________________________
>=20
>=20
> 		From: mpls-bounces@ietf.org [mailto:mpls-
> bounces@ietf.org] On Behalf Of Alexander Vainshtein
> 		Sent: Monday, July 26, 2010 9:57 AM
> 		To: Sriganesh Kini
> 		Cc: mpls@ietf.org
> 		Subject: [mpls] Scalability of the "effective FRR"
approach in
> draft-kini-mpls-ring-frr-facility-backup-00.txt
>=20
> 		Sriganesh and all,
>=20
> 		If I understood you correctly, your proposal requires a
> dedicated backup tunnel for all LSPs with the given {head-end,
tail-end} pair
> of LSRs in the ring. (Regular facility FRR requires just two backup
tunnels).
>=20
> 		If this understanding is correct, this looks to like a
serious
> scalability issue with your approach.
>=20
>=20
>=20
> 		Regards,
>=20
> 		     Sasha
>=20
>=20


From italo.busi@alcatel-lucent.com  Tue Jul 27 01:43:42 2010
Return-Path: <italo.busi@alcatel-lucent.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E26403A6BA4 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 01:43:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=-1.200, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 lXRJO9BXKqEI for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 01:43:40 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 301DE3A6A1F for <mpls@ietf.org>; Tue, 27 Jul 2010 01:43:38 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o6R8hogP010129 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 27 Jul 2010 10:43:51 +0200
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.39]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Tue, 27 Jul 2010 10:43:50 +0200
From: "BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com>
To: Sami Boutros <sboutros@cisco.com>
Date: Tue, 27 Jul 2010 10:43:49 +0200
Thread-Topic: Your comment to the draft-boutros-mpls-lsp-ping-ttl-tlv presentation yesterday in the MPLS WG.
Thread-Index: AcstXu/4DZ4c6/o5RAaRTTTmSWWFQAACNb3g
Message-ID: <15740615FC9674499FBCE797B011623F0C1159D9@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <XFE-SJC-232YoaT0fLG0000004a@xfe-sjc-232.amer.cisco.com>
In-Reply-To: <XFE-SJC-232YoaT0fLG0000004a@xfe-sjc-232.amer.cisco.com>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: it-IT, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: [mpls] R: Your comment to the draft-boutros-mpls-lsp-ping-ttl-tlv presentation yesterday in the MPLS WG.
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 08:43:42 -0000

Sami,

Your reply fully address my concerns ;-)

Thanks, Italo

> -----Messaggio originale-----
> Da: Sami Boutros [mailto:sboutros@cisco.com]
> Inviato: marted=EC 27 luglio 2010 9.39
> A: BUSI, ITALO (ITALO)
> Cc: mpls@ietf.org
> Oggetto: Your comment to the draft-boutros-mpls-lsp-ping-ttl-tlv
> presentation yesterday in the MPLS WG.
>=20
> Hi Italo,
>=20
> The draft is about a new LSP Ping TLV that can be used to allow the
> verification of a segment of a MS-PW or a bidir co-routed LSP.
>=20
> The mechanisms will be used for LSP Ping on demand CV only, i.e. this
> is not going to be used by all OAM functions.
>=20
> Given that, if the # of hops in a given segment change due to FRR,
> then there will either be no reply for the LSP Ping echo request, or
> a reply will come from the wrong node, in either case the user
> issuing the on demand CV can simply re-send the request with the TTL
> TLV specifying the new # of hops.
>=20
> Thanks,
>=20
> Sami


From sriganesh.kini@ericsson.com  Tue Jul 27 01:51:49 2010
Return-Path: <sriganesh.kini@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB0633A6859 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 01:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[AWL=1.501,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 A75yaGr-NNqS for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 01:51:47 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 352773A6BA4 for <mpls@ietf.org>; Tue, 27 Jul 2010 01:51:47 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o6R90bDJ017479; Tue, 27 Jul 2010 04:00:37 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 27 Jul 2010 04:51:36 -0400
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Date: Tue, 27 Jul 2010 04:51:35 -0400
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaAABzm8kAAAGaFoAAB6yoAAADgilA=
Message-ID: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80E8F@EUSAACMS0703.eamcs.ericsson.se>
References: <D29E470202D67745B61059870F433B5402511686@XMB-RCD-202.cisco.com>
In-Reply-To: <D29E470202D67745B61059870F433B5402511686@XMB-RCD-202.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 08:51:49 -0000

Eric, pls see inline @ [Sri]

- Sri
=20

> -----Original Message-----
> From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com]=20
> Sent: Tuesday, July 27, 2010 1:19 AM
> To: Sriganesh Kini; Alexander Vainshtein
> Cc: mpls@ietf.org
> Subject: RE: [mpls] Scalability of the "effective FRR"=20
> approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
>=20
> I'm afraid I don't quite see the severity of the u-turn. =20
> Yes, it's suboptimal.  But how long does the condition last? =20
> All implementations I'm familiar with will rebuild the new=20
> primary LSP (the L9->L6 LSP, in your example) in O(seconds),=20
> so the suboptimal condition is pretty transient.  Your=20
> solution seems like quite a lot of work (BFD, e-backup
> tunnels) for a few seconds of gain.

This solution aims for characteristics as close to MPLS-FRR when repair is =
done at an LSR adjacent to the failure. MPLS-FRR is used for networks requi=
ring failure recovery with very low traffic loss (typically sub 50msec). If=
 the network you are considering is tolerant to several seconds of traffic =
loss, plain old IGP convergence should be more than enough.

>=20
> Also, it's not clear to me what happens in the time after the=20
> failure but before fast-alert messages are processed at the=20
> u-PLR.  Does the PLR drop traffic until then?  Does it do=20
> inefficient backup?  Is this an implementations-specific decision? =20

Typically a protection switch at PLR should result in lower overall loss th=
an completely dropping traffic. If there are very specific conditions where=
 completely dropping traffic is more advantageous, it may be an additional =
behavior.

>=20
> Thirdly, I'm not sure how generalizable this solution is to a=20
> mesh topology.  While it will certainly work just as well=20
> there as in a ring, it is entirely possible (and in my=20
> experience quite common) that the backup tunnel does not=20
> overlap with many of the tunnels which it is protecting, and=20
> thus you do not have a problem to solve.  As you are solving=20
> a problem that is IMHO predominant only in ring topologies,=20
> this mechanism is more of a specialized, ring-optimized tool=20
> than a general-purpose thing.

The draft makes a statement about applicability to general topologies and a=
s you correctly noted it works just as well. How much of overlap is there w=
ill vary from one network to another.

>=20
>=20
>=20
> eric
>=20
>=20
> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of
> > Sriganesh Kini
> > Sent: Tuesday, July 27, 2010 9:28 AM
> > To: Alexander Vainshtein
> > Cc: mpls@ietf.org
> > Subject: Re: [mpls] Scalability of the "effective FRR" approach in
> draft-kini-
> > mpls-ring-frr-facility-backup-00.txt
> >=20
> > Sasha, you are welcome.
> >=20
> > It should be noted that path computation for e-backup is=20
> trivial when
> routed
> > along the backup. That should not impact operational experience.
> > Setup/maintenance of e-backup should be fairly straightforward. It
> would be
> > helpful if you can quantify a 'proliferation'.
> >=20
> > Bandwidth can be shared between the e-backup and the backup tunnel.
> > When the e-backup is routed along the backup, there should=20
> not be any=20
> > extra bandwidth consumed compared to [MPLS-FRR]. The benefit is that
> the
> > problematic U-turn goes away.
> >=20
> > Thanks
> >=20
> > - Sri
> >=20
> >=20
> >=20
> >=20
> > ________________________________
> >=20
> > 	From: Alexander Vainshtein
> > [mailto:Alexander.Vainshtein@ecitele.com]
> > 	Sent: Monday, July 26, 2010 11:55 PM
> > 	To: Sriganesh Kini
> > 	Cc: mpls@ietf.org
> > 	Subject: RE: [mpls] Scalability of the "effective FRR" approach
> in
> > draft-kini-mpls-ring-frr-facility-backup-00.txt
> >=20
> >=20
> >=20
> > 	Sri,
> >=20
> > 	Lots of thanks for a prompt response. It seems that we more or
> less
> > agree on the facts (proliferation of e-backup LSPs) but we=20
> differ in=20
> > interpreting  the impact  of these facts  on the actual operational
> experience.
> >=20
> >=20
> >=20
> > 	However, I'd like to notice that "BW effectiveness" of e-backup
> LSPs
> > is also somewhat problematic IMO.
> >=20
> > 	Please note that both the regular backup and e-backup=20
> bypass tunnels=20
> > cross multiple links that are not involved with the original
> set of LSPs
> > they are protecting. And they both consume BW on these=20
> links. The only=20
> > difference is that they are competing for BW with other=20
> LSPs, not with
> ones
> > they are protecting. But the overall effect is exactly the same IMO.
> >=20
> >=20
> >=20
> > 	My 2c,
> >=20
> > 	     Sasha
> >=20
> >=20
> >=20
> > 	From: Sriganesh Kini [mailto:sriganesh.kini@ericsson.com]
> > 	Sent: Monday, July 26, 2010 8:01 PM
> > 	To: Alexander Vainshtein
> > 	Cc: mpls@ietf.org
> > 	Subject: RE: [mpls] Scalability of the "effective FRR" approach
> in
> > draft-kini-mpls-ring-frr-facility-backup-00.txt
> >=20
> >=20
> >=20
> > 	Sasha,
> >=20
> >=20
> >=20
> > 	As you noted the e-backup tunnel protects all LSPs that=20
> have a common=20
> > {head-end, tail-end} pair. More precisely, the e-backup can=20
> be shared=20
> > to protect all LSPs that have a common {ring-ingress-LSR,
> ring-egress-
> > LSR} pair (that is path is disjoint with the e-backup).
> >=20
> >=20
> >=20
> > 	If I understood correctly your concern is about the=20
> number of number=20
> > of e-backup tunnels?
> >=20
> >=20
> >=20
> > 	E-backup tunnels should be setup based on protected=20
> LSP's {ring-=20
> > ingress, ring-egress} LSRs. Consider a typical case where in a ring,
> there is a
> > 'ring-head-end' and LSPs are setup from other LSRs on the=20
> ring to the
> 'ring-
> > head-end'. An e-backup should be setup from each LSR on the ring to
> the
> > 'ring-head-end'. This is order(n).
> >=20
> >=20
> >=20
> > 	Even for cases where protected LSPs have many possible=20
> combinations=20
> > for {ring-ingress, ring-egress}, for typical ring sizes,
> the number
> > of tunnels required should not be a concern for today's
> implementations.
> >=20
> >=20
> >=20
> > 	Also, in many topologies an LSR that is purely a transit for
> protected
> > LSPs, does not have to originate any e-backup.
> >=20
> >=20
> >=20
> > 	Thanks
> >=20
> > 	- Sri
> >=20
> > 	PS: Regular facility FRR requires more that two backup tunnels,=20
> > depending on what is being protected.
> >=20
> >=20
> >=20
> >=20
> > ________________________________
> >=20
> >=20
> > 		From: mpls-bounces@ietf.org [mailto:mpls-=20
> bounces@ietf.org] On=20
> > Behalf Of Alexander Vainshtein
> > 		Sent: Monday, July 26, 2010 9:57 AM
> > 		To: Sriganesh Kini
> > 		Cc: mpls@ietf.org
> > 		Subject: [mpls] Scalability of the "effective FRR"
> approach in
> > draft-kini-mpls-ring-frr-facility-backup-00.txt
> >=20
> > 		Sriganesh and all,
> >=20
> > 		If I understood you correctly, your proposal=20
> requires a dedicated=20
> > backup tunnel for all LSPs with the given {head-end,
> tail-end} pair
> > of LSRs in the ring. (Regular facility FRR requires just two backup
> tunnels).
> >=20
> > 		If this understanding is correct, this looks to like a
> serious
> > scalability issue with your approach.
> >=20
> >=20
> >=20
> > 		Regards,
> >=20
> > 		     Sasha
> >=20
> >=20
>=20
> =

From chair@ietf.org  Tue Jul 27 02:07:02 2010
Return-Path: <chair@ietf.org>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 866163A6AAA; Tue, 27 Jul 2010 02:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.382
X-Spam-Level: 
X-Spam-Status: No, score=-102.382 tagged_above=-999 required=5 tests=[AWL=0.217, 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 NgB+ZbsZA4ko; Tue, 27 Jul 2010 02:07:01 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 833D93A6A14; Tue, 27 Jul 2010 02:07:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 9E998E08C0; Tue, 27 Jul 2010 02:07:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4geYPXmxDc2j; Tue, 27 Jul 2010 02:07:23 -0700 (PDT)
Received: from [130.129.34.235] (dhcp-22eb.meeting.ietf.org [130.129.34.235]) by c1a.amsl.com (Postfix) with ESMTPSA id D39FBE08BD; Tue, 27 Jul 2010 02:07:19 -0700 (PDT)
Message-ID: <4C4EA1C5.30700@ietf.org>
Date: Tue, 27 Jul 2010 05:07:17 -0400
From: IETF Chair <chair@ietf.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, steve.trowbridge@alcatel-lucent.com, malcolm.betts@zte.com.cn, IETF Liaison Statements <statements@ietf.org>, yoichi.maeda@ntt-at.co.jp, rcallon@juniper.net, paf@cisco.com, adrian.farrel@huawei.com, iesg@ietf.org, stbryant@cisco.com
Subject: [mpls] Liaison Statement: Re: Review of draft-ietf-mpls-tp-data-plane-03 (Ref #035.02)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 09:07:02 -0000

Thank you for your liaison COM15-LS207-E (ref 35.01) dated 24-June-2010
providing further review comments on draft-ietf-mpls-tp-data-plane.

This document completed IETF last call on 14-June-2010 and received IETF
consensus. The document was reviewed by the IESG on 17-June-2010 and
received approval for publication subject to some minor modifications.
Documents in the RFC Editor's queue are only open for minor editorial
changes.

We have examined the changes proposed by the ITU-T and have formed the
following view:

Proposed change on page 8:

This change is of technical substance, and cannot be made to a document
in the RFC Editor's Queue.

Proposed change to Section 6:

The terms "peer" and "neighbor" are well understood within the IETF and
do not need further clarification.

The proposed description of the application scenario constitutes a
change of technical substance, and cannot be made to a document in the
RFC Editor's Queue.

If IETF contributors feel that there is an issue to be resolved, there
are two processes that are available to make changes to published RFCs.
One method is to submit an Erratum Notice using the IETF web pages
(http://www.rfc-editor.org/errata.php). The other method is to produce a
revision or modification to the published RFC by submitting an
Internet-Draft and taking it through the IETF consensus process. Both
methods are subject to review before approval.

On behalf of the IESG,
 Russ Housley

From chair@ietf.org  Tue Jul 27 02:18:26 2010
Return-Path: <chair@ietf.org>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B2BF3A6ACC; Tue, 27 Jul 2010 02:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, 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 wENO3ZfQeQ8a; Tue, 27 Jul 2010 02:18:19 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id C39BF3A6A69; Tue, 27 Jul 2010 02:17:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id E76C1E08C0; Tue, 27 Jul 2010 02:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8PoZP1+QtzXA; Tue, 27 Jul 2010 02:18:16 -0700 (PDT)
Received: from [130.129.34.235] (dhcp-22eb.meeting.ietf.org [130.129.34.235]) by c1a.amsl.com (Postfix) with ESMTPSA id 458E6E08AE; Tue, 27 Jul 2010 02:18:13 -0700 (PDT)
Message-ID: <4C4EA452.6030107@ietf.org>
Date: Tue, 27 Jul 2010 05:18:10 -0400
From: IETF Chair <chair@ietf.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, steve.trowbridge@alcatel-lucent.com, malcolm.betts@zte.com.cn, IETF Liaison Statements <statements@ietf.org>, yoichi.maeda@ntt-at.co.jp, rcallon@juniper.net, paf@cisco.com, adrian.farrel@huawei.com, iesg@ietf.org, stbryant@cisco.com
Subject: [mpls] Liaison Statement: LS206 - Review of draft-ietf-mpls-tp-framework-12 (Ref #034.02)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 09:18:26 -0000

Thank you for your liaison COM15-LS206-E, Review of
draft-ietf-mpls-tp-framework-12 (Ref #034.01) dated 24-June-2010.

We regret that the ITU-T was unable to review
draft-ietf-mpls-tp-framework-12 within the requested time. It should be
noted that participants in SG15 had the same amount of time to review
this document as other members of the MPLS-TP design community. The
ITU-T participants were therefore afforded no less privilege in the
review cycle than any other group of participants.

This document completed IETF last call with IETF consensus on
21-April-2010. It was reviewed by the IESG on 20-May-2010 and was
approved for publication as an RFC on 24-May-2010. In response to the
requirements of the ITU-T, this document was expedited in the RFC
Editor's queue and was published as RFC 5921. The text of the published
RFC cannot be changed.

We note that the ITU-T's requests (cf. COM15-LS205-E) to expedite the
development of IETF solutions is not consistent with the request for
additional review time. We suggest that the best way to expedite the
MPLS-TP work is through a full involvement with the standards
development process. This will facilitate earlier input to the
documents and mean that the final review can be completed in the time
available.

We understand the requirements under Recommendation A.5 and we encourage
ITU-T participants who are worried about the issues of referenced
documents to become involved in the development of those documents
earlier in the cycle and throughout the IETF process.

This document completed IETF last call with IETF consensus on
21-April-2010. It was reviewed by the IESG on 20-May-2010 and was
approved for publication as an RFC on 24-May-2010. In response to the
requirements of the ITU-T, this document was expedited in the RFC
Editor's queue and was published as RFC 5921. Obviously, the text of the
published RFC cannot be changed.

Regarding your requested changes these were evaluated and processed as
follows:

Section 3.4.3:

The additional text that you propose is a duplication of the previous
sentence where it already says that the UNI is between the CE and the
MPLS-TP network. It was not considered appropriate to make such a change
at this stage in the process.

Figures 3 and 5:

These changes are of technical substance and would have required IETF
consensus to implement. They were not therefore accepted at this stage
in the process.

Section 3.4.5, page 32;
Section 3.7, pages 36 and 37;
Section 3.13, page 45;
Section 3.13, page 46:

These four cases were communicated informally to the responsible IETF
Area Director during your plenary and were included as a late change by
the RFC Editor as they were purely minor editorial in nature. Thus, they
are already included in the published RFC.

If IETF contributors feel that there is an issue to be resolved, there
are two processes that are available to make changes to published RFCs.
One method is to submit an Erratum Notice using the IETF web pages
(http://www.rfc-editor.org/errata.php). The other method is to produce a
revision or modification to the published RFC by submitting an
Internet-Draft and taking it through the IETF consensus process. Both
methods are subject to review before approval.

On behalf of the IESG,
 Russ Housley

From eosborne@cisco.com  Tue Jul 27 02:18:27 2010
Return-Path: <eosborne@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26D963A6BB7 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 02:18:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 ByT-yx3PRq6s for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 02:18:20 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 319853A6BB3 for <mpls@ietf.org>; Tue, 27 Jul 2010 02:17:58 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGNBTkytJV2a/2dsb2JhbACfZXGlIptMhTYEhAmHGQwB
X-IronPort-AV: E=Sophos;i="4.55,267,1278288000"; d="scan'208";a="139611295"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rtp-iport-1.cisco.com with ESMTP; 27 Jul 2010 09:18:19 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id o6R9IJxx029916;  Tue, 27 Jul 2010 09:18:19 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 27 Jul 2010 04:18:19 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Jul 2010 04:18:16 -0500
Message-ID: <D29E470202D67745B61059870F433B5402511689@XMB-RCD-202.cisco.com>
In-Reply-To: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80E8F@EUSAACMS0703.eamcs.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaAABzm8kAAAGaFoAAB6yoAAADgilAAAUKywA==
References: <D29E470202D67745B61059870F433B5402511686@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80E8F@EUSAACMS0703.eamcs.ericsson.se>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Sriganesh Kini" <sriganesh.kini@ericsson.com>, "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 27 Jul 2010 09:18:19.0347 (UTC) FILETIME=[A71AF230:01CB2D6C]
Cc: mpls@ietf.org
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 09:18:28 -0000

Inline with EO#

> -----Original Message-----
> From: Sriganesh Kini [mailto:sriganesh.kini@ericsson.com]
> Sent: Tuesday, July 27, 2010 10:52 AM
> To: Eric Osborne (eosborne); Alexander Vainshtein
> Cc: mpls@ietf.org
> Subject: RE: [mpls] Scalability of the "effective FRR" approach in
draft-kini-
> mpls-ring-frr-facility-backup-00.txt
>=20
> Eric, pls see inline @ [Sri]
>=20
> - Sri
>=20
>=20
> > -----Original Message-----
> > From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com]
> > Sent: Tuesday, July 27, 2010 1:19 AM
> > To: Sriganesh Kini; Alexander Vainshtein
> > Cc: mpls@ietf.org
> > Subject: RE: [mpls] Scalability of the "effective FRR"
> > approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
> >
> > I'm afraid I don't quite see the severity of the u-turn.
> > Yes, it's suboptimal.  But how long does the condition last?
> > All implementations I'm familiar with will rebuild the new primary
LSP
> > (the L9->L6 LSP, in your example) in O(seconds), so the suboptimal
> > condition is pretty transient.  Your solution seems like quite a lot
> > of work (BFD, e-backup
> > tunnels) for a few seconds of gain.
>=20
> This solution aims for characteristics as close to MPLS-FRR when
repair is
> done at an LSR adjacent to the failure. MPLS-FRR is used for networks
> requiring failure recovery with very low traffic loss (typically sub
50msec). If
> the network you are considering is tolerant to several seconds of
traffic loss,
> plain old IGP convergence should be more than enough.

EO#  Yes, I'm familiar with how that works and that's not my point.  In
FRR networks as currently deployed, the timeline goes something like
this:

i) failure happens
ii) PLR kicks in protection.  Traffic is protected, but may (in some
topologies) be routed in the manner you refer to as suboptimal
iii) headend of the protected tunnel is notified of the failure and
reroutes to a new primary path

Elapsed time:
(i) -> (ii)  <=3D50ms
(ii)->(iii) ~=3D O(seconds)

The point I'm making is not that there are O(seconds) of loss, but
O(seconds) of suboptimality.  And I'm questioning whether the amount of
work you're proposing is worth it in order to minimize this O(seconds)
of suboptimality.  If the suboptimality lasted for a long time (minutes?
hours?) I think it may be worth trying to optimize away, but it doesn't
and thus IMHO isn't.

There are also existing mechanisms to minimize the impact of this
suboptimality.  They include proper placement of primary and backup
paths, QoS for congestion control, and path protection.  None of these
are mandatory, but all of them are useful.  To me, this further reduces
the utility of the mechanism you describe.  This is, of course, always
going to be a matter of opinion.

And don't even get me started on "if you don't like how ring networks
behave, don't build ring networks".  That's a whole different topic.



eric

> >
> > Also, it's not clear to me what happens in the time after the
failure
> > but before fast-alert messages are processed at the u-PLR.  Does the
> > PLR drop traffic until then?  Does it do inefficient backup?  Is
this
> > an implementations-specific decision?
>=20
> Typically a protection switch at PLR should result in lower overall
loss than
> completely dropping traffic. If there are very specific conditions
where
> completely dropping traffic is more advantageous, it may be an
additional
> behavior.

OK, so your desire is that the PLR locally (suboptimally) protect
traffic until the u-PLR does its thing.

>=20
> >
> > Thirdly, I'm not sure how generalizable this solution is to a mesh
> > topology.  While it will certainly work just as well there as in a
> > ring, it is entirely possible (and in my experience quite common)
that
> > the backup tunnel does not overlap with many of the tunnels which it
> > is protecting, and thus you do not have a problem to solve.  As you
> > are solving a problem that is IMHO predominant only in ring
> > topologies, this mechanism is more of a specialized, ring-optimized
> > tool than a general-purpose thing.
>=20
> The draft makes a statement about applicability to general topologies
and as
> you correctly noted it works just as well. How much of overlap is
there will
> vary from one network to another.
>=20
> >
> >
> >
> > eric
> >
> >
> > > -----Original Message-----
> > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
Behalf
> > Of
> > > Sriganesh Kini
> > > Sent: Tuesday, July 27, 2010 9:28 AM
> > > To: Alexander Vainshtein
> > > Cc: mpls@ietf.org
> > > Subject: Re: [mpls] Scalability of the "effective FRR" approach in
> > draft-kini-
> > > mpls-ring-frr-facility-backup-00.txt
> > >
> > > Sasha, you are welcome.
> > >
> > > It should be noted that path computation for e-backup is
> > trivial when
> > routed
> > > along the backup. That should not impact operational experience.
> > > Setup/maintenance of e-backup should be fairly straightforward. It
> > would be
> > > helpful if you can quantify a 'proliferation'.
> > >
> > > Bandwidth can be shared between the e-backup and the backup
tunnel.
> > > When the e-backup is routed along the backup, there should
> > not be any
> > > extra bandwidth consumed compared to [MPLS-FRR]. The benefit is
that
> > the
> > > problematic U-turn goes away.
> > >
> > > Thanks
> > >
> > > - Sri
> > >
> > >
> > >
> > >
> > > ________________________________
> > >
> > > 	From: Alexander Vainshtein
> > > [mailto:Alexander.Vainshtein@ecitele.com]
> > > 	Sent: Monday, July 26, 2010 11:55 PM
> > > 	To: Sriganesh Kini
> > > 	Cc: mpls@ietf.org
> > > 	Subject: RE: [mpls] Scalability of the "effective FRR" approach
> > in
> > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > >
> > >
> > >
> > > 	Sri,
> > >
> > > 	Lots of thanks for a prompt response. It seems that we more or
> > less
> > > agree on the facts (proliferation of e-backup LSPs) but we
> > differ in
> > > interpreting  the impact  of these facts  on the actual
operational
> > experience.
> > >
> > >
> > >
> > > 	However, I'd like to notice that "BW effectiveness" of e-backup
> > LSPs
> > > is also somewhat problematic IMO.
> > >
> > > 	Please note that both the regular backup and e-backup
> > bypass tunnels
> > > cross multiple links that are not involved with the original
> > set of LSPs
> > > they are protecting. And they both consume BW on these
> > links. The only
> > > difference is that they are competing for BW with other
> > LSPs, not with
> > ones
> > > they are protecting. But the overall effect is exactly the same
IMO.
> > >
> > >
> > >
> > > 	My 2c,
> > >
> > > 	     Sasha
> > >
> > >
> > >
> > > 	From: Sriganesh Kini [mailto:sriganesh.kini@ericsson.com]
> > > 	Sent: Monday, July 26, 2010 8:01 PM
> > > 	To: Alexander Vainshtein
> > > 	Cc: mpls@ietf.org
> > > 	Subject: RE: [mpls] Scalability of the "effective FRR" approach
> > in
> > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > >
> > >
> > >
> > > 	Sasha,
> > >
> > >
> > >
> > > 	As you noted the e-backup tunnel protects all LSPs that
> > have a common
> > > {head-end, tail-end} pair. More precisely, the e-backup can
> > be shared
> > > to protect all LSPs that have a common {ring-ingress-LSR,
> > ring-egress-
> > > LSR} pair (that is path is disjoint with the e-backup).
> > >
> > >
> > >
> > > 	If I understood correctly your concern is about the
> > number of number
> > > of e-backup tunnels?
> > >
> > >
> > >
> > > 	E-backup tunnels should be setup based on protected
> > LSP's {ring-
> > > ingress, ring-egress} LSRs. Consider a typical case where in a
ring,
> > there is a
> > > 'ring-head-end' and LSPs are setup from other LSRs on the
> > ring to the
> > 'ring-
> > > head-end'. An e-backup should be setup from each LSR on the ring
to
> > the
> > > 'ring-head-end'. This is order(n).
> > >
> > >
> > >
> > > 	Even for cases where protected LSPs have many possible
> > combinations
> > > for {ring-ingress, ring-egress}, for typical ring sizes,
> > the number
> > > of tunnels required should not be a concern for today's
> > implementations.
> > >
> > >
> > >
> > > 	Also, in many topologies an LSR that is purely a transit for
> > protected
> > > LSPs, does not have to originate any e-backup.
> > >
> > >
> > >
> > > 	Thanks
> > >
> > > 	- Sri
> > >
> > > 	PS: Regular facility FRR requires more that two backup tunnels,
> > > depending on what is being protected.
> > >
> > >
> > >
> > >
> > > ________________________________
> > >
> > >
> > > 		From: mpls-bounces@ietf.org [mailto:mpls-
> > bounces@ietf.org] On
> > > Behalf Of Alexander Vainshtein
> > > 		Sent: Monday, July 26, 2010 9:57 AM
> > > 		To: Sriganesh Kini
> > > 		Cc: mpls@ietf.org
> > > 		Subject: [mpls] Scalability of the "effective FRR"
> > approach in
> > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > >
> > > 		Sriganesh and all,
> > >
> > > 		If I understood you correctly, your proposal
> > requires a dedicated
> > > backup tunnel for all LSPs with the given {head-end,
> > tail-end} pair
> > > of LSRs in the ring. (Regular facility FRR requires just two
backup
> > tunnels).
> > >
> > > 		If this understanding is correct, this looks to like a
> > serious
> > > scalability issue with your approach.
> > >
> > >
> > >
> > > 		Regards,
> > >
> > > 		     Sasha
> > >
> > >
> >
> >

From chair@ietf.org  Tue Jul 27 02:31:24 2010
Return-Path: <chair@ietf.org>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 103133A6A4D; Tue, 27 Jul 2010 02:31:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.121
X-Spam-Level: 
X-Spam-Status: No, score=-102.121 tagged_above=-999 required=5 tests=[AWL=-0.122, BAYES_00=-2.599, J_CHICKENPOX_82=0.6, 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 yPX8M-FAXNuk; Tue, 27 Jul 2010 02:31:23 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id A49683A6AAB; Tue, 27 Jul 2010 02:31:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id BE6CEE08C1; Tue, 27 Jul 2010 02:31:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ufk3QpSRo5eB; Tue, 27 Jul 2010 02:31:44 -0700 (PDT)
Received: from [130.129.34.235] (dhcp-22eb.meeting.ietf.org [130.129.34.235]) by c1a.amsl.com (Postfix) with ESMTPSA id DAD66E0892; Tue, 27 Jul 2010 02:31:40 -0700 (PDT)
Message-ID: <4C4EA77A.5000602@ietf.org>
Date: Tue, 27 Jul 2010 05:31:38 -0400
From: IETF Chair <chair@ietf.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, steve.trowbridge@alcatel-lucent.com, malcolm.betts@zte.com.cn, iab-chair@iab.org, yoichi.maeda@ntt-at.co.jp, paf@cisco.co, rcallon@juniper.net, iab@iab.org, adrian.farrel@huawei.com, IETF Liaison Statements <statements@ietf.org>, iesg@ietf.org
Subject: [mpls] Liaison Statement: Re: LS205 - Considerations on the approach, to providing OAM for MPLS-TP (#37.02)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 09:31:24 -0000

Purpose: In response

Thank you for your liaison COM15-LS205-E, Considerations on the approach
to providing OAM for MPLS-TP.

We agree that it is desirable to extend the OAM capabilities of the MPLS
protocol suite to support the needs of the transport network operators
in a timely manner. We hope that these requirements are correctly
captured in RFC 5654 and RFC 5860 both of which completed the IETF
consensus process and received substantial and constructive review by
Study Group 15 of the ITU-T.

As you appreciate, both the IETF and the ITU-T are contribution driven
organizations. The IETF would therefore encourage the service providers
who are requesting more rapid development of standards to participate
more fully in the IETF standardization process.

Your liaison references some interoperability tests. It is hard for us
to evaluate the scope and validity of these tests for a number of reasons:

   - The specification of the protocols actually tested and the
     detailed results are confidential to the participants and not
     generally available.

   - We cannot assess which features documented in the referenced
     draft (draft-bhh-mpls-tp-oam-y1731) were tested and which
     were not tested.

   - The current revision of draft-bhh-mpls-tp-oam-y1731 does not
     provide full details of the protocol mechanisms of all of the
     features it describes.

   - The test description refers to the unpublished G.8114 (2008),
     which we understand does not have ITU-T consensus.

With regard to the specific technical proposal outlined in the liaison,
the IETF process is available to investigate the approaches to the
design of an enhanced MPLS OAM to satisfy the needs of network
operators, including of course the transport network operators. Such
ideas must comply with previously agreed requirements unless new
requirements are brought forward and agreed by consensus in both the
IETF and the ITU-T. All new approaches are subject to technical
discussion within the IETF and will be reviewed by IETF consensus.
Proponents of alternative solutions are encouraged to discuss them on
the appropriate IETF mailing lists and to attempt to persuade the
community of the technical merit of their proposals.

The IETF looks forward to working cooperatively with the ITU-T to
develop MPLS-TP OAM solution components in a timely manner that meets
the needs of network operators wishing to deploy MPLS technology.

On behalf of the IESG,
 Russ Housley

From chair@ietf.org  Tue Jul 27 04:04:05 2010
Return-Path: <chair@ietf.org>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4FD43A6B7C; Tue, 27 Jul 2010 04:04:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.409
X-Spam-Level: 
X-Spam-Status: No, score=-102.409 tagged_above=-999 required=5 tests=[AWL=0.190, 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 0xknO1wvp-Bp; Tue, 27 Jul 2010 04:03:57 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 13D653A6A67; Tue, 27 Jul 2010 04:03:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 402FCE08CF; Tue, 27 Jul 2010 04:04:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLt26gYAXhMb; Tue, 27 Jul 2010 04:04:19 -0700 (PDT)
Received: from [130.129.34.235] (dhcp-22eb.meeting.ietf.org [130.129.34.235]) by c1a.amsl.com (Postfix) with ESMTPSA id 8EC2FE0892; Tue, 27 Jul 2010 04:04:15 -0700 (PDT)
Message-ID: <4C4EB2BE.8040008@ietf.org>
Date: Tue, 27 Jul 2010 06:19:42 -0400
From: IETF Chair <chair@ietf.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: tsbsg15@itu.int, greg.jones@itu.int, hhelvoort@huawei.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, steve.trowbridge@alcatel-lucent.com, iab-chair@iab.org, yoichi.maeda@ntt-at.co.jp, mpls-tp@ietf.org, paf@cisco.co, iab@iab.org, adrian.farrel@huawei.com, IETF Liaison Statements <statements@ietf.org>, iesg@ietf.org
Subject: [mpls] Liaison Statement: Re: L211 - Request for the roadmap of MPLS-TP OAM (#038.01)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 11:04:05 -0000

Purpose: In response

Thank you for your liaison COM15-LS211-E "Request for the roadmap of
MPLS-TP OAM (#038.01)" dated 24-June-2010.

Like the ITU-T, the IETF is a contribution-driven organization that
relies on the voluntary effort of its members. The specific order and
the time of delivery is dependent on the timeliness of the input
received and the level of contribution.

We divide the work into four broad topic areas. Work has started on all
four areas, and given the constraints stated above we are unable to
impose a priority on the contributors.

The first area is linear protection, and the working group has drafts on
this topic.

The second area is the OAM.  The list of drafts are currently found in
draft-ietf-mpls-tp-oam-analysis, and this set of drafts cover the
required OAM functionality as documented in RFC 5860.

The third area is extensions for the MPLS control plane for MPLS-TP
networks, and the control plane framework is under way and extensions to
RSVP-TE for OAM parameters have been defined.

The fourth area covers the rest of the work items, including ring
protection.

In order to accelerate the progress and meet the operators' urgent
requirements for MPLS-TP OAM, it is suggested the ITU-T encourages the
service providers who are requesting more rapid development of standards
to participate more fully in the IETF standardization process, as
jointly agreed upon.

The IETF looks forward to working cooperatively with the ITU-T to
develop MPLS-TP OAM solution components in a timely manner that meet the
needs of network operators wishing to deploy MPLS technology.

On behalf of the IESG,
 Russ Housley

From sriganesh.kini@ericsson.com  Tue Jul 27 04:47:26 2010
Return-Path: <sriganesh.kini@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38CAD3A69E4 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 04:47:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[AWL=1.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 QoFRelw6m98J for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 04:47:23 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 9DAE53A6AD2 for <mpls@ietf.org>; Tue, 27 Jul 2010 04:47:22 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o6RBudn2022858; Tue, 27 Jul 2010 06:56:39 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Tue, 27 Jul 2010 07:47:37 -0400
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Date: Tue, 27 Jul 2010 07:47:35 -0400
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaAABzm8kAAAGaFoAAB6yoAAADgilAAAUKywAABic6Q
Message-ID: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EA0@EUSAACMS0703.eamcs.ericsson.se>
References: <D29E470202D67745B61059870F433B5402511686@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80E8F@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B5402511689@XMB-RCD-202.cisco.com>
In-Reply-To: <D29E470202D67745B61059870F433B5402511689@XMB-RCD-202.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 11:47:26 -0000

Inline @ [Sri]

- Sri
=20

> -----Original Message-----
> From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com]=20
> Sent: Tuesday, July 27, 2010 2:18 AM
> To: Sriganesh Kini; Alexander Vainshtein
> Cc: mpls@ietf.org
> Subject: RE: [mpls] Scalability of the "effective FRR"=20
> approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
>=20
> Inline with EO#
>=20
> > -----Original Message-----
> > From: Sriganesh Kini [mailto:sriganesh.kini@ericsson.com]
> > Sent: Tuesday, July 27, 2010 10:52 AM
> > To: Eric Osborne (eosborne); Alexander Vainshtein
> > Cc: mpls@ietf.org
> > Subject: RE: [mpls] Scalability of the "effective FRR" approach in
> draft-kini-
> > mpls-ring-frr-facility-backup-00.txt
> >=20
> > Eric, pls see inline @ [Sri]
> >=20
> > - Sri
> >=20
> >=20
> > > -----Original Message-----
> > > From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com]
> > > Sent: Tuesday, July 27, 2010 1:19 AM
> > > To: Sriganesh Kini; Alexander Vainshtein
> > > Cc: mpls@ietf.org
> > > Subject: RE: [mpls] Scalability of the "effective FRR"
> > > approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
> > >
> > > I'm afraid I don't quite see the severity of the u-turn.
> > > Yes, it's suboptimal.  But how long does the condition last?
> > > All implementations I'm familiar with will rebuild the new primary
> LSP
> > > (the L9->L6 LSP, in your example) in O(seconds), so the=20
> suboptimal=20
> > > condition is pretty transient.  Your solution seems like=20
> quite a lot=20
> > > of work (BFD, e-backup
> > > tunnels) for a few seconds of gain.
> >=20
> > This solution aims for characteristics as close to MPLS-FRR when
> repair is
> > done at an LSR adjacent to the failure. MPLS-FRR is used=20
> for networks=20
> > requiring failure recovery with very low traffic loss (typically sub
> 50msec). If
> > the network you are considering is tolerant to several seconds of
> traffic loss,
> > plain old IGP convergence should be more than enough.
>=20
> EO#  Yes, I'm familiar with how that works and that's not my=20
> point.  In FRR networks as currently deployed, the timeline=20
> goes something like
> this:
>=20
> i) failure happens
> ii) PLR kicks in protection.  Traffic is protected, but may (in some
> topologies) be routed in the manner you refer to as suboptimal
> iii) headend of the protected tunnel is notified of the=20
> failure and reroutes to a new primary path
>=20
> Elapsed time:
> (i) -> (ii)  <=3D50ms
> (ii)->(iii) ~=3D O(seconds)
>=20
> The point I'm making is not that there are O(seconds) of loss, but
> O(seconds) of suboptimality.  And I'm questioning whether the=20
> amount of work you're proposing is worth it in order to=20
> minimize this O(seconds) of suboptimality.  If the=20
> suboptimality lasted for a long time (minutes?
> hours?) I think it may be worth trying to optimize away, but=20
> it doesn't and thus IMHO isn't.

[Sri] Sub-optimality can result in degraded service (see example in section=
 3). Preventing this in time periods close to MPLS-FRR is important.

>=20
> There are also existing mechanisms to minimize the impact of=20
> this suboptimality.  They include proper placement of primary=20
> and backup paths, QoS for congestion control, and path=20
> protection.  None of these are mandatory, but all of them are=20
> useful.  To me, this further reduces the utility of the=20
> mechanism you describe.  This is, of course, always going to=20
> be a matter of opinion.

[Sri] It would be useful if you describe in detail how the 'existing mechan=
isms' solves a specific problem such as the one described in section 3.

>=20
> And don't even get me started on "if you don't like how ring=20
> networks behave, don't build ring networks".  That's a whole=20

[Sri] Not sure what gave you that impression.

> different topic.
>=20
>=20
>=20
> eric
>=20
> > >
> > > Also, it's not clear to me what happens in the time after the
> failure
> > > but before fast-alert messages are processed at the=20
> u-PLR.  Does the=20
> > > PLR drop traffic until then?  Does it do inefficient backup?  Is
> this
> > > an implementations-specific decision?
> >=20
> > Typically a protection switch at PLR should result in lower overall
> loss than
> > completely dropping traffic. If there are very specific conditions
> where
> > completely dropping traffic is more advantageous, it may be an
> additional
> > behavior.
>=20
> OK, so your desire is that the PLR locally (suboptimally)=20
> protect traffic until the u-PLR does its thing.
>=20
> >=20
> > >
> > > Thirdly, I'm not sure how generalizable this solution is=20
> to a mesh=20
> > > topology.  While it will certainly work just as well=20
> there as in a=20
> > > ring, it is entirely possible (and in my experience quite common)
> that
> > > the backup tunnel does not overlap with many of the=20
> tunnels which it=20
> > > is protecting, and thus you do not have a problem to=20
> solve.  As you=20
> > > are solving a problem that is IMHO predominant only in ring=20
> > > topologies, this mechanism is more of a specialized,=20
> ring-optimized=20
> > > tool than a general-purpose thing.
> >=20
> > The draft makes a statement about applicability to general=20
> topologies
> and as
> > you correctly noted it works just as well. How much of overlap is
> there will
> > vary from one network to another.
> >=20
> > >
> > >
> > >
> > > eric
> > >
> > >
> > > > -----Original Message-----
> > > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> Behalf
> > > Of
> > > > Sriganesh Kini
> > > > Sent: Tuesday, July 27, 2010 9:28 AM
> > > > To: Alexander Vainshtein
> > > > Cc: mpls@ietf.org
> > > > Subject: Re: [mpls] Scalability of the "effective FRR"=20
> approach in
> > > draft-kini-
> > > > mpls-ring-frr-facility-backup-00.txt
> > > >
> > > > Sasha, you are welcome.
> > > >
> > > > It should be noted that path computation for e-backup is
> > > trivial when
> > > routed
> > > > along the backup. That should not impact operational experience.
> > > > Setup/maintenance of e-backup should be fairly=20
> straightforward. It
> > > would be
> > > > helpful if you can quantify a 'proliferation'.
> > > >
> > > > Bandwidth can be shared between the e-backup and the backup
> tunnel.
> > > > When the e-backup is routed along the backup, there should
> > > not be any
> > > > extra bandwidth consumed compared to [MPLS-FRR]. The benefit is
> that
> > > the
> > > > problematic U-turn goes away.
> > > >
> > > > Thanks
> > > >
> > > > - Sri
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >
> > > > 	From: Alexander Vainshtein
> > > > [mailto:Alexander.Vainshtein@ecitele.com]
> > > > 	Sent: Monday, July 26, 2010 11:55 PM
> > > > 	To: Sriganesh Kini
> > > > 	Cc: mpls@ietf.org
> > > > 	Subject: RE: [mpls] Scalability of the=20
> "effective FRR" approach
> > > in
> > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > >
> > > >
> > > >
> > > > 	Sri,
> > > >
> > > > 	Lots of thanks for a prompt response. It seems=20
> that we more or
> > > less
> > > > agree on the facts (proliferation of e-backup LSPs) but we
> > > differ in
> > > > interpreting  the impact  of these facts  on the actual
> operational
> > > experience.
> > > >
> > > >
> > > >
> > > > 	However, I'd like to notice that "BW=20
> effectiveness" of e-backup
> > > LSPs
> > > > is also somewhat problematic IMO.
> > > >
> > > > 	Please note that both the regular backup and e-backup
> > > bypass tunnels
> > > > cross multiple links that are not involved with the original
> > > set of LSPs
> > > > they are protecting. And they both consume BW on these
> > > links. The only
> > > > difference is that they are competing for BW with other
> > > LSPs, not with
> > > ones
> > > > they are protecting. But the overall effect is exactly the same
> IMO.
> > > >
> > > >
> > > >
> > > > 	My 2c,
> > > >
> > > > 	     Sasha
> > > >
> > > >
> > > >
> > > > 	From: Sriganesh Kini=20
> [mailto:sriganesh.kini@ericsson.com]
> > > > 	Sent: Monday, July 26, 2010 8:01 PM
> > > > 	To: Alexander Vainshtein
> > > > 	Cc: mpls@ietf.org
> > > > 	Subject: RE: [mpls] Scalability of the=20
> "effective FRR" approach
> > > in
> > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > >
> > > >
> > > >
> > > > 	Sasha,
> > > >
> > > >
> > > >
> > > > 	As you noted the e-backup tunnel protects all LSPs that
> > > have a common
> > > > {head-end, tail-end} pair. More precisely, the e-backup can
> > > be shared
> > > > to protect all LSPs that have a common {ring-ingress-LSR,
> > > ring-egress-
> > > > LSR} pair (that is path is disjoint with the e-backup).
> > > >
> > > >
> > > >
> > > > 	If I understood correctly your concern is about the
> > > number of number
> > > > of e-backup tunnels?
> > > >
> > > >
> > > >
> > > > 	E-backup tunnels should be setup based on protected
> > > LSP's {ring-
> > > > ingress, ring-egress} LSRs. Consider a typical case where in a
> ring,
> > > there is a
> > > > 'ring-head-end' and LSPs are setup from other LSRs on the
> > > ring to the
> > > 'ring-
> > > > head-end'. An e-backup should be setup from each LSR on the ring
> to
> > > the
> > > > 'ring-head-end'. This is order(n).
> > > >
> > > >
> > > >
> > > > 	Even for cases where protected LSPs have many possible
> > > combinations
> > > > for {ring-ingress, ring-egress}, for typical ring sizes,
> > > the number
> > > > of tunnels required should not be a concern for today's
> > > implementations.
> > > >
> > > >
> > > >
> > > > 	Also, in many topologies an LSR that is purely=20
> a transit for
> > > protected
> > > > LSPs, does not have to originate any e-backup.
> > > >
> > > >
> > > >
> > > > 	Thanks
> > > >
> > > > 	- Sri
> > > >
> > > > 	PS: Regular facility FRR requires more that two=20
> backup tunnels,=20
> > > > depending on what is being protected.
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >
> > > >
> > > > 		From: mpls-bounces@ietf.org [mailto:mpls-
> > > bounces@ietf.org] On
> > > > Behalf Of Alexander Vainshtein
> > > > 		Sent: Monday, July 26, 2010 9:57 AM
> > > > 		To: Sriganesh Kini
> > > > 		Cc: mpls@ietf.org
> > > > 		Subject: [mpls] Scalability of the=20
> "effective FRR"
> > > approach in
> > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > >
> > > > 		Sriganesh and all,
> > > >
> > > > 		If I understood you correctly, your proposal
> > > requires a dedicated
> > > > backup tunnel for all LSPs with the given {head-end,
> > > tail-end} pair
> > > > of LSRs in the ring. (Regular facility FRR requires just two
> backup
> > > tunnels).
> > > >
> > > > 		If this understanding is correct, this=20
> looks to like a
> > > serious
> > > > scalability issue with your approach.
> > > >
> > > >
> > > >
> > > > 		Regards,
> > > >
> > > > 		     Sasha
> > > >
> > > >
> > >
> > >
> =

From eosborne@cisco.com  Tue Jul 27 05:29:43 2010
Return-Path: <eosborne@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E77C63A6A51 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 05:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 rQD+NH74bXKQ for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 05:29:42 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id B5A623A68D4 for <mpls@ietf.org>; Tue, 27 Jul 2010 05:29:41 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEALJtTkytJV2Y/2dsb2JhbACfZXGmC5tEhTYEhAmHGQwB
X-IronPort-AV: E=Sophos;i="4.55,267,1278288000"; d="scan'208";a="139732814"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rtp-iport-2.cisco.com with ESMTP; 27 Jul 2010 12:30:02 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id o6RCU22N000565;  Tue, 27 Jul 2010 12:30:02 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 27 Jul 2010 07:30:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Jul 2010 07:30:00 -0500
Message-ID: <D29E470202D67745B61059870F433B54025116C2@XMB-RCD-202.cisco.com>
In-Reply-To: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EA0@EUSAACMS0703.eamcs.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaAABzm8kAAAGaFoAAB6yoAAADgilAAAUKywAABic6QAASecBA=
References: <D29E470202D67745B61059870F433B5402511686@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80E8F@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B5402511689@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EA0@EUSAACMS0703.eamcs.ericsson.se>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Sriganesh Kini" <sriganesh.kini@ericsson.com>, "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 27 Jul 2010 12:30:02.0832 (UTC) FILETIME=[6FB77500:01CB2D87]
Cc: mpls@ietf.org
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 12:29:44 -0000

Inline with EO#
...

> > The point I'm making is not that there are O(seconds) of loss, but
> > O(seconds) of suboptimality.  And I'm questioning whether the amount
> > of work you're proposing is worth it in order to minimize this
> > O(seconds) of suboptimality.  If the suboptimality lasted for a long
> > time (minutes?
> > hours?) I think it may be worth trying to optimize away, but it
> > doesn't and thus IMHO isn't.
>=20
> [Sri] Sub-optimality can result in degraded service (see example in
section 3).
> Preventing this in time periods close to MPLS-FRR is important.
>=20
> >
> > There are also existing mechanisms to minimize the impact of this
> > suboptimality.  They include proper placement of primary and backup
> > paths, QoS for congestion control, and path protection.  None of
these
> > are mandatory, but all of them are useful.  To me, this further
> > reduces the utility of the mechanism you describe.  This is, of
> > course, always going to be a matter of opinion.
>=20
> [Sri] It would be useful if you describe in detail how the 'existing
mechanisms'
> solves a specific problem such as the one described in section 3.


EO#=20
I think it's important to distinguish between 'solve' and 'optimize'.
You cannot eliminate L9->L8->L9 packet forwarding unless L8 simply
decides to drop packets when link L8-L7 goes down.  We agreed on as much
in an earlier email.  To me, this means you cannot 'solve' the problem.
You can only optimize it, insofar as you can minimize the amount of time
that packets go L9->L8->L9 before the network makes this suboptimality
go away - this is the whole point of your draft. =20

Also - the suboptimality you point out comprises two parts.  You have
some time where you have additional delay, and during that same amount
of time you have the potential for traffic loss due to congestion.  Do
you agree?

I am not claiming that existing mechanisms *solve* the problem you've
pointed out.  But I hope that if you were to take my distinction between
solve and  optimize that you would agree that the method in your draft
does not solve this problem either.  Given that it takes some finite
amount of time to react to a failure, all any mechanism can ever do is
minimize the time spent in this suboptimal condition - that is,
'optimize'.

Do you agree?  If not, we have a fundamental disagreement (probably one
of terminology rather than of technology) and we should sort that out
first.

I assume henceforth that you agree with my solve/optimize distinction
and my view of the limitations of what can ever be done here.

Assuming you do, then I think what you're asking is "how do existing
mechanisms minimize the impact of this suboptimality?"  And I think the
implicit question here is also "...and why do you contend that these
mechanisms reduce the utility of the draft-kini mechanism?"

If that's true, then it should be pretty clear.  Any mechanism which can
be used to structure the network or the behavior of the network such
that the exposure to either the congestion or delay piece of the
suboptimality is minimized optimizes things (by definition). =20

All I'm contending is that these mechanisms (QoS, traffic engineering,
path protection), which are common operational tools that are by and
large not specific to MPLS-TE, optimize enough of the suboptimality away
that the additional mechanisms you propose will not add much, and which
will add whatever they add at a significant cost.  This is, of course,
necessarily an opinion rather than a hard fact. =20





eric



>=20
> >
> > And don't even get me started on "if you don't like how ring
networks
> > behave, don't build ring networks".  That's a whole
>=20
> [Sri] Not sure what gave you that impression.
>=20
> > different topic.
> >
> >
> >
> > eric
> >
> > > >
> > > > Also, it's not clear to me what happens in the time after the
> > failure
> > > > but before fast-alert messages are processed at the
> > u-PLR.  Does the
> > > > PLR drop traffic until then?  Does it do inefficient backup?  Is
> > this
> > > > an implementations-specific decision?
> > >
> > > Typically a protection switch at PLR should result in lower
overall
> > loss than
> > > completely dropping traffic. If there are very specific conditions
> > where
> > > completely dropping traffic is more advantageous, it may be an
> > additional
> > > behavior.
> >
> > OK, so your desire is that the PLR locally (suboptimally) protect
> > traffic until the u-PLR does its thing.
> >
> > >
> > > >
> > > > Thirdly, I'm not sure how generalizable this solution is
> > to a mesh
> > > > topology.  While it will certainly work just as well
> > there as in a
> > > > ring, it is entirely possible (and in my experience quite
common)
> > that
> > > > the backup tunnel does not overlap with many of the
> > tunnels which it
> > > > is protecting, and thus you do not have a problem to
> > solve.  As you
> > > > are solving a problem that is IMHO predominant only in ring
> > > > topologies, this mechanism is more of a specialized,
> > ring-optimized
> > > > tool than a general-purpose thing.
> > >
> > > The draft makes a statement about applicability to general
> > topologies
> > and as
> > > you correctly noted it works just as well. How much of overlap is
> > there will
> > > vary from one network to another.
> > >
> > > >
> > > >
> > > >
> > > > eric
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> > Behalf
> > > > Of
> > > > > Sriganesh Kini
> > > > > Sent: Tuesday, July 27, 2010 9:28 AM
> > > > > To: Alexander Vainshtein
> > > > > Cc: mpls@ietf.org
> > > > > Subject: Re: [mpls] Scalability of the "effective FRR"
> > approach in
> > > > draft-kini-
> > > > > mpls-ring-frr-facility-backup-00.txt
> > > > >
> > > > > Sasha, you are welcome.
> > > > >
> > > > > It should be noted that path computation for e-backup is
> > > > trivial when
> > > > routed
> > > > > along the backup. That should not impact operational
experience.
> > > > > Setup/maintenance of e-backup should be fairly
> > straightforward. It
> > > > would be
> > > > > helpful if you can quantify a 'proliferation'.
> > > > >
> > > > > Bandwidth can be shared between the e-backup and the backup
> > tunnel.
> > > > > When the e-backup is routed along the backup, there should
> > > > not be any
> > > > > extra bandwidth consumed compared to [MPLS-FRR]. The benefit
is
> > that
> > > > the
> > > > > problematic U-turn goes away.
> > > > >
> > > > > Thanks
> > > > >
> > > > > - Sri
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > >
> > > > > 	From: Alexander Vainshtein
> > > > > [mailto:Alexander.Vainshtein@ecitele.com]
> > > > > 	Sent: Monday, July 26, 2010 11:55 PM
> > > > > 	To: Sriganesh Kini
> > > > > 	Cc: mpls@ietf.org
> > > > > 	Subject: RE: [mpls] Scalability of the
> > "effective FRR" approach
> > > > in
> > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > >
> > > > >
> > > > >
> > > > > 	Sri,
> > > > >
> > > > > 	Lots of thanks for a prompt response. It seems
> > that we more or
> > > > less
> > > > > agree on the facts (proliferation of e-backup LSPs) but we
> > > > differ in
> > > > > interpreting  the impact  of these facts  on the actual
> > operational
> > > > experience.
> > > > >
> > > > >
> > > > >
> > > > > 	However, I'd like to notice that "BW
> > effectiveness" of e-backup
> > > > LSPs
> > > > > is also somewhat problematic IMO.
> > > > >
> > > > > 	Please note that both the regular backup and e-backup
> > > > bypass tunnels
> > > > > cross multiple links that are not involved with the original
> > > > set of LSPs
> > > > > they are protecting. And they both consume BW on these
> > > > links. The only
> > > > > difference is that they are competing for BW with other
> > > > LSPs, not with
> > > > ones
> > > > > they are protecting. But the overall effect is exactly the
same
> > IMO.
> > > > >
> > > > >
> > > > >
> > > > > 	My 2c,
> > > > >
> > > > > 	     Sasha
> > > > >
> > > > >
> > > > >
> > > > > 	From: Sriganesh Kini
> > [mailto:sriganesh.kini@ericsson.com]
> > > > > 	Sent: Monday, July 26, 2010 8:01 PM
> > > > > 	To: Alexander Vainshtein
> > > > > 	Cc: mpls@ietf.org
> > > > > 	Subject: RE: [mpls] Scalability of the
> > "effective FRR" approach
> > > > in
> > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > >
> > > > >
> > > > >
> > > > > 	Sasha,
> > > > >
> > > > >
> > > > >
> > > > > 	As you noted the e-backup tunnel protects all LSPs that
> > > > have a common
> > > > > {head-end, tail-end} pair. More precisely, the e-backup can
> > > > be shared
> > > > > to protect all LSPs that have a common {ring-ingress-LSR,
> > > > ring-egress-
> > > > > LSR} pair (that is path is disjoint with the e-backup).
> > > > >
> > > > >
> > > > >
> > > > > 	If I understood correctly your concern is about the
> > > > number of number
> > > > > of e-backup tunnels?
> > > > >
> > > > >
> > > > >
> > > > > 	E-backup tunnels should be setup based on protected
> > > > LSP's {ring-
> > > > > ingress, ring-egress} LSRs. Consider a typical case where in a
> > ring,
> > > > there is a
> > > > > 'ring-head-end' and LSPs are setup from other LSRs on the
> > > > ring to the
> > > > 'ring-
> > > > > head-end'. An e-backup should be setup from each LSR on the
ring
> > to
> > > > the
> > > > > 'ring-head-end'. This is order(n).
> > > > >
> > > > >
> > > > >
> > > > > 	Even for cases where protected LSPs have many possible
> > > > combinations
> > > > > for {ring-ingress, ring-egress}, for typical ring sizes,
> > > > the number
> > > > > of tunnels required should not be a concern for today's
> > > > implementations.
> > > > >
> > > > >
> > > > >
> > > > > 	Also, in many topologies an LSR that is purely
> > a transit for
> > > > protected
> > > > > LSPs, does not have to originate any e-backup.
> > > > >
> > > > >
> > > > >
> > > > > 	Thanks
> > > > >
> > > > > 	- Sri
> > > > >
> > > > > 	PS: Regular facility FRR requires more that two
> > backup tunnels,
> > > > > depending on what is being protected.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > >
> > > > >
> > > > > 		From: mpls-bounces@ietf.org [mailto:mpls-
> > > > bounces@ietf.org] On
> > > > > Behalf Of Alexander Vainshtein
> > > > > 		Sent: Monday, July 26, 2010 9:57 AM
> > > > > 		To: Sriganesh Kini
> > > > > 		Cc: mpls@ietf.org
> > > > > 		Subject: [mpls] Scalability of the
> > "effective FRR"
> > > > approach in
> > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > >
> > > > > 		Sriganesh and all,
> > > > >
> > > > > 		If I understood you correctly, your proposal
> > > > requires a dedicated
> > > > > backup tunnel for all LSPs with the given {head-end,
> > > > tail-end} pair
> > > > > of LSRs in the ring. (Regular facility FRR requires just two
> > backup
> > > > tunnels).
> > > > >
> > > > > 		If this understanding is correct, this
> > looks to like a
> > > > serious
> > > > > scalability issue with your approach.
> > > > >
> > > > >
> > > > >
> > > > > 		Regards,
> > > > >
> > > > > 		     Sasha
> > > > >
> > > > >
> > > >
> > > >
> >

From lucyyong@huawei.com  Tue Jul 27 05:31:15 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C98863A6A0E for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 05:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5 tests=[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 7OYSxTEJz34z for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 05:31:12 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 3583E3A68D4 for <mpls@ietf.org>; Tue, 27 Jul 2010 05:31:12 -0700 (PDT)
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 <0L6700FLUUSBOR@szxga03-in.huawei.com> for mpls@ietf.org; Tue, 27 Jul 2010 20:31:23 +0800 (CST)
Received: from 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 <0L67006WSUSB9Z@szxga03-in.huawei.com> for mpls@ietf.org; Tue, 27 Jul 2010 20:31:23 +0800 (CST)
Received: from y736742 (dhcp-72c7.meeting.ietf.org [130.129.114.199]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L6700IFDUS7UX@szxml02-in.huawei.com>; Tue, 27 Jul 2010 20:31:23 +0800 (CST)
Date: Tue, 27 Jul 2010 07:31:21 -0500
From: Yong Lucy <lucyyong@huawei.com>
To: 'Kireeti Kompella' <kireeti@juniper.net>, 'Shane Amante' <shane@castlepoint.net>, mpls@ietf.org
Message-id: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_O+PEsHYB1Sbati4QezOomg)"
Thread-index: Acsth0oUJSF/XWniQyWod9gx1LMJ/Q==
Subject: [mpls] entropy label indicator label in draft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 12:31:15 -0000

This is a multi-part message in MIME format.

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

Hi Kireeti and Shane,

 

Could we consider use one of reserved label for ELI purpose? This will make
implementation much easy, i.e. not need to keep the state for each ELI
label. The approach can be used in general for RSVP-TE and BGP as well.

 

Regards,

Lucy

 

 

 


--Boundary_(ID_O+PEsHYB1Sbati4QezOomg)
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="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 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Hi Kireeti and Shane,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Could we consider use one of reserved label for ELI
purpose? This will make implementation much easy, i.e. not need to keep the
state for each ELI label. The approach can be used in general for RSVP-TE and
BGP as well.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Regards,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Lucy<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_O+PEsHYB1Sbati4QezOomg)--

From venkatflex@gmail.com  Tue Jul 27 05:45:46 2010
Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CDC23A68D9; Tue, 27 Jul 2010 05:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level: 
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.171,  BAYES_00=-2.599, HTML_MESSAGE=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 O2L8DC6uvTqK; Tue, 27 Jul 2010 05:45:44 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 5A88E3A68D4; Tue, 27 Jul 2010 05:45:44 -0700 (PDT)
Received: by pxi20 with SMTP id 20so520675pxi.31 for <multiple recipients>; Tue, 27 Jul 2010 05:46:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=W54rN0Sj7JYNuI1mWW73Faby87kpTnWJmwCoeCFdDMM=; b=DPlzGkk0uDDv1AW4aXECbTCb8q3l0Ug/ZKIXbbTqQNEqjsUxHoVTEejPMr2jaY9x3k qZEbfKKFwqzrTx/zUpreljbmz/Eld3AzeEcmH//8xJQGGi38u1c50ztDRc+JkLv8X3TQ p2G68D0J2p4WjqtOyffwbsJKXS0Z6vGNY1+cg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=SnAbJVp20x4rVcW5b1keqeziKP6loS7c8kaOKG8qHebJ0AW3aU01nE7168JVSGkMsB JQoPKCsoD+Yv0FwwHxtPPjHn1DZ+0+NHrY2UCi9EYVQMD+t8Uc1dIhi+7scfmSF4Lo69 gqwqO7A6pMPOdFWQ/arkhf9H4JKhECx/gjG/g=
MIME-Version: 1.0
Received: by 10.142.199.20 with SMTP id w20mr3799222wff.176.1280234766096;  Tue, 27 Jul 2010 05:46:06 -0700 (PDT)
Received: by 10.142.77.1 with HTTP; Tue, 27 Jul 2010 05:46:05 -0700 (PDT)
Date: Tue, 27 Jul 2010 18:16:05 +0530
Message-ID: <AANLkTimNy3X8PB-Un9cEmgKFv=EGA_PX=s_GYxKiunEv@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: mpls-tp@ietf.org, mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary=000e0cd258827659d0048c5de2d0
Subject: [mpls] Query regarding MPLS P2MP ID usage
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 12:45:46 -0000

--000e0cd258827659d0048c5de2d0
Content-Type: text/plain; charset=ISO-8859-1

Hi,

As per draft-ietf-mpls-p2mp-te-mib-09.txt<http://tools.ietf.org/html/draft-ietf-mpls-p2mp-te-mib-09.txt>
draft,
P2MP MPLS-TE MIB is extended from MPLS-TE-STD-MIB.

So, mplsTunnelTable table can contain the informations for both normal MPLS
tunnels and MPLS P2MP tunnels.
How the two entries can be differentiated, do we need to check the entry
existence in the P2MP tunnel to
confirm the entry in the mplsTunnelTable is for P2MP tunnel?

 P2MP tunnel information in mplsTunnelTable is as follows:
     {
       mplsTunnelIndex              = 4,
       mplsTunnelInstance           = 0,
       mplsTunnelIngressLSRId       = "192.0.2.1",
       -- The tunnel egress LSR ID is used to
       -- hold the P2MP ID for the P2MP LSP tunnel
 *      mplsTunnelEgressLSRId        = 328,*
*       .........................*
*       .........................*
   }

What if the mplsTunnelEgressLSRId unsigned 32 bit integer matches with the
normal MPLS-TE tunnel's egress-id (Egress node IP address)?
Are we assuming that P2MP Id (mplsTunnelEgressLSRId) will not overlap the
valid IP address range?

-- 
Best Regards,
Venkatesan Mahalingam.

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

<div>Hi,</div>
<div>=A0</div>
<div>As per <a href=3D"http://tools.ietf.org/html/draft-ietf-mpls-p2mp-te-m=
ib-09.txt">draft-ietf-mpls-p2mp-te-mib-09.txt</a>=A0draft, P2MP MPLS-TE MIB=
 is extended from MPLS-TE-STD-MIB.</div>
<div>=A0</div>
<div>So, mplsTunnelTable table can contain the informations for both normal=
 MPLS tunnels and MPLS P2MP tunnels.</div>
<div>How=A0the two entries can be differentiated, do we need to check the e=
ntry existence in the P2MP tunnel to </div>
<div>confirm the entry in the mplsTunnelTable is for P2MP tunnel?</div>
<div>=A0</div>
<div>=A0P2MP tunnel information in mplsTunnelTable is as follows:<br>=A0=A0=
=A0=A0 {<br>=A0=A0=A0=A0=A0=A0 mplsTunnelIndex=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 =3D 4,<br>=A0=A0=A0=A0=A0=A0 mplsTunnelInstance=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 =3D 0,<br>=A0=A0=A0=A0=A0=A0 mplsTunnelIngressLSRId=A0=A0=
=A0=A0=A0=A0 =3D &quot;192.0.2.1&quot;,</div>

<div>=A0=A0=A0 =A0=A0 -- The tunnel egress LSR ID is used to<br>=A0=A0=A0=
=A0=A0=A0 -- hold the P2MP ID for the P2MP LSP tunnel<br>=A0<strong>=A0=A0=
=A0=A0=A0 mplsTunnelEgressLSRId=A0=A0=A0=A0=A0=A0=A0 =3D 328,</strong></div=
>
<div><strong>=A0=A0=A0=A0=A0=A0 .........................</strong></div>
<div><strong>=A0=A0=A0=A0=A0=A0 .........................</strong></div>
<div>=A0=A0 }</div>
<div>=A0</div>
<div>What if the mplsTunnelEgressLSRId=A0unsigned 32 bit integer matches wi=
th the normal MPLS-TE tunnel&#39;s egress-id (Egress node IP address)?<br><=
/div>
<div>Are we assuming that P2MP Id (mplsTunnelEgressLSRId)=A0will not overla=
p the valid IP address range?</div>
<div>=A0</div>
<div>-- <br>Best Regards,<br>Venkatesan Mahalingam.<br></div>

--000e0cd258827659d0048c5de2d0--

From sriganesh.kini@ericsson.com  Tue Jul 27 06:00:55 2010
Return-Path: <sriganesh.kini@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E83933A685A for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 06:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599]
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 SsFKa6Qz2TXh for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 06:00:54 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 429D43A6919 for <mpls@ietf.org>; Tue, 27 Jul 2010 06:00:54 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6RCxCO1019830 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Jul 2010 07:59:13 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 27 Jul 2010 08:59:12 -0400
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Date: Tue, 27 Jul 2010 08:59:10 -0400
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaAABzm8kAAAGaFoAAB6yoAAADgilAAAUKywAABic6QAASecBAAAb+9UA==
Message-ID: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EDC@EUSAACMS0703.eamcs.ericsson.se>
References: <D29E470202D67745B61059870F433B5402511686@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80E8F@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B5402511689@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EA0@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B54025116C2@XMB-RCD-202.cisco.com>
In-Reply-To: <D29E470202D67745B61059870F433B54025116C2@XMB-RCD-202.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 13:00:56 -0000

Eric, the important thing to consider is the time-scale. O(seconds) of subo=
ptimality (leading to O-seconds of degraded-service/packet-loss) is NOT com=
parable to the expected packet-loss (typically sub-50msec) in the facility =
bypass method of [MPLS-FRR] where PLR is adjacent to failure. It is much hi=
gher. Do you agree?

- Sri

PS: The title of the draft says "Efficient FRR ..." so obviously it is tryi=
ng to improve (optimize - if you prefer that term) FRR.

> -----Original Message-----
> From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com]=20
> Sent: Tuesday, July 27, 2010 5:30 AM
> To: Sriganesh Kini; Alexander Vainshtein
> Cc: mpls@ietf.org
> Subject: RE: [mpls] Scalability of the "effective FRR"=20
> approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
>=20
> Inline with EO#
> ...
>=20
> > > The point I'm making is not that there are O(seconds) of loss, but
> > > O(seconds) of suboptimality.  And I'm questioning whether=20
> the amount=20
> > > of work you're proposing is worth it in order to minimize this
> > > O(seconds) of suboptimality.  If the suboptimality lasted=20
> for a long=20
> > > time (minutes?
> > > hours?) I think it may be worth trying to optimize away, but it=20
> > > doesn't and thus IMHO isn't.
> >=20
> > [Sri] Sub-optimality can result in degraded service (see example in
> section 3).
> > Preventing this in time periods close to MPLS-FRR is important.
> >=20
> > >
> > > There are also existing mechanisms to minimize the impact of this=20
> > > suboptimality.  They include proper placement of primary=20
> and backup=20
> > > paths, QoS for congestion control, and path protection.  None of
> these
> > > are mandatory, but all of them are useful.  To me, this further=20
> > > reduces the utility of the mechanism you describe.  This is, of=20
> > > course, always going to be a matter of opinion.
> >=20
> > [Sri] It would be useful if you describe in detail how the 'existing
> mechanisms'
> > solves a specific problem such as the one described in section 3.
>=20
>=20
> EO#
> I think it's important to distinguish between 'solve' and 'optimize'.
> You cannot eliminate L9->L8->L9 packet forwarding unless L8=20
> simply decides to drop packets when link L8-L7 goes down.  We=20
> agreed on as much in an earlier email.  To me, this means you=20
> cannot 'solve' the problem.
> You can only optimize it, insofar as you can minimize the=20
> amount of time that packets go L9->L8->L9 before the network=20
> makes this suboptimality go away - this is the whole point of=20
> your draft. =20
>=20
> Also - the suboptimality you point out comprises two parts. =20
> You have some time where you have additional delay, and=20
> during that same amount of time you have the potential for=20
> traffic loss due to congestion.  Do you agree?
>=20
> I am not claiming that existing mechanisms *solve* the=20
> problem you've pointed out.  But I hope that if you were to=20
> take my distinction between solve and  optimize that you=20
> would agree that the method in your draft does not solve this=20
> problem either.  Given that it takes some finite amount of=20
> time to react to a failure, all any mechanism can ever do is=20
> minimize the time spent in this suboptimal condition - that=20
> is, 'optimize'.
>=20
> Do you agree?  If not, we have a fundamental disagreement=20
> (probably one of terminology rather than of technology) and=20
> we should sort that out first.
>=20
> I assume henceforth that you agree with my solve/optimize=20
> distinction and my view of the limitations of what can ever=20
> be done here.
>=20
> Assuming you do, then I think what you're asking is "how do=20
> existing mechanisms minimize the impact of this=20
> suboptimality?"  And I think the implicit question here is=20
> also "...and why do you contend that these mechanisms reduce=20
> the utility of the draft-kini mechanism?"
>=20
> If that's true, then it should be pretty clear.  Any=20
> mechanism which can be used to structure the network or the=20
> behavior of the network such that the exposure to either the=20
> congestion or delay piece of the suboptimality is minimized=20
> optimizes things (by definition). =20
>=20
> All I'm contending is that these mechanisms (QoS, traffic=20
> engineering, path protection), which are common operational=20
> tools that are by and large not specific to MPLS-TE, optimize=20
> enough of the suboptimality away that the additional=20
> mechanisms you propose will not add much, and which will add=20
> whatever they add at a significant cost.  This is, of course,=20
> necessarily an opinion rather than a hard fact. =20
>=20
>=20
>=20
>=20
>=20
> eric
>=20
>=20
>=20
> >=20
> > >
> > > And don't even get me started on "if you don't like how ring
> networks
> > > behave, don't build ring networks".  That's a whole
> >=20
> > [Sri] Not sure what gave you that impression.
> >=20
> > > different topic.
> > >
> > >
> > >
> > > eric
> > >
> > > > >
> > > > > Also, it's not clear to me what happens in the time after the
> > > failure
> > > > > but before fast-alert messages are processed at the
> > > u-PLR.  Does the
> > > > > PLR drop traffic until then?  Does it do inefficient=20
> backup?  Is
> > > this
> > > > > an implementations-specific decision?
> > > >
> > > > Typically a protection switch at PLR should result in lower
> overall
> > > loss than
> > > > completely dropping traffic. If there are very specific=20
> conditions
> > > where
> > > > completely dropping traffic is more advantageous, it may be an
> > > additional
> > > > behavior.
> > >
> > > OK, so your desire is that the PLR locally (suboptimally) protect=20
> > > traffic until the u-PLR does its thing.
> > >
> > > >
> > > > >
> > > > > Thirdly, I'm not sure how generalizable this solution is
> > > to a mesh
> > > > > topology.  While it will certainly work just as well
> > > there as in a
> > > > > ring, it is entirely possible (and in my experience quite
> common)
> > > that
> > > > > the backup tunnel does not overlap with many of the
> > > tunnels which it
> > > > > is protecting, and thus you do not have a problem to
> > > solve.  As you
> > > > > are solving a problem that is IMHO predominant only in ring=20
> > > > > topologies, this mechanism is more of a specialized,
> > > ring-optimized
> > > > > tool than a general-purpose thing.
> > > >
> > > > The draft makes a statement about applicability to general
> > > topologies
> > > and as
> > > > you correctly noted it works just as well. How much of=20
> overlap is
> > > there will
> > > > vary from one network to another.
> > > >
> > > > >
> > > > >
> > > > >
> > > > > eric
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: mpls-bounces@ietf.org=20
> [mailto:mpls-bounces@ietf.org] On
> > > Behalf
> > > > > Of
> > > > > > Sriganesh Kini
> > > > > > Sent: Tuesday, July 27, 2010 9:28 AM
> > > > > > To: Alexander Vainshtein
> > > > > > Cc: mpls@ietf.org
> > > > > > Subject: Re: [mpls] Scalability of the "effective FRR"
> > > approach in
> > > > > draft-kini-
> > > > > > mpls-ring-frr-facility-backup-00.txt
> > > > > >
> > > > > > Sasha, you are welcome.
> > > > > >
> > > > > > It should be noted that path computation for e-backup is
> > > > > trivial when
> > > > > routed
> > > > > > along the backup. That should not impact operational
> experience.
> > > > > > Setup/maintenance of e-backup should be fairly
> > > straightforward. It
> > > > > would be
> > > > > > helpful if you can quantify a 'proliferation'.
> > > > > >
> > > > > > Bandwidth can be shared between the e-backup and the backup
> > > tunnel.
> > > > > > When the e-backup is routed along the backup, there should
> > > > > not be any
> > > > > > extra bandwidth consumed compared to [MPLS-FRR]. The benefit
> is
> > > that
> > > > > the
> > > > > > problematic U-turn goes away.
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > - Sri
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > > 	From: Alexander Vainshtein
> > > > > > [mailto:Alexander.Vainshtein@ecitele.com]
> > > > > > 	Sent: Monday, July 26, 2010 11:55 PM
> > > > > > 	To: Sriganesh Kini
> > > > > > 	Cc: mpls@ietf.org
> > > > > > 	Subject: RE: [mpls] Scalability of the
> > > "effective FRR" approach
> > > > > in
> > > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	Sri,
> > > > > >
> > > > > > 	Lots of thanks for a prompt response. It seems
> > > that we more or
> > > > > less
> > > > > > agree on the facts (proliferation of e-backup LSPs) but we
> > > > > differ in
> > > > > > interpreting  the impact  of these facts  on the actual
> > > operational
> > > > > experience.
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	However, I'd like to notice that "BW
> > > effectiveness" of e-backup
> > > > > LSPs
> > > > > > is also somewhat problematic IMO.
> > > > > >
> > > > > > 	Please note that both the regular backup and e-backup
> > > > > bypass tunnels
> > > > > > cross multiple links that are not involved with the original
> > > > > set of LSPs
> > > > > > they are protecting. And they both consume BW on these
> > > > > links. The only
> > > > > > difference is that they are competing for BW with other
> > > > > LSPs, not with
> > > > > ones
> > > > > > they are protecting. But the overall effect is exactly the
> same
> > > IMO.
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	My 2c,
> > > > > >
> > > > > > 	     Sasha
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	From: Sriganesh Kini
> > > [mailto:sriganesh.kini@ericsson.com]
> > > > > > 	Sent: Monday, July 26, 2010 8:01 PM
> > > > > > 	To: Alexander Vainshtein
> > > > > > 	Cc: mpls@ietf.org
> > > > > > 	Subject: RE: [mpls] Scalability of the
> > > "effective FRR" approach
> > > > > in
> > > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	Sasha,
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	As you noted the e-backup tunnel protects all LSPs that
> > > > > have a common
> > > > > > {head-end, tail-end} pair. More precisely, the e-backup can
> > > > > be shared
> > > > > > to protect all LSPs that have a common {ring-ingress-LSR,
> > > > > ring-egress-
> > > > > > LSR} pair (that is path is disjoint with the e-backup).
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	If I understood correctly your concern is about the
> > > > > number of number
> > > > > > of e-backup tunnels?
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	E-backup tunnels should be setup based on protected
> > > > > LSP's {ring-
> > > > > > ingress, ring-egress} LSRs. Consider a typical case=20
> where in a
> > > ring,
> > > > > there is a
> > > > > > 'ring-head-end' and LSPs are setup from other LSRs on the
> > > > > ring to the
> > > > > 'ring-
> > > > > > head-end'. An e-backup should be setup from each LSR on the
> ring
> > > to
> > > > > the
> > > > > > 'ring-head-end'. This is order(n).
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	Even for cases where protected LSPs have many possible
> > > > > combinations
> > > > > > for {ring-ingress, ring-egress}, for typical ring sizes,
> > > > > the number
> > > > > > of tunnels required should not be a concern for today's
> > > > > implementations.
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	Also, in many topologies an LSR that is purely
> > > a transit for
> > > > > protected
> > > > > > LSPs, does not have to originate any e-backup.
> > > > > >
> > > > > >
> > > > > >
> > > > > > 	Thanks
> > > > > >
> > > > > > 	- Sri
> > > > > >
> > > > > > 	PS: Regular facility FRR requires more that two
> > > backup tunnels,
> > > > > > depending on what is being protected.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > >
> > > > > >
> > > > > > 		From: mpls-bounces@ietf.org [mailto:mpls-
> > > > > bounces@ietf.org] On
> > > > > > Behalf Of Alexander Vainshtein
> > > > > > 		Sent: Monday, July 26, 2010 9:57 AM
> > > > > > 		To: Sriganesh Kini
> > > > > > 		Cc: mpls@ietf.org
> > > > > > 		Subject: [mpls] Scalability of the
> > > "effective FRR"
> > > > > approach in
> > > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > > >
> > > > > > 		Sriganesh and all,
> > > > > >
> > > > > > 		If I understood you correctly, your proposal
> > > > > requires a dedicated
> > > > > > backup tunnel for all LSPs with the given {head-end,
> > > > > tail-end} pair
> > > > > > of LSRs in the ring. (Regular facility FRR requires just two
> > > backup
> > > > > tunnels).
> > > > > >
> > > > > > 		If this understanding is correct, this
> > > looks to like a
> > > > > serious
> > > > > > scalability issue with your approach.
> > > > > >
> > > > > >
> > > > > >
> > > > > > 		Regards,
> > > > > >
> > > > > > 		     Sasha
> > > > > >
> > > > > >
> > > > >
> > > > >
> > >
> =

From jdrake@juniper.net  Tue Jul 27 06:11:47 2010
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 108223A69E8 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 06:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.171
X-Spam-Level: 
X-Spam-Status: No, score=-6.171 tagged_above=-999 required=5 tests=[AWL=0.427,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 4vJF3IFZqOlo for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 06:11:42 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with ESMTP id 59BF73A6829 for <mpls@ietf.org>; Tue, 27 Jul 2010 06:11:42 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKTE7bIhEiMHPGFdqV3IzFl4ENZc9bYUzW@postini.com; Tue, 27 Jul 2010 06:12:04 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Tue, 27 Jul 2010 06:09:59 -0700
From: John E Drake <jdrake@juniper.net>
To: Yong Lucy <lucyyong@huawei.com>, Kireeti Kompella <kireeti@juniper.net>, 'Shane Amante' <shane@castlepoint.net>, "mpls@ietf.org" <mpls@ietf.org>
Date: Tue, 27 Jul 2010 06:09:56 -0700
Thread-Topic: [mpls] entropy label indicator label in draft-kompella-mpls-entropy-label
Thread-Index: Acsth0oUJSF/XWniQyWod9gx1LMJ/QABXatQ
Message-ID: <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net>
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com>
In-Reply-To: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5E893DB832F57341992548CDBB3331639844EED6E7EMBX01HQjnprn_"
MIME-Version: 1.0
Subject: Re: [mpls] entropy label indicator label in	draft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 13:11:47 -0000

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

Lucy, we discussed this and decided it was better to have the egress contro=
l the values of the ELI it advertises.  Plus, getting a reserved value woul=
d be difficult

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Yon=
g Lucy
Sent: Tuesday, July 27, 2010 5:31 AM
To: Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
Subject: [mpls] entropy label indicator label in draft-kompella-mpls-entrop=
y-label

Hi Kireeti and Shane,

Could we consider use one of reserved label for ELI purpose? This will make=
 implementation much easy, i.e. not need to keep the state for each ELI lab=
el. The approach can be used in general for RSVP-TE and BGP as well.

Regards,
Lucy




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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Lucy, we discussed this and decided it was better to have th=
e egress
control the values of the ELI it advertises.&nbsp; Plus, getting a reserved=
 value
would be difficult<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <b>On Behalf Of </b>Yo=
ng
Lucy<br>
<b>Sent:</b> Tuesday, July 27, 2010 5:31 AM<br>
<b>To:</b> Kireeti Kompella; 'Shane Amante'; mpls@ietf.org<br>
<b>Subject:</b> [mpls] entropy label indicator label in
draft-kompella-mpls-entropy-label<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'>Hi Kireeti a=
nd
Shane,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'>Could we con=
sider
use one of reserved label for ELI purpose? This will make implementation mu=
ch
easy, i.e. not need to keep the state for each ELI label. The approach can =
be
used in general for RSVP-TE and BGP as well.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'>Regards,<o:p=
></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'>Lucy<o:p></o=
:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p>

</div>

</div>

</body>

</html>

--_000_5E893DB832F57341992548CDBB3331639844EED6E7EMBX01HQjnprn_--

From lucyyong@huawei.com  Tue Jul 27 06:24:54 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E42873A69F2 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 06:24:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.546
X-Spam-Level: 
X-Spam-Status: No, score=-1.546 tagged_above=-999 required=5 tests=[AWL=1.052,  BAYES_00=-2.599, HTML_MESSAGE=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 ugKZWSy8tGlK for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 06:24:53 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 900E93A68B1 for <mpls@ietf.org>; Tue, 27 Jul 2010 06:24:53 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L6700AOOXA1LD@szxga01-in.huawei.com> for mpls@ietf.org; Tue, 27 Jul 2010 21:25:13 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L670086CXA1FM@szxga01-in.huawei.com> for mpls@ietf.org; Tue, 27 Jul 2010 21:25:13 +0800 (CST)
Received: from y736742 (dhcp-72c7.meeting.ietf.org [130.129.114.199]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L6700A01X9V0Z@szxml02-in.huawei.com>; Tue, 27 Jul 2010 21:25:13 +0800 (CST)
Date: Tue, 27 Jul 2010 08:25:09 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net>
To: 'John E Drake' <jdrake@juniper.net>, 'Kireeti Kompella' <kireeti@juniper.net>, 'Shane Amante' <shane@castlepoint.net>, mpls@ietf.org
Message-id: <034201cb2d8f$25cd0ec0$c7728182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_yOJr2BYBpiTkTg1OLBJ+Fw)"
Thread-index: Acsth0oUJSF/XWniQyWod9gx1LMJ/QABXatQAACQDfA=
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net>
Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 13:24:55 -0000

This is a multi-part message in MIME format.

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

What is the benefit for such control? Egress LSR does not use this value.

Lucy

 

  _____  

From: John E Drake [mailto:jdrake@juniper.net] 
Sent: Tuesday, July 27, 2010 8:10 AM
To: Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
Subject: RE: [mpls] entropy label indicator label
indraft-kompella-mpls-entropy-label

 

Lucy, we discussed this and decided it was better to have the egress control
the values of the ELI it advertises.  Plus, getting a reserved value would
be difficult

 

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Yong
Lucy
Sent: Tuesday, July 27, 2010 5:31 AM
To: Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
Subject: [mpls] entropy label indicator label in
draft-kompella-mpls-entropy-label

 

Hi Kireeti and Shane,

 

Could we consider use one of reserved label for ELI purpose? This will make
implementation much easy, i.e. not need to keep the state for each ELI
label. The approach can be used in general for RSVP-TE and BGP as well.

 

Regards,

Lucy

 

 

 


--Boundary_(ID_yOJr2BYBpiTkTg1OLBJ+Fw)
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="http://www.w3.org/TR/REC-html40"
xmlns:ns1="http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	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;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Calibri;
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>What is the
benefit for such control? Egress LSR does not use this value.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>Lucy<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'><o:p>&nbsp;</o:p></span></font></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<div>

<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>

<hr size=2 width="100%" align=center tabindex=-1>

</span></font></div>

<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> John E Drake
[mailto:jdrake@juniper.net] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, July 27, 2010 8:10
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Yong Lucy; Kireeti Kompella;
'Shane Amante'; mpls@ietf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [mpls] entropy label
indicator label indraft-kompella-mpls-entropy-label</span></font><o:p></o:p></p>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Lucy, we discussed
this and decided it was better to have the egress control the values of the ELI
it advertises.&nbsp; Plus, getting a reserved value would be difficult<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;</o:p></span></font></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> mpls-bounces@ietf.org
[mailto:mpls-bounces@ietf.org] <b><span style='font-weight:bold'>On Behalf Of </span></b>Yong
Lucy<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, July 27, 2010 5:31
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Kireeti Kompella; 'Shane
Amante'; mpls@ietf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [mpls] entropy label
indicator label in draft-kompella-mpls-entropy-label<o:p></o:p></span></font></p>

</div>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Hi Kireeti and Shane,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Could we consider use one of reserved label for ELI
purpose? This will make implementation much easy, i.e. not need to keep the
state for each ELI label. The approach can be used in general for RSVP-TE and
BGP as well.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Regards,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Lucy<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

</div>

</body>

</html>

--Boundary_(ID_yOJr2BYBpiTkTg1OLBJ+Fw)--

From jdrake@juniper.net  Tue Jul 27 06:34:54 2010
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AAFC3A695E for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 06:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.181
X-Spam-Level: 
X-Spam-Status: No, score=-6.181 tagged_above=-999 required=5 tests=[AWL=0.417,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 9u6836XxS4hY for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 06:34:49 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by core3.amsl.com (Postfix) with ESMTP id F18DB3A6994 for <mpls@ietf.org>; Tue, 27 Jul 2010 06:34:48 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKTE7gidBoHITZaIFbkJY7YPikjaTZvzsp@postini.com; Tue, 27 Jul 2010 06:35:11 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Tue, 27 Jul 2010 06:31:05 -0700
From: John E Drake <jdrake@juniper.net>
To: Yong Lucy <lucyyong@huawei.com>, Kireeti Kompella <kireeti@juniper.net>, 'Shane Amante' <shane@castlepoint.net>, "mpls@ietf.org" <mpls@ietf.org>
Date: Tue, 27 Jul 2010 06:31:03 -0700
Thread-Topic: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
Thread-Index: Acsth0oUJSF/XWniQyWod9gx1LMJ/QABXatQAACQDfAAACju8A==
Message-ID: <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net>
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net> <034201cb2d8f$25cd0ec0$c7728182@china.huawei.com>
In-Reply-To: <034201cb2d8f$25cd0ec0$c7728182@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5E893DB832F57341992548CDBB3331639844EED714EMBX01HQjnprn_"
MIME-Version: 1.0
Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 13:34:54 -0000

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

Lucy,

Yes it does.  That is the whole point.  That is how the egress knows whethe=
r the ingress has placed an entropy label in the stack.  (That is why we te=
rmed it the 'Entropy Label Indicator'.)

Thanks,

John

From: Yong Lucy [mailto:lucyyong@huawei.com]
Sent: Tuesday, July 27, 2010 6:25 AM
To: John E Drake; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
Subject: RE: [mpls] entropy label indicator label indraft-kompella-mpls-ent=
ropy-label

What is the benefit for such control? Egress LSR does not use this value.
Lucy

________________________________
From: John E Drake [mailto:jdrake@juniper.net]
Sent: Tuesday, July 27, 2010 8:10 AM
To: Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
Subject: RE: [mpls] entropy label indicator label indraft-kompella-mpls-ent=
ropy-label

Lucy, we discussed this and decided it was better to have the egress contro=
l the values of the ELI it advertises.  Plus, getting a reserved value woul=
d be difficult

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Yon=
g Lucy
Sent: Tuesday, July 27, 2010 5:31 AM
To: Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
Subject: [mpls] entropy label indicator label in draft-kompella-mpls-entrop=
y-label

Hi Kireeti and Shane,

Could we consider use one of reserved label for ELI purpose? This will make=
 implementation much easy, i.e. not need to keep the state for each ELI lab=
el. The approach can be used in general for RSVP-TE and BGP as well.

Regards,
Lucy




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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Courier New";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Lucy,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Yes it does.&nbsp; That is the whole point.&nbsp; That is ho=
w the egress
knows whether the ingress has placed an entropy label in the stack.&nbsp; (=
That is
why we termed it the &#8216;Entropy Label Indicator&#8217;.) <o:p></o:p></s=
pan></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Thanks,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>John<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Yong Lucy
[mailto:lucyyong@huawei.com] <br>
<b>Sent:</b> Tuesday, July 27, 2010 6:25 AM<br>
<b>To:</b> John E Drake; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org<br=
>
<b>Subject:</b> RE: [mpls] entropy label indicator label
indraft-kompella-mpls-entropy-label<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New";color:blue'>W=
hat is
the benefit for such control? Egress LSR does not use this value.<o:p></o:p=
></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New";color:blue'>L=
ucy<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New";color:blue'><=
o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> John E Drake
[mailto:jdrake@juniper.net] <br>
<b>Sent:</b> Tuesday, July 27, 2010 8:10 AM<br>
<b>To:</b> Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org<br>
<b>Subject:</b> RE: [mpls] entropy label indicator label
indraft-kompella-mpls-entropy-label</span><o:p></o:p></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Lucy, we discussed this and decided it was better to have th=
e
egress control the values of the ELI it advertises.&nbsp; Plus, getting a
reserved value would be difficult<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <b>On Behalf Of </b>Yo=
ng
Lucy<br>
<b>Sent:</b> Tuesday, July 27, 2010 5:31 AM<br>
<b>To:</b> Kireeti Kompella; 'Shane Amante'; mpls@ietf.org<br>
<b>Subject:</b> [mpls] entropy label indicator label in
draft-kompella-mpls-entropy-label<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'>Hi Kireeti a=
nd
Shane,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'>Could we con=
sider
use one of reserved label for ELI purpose? This will make implementation mu=
ch
easy, i.e. not need to keep the state for each ELI label. The approach can =
be
used in general for RSVP-TE and BGP as well.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'>Regards,<o:p=
></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'>Lucy<o:p></o=
:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p>

</div>

</div>

</div>

</div>

</body>

</html>

--_000_5E893DB832F57341992548CDBB3331639844EED714EMBX01HQjnprn_--

From eosborne@cisco.com  Tue Jul 27 06:49:04 2010
Return-Path: <eosborne@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD4BA3A6ADD for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 06:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 T9XqNm91yASp for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 06:49:02 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id A48213A6A5B for <mpls@ietf.org>; Tue, 27 Jul 2010 06:48:54 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKuATkytJV2b/2dsb2JhbACfZnGmI5tLhTYEhAmHGwwB
X-IronPort-AV: E=Sophos;i="4.55,267,1278288000"; d="scan'208";a="139725007"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rtp-iport-1.cisco.com with ESMTP; 27 Jul 2010 13:49:15 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id o6RDnFMW004273;  Tue, 27 Jul 2010 13:49:15 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 27 Jul 2010 08:49:15 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Jul 2010 08:49:12 -0500
Message-ID: <D29E470202D67745B61059870F433B540251173C@XMB-RCD-202.cisco.com>
In-Reply-To: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EDC@EUSAACMS0703.eamcs.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaAABzm8kAAAGaFoAAB6yoAAADgilAAAUKywAABic6QAASecBAAAb+9UAABmppQ
References: <D29E470202D67745B61059870F433B5402511686@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80E8F@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B5402511689@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EA0@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B54025116C2@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EDC@EUSAACMS0703.eamcs.ericsson.se>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Sriganesh Kini" <sriganesh.kini@ericsson.com>, "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 27 Jul 2010 13:49:15.0879 (UTC) FILETIME=[80C0DF70:01CB2D92]
Cc: mpls@ietf.org
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 13:49:04 -0000

> -----Original Message-----
> From: Sriganesh Kini [mailto:sriganesh.kini@ericsson.com]
> Sent: Tuesday, July 27, 2010 2:59 PM
> To: Eric Osborne (eosborne); Alexander Vainshtein
> Cc: mpls@ietf.org
> Subject: RE: [mpls] Scalability of the "effective FRR" approach in
draft-kini-
> mpls-ring-frr-facility-backup-00.txt
>=20
> Eric, the important thing to consider is the time-scale. O(seconds) of
> suboptimality (leading to O-seconds of degraded-service/packet-loss)
is NOT
> comparable to the expected packet-loss (typically sub-50msec) in the
facility
> bypass method of [MPLS-FRR] where PLR is adjacent to failure. It is
much
> higher. Do you agree?

It is obvious that O(sec) is worse than O(msec).  This is why FRR was
developed in the first place and is the factor that drives its continued
deployment. =20

But you are attacking a straw man.  We are not discussing whether FRR is
better than no FRR.  We are discussing whether draft-kini 'efficient
FRR' is better than straight-up rfc4090 FRR. =20

Actually, we're not even discussing that.  I'm happy to stipulate that
the method you have specified is, within its domain, likely to expose
you to less potential suboptimality than the FRR that exists today.  You
have O(sec) of congestion/delay exposure no matter what you do, but in
your case the time is lower. =20

You cannot claim that you will reduce or eliminate the O(msec) part of
FRR; that's laws of physics plus particulars of a given implementation.
All you can claim is that you will *reduce* the O(sec) time in some
cases.  And I agree that your draft is likely to do that.

My contention is, and always has been, that the difference here is not
worth the work (by vendor or by operator). =20




eric



>=20
> - Sri
>=20
> PS: The title of the draft says "Efficient FRR ..." so obviously it is
trying to
> improve (optimize - if you prefer that term) FRR.
>=20
> > -----Original Message-----
> > From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com]
> > Sent: Tuesday, July 27, 2010 5:30 AM
> > To: Sriganesh Kini; Alexander Vainshtein
> > Cc: mpls@ietf.org
> > Subject: RE: [mpls] Scalability of the "effective FRR"
> > approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
> >
> > Inline with EO#
> > ...
> >
> > > > The point I'm making is not that there are O(seconds) of loss,
but
> > > > O(seconds) of suboptimality.  And I'm questioning whether
> > the amount
> > > > of work you're proposing is worth it in order to minimize this
> > > > O(seconds) of suboptimality.  If the suboptimality lasted
> > for a long
> > > > time (minutes?
> > > > hours?) I think it may be worth trying to optimize away, but it
> > > > doesn't and thus IMHO isn't.
> > >
> > > [Sri] Sub-optimality can result in degraded service (see example
in
> > section 3).
> > > Preventing this in time periods close to MPLS-FRR is important.
> > >
> > > >
> > > > There are also existing mechanisms to minimize the impact of
this
> > > > suboptimality.  They include proper placement of primary
> > and backup
> > > > paths, QoS for congestion control, and path protection.  None of
> > these
> > > > are mandatory, but all of them are useful.  To me, this further
> > > > reduces the utility of the mechanism you describe.  This is, of
> > > > course, always going to be a matter of opinion.
> > >
> > > [Sri] It would be useful if you describe in detail how the
'existing
> > mechanisms'
> > > solves a specific problem such as the one described in section 3.
> >
> >
> > EO#
> > I think it's important to distinguish between 'solve' and
'optimize'.
> > You cannot eliminate L9->L8->L9 packet forwarding unless L8 simply
> > decides to drop packets when link L8-L7 goes down.  We agreed on as
> > much in an earlier email.  To me, this means you cannot 'solve' the
> > problem.
> > You can only optimize it, insofar as you can minimize the amount of
> > time that packets go L9->L8->L9 before the network makes this
> > suboptimality go away - this is the whole point of your draft.
> >
> > Also - the suboptimality you point out comprises two parts.
> > You have some time where you have additional delay, and during that
> > same amount of time you have the potential for traffic loss due to
> > congestion.  Do you agree?
> >
> > I am not claiming that existing mechanisms *solve* the problem
you've
> > pointed out.  But I hope that if you were to take my distinction
> > between solve and  optimize that you would agree that the method in
> > your draft does not solve this problem either.  Given that it takes
> > some finite amount of time to react to a failure, all any mechanism
> > can ever do is minimize the time spent in this suboptimal condition
-
> > that is, 'optimize'.
> >
> > Do you agree?  If not, we have a fundamental disagreement (probably
> > one of terminology rather than of technology) and we should sort
that
> > out first.
> >
> > I assume henceforth that you agree with my solve/optimize
distinction
> > and my view of the limitations of what can ever be done here.
> >
> > Assuming you do, then I think what you're asking is "how do existing
> > mechanisms minimize the impact of this suboptimality?"  And I think
> > the implicit question here is also "...and why do you contend that
> > these mechanisms reduce the utility of the draft-kini mechanism?"
> >
> > If that's true, then it should be pretty clear.  Any mechanism which
> > can be used to structure the network or the behavior of the network
> > such that the exposure to either the congestion or delay piece of
the
> > suboptimality is minimized optimizes things (by definition).
> >
> > All I'm contending is that these mechanisms (QoS, traffic
engineering,
> > path protection), which are common operational tools that are by and
> > large not specific to MPLS-TE, optimize enough of the suboptimality
> > away that the additional mechanisms you propose will not add much,
and
> > which will add whatever they add at a significant cost.  This is, of
> > course, necessarily an opinion rather than a hard fact.
> >
> >
> >
> >
> >
> > eric
> >
> >
> >
> > >
> > > >
> > > > And don't even get me started on "if you don't like how ring
> > networks
> > > > behave, don't build ring networks".  That's a whole
> > >
> > > [Sri] Not sure what gave you that impression.
> > >
> > > > different topic.
> > > >
> > > >
> > > >
> > > > eric
> > > >
> > > > > >
> > > > > > Also, it's not clear to me what happens in the time after
the
> > > > failure
> > > > > > but before fast-alert messages are processed at the
> > > > u-PLR.  Does the
> > > > > > PLR drop traffic until then?  Does it do inefficient
> > backup?  Is
> > > > this
> > > > > > an implementations-specific decision?
> > > > >
> > > > > Typically a protection switch at PLR should result in lower
> > overall
> > > > loss than
> > > > > completely dropping traffic. If there are very specific
> > conditions
> > > > where
> > > > > completely dropping traffic is more advantageous, it may be an
> > > > additional
> > > > > behavior.
> > > >
> > > > OK, so your desire is that the PLR locally (suboptimally)
protect
> > > > traffic until the u-PLR does its thing.
> > > >
> > > > >
> > > > > >
> > > > > > Thirdly, I'm not sure how generalizable this solution is
> > > > to a mesh
> > > > > > topology.  While it will certainly work just as well
> > > > there as in a
> > > > > > ring, it is entirely possible (and in my experience quite
> > common)
> > > > that
> > > > > > the backup tunnel does not overlap with many of the
> > > > tunnels which it
> > > > > > is protecting, and thus you do not have a problem to
> > > > solve.  As you
> > > > > > are solving a problem that is IMHO predominant only in ring
> > > > > > topologies, this mechanism is more of a specialized,
> > > > ring-optimized
> > > > > > tool than a general-purpose thing.
> > > > >
> > > > > The draft makes a statement about applicability to general
> > > > topologies
> > > > and as
> > > > > you correctly noted it works just as well. How much of
> > overlap is
> > > > there will
> > > > > vary from one network to another.
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > eric
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: mpls-bounces@ietf.org
> > [mailto:mpls-bounces@ietf.org] On
> > > > Behalf
> > > > > > Of
> > > > > > > Sriganesh Kini
> > > > > > > Sent: Tuesday, July 27, 2010 9:28 AM
> > > > > > > To: Alexander Vainshtein
> > > > > > > Cc: mpls@ietf.org
> > > > > > > Subject: Re: [mpls] Scalability of the "effective FRR"
> > > > approach in
> > > > > > draft-kini-
> > > > > > > mpls-ring-frr-facility-backup-00.txt
> > > > > > >
> > > > > > > Sasha, you are welcome.
> > > > > > >
> > > > > > > It should be noted that path computation for e-backup is
> > > > > > trivial when
> > > > > > routed
> > > > > > > along the backup. That should not impact operational
> > experience.
> > > > > > > Setup/maintenance of e-backup should be fairly
> > > > straightforward. It
> > > > > > would be
> > > > > > > helpful if you can quantify a 'proliferation'.
> > > > > > >
> > > > > > > Bandwidth can be shared between the e-backup and the
backup
> > > > tunnel.
> > > > > > > When the e-backup is routed along the backup, there should
> > > > > > not be any
> > > > > > > extra bandwidth consumed compared to [MPLS-FRR]. The
benefit
> > is
> > > > that
> > > > > > the
> > > > > > > problematic U-turn goes away.
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > - Sri
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > >
> > > > > > > 	From: Alexander Vainshtein
> > > > > > > [mailto:Alexander.Vainshtein@ecitele.com]
> > > > > > > 	Sent: Monday, July 26, 2010 11:55 PM
> > > > > > > 	To: Sriganesh Kini
> > > > > > > 	Cc: mpls@ietf.org
> > > > > > > 	Subject: RE: [mpls] Scalability of the
> > > > "effective FRR" approach
> > > > > > in
> > > > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	Sri,
> > > > > > >
> > > > > > > 	Lots of thanks for a prompt response. It seems
> > > > that we more or
> > > > > > less
> > > > > > > agree on the facts (proliferation of e-backup LSPs) but we
> > > > > > differ in
> > > > > > > interpreting  the impact  of these facts  on the actual
> > > > operational
> > > > > > experience.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	However, I'd like to notice that "BW
> > > > effectiveness" of e-backup
> > > > > > LSPs
> > > > > > > is also somewhat problematic IMO.
> > > > > > >
> > > > > > > 	Please note that both the regular backup and e-backup
> > > > > > bypass tunnels
> > > > > > > cross multiple links that are not involved with the
original
> > > > > > set of LSPs
> > > > > > > they are protecting. And they both consume BW on these
> > > > > > links. The only
> > > > > > > difference is that they are competing for BW with other
> > > > > > LSPs, not with
> > > > > > ones
> > > > > > > they are protecting. But the overall effect is exactly the
> > same
> > > > IMO.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	My 2c,
> > > > > > >
> > > > > > > 	     Sasha
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	From: Sriganesh Kini
> > > > [mailto:sriganesh.kini@ericsson.com]
> > > > > > > 	Sent: Monday, July 26, 2010 8:01 PM
> > > > > > > 	To: Alexander Vainshtein
> > > > > > > 	Cc: mpls@ietf.org
> > > > > > > 	Subject: RE: [mpls] Scalability of the
> > > > "effective FRR" approach
> > > > > > in
> > > > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	Sasha,
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	As you noted the e-backup tunnel protects all LSPs that
> > > > > > have a common
> > > > > > > {head-end, tail-end} pair. More precisely, the e-backup
can
> > > > > > be shared
> > > > > > > to protect all LSPs that have a common {ring-ingress-LSR,
> > > > > > ring-egress-
> > > > > > > LSR} pair (that is path is disjoint with the e-backup).
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	If I understood correctly your concern is about the
> > > > > > number of number
> > > > > > > of e-backup tunnels?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	E-backup tunnels should be setup based on protected
> > > > > > LSP's {ring-
> > > > > > > ingress, ring-egress} LSRs. Consider a typical case
> > where in a
> > > > ring,
> > > > > > there is a
> > > > > > > 'ring-head-end' and LSPs are setup from other LSRs on the
> > > > > > ring to the
> > > > > > 'ring-
> > > > > > > head-end'. An e-backup should be setup from each LSR on
the
> > ring
> > > > to
> > > > > > the
> > > > > > > 'ring-head-end'. This is order(n).
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	Even for cases where protected LSPs have many possible
> > > > > > combinations
> > > > > > > for {ring-ingress, ring-egress}, for typical ring sizes,
> > > > > > the number
> > > > > > > of tunnels required should not be a concern for today's
> > > > > > implementations.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	Also, in many topologies an LSR that is purely
> > > > a transit for
> > > > > > protected
> > > > > > > LSPs, does not have to originate any e-backup.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 	Thanks
> > > > > > >
> > > > > > > 	- Sri
> > > > > > >
> > > > > > > 	PS: Regular facility FRR requires more that two
> > > > backup tunnels,
> > > > > > > depending on what is being protected.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > >
> > > > > > >
> > > > > > > 		From: mpls-bounces@ietf.org [mailto:mpls-
> > > > > > bounces@ietf.org] On
> > > > > > > Behalf Of Alexander Vainshtein
> > > > > > > 		Sent: Monday, July 26, 2010 9:57 AM
> > > > > > > 		To: Sriganesh Kini
> > > > > > > 		Cc: mpls@ietf.org
> > > > > > > 		Subject: [mpls] Scalability of the
> > > > "effective FRR"
> > > > > > approach in
> > > > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > > > >
> > > > > > > 		Sriganesh and all,
> > > > > > >
> > > > > > > 		If I understood you correctly, your proposal
> > > > > > requires a dedicated
> > > > > > > backup tunnel for all LSPs with the given {head-end,
> > > > > > tail-end} pair
> > > > > > > of LSRs in the ring. (Regular facility FRR requires just
two
> > > > backup
> > > > > > tunnels).
> > > > > > >
> > > > > > > 		If this understanding is correct, this
> > > > looks to like a
> > > > > > serious
> > > > > > > scalability issue with your approach.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 		Regards,
> > > > > > >
> > > > > > > 		     Sasha
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > >
> >

From stbryant@cisco.com  Tue Jul 27 07:24:01 2010
Return-Path: <stbryant@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD4213A695E for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 07:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.537
X-Spam-Level: 
X-Spam-Status: No, score=-10.537 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 DXVmt3Sm0+T6 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 07:23:51 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 13FF73A6A02 for <mpls@ietf.org>; Tue, 27 Jul 2010 07:23:49 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAKOITkxAZnwM/2dsb2JhbACBRJ4icaYuggcLAZk2hTYEiGo
X-IronPort-AV: E=Sophos;i="4.55,268,1278288000";  d="scan'208,217";a="139789679"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 27 Jul 2010 14:24:04 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o6REO4qe004097 for <mpls@ietf.org>; Tue, 27 Jul 2010 14:24:04 GMT
Received: from dhcp-24f9.meeting.ietf.org (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o6REO2609450; Tue, 27 Jul 2010 15:24:03 +0100 (BST)
Message-ID: <4C4EEC02.2040202@cisco.com>
Date: Tue, 27 Jul 2010 15:24:02 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.7) Gecko/20100713 Lightning/1.0b2 Thunderbird/3.1.1
MIME-Version: 1.0
To: mpls@ietf.org
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com>	<5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net>	<034201cb2d8f$25cd0ec0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net>
Content-Type: multipart/alternative; boundary="------------040801090106080901090608"
Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 14:24:01 -0000

This is a multi-part message in MIME format.
--------------040801090106080901090608
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

  John

Why do you prefer to use an ELI as opposed to using a new set of FECs 
with the property that they are followed by an EL?

Stewart


On 27/07/2010 14:31, John E Drake wrote:
>
> Lucy,
>
> Yes it does.  That is the whole point.  That is how the egress knows 
> whether the ingress has placed an entropy label in the stack.  (That 
> is why we termed it the 'Entropy Label Indicator'.)
>
> Thanks,
>
> John
>
> *From:* Yong Lucy [mailto:lucyyong@huawei.com]
> *Sent:* Tuesday, July 27, 2010 6:25 AM
> *To:* John E Drake; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> *Subject:* RE: [mpls] entropy label indicator label 
> indraft-kompella-mpls-entropy-label
>
> What is the benefit for such control? Egress LSR does not use this value.
>
> Lucy
>
> ------------------------------------------------------------------------
>
> *From:* John E Drake [mailto:jdrake@juniper.net]
> *Sent:* Tuesday, July 27, 2010 8:10 AM
> *To:* Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> *Subject:* RE: [mpls] entropy label indicator label 
> indraft-kompella-mpls-entropy-label
>
> Lucy, we discussed this and decided it was better to have the egress 
> control the values of the ELI it advertises.  Plus, getting a reserved 
> value would be difficult
>
> *From:* mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] *On 
> Behalf Of *Yong Lucy
> *Sent:* Tuesday, July 27, 2010 5:31 AM
> *To:* Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> *Subject:* [mpls] entropy label indicator label in 
> draft-kompella-mpls-entropy-label
>
> Hi Kireeti and Shane,
>
> Could we consider use one of reserved label for ELI purpose? This will 
> make implementation much easy, i.e. not need to keep the state for 
> each ELI label. The approach can be used in general for RSVP-TE and 
> BGP as well.
>
> Regards,
>
> Lucy
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



--------------040801090106080901090608
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    John<br>
    <br>
    Why do you prefer to use an ELI as opposed to using a new set of
    FECs with the property that they are followed by an EL?<br>
    <br>
    Stewart<br>
    <br>
    <br>
    On 27/07/2010 14:31, John E Drake wrote:
    <blockquote
      cite="mid:5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
      <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Courier New";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
-->
</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]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Lucy,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Yes it does.&nbsp; That is the whole point.&nbsp; That is
            how the egress
            knows whether the ingress has placed an entropy label in the
            stack.&nbsp; (That is
            why we termed it the &#8216;Entropy Label Indicator&#8217;.) <o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Thanks,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">John<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <div style="border-width: medium medium medium 1.5pt;
          border-style: none none none solid; border-color:
          -moz-use-text-color -moz-use-text-color -moz-use-text-color
          blue; padding: 0in 0in 0in 4pt;">
          <div>
            <div style="border-right: medium none; border-width: 1pt
              medium medium; border-style: solid none none;
              border-color: rgb(181, 196, 223) -moz-use-text-color
              -moz-use-text-color; padding: 3pt 0in 0in;">
              <p class="MsoNormal"><b><span style="font-size: 10pt;
                    font-family:
                    &quot;Tahoma&quot;,&quot;sans-serif&quot;;">From:</span></b><span
                  style="font-size: 10pt; font-family:
                  &quot;Tahoma&quot;,&quot;sans-serif&quot;;"> Yong Lucy
                  [<a class="moz-txt-link-freetext" href="mailto:lucyyong@huawei.com">mailto:lucyyong@huawei.com</a>] <br>
                  <b>Sent:</b> Tuesday, July 27, 2010 6:25 AM<br>
                  <b>To:</b> John E Drake; Kireeti Kompella; 'Shane
                  Amante'; <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
                  <b>Subject:</b> RE: [mpls] entropy label indicator
                  label
                  indraft-kompella-mpls-entropy-label<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          <p class="MsoNormal"><span style="font-family: &quot;Courier
              New&quot;; color: blue;">What is
              the benefit for such control? Egress LSR does not use this
              value.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="font-family: &quot;Courier
              New&quot;; color: blue;">Lucy<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="font-family: &quot;Courier
              New&quot;; color: blue;"><o:p>&nbsp;</o:p></span></p>
          <div style="border-width: medium medium medium 1.5pt;
            border-style: none none none solid; border-color:
            -moz-use-text-color -moz-use-text-color -moz-use-text-color
            blue; padding: 0in 0in 0in 4pt;">
            <div>
              <div class="MsoNormal" style="text-align: center;"
                align="center">
                <hr size="2" align="center" width="100%">
              </div>
              <p class="MsoNormal"><b><span style="font-size: 10pt;
                    font-family:
                    &quot;Tahoma&quot;,&quot;sans-serif&quot;;">From:</span></b><span
                  style="font-size: 10pt; font-family:
                  &quot;Tahoma&quot;,&quot;sans-serif&quot;;"> John E
                  Drake
                  [<a class="moz-txt-link-freetext" href="mailto:jdrake@juniper.net">mailto:jdrake@juniper.net</a>] <br>
                  <b>Sent:</b> Tuesday, July 27, 2010 8:10 AM<br>
                  <b>To:</b> Yong Lucy; Kireeti Kompella; 'Shane
                  Amante'; <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
                  <b>Subject:</b> RE: [mpls] entropy label indicator
                  label
                  indraft-kompella-mpls-entropy-label</span><o:p></o:p></p>
            </div>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
            <p class="MsoNormal"><span style="font-size: 11pt;
                font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;
                color: rgb(31, 73, 125);">Lucy, we discussed this and
                decided it was better to have the
                egress control the values of the ELI it advertises.&nbsp;
                Plus, getting a
                reserved value would be difficult<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="font-size: 11pt;
                font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;
                color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
            <div style="border-width: medium medium medium 1.5pt;
              border-style: none none none solid; border-color:
              -moz-use-text-color -moz-use-text-color
              -moz-use-text-color blue; padding: 0in 0in 0in 4pt;">
              <div>
                <div style="border-right: medium none; border-width: 1pt
                  medium medium; border-style: solid none none;
                  border-color: rgb(181, 196, 223) -moz-use-text-color
                  -moz-use-text-color; padding: 3pt 0in 0in;">
                  <p class="MsoNormal"><b><span style="font-size: 10pt;
                        font-family:
                        &quot;Tahoma&quot;,&quot;sans-serif&quot;;">From:</span></b><span
                      style="font-size: 10pt; font-family:
                      &quot;Tahoma&quot;,&quot;sans-serif&quot;;">
                      <a class="moz-txt-link-abbreviated" href="mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a>
                      [<a class="moz-txt-link-freetext" href="mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>] <b>On Behalf Of </b>Yong
                      Lucy<br>
                      <b>Sent:</b> Tuesday, July 27, 2010 5:31 AM<br>
                      <b>To:</b> Kireeti Kompella; 'Shane Amante';
                      <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
                      <b>Subject:</b> [mpls] entropy label indicator
                      label in
                      draft-kompella-mpls-entropy-label<o:p></o:p></span></p>
                </div>
              </div>
              <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
              <p class="MsoNormal"><span style="font-family:
                  &quot;Courier New&quot;;">Hi Kireeti and
                  Shane,<o:p></o:p></span></p>
              <p class="MsoNormal"><span style="font-family:
                  &quot;Courier New&quot;;"><o:p>&nbsp;</o:p></span></p>
              <p class="MsoNormal"><span style="font-family:
                  &quot;Courier New&quot;;">Could we consider
                  use one of reserved label for ELI purpose? This will
                  make implementation much
                  easy, i.e. not need to keep the state for each ELI
                  label. The approach can be
                  used in general for RSVP-TE and BGP as well.<o:p></o:p></span></p>
              <p class="MsoNormal"><span style="font-family:
                  &quot;Courier New&quot;;"><o:p>&nbsp;</o:p></span></p>
              <p class="MsoNormal"><span style="font-family:
                  &quot;Courier New&quot;;">Regards,<o:p></o:p></span></p>
              <p class="MsoNormal"><span style="font-family:
                  &quot;Courier New&quot;;">Lucy<o:p></o:p></span></p>
              <p class="MsoNormal"><span style="font-family:
                  &quot;Courier New&quot;;"><o:p>&nbsp;</o:p></span></p>
              <p class="MsoNormal"><span style="font-family:
                  &quot;Courier New&quot;;"><o:p>&nbsp;</o:p></span></p>
              <p class="MsoNormal"><span style="font-family:
                  &quot;Courier New&quot;;"><o:p>&nbsp;</o:p></span></p>
            </div>
          </div>
        </div>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
mpls mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/mailman/listinfo/mpls</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------040801090106080901090608--

From kireeti@juniper.net  Tue Jul 27 07:36:43 2010
Return-Path: <kireeti@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E7AA3A6BEF for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 07:36:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U0boEqfUNYmC for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 07:36:39 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by core3.amsl.com (Postfix) with ESMTP id 2A3B63A6B86 for <mpls@ietf.org>; Tue, 27 Jul 2010 07:36:37 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKTE7vBvU+8cAcivSfE9YppL8/WQuVYIXr@postini.com; Tue, 27 Jul 2010 07:36:59 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Tue, 27 Jul 2010 07:35:28 -0700
From: Kireeti Kompella <kireeti@juniper.net>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Tue, 27 Jul 2010 07:35:27 -0700
Thread-Topic: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
Thread-Index: AcstmPUotcO+R5ZdSoSLeLMTfeNdSg==
Message-ID: <79C0A7DD-2639-42B5-9437-A115B4E5570E@juniper.net>
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net> <034201cb2d8f$25cd0ec0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net> <4C4EEC02.2040202@cisco.com>
In-Reply-To: <4C4EEC02.2040202@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] entropy label indicator label	indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 14:36:43 -0000

Hi Stewart,

On Jul 27, 2010, at 07:24 , Stewart Bryant wrote:

> John
>=20
> Why do you prefer to use an ELI as opposed to using a new set of FECs wit=
h the property that they are followed by an EL?

The ELI is a catch-all, in case there is any potential confusion that the E=
L may be interpreted as an app label.  Most app labels (PWs (via T-LDP or B=
GP), VPN labels, etc.) can easily be followed by an EL, as Shane's slides s=
howed.  No need for new FECs.

The sticky case is "naked" IP over LDP tunnels.  Do you have a suggestion t=
hat doesn't need an ELI in that case?

Thanks,
Kireeti.

> Stewart


From jdrake@juniper.net  Tue Jul 27 07:46:43 2010
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF0183A6BF9 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 07:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.192
X-Spam-Level: 
X-Spam-Status: No, score=-6.192 tagged_above=-999 required=5 tests=[AWL=0.407,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 CIf+5QsLVdye for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 07:46:42 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by core3.amsl.com (Postfix) with ESMTP id 37D4A3A6BCD for <mpls@ietf.org>; Tue, 27 Jul 2010 07:46:42 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTE7xZ4w4cYT5sBqE8kOQ7C/Yb0zJf8mi@postini.com; Tue, 27 Jul 2010 07:47:04 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Tue, 27 Jul 2010 07:35:14 -0700
From: John E Drake <jdrake@juniper.net>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Tue, 27 Jul 2010 07:35:05 -0700
Thread-Topic: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
Thread-Index: AcstmOyCxYdanrBPTMyB8HifVpjOEw==
Message-ID: <DC8AC648-5B10-402F-AA2F-D998FB6DD1E4@juniper.net>
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net> <034201cb2d8f$25cd0ec0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net> <4C4EEC02.2040202@cisco.com>
In-Reply-To: <4C4EEC02.2040202@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] entropy label indicator label	indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 14:46:44 -0000

U3Rld2FydCwNCg0KT25seSB0aGUgaW5ncmVzcyBhbmQgZWdyZXNzIG5lZWQgdG8gdW5kZXN0YW5k
IGVudHJvcHkgbGFiZWxzLCBzbyBkb2luZyBpdCB0aGlzIHdheSBtYWtlcyBpbmNyZW1lbnRhbCBk
ZXBsb3ltZW50IGVhc2llci4gIFRoZSBpbmdyZXNzIGFuZCBlZ3Jlc3MgYXJlIGFsc28gbm90IGNv
dXBsZWQgYW5kIGNhbiBiZSB1cGdyYWRlZCBzZXBhcmF0ZWx5Lg0KDQpUaGFua3MsDQoNCkpvaG4N
Cg0KU2VudCBmcm9tIG15IGlQaG9uZQ0KDQpPbiBKdWwgMjcsIDIwMTAsIGF0IDQ6MjQgUE0sICJT
dGV3YXJ0IEJyeWFudCIgPHN0YnJ5YW50QGNpc2NvLmNvbTxtYWlsdG86c3RicnlhbnRAY2lzY28u
Y29tPj4gd3JvdGU6DQoNCkpvaG4NCg0KV2h5IGRvIHlvdSBwcmVmZXIgdG8gdXNlIGFuIEVMSSBh
cyBvcHBvc2VkIHRvIHVzaW5nIGEgbmV3IHNldCBvZiBGRUNzIHdpdGggdGhlIHByb3BlcnR5IHRo
YXQgdGhleSBhcmUgZm9sbG93ZWQgYnkgYW4gRUw/DQoNClN0ZXdhcnQNCg0KDQpPbiAyNy8wNy8y
MDEwIDE0OjMxLCBKb2huIEUgRHJha2Ugd3JvdGU6DQpMdWN5LA0KDQpZZXMgaXQgZG9lcy4gIFRo
YXQgaXMgdGhlIHdob2xlIHBvaW50LiAgVGhhdCBpcyBob3cgdGhlIGVncmVzcyBrbm93cyB3aGV0
aGVyIHRoZSBpbmdyZXNzIGhhcyBwbGFjZWQgYW4gZW50cm9weSBsYWJlbCBpbiB0aGUgc3RhY2su
ICAoVGhhdCBpcyB3aHkgd2UgdGVybWVkIGl0IHRoZSDigJhFbnRyb3B5IExhYmVsIEluZGljYXRv
cuKAmS4pDQoNClRoYW5rcywNCg0KSm9obg0KDQpGcm9tOiBZb25nIEx1Y3kgWzxtYWlsdG86bHVj
eXlvbmdAaHVhd2VpLmNvbT5tYWlsdG86bHVjeXlvbmdAaHVhd2VpLmNvbV0NClNlbnQ6IFR1ZXNk
YXksIEp1bHkgMjcsIDIwMTAgNjoyNSBBTQ0KVG86IEpvaG4gRSBEcmFrZTsgS2lyZWV0aSBLb21w
ZWxsYTsgJ1NoYW5lIEFtYW50ZSc7IDxtYWlsdG86bXBsc0BpZXRmLm9yZz4gbXBsc0BpZXRmLm9y
ZzxtYWlsdG86bXBsc0BpZXRmLm9yZz4NClN1YmplY3Q6IFJFOiBbbXBsc10gZW50cm9weSBsYWJl
bCBpbmRpY2F0b3IgbGFiZWwgaW5kcmFmdC1rb21wZWxsYS1tcGxzLWVudHJvcHktbGFiZWwNCg0K
V2hhdCBpcyB0aGUgYmVuZWZpdCBmb3Igc3VjaCBjb250cm9sPyBFZ3Jlc3MgTFNSIGRvZXMgbm90
IHVzZSB0aGlzIHZhbHVlLg0KTHVjeQ0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KRnJvbTogSm9obiBFIERyYWtlIFs8bWFpbHRvOmpkcmFrZUBqdW5pcGVyLm5ldD5tYWlsdG86
amRyYWtlQGp1bmlwZXIubmV0XQ0KU2VudDogVHVlc2RheSwgSnVseSAyNywgMjAxMCA4OjEwIEFN
DQpUbzogWW9uZyBMdWN5OyBLaXJlZXRpIEtvbXBlbGxhOyAnU2hhbmUgQW1hbnRlJzsgPG1haWx0
bzptcGxzQGlldGYub3JnPiBtcGxzQGlldGYub3JnPG1haWx0bzptcGxzQGlldGYub3JnPg0KU3Vi
amVjdDogUkU6IFttcGxzXSBlbnRyb3B5IGxhYmVsIGluZGljYXRvciBsYWJlbCBpbmRyYWZ0LWtv
bXBlbGxhLW1wbHMtZW50cm9weS1sYWJlbA0KDQpMdWN5LCB3ZSBkaXNjdXNzZWQgdGhpcyBhbmQg
ZGVjaWRlZCBpdCB3YXMgYmV0dGVyIHRvIGhhdmUgdGhlIGVncmVzcyBjb250cm9sIHRoZSB2YWx1
ZXMgb2YgdGhlIEVMSSBpdCBhZHZlcnRpc2VzLiAgUGx1cywgZ2V0dGluZyBhIHJlc2VydmVkIHZh
bHVlIHdvdWxkIGJlIGRpZmZpY3VsdA0KDQpGcm9tOiA8bWFpbHRvOm1wbHMtYm91bmNlc0BpZXRm
Lm9yZz4gbXBscy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzptcGxzLWJvdW5jZXNAaWV0Zi5vcmc+
IFs8bWFpbHRvOm1wbHMtYm91bmNlc0BpZXRmLm9yZz5tYWlsdG86bXBscy1ib3VuY2VzQGlldGYu
b3JnXSBPbiBCZWhhbGYgT2YgWW9uZyBMdWN5DQpTZW50OiBUdWVzZGF5LCBKdWx5IDI3LCAyMDEw
IDU6MzEgQU0NClRvOiBLaXJlZXRpIEtvbXBlbGxhOyAnU2hhbmUgQW1hbnRlJzsgPG1haWx0bzpt
cGxzQGlldGYub3JnPiBtcGxzQGlldGYub3JnPG1haWx0bzptcGxzQGlldGYub3JnPg0KU3ViamVj
dDogW21wbHNdIGVudHJvcHkgbGFiZWwgaW5kaWNhdG9yIGxhYmVsIGluIGRyYWZ0LWtvbXBlbGxh
LW1wbHMtZW50cm9weS1sYWJlbA0KDQpIaSBLaXJlZXRpIGFuZCBTaGFuZSwNCg0KQ291bGQgd2Ug
Y29uc2lkZXIgdXNlIG9uZSBvZiByZXNlcnZlZCBsYWJlbCBmb3IgRUxJIHB1cnBvc2U/IFRoaXMg
d2lsbCBtYWtlIGltcGxlbWVudGF0aW9uIG11Y2ggZWFzeSwgaS5lLiBub3QgbmVlZCB0byBrZWVw
IHRoZSBzdGF0ZSBmb3IgZWFjaCBFTEkgbGFiZWwuIFRoZSBhcHByb2FjaCBjYW4gYmUgdXNlZCBp
biBnZW5lcmFsIGZvciBSU1ZQLVRFIGFuZCBCR1AgYXMgd2VsbC4NCg0KUmVnYXJkcywNCkx1Y3kN
Cg0KDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KbXBscyBtYWlsaW5nIGxpc3QNCjxtYWlsdG86bXBsc0BpZXRmLm9yZz5tcGxzQGlldGYub3Jn
PG1haWx0bzptcGxzQGlldGYub3JnPg0KPGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vbXBscz5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMNCg0K
DQoNCg0KLS0NCkZvciBjb3Jwb3JhdGUgbGVnYWwgaW5mb3JtYXRpb24gZ28gdG86DQoNCjxodHRw
Oi8vd3d3LmNpc2NvLmNvbS93ZWIvYWJvdXQvZG9pbmdfYnVzaW5lc3MvbGVnYWwvY3JpL2luZGV4
Lmh0bWw+aHR0cDovL3d3dy5jaXNjby5jb20vd2ViL2Fib3V0L2RvaW5nX2J1c2luZXNzL2xlZ2Fs
L2NyaS9pbmRleC5odG1sDQoNCg0KDQo8QVRUMDAwMDEuLnR4dD4NCg==

From curtis@occnc.com  Tue Jul 27 07:50:55 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 92FBD3A689F for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 07:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level: 
X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5 tests=[AWL=-1.099, BAYES_50=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 bisXs4E10RjE for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 07:50:53 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 499BC3A6BA6 for <mpls@ietf.org>; Tue, 27 Jul 2010 07:50:53 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6REpBup059259; Tue, 27 Jul 2010 10:51:11 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007271451.o6REpBup059259@harbor.orleans.occnc.com>
To: Yong Lucy <lucyyong@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 22 Jul 2010 15:19:03 CDT." <011101cb29db$22185df0$380c7c0a@china.huawei.com> 
Date: Tue, 27 Jul 2010 10:51:11 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org
Subject: Re: [mpls] draft-villamizar-mpls-tp-multipath
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 14:50:55 -0000

In message <011101cb29db$22185df0$380c7c0a@china.huawei.com>
Yong Lucy writes:
>  
> Hi Curtis,
>  
> Thank you for summarizing hashing based multipath solution in this draft.
> Share my opinion here.

Thanks for reading the draft.

> Draft Text:
>  
>    An alternate simple multipath technique uses a table
>    generally with a power of two size, and distributes the table entries
>    proportionally among component links according to the capacity of
>    each component link.
>  
>    An adaptive multipath technique is one where the traffic bound to
>    each component link is measured and the load split is adjusted
>    accordingly.   
>  
> End Text
>  
> Comment:
>  
> 1) Adjusting load over component link may cause flow reordering. 

Yes.  That is why adjustments should be minimizaed and the why
adjustments should avoid moving the same traffic back and forth if it
sits on some sort of mathematical boundary.

> 2) If a huge amount of micro flows mix with few large and long live flows,
> the load per entry can be out of balance

For a hash space size of 24 bits, 1/16,000,000 of the tiny flows will
be mixed in the same hash bucket as a large flow.  This is why large
flows can only be sized at max-component BW minus epsilon, where
epsilong depends on the hash space size.

Perhaps you haven't figured out how a very large hash space can be
supported with a modest amount of hardware.  It can.  You might want
to look at the expired optimized multipath drafts in data-tracker.
There is a little more detail there.

> 3) Measure component link load does not provide the info. for table entry
> mapping adjustment

The measurement is much finer that component link.  Again, look at the
expired optimized multipath drafts in data-tracker.

This is a solved problem.  The sections that describe how it was
successfully done a decade ago is intended only to provide an
existance proof that there is a simple solution.  There are other
solutions that make use of the same properties of the hash but build
the hardware somewhat differently than described in the OMP drafts.

> Internet traffic pattern today is different from decade or more years ago.
> Hashing works well under the condition 

Yes.  I know that.

> 1) # of flows is very large and flow IDs are statistically random; 2) flow
> BWs are pretty balanced. 

The number of flows observed within a minute interval 15 years ago was
in the millions.  Today in LAGs of tens of 10GbE, it is likely to be
in the billion range.  I am aware of this.  If 2% of the flows are
large then 2% of a billion is also large meaning that they are very
numerous.  Building core equipment support 20 million hardware entries
to handle such a case is not a good suggestion.

> Otherwise, hashing has a trouble to make even load balance.  Hashing +
> bucket mapping brings a room to deal with the unbalance if each bucket load
> is measured. 

You clearly don't understand how this works.  There is a finite
probability that too many large flows end up in the same hash bucket
but with a large hash space this probability becomes extremely small.
The consequence is modestly disruptive, a hash reseed, but the
probability of needing two consecutive reseeds is miniscule.  I've
studied this problem but didn't put anything in the draft.

> If the equipment understands flows better rather than just flow ID, more
> proactive way can apply to multipath load balance. This is why we suggest
> having large flow classification (draft-yong-pwe3-lfc-fat-pw-01)

I don't see any support at all for that.  I didn't see any signs of
support for it this morning in PWE.

I also didn't see any considerations for MPLS-TP in your draft.

This draft is about extending a current practice to support a new
requirement - having MPLS act as a server layer that can carry fully
compliant MPLS-TP client layer LSP.

> Regards,
>  
> Lucy

Curtis

From sriganesh.kini@ericsson.com  Tue Jul 27 07:57:54 2010
Return-Path: <sriganesh.kini@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F3C53A6C21 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 07:57:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.456
X-Spam-Level: 
X-Spam-Status: No, score=-3.456 tagged_above=-999 required=5 tests=[AWL=-0.857, BAYES_00=-2.599]
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 eBUz1BZq1voU for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 07:57:52 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id D027E3A6A06 for <mpls@ietf.org>; Tue, 27 Jul 2010 07:57:51 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6REw7bC004524 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Jul 2010 09:58:10 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 27 Jul 2010 10:58:07 -0400
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Date: Tue, 27 Jul 2010 10:58:03 -0400
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: Acss451Rwl5jkjLdTWWmLbBSEMenUAAAJKaAABzm8kAAAGaFoAAB6yoAAADgilAAAUKywAABic6QAASecBAAAb+9UAABmppQAAJf+zA=
Message-ID: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80FED@EUSAACMS0703.eamcs.ericsson.se>
References: <D29E470202D67745B61059870F433B5402511686@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80E8F@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B5402511689@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EA0@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B54025116C2@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EDC@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B540251173C@XMB-RCD-202.cisco.com>
In-Reply-To: <D29E470202D67745B61059870F433B540251173C@XMB-RCD-202.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 14:57:54 -0000

Eric, lets discuss this in person. Some comments inline @ [Sri]

- Sri


> -----Original Message-----
> From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com]
> Sent: Tuesday, July 27, 2010 6:49 AM
> To: Sriganesh Kini; Alexander Vainshtein
> Cc: mpls@ietf.org
> Subject: RE: [mpls] Scalability of the "effective FRR"
> approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
>
>
>
> > -----Original Message-----
> > From: Sriganesh Kini [mailto:sriganesh.kini@ericsson.com]
> > Sent: Tuesday, July 27, 2010 2:59 PM
> > To: Eric Osborne (eosborne); Alexander Vainshtein
> > Cc: mpls@ietf.org
> > Subject: RE: [mpls] Scalability of the "effective FRR" approach in
> draft-kini-
> > mpls-ring-frr-facility-backup-00.txt
> >
> > Eric, the important thing to consider is the time-scale.
> O(seconds) of
> > suboptimality (leading to O-seconds of degraded-service/packet-loss)
> is NOT
> > comparable to the expected packet-loss (typically sub-50msec) in the
> facility
> > bypass method of [MPLS-FRR] where PLR is adjacent to failure. It is
> much
> > higher. Do you agree?
>
> It is obvious that O(sec) is worse than O(msec).  This is why
> FRR was developed in the first place and is the factor that
> drives its continued deployment.
>
> But you are attacking a straw man.  We are not discussing
> whether FRR is better than no FRR.  We are discussing whether
> draft-kini 'efficient FRR' is better than straight-up rfc4090 FRR.

Correct. To be precise the proposal is to make RFC4090 FRR better when ther=
e is a U-turn.

>
> Actually, we're not even discussing that.  I'm happy to
> stipulate that the method you have specified is, within its
> domain, likely to expose you to less potential suboptimality
> than the FRR that exists today.  You have O(sec) of
> congestion/delay exposure no matter what you do, but in your
> case the time is lower.
>
> You cannot claim that you will reduce or eliminate the
> O(msec) part of FRR; that's laws of physics plus particulars
> of a given implementation.

No claim is made that violates the laws of physics !

> All you can claim is that you will *reduce* the O(sec) time
> in some cases.  And I agree that your draft is likely to do that.

Good. So let us treat this as a basis for agreement. I would also like to q=
ualify it further that in those cases the draft reduces the time to somethi=
ng that is comparable to that expected from RFC4090 FRR where PLR is adjace=
nt to failure (typically sub-50msec). Hope you agree on that too.

>
> My contention is, and always has been, that the difference
> here is not worth the work (by vendor or by operator).

If RFC4090 was worth the work so-far (by vendor and operator) it is importa=
nt to make it work in all topologies/scenarios. Rings are topologies of int=
erest in many deployments.

The work required by this draft are straightforward extensions to capabilit=
ies already present in implementations supporting RFC4090.
1. The alert mechanism builds on the alert mechanism already present in MPL=
S with a small change. A single new diagnostic code is defined for BFD.
2. The protection-switch at PLR-u closely mirrors the node protection mecha=
nism that should already exist in current FRR.
3. RSVP-TE signaling extensions uses already defined encoding of objects an=
d the association of protected to e-backup should be straightforward.

The work required by operator should also be straightforward
1. Path computation for e-backup should not need extra planning since it fo=
llows the path of the backup
2. Setup/maintenance of e-backup should be similar/same as whatever the ope=
rator uses.
3. There would be more tunnels, but the number is not a lot more for typica=
l topologies.

Recovering at head-end runs loses the nice scalability properties that back=
up tunnels provide.

>
>
>
>
> eric
>
>
>
> >
> > - Sri
> >
> > PS: The title of the draft says "Efficient FRR ..." so
> obviously it is
> trying to
> > improve (optimize - if you prefer that term) FRR.
> >
> > > -----Original Message-----
> > > From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com]
> > > Sent: Tuesday, July 27, 2010 5:30 AM
> > > To: Sriganesh Kini; Alexander Vainshtein
> > > Cc: mpls@ietf.org
> > > Subject: RE: [mpls] Scalability of the "effective FRR"
> > > approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
> > >
> > > Inline with EO#
> > > ...
> > >
> > > > > The point I'm making is not that there are O(seconds) of loss,
> but
> > > > > O(seconds) of suboptimality.  And I'm questioning whether
> > > the amount
> > > > > of work you're proposing is worth it in order to minimize this
> > > > > O(seconds) of suboptimality.  If the suboptimality lasted
> > > for a long
> > > > > time (minutes?
> > > > > hours?) I think it may be worth trying to optimize
> away, but it
> > > > > doesn't and thus IMHO isn't.
> > > >
> > > > [Sri] Sub-optimality can result in degraded service (see example
> in
> > > section 3).
> > > > Preventing this in time periods close to MPLS-FRR is important.
> > > >
> > > > >
> > > > > There are also existing mechanisms to minimize the impact of
> this
> > > > > suboptimality.  They include proper placement of primary
> > > and backup
> > > > > paths, QoS for congestion control, and path
> protection.  None of
> > > these
> > > > > are mandatory, but all of them are useful.  To me,
> this further
> > > > > reduces the utility of the mechanism you describe.
> This is, of
> > > > > course, always going to be a matter of opinion.
> > > >
> > > > [Sri] It would be useful if you describe in detail how the
> 'existing
> > > mechanisms'
> > > > solves a specific problem such as the one described in
> section 3.
> > >
> > >
> > > EO#
> > > I think it's important to distinguish between 'solve' and
> 'optimize'.
> > > You cannot eliminate L9->L8->L9 packet forwarding unless
> L8 simply
> > > decides to drop packets when link L8-L7 goes down.  We
> agreed on as
> > > much in an earlier email.  To me, this means you cannot
> 'solve' the
> > > problem.
> > > You can only optimize it, insofar as you can minimize the
> amount of
> > > time that packets go L9->L8->L9 before the network makes this
> > > suboptimality go away - this is the whole point of your draft.
> > >
> > > Also - the suboptimality you point out comprises two parts.
> > > You have some time where you have additional delay, and
> during that
> > > same amount of time you have the potential for traffic
> loss due to
> > > congestion.  Do you agree?
> > >
> > > I am not claiming that existing mechanisms *solve* the problem
> you've
> > > pointed out.  But I hope that if you were to take my distinction
> > > between solve and  optimize that you would agree that the
> method in
> > > your draft does not solve this problem either.  Given
> that it takes
> > > some finite amount of time to react to a failure, all any
> mechanism
> > > can ever do is minimize the time spent in this suboptimal
> condition
> -
> > > that is, 'optimize'.
> > >
> > > Do you agree?  If not, we have a fundamental disagreement
> (probably
> > > one of terminology rather than of technology) and we should sort
> that
> > > out first.
> > >
> > > I assume henceforth that you agree with my solve/optimize
> distinction
> > > and my view of the limitations of what can ever be done here.
> > >
> > > Assuming you do, then I think what you're asking is "how
> do existing
> > > mechanisms minimize the impact of this suboptimality?"
> And I think
> > > the implicit question here is also "...and why do you
> contend that
> > > these mechanisms reduce the utility of the draft-kini mechanism?"
> > >
> > > If that's true, then it should be pretty clear.  Any
> mechanism which
> > > can be used to structure the network or the behavior of
> the network
> > > such that the exposure to either the congestion or delay piece of
> the
> > > suboptimality is minimized optimizes things (by definition).
> > >
> > > All I'm contending is that these mechanisms (QoS, traffic
> engineering,
> > > path protection), which are common operational tools that
> are by and
> > > large not specific to MPLS-TE, optimize enough of the
> suboptimality
> > > away that the additional mechanisms you propose will not add much,
> and
> > > which will add whatever they add at a significant cost.
> This is, of
> > > course, necessarily an opinion rather than a hard fact.
> > >
> > >
> > >
> > >
> > >
> > > eric
> > >
> > >
> > >
> > > >
> > > > >
> > > > > And don't even get me started on "if you don't like how ring
> > > networks
> > > > > behave, don't build ring networks".  That's a whole
> > > >
> > > > [Sri] Not sure what gave you that impression.
> > > >
> > > > > different topic.
> > > > >
> > > > >
> > > > >
> > > > > eric
> > > > >
> > > > > > >
> > > > > > > Also, it's not clear to me what happens in the time after
> the
> > > > > failure
> > > > > > > but before fast-alert messages are processed at the
> > > > > u-PLR.  Does the
> > > > > > > PLR drop traffic until then?  Does it do inefficient
> > > backup?  Is
> > > > > this
> > > > > > > an implementations-specific decision?
> > > > > >
> > > > > > Typically a protection switch at PLR should result in lower
> > > overall
> > > > > loss than
> > > > > > completely dropping traffic. If there are very specific
> > > conditions
> > > > > where
> > > > > > completely dropping traffic is more advantageous,
> it may be an
> > > > > additional
> > > > > > behavior.
> > > > >
> > > > > OK, so your desire is that the PLR locally (suboptimally)
> protect
> > > > > traffic until the u-PLR does its thing.
> > > > >
> > > > > >
> > > > > > >
> > > > > > > Thirdly, I'm not sure how generalizable this solution is
> > > > > to a mesh
> > > > > > > topology.  While it will certainly work just as well
> > > > > there as in a
> > > > > > > ring, it is entirely possible (and in my experience quite
> > > common)
> > > > > that
> > > > > > > the backup tunnel does not overlap with many of the
> > > > > tunnels which it
> > > > > > > is protecting, and thus you do not have a problem to
> > > > > solve.  As you
> > > > > > > are solving a problem that is IMHO predominant
> only in ring
> > > > > > > topologies, this mechanism is more of a specialized,
> > > > > ring-optimized
> > > > > > > tool than a general-purpose thing.
> > > > > >
> > > > > > The draft makes a statement about applicability to general
> > > > > topologies
> > > > > and as
> > > > > > you correctly noted it works just as well. How much of
> > > overlap is
> > > > > there will
> > > > > > vary from one network to another.
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > eric
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: mpls-bounces@ietf.org
> > > [mailto:mpls-bounces@ietf.org] On
> > > > > Behalf
> > > > > > > Of
> > > > > > > > Sriganesh Kini
> > > > > > > > Sent: Tuesday, July 27, 2010 9:28 AM
> > > > > > > > To: Alexander Vainshtein
> > > > > > > > Cc: mpls@ietf.org
> > > > > > > > Subject: Re: [mpls] Scalability of the "effective FRR"
> > > > > approach in
> > > > > > > draft-kini-
> > > > > > > > mpls-ring-frr-facility-backup-00.txt
> > > > > > > >
> > > > > > > > Sasha, you are welcome.
> > > > > > > >
> > > > > > > > It should be noted that path computation for e-backup is
> > > > > > > trivial when
> > > > > > > routed
> > > > > > > > along the backup. That should not impact operational
> > > experience.
> > > > > > > > Setup/maintenance of e-backup should be fairly
> > > > > straightforward. It
> > > > > > > would be
> > > > > > > > helpful if you can quantify a 'proliferation'.
> > > > > > > >
> > > > > > > > Bandwidth can be shared between the e-backup and the
> backup
> > > > > tunnel.
> > > > > > > > When the e-backup is routed along the backup,
> there should
> > > > > > > not be any
> > > > > > > > extra bandwidth consumed compared to [MPLS-FRR]. The
> benefit
> > > is
> > > > > that
> > > > > > > the
> > > > > > > > problematic U-turn goes away.
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > - Sri
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ________________________________
> > > > > > > >
> > > > > > > >         From: Alexander Vainshtein
> > > > > > > > [mailto:Alexander.Vainshtein@ecitele.com]
> > > > > > > >         Sent: Monday, July 26, 2010 11:55 PM
> > > > > > > >         To: Sriganesh Kini
> > > > > > > >         Cc: mpls@ietf.org
> > > > > > > >         Subject: RE: [mpls] Scalability of the
> > > > > "effective FRR" approach
> > > > > > > in
> > > > > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         Sri,
> > > > > > > >
> > > > > > > >         Lots of thanks for a prompt response. It seems
> > > > > that we more or
> > > > > > > less
> > > > > > > > agree on the facts (proliferation of e-backup
> LSPs) but we
> > > > > > > differ in
> > > > > > > > interpreting  the impact  of these facts  on the actual
> > > > > operational
> > > > > > > experience.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         However, I'd like to notice that "BW
> > > > > effectiveness" of e-backup
> > > > > > > LSPs
> > > > > > > > is also somewhat problematic IMO.
> > > > > > > >
> > > > > > > >         Please note that both the regular
> backup and e-backup
> > > > > > > bypass tunnels
> > > > > > > > cross multiple links that are not involved with the
> original
> > > > > > > set of LSPs
> > > > > > > > they are protecting. And they both consume BW on these
> > > > > > > links. The only
> > > > > > > > difference is that they are competing for BW with other
> > > > > > > LSPs, not with
> > > > > > > ones
> > > > > > > > they are protecting. But the overall effect is
> exactly the
> > > same
> > > > > IMO.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         My 2c,
> > > > > > > >
> > > > > > > >              Sasha
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         From: Sriganesh Kini
> > > > > [mailto:sriganesh.kini@ericsson.com]
> > > > > > > >         Sent: Monday, July 26, 2010 8:01 PM
> > > > > > > >         To: Alexander Vainshtein
> > > > > > > >         Cc: mpls@ietf.org
> > > > > > > >         Subject: RE: [mpls] Scalability of the
> > > > > "effective FRR" approach
> > > > > > > in
> > > > > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         Sasha,
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         As you noted the e-backup tunnel
> protects all LSPs that
> > > > > > > have a common
> > > > > > > > {head-end, tail-end} pair. More precisely, the e-backup
> can
> > > > > > > be shared
> > > > > > > > to protect all LSPs that have a common
> {ring-ingress-LSR,
> > > > > > > ring-egress-
> > > > > > > > LSR} pair (that is path is disjoint with the e-backup).
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         If I understood correctly your concern
> is about the
> > > > > > > number of number
> > > > > > > > of e-backup tunnels?
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         E-backup tunnels should be setup based
> on protected
> > > > > > > LSP's {ring-
> > > > > > > > ingress, ring-egress} LSRs. Consider a typical case
> > > where in a
> > > > > ring,
> > > > > > > there is a
> > > > > > > > 'ring-head-end' and LSPs are setup from other
> LSRs on the
> > > > > > > ring to the
> > > > > > > 'ring-
> > > > > > > > head-end'. An e-backup should be setup from each LSR on
> the
> > > ring
> > > > > to
> > > > > > > the
> > > > > > > > 'ring-head-end'. This is order(n).
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         Even for cases where protected LSPs
> have many possible
> > > > > > > combinations
> > > > > > > > for {ring-ingress, ring-egress}, for typical ring sizes,
> > > > > > > the number
> > > > > > > > of tunnels required should not be a concern for today's
> > > > > > > implementations.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         Also, in many topologies an LSR that is purely
> > > > > a transit for
> > > > > > > protected
> > > > > > > > LSPs, does not have to originate any e-backup.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >         Thanks
> > > > > > > >
> > > > > > > >         - Sri
> > > > > > > >
> > > > > > > >         PS: Regular facility FRR requires more that two
> > > > > backup tunnels,
> > > > > > > > depending on what is being protected.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ________________________________
> > > > > > > >
> > > > > > > >
> > > > > > > >                 From: mpls-bounces@ietf.org
> [mailto:mpls-
> > > > > > > bounces@ietf.org] On
> > > > > > > > Behalf Of Alexander Vainshtein
> > > > > > > >                 Sent: Monday, July 26, 2010 9:57 AM
> > > > > > > >                 To: Sriganesh Kini
> > > > > > > >                 Cc: mpls@ietf.org
> > > > > > > >                 Subject: [mpls] Scalability of the
> > > > > "effective FRR"
> > > > > > > approach in
> > > > > > > > draft-kini-mpls-ring-frr-facility-backup-00.txt
> > > > > > > >
> > > > > > > >                 Sriganesh and all,
> > > > > > > >
> > > > > > > >                 If I understood you correctly,
> your proposal
> > > > > > > requires a dedicated
> > > > > > > > backup tunnel for all LSPs with the given {head-end,
> > > > > > > tail-end} pair
> > > > > > > > of LSRs in the ring. (Regular facility FRR requires just
> two
> > > > > backup
> > > > > > > tunnels).
> > > > > > > >
> > > > > > > >                 If this understanding is correct, this
> > > > > looks to like a
> > > > > > > serious
> > > > > > > > scalability issue with your approach.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >                 Regards,
> > > > > > > >
> > > > > > > >                      Sasha
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
>

From stbryant@cisco.com  Tue Jul 27 08:02:10 2010
Return-Path: <stbryant@cisco.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82A663A68DD for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 08:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.539
X-Spam-Level: 
X-Spam-Status: No, score=-10.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, 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 WJdNWek7pj5b for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 08:02:09 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 69C9D3A6C20 for <mpls@ietf.org>; Tue, 27 Jul 2010 08:02:09 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAD+STkxAZnwN/2dsb2JhbACfaHGmYYIHCwGZMoU2BIhq
X-IronPort-AV: E=Sophos;i="4.55,269,1278288000"; d="scan'208";a="139761185"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 27 Jul 2010 15:02:31 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o6RF2SZU021489; Tue, 27 Jul 2010 15:02:28 GMT
Received: from dhcp-24f9.meeting.ietf.org (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o6RF2S614034; Tue, 27 Jul 2010 16:02:28 +0100 (BST)
Message-ID: <4C4EF504.6070407@cisco.com>
Date: Tue, 27 Jul 2010 16:02:28 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.7) Gecko/20100713 Lightning/1.0b2 Thunderbird/3.1.1
MIME-Version: 1.0
To: Kireeti Kompella <kireeti@juniper.net>
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net> <034201cb2d8f$25cd0ec0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net> <4C4EEC02.2040202@cisco.com> <79C0A7DD-2639-42B5-9437-A115B4E5570E@juniper.net>
In-Reply-To: <79C0A7DD-2639-42B5-9437-A115B4E5570E@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] entropy label indicator label	indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 15:02:10 -0000

  On 27/07/2010 15:35, Kireeti Kompella wrote:
> Hi Stewart,
>
> On Jul 27, 2010, at 07:24 , Stewart Bryant wrote:
>
>> John
>>
>> Why do you prefer to use an ELI as opposed to using a new set of FECs with the property that they are followed by an EL?
> The ELI is a catch-all, in case there is any potential confusion that the EL may be interpreted as an app label.  Most app labels (PWs (via T-LDP or BGP), VPN labels, etc.) can easily be followed by an EL, as Shane's slides showed.  No need for new FECs.
>
> The sticky case is "naked" IP over LDP tunnels.  Do you have a suggestion that doesn't need an ELI in that case?
Hi Kireeti,

Well you could do this with a new IP FEC, but you would have to have 
this running on all P routers along the path and you would need to  PHP 
both the LSP and the entropy labels.

It's not clear which is worse here. Though I note that the core 
philosophy of MPLS is to signal in the control plane and not in the data 
plane.

Stewart


From lucyyong@huawei.com  Tue Jul 27 08:06:36 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B3E803A68DD for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 08:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.02
X-Spam-Level: 
X-Spam-Status: No, score=-1.02 tagged_above=-999 required=5 tests=[AWL=-0.526,  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 v5nEZ2XGb04X for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 08:06:29 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 9A9893A6862 for <mpls@ietf.org>; Tue, 27 Jul 2010 08:06:28 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L6800DZI1Z3CE@szxga02-in.huawei.com> for mpls@ietf.org; Tue, 27 Jul 2010 23:06:40 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L6800E4G1Z34U@szxga02-in.huawei.com> for mpls@ietf.org; Tue, 27 Jul 2010 23:06:39 +0800 (CST)
Received: from y736742 (dhcp-72c7.meeting.ietf.org [130.129.114.199]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L68005FT1YR6N@szxml01-in.huawei.com>; Tue, 27 Jul 2010 23:06:39 +0800 (CST)
Date: Tue, 27 Jul 2010 10:06:29 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net>
To: 'John E Drake' <jdrake@juniper.net>, 'Kireeti Kompella' <kireeti@juniper.net>, 'Shane Amante' <shane@castlepoint.net>, mpls@ietf.org
Message-id: <03ba01cb2d9d$518de440$c7728182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_uEDxsT2NsKZ4hmAEKSCuCA)"
Thread-index: Acsth0oUJSF/XWniQyWod9gx1LMJ/QABXatQAACQDfAAACju8AADEgpg
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net> <034201cb2d8f$25cd0ec0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net>
Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 15:06:36 -0000

This is a multi-part message in MIME format.

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

Hi John,

I don't get it. If egress LSR asks ingress LSR to place ELI on the stack,
the ingress can insert a unique ELI label on the stack followed by entropy
label. When packet arrives to egress LSR, the LSR will find ELI on the
stack. Why is it important for egress LSP to allocate a value for ELI
instead of using standardized value? 

 

Regards,

Lucy

 

  _____  

From: John E Drake [mailto:jdrake@juniper.net] 
Sent: Tuesday, July 27, 2010 8:31 AM
To: Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
Subject: RE: [mpls] entropy label indicator label
indraft-kompella-mpls-entropy-label

 

Lucy,

 

Yes it does.  That is the whole point.  That is how the egress knows whether
the ingress has placed an entropy label in the stack.  (That is why we
termed it the 'Entropy Label Indicator'.) 

 

Thanks,

 

John

 

From: Yong Lucy [mailto:lucyyong@huawei.com] 
Sent: Tuesday, July 27, 2010 6:25 AM
To: John E Drake; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
Subject: RE: [mpls] entropy label indicator label
indraft-kompella-mpls-entropy-label

 

What is the benefit for such control? Egress LSR does not use this value.

Lucy

 

  _____  

From: John E Drake [mailto:jdrake@juniper.net] 
Sent: Tuesday, July 27, 2010 8:10 AM
To: Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
Subject: RE: [mpls] entropy label indicator label
indraft-kompella-mpls-entropy-label

 

Lucy, we discussed this and decided it was better to have the egress control
the values of the ELI it advertises.  Plus, getting a reserved value would
be difficult

 

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Yong
Lucy
Sent: Tuesday, July 27, 2010 5:31 AM
To: Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
Subject: [mpls] entropy label indicator label in
draft-kompella-mpls-entropy-label

 

Hi Kireeti and Shane,

 

Could we consider use one of reserved label for ELI purpose? This will make
implementation much easy, i.e. not need to keep the state for each ELI
label. The approach can be used in general for RSVP-TE and BGP as well.

 

Regards,

Lucy

 

 

 


--Boundary_(ID_uEDxsT2NsKZ4hmAEKSCuCA)
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:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40"
xmlns:ns1="http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	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;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Calibri;
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Courier New";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:Calibri;
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>Hi John,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>I don&#8217;t get
it. If egress LSR asks ingress LSR to place ELI on the stack, the ingress can
insert a unique ELI label on the stack followed by entropy label. When packet
arrives to egress LSR, the LSR will find ELI on the stack. Why is it important
for egress LSP to allocate a value for ELI instead of using standardized value?
<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>Regards,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>Lucy<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'><o:p>&nbsp;</o:p></span></font></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<div>

<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>

<hr size=2 width="100%" align=center tabindex=-1>

</span></font></div>

<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> John E Drake
[mailto:jdrake@juniper.net] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, July 27, 2010 8:31
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Yong Lucy; Kireeti Kompella;
'Shane Amante'; mpls@ietf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [mpls] entropy label
indicator label indraft-kompella-mpls-entropy-label</span></font><o:p></o:p></p>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Lucy,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Yes it does.&nbsp;
That is the whole point.&nbsp; That is how the egress knows whether the ingress
has placed an entropy label in the stack.&nbsp; (That is why we termed it the
&#8216;Entropy Label Indicator&#8217;.) <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Thanks,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>John<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;</o:p></span></font></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Yong Lucy
[mailto:lucyyong@huawei.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, July 27, 2010 6:25
AM<br>
<b><span style='font-weight:bold'>To:</span></b> John E Drake; Kireeti
Kompella; 'Shane Amante'; mpls@ietf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [mpls] entropy label
indicator label indraft-kompella-mpls-entropy-label<o:p></o:p></span></font></p>

</div>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>What is the
benefit for such control? Egress LSR does not use this value.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>Lucy<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'><o:p>&nbsp;</o:p></span></font></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<div>

<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>

<hr size=2 width="100%" align=center>

</span></font></div>

<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> John E Drake
[mailto:jdrake@juniper.net] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, July 27, 2010 8:10
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Yong Lucy; Kireeti Kompella;
'Shane Amante'; mpls@ietf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [mpls] entropy label
indicator label indraft-kompella-mpls-entropy-label</span></font><o:p></o:p></p>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Lucy, we discussed
this and decided it was better to have the egress control the values of the ELI
it advertises.&nbsp; Plus, getting a reserved value would be difficult<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;</o:p></span></font></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <b><span style='font-weight:
bold'>On Behalf Of </span></b>Yong Lucy<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, July 27, 2010 5:31
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Kireeti Kompella; 'Shane
Amante'; mpls@ietf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [mpls] entropy label
indicator label in draft-kompella-mpls-entropy-label<o:p></o:p></span></font></p>

</div>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Hi Kireeti and Shane,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Could we consider use one of reserved label for ELI
purpose? This will make implementation much easy, i.e. not need to keep the
state for each ELI label. The approach can be used in general for RSVP-TE and
BGP as well.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Regards,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>Lucy<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

</div>

</div>

</div>

</body>

</html>

--Boundary_(ID_uEDxsT2NsKZ4hmAEKSCuCA)--

From AMukherjee@ixiacom.com  Tue Jul 27 07:34:08 2010
Return-Path: <AMukherjee@ixiacom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F12D53A6AD7; Tue, 27 Jul 2010 07:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.69
X-Spam-Level: 
X-Spam-Status: No, score=-0.69 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_ILLEGAL_IP=1.908]
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 SQsM4sjwv36w; Tue, 27 Jul 2010 07:34:01 -0700 (PDT)
Received: from ixqw-mail-out.ixiacom.com (ixqw-mail-out.ixiacom.com [66.77.12.12]) by core3.amsl.com (Postfix) with ESMTP id E00793A6B81; Tue, 27 Jul 2010 07:34:00 -0700 (PDT)
Received: from ixcaexch07.ixiacom.com ([fe80:0000:0000:0000:e021:fcf5:238.143.231.20]) by IXCA-HC2.ixiacom.com ([10.200.2.51]) with mapi; Tue, 27 Jul 2010 07:34:23 -0700
From: Apratim Mukherjee <AMukherjee@ixiacom.com>
To: venkatesan mahalingam <venkatflex@gmail.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, mpls <mpls@ietf.org>
Date: Tue, 27 Jul 2010 07:34:16 -0700
Thread-Topic: [mpls-tp] Query regarding MPLS P2MP ID usage
Thread-Index: AcstibGZJ/36XM+qRzOUuG2JhLIAqAADObcA
Message-ID: <716209EC190CA740BA799AC4ACCBFB5D180E3F434B@IXCAEXCH07.ixiacom.com>
References: <AANLkTimNy3X8PB-Un9cEmgKFv=EGA_PX=s_GYxKiunEv@mail.gmail.com>
In-Reply-To: <AANLkTimNy3X8PB-Un9cEmgKFv=EGA_PX=s_GYxKiunEv@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_716209EC190CA740BA799AC4ACCBFB5D180E3F434BIXCAEXCH07ixi_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 27 Jul 2010 08:35:32 -0700
Subject: Re: [mpls] [mpls-tp] Query regarding MPLS P2MP ID usage
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 14:34:09 -0000

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

My comments inline.

Regards,
Apratim
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf =
Of venkatesan mahalingam
Sent: Tuesday, July 27, 2010 6:16 PM
To: mpls-tp@ietf.org; mpls
Subject: [mpls-tp] Query regarding MPLS P2MP ID usage

Hi,

As per draft-ietf-mpls-p2mp-te-mib-09.txt<http://tools.ietf.org/html/draft-=
ietf-mpls-p2mp-te-mib-09.txt> draft, P2MP MPLS-TE MIB is extended from MPLS=
-TE-STD-MIB.

So, mplsTunnelTable table can contain the informations for both normal MPLS=
 tunnels and MPLS P2MP tunnels.
How the two entries can be differentiated, do we need to check the entry ex=
istence in the P2MP tunnel to
confirm the entry in the mplsTunnelTable is for P2MP tunnel?
[Apratim Mukherjee] Section 4.2 "As indicated in the next section, the pres=
ence of a conceptual row in the mplsTeP2mpTunnelTable of the MIB module def=
ined in this document shows that a tunnel defined in the corresponding conc=
eptual row of the mplsTunnelTable of MPLS-TE-STD-MIB

is a P2MP tunnel"

Hence , answer is yes.

 P2MP tunnel information in mplsTunnelTable is as follows:
     {
       mplsTunnelIndex              =3D 4,
       mplsTunnelInstance           =3D 0,
       mplsTunnelIngressLSRId       =3D "192.0.2.1",
       -- The tunnel egress LSR ID is used to
       -- hold the P2MP ID for the P2MP LSP tunnel
       mplsTunnelEgressLSRId        =3D 328,
       .........................
       .........................
   }


What if the mplsTunnelEgressLSRId unsigned 32 bit integer matches with the =
normal MPLS-TE tunnel's egress-id (Egress node IP address)?
Are we assuming that P2MP Id (mplsTunnelEgressLSRId) will not overlap the v=
alid IP address range?
[Apratim Mukherjee] Since the key is TunnelIndex + IngressLSRId + EgressLSR=
Id  normally this entire set would be unique.
e.g. p2p tunnel : Ingress LSR Id =3D 1.1.1.1 , Egress LSR Id =3D 2.2.2.2 , =
TunnelIndex =3D 1 .
If p2mp tunnel from same source , I expect tunnel id would be different eve=
n if by some chance Egress LSR Id were to match for p2p Egress IP and p2mp =
id ( I don't think this is the realistic case , in some cases this is same =
as Tunnel Index , in others same as Ingress LSR Id , so no chance of clash =
in those scenarios )
However , this is not made mandatory by the specifications (i.e tunnel id c=
ould be same for p2p and p2mp tunnel originating from same Ingress )

So probably the safe way to interpret this might be that the key is assumed=
 to be TunnelIndex+ IngressLSRId + EgressLSRId + rsvpTunnelType(derived fro=
m the fact whether entry exists in the derived mplsTeP2mpTunnelTable to be =
of type p2p or p2mp )


--
Best Regards,
Venkatesan Mahalingam.

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>My comments inline.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>Regards,</span><span style=3D'color:#1F497D'><o:p></o:p></span>=
</p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>Apratim</span><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] <b>On Behalf Of =
</b>venkatesan
mahalingam<br>
<b>Sent:</b> Tuesday, July 27, 2010 6:16 PM<br>
<b>To:</b> mpls-tp@ietf.org; mpls<br>
<b>Subject:</b> [mpls-tp] Query regarding MPLS P2MP ID usage<o:p></o:p></sp=
an></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=3DMsoNormal>Hi,<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>As per <a
href=3D"http://tools.ietf.org/html/draft-ietf-mpls-p2mp-te-mib-09.txt">draf=
t-ietf-mpls-p2mp-te-mib-09.txt</a>&nbsp;draft,
P2MP MPLS-TE MIB is extended from MPLS-TE-STD-MIB.<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>So, mplsTunnelTable table can contain the informations=
 for
both normal MPLS tunnels and MPLS P2MP tunnels.<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>How&nbsp;the two entries can be differentiated, do we =
need
to check the entry existence in the P2MP tunnel to <o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>confirm the entry in the mplsTunnelTable is for P2MP t=
unnel?<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew"'>[Apratim
Mukherjee] Section 4.2 &#8220;As indicated in the next section, the presenc=
e of
a conceptual row in the mplsTeP2mpTunnelTable of the MIB module defined in =
this
document shows that a tunnel defined in the corresponding conceptual row of=
</span>
<span style=3D'font-size:10.0pt;font-family:"Courier New"'>the mplsTunnelTa=
ble of
MPLS-TE-STD-MIB </span><o:p></o:p></p>

<pre>is a P2MP tunnel&#8221;<o:p></o:p></pre><pre>Hence , answer is yes.<o:=
p></o:p></pre>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;P2MP tunnel information in mplsTunnelTable is as
follows:<br>
&nbsp;&nbsp;&nbsp;&nbsp; {<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
mplsTunnelIndex&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
=3D 4,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
mplsTunnelInstance&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
=3D 0,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
mplsTunnelIngressLSRId&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D
&quot;192.0.2.1&quot;,<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; -- The tunnel egress L=
SR ID
is used to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- hold the P2MP ID for the P2MP LSP
tunnel<br>
&nbsp;<strong>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
mplsTunnelEgressLSRId&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D 328,</s=
trong><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><strong>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
.........................</strong><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><strong>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
.........................</strong><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp; }<o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>What if the mplsTunnelEgressLSRId&nbsp;unsigned 32 bit
integer matches with the normal MPLS-TE tunnel's egress-id (Egress node IP
address)?<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>Are we assuming that P2MP Id
(mplsTunnelEgressLSRId)&nbsp;will not overlap the valid IP address range?<o=
:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew"'>[Apratim
Mukherjee] Since the key is TunnelIndex + IngressLSRId + EgressLSRId &nbsp;=
normally
this entire set would be unique. <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew"'>e.g.
p2p tunnel : Ingress LSR Id =3D 1.1.1.1 , Egress LSR Id =3D 2.2.2.2 , Tunne=
lIndex =3D
1 .<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew"'>If
p2mp tunnel from same source , I expect tunnel id would be different even i=
f by
some chance Egress LSR Id were to match for p2p Egress IP and p2mp id ( I d=
on&#8217;t
think this is the realistic case , in some cases this is same as Tunnel Ind=
ex ,
in others same as Ingress LSR Id , so no chance of clash in those scenarios=
 ) &nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew"'>However
, this is not made mandatory by the specifications (i.e tunnel id could be =
same
for p2p and p2mp tunnel originating from same Ingress ) <o:p></o:p></span><=
/p>

<pre>So probably the safe way to interpret this might be that the key is as=
sumed to be TunnelIndex+ IngressLSRId + EgressLSRId + rsvpTunnelType(derive=
d from the fact whether entry exists in the derived mplsTeP2mpTunnelTable t=
o be of type p2p or p2mp ) <o:p></o:p></pre>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>-- <br>
Best Regards,<br>
Venkatesan Mahalingam.<o:p></o:p></p>

</div>

</div>

</body>

</html>

--_000_716209EC190CA740BA799AC4ACCBFB5D180E3F434BIXCAEXCH07ixi_--

From ietfc@btconnect.com  Tue Jul 27 08:37:05 2010
Return-Path: <ietfc@btconnect.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 652803A6A40; Tue, 27 Jul 2010 08:37:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level: 
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[AWL=1.101,  BAYES_00=-2.599]
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 zg9pCcLyrUXf; Tue, 27 Jul 2010 08:37:04 -0700 (PDT)
Received: from c2beaomr04.btconnect.com (c2beaomr04.btconnect.com [213.123.26.182]) by core3.amsl.com (Postfix) with ESMTP id AE6B43A68AB; Tue, 27 Jul 2010 08:37:03 -0700 (PDT)
Received: from pc6 (host86-145-196-228.range86-145.btcentralplus.com [86.145.196.228]) by c2beaomr04.btconnect.com with SMTP id CHO87250; Tue, 27 Jul 2010 16:36:57 +0100 (BST)
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=0001.0A0B0301.4C4EFD19.014A, actions=tag
Message-ID: <01eb01cb2d98$974743a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: <lberger@labn.net>, <dbrungard@att.com>, <loa@pi.nu>
References: <20100723213112.22BA83A68D3@core3.amsl.com>
Date: Tue, 27 Jul 2010 16:32:31 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Junkmail-Status: score=10/50, host=c2beaomr04.btconnect.com
X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A0B020A.4C4EFD2B.02EB,ss=1,fgs=0, ip=0.0.0.0, so=2009-07-20 21:54:04, dmn=5.7.1/2009-08-27, mode=single engine
X-Junkmail-IWF: false
Cc: mpls@ietf.org, greg.jones@itu.int, malcolm.betts@zte.com.cn, ccamp@ietf.org, adrian.farrel@huawei.com, rcallon@juniper.net
Subject: Re: [mpls] New Liaison Statement, "LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref # 036.02]"
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 15:37:05 -0000

Greg

Trimming the cc list a smidgeon ...

I notice that the message to the CCAMP list gave the files as file1087.pdf and
file1089.pdf whereas this has file1087.pdf and file1088.pdf, the last of which
gives HTTP 404; am I right in thinking that this reference to file1088.pdf is in
error?

Tom Petch


----- Original Message -----
From: "Greg Jones (ITU-T SG 15)" <tsbsg15@itu.int>
To: <lberger@labn.net>; <dbrungard@att.com>; <andrew.g.malis@verizon.com>;
<matthew.bocci@alcatel-lucent.com>; <swallow@cisco.com>; <loa@pi.nu>
Cc: <mpls@ietf.org>; <hiroshi.ota@itu.int>; <greg.jones@itu.int>;
<steve.trowbridge@alcatel-lucent.com>; <malcolm.betts@zte.com.cn>;
<ccamp@ietf.org>; <yoichi.maeda@ntt-at.co.jp>; <pwe3@ietf.org>;
<adrian.farrel@huawei.com>; <tsbsg15@itu.int>; <rcallon@juniper.net>;
<paf@cisco.com>; <stbryant@cisco.com>
Sent: Friday, July 23, 2010 11:30 PM
Subject: [mpls] New Liaison Statement, "LS218 - Comments on
draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref # 036.02]"


>
> Title: LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref #
036.02]
> Submission Date: 2010-07-23
> URL of the IETF Web page:
https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=938
> Please reply by 2010-08-16
>
> From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
> To: IETF MPLS, CCAMP and PWE3
WGs(lberger@labn.net,dbrungard@att.com,andrew.g.malis@verizon.com,matthew.bocci@
alcatel-lucent.com,swallow@cisco.com,loa@pi.nu)
> Cc: paf@cisco.com
> stbryant@cisco.com
> adrian.farrel@huawei.com
> rcallon@juniper.net
> mpls@ietf.org
> pwe3@ietf.org
> ccamp@ietf.org
> yoichi.maeda@ntt-at.co.jp
> steve.trowbridge@alcatel-lucent.com
> Reponse Contact: tsbsg15@itu.int
> greg.jones@itu.int
> hiroshi.ota@itu.int
> Technical Contact: malcolm.betts@zte.com.cn
> Kam.Lam@alcatel-lucent.com
> Purpose: For action
> Body:
> Attachment(s):
>      LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref #
036.02] - pdf body (https://datatracker.ietf.org/documents/LIAISON/file1087.pdf)
>      LS218 - Comments on draft-ietf-ccamp-mpls-tp-cp-framework-02 [Ref #
036.02] - pdf attach
(https://datatracker.ietf.org/documents/LIAISON/file1088.pdf)
>
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From db3546@att.com  Tue Jul 27 08:43:34 2010
Return-Path: <db3546@att.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 647E83A69BC; Tue, 27 Jul 2010 08:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DHOWhfYMGO-8; Tue, 27 Jul 2010 08:43:33 -0700 (PDT)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id 543613A680B; Tue, 27 Jul 2010 08:43:33 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: db3546@att.com
X-Msg-Ref: server-12.tower-167.messagelabs.com!1280245433!35772743!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 5675 invoked from network); 27 Jul 2010 15:43:54 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-12.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Jul 2010 15:43:54 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o6RFhQnh027548; Tue, 27 Jul 2010 11:43:27 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o6RFhO8c027520; Tue, 27 Jul 2010 11:43:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Jul 2010 11:43:47 -0400
Message-ID: <D6CB948F7AFD6F4881D4B4F80C8509AA07759F4C@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [CCAMP] Last call on draft-ietf-ccamp-mpls-tp-cp-framework-02.txt
Thread-Index: Acsd5KjavXnp1fQlSf+BwrHsqstq4wA1mEKgA7ml5AA=
From: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
To: "CCAMP" <ccamp@ietf.org>, <pwe3@ietf.org>, <mpls@ietf.org>
Cc: mpls-tp@ietf.org
Subject: Re: [mpls] [CCAMP] Last call on draft-ietf-ccamp-mpls-tp-cp-framework-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 15:43:34 -0000

The last call has ended.

Authors, please address the comments and update the document.

Thanks,
CCAMP Co-Chairs, PWE3 Co-Chairs, MPLS Co-Chairs

-----Original Message-----
From: BRUNGARD, DEBORAH A (ATTLABS)=20
Sent: Thursday, July 08, 2010 12:40 PM
To: CCAMP; pwe3@ietf.org; mpls@ietf.org
Cc: mpls-tp@ietf.org
Subject: FW: [CCAMP] Last call on
draft-ietf-ccamp-mpls-tp-cp-framework-02.txt

This WG Last Call will be extended to be a joint last call of the ccamp,
pwe3, and mpls wgs and the end date extended to July 26th.

Thanks,
CCAMP Co-Chairs, PWE3 Co-Chairs, MPLS Co-Chairs

-----Original Message-----
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf
Of BRUNGARD, DEBORAH A (ATTLABS)
Sent: Wednesday, July 07, 2010 10:57 AM
To: CCAMP; pwe3@ietf.org
Cc: mpls@ietf.org; mpls-tp@ietf.org
Subject: [CCAMP] Last call on
draft-ietf-ccamp-mpls-tp-cp-framework-02.txt

This begins a joint ccamp and pwe3 last call on
draft-ietf-ccamp-mpls-tp-cp-framework-02.txt:
http://www.ietf.org/id/draft-ietf-ccamp-mpls-tp-cp-framework-02.txt

The last call ends on July 21, 2010 at 24:00 UTC.

Please send comments to the ccamp and pwe3 lists.

Deborah and Andy and Matthew
_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp

From gregimirsky@gmail.com  Tue Jul 27 08:45:26 2010
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 660583A680B; Tue, 27 Jul 2010 08:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.253
X-Spam-Level: 
X-Spam-Status: No, score=-2.253 tagged_above=-999 required=5 tests=[AWL=0.345,  BAYES_00=-2.599, HTML_MESSAGE=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 HK4EvnC9Fm56; Tue, 27 Jul 2010 08:45:25 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id D26B53A69D9; Tue, 27 Jul 2010 08:45:24 -0700 (PDT)
Received: by vws10 with SMTP id 10so3903296vws.31 for <multiple recipients>; Tue, 27 Jul 2010 08:45:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=4iRYRBxJ9V8l1W+EgmHXP978q51PaV4oIrYOMHwh3pY=; b=mJsnUaGgFSA9B1lIHAdo8Edoj/CsfoHwj8o/IIq5iILC1HPPOBrCi0HRSxx5fuj2bJ tK8kIMs9JzdeLTmzGJsqOrepfi7bL6lQLFetmyceRmZ4tFeQYVW74Mbrjo6B+TjxSob3 8kmznMNaX4qHTE2NH7i5ZP05aFfv0HtqyEmUM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xYlF4wKDKTfWQwkZ0bXG8z9tjIU09XeV/VdeKS4059WZBQEDUOlOte0LwwLWnJ0qQL yFvU7L+2AmYsIQPsMS85P0Odi7/xowJ6upKjaKdae3GnxJsPpeXMPm2vh2ozHrPZGgoP +iayuZ4w7dBXNMMUAM4r0bK5Lhu38XLdxjHSU=
MIME-Version: 1.0
Received: by 10.220.90.212 with SMTP id j20mr5299350vcm.67.1280245546489; Tue,  27 Jul 2010 08:45:46 -0700 (PDT)
Received: by 10.220.86.72 with HTTP; Tue, 27 Jul 2010 08:45:46 -0700 (PDT)
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51AE5193C2@EUSAACMS0703.eamcs.ericsson.se>
References: <4BE95E75.9040406@pi.nu> <15740615FC9674499FBCE797B011623F0A42BBC0@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <60C093A41B5E45409A19D42CF7786DFD51AE5193C2@EUSAACMS0703.eamcs.ericsson.se>
Date: Tue, 27 Jul 2010 08:45:46 -0700
Message-ID: <AANLkTimyHkZ2m856Mi9WR3n9SqA0H6js2p_RbX2SpnSY@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: David Allan I <david.i.allan@ericsson.com>
Content-Type: multipart/alternative; boundary=0016e6471848062053048c6065f0
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls] Issues with draft-ietf-mplt-tp-cc-cv-rdi-01 relating to becoming a WG document...
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 15:45:26 -0000

--0016e6471848062053048c6065f0
Content-Type: text/plain; charset=ISO-8859-1

Dear Dave,
I welcome your statement:
" We will have a "profile" of BFD just like we have a "profile" of MPLS."
And the draft-ietf-mpls-tp-cc-cv-01 in many aspects clearly identifies this
superset. My concern, as we've discussed on the list, is that some BFD-base
functionality inherited by BFD-based MPLS-TP OAM not for technical reason
but for the sake of "existing implementations". Risking to repeat arguments
already made, I'd propose to make timer change possible only through
AdminDown state. Though that changes the BFD-base behavior, it would be, in
my view, appropriate for the profile.

Regards,
Greg

On Tue, Jul 27, 2010 at 12:24 AM, David Allan I
<david.i.allan@ericsson.com>wrote:

> Hi
>
> The existence of unresolved comments was raised yesterday. I thought the
> comments raised had been dealt with at the time by a post from co-author
> John Drake.....
>
> Apparently that must have been missed, Here is a reiteration....
>
> The issues raised were:
>
> 1) running BFD at a fixed operator's configurable rate.
> Nothing in the draft precludes this.
>
> 2) Unidirectional path support
> It is noted as FFS and dependent on a uni-directional BFD solution which
> would involve reviving the p2mp BFD draft. As adopting as a WG document is
> indication of intent to progress and finish the work, not a statement of
> completeness, and use of BFD is consistent with existing agreements on how
> to proceed, although a legit concern I'd assume it is not gating.
>
> 3) One mechanism that can work independently from the protection switching
> configuration.
> This comment was addressed as the modes (BFD as it exists, and BFD as
> extended for TP) have been decoupled from any suggestion of use cases.
>
> Based on comments yesterday at the mike and on the list in the past, I'd
> assume the issue folks actually have is that BFD is a superset of the
> required functionality. That comes with the territory. We will have a
> "profile" of BFD just like we have a "profile" of MPLS. It is not clear to
> me that this is well understood.
>
> Is there anything else that was missed?
> Cheers
> Dave
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

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

Dear Dave,<br>I welcome your statement:<br>&quot; We will have a &quot;prof=
ile&quot; of BFD just like we have a &quot;profile&quot; of MPLS.&quot;<br>=
And the draft-ietf-mpls-tp-cc-cv-01 in many aspects clearly identifies this=
 superset. My concern, as we&#39;ve discussed on the list, is that some BFD=
-base functionality inherited by BFD-based MPLS-TP OAM not for technical re=
ason but for the sake of &quot;existing implementations&quot;. Risking to r=
epeat arguments already made, I&#39;d propose to make timer change possible=
 only through AdminDown state. Though that changes the BFD-base behavior, i=
t would be, in my view, appropriate for the profile.<br>
<br>Regards,<br>Greg<br><br><div class=3D"gmail_quote">On Tue, Jul 27, 2010=
 at 12:24 AM, David Allan I <span dir=3D"ltr">&lt;<a href=3D"mailto:david.i=
.allan@ericsson.com">david.i.allan@ericsson.com</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-=
left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi<br>
<br>
The existence of unresolved comments was raised yesterday. I thought the co=
mments raised had been dealt with at the time by a post from co-author John=
 Drake.....<br>
<br>
Apparently that must have been missed, Here is a reiteration....<br>
<br>
The issues raised were:<br>
<br>
1) running BFD at a fixed operator&#39;s configurable rate.<br>
Nothing in the draft precludes this.<br>
<br>
2) Unidirectional path support<br>
It is noted as FFS and dependent on a uni-directional BFD solution which wo=
uld involve reviving the p2mp BFD draft. As adopting as a WG document is in=
dication of intent to progress and finish the work, not a statement of comp=
leteness, and use of BFD is consistent with existing agreements on how to p=
roceed, although a legit concern I&#39;d assume it is not gating.<br>

<br>
3) One mechanism that can work independently from the protection switching =
configuration.<br>
This comment was addressed as the modes (BFD as it exists, and BFD as exten=
ded for TP) have been decoupled from any suggestion of use cases.<br>
<br>
Based on comments yesterday at the mike and on the list in the past, I&#39;=
d assume the issue folks actually have is that BFD is a superset of the req=
uired functionality. That comes with the territory. We will have a &quot;pr=
ofile&quot; of BFD just like we have a &quot;profile&quot; of MPLS. It is n=
ot clear to me that this is well understood.<br>

<br>
Is there anything else that was missed?<br>
Cheers<br>
Dave<br>
<br>
_______________________________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>
</blockquote></div><br>

--0016e6471848062053048c6065f0--

From lucyyong@huawei.com  Tue Jul 27 09:02:09 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 655A03A681E for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 09:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.845
X-Spam-Level: 
X-Spam-Status: No, score=-0.845 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 NH1JoBjNLb7E for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 09:02:08 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id A4DA23A6926 for <mpls@ietf.org>; Tue, 27 Jul 2010 09:02:03 -0700 (PDT)
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 <0L68009K14JRP5@szxga03-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 00:02:15 +0800 (CST)
Received: from 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 <0L68000PU4JQZA@szxga03-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 00:02:14 +0800 (CST)
Received: from y736742 (dhcp-72c7.meeting.ietf.org [130.129.114.199]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L680018T4JKYS@szxml01-in.huawei.com>; Wed, 28 Jul 2010 00:02:14 +0800 (CST)
Date: Tue, 27 Jul 2010 11:02:05 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <201007271451.o6REpBup059259@harbor.orleans.occnc.com>
To: curtis@occnc.com
Message-id: <03e201cb2da5$15f4a740$c7728182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcstnDggSVfX1M1HTYqwKIZH2W6ULwABE/Eg
References: "Your message of Thu, 22 Jul 2010 15:19:03 CDT." <011101cb29db$22185df0$380c7c0a@china.huawei.com> <201007271451.o6REpBup059259@harbor.orleans.occnc.com>
Cc: mpls@ietf.org
Subject: Re: [mpls] draft-villamizar-mpls-tp-multipath
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 16:02:09 -0000

Cutis,

Please see inline.

> >
> > Comment:
> >
> > 1) Adjusting load over component link may cause flow reordering.
> 
> Yes.  That is why adjustments should be minimizaed and the why
> adjustments should avoid moving the same traffic back and forth if it
> sits on some sort of mathematical boundary.
> 
> > 2) If a huge amount of micro flows mix with few large and long live
> flows,
> > the load per entry can be out of balance
> 
> For a hash space size of 24 bits, 1/16,000,000 of the tiny flows will
> be mixed in the same hash bucket as a large flow.  This is why large
> flows can only be sized at max-component BW minus epsilon, where
> epsilong depends on the hash space size.
[LY] This is true when only hashing is used. 
> 
> Perhaps you haven't figured out how a very large hash space can be
> supported with a modest amount of hardware.  It can.  You might want
> to look at the expired optimized multipath drafts in data-tracker.
> There is a little more detail there.
[LY] hashing is stateless and provides the simple way to support the large
hash space. This is not the problem we address. 
> 
> > 3) Measure component link load does not provide the info. for table
> entry
> > mapping adjustment
> 
> The measurement is much finer that component link.  Again, look at the
> expired optimized multipath drafts in data-tracker.
> 
> This is a solved problem.  The sections that describe how it was
> successfully done a decade ago is intended only to provide an
> existance proof that there is a simple solution.  There are other
> solutions that make use of the same properties of the hash but build
> the hardware somewhat differently than described in the OMP drafts.
> 
> > Internet traffic pattern today is different from decade or more years
> ago.
> > Hashing works well under the condition
> 
> Yes.  I know that.
> 
> > 1) # of flows is very large and flow IDs are statistically random; 2)
> flow
> > BWs are pretty balanced.
> 
> The number of flows observed within a minute interval 15 years ago was
> in the millions.  Today in LAGs of tens of 10GbE, it is likely to be
> in the billion range.  I am aware of this.  If 2% of the flows are
> large then 2% of a billion is also large meaning that they are very
> numerous.  Building core equipment support 20 million hardware entries
> to handle such a case is not a good suggestion.
[LY] If large flow has the notion that its rate is about the threshold, it
is easy to count how many large flows a link can support. Be honest, we
don't see such many large flows in today's network.
For a 10x10GE link,
If 500Mbps is the threshold for large flow, the link can not take more than
200 large flows.
If 50M is the mark, the link can not take more than 2000 large flows.
If 5M is the mark, the link can not take more than 20000 large flows.

[LY] We don't think the flow with 5Mpbs belonging to large flow class. We
need to speak to reality. It seems that we can different ways to count ratio
of large flow ratio.

Regards,
Lucy


Snip



From shane@castlepoint.net  Tue Jul 27 09:22:05 2010
Return-Path: <shane@castlepoint.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A43F93A6A40 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 09:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=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 3SVsx9BKO9Lz for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 09:22:04 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id EB7A73A6880 for <mpls@ietf.org>; Tue, 27 Jul 2010 09:22:03 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 239A036817C; Tue, 27 Jul 2010 10:22:26 -0600 (MDT)
Received: from host2.tcb.net (64.78.235.218 [64.78.235.218]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Tue, 27 Jul 2010 10:22:24 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.235.218; client-port=58566; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-25--854653069
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <03ba01cb2d9d$518de440$c7728182@china.huawei.com>
Date: Tue, 27 Jul 2010 18:22:21 +0200
Message-Id: <854FD998-DD00-48F1-9682-589EBE89F27A@castlepoint.net>
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net> <034201cb2d8f$25cd0ec0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net> <03ba01cb2d9d$518de440$c7728182@china.huawei.com>
To: Yong Lucy <lucyyong@huawei.com>
X-Mailer: Apple Mail (2.1081)
Cc: mpls@ietf.org
Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 16:22:05 -0000

--Apple-Mail-25--854653069
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Lucy,

On Jul 27, 2010, at 17:06 GMT+02:00, Yong Lucy wrote:
> Hi John,
> I don=92t get it. If egress LSR asks ingress LSR to place ELI on the =
stack, the ingress can insert a unique ELI label on the stack followed =
by entropy label. When packet arrives to egress LSR, the LSR will find =
ELI on the stack. Why is it important for egress LSP to allocate a value =
for ELI instead of using standardized value?

I think John already answered this question, but I'll give it a try, as =
well.  It's really a design choice on the part of the co-authors, in an =
attempt to avoid asking the MPLS WG to allocate a reserved label from =
the very scarce reserved label space.  I would note that there are only =
8 reserved MPLS label values that are currently unassigned:
=
http://www.iana.org/assignments/mpls-label-values/mpls-label-values.xhtml

So, if we believe it's "sound engineering" to use an ELI instead of a =
reserved label -- certainly a judgement call -- then, I believe, we =
should NOT request a reserved label in order that future applications =
that have a legitimate use (or, said differently, may not be able to =
function properly without a reserved label value) have an ability to =
acquire one.

-shane



> Regards,
> Lucy
> =20
> From: John E Drake [mailto:jdrake@juniper.net]=20
> Sent: Tuesday, July 27, 2010 8:31 AM
> To: Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: RE: [mpls] entropy label indicator label =
indraft-kompella-mpls-entropy-label
> =20
> Lucy,
> =20
> Yes it does.  That is the whole point.  That is how the egress knows =
whether the ingress has placed an entropy label in the stack.  (That is =
why we termed it the =91Entropy Label Indicator=92.)
> =20
> Thanks,
> =20
> John
> =20
> From: Yong Lucy [mailto:lucyyong@huawei.com]=20
> Sent: Tuesday, July 27, 2010 6:25 AM
> To: John E Drake; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: RE: [mpls] entropy label indicator label =
indraft-kompella-mpls-entropy-label
> =20
> What is the benefit for such control? Egress LSR does not use this =
value.
> Lucy
> =20
> From: John E Drake [mailto:jdrake@juniper.net]=20
> Sent: Tuesday, July 27, 2010 8:10 AM
> To: Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: RE: [mpls] entropy label indicator label =
indraft-kompella-mpls-entropy-label
> =20
> Lucy, we discussed this and decided it was better to have the egress =
control the values of the ELI it advertises.  Plus, getting a reserved =
value would be difficult
> =20
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =
Of Yong Lucy
> Sent: Tuesday, July 27, 2010 5:31 AM
> To: Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: [mpls] entropy label indicator label in =
draft-kompella-mpls-entropy-label
> =20
> Hi Kireeti and Shane,
> =20
> Could we consider use one of reserved label for ELI purpose? This will =
make implementation much easy, i.e. not need to keep the state for each =
ELI label. The approach can be used in general for RSVP-TE and BGP as =
well.
> =20
> Regards,
> Lucy
> =20
> =20
> =20


--Apple-Mail-25--854653069
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Lucy,<div><br><div><div>On Jul 27, 2010, at 17:06 GMT+02:00, Yong Lucy =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Monaco; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"Section1" =
style=3D"page: Section1; "><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman'; "><font size=3D"3" color=3D"blue" =
face=3D"Courier New"><span style=3D"font-size: 12pt; font-family: =
'Courier New'; color: blue; ">Hi =
John,<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"3" color=3D"blue" =
face=3D"Courier New"><span style=3D"font-size: 12pt; font-family: =
'Courier New'; color: blue; ">I don=92t get it. If egress LSR asks =
ingress LSR to place ELI on the stack, the ingress can insert a unique =
ELI label on the stack followed by entropy label. When packet arrives to =
egress LSR, the LSR will find ELI on the stack. Why is it important for =
egress LSP to allocate a value for ELI instead of using standardized =
value?</span></font></div></div></div></span></blockquote><div><br></div><=
div>I think John already answered this question, but I'll give it a try, =
as well.&nbsp;&nbsp;It's really a design choice on the part of the =
co-authors, in an attempt to avoid asking the MPLS WG to allocate a =
reserved label from the very scarce reserved label space. &nbsp;I would =
note that there are only 8 reserved MPLS label values that are currently =
unassigned:</div><div><a =
href=3D"http://www.iana.org/assignments/mpls-label-values/mpls-label-value=
s.xhtml">http://www.iana.org/assignments/mpls-label-values/mpls-label-valu=
es.xhtml</a></div><div><br></div><div>So, if we believe it's "sound =
engineering" to use an ELI instead of a reserved label -- certainly a =
judgement call -- then, I believe, we should NOT request a reserved =
label in order that future applications that have a legitimate use (or, =
said differently, may not be able to function properly without a =
reserved label value) have an ability to acquire =
one.</div><div><br></div><div>-shane</div><div><br></div></div><div><br></=
div><div><br><blockquote type=3D"cite"><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple"><div class=3D"Section1" style=3D"page: Section1; "><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"3" color=3D"blue" face=3D"Courier New"><span =
style=3D"font-size: 12pt; font-family: 'Courier New'; color: blue; =
"><o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><span class=3D"Apple-style-span" =
style=3D"color: rgb(0, 0, 255); font-family: 'Courier New'; =
">Regards,</span></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman'; "><font size=3D"3" color=3D"blue" face=3D"Courier =
New"><span style=3D"font-size: 12pt; font-family: 'Courier New'; color: =
blue; ">Lucy<o:p></o:p></span></font></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman'; "><font size=3D"3" =
color=3D"blue" face=3D"Courier New"><span style=3D"font-size: 12pt; =
font-family: 'Courier New'; color: blue; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"border-top-style: =
none; border-right-style: none; border-bottom-style: none; border-width: =
initial; border-color: initial; border-left-style: solid; =
border-left-color: blue; border-left-width: 1.5pt; padding-top: 0in; =
padding-right: 0in; padding-bottom: 0in; padding-left: 4pt; "><div><div =
class=3D"MsoNormal" align=3D"center" style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; text-align: center; "><font =
size=3D"3" face=3D"Times New Roman"><span style=3D"font-size: 12pt; =
"><hr size=3D"2" width=3D"100%" align=3D"center" =
tabindex=3D"-1"></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><b><font size=3D"2" =
face=3D"Tahoma"><span style=3D"font-size: 10pt; font-family: Tahoma; =
font-weight: bold; ">From:</span></font></b><font size=3D"2" =
face=3D"Tahoma"><span style=3D"font-size: 10pt; font-family: Tahoma; =
"><span class=3D"Apple-converted-space">&nbsp;</span>John E Drake =
[mailto:jdrake@juniper.net]<span =
class=3D"Apple-converted-space">&nbsp;</span><br><b><span =
style=3D"font-weight: bold; ">Sent:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Tuesday, July 27, 2010 8:31 =
AM<br><b><span style=3D"font-weight: bold; ">To:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Yong Lucy; Kireeti =
Kompella; 'Shane Amante';<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">mpls@ietf.org</a><br><b><span style=3D"font-weight: bold; =
">Subject:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>RE: [mpls] entropy label =
indicator label =
indraft-kompella-mpls-entropy-label</span></font><o:p></o:p></div></div><d=
iv style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size: =
12pt; "><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman'; "><font size=3D"2" =
color=3D"#1f497d" face=3D"Calibri"><span style=3D"font-size: 11pt; =
font-family: Calibri; color: rgb(31, 73, 125); =
">Lucy,<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"2" color=3D"#1f497d"=
 face=3D"Calibri"><span style=3D"font-size: 11pt; font-family: Calibri; =
color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri"><span =
style=3D"font-size: 11pt; font-family: Calibri; color: rgb(31, 73, 125); =
">Yes it does.&nbsp; That is the whole point.&nbsp; That is how the =
egress knows whether the ingress has placed an entropy label in the =
stack.&nbsp; (That is why we termed it the =91Entropy Label =
Indicator=92.)<o:p></o:p></span></font></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman'; "><font size=3D"2" =
color=3D"#1f497d" face=3D"Calibri"><span style=3D"font-size: 11pt; =
font-family: Calibri; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"2" color=3D"#1f497d"=
 face=3D"Calibri"><span style=3D"font-size: 11pt; font-family: Calibri; =
color: rgb(31, 73, 125); ">Thanks,<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri"><span =
style=3D"font-size: 11pt; font-family: Calibri; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"2" color=3D"#1f497d"=
 face=3D"Calibri"><span style=3D"font-size: 11pt; font-family: Calibri; =
color: rgb(31, 73, 125); ">John<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri"><span =
style=3D"font-size: 11pt; font-family: Calibri; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"border-top-style: =
none; border-right-style: none; border-bottom-style: none; border-width: =
initial; border-color: initial; border-left-style: solid; =
border-left-color: blue; border-left-width: 1.5pt; padding-top: 0in; =
padding-right: 0in; padding-bottom: 0in; padding-left: 4pt; "><div><div =
style=3D"border-right-style: none; border-bottom-style: none; =
border-left-style: none; border-width: initial; border-color: initial; =
border-top-style: solid; border-top-color: rgb(181, 196, 223); =
border-top-width: 1pt; padding-top: 3pt; padding-right: 0in; =
padding-bottom: 0in; padding-left: 0in; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><b><font size=3D"2" =
face=3D"Tahoma"><span style=3D"font-size: 10pt; font-family: Tahoma; =
font-weight: bold; ">From:</span></font></b><font size=3D"2" =
face=3D"Tahoma"><span style=3D"font-size: 10pt; font-family: Tahoma; =
"><span class=3D"Apple-converted-space">&nbsp;</span>Yong Lucy =
[mailto:lucyyong@huawei.com]<span =
class=3D"Apple-converted-space">&nbsp;</span><br><b><span =
style=3D"font-weight: bold; ">Sent:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Tuesday, July 27, 2010 6:25 =
AM<br><b><span style=3D"font-weight: bold; ">To:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>John E Drake; Kireeti =
Kompella; 'Shane Amante';<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">mpls@ietf.org</a><br><b><span style=3D"font-weight: bold; =
">Subject:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>RE: [mpls] entropy label =
indicator label =
indraft-kompella-mpls-entropy-label<o:p></o:p></span></font></div></div></=
div><div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: =
0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New =
Roman'; "><font size=3D"3" face=3D"Times New Roman"><span =
style=3D"font-size: 12pt; "><o:p>&nbsp;</o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"3" color=3D"blue" face=3D"Courier New"><span =
style=3D"font-size: 12pt; font-family: 'Courier New'; color: blue; =
">What is the benefit for such control? Egress LSR does not use this =
value.<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"3" color=3D"blue" =
face=3D"Courier New"><span style=3D"font-size: 12pt; font-family: =
'Courier New'; color: blue; ">Lucy<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"3" color=3D"blue" face=3D"Courier New"><span =
style=3D"font-size: 12pt; font-family: 'Courier New'; color: blue; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"border-top-style: =
none; border-right-style: none; border-bottom-style: none; border-width: =
initial; border-color: initial; border-left-style: solid; =
border-left-color: blue; border-left-width: 1.5pt; padding-top: 0in; =
padding-right: 0in; padding-bottom: 0in; padding-left: 4pt; "><div><div =
class=3D"MsoNormal" align=3D"center" style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; text-align: center; "><font =
size=3D"3" face=3D"Times New Roman"><span style=3D"font-size: 12pt; =
"><hr size=3D"2" width=3D"100%" align=3D"center"></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><b><font size=3D"2" face=3D"Tahoma"><span style=3D"font-size: 10pt; =
font-family: Tahoma; font-weight: bold; ">From:</span></font></b><font =
size=3D"2" face=3D"Tahoma"><span style=3D"font-size: 10pt; font-family: =
Tahoma; "><span class=3D"Apple-converted-space">&nbsp;</span>John E =
Drake [mailto:jdrake@juniper.net]<span =
class=3D"Apple-converted-space">&nbsp;</span><br><b><span =
style=3D"font-weight: bold; ">Sent:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Tuesday, July 27, 2010 8:10 =
AM<br><b><span style=3D"font-weight: bold; ">To:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Yong Lucy; Kireeti =
Kompella; 'Shane Amante';<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">mpls@ietf.org</a><br><b><span style=3D"font-weight: bold; =
">Subject:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>RE: [mpls] entropy label =
indicator label =
indraft-kompella-mpls-entropy-label</span></font><o:p></o:p></div></div><d=
iv style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size: =
12pt; "><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman'; "><font size=3D"2" =
color=3D"#1f497d" face=3D"Calibri"><span style=3D"font-size: 11pt; =
font-family: Calibri; color: rgb(31, 73, 125); ">Lucy, we discussed this =
and decided it was better to have the egress control the values of the =
ELI it advertises.&nbsp; Plus, getting a reserved value would be =
difficult<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"2" color=3D"#1f497d"=
 face=3D"Calibri"><span style=3D"font-size: 11pt; font-family: Calibri; =
color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></font></div><div =
style=3D"border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-width: initial; border-color: initial; =
border-left-style: solid; border-left-color: blue; border-left-width: =
1.5pt; padding-top: 0in; padding-right: 0in; padding-bottom: 0in; =
padding-left: 4pt; "><div><div style=3D"border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; border-top-style: solid; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; =
padding-top: 3pt; padding-right: 0in; padding-bottom: 0in; padding-left: =
0in; "><div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: =
0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New =
Roman'; "><b><font size=3D"2" face=3D"Tahoma"><span style=3D"font-size: =
10pt; font-family: Tahoma; font-weight: bold; =
">From:</span></font></b><font size=3D"2" face=3D"Tahoma"><span =
style=3D"font-size: 10pt; font-family: Tahoma; "><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">mpls-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[mailto:mpls-bounces@ietf.org=
]<span class=3D"Apple-converted-space">&nbsp;</span><b><span =
style=3D"font-weight: bold; ">On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b>Yong =
Lucy<br><b><span style=3D"font-weight: bold; ">Sent:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Tuesday, July 27, 2010 5:31 =
AM<br><b><span style=3D"font-weight: bold; ">To:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Kireeti Kompella; 'Shane =
Amante';<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">mpls@ietf.org</a><br><b><span style=3D"font-weight: bold; =
">Subject:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>[mpls] entropy label =
indicator label in =
draft-kompella-mpls-entropy-label<o:p></o:p></span></font></div></div></di=
v><div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: =
0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New =
Roman'; "><font size=3D"3" face=3D"Times New Roman"><span =
style=3D"font-size: 12pt; "><o:p>&nbsp;</o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"3" face=3D"Courier New"><span style=3D"font-size: 12pt; =
font-family: 'Courier New'; ">Hi Kireeti and =
Shane,<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"3" face=3D"Courier =
New"><span style=3D"font-size: 12pt; font-family: 'Courier New'; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"3" face=3D"Courier =
New"><span style=3D"font-size: 12pt; font-family: 'Courier New'; ">Could =
we consider use one of reserved label for ELI purpose? This will make =
implementation much easy, i.e. not need to keep the state for each ELI =
label. The approach can be used in general for RSVP-TE and BGP as =
well.<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"3" face=3D"Courier =
New"><span style=3D"font-size: 12pt; font-family: 'Courier New'; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"3" face=3D"Courier =
New"><span style=3D"font-size: 12pt; font-family: 'Courier New'; =
">Regards,<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"3" face=3D"Courier =
New"><span style=3D"font-size: 12pt; font-family: 'Courier New'; =
">Lucy<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"3" face=3D"Courier =
New"><span style=3D"font-size: 12pt; font-family: 'Courier New'; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"3" face=3D"Courier =
New"><span style=3D"font-size: 12pt; font-family: 'Courier New'; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"3" face=3D"Courier =
New"><span style=3D"font-size: 12pt; font-family: 'Courier New'; =
"><o:p>&nbsp;</o:p></span></font></div></div></div></div></div></div></div=
></blockquote></div><br></div></body></html>=

--Apple-Mail-25--854653069--

From jdrake@juniper.net  Tue Jul 27 10:28:45 2010
Return-Path: <jdrake@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 946DC3A6A41 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 10:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.202
X-Spam-Level: 
X-Spam-Status: No, score=-6.202 tagged_above=-999 required=5 tests=[AWL=0.397,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 vP4xFFQ+NFzq for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 10:28:44 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by core3.amsl.com (Postfix) with ESMTP id E06BA3A6907 for <mpls@ietf.org>; Tue, 27 Jul 2010 10:28:43 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKTE8XYGYsD4h5aSa5a8d3tSlnIAcKOGTT@postini.com; Tue, 27 Jul 2010 10:29:06 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Tue, 27 Jul 2010 10:19:08 -0700
From: John E Drake <jdrake@juniper.net>
To: "stbryant@cisco.com" <stbryant@cisco.com>, Kireeti Kompella <kireeti@juniper.net>
Date: Tue, 27 Jul 2010 10:19:04 -0700
Thread-Topic: [mpls] entropy label indicator	label indraft-kompella-mpls-entropy-label
Thread-Index: AcstnMnJV2EDxpKDQV+D6yI8/cKAwwAEq/Kw
Message-ID: <5E893DB832F57341992548CDBB3331639845060BAB@EMBX01-HQ.jnpr.net>
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net> <034201cb2d8f$25cd0ec0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net> <4C4EEC02.2040202@cisco.com> <79C0A7DD-2639-42B5-9437-A115B4E5570E@juniper.net> <4C4EF504.6070407@cisco.com>
In-Reply-To: <4C4EF504.6070407@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] entropy label indicator	label	indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 17:28:45 -0000

The egress signals the ability to support the receipt of an entropy label a=
nd the ELI value in the control plane.

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Stewart Bryant
> Sent: Tuesday, July 27, 2010 8:02 AM
> To: Kireeti Kompella
> Cc: mpls@ietf.org
> Subject: Re: [mpls] entropy label indicator label indraft-kompella-
> mpls-entropy-label
>=20
>   On 27/07/2010 15:35, Kireeti Kompella wrote:
> > Hi Stewart,
> >
> > On Jul 27, 2010, at 07:24 , Stewart Bryant wrote:
> >
> >> John
> >>
> >> Why do you prefer to use an ELI as opposed to using a new set of
> FECs with the property that they are followed by an EL?
> > The ELI is a catch-all, in case there is any potential confusion that
> the EL may be interpreted as an app label.  Most app labels (PWs (via
> T-LDP or BGP), VPN labels, etc.) can easily be followed by an EL, as
> Shane's slides showed.  No need for new FECs.
> >
> > The sticky case is "naked" IP over LDP tunnels.  Do you have a
> suggestion that doesn't need an ELI in that case?
> Hi Kireeti,
>=20
> Well you could do this with a new IP FEC, but you would have to have
> this running on all P routers along the path and you would need to  PHP
> both the LSP and the entropy labels.
>=20
> It's not clear which is worse here. Though I note that the core
> philosophy of MPLS is to signal in the control plane and not in the
> data
> plane.
>=20
> Stewart
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From curtis@occnc.com  Tue Jul 27 12:05:15 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61DBC3A684B for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 12:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level: 
X-Spam-Status: No, score=-2.381 tagged_above=-999 required=5 tests=[AWL=0.218,  BAYES_00=-2.599]
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 1rypYuO2nW61 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 12:05:14 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 1FCD43A680F for <mpls@ietf.org>; Tue, 27 Jul 2010 12:05:14 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6RJ5Xrl069109; Tue, 27 Jul 2010 15:05:33 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007271905.o6RJ5Xrl069109@harbor.orleans.occnc.com>
To: Yong Lucy <lucyyong@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Tue, 27 Jul 2010 11:02:05 CDT." <03e201cb2da5$15f4a740$c7728182@china.huawei.com> 
Date: Tue, 27 Jul 2010 15:05:33 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org
Subject: Re: [mpls] draft-villamizar-mpls-tp-multipath
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 19:05:15 -0000

In message <03e201cb2da5$15f4a740$c7728182@china.huawei.com>
Yong Lucy writes:
>  
> Cutis,
>  
> Please see inline.
>  
> > >
> > > Comment:
> > >
> > > 1) Adjusting load over component link may cause flow reordering.
> > 
> > Yes.  That is why adjustments should be minimizaed and the why
> > adjustments should avoid moving the same traffic back and forth if it
> > sits on some sort of mathematical boundary.
> > 
> > > 2) If a huge amount of micro flows mix with few large and long live
> > flows,
> > > the load per entry can be out of balance
> > 
> > For a hash space size of 24 bits, 1/16,000,000 of the tiny flows will
> > be mixed in the same hash bucket as a large flow.  This is why large
> > flows can only be sized at max-component BW minus epsilon, where
> > epsilong depends on the hash space size.
> [LY] This is true when only hashing is used. 
> > 
> > Perhaps you haven't figured out how a very large hash space can be
> > supported with a modest amount of hardware.  It can.  You might want
> > to look at the expired optimized multipath drafts in data-tracker.
> > There is a little more detail there.
> [LY] hashing is stateless and provides the simple way to support the large
> hash space. This is not the problem we address. 

This thread is not about your draft.  It is about a draft which
extends an existing widely implemented technique used with MPLS and
multipath to support MPLS-TP.

> > > 3) Measure component link load does not provide the info. for table
> > entry
> > > mapping adjustment
> > 
> > The measurement is much finer that component link.  Again, look at the
> > expired optimized multipath drafts in data-tracker.
> > 
> > This is a solved problem.  The sections that describe how it was
> > successfully done a decade ago is intended only to provide an
> > existance proof that there is a simple solution.  There are other
> > solutions that make use of the same properties of the hash but build
> > the hardware somewhat differently than described in the OMP drafts.
> > 
> > > Internet traffic pattern today is different from decade or more years
> > ago.
> > > Hashing works well under the condition
> > 
> > Yes.  I know that.
> > 
> > > 1) # of flows is very large and flow IDs are statistically random; 2)
> > flow
> > > BWs are pretty balanced.
> > 
> > The number of flows observed within a minute interval 15 years ago was
> > in the millions.  Today in LAGs of tens of 10GbE, it is likely to be
> > in the billion range.  I am aware of this.  If 2% of the flows are
> > large then 2% of a billion is also large meaning that they are very
> > numerous.  Building core equipment support 20 million hardware entries
> > to handle such a case is not a good suggestion.
> [LY] If large flow has the notion that its rate is about the threshold, it
> is easy to count how many large flows a link can support. Be honest, we
> don't see such many large flows in today's network.
> For a 10x10GE link,
> If 500Mbps is the threshold for large flow, the link can not take more than
> 200 large flows.

500 Mbps x 200 is 100Gb/s is the whole 10x10G.

> If 50M is the mark, the link can not take more than 2000 large flows.

50 Mbps x 2000 is 100Gb/s is the whole 10x10G.

> If 5M is the mark, the link can not take more than 20000 large flows.

5 Mbps x 20000 is 100Gb/s is the whole 10x10G.

So total is 300G.  Is something wrong with your math here?

The large flows come and go.  A flow for an enterprise VPN may be
small all day and then run a database backup.  They are not going to
signal any LSP differently before this happens.  In the core the PW
LSP associated with this flow may be inside another MPLS LSP used to
improve network scalability.  Most likely the PW with be inside an LDP
LSP which is inside a TE LSP in the core.

> [LY] We don't think the flow with 5Mpbs belonging to large flow class. We
> need to speak to reality. It seems that we can different ways to count ratio
> of large flow ratio.

Once again, this is not about your draft.  Start another thread for
that.  This is about small changes to an existing MPLS technique that
allow MPLS (without the TP) to be used as a server layer for MPLS-TP.
There is no signaling of large or small flows so that topic is
irrelevant to this draft.

Curtis

From sriganesh.kini@ericsson.com  Tue Jul 27 14:55:03 2010
Return-Path: <sriganesh.kini@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D61763A696C for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 14:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.265
X-Spam-Level: 
X-Spam-Status: No, score=-3.265 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, HTML_MESSAGE=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 Q7o9yKdR7PAv for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 14:55:02 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 303523A6968 for <mpls@ietf.org>; Tue, 27 Jul 2010 14:55:01 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6RLtJqa000891 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Jul 2010 16:55:20 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 27 Jul 2010 17:55:19 -0400
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
To: Greg Mirsky <gregimirsky@gmail.com>, "Eric Osborne (eosborne)" <eosborne@cisco.com>
Date: Tue, 27 Jul 2010 17:55:17 -0400
Thread-Topic: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
Thread-Index: AcstpaArRgpTPPT8Q+6rwjDrMtBpaAAMJmPQ
Message-ID: <5A5E55DF96F73844AF7DFB0F48721F0F567DB813EE@EUSAACMS0703.eamcs.ericsson.se>
References: <D29E470202D67745B61059870F433B5402511686@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80E8F@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B5402511689@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EA0@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B54025116C2@XMB-RCD-202.cisco.com> <5A5E55DF96F73844AF7DFB0F48721F0F567DB80EDC@EUSAACMS0703.eamcs.ericsson.se> <D29E470202D67745B61059870F433B540251173C@XMB-RCD-202.cisco.com> <AANLkTimEWbL5NU_j2SG8Bx4-5AbVT5otPF_--pHKKWUo@mail.gmail.com>
In-Reply-To: <AANLkTimEWbL5NU_j2SG8Bx4-5AbVT5otPF_--pHKKWUo@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5A5E55DF96F73844AF7DFB0F48721F0F567DB813EEEUSAACMS0703e_"
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-kini-mpls-ring-frr-facility-backup-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 21:55:04 -0000

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

[Re-send due to mail size issues]

Greg,

Couple comments
1. FLA should be do-able in firmware, if hardware is inflexible.
2. Do you have any evidence to support your observation that deploying path=
 and segment protection would run into lesser issues than the ones you are =
presuming.


- Sri



________________________________
From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: Tuesday, July 27, 2010 9:06 AM
To: Eric Osborne (eosborne)
Cc: Sriganesh Kini; Alexander Vainshtein; mpls@ietf.org
Subject: Re: [mpls] Scalability of the "effective FRR" approach in draft-ki=
ni-mpls-ring-frr-facility-backup-00.txt

Dear Eric,
as a developer I share your concerns regarding advantages of proposed chang=
es (I consider Fast LSA Alert and Efficient FRR in combination as latter de=
pends on the former). It would be helpful to hear opinions of providers whe=
ther they would be ready to accept risks and possibly go through fork-lift =
upgrades of existing equipment (to support FLA) in order to improve FRR. To=
 me there's not enough benefit to justify risks and troubles (note that het=
erogeneous environment might require extensions to IGP-TEs). I'd rather sug=
gest deployment of Path and Segment protection schemes if inefficiency of F=
RR's backup is the major problem for an operator.

Regards,
Greg

On Tue, Jul 27, 2010 at 6:49 AM, Eric Osborne (eosborne) <eosborne@cisco.co=
m<mailto:eosborne@cisco.com>> wrote:


> -----Original Message-----
> From: Sriganesh Kini [mailto:sriganesh.kini@ericsson.com<mailto:sriganesh=
.kini@ericsson.com>]
> Sent: Tuesday, July 27, 2010 2:59 PM
> To: Eric Osborne (eosborne); Alexander Vainshtein
> Cc: mpls@ietf.org<mailto:mpls@ietf.org>
> Subject: RE: [mpls] Scalability of the "effective FRR" approach in
draft-kini-
> mpls-ring-frr-facility-backup-00.txt
>
> Eric, the important thing to consider is the time-scale. O(seconds) of
> suboptimality (leading to O-seconds of degraded-service/packet-loss)
is NOT
> comparable to the expected packet-loss (typically sub-50msec) in the
facility
> bypass method of [MPLS-FRR] where PLR is adjacent to failure. It is
much
> higher. Do you agree?

It is obvious that O(sec) is worse than O(msec).  This is why FRR was
developed in the first place and is the factor that drives its continued
deployment.

But you are attacking a straw man.  We are not discussing whether FRR is
better than no FRR.  We are discussing whether draft-kini 'efficient
FRR' is better than straight-up rfc4090 FRR.

Actually, we're not even discussing that.  I'm happy to stipulate that
the method you have specified is, within its domain, likely to expose
you to less potential suboptimality than the FRR that exists today.  You
have O(sec) of congestion/delay exposure no matter what you do, but in
your case the time is lower.

You cannot claim that you will reduce or eliminate the O(msec) part of
FRR; that's laws of physics plus particulars of a given implementation.
All you can claim is that you will *reduce* the O(sec) time in some
cases.  And I agree that your draft is likely to do that.

My contention is, and always has been, that the difference here is not
worth the work (by vendor or by operator).




eric



>
> - Sri
>
> PS: The title of the draft says "Efficient FRR ..." so obviously it is
trying to
> improve (optimize - if you prefer that term) FRR.
>
> > -----Original Message-----

[Sri ] [---- deleted mail --------]

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18470" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D256041816-27072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><SPAN class=3D510025421-27072010>[Re-send due to m=
ail size=20
issues]</SPAN></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D256041816-27072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><SPAN=20
class=3D510025421-27072010></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D256041816-27072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Greg,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D256041816-27072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D256041816-27072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Couple comments</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D256041816-27072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>1.&nbsp;FLA should be do-able in firmware, if hard=
ware is=20
inflexible.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D256041816-27072010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>2. Do you have any evidence to=20
support&nbsp;your&nbsp;observation that&nbsp;deploying path and segment=20
protection would&nbsp;run into&nbsp;lesser issues than the ones you are=20
presuming.&nbsp;</FONT></SPAN></DIV><!-- Converted from text/rtf format -->=
</DIV>
<DIV>&nbsp;</DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>- Sri</FONT></SPAN> </P>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Greg Mirsky=20
  [mailto:gregimirsky@gmail.com] <BR><B>Sent:</B> Tuesday, July 27, 2010 9:=
06=20
  AM<BR><B>To:</B> Eric Osborne (eosborne)<BR><B>Cc:</B> Sriganesh Kini;=20
  Alexander Vainshtein; mpls@ietf.org<BR><B>Subject:</B> Re: [mpls] Scalabi=
lity=20
  of the "effective FRR" approach in=20
  draft-kini-mpls-ring-frr-facility-backup-00.txt<BR></FONT><BR></DIV>
  <DIV></DIV>Dear Eric,<BR>as a developer I share your concerns regarding=20
  advantages of proposed changes (I consider Fast LSA Alert and Efficient F=
RR in=20
  combination as latter depends on the former). It would be helpful to hear=
=20
  opinions of providers whether they would be ready to accept risks and pos=
sibly=20
  go through fork-lift upgrades of existing equipment (to support FLA) in o=
rder=20
  to improve FRR. To me there's not enough benefit to justify risks and tro=
ubles=20
  (note that heterogeneous environment might require extensions to IGP-TEs)=
. I'd=20
  rather suggest deployment of Path and Segment protection schemes if=20
  inefficiency of FRR's backup is the major problem for an=20
  operator.<BR><BR>Regards,<BR>Greg<BR><BR>
  <DIV class=3Dgmail_quote>On Tue, Jul 27, 2010 at 6:49 AM, Eric Osborne=20
  (eosborne) <SPAN dir=3Dltr>&lt;<A=20
  href=3D"mailto:eosborne@cisco.com">eosborne@cisco.com</A>&gt;</SPAN> wrot=
e:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
04,204,204) 1px solid">
    <DIV class=3Dim><BR><BR>&gt; -----Original Message-----<BR>&gt; From:=20
    Sriganesh Kini [mailto:<A=20
    href=3D"mailto:sriganesh.kini@ericsson.com">sriganesh.kini@ericsson.com=
</A>]<BR></DIV>
    <DIV class=3Dim>&gt; Sent: Tuesday, July 27, 2010 2:59 PM<BR>&gt; To: E=
ric=20
    Osborne (eosborne); Alexander Vainshtein<BR>&gt; Cc: <A=20
    href=3D"mailto:mpls@ietf.org">mpls@ietf.org</A><BR>&gt; Subject: RE: [m=
pls]=20
    Scalability of the "effective FRR" approach in<BR>draft-kini-<BR>&gt;=20
    mpls-ring-frr-facility-backup-00.txt<BR>&gt;<BR></DIV>
    <DIV class=3Dim>&gt; Eric, the important thing to consider is the time-=
scale.=20
    O(seconds) of<BR>&gt; suboptimality (leading to O-seconds of=20
    degraded-service/packet-loss)<BR>is NOT<BR>&gt; comparable to the expec=
ted=20
    packet-loss (typically sub-50msec) in the<BR>facility<BR>&gt; bypass me=
thod=20
    of [MPLS-FRR] where PLR is adjacent to failure. It is<BR>much<BR>&gt;=20
    higher. Do you agree?<BR><BR></DIV>It is obvious that O(sec) is worse t=
han=20
    O(msec). &nbsp;This is why FRR was<BR>developed in the first place and =
is=20
    the factor that drives its continued<BR>deployment.<BR><BR>But you are=
=20
    attacking a straw man. &nbsp;We are not discussing whether FRR is<BR>be=
tter=20
    than no FRR. &nbsp;We are discussing whether draft-kini 'efficient<BR>F=
RR'=20
    is better than straight-up rfc4090 FRR.<BR><BR>Actually, we're not even=
=20
    discussing that. &nbsp;I'm happy to stipulate that<BR>the method you ha=
ve=20
    specified is, within its domain, likely to expose<BR>you to less potent=
ial=20
    suboptimality than the FRR that exists today. &nbsp;You<BR>have O(sec) =
of=20
    congestion/delay exposure no matter what you do, but in<BR>your case th=
e=20
    time is lower.<BR><BR>You cannot claim that you will reduce or eliminat=
e the=20
    O(msec) part of<BR>FRR; that's laws of physics plus particulars of a gi=
ven=20
    implementation.<BR>All you can claim is that you will *reduce* the O(se=
c)=20
    time in some<BR>cases. &nbsp;And I agree that your draft is likely to d=
o=20
    that.<BR><BR>My contention is, and always has been, that the difference=
 here=20
    is not<BR>worth the work (by vendor or by operator).<BR><FONT=20
    color=3D#888888><BR><BR><BR><BR>eric<BR></FONT>
    <DIV>
    <DIV></DIV>
    <DIV class=3Dh5><FONT face=3DArial color=3D#0000ff=20
    size=3D2></FONT><BR><BR><BR>&gt;<BR>&gt; - Sri<BR>&gt;<BR>&gt; PS: The =
title=20
    of the draft says "Efficient FRR ..." so obviously it is<BR>trying=20
    to<BR>&gt; improve (optimize - if you prefer that term) FRR.<BR>&gt;<BR=
>&gt;=20
    &gt; -----Original Message-----<BR><BR><SPAN class=3D510025421-27072010=
><FONT=20
    face=3DArial color=3D#0000ff size=3D2>[Sri ]&nbsp;[---- deleted mail=20
    --------]&nbsp;</FONT></SPAN></DIV></DIV></BLOCKQUOTE></DIV></BLOCKQUOT=
E></BODY></HTML>

--_000_5A5E55DF96F73844AF7DFB0F48721F0F567DB813EEEUSAACMS0703e_--

From autumn.liu@ericsson.com  Tue Jul 27 15:34:53 2010
Return-Path: <autumn.liu@ericsson.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE8063A6979 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 15:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=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 zzAeF+ilz5Y7 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 15:34:51 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 8026828C0EF for <mpls@ietf.org>; Tue, 27 Jul 2010 15:34:51 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o6RMZCMj005197 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Jul 2010 17:35:12 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.134]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 27 Jul 2010 18:35:11 -0400
From: Autumn Liu <autumn.liu@ericsson.com>
To: Greg Mirsky <gregimirsky@gmail.com>, Julien Meuric <julien.meuric@orange-ftgroup.com>
Date: Tue, 27 Jul 2010 18:35:10 -0400
Thread-Topic: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
Thread-Index: AcstAmcuHunxF55GQeyPqim4Gp+bygA2QYrg
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51AE592A5E@EUSAACMS0703.eamcs.ericsson.se>
References: <5A5E55DF96F73844AF7DFB0F48721F0F567DB80A69@EUSAACMS0703.eamcs.ericsson.se> <4C4DC874.6000502@orange-ftgroup.com> <60C093A41B5E45409A19D42CF7786DFD51AE518F86@EUSAACMS0703.eamcs.ericsson.se> <AANLkTin+JgCSWxV-oY6_1dH5zeqLSM1Lr65LJUkDjX3s@mail.gmail.com> <60C093A41B5E45409A19D42CF7786DFD51AE519013@EUSAACMS0703.eamcs.ericsson.se> <AANLkTikQ50unSLTmg+4i5H==_z2pOHPeYqOrS3r5oygf@mail.gmail.com>
In-Reply-To: <AANLkTikQ50unSLTmg+4i5H==_z2pOHPeYqOrS3r5oygf@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_60C093A41B5E45409A19D42CF7786DFD51AE592A5EEUSAACMS0703e_"
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Updated drafts -	draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 22:34:53 -0000

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

Hi Greg and Julien

Thanks for pointing this out. The draft can be applied to the case when seg=
ment protection is utilized as defined in 4873. We will update the draft ac=
cordingly.

Regards,
Autumn



________________________________
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Gre=
g Mirsky
Sent: Monday, July 26, 2010 1:37 PM
To: Autumn Liu
Cc: mpls@ietf.org
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-back=
up, draft-kini-mpls-fast-lsp-alert

Dear Autumn,
thank you for adding specific case to our discussion. In my view protecting=
 segment L10-L1-L2-L3-L4-L5 (e-backup tunnel) is shared by all backup tunne=
ls that traverse the ring through nodes L10-L9-L8-L7-L6-L5. This e-backup t=
unnel is the e-backup tunnels for all working sections/segments (in case of=
 link and node protection) of an LSP L10-...-L8-..-L5. I'd re-state my ques=
tion to authors whether they've considered re-using RSVP-TE objects and sub=
objects defined in RFC 4873.  If mechanisms and objects defined in RFC 4873=
 not sufficient, why RFC 4873 not referenced in the draft Efficient Facilit=
y Backup FRR.

Regards,
Greg

On Mon, Jul 26, 2010 at 12:16 PM, Autumn Liu <autumn.liu@ericsson.com<mailt=
o:autumn.liu@ericsson.com>> wrote:
Hi Greg,

 +-------L1--------L2---------L3--------L4-------+
  |                                                      |
 L10                                                  L5
  |                                                      |
 +-------L9--------L8---------L7--------L6-------+

Not all PLRs. Using the diagram in draft as an example.
Bypass 1 (to protect link between L8 and L7) : L8-L9-L10-L1-L2-L3-L4-L5-L6-=
L7
Bypass 2 (to protect node failure on L8) : L9-L10-L1-L2-L3-L4-L5-L6-L7

e-backup tunnel L10-L1-L2-L3-L4-L5 can be used instead for both cases witho=
ut getting traffic u-turned.

Regards,
Autumn



________________________________
From: Greg Mirsky [mailto:gregimirsky@gmail.com<mailto:gregimirsky@gmail.co=
m>]
Sent: Monday, July 26, 2010 12:03 PM
To: Autumn Liu
Cc: Julien Meuric; Sriganesh Kini; mpls@ietf.org<mailto:mpls@ietf.org>

Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-back=
up, draft-kini-mpls-fast-lsp-alert

Dear Autumn,
I'm quite surprised to read your reply to Julien. My understanding of your =
proposal is that all PLRs share the same u-PLR for given ring segment of LS=
P. Please correct me if my understanding is different from authors intentio=
n.
I'd like to add to Julien's comment that RFC 4873 seems relevant to your so=
lution as well as RFC 4872. And I'd ask the same question as Julien in rega=
rd to not referencing RFC 4873.

Regards,
Greg

On Mon, Jul 26, 2010 at 11:30 AM, Autumn Liu <autumn.liu@ericsson.com<mailt=
o:autumn.liu@ericsson.com>> wrote:
Hi Julien,

draft-kini-mpls-ring-frr-facility-backup describes a mechanism to let the p=
rimary LSP be aware of what the bypass LSP for corresponding protected faci=
lity. If my understanding is correct, the association mechanism defined in =
4872 is used to associate the primary and backup LSPs. This is not good eno=
ugh for the problem the draft is trying to address since each link/node alo=
ng the primary LSP may have different bypass LSPs.

Regards,
Autumn


-----Original Message-----
From: mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org> [mailto:mpls-boun=
ces@ietf.org<mailto:mpls-bounces@ietf.org>] On Behalf Of Julien Meuric
Sent: Monday, July 26, 2010 10:40 AM
To: Sriganesh Kini
Cc: mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-back=
up, draft-kini-mpls-fast-lsp-alert

Hi Sriganesh.

The mechanism described in draft-kini-mpls-ring-frr-facility-backup
reminds me of end to end recovery (or more specifically end to end protecti=
on), as enabled by RFC 4872. That is all the more similar because the assoc=
iation mechanism is already defined in there, with a dedicated RSVP-TE obje=
ct. RFC 4872 is Standard Track: is there any rational for not considering i=
t?

Regards,

Julien


Le 26/07/2010 18:59, Sriganesh Kini a =E9crit :
> FYI - These updated version of these drafts were presented today at
> IETF78.
> http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-backup-01
> http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01
> Thanks
>
> - Sri
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org<mailto:mpls@ietf.org>
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.6001.18444" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D602163122-27072010>Hi Greg and Julien </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D602163122-27072010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D602163122-27072010>Thanks for pointing this out. The draft can be a=
pplied=20
to the case when segment protection is utilized as defined in 4873. We will=
=20
update the draft accordingly.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D602163122-27072010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D602163122-27072010>Regards,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D602163122-27072010>Autumn</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D602163122-27072010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D602163122-27072010></SPAN></FONT>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> mpls-bounces@ietf.org=20
[mailto:mpls-bounces@ietf.org] <B>On Behalf Of </B>Greg Mirsky<BR><B>Sent:<=
/B>=20
Monday, July 26, 2010 1:37 PM<BR><B>To:</B> Autumn Liu<BR><B>Cc:</B>=20
mpls@ietf.org<BR><B>Subject:</B> Re: [mpls] Updated drafts -=20
draft-kini-mpls-ring-frr-facility-backup,=20
draft-kini-mpls-fast-lsp-alert<BR></FONT><BR></DIV>
<DIV></DIV>Dear Autumn,<BR>thank you for adding specific case to our discus=
sion.=20
In my view protecting segment <FONT face=3DArial size=3D2><SPAN>L10-L1-L2-L=
3-L4-L5=20
(e-backup tunnel) is shared by all backup tunnels that traverse the ring th=
rough=20
nodes L10-L9-L8-L7-L6-L5. This e-backup tunnel is the e-backup tunnels for =
all=20
working sections/segments (in case of link and node protection) of an LSP=20
L10-...-L8-..-L5. I'd re-state my question to authors whether they've consi=
dered=20
re-using RSVP-TE objects and subobjects defined in RFC 4873.&nbsp; If mecha=
nisms=20
and objects defined in RFC 4873 not sufficient, why RFC 4873 not referenced=
 in=20
the draft Efficient Facility Backup=20
FRR.</SPAN></FONT><BR><BR>Regards,<BR>Greg<BR><BR>
<DIV class=3Dgmail_quote>On Mon, Jul 26, 2010 at 12:16 PM, Autumn Liu <SPAN=
=20
dir=3Dltr>&lt;<A href=3D"mailto:autumn.liu@ericsson.com"=20
target=3D_blank>autumn.liu@ericsson.com</A>&gt;</SPAN> wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204=
,204,204) 1px solid">
  <DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN>Hi=20
  Greg,</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
  size=3D2><SPAN></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial=20
  size=3D2><SPAN>&nbsp;+-------L1--------L2---------L3--------L4-------+<BR=
>&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;|</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial=20
  size=3D2><SPAN>&nbsp;L10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
  L5</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial=20
  size=3D2><SPAN>&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial=20
  size=3D2><SPAN>&nbsp;+-------L9--------L8---------L7--------L6-------+<BR=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
  </SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN>Not all PLR=
s. Using the=20
  diagram in draft as an example.</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN>Bypass 1 (t=
o protect=20
  link between L8 and L7) : L8-L9-L10-L1-L2-L3-L4-L5-L6-L7 </SPAN></FONT></=
DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN>Bypass 2 (t=
o protect=20
  node failure on L8) : L9-L10-L1-L2-L3-L4-L5-L6-L7</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial=20
  size=3D2><SPAN></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN>e-backup tu=
nnel=20
  L10-L1-L2-L3-L4-L5&nbsp;can be&nbsp;used instead for both cases without=20
  getting traffic&nbsp;u-turned.</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial=20
  size=3D2><SPAN></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial=20
  size=3D2><SPAN>Regards,</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial=20
  size=3D2><SPAN>Autumn</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial=20
  size=3D2><SPAN><BR>&nbsp;</SPAN></FONT></DIV><BR>
  <DIV lang=3Den-us dir=3Dltr align=3Dleft>
  <HR>
  <FONT face=3DTahoma size=3D2><B>From:</B> Greg Mirsky [mailto:<A=20
  href=3D"mailto:gregimirsky@gmail.com" target=3D_blank>gregimirsky@gmail.c=
om</A>]=20
  <BR><B>Sent:</B> Monday, July 26, 2010 12:03 PM<BR><B>To:</B> Autumn=20
  Liu<BR><B>Cc:</B> Julien Meuric; Sriganesh Kini; <A=20
  href=3D"mailto:mpls@ietf.org" target=3D_blank>mpls@ietf.org</A>
  <DIV>
  <DIV></DIV>
  <DIV><BR><B>Subject:</B> Re: [mpls] Updated drafts -=20
  draft-kini-mpls-ring-frr-facility-backup,=20
  draft-kini-mpls-fast-lsp-alert<BR></DIV></DIV></FONT><BR></DIV>
  <DIV>
  <DIV></DIV>
  <DIV>
  <DIV></DIV>Dear Autumn,<BR>I'm quite surprised to read your reply to Juli=
en.=20
  My understanding of your proposal is that all PLRs share the same u-PLR f=
or=20
  given ring segment of LSP. Please correct me if my understanding is diffe=
rent=20
  from authors intention.<BR>I'd like to add to Julien's comment that RFC 4=
873=20
  seems relevant to your solution as well as RFC 4872. And I'd ask the same=
=20
  question as Julien in regard to not referencing RFC=20
  4873.<BR><BR>Regards,<BR>Greg<BR><BR>
  <DIV class=3Dgmail_quote>On Mon, Jul 26, 2010 at 11:30 AM, Autumn Liu <SP=
AN=20
  dir=3Dltr>&lt;<A href=3D"mailto:autumn.liu@ericsson.com"=20
  target=3D_blank>autumn.liu@ericsson.com</A>&gt;</SPAN> wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(2=
04,204,204) 1px solid">Hi=20
    Julien,<BR><BR>draft-kini-mpls-ring-frr-facility-backup describes a=20
    mechanism to let the primary LSP be aware of what the bypass LSP for=20
    corresponding protected facility. If my understanding is correct, the=20
    association mechanism defined in 4872 is used to associate the primary =
and=20
    backup LSPs. This is not good enough for the problem the draft is tryin=
g to=20
    address since each link/node along the primary LSP may have different b=
ypass=20
    LSPs.<BR><BR>Regards,<BR><FONT color=3D#888888>Autumn<BR></FONT>
    <DIV>
    <DIV></DIV>
    <DIV><BR><BR>-----Original Message-----<BR>From: <A=20
    href=3D"mailto:mpls-bounces@ietf.org" target=3D_blank>mpls-bounces@ietf=
.org</A>=20
    [mailto:<A href=3D"mailto:mpls-bounces@ietf.org"=20
    target=3D_blank>mpls-bounces@ietf.org</A>] On Behalf Of Julien Meuric<B=
R>Sent:=20
    Monday, July 26, 2010 10:40 AM<BR>To: Sriganesh Kini<BR>Cc: <A=20
    href=3D"mailto:mpls@ietf.org" target=3D_blank>mpls@ietf.org</A><BR>Subj=
ect: Re:=20
    [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup,=20
    draft-kini-mpls-fast-lsp-alert<BR><BR>Hi Sriganesh.<BR><BR>The mechanis=
m=20
    described in draft-kini-mpls-ring-frr-facility-backup<BR>reminds me of =
end=20
    to end recovery (or more specifically end to end protection), as enable=
d by=20
    RFC 4872. That is all the more similar because the association mechanis=
m is=20
    already defined in there, with a dedicated RSVP-TE object. RFC 4872 is=
=20
    Standard Track: is there any rational for not considering=20
    it?<BR><BR>Regards,<BR><BR>Julien<BR><BR><BR>Le 26/07/2010 18:59, Sriga=
nesh=20
    Kini a =E9crit :<BR>&gt; FYI - These updated version of these drafts we=
re=20
    presented today at<BR>&gt; IETF78.<BR>&gt; <A=20
    href=3D"http://tools.ietf.org/html/draft-kini-mpls-ring-frr-facility-ba=
ckup-01"=20
    target=3D_blank>http://tools.ietf.org/html/draft-kini-mpls-ring-frr-fac=
ility-backup-01</A><BR>&gt;=20
    <A href=3D"http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-alert-01=
"=20
    target=3D_blank>http://tools.ietf.org/html/draft-kini-mpls-fast-lsp-ale=
rt-01</A><BR>&gt;=20
    Thanks<BR>&gt;<BR>&gt; - Sri<BR>&gt;<BR>&gt;<BR>&gt;=20
    _______________________________________________<BR>&gt; mpls mailing=20
    list<BR>&gt; <A href=3D"mailto:mpls@ietf.org"=20
    target=3D_blank>mpls@ietf.org</A><BR>&gt; <A=20
    href=3D"https://www.ietf.org/mailman/listinfo/mpls"=20
    target=3D_blank>https://www.ietf.org/mailman/listinfo/mpls</A><BR>&gt;<=
BR>_______________________________________________<BR>mpls=20
    mailing list<BR><A href=3D"mailto:mpls@ietf.org"=20
    target=3D_blank>mpls@ietf.org</A><BR><A=20
    href=3D"https://www.ietf.org/mailman/listinfo/mpls"=20
    target=3D_blank>https://www.ietf.org/mailman/listinfo/mpls</A><BR>_____=
__________________________________________<BR>mpls=20
    mailing list<BR><A href=3D"mailto:mpls@ietf.org"=20
    target=3D_blank>mpls@ietf.org</A><BR><A=20
    href=3D"https://www.ietf.org/mailman/listinfo/mpls"=20
    target=3D_blank>https://www.ietf.org/mailman/listinfo/mpls</A><BR></DIV=
></DIV></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV></BLOCKQUOTE></DIV><BR></BO=
DY></HTML>

--_000_60C093A41B5E45409A19D42CF7786DFD51AE592A5EEUSAACMS0703e_--

From curtis@occnc.com  Wed Jul 28 00:18:24 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7F3A3A68D7 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 00:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.388
X-Spam-Level: 
X-Spam-Status: No, score=-2.388 tagged_above=-999 required=5 tests=[AWL=0.211,  BAYES_00=-2.599]
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 P8Y71GzoyuQ1 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 00:17:55 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 9D6D43A688C for <mpls@ietf.org>; Wed, 28 Jul 2010 00:17:55 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6S7HUj2089774; Wed, 28 Jul 2010 03:17:30 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007280717.o6S7HUj2089774@harbor.orleans.occnc.com>
To: Yong Lucy <lucyyong@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Tue, 27 Jul 2010 07:31:21 CDT." <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com> 
Date: Wed, 28 Jul 2010 03:17:30 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org
Subject: Re: [mpls] entropy label indicator label in draft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 07:18:24 -0000

In message <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com>
Yong Lucy writes:
>  
> Hi Kireeti and Shane,
>  
> Could we consider use one of reserved label for ELI purpose? This will make
> implementation much easy, i.e. not need to keep the state for each ELI
> label. The approach can be used in general for RSVP-TE and BGP as well.
>  
> Regards,
>  
> Lucy


Kireeti, Shane, Lucy,

I agree that a reserved label would be useful.

You should also remove the restriction that the entropy label is on
the bottom of stack.

With three more bits of information in the TE-LSDB an LSR can identify
a path over which it can carry a very large aggregate MPLS LSP
containing smaller MPLS-TP LSP.

  1.  Each LSR must identify itelf as "entropy label capable" (if it
      is capable, otherwise it remains silent on this).

  2.  Each LSR must identify itself as capable of limiting the stack
      depth over which it will hash on a per LSP basis if it is
      capable, otherwise it remains silent on this).

  3.  Each LAG or bundle must identify itself as multipath capable
      (implied in LAG, currently uncertain for bundle) and indicate
      the largest microflow it can handle (this would be the largest
      component link minus some epsilon if it was capable of moving
      traffic to accommodate a large microflow).  This is similar to
      (but not identical to) Maximum-LSP-Bandwidth in bundles.
      Perhaps this could be called Maximum-Microflow.

If this approach is used, the CSPF for an MPLS LSP containing MPLS-TP
requires pruning all LSR that do not have the first two capabilities
and pruning all links that do not state a Maximum-Microflow or that
state a Maximum-Microflow that is less than the largest MPLS-TP LSP
being carried.

Signaling must indicate the depth to hash to.  The ingress of the
aggregated LSP would put the entropy label for all sub-LSP that can be
subdivided into flows (generally most or all non-MPLS-TP LSP).

At each forwarding hop the the hash depth limit must be respected but
with the entropy label above that depth the balance could be
maintained without impacting MPLS-TP.

Note: There is no requirement to identify the large flows through an
explicity marking at ingress.  This comment is not relevant to this
draft, but I thought I'd point this out before the thread goes off in
that direction.  Please keep that discussion on a separate thread.

Curtis

From curtis@occnc.com  Wed Jul 28 00:24:32 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E99E43A69C9 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 00:24:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.391
X-Spam-Level: 
X-Spam-Status: No, score=-2.391 tagged_above=-999 required=5 tests=[AWL=0.208,  BAYES_00=-2.599]
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 VMNynORaFwrn for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 00:24:32 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id D25123A68D6 for <mpls@ietf.org>; Wed, 28 Jul 2010 00:24:31 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6S7O9oa090170; Wed, 28 Jul 2010 03:24:09 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007280724.o6S7O9oa090170@harbor.orleans.occnc.com>
To: John E Drake <jdrake@juniper.net>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Tue, 27 Jul 2010 06:31:03 PDT." <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net> 
Date: Wed, 28 Jul 2010 03:24:09 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 07:24:33 -0000

In message <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net>
John E Drake writes:
>  
>  
> Lucy,
>  
> Yes it does.  That is the whole point.  That is how the egress knows
> whethe= r the ingress has placed an entropy label in the stack.  (That
> is why we te= rmed it the 'Entropy Label Indicator'.)
>  
> Thanks,
>  
> John


OK.  I see the point of avoiding the reserved label and the reason
that the LSP egress only needs to recognize it.

I still feel that the restriction to put this at BOS is not necessary.
It must only be below the forwarding label of the egress for that LSP.

Curtis


> From: Yong Lucy [mailto:lucyyong@huawei.com]
> Sent: Tuesday, July 27, 2010 6:25 AM
> To: John E Drake; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: RE: [mpls] entropy label indicator label indraft-kompella-mpls-ent=
> ropy-label
>  
> What is the benefit for such control? Egress LSR does not use this value.
> Lucy
>  
> ________________________________
> From: John E Drake [mailto:jdrake@juniper.net]
> Sent: Tuesday, July 27, 2010 8:10 AM
> To: Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: RE: [mpls] entropy label indicator label indraft-kompella-mpls-ent=
> ropy-label
>  
> Lucy, we discussed this and decided it was better to have the egress
> contro= l the values of the ELI it advertises.  Plus, getting a
> reserved value woul= d be difficult
>  
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Yon=
> g Lucy
> Sent: Tuesday, July 27, 2010 5:31 AM
> To: Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: [mpls] entropy label indicator label in draft-kompella-mpls-entrop=
> y-label
>  
> Hi Kireeti and Shane,
>  
> Could we consider use one of reserved label for ELI purpose? This will
>  make= implementation much easy, i.e. not need to keep the state for
>  each ELI lab= el. The approach can be used in general for RSVP-TE and
>  BGP as well.
>  
> Regards,
> Lucy
 

From curtis@occnc.com  Wed Jul 28 00:37:18 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA5713A68D7 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 00:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.394
X-Spam-Level: 
X-Spam-Status: No, score=-2.394 tagged_above=-999 required=5 tests=[AWL=0.205,  BAYES_00=-2.599]
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 Gg1lHMH+1+Ho for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 00:37:17 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 9A9113A67E6 for <mpls@ietf.org>; Wed, 28 Jul 2010 00:37:17 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6S7bcXk090494; Wed, 28 Jul 2010 03:37:38 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007280737.o6S7bcXk090494@harbor.orleans.occnc.com>
To: stbryant@cisco.com
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Tue, 27 Jul 2010 15:24:02 BST." <4C4EEC02.2040202@cisco.com> 
Date: Wed, 28 Jul 2010 03:37:38 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org
Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 07:37:18 -0000

In message <4C4EEC02.2040202@cisco.com>
Stewart Bryant writes:
>
> John
>  
> Why do you prefer to use an ELI as opposed to using a new set of FECs
> with the property that they are followed by an EL?
>  
> Stewart


Stewart,

The same TE LSP can carry an IP payload and other MPLS LSP.  This
avoids confusing an entropy label with a forwarding label.

The egress does not have to know apriori whether the ingress is adding
an entropy label and the ingress is free to add an entropy label to
some but not all traffic.

The draft only provides LDP signaling.  TE signaling should also be
provided.  The entropy label can be a per host value (platform label
space) and it doesn't matter much where in OSPF-TE or ISIS-TE the TLV
is placed.

It would be nice if as we add further MPLS extensions we got the new
behavior we are looking for without making it such that MPLS-TP cannot
be accommodated on the same path and adding signaling to TE as well as
LDP is a small step in that direction.

Curtis

From curtis@occnc.com  Wed Jul 28 00:48:39 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B97B53A69C9 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 00:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.397
X-Spam-Level: 
X-Spam-Status: No, score=-2.397 tagged_above=-999 required=5 tests=[AWL=0.202,  BAYES_00=-2.599]
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 6SB5OmjuPOlV for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 00:48:38 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 3E9473A6967 for <mpls@ietf.org>; Wed, 28 Jul 2010 00:48:38 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6S7mNf3090648; Wed, 28 Jul 2010 03:48:23 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007280748.o6S7mNf3090648@harbor.orleans.occnc.com>
To: Shane Amante <shane@castlepoint.net>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Tue, 27 Jul 2010 18:22:21 +0200." <854FD998-DD00-48F1-9682-589EBE89F27A@castlepoint.net> 
Date: Wed, 28 Jul 2010 03:48:23 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org
Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 07:48:39 -0000

In message <854FD998-DD00-48F1-9682-589EBE89F27A@castlepoint.net>
Shane Amante writes:
>  
>  
> Lucy,
>  
> On Jul 27, 2010, at 17:06 GMT+02:00, Yong Lucy wrote:
> > Hi John,
> > I don=92t get it. If egress LSR asks ingress LSR to place ELI on the =
> stack, the ingress can insert a unique ELI label on the stack followed =
> by entropy label. When packet arrives to egress LSR, the LSR will find =
> ELI on the stack. Why is it important for egress LSP to allocate a value =
> for ELI instead of using standardized value?
>  
> I think John already answered this question, but I'll give it a try, as =
> well.  It's really a design choice on the part of the co-authors, in an =
> attempt to avoid asking the MPLS WG to allocate a reserved label from =
> the very scarce reserved label space.  I would note that there are only =
> 8 reserved MPLS label values that are currently unassigned:
> =
> http://www.iana.org/assignments/mpls-label-values/mpls-label-values.xhtml
>  
> So, if we believe it's "sound engineering" to use an ELI instead of a =
> reserved label -- certainly a judgement call -- then, I believe, we =
> should NOT request a reserved label in order that future applications =
> that have a legitimate use (or, said differently, may not be able to =
> function properly without a reserved label value) have an ability to =
> acquire one.
>  
> -shane


Whether it is reserved or not, the ingress needs to verify that the
egress understands it so there is little additional change having the
egress provide its own reserved value.  This avoids using a scarse
resource for no good reason.

Curtis
 

From lucyyong@huawei.com  Wed Jul 28 01:28:39 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 242D73A69C3 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 01:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.458
X-Spam-Level: 
X-Spam-Status: No, score=-0.458 tagged_above=-999 required=5 tests=[AWL=-0.563, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_65=0.6, 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 zIIhtw-GavXQ for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 01:28:38 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id CB4743A67A2 for <mpls@ietf.org>; Wed, 28 Jul 2010 01:28:37 -0700 (PDT)
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 <0L6900H6RE6A0B@szxga04-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 16:27:47 +0800 (CST)
Received: from 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 <0L6900FWBE623Q@szxga04-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 16:27:46 +0800 (CST)
Received: from y736742 (dhcp-72c7.meeting.ietf.org [130.129.114.199]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L69009TJE5Z0W@szxml02-in.huawei.com>; Wed, 28 Jul 2010 16:27:43 +0800 (CST)
Date: Wed, 28 Jul 2010 03:27:36 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <201007280748.o6S7mNf3090648@harbor.orleans.occnc.com>
To: curtis@occnc.com, 'Shane Amante' <shane@castlepoint.net>
Message-id: <04b701cb2e2e$c19609c0$c7728182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsuKbs8/ViBOLWrRlCpn8xK25MuaQAAyRDQ
References: "Your message of Tue, 27 Jul 2010 18:22:21 +0200." <854FD998-DD00-48F1-9682-589EBE89F27A@castlepoint.net> <201007280748.o6S7mNf3090648@harbor.orleans.occnc.com>
Cc: mpls@ietf.org
Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 08:28:39 -0000

Yes, Egress PE has its own reserved value.

Cheers,
Lucy

> -----Original Message-----
> From: curtis@occnc.com [mailto:curtis@occnc.com]
> Sent: Wednesday, July 28, 2010 2:48 AM
> To: Shane Amante
> Cc: Yong Lucy; mpls@ietf.org
> Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-
> entropy-label
> 
> 
> In message <854FD998-DD00-48F1-9682-589EBE89F27A@castlepoint.net>
> Shane Amante writes:
> >
> >
> > Lucy,
> >
> > On Jul 27, 2010, at 17:06 GMT+02:00, Yong Lucy wrote:
> > > Hi John,
> > > I don=92t get it. If egress LSR asks ingress LSR to place ELI on the =
> > stack, the ingress can insert a unique ELI label on the stack followed =
> > by entropy label. When packet arrives to egress LSR, the LSR will find =
> > ELI on the stack. Why is it important for egress LSP to allocate a value
> =
> > for ELI instead of using standardized value?
> >
> > I think John already answered this question, but I'll give it a try, as
> =
> > well.  It's really a design choice on the part of the co-authors, in an
> =
> > attempt to avoid asking the MPLS WG to allocate a reserved label from =
> > the very scarce reserved label space.  I would note that there are only
> =
> > 8 reserved MPLS label values that are currently unassigned:
> > =
> > http://www.iana.org/assignments/mpls-label-values/mpls-label-
> values.xhtml
> >
> > So, if we believe it's "sound engineering" to use an ELI instead of a =
> > reserved label -- certainly a judgement call -- then, I believe, we =
> > should NOT request a reserved label in order that future applications =
> > that have a legitimate use (or, said differently, may not be able to =
> > function properly without a reserved label value) have an ability to =
> > acquire one.
> >
> > -shane
> 
> 
> Whether it is reserved or not, the ingress needs to verify that the
> egress understands it so there is little additional change having the
> egress provide its own reserved value.  This avoids using a scarse
> resource for no good reason.
> 
> Curtis
> 


From lucyyong@huawei.com  Wed Jul 28 01:48:50 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7521E3A69F7 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 01:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.645
X-Spam-Level: 
X-Spam-Status: No, score=-0.645 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 G7bDgemBNygD for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 01:48:49 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id CB40B3A6947 for <mpls@ietf.org>; Wed, 28 Jul 2010 01:48:48 -0700 (PDT)
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 <0L6900MIWECGY5@szxga05-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 16:31:28 +0800 (CST)
Received: from 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 <0L6900HOPECFM4@szxga05-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 16:31:28 +0800 (CST)
Received: from y736742 (dhcp-72c7.meeting.ietf.org [130.129.114.199]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L69001I6EC7WL@szxml02-in.huawei.com>; Wed, 28 Jul 2010 16:31:27 +0800 (CST)
Date: Wed, 28 Jul 2010 03:31:21 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <201007271905.o6RJ5Xrl069109@harbor.orleans.occnc.com>
To: curtis@occnc.com
Message-id: <04c701cb2e2f$47176fd0$c7728182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acstvs+Wp1J+pWIoQRuvm0YU8kyRuQAbpE6A
References: "Your message of Tue, 27 Jul 2010 11:02:05 CDT." <03e201cb2da5$15f4a740$c7728182@china.huawei.com> <201007271905.o6RJ5Xrl069109@harbor.orleans.occnc.com>
Cc: mpls@ietf.org
Subject: Re: [mpls] draft-villamizar-mpls-tp-multipath
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 08:48:50 -0000

Curtis,

You are right. This is not thread for large flow classification. Sorry.

I agree that the flow size can't be larger than component link size minus
the epsilon.

PS: you missed my point about large flow mark in previous mail.

Regards,
Lucy

> -----Original Message-----
> From: curtis@occnc.com [mailto:curtis@occnc.com]
> Sent: Tuesday, July 27, 2010 2:06 PM
> To: Yong Lucy
> Cc: curtis@occnc.com; mpls@ietf.org
> Subject: Re: draft-villamizar-mpls-tp-multipath
> 
> 
> In message <03e201cb2da5$15f4a740$c7728182@china.huawei.com>
> Yong Lucy writes:
> >
> > Cutis,
> >
> > Please see inline.
> >
> > > >
> > > > Comment:
> > > >
> > > > 1) Adjusting load over component link may cause flow reordering.
> > >
> > > Yes.  That is why adjustments should be minimizaed and the why
> > > adjustments should avoid moving the same traffic back and forth if it
> > > sits on some sort of mathematical boundary.
> > >
> > > > 2) If a huge amount of micro flows mix with few large and long live
> > > flows,
> > > > the load per entry can be out of balance
> > >
> > > For a hash space size of 24 bits, 1/16,000,000 of the tiny flows will
> > > be mixed in the same hash bucket as a large flow.  This is why large
> > > flows can only be sized at max-component BW minus epsilon, where
> > > epsilong depends on the hash space size.
> > [LY] This is true when only hashing is used.
> > >
> > > Perhaps you haven't figured out how a very large hash space can be
> > > supported with a modest amount of hardware.  It can.  You might want
> > > to look at the expired optimized multipath drafts in data-tracker.
> > > There is a little more detail there.
> > [LY] hashing is stateless and provides the simple way to support the
> large
> > hash space. This is not the problem we address.
> 
> This thread is not about your draft.  It is about a draft which
> extends an existing widely implemented technique used with MPLS and
> multipath to support MPLS-TP.
> 
> > > > 3) Measure component link load does not provide the info. for table
> > > entry
> > > > mapping adjustment
> > >
> > > The measurement is much finer that component link.  Again, look at the
> > > expired optimized multipath drafts in data-tracker.
> > >
> > > This is a solved problem.  The sections that describe how it was
> > > successfully done a decade ago is intended only to provide an
> > > existance proof that there is a simple solution.  There are other
> > > solutions that make use of the same properties of the hash but build
> > > the hardware somewhat differently than described in the OMP drafts.
> > >
> > > > Internet traffic pattern today is different from decade or more
> years
> > > ago.
> > > > Hashing works well under the condition
> > >
> > > Yes.  I know that.
> > >
> > > > 1) # of flows is very large and flow IDs are statistically random;
2)
> > > flow
> > > > BWs are pretty balanced.
> > >
> > > The number of flows observed within a minute interval 15 years ago was
> > > in the millions.  Today in LAGs of tens of 10GbE, it is likely to be
> > > in the billion range.  I am aware of this.  If 2% of the flows are
> > > large then 2% of a billion is also large meaning that they are very
> > > numerous.  Building core equipment support 20 million hardware entries
> > > to handle such a case is not a good suggestion.
> > [LY] If large flow has the notion that its rate is about the threshold,
> it
> > is easy to count how many large flows a link can support. Be honest, we
> > don't see such many large flows in today's network.
> > For a 10x10GE link,
> > If 500Mbps is the threshold for large flow, the link can not take more
> than
> > 200 large flows.
> 
> 500 Mbps x 200 is 100Gb/s is the whole 10x10G.
> 
> > If 50M is the mark, the link can not take more than 2000 large flows.
> 
> 50 Mbps x 2000 is 100Gb/s is the whole 10x10G.
> 
> > If 5M is the mark, the link can not take more than 20000 large flows.
> 
> 5 Mbps x 20000 is 100Gb/s is the whole 10x10G.
> 
> So total is 300G.  Is something wrong with your math here?
> 
> The large flows come and go.  A flow for an enterprise VPN may be
> small all day and then run a database backup.  They are not going to
> signal any LSP differently before this happens.  In the core the PW
> LSP associated with this flow may be inside another MPLS LSP used to
> improve network scalability.  Most likely the PW with be inside an LDP
> LSP which is inside a TE LSP in the core.
> 
> > [LY] We don't think the flow with 5Mpbs belonging to large flow class.
> We
> > need to speak to reality. It seems that we can different ways to count
> ratio
> > of large flow ratio.
> 
> Once again, this is not about your draft.  Start another thread for
> that.  This is about small changes to an existing MPLS technique that
> allow MPLS (without the TP) to be used as a server layer for MPLS-TP.
> There is no signaling of large or small flows so that topic is
> irrelevant to this draft.
> 
> Curtis


From kireeti@juniper.net  Wed Jul 28 02:06:51 2010
Return-Path: <kireeti@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F4993A687D for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 02:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fe8wGx8ElsB6 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 02:06:49 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by core3.amsl.com (Postfix) with ESMTP id 9E1F83A69B9 for <mpls@ietf.org>; Wed, 28 Jul 2010 02:06:49 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKTE/zPsfVuAoZUur2ib0wCIaMf95zsZAB@postini.com; Wed, 28 Jul 2010 02:07:12 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Wed, 28 Jul 2010 02:05:38 -0700
From: Kireeti Kompella <kireeti@juniper.net>
To: "curtis@occnc.com" <curtis@occnc.com>
Date: Wed, 28 Jul 2010 02:05:35 -0700
Thread-Topic: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
Thread-Index: AcsuNAu9ktCWWz+3SlqxCVbKJAH1wA==
Message-ID: <EBCA99AB-3D5C-4CD2-91A7-D421144B2175@juniper.net>
References: <201007280737.o6S7bcXk090494@harbor.orleans.occnc.com>
In-Reply-To: <201007280737.o6S7bcXk090494@harbor.orleans.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: Re: [mpls] entropy label indicator label	indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 09:06:51 -0000

Hi Curtis, Stewart,

On Jul 28, 2010, at 00:37 , Curtis Villamizar wrote:

>=20
> In message <4C4EEC02.2040202@cisco.com>
> Stewart Bryant writes:
>>=20
>> John
>>=20
>> Why do you prefer to use an ELI as opposed to using a new set of FECs
>> with the property that they are followed by an EL?
>>=20
>> Stewart
>=20
>=20
> Stewart,
>=20
> The same TE LSP can carry an IP payload and other MPLS LSP.  This
> avoids confusing an entropy label with a forwarding label.

In a discussion yesterday, it occurred to me that upstream allocated labels=
 also call for the use of ELI.  Again, the issue is confusing an EL with a =
forwarding label.  We'll spell this out in the next revision.

> The egress does not have to know apriori whether the ingress is adding
> an entropy label and the ingress is free to add an entropy label to
> some but not all traffic.
>=20
> The draft only provides LDP signaling.  TE signaling should also be
> provided.  The entropy label can be a per host value (platform label
> space) and it doesn't matter much where in OSPF-TE or ISIS-TE the TLV
> is placed.

That's the plan (and BGP signaling as well).

Kireeti.=

From curtis@occnc.com  Wed Jul 28 02:07:06 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F54A28C13D for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 02:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[AWL=0.199, BAYES_00=-2.599]
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 KN-I7ALUqd9p for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 02:07:01 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 417F928C104 for <mpls@ietf.org>; Wed, 28 Jul 2010 02:07:00 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6S97FBr092915; Wed, 28 Jul 2010 05:07:15 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007280907.o6S97FBr092915@harbor.orleans.occnc.com>
To: Yong Lucy <lucyyong@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Wed, 28 Jul 2010 03:31:21 CDT." <04c701cb2e2f$47176fd0$c7728182@china.huawei.com> 
Date: Wed, 28 Jul 2010 05:07:15 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org
Subject: [mpls] large flow mark?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 09:07:06 -0000

In message <04c701cb2e2f$47176fd0$c7728182@china.huawei.com>
Yong Lucy writes:
>  
> Curtis,
>  
> You are right. This is not thread for large flow classification. Sorry.
>  
> I agree that the flow size can't be larger than component link size
> minus the epsilon.
>  
> PS: you missed my point about large flow mark in previous mail.
>  
> Regards,
> Lucy


OK.  What point did I miss.  Could you please summarize.

Curtis

From lucyyong@huawei.com  Wed Jul 28 04:06:54 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1214B3A6877 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 04:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.62
X-Spam-Level: 
X-Spam-Status: No, score=-0.62 tagged_above=-999 required=5 tests=[AWL=-0.125,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 xvwU4hATgR-t for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 04:06:51 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id ABF8F3A67E5 for <mpls@ietf.org>; Wed, 28 Jul 2010 04:06:51 -0700 (PDT)
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 <0L6900ML9LIARC@szxga04-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 19:06:10 +0800 (CST)
Received: from 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 <0L6900BP6LIAVD@szxga04-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 19:06:10 +0800 (CST)
Received: from y736742 (dhcp-72c7.meeting.ietf.org [130.129.114.199]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L690028TLI6XL@szxml01-in.huawei.com>; Wed, 28 Jul 2010 19:06:10 +0800 (CST)
Date: Wed, 28 Jul 2010 06:06:09 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <201007280737.o6S7bcXk090494@harbor.orleans.occnc.com>
To: curtis@occnc.com, stbryant@cisco.com
Message-id: <04d401cb2e44$e45dfdd0$c7728182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsuKLPI9YGeid1SSK2Pyc7MDP+VOAACDAgw
References: "Your message of Tue, 27 Jul 2010 15:24:02 BST." <4C4EEC02.2040202@cisco.com> <201007280737.o6S7bcXk090494@harbor.orleans.occnc.com>
Cc: mpls@ietf.org
Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 11:06:54 -0000

Yes, each egress PE reserves its own ELI label value. Ingress PEs need
remember each PE reserved ELI label. For a large network, one PE may send
packets to many PEs.

Cheers,
Lucy 

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Curtis Villamizar
> Sent: Wednesday, July 28, 2010 2:38 AM
> To: stbryant@cisco.com
> Cc: mpls@ietf.org
> Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-
> entropy-label
> 
> 
> In message <4C4EEC02.2040202@cisco.com>
> Stewart Bryant writes:
> >
> > John
> >
> > Why do you prefer to use an ELI as opposed to using a new set of FECs
> > with the property that they are followed by an EL?
> >
> > Stewart
> 
> 
> Stewart,
> 
> The same TE LSP can carry an IP payload and other MPLS LSP.  This
> avoids confusing an entropy label with a forwarding label.
> 
> The egress does not have to know apriori whether the ingress is adding
> an entropy label and the ingress is free to add an entropy label to
> some but not all traffic.
> 
> The draft only provides LDP signaling.  TE signaling should also be
> provided.  The entropy label can be a per host value (platform label
> space) and it doesn't matter much where in OSPF-TE or ISIS-TE the TLV
> is placed.
> 
> It would be nice if as we add further MPLS extensions we got the new
> behavior we are looking for without making it such that MPLS-TP cannot
> be accommodated on the same path and adding signaling to TE as well as
> LDP is a small step in that direction.
> 
> Curtis
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From kireeti@juniper.net  Wed Jul 28 04:24:00 2010
Return-Path: <kireeti@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5AD628C126 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 04:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upI0eXwpcjjH for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 04:23:59 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by core3.amsl.com (Postfix) with ESMTP id CFB5B28C15A for <mpls@ietf.org>; Wed, 28 Jul 2010 04:23:56 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKTFATYevk/E+XMRzyRRM67kq+JQQgx0G7@postini.com; Wed, 28 Jul 2010 04:24:20 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Wed, 28 Jul 2010 04:18:42 -0700
From: Kireeti Kompella <kireeti@juniper.net>
To: Yong Lucy <lucyyong@huawei.com>
Date: Wed, 28 Jul 2010 04:18:40 -0700
Thread-Topic: [mpls] entropy label indicator labelindraft-kompella-mpls-entropy-label
Thread-Index: AcsuRqKlgGN3H+7PSM+x9xZh/ZHDTw==
Message-ID: <82522A95-8A16-4BB4-B0BC-F86A9A8F03E1@juniper.net>
References: "Your message of Tue, 27 Jul 2010 15:24:02 BST." <4C4EEC02.2040202@cisco.com> <201007280737.o6S7bcXk090494@harbor.orleans.occnc.com> <04d401cb2e44$e45dfdd0$c7728182@china.huawei.com>
In-Reply-To: <04d401cb2e44$e45dfdd0$c7728182@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 11:24:00 -0000

Hi Lucy,

On Jul 28, 2010, at 04:06 , Yong Lucy wrote:

> Yes, each egress PE reserves its own ELI label value. Ingress PEs need
> remember each PE reserved ELI label. For a large network, one PE may send
> packets to many PEs.

We might be making a bit too much of this.  A PE needs to allocate for rece=
ption only one ELI for *all* its apps/protocols.  In fact, a vendor will pr=
obably have a single ELI value across all their boxes.  We (the mpls WG) co=
uld pick a suggested value (outside the reserved range) that several vendor=
s could choose to implement.  The net is that a PE even though it sends to =
many other PEs may have a small handful (or even one) value of ELI to send.

Folks, speak up, and if there is enough support, I'll throw in a para sugge=
sting a common ELI value ... unless the chairs/ADs step in and provide tech=
nical reasons why not.

Kireeti.

> Cheers,
> Lucy=20
>=20
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
>> Curtis Villamizar
>> Sent: Wednesday, July 28, 2010 2:38 AM
>> To: stbryant@cisco.com
>> Cc: mpls@ietf.org
>> Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-
>> entropy-label
>>=20
>>=20
>> In message <4C4EEC02.2040202@cisco.com>
>> Stewart Bryant writes:
>>>=20
>>> John
>>>=20
>>> Why do you prefer to use an ELI as opposed to using a new set of FECs
>>> with the property that they are followed by an EL?
>>>=20
>>> Stewart
>>=20
>>=20
>> Stewart,
>>=20
>> The same TE LSP can carry an IP payload and other MPLS LSP.  This
>> avoids confusing an entropy label with a forwarding label.
>>=20
>> The egress does not have to know apriori whether the ingress is adding
>> an entropy label and the ingress is free to add an entropy label to
>> some but not all traffic.
>>=20
>> The draft only provides LDP signaling.  TE signaling should also be
>> provided.  The entropy label can be a per host value (platform label
>> space) and it doesn't matter much where in OSPF-TE or ISIS-TE the TLV
>> is placed.
>>=20
>> It would be nice if as we add further MPLS extensions we got the new
>> behavior we are looking for without making it such that MPLS-TP cannot
>> be accommodated on the same path and adding signaling to TE as well as
>> LDP is a small step in that direction.
>>=20
>> Curtis
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From curtis@occnc.com  Wed Jul 28 05:00:01 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CB2E3A6A8A for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 05:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.403
X-Spam-Level: 
X-Spam-Status: No, score=-2.403 tagged_above=-999 required=5 tests=[AWL=0.196,  BAYES_00=-2.599]
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 fBa313P0lvGk for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 05:00:00 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 3D38F3A6A75 for <mpls@ietf.org>; Wed, 28 Jul 2010 05:00:00 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6SC0ESb096811; Wed, 28 Jul 2010 08:00:14 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007281200.o6SC0ESb096811@harbor.orleans.occnc.com>
To: Yong Lucy <lucyyong@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Wed, 28 Jul 2010 06:06:09 CDT." <04d401cb2e44$e45dfdd0$c7728182@china.huawei.com> 
Date: Wed, 28 Jul 2010 08:00:14 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org, stbryant@cisco.com
Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 12:00:01 -0000

In message <04d401cb2e44$e45dfdd0$c7728182@china.huawei.com>
Yong Lucy writes:
>  
> Yes, each egress PE reserves its own ELI label value. Ingress PEs need
> remember each PE reserved ELI label. For a large network, one PE may send
> packets to many PEs.
>  
> Cheers,
> Lucy 


An LSR doing TE can afford another 20 bits of memory per node in
addition to the existing OSPF-TE and ISIS-TE information.  An LSR
doing PW can afford another 20 bits per T-LDP session.

BTW- (question to authors) does the FEC approach for LDP work for
MS-PW where the ingress and egress do not have a direct T-LDP
adjacency?

Curtis


> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> > Curtis Villamizar
> > Sent: Wednesday, July 28, 2010 2:38 AM
> > To: stbryant@cisco.com
> > Cc: mpls@ietf.org
> > Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-
> > entropy-label
> > 
> > 
> > In message <4C4EEC02.2040202@cisco.com>
> > Stewart Bryant writes:
> > >
> > > John
> > >
> > > Why do you prefer to use an ELI as opposed to using a new set of FECs
> > > with the property that they are followed by an EL?
> > >
> > > Stewart
> > 
> > 
> > Stewart,
> > 
> > The same TE LSP can carry an IP payload and other MPLS LSP.  This
> > avoids confusing an entropy label with a forwarding label.
> > 
> > The egress does not have to know apriori whether the ingress is adding
> > an entropy label and the ingress is free to add an entropy label to
> > some but not all traffic.
> > 
> > The draft only provides LDP signaling.  TE signaling should also be
> > provided.  The entropy label can be a per host value (platform label
> > space) and it doesn't matter much where in OSPF-TE or ISIS-TE the TLV
> > is placed.
> > 
> > It would be nice if as we add further MPLS extensions we got the new
> > behavior we are looking for without making it such that MPLS-TP cannot
> > be accommodated on the same path and adding signaling to TE as well as
> > LDP is a small step in that direction.
> > 
> > Curtis
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls

From lucyyong@huawei.com  Wed Jul 28 05:15:20 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C99B28C123 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 05:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.589
X-Spam-Level: 
X-Spam-Status: No, score=-0.589 tagged_above=-999 required=5 tests=[AWL=-0.094, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 v8Lyov2kxXSW for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 05:15:19 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 5CA7628C0F0 for <mpls@ietf.org>; Wed, 28 Jul 2010 05:15:09 -0700 (PDT)
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 <0L6900M5LOPFS5@szxga04-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 20:15:15 +0800 (CST)
Received: from 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 <0L6900FPKOPF3Q@szxga04-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 20:15:15 +0800 (CST)
Received: from y736742 (dhcp-72c7.meeting.ietf.org [130.129.114.199]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L69001DSOP7WL@szxml02-in.huawei.com>; Wed, 28 Jul 2010 20:15:15 +0800 (CST)
Date: Wed, 28 Jul 2010 07:15:10 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <82522A95-8A16-4BB4-B0BC-F86A9A8F03E1@juniper.net>
To: 'Kireeti Kompella' <kireeti@juniper.net>
Message-id: <000601cb2e4e$8b0ddf20$c7728182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsuRqKlgGN3H+7PSM+x9xZh/ZHDTwABzXRg
References: "Your message of Tue, 27 Jul 2010 15:24:02 BST." <4C4EEC02.2040202@cisco.com> <201007280737.o6S7bcXk090494@harbor.orleans.occnc.com> <04d401cb2e44$e45dfdd0$c7728182@china.huawei.com> <82522A95-8A16-4BB4-B0BC-F86A9A8F03E1@juniper.net>
Cc: mpls@ietf.org
Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 12:15:20 -0000

Kireeti,

There is one technical reason to have one common ELI label value: for
multicast packets. Multicast message may be sent to many egress PEs. Ingress
PE can only put one value for ELI label. So this enforces all PEs use the
same ELI label value. Is this right?

Regards,
Lucy

> -----Original Message-----
> From: Kireeti Kompella [mailto:kireeti@juniper.net]
> Sent: Wednesday, July 28, 2010 6:19 AM
> To: Yong Lucy
> Cc: mpls@ietf.org
> Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-
> entropy-label
> 
> Hi Lucy,
> 
> On Jul 28, 2010, at 04:06 , Yong Lucy wrote:
> 
> > Yes, each egress PE reserves its own ELI label value. Ingress PEs need
> > remember each PE reserved ELI label. For a large network, one PE may
> send
> > packets to many PEs.
> 
> We might be making a bit too much of this.  A PE needs to allocate for
> reception only one ELI for *all* its apps/protocols.  In fact, a vendor
> will probably have a single ELI value across all their boxes.  We (the
> mpls WG) could pick a suggested value (outside the reserved range) that
> several vendors could choose to implement.  The net is that a PE even
> though it sends to many other PEs may have a small handful (or even one)
> value of ELI to send.
> 
> Folks, speak up, and if there is enough support, I'll throw in a para
> suggesting a common ELI value ... unless the chairs/ADs step in and
> provide technical reasons why not.
> 
> Kireeti.
> 
> > Cheers,
> > Lucy
> >
> >> -----Original Message-----
> >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> >> Curtis Villamizar
> >> Sent: Wednesday, July 28, 2010 2:38 AM
> >> To: stbryant@cisco.com
> >> Cc: mpls@ietf.org
> >> Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-
> >> entropy-label
> >>
> >>
> >> In message <4C4EEC02.2040202@cisco.com>
> >> Stewart Bryant writes:
> >>>
> >>> John
> >>>
> >>> Why do you prefer to use an ELI as opposed to using a new set of FECs
> >>> with the property that they are followed by an EL?
> >>>
> >>> Stewart
> >>
> >>
> >> Stewart,
> >>
> >> The same TE LSP can carry an IP payload and other MPLS LSP.  This
> >> avoids confusing an entropy label with a forwarding label.
> >>
> >> The egress does not have to know apriori whether the ingress is adding
> >> an entropy label and the ingress is free to add an entropy label to
> >> some but not all traffic.
> >>
> >> The draft only provides LDP signaling.  TE signaling should also be
> >> provided.  The entropy label can be a per host value (platform label
> >> space) and it doesn't matter much where in OSPF-TE or ISIS-TE the TLV
> >> is placed.
> >>
> >> It would be nice if as we add further MPLS extensions we got the new
> >> behavior we are looking for without making it such that MPLS-TP cannot
> >> be accommodated on the same path and adding signaling to TE as well as
> >> LDP is a small step in that direction.
> >>
> >> Curtis
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls


From kireeti@juniper.net  Wed Jul 28 05:52:38 2010
Return-Path: <kireeti@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D109828C0E8 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 05:52:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SD7u3XKmDB2G for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 05:52:36 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id 3C2C028C163 for <mpls@ietf.org>; Wed, 28 Jul 2010 05:52:36 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKTFAoKSRMAul7k4d69DBx0uNiYzCAbhNX@postini.com; Wed, 28 Jul 2010 05:52:59 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Wed, 28 Jul 2010 05:46:50 -0700
From: Kireeti Kompella <kireeti@juniper.net>
To: Yong Lucy <lucyyong@huawei.com>
Date: Wed, 28 Jul 2010 05:46:49 -0700
Thread-Topic: [mpls] entropy label indicator labelindraft-kompella-mpls-entropy-label
Thread-Index: AcsuUvKQcoGG+EjLShydmNZTk1N4tA==
Message-ID: <5ED611B4-1534-4CA7-BCC8-A51AA174BF26@juniper.net>
References: "Your message of Tue, 27 Jul 2010 15:24:02 BST." <4C4EEC02.2040202@cisco.com> <201007280737.o6S7bcXk090494@harbor.orleans.occnc.com> <04d401cb2e44$e45dfdd0$c7728182@china.huawei.com> <82522A95-8A16-4BB4-B0BC-F86A9A8F03E1@juniper.net> <000601cb2e4e$8b0ddf20$c7728182@china.huawei.com>
In-Reply-To: <000601cb2e4e$8b0ddf20$c7728182@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 12:52:39 -0000

On Jul 28, 2010, at 05:15 , Yong Lucy wrote:

> Kireeti,
>=20
> There is one technical reason to have one common ELI label value: for
> multicast packets.

How does one signal a multi-path p2mp LSP?

Kireeti.

From lucyyong@huawei.com  Wed Jul 28 06:14:28 2010
Return-Path: <lucyyong@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D02BD28C106 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 06:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.578
X-Spam-Level: 
X-Spam-Status: No, score=-0.578 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 qLsoun+FAfGG for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 06:14:28 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id CB4193A68AD for <mpls@ietf.org>; Wed, 28 Jul 2010 06:14:27 -0700 (PDT)
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 <0L6900JPDRGG3Z@szxga05-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 21:14:40 +0800 (CST)
Received: from 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 <0L6900C4QRGFQU@szxga05-in.huawei.com> for mpls@ietf.org; Wed, 28 Jul 2010 21:14:40 +0800 (CST)
Received: from y736742 (dhcp-72c7.meeting.ietf.org [130.129.114.199]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L6900FW8RGBBN@szxml01-in.huawei.com>; Wed, 28 Jul 2010 21:14:39 +0800 (CST)
Date: Wed, 28 Jul 2010 08:14:38 -0500
From: Yong Lucy <lucyyong@huawei.com>
In-reply-to: <5ED611B4-1534-4CA7-BCC8-A51AA174BF26@juniper.net>
To: 'Kireeti Kompella' <kireeti@juniper.net>
Message-id: <004901cb2e56$d734ad90$c7728182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsuUvKQcoGG+EjLShydmNZTk1N4tAAA2GkA
References: "Your message of Tue, 27 Jul 2010 15:24:02 BST." <4C4EEC02.2040202@cisco.com> <201007280737.o6S7bcXk090494@harbor.orleans.occnc.com> <04d401cb2e44$e45dfdd0$c7728182@china.huawei.com> <82522A95-8A16-4BB4-B0BC-F86A9A8F03E1@juniper.net> <000601cb2e4e$8b0ddf20$c7728182@china.huawei.com> <5ED611B4-1534-4CA7-BCC8-A51AA174BF26@juniper.net>
Cc: mpls@ietf.org
Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 13:14:28 -0000

What I mean is that this approach could apply to P2MP LSP. One value can
make the backward compatibility in future easy.

Lucy

> -----Original Message-----
> From: Kireeti Kompella [mailto:kireeti@juniper.net]
> Sent: Wednesday, July 28, 2010 7:47 AM
> To: Yong Lucy
> Cc: mpls@ietf.org
> Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-
> entropy-label
> 
> On Jul 28, 2010, at 05:15 , Yong Lucy wrote:
> 
> > Kireeti,
> >
> > There is one technical reason to have one common ELI label value: for
> > multicast packets.
> 
> How does one signal a multi-path p2mp LSP?
> 
> Kireeti.


From curtis@occnc.com  Wed Jul 28 06:25:12 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3F553A682E for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 06:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.418
X-Spam-Level: 
X-Spam-Status: No, score=-2.418 tagged_above=-999 required=5 tests=[AWL=0.181,  BAYES_00=-2.599]
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 MZyvZ3sT1FKA for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 06:25:11 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id E7BFA3A68BD for <mpls@ietf.org>; Wed, 28 Jul 2010 06:25:10 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6SDPRKk099084; Wed, 28 Jul 2010 09:25:27 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007281325.o6SDPRKk099084@harbor.orleans.occnc.com>
To: Kireeti Kompella <kireeti@juniper.net>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Wed, 28 Jul 2010 05:46:49 PDT." <5ED611B4-1534-4CA7-BCC8-A51AA174BF26@juniper.net> 
Date: Wed, 28 Jul 2010 09:25:27 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] entropy label indicator labelindraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 13:25:12 -0000

In message <5ED611B4-1534-4CA7-BCC8-A51AA174BF26@juniper.net>
Kireeti Kompella writes:
>  
> On Jul 28, 2010, at 05:15 , Yong Lucy wrote:
>  
> > Kireeti,
> > 
> > There is one technical reason to have one common ELI label value: for
> > multicast packets.
>  
> How does one signal a multi-path p2mp LSP?
>  
> Kireeti.


You signal an LSP that crosses a LAG.  (Or that crosses link bundles
that use the all-ones component link by default).

Curtis

From kireeti@juniper.net  Wed Jul 28 06:25:14 2010
Return-Path: <kireeti@juniper.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A8C63A6A4C for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 06:25:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1wreTQQ5vgLT for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 06:25:13 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by core3.amsl.com (Postfix) with ESMTP id 29D163A699E for <mpls@ietf.org>; Wed, 28 Jul 2010 06:25:13 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKTFAvzEjf+NBFWtWYeeh2GxbqdqQGA+fz@postini.com; Wed, 28 Jul 2010 06:25:36 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Wed, 28 Jul 2010 06:22:32 -0700
From: Kireeti Kompella <kireeti@juniper.net>
To: Yong Lucy <lucyyong@huawei.com>
Date: Wed, 28 Jul 2010 06:22:31 -0700
Thread-Topic: [mpls] entropy label indicator -- single, commonly agreed value?
Thread-Index: AcsuV+9Rbl+CGyPORiuLtdNWYbKlBw==
Message-ID: <45D187C3-54F5-451D-9146-2966DD74B5B6@juniper.net>
References: "Your message of Tue, 27 Jul 2010 15:24:02 BST." <4C4EEC02.2040202@cisco.com> <201007280737.o6S7bcXk090494@harbor.orleans.occnc.com> <04d401cb2e44$e45dfdd0$c7728182@china.huawei.com> <82522A95-8A16-4BB4-B0BC-F86A9A8F03E1@juniper.net> <000601cb2e4e$8b0ddf20$c7728182@china.huawei.com>
In-Reply-To: <000601cb2e4e$8b0ddf20$c7728182@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] entropy label indicator -- single, commonly agreed value?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 13:25:14 -0000

On Jul 28, 2010, at 05:15 , Yong Lucy wrote:

> There is one technical reason to have one common ELI label value: for
> multicast packets.

Shane gently pointed out that ELs can be used for better load balancing on =
LAGs (i.e., not just multi-path LSPs).

Given that, I'll ask the chairs to start a thread on how we can converge on=
 a single ELI value.

George, Loa: having everyone agree on a common ELI is convenient, and neces=
sary in some cases.  So, can we (a) ignore those cases; or (b) coopt a rese=
rved label, or (c) coopt a regular label, or (d) [I'm open to other suggest=
ions]

Kireeti.=

From allendlung@gmail.com  Wed Jul 28 17:20:04 2010
Return-Path: <allendlung@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41C683A67FC for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 17:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 nni8J6P3KS4j for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 17:20:03 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id 69BFC3A67AF for <mpls@ietf.org>; Wed, 28 Jul 2010 17:20:03 -0700 (PDT)
Received: by pzk6 with SMTP id 6so16354pzk.31 for <mpls@ietf.org>; Wed, 28 Jul 2010 17:20:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=lBSS6snmPctPi9645sVyZLhAMriLs44L8pO7/EYi80A=; b=ZT5ZyVeYlk1461AaiHNWVvxmhr57BQoMPNCakGNNKZr0lw/zKrgkMAfFknjODr7D5X cyeuCudNi/4IaRlEnnHC/IrVdOhDhYdLkpWT41kQZpuLoKZCE3C7xwlkqi6M17roHuxX vTitykU0BzTXWtjEd5+bUPcT7c9GjDMHJbOQU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ZsTAWM+Sgk3XS2T5s+duXyt6kjmMzAW1OQglLfqGZBH0C6GbzW7M0ZWziw3G/jyRVk sz8TWdkQWwBEE3eOKkltzPFjBK2LFHat7XPRy8867hUMJ99N49ZJK5CjDRxvWd9mYcHO Vn9GtAHEhb0aViazCfB3LQC1UBOKd2fDjmY3Q=
MIME-Version: 1.0
Received: by 10.143.45.14 with SMTP id x14mr1356516wfj.42.1280362826672; Wed,  28 Jul 2010 17:20:26 -0700 (PDT)
Received: by 10.143.133.7 with HTTP; Wed, 28 Jul 2010 17:20:26 -0700 (PDT)
Date: Wed, 28 Jul 2010 17:20:26 -0700
Message-ID: <AANLkTinrA9ayfP5xOi_gs4xQAVbkyHM7MBYtyaidDoJN@mail.gmail.com>
From: Allen <allendlung@gmail.com>
To: mpls@ietf.org
Content-Type: multipart/alternative; boundary=001636e909a377ac5a048c7bb370
Subject: [mpls] Learning MPLS
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2010 00:53:43 -0000

--001636e909a377ac5a048c7bb370
Content-Type: text/plain; charset=ISO-8859-1

I'm looking for suggestions on book, websites etc. that will assist me in
learning about MPLS. Any help is appreciated.

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

I&#39;m looking for suggestions on book, websites etc. that will assist me =
in learning about MPLS. Any help is=A0appreciated.=A0

--001636e909a377ac5a048c7bb370--

From mdomdor@unex.es  Wed Jul 28 23:33:42 2010
Return-Path: <mdomdor@unex.es>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C852A3A683F for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 23:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.699
X-Spam-Level: 
X-Spam-Status: No, score=-3.699 tagged_above=-999 required=5 tests=[BAYES_50=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 iOuLHCRoAjCy for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 23:33:15 -0700 (PDT)
Received: from pizarro.unex.es (pizarro.unex.es [158.49.8.2]) by core3.amsl.com (Postfix) with ESMTP id 710B63A6912 for <mpls@ietf.org>; Wed, 28 Jul 2010 23:32:24 -0700 (PDT)
Received: from localhost (lavadora.siue [192.168.1.121]) by pizarro.unex.es (Postfix) with ESMTP id A4C451480AA for <mpls@ietf.org>; Thu, 29 Jul 2010 08:32:47 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at lavadora.unex.es
Received: from pizarro.unex.es ([192.168.1.103]) by localhost (lavadora.unex.es [192.168.1.121]) (amavisd-new, port 10024) with ESMTP id DOo7phAzdcdz for <mpls@ietf.org>; Thu, 29 Jul 2010 08:25:45 +0200 (CEST)
Received: from cartero.unex.es (unknown [158.49.17.100]) by pizarro.unex.es (Postfix) with ESMTP id 4C60B1486F0 for <mpls@ietf.org>; Thu, 29 Jul 2010 08:32:47 +0200 (CEST)
Received: from 80.38.18.174 (SquirrelMail authenticated user mdomdor) by cartero.unex.es with HTTP; Thu, 29 Jul 2010 08:32:47 +0200 (CEST)
Message-ID: <676f9a596d6dca517daf1c188e17375d.squirrel@cartero.unex.es>
In-Reply-To: <AANLkTinrA9ayfP5xOi_gs4xQAVbkyHM7MBYtyaidDoJN@mail.gmail.com>
References: <AANLkTinrA9ayfP5xOi_gs4xQAVbkyHM7MBYtyaidDoJN@mail.gmail.com>
Date: Thu, 29 Jul 2010 08:32:47 +0200 (CEST)
From: Manuel =?iso-8859-1?Q?Dom=ED=ADnguez_Dorado?= <mdomdor@unex.es>
To: mpls@ietf.org
User-Agent: SquirrelMail/1.4.17
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: Re: [mpls] Learning MPLS
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mdomdor@unex.es
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2010 06:33:42 -0000

We have developed an MPLS network simulator very intuitive, visual and
easy to use. It is developed in Java and is also simple to install. It is
free software, so you can make almost anything you want with it.

http://www.manolodominguez.com/projects/opensimmpls

If you're not familiar with MPLS, this simulator can be a good start.

I hope it is helpful.

A greeting.

> I'm looking for suggestions on book, websites etc. that will assist me in
> learning about MPLS. Any help is appreciated.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>


-----------------------------------------------------------------
Manuel Domí­nguez Dorado
Departamento de Ingeniería de Sistemas Informáticos y Telemáticos
Universidad de Extremadura
SPAIN

TLF..: 607 417 860
Web..: http://www.ManoloDominguez.com
Email: ingeniero@ManoloDominguez.com
-----------------------------------------------------------------


From mdomdor@unex.es  Wed Jul 28 23:34:26 2010
Return-Path: <mdomdor@unex.es>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D23823A6944 for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 23:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.699
X-Spam-Level: 
X-Spam-Status: No, score=-3.699 tagged_above=-999 required=5 tests=[BAYES_50=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 WsLNYW39FvMG for <mpls@core3.amsl.com>; Wed, 28 Jul 2010 23:34:18 -0700 (PDT)
Received: from pizarro.unex.es (pizarro.unex.es [158.49.8.2]) by core3.amsl.com (Postfix) with ESMTP id F1C1A3A6998 for <mpls@ietf.org>; Wed, 28 Jul 2010 23:33:02 -0700 (PDT)
Received: from localhost (lavadora.siue [192.168.1.121]) by pizarro.unex.es (Postfix) with ESMTP id 649EB1486F2 for <mpls@ietf.org>; Thu, 29 Jul 2010 08:33:16 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at lavadora.unex.es
Received: from pizarro.unex.es ([192.168.1.103]) by localhost (lavadora.unex.es [192.168.1.121]) (amavisd-new, port 10024) with ESMTP id t98A2r5IrbJ9 for <mpls@ietf.org>; Thu, 29 Jul 2010 08:26:14 +0200 (CEST)
Received: from cartero.unex.es (unknown [158.49.17.100]) by pizarro.unex.es (Postfix) with ESMTP id 2DD8D1480AA for <mpls@ietf.org>; Thu, 29 Jul 2010 08:33:16 +0200 (CEST)
Received: from 80.38.18.174 (SquirrelMail authenticated user mdomdor) by cartero.unex.es with HTTP; Thu, 29 Jul 2010 08:33:16 +0200 (CEST)
Message-ID: <b6a3bb2a109023f60a51b2c7730021f7.squirrel@cartero.unex.es>
In-Reply-To: <AANLkTinrA9ayfP5xOi_gs4xQAVbkyHM7MBYtyaidDoJN@mail.gmail.com>
References: <AANLkTinrA9ayfP5xOi_gs4xQAVbkyHM7MBYtyaidDoJN@mail.gmail.com>
Date: Thu, 29 Jul 2010 08:33:16 +0200 (CEST)
From: Manuel =?iso-8859-1?Q?Dom=ED=ADnguez_Dorado?= <mdomdor@unex.es>
To: mpls@ietf.org
User-Agent: SquirrelMail/1.4.17
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: Re: [mpls] Learning MPLS
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mdomdor@unex.es
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2010 06:34:30 -0000

We have developed an MPLS network simulator very intuitive, visual and
easy to use. It is developed in Java and is also simple to install. It is
free software, so you can make almost anything you want with it.

http://www.manolodominguez.com/projects/opensimmpls

If you're not familiar with MPLS, this simulator can be a good start.

I hope it is helpful.

A greeting.

> I'm looking for suggestions on book, websites etc. that will assist me in
> learning about MPLS. Any help is appreciated.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>


-----------------------------------------------------------------
Manuel Domí­nguez Dorado
Departamento de Ingeniería de Sistemas Informáticos y Telemáticos
Universidad de Extremadura
SPAIN

TLF..: 607 417 860
Web..: http://www.ManoloDominguez.com
Email: ingeniero@ManoloDominguez.com
-----------------------------------------------------------------


From liu.guoman@zte.com.cn  Fri Jul 30 01:15:36 2010
Return-Path: <liu.guoman@zte.com.cn>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5723328C274; Fri, 30 Jul 2010 01:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.736
X-Spam-Level: 
X-Spam-Status: No, score=-99.736 tagged_above=-999 required=5 tests=[AWL=2.102, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, 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 ID2ciGbW-GNB; Fri, 30 Jul 2010 01:15:29 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 589FF28C275; Fri, 30 Jul 2010 01:15:28 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205951570495873; Fri, 30 Jul 2010 16:13:30 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 79973.3500714166; Fri, 30 Jul 2010 16:14:58 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o6U7dNSr023884; Fri, 30 Jul 2010 16:06:56 +0800 (CST) (envelope-from liu.guoman@zte.com.cn)
To: ryoo@etri.re.kr, cts@etri.re.kr
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFE7007A09.78197DEB-ON48257770.0029A032-48257770.002CB81C@zte.com.cn>
From: liu.guoman@zte.com.cn
Date: Fri, 30 Jul 2010 16:06:30 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-30 16:06:44, Serialize complete at 2010-07-30 16:06:44
Content-Type: multipart/alternative; boundary="=_alternative 002CB81948257770_="
X-MAIL: mse2.zte.com.cn o6U7dNSr023884
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jul 2010 08:15:36 -0000

This is a multipart message in MIME format.
--=_alternative 002CB81948257770_=
Content-Type: text/plain; charset="US-ASCII"

 hi,
 today I reviewed your this draft, I have a few questions for mesh 
protection 
 1 in section 3, In my mind, there is a sentence : In both cases, 1:1 or 
1+1 protection may be used. 
   if there use 1+1 protection for each working path. it is no necessary 
to apply mesh protection.
   beacause the bandwidth resource of protection is equal to the sum of 
bandwidth resource of all 
   protected path. so I think 1+1 protection should not be used in the 
mesh protection.
   do you think so?

 2 about the Shared node SEN will send the protection locking message 
requesting 
      LoP to the end node of protected LSP. IMO, as SEN node is MIP of the 
protected 
      LSP , it can't generate unsolicit OAM packet to send other node. so 
how to generate
    the protection locking message requesting LOP in the SEN node ?

  Maybe i miss something important?
  thank you

  best regards
  liu

 
    





--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 002CB81948257770_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=3 face="sans-serif">&nbsp;hi,</font>
<br><font size=3 face="sans-serif">&nbsp;today I reviewed your this draft,
I have a few questions for mesh protection </font>
<br><font size=3 face="sans-serif">&nbsp;1 in section 3, In my mind, there
is a sentence : </font><font size=3 color=red face="sans-serif">In both
cases, 1:1 or 1+1 protection may be used. </font>
<br><font size=3 color=red face="sans-serif">&nbsp; </font><font size=3 face="sans-serif">&nbsp;if
there use 1+1 protection for each working path. it is no necessary to apply
mesh protection.</font>
<br><font size=3 face="sans-serif">&nbsp; &nbsp;beacause the bandwidth
resource of protection is equal to the sum of bandwidth resource of all
</font>
<br><font size=3 face="sans-serif">&nbsp; &nbsp;protected path. so I think
1+1 protection should not be used in the mesh protection.</font>
<br><font size=3 face="sans-serif">&nbsp; &nbsp;do you think so?</font>
<br>
<br><font size=3 face="sans-serif">&nbsp;2 about the Shared node SEN will
send the protection locking message requesting </font>
<br><font size=3 face="sans-serif">&nbsp; &nbsp; &nbsp; LoP to the end
node of protected LSP. IMO, as SEN node is MIP of the protected </font>
<br><font size=3 face="sans-serif">&nbsp; &nbsp; &nbsp; LSP , it can't
generate unsolicit OAM packet to send other node. so how to generate</font>
<br><font size=3 face="sans-serif">&nbsp; &nbsp; the protection locking
message requesting LOP in the SEN node ?</font>
<br>
<br><font size=3 face="sans-serif">&nbsp; Maybe i miss something important?</font>
<br><font size=3 face="sans-serif">&nbsp; thank you</font>
<br>
<br><font size=3 face="sans-serif">&nbsp; best regards</font>
<br><font size=3 face="sans-serif">&nbsp; liu</font>
<br>
<br><font size=3 color=red face="sans-serif">&nbsp; &nbsp; </font>
<br><font size=3 color=red face="sans-serif">&nbsp; &nbsp; </font><font size=2 color=red face="sans-serif"><br>
</font>
<table>
<tr>
<td>
<div align=center></div>
<td></table>
<br><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 002CB81948257770_=--


From cts@etri.re.kr  Fri Jul 30 01:45:02 2010
Return-Path: <cts@etri.re.kr>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 766FA28C291; Fri, 30 Jul 2010 01:45:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.52
X-Spam-Level: 
X-Spam-Status: No, score=-100.52 tagged_above=-999 required=5 tests=[AWL=-0.110, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, MPART_ALT_DIFF=0.739, 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 aJmDah-X3Tt4; Fri, 30 Jul 2010 01:45:00 -0700 (PDT)
Received: from email1.etri.info (email1.etri.re.kr [129.254.16.131]) by core3.amsl.com (Postfix) with ESMTP id 4304528C24B; Fri, 30 Jul 2010 01:44:59 -0700 (PDT)
Received: from mail pickup service by email1.etri.info with Microsoft SMTPSVC;  Fri, 30 Jul 2010 17:45:23 +0900
priority: normal
thread-index: Acsvw4xv4Fv6AU/CSzC6+trx8TGnpA==
Thread-Topic: a question about draft-cheung-mpls-tp-mesh-protection-01
From: "Taesik Cheung" <cts@etri.re.kr>
To: <liu.guoman@zte.com.cn>, <ryoo@etri.re.kr>
Date: Fri, 30 Jul 2010 17:45:23 +0900
Comment: ??, ??, 
Message-ID: <CEC8C88293A04D06A95E6FA87537804F@etri.info>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_88F6_01CB300E.FC593050"
X-Mailer: Microsoft CDO for Exchange 2000
Content-Class: urn:content-classes:message
Importance: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
X-OriginalArrivalTime: 30 Jul 2010 08:45:23.0360 (UTC) FILETIME=[8C908200:01CB2FC3]
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Taesik Cheung <cts@etri.re.kr>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jul 2010 08:45:02 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_88F6_01CB300E.FC593050
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64


------=_NextPart_000_88F6_01CB300E.FC593050
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IEFyaWFsOyBGT05ULVNJWkU6IDEwcHQiIGlkPW1zZ2Jv
ZHk+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTog6rW066a8OyBXT1JELUJSRUFLOiBicmVhay1h
bGwiPg0KPERJVj4NCjxESVYgc3R5bGU9IkZPTlQtRkFNSUxZOiDqtbTrprw7IEZPTlQtU0laRTog
MTBwdCI+DQo8RElWPkhpIExpdSw8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPlRoYW5r
IHlvdSBmb3IgdGhlIGNvbW1lbnRzLjwvRElWPg0KPERJVj5QbGVhc2Ugc2VlIGluLWxpbmUuPC9E
SVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5SZWdhcmRzLDwvRElWPg0KPERJVj5UYWVzaWs8
L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+PC9ESVY+PC9ESVY+PC9ESVY+DQo8RElWPjxCUj4tLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxCUj48Qj5Gcm9tOjwvQj4gImxpdS5ndW9tYW5AenRlLmNv
bS5jbiIgJmx0O2xpdS5ndW9tYW5AenRlLmNvbS5jbiZndDs8QlI+PEI+RnJvbSBEYXRlOjwvQj4g
MjAxMC0wNy0zMCBQTSA1OjA2OjMwPEJSPjxCPlRvOjwvQj4gInJ5b29AZXRyaS5yZS5rciIgJmx0
O3J5b29AZXRyaS5yZS5rciZndDssICJjdHNAZXRyaS5yZS5rciIgJmx0O2N0c0BldHJpLnJlLmty
Jmd0OzxCUj48Qj5DYzo8L0I+ICJtcGxzQGlldGYub3JnIiAmbHQ7bXBsc0BpZXRmLm9yZyZndDss
ICJtcGxzLXRwQGlldGYub3JnIiAmbHQ7bXBscy10cEBpZXRmLm9yZyZndDs8QlI+PEI+U3ViamVj
dDo8L0I+IGEgcXVlc3Rpb24gYWJvdXQgZHJhZnQtY2hldW5nLW1wbHMtdHAtbWVzaC1wcm90ZWN0
aW9uLTAxPEJSPjxCUj48QlI+PEZPTlQgc2l6ZT0zIGZhY2U9c2Fucy1zZXJpZj4mbmJzcDtoaSw8
L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTMgZmFjZT1zYW5zLXNlcmlmPiZuYnNwO3RvZGF5IEkgcmV2
aWV3ZWQgeW91ciB0aGlzIGRyYWZ0LCBJIGhhdmUgYSBmZXcgcXVlc3Rpb25zIGZvciBtZXNoIHBy
b3RlY3Rpb24gPC9GT05UPjxCUj48Rk9OVCBzaXplPTMgZmFjZT1zYW5zLXNlcmlmPiZuYnNwOzEg
aW4gc2VjdGlvbiAzLCBJbiBteSBtaW5kLCB0aGVyZSBpcyBhIHNlbnRlbmNlIDogPC9GT05UPjxG
T05UIGNvbG9yPXJlZCBzaXplPTMgZmFjZT1zYW5zLXNlcmlmPkluIGJvdGggY2FzZXMsIDE6MSBv
ciAxKzEgcHJvdGVjdGlvbiBtYXkgYmUgdXNlZC4gPC9GT05UPjxCUj48Rk9OVCBjb2xvcj1yZWQg
c2l6ZT0zIGZhY2U9c2Fucy1zZXJpZj4mbmJzcDsgPC9GT05UPjxGT05UIHNpemU9MyBmYWNlPXNh
bnMtc2VyaWY+Jm5ic3A7aWYgdGhlcmUgdXNlIDErMSBwcm90ZWN0aW9uIGZvciBlYWNoIHdvcmtp
bmcgcGF0aC4gaXQgaXMgbm8gbmVjZXNzYXJ5IHRvIGFwcGx5IG1lc2ggcHJvdGVjdGlvbi48L0ZP
TlQ+IDxCUj48Rk9OVCBzaXplPTMgZmFjZT1zYW5zLXNlcmlmPiZuYnNwOyAmbmJzcDtiZWFjYXVz
ZSB0aGUgYmFuZHdpZHRoIHJlc291cmNlIG9mIHByb3RlY3Rpb24gaXMgZXF1YWwgdG8gdGhlIHN1
bSBvZiBiYW5kd2lkdGggcmVzb3VyY2Ugb2YgYWxsIDwvRk9OVD48QlI+PEZPTlQgc2l6ZT0zIGZh
Y2U9c2Fucy1zZXJpZj4mbmJzcDsgJm5ic3A7cHJvdGVjdGVkIHBhdGguIHNvIEkgdGhpbmsgMSsx
IHByb3RlY3Rpb24gc2hvdWxkIG5vdCBiZSB1c2VkIGluIHRoZSBtZXNoIHByb3RlY3Rpb24uPC9G
T05UPiA8QlI+PEZPTlQgc2l6ZT0zIGZhY2U9c2Fucy1zZXJpZj4mbmJzcDsgJm5ic3A7ZG8geW91
IHRoaW5rIHNvPzwvRk9OVD4gPEJSPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTM+W1RhZXNpa10g
WWVzLCBpZiAxKzEgcHJvdGVjdGlvbiBpcyB1c2VkLCBzaGFyZWQgbWVzaCBwcm90ZWN0aW9uIGlz
IG5vdCBuZWNlc3NhcnkuJm5ic3A7VGhlIHNlbnRlbmNlIGlzJm5ic3A7anVzdCZuYnNwO2dlbmVy
aWMgb25lLiZuYnNwO1JpZ2h0IGFmdGVyIHRoZSBzZW50ZW5jZSwgd2UgZGVzY3JpYmVkIHRoYXQg
aWYgMToxIHByb3RlY3Rpb24gaXMgdXNlZCwgdGhlIHNlZ21lbnQgUFFSIGNhbiBiZSBzaGFyZWQg
YnkgdHdvIHByb3RlY3Rpb24gcGF0aHMuPC9GT05UPjwvRElWPg0KPERJVj48QlI+PEZPTlQgc2l6
ZT0zIGZhY2U9c2Fucy1zZXJpZj4mbmJzcDsyIGFib3V0IHRoZSBTaGFyZWQgbm9kZSBTRU4gd2ls
bCBzZW5kIHRoZSBwcm90ZWN0aW9uIGxvY2tpbmcgbWVzc2FnZSByZXF1ZXN0aW5nIDwvRk9OVD48
QlI+PEZPTlQgc2l6ZT0zIGZhY2U9c2Fucy1zZXJpZj4mbmJzcDsgJm5ic3A7ICZuYnNwOyBMb1Ag
dG8gdGhlIGVuZCBub2RlIG9mIHByb3RlY3RlZCBMU1AuIElNTywgYXMgU0VOIG5vZGUgaXMgTUlQ
IG9mIHRoZSBwcm90ZWN0ZWQgPC9GT05UPjxCUj48Rk9OVCBzaXplPTMgZmFjZT1zYW5zLXNlcmlm
PiZuYnNwOyAmbmJzcDsgJm5ic3A7IExTUCAsIGl0IGNhbid0IGdlbmVyYXRlIHVuc29saWNpdCBP
QU0gcGFja2V0IHRvIHNlbmQgb3RoZXIgbm9kZS4gc28gaG93IHRvIGdlbmVyYXRlPC9GT05UPiA8
QlI+PEZPTlQgc2l6ZT0zIGZhY2U9c2Fucy1zZXJpZj4mbmJzcDsgJm5ic3A7IHRoZSBwcm90ZWN0
aW9uIGxvY2tpbmcgbWVzc2FnZSByZXF1ZXN0aW5nIExPUCBpbiB0aGUgU0VOIG5vZGUgPzwvRk9O
VD4gPEJSPjxGT05UIHNpemU9Mz48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mz5bVGFl
c2lrXSZuYnNwO1RoZSBwcm90ZWN0aW9uIGxvY2tpbmcgbWVzc2FnZSBpcyBhIHJlc3BvbnNlIHRv
IHRoZSBwcm90ZWN0aW9uIHN0YXRlIGNoYW5nZSBub3RpZmljYXRpb24gbWVzc2FnZSBzZW50IGZy
b20gYSBNRVAuIEl0IGlzIHNpbWlsYXIgdG8gTFRNL0xUUiBvciBMb2NrIEludHJ1Y3QgLyBMb2Nr
IFJlcG9ydCByZWxhdGlvbnNoaXAuPC9GT05UPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxE
SVY+PEJSPjxGT05UIHNpemU9MyBmYWNlPXNhbnMtc2VyaWY+Jm5ic3A7IE1heWJlIGkgbWlzcyBz
b21ldGhpbmcgaW1wb3J0YW50PzwvRk9OVD4gPEJSPjxGT05UIHNpemU9MyBmYWNlPXNhbnMtc2Vy
aWY+Jm5ic3A7IHRoYW5rIHlvdTwvRk9OVD4gPEJSPjxCUj48Rk9OVCBzaXplPTMgZmFjZT1zYW5z
LXNlcmlmPiZuYnNwOyBiZXN0IHJlZ2FyZHM8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTMgZmFjZT1z
YW5zLXNlcmlmPiZuYnNwOyBsaXU8L0ZPTlQ+IDxCUj48QlI+PEZPTlQgY29sb3I9cmVkIHNpemU9
MyBmYWNlPXNhbnMtc2VyaWY+Jm5ic3A7ICZuYnNwOyA8L0ZPTlQ+PEJSPjxGT05UIGNvbG9yPXJl
ZCBzaXplPTMgZmFjZT1zYW5zLXNlcmlmPiZuYnNwOyAmbmJzcDsgPC9GT05UPjxGT05UIGNvbG9y
PXJlZCBzaXplPTIgZmFjZT1zYW5zLXNlcmlmPjxCUj48L0RJVj48L0ZPTlQ+DQo8RElWPg0KPFRB
QkxFPg0KPFRCT0RZPg0KPFRSPg0KPFREPiZuYnNwOw0KPFREPiZuYnNwOzwvVEQ+PC9UUj48L1RC
T0RZPjwvVEFCTEU+PC9ESVY+DQo8RElWPjxCUj48QlI+PC9ESVY+PFBSRT4tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFJm5ic3A7SW5m
b3JtYXRpb24mbmJzcDtTZWN1cml0eSZuYnNwO05vdGljZTombmJzcDtUaGUmbmJzcDtpbmZvcm1h
dGlvbiZuYnNwO2NvbnRhaW5lZCZuYnNwO2luJm5ic3A7dGhpcyZuYnNwO21haWwmbmJzcDtpcyZu
YnNwO3NvbGVseSZuYnNwO3Byb3BlcnR5Jm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtzZW5kZXIncyZu
YnNwO29yZ2FuaXphdGlvbi4mbmJzcDtUaGlzJm5ic3A7bWFpbCZuYnNwO2NvbW11bmljYXRpb24m
bmJzcDtpcyZuYnNwO2NvbmZpZGVudGlhbC4mbmJzcDtSZWNpcGllbnRzJm5ic3A7bmFtZWQmbmJz
cDthYm92ZSZuYnNwO2FyZSZuYnNwO29ibGlnYXRlZCZuYnNwO3RvJm5ic3A7bWFpbnRhaW4mbmJz
cDtzZWNyZWN5Jm5ic3A7YW5kJm5ic3A7YXJlJm5ic3A7bm90Jm5ic3A7cGVybWl0dGVkJm5ic3A7
dG8mbmJzcDtkaXNjbG9zZSZuYnNwO3RoZSZuYnNwO2NvbnRlbnRzJm5ic3A7b2YmbmJzcDt0aGlz
Jm5ic3A7Y29tbXVuaWNhdGlvbiZuYnNwO3RvJm5ic3A7b3RoZXJzLg0KVGhpcyZuYnNwO2VtYWls
Jm5ic3A7YW5kJm5ic3A7YW55Jm5ic3A7ZmlsZXMmbmJzcDt0cmFuc21pdHRlZCZuYnNwO3dpdGgm
bmJzcDtpdCZuYnNwO2FyZSZuYnNwO2NvbmZpZGVudGlhbCZuYnNwO2FuZCZuYnNwO2ludGVuZGVk
Jm5ic3A7c29sZWx5Jm5ic3A7Zm9yJm5ic3A7dGhlJm5ic3A7dXNlJm5ic3A7b2YmbmJzcDt0aGUm
bmJzcDtpbmRpdmlkdWFsJm5ic3A7b3ImbmJzcDtlbnRpdHkmbmJzcDt0byZuYnNwO3dob20mbmJz
cDt0aGV5Jm5ic3A7YXJlJm5ic3A7YWRkcmVzc2VkLiZuYnNwO0lmJm5ic3A7eW91Jm5ic3A7aGF2
ZSZuYnNwO3JlY2VpdmVkJm5ic3A7dGhpcyZuYnNwO2VtYWlsJm5ic3A7aW4mbmJzcDtlcnJvciZu
YnNwO3BsZWFzZSZuYnNwO25vdGlmeSZuYnNwO3RoZSZuYnNwO29yaWdpbmF0b3ImbmJzcDtvZiZu
YnNwO3RoZSZuYnNwO21lc3NhZ2UuJm5ic3A7QW55Jm5ic3A7dmlld3MmbmJzcDtleHByZXNzZWQm
bmJzcDtpbiZuYnNwO3RoaXMmbmJzcDttZXNzYWdlJm5ic3A7YXJlJm5ic3A7dGhvc2UmbmJzcDtv
ZiZuYnNwO3RoZSZuYnNwO2luZGl2aWR1YWwmbmJzcDtzZW5kZXIuDQpUaGlzJm5ic3A7bWVzc2Fn
ZSZuYnNwO2hhcyZuYnNwO2JlZW4mbmJzcDtzY2FubmVkJm5ic3A7Zm9yJm5ic3A7dmlydXNlcyZu
YnNwO2FuZCZuYnNwO1NwYW0mbmJzcDtieSZuYnNwO1pURSZuYnNwO0FudGktU3BhbSZuYnNwO3N5
c3RlbS4NCjwvUFJFPjwvRElWPg==

------=_NextPart_000_88F6_01CB300E.FC593050--

From curtis@occnc.com  Fri Jul 30 02:05:43 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0DF1128C29C; Fri, 30 Jul 2010 02:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.422
X-Spam-Level: 
X-Spam-Status: No, score=-2.422 tagged_above=-999 required=5 tests=[AWL=0.177,  BAYES_00=-2.599]
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 RvaLA2-78vvy; Fri, 30 Jul 2010 02:05:42 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id E033728C295; Fri, 30 Jul 2010 02:05:41 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6U966Nt036645; Fri, 30 Jul 2010 05:06:06 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007300906.o6U966Nt036645@harbor.orleans.occnc.com>
To: pwe3@ietf.org, mpls@ietf.org
From: Curtis Villamizar <curtis@occnc.com>
Date: Fri, 30 Jul 2010 05:06:06 -0400
Sender: curtis@occnc.com
Subject: [mpls] ELI as a reserved label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mpls@ietf.org
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jul 2010 09:05:43 -0000

The Entropy Label Indicator (ELI) is called for in
draft-kompella-mpls-entropy-label-01.txt

After brief discussion with Stewart and with Kireeti and Lucy Yong,
there were three uses of ELI that would benefit from making the ELI a
reserved label.  It may be premature to make any such request and the
remaining reserved label number space is sparse, so this will be
floated as a separate draft, and put on hold awaiting advancement of
the drafts that depend on it.

The three benefits of making ELI a reserved label are in:

  1.  Extending any use of entropy-label to P2MP (where there are
      multiple egress and the possibility of each egress requiring a
      separate entropy label value is problematic for the ingress).

  2.  Extending any use of entropy-label to any arbitrary position in
      the label stack such that in an aggregation LSP with aggregates
      both MPLS-TP and MPLS LSP, load split on the MPLS LSPs is
      simplified and not impacted by limiting label stack depth for
      the MPLS-TP LSPs.  This is when label stack hash is limited to
      support MPLS-TP as proposed in
      draft-villamizar-mpls-tp-multipath-00.txt .

  3.  Providing a means to carry indication of large flow as described
      in draft-yong-pwe3-enhance-ecmp-lfat-01.txt and
      draft-yong-pwe3-lfc-fat-pw-01.txt without changing the use of TC
      in a forwarding LSP label.

This would reuse one reserved label for three purposes.

This email is to gauge the reaction to this proposal (preferably among
those familiar with these drafts) before taking the time to write a
new draft proposing that a reserved label be allocated.

Curtis

From liu.guoman@zte.com.cn  Fri Jul 30 02:28:07 2010
Return-Path: <liu.guoman@zte.com.cn>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D7263A6891; Fri, 30 Jul 2010 02:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.635
X-Spam-Level: 
X-Spam-Status: No, score=-97.635 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, 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 HM0N-kIOE2M2; Fri, 30 Jul 2010 02:28:02 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id D689A3A6874; Fri, 30 Jul 2010 02:27:56 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 35102548420933; Fri, 30 Jul 2010 17:27:33 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 79973.4478639226; Fri, 30 Jul 2010 17:28:06 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o6U9KeSv069445; Fri, 30 Jul 2010 17:21:24 +0800 (CST) (envelope-from liu.guoman@zte.com.cn)
In-Reply-To: <CEC8C88293A04D06A95E6FA87537804F@etri.info>
To: Taesik Cheung <cts@etri.re.kr>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF918CBF71.8789D3B2-ON48257770.00306227-48257770.00338D2B@zte.com.cn>
From: liu.guoman@zte.com.cn
Date: Fri, 30 Jul 2010 17:21:08 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-30 17:21:10, Serialize complete at 2010-07-30 17:21:10
Content-Type: multipart/alternative; boundary="=_alternative 00338D2848257770_="
X-MAIL: mse2.zte.com.cn o6U9KeSv069445
Cc: mpls@ietf.org, mpls-bounces@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jul 2010 09:28:07 -0000

This is a multipart message in MIME format.
--=_alternative 00338D2848257770_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

VGFlc2lrDQp0aGFuayB5b3UgZm9yIHJlcGx5aW5nIC5idXQgSSBkb24ndCBhZ3JlZSB5b3VyIG9w
aW5pb25zDQpBY2NvcmRpbmcgdG8geW91ciBkZXNjcmlibGVzIGluIHRoZSBkcmFmdC4gSSB0aGlu
ayB0aGUgcHJvdGVjdGlvbiBsb2NraW5nIA0KbWVzc2FnZSBpc24ndCAgYSByZXNwb25zZSB0byB0
aGUgcHJvdGVjdGlvbiBzdGF0ZSBjaGFuZ2Ugbm90aWZpY2F0aW9uIA0KbWVzc2FnZSBzZW50IGZy
b20gYSBNRVAuDQphbmQgaXQgaXMgYWN0aXZsZXkgZ2VuZXJhdGUgYSBMb2NraW5nIFJlcXVlc3Qg
bWVzc2FnZSBmb3IgdGhlIFNFTiBub2RlLg0KZm9yIGV4YW1wbGUuIHRoZSBmb2xsb3dpbmcgZmln
dXJlIDogDQogICAgICAgICAgQS0tLS0tLUItLS0tLS1DICBELS0tLS0tRS0tLS0tLUYgDQogICAg
ICAgICAgICBcICAgTFBEMSAgIC8gICAgICAgIFwgICBMUEQzICAvIA0KICAgICAgICAgICAgICBc
ICAgICAgICAgICAgLyAgICAgICAgICAgIFwgICAgICAgICAgICAvIA0KICAgICAgICAgICAgICAg
UC0tLS0tUS0tLS0tLS0tLS1SLS0tLS1TIA0KICAgICAgICAgICAgICAvICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICBcIA0KICAgICAgICAgICAgIC8gICAgICAgICAgIExQRDIgICAg
ICAgICAgICAgICAgXCANCiAgICAgICAgICAgIC8gICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgXCANCiAgICAgICAgICAgRy0tLS0tLS0tLS0tLS0tSC0tLS0tLS0tLS0tLS0t
LUogDQphLiBOb2RlIEcgZGV0ZWN0cyB0aGUgZmFpbHVyZSwgYW5kIGluaXRpYXRlcyB0aGUgbGlu
ZWFyIHByb3RlY3Rpb24gDQogICAgICBzd2l0Y2hpbmcgZm9yIHRoZSBmYWlsZWQgd29ya2luZyBw
YXRoIEctSC1KOw0KDQogICBiLiBBdCB0aGUgc2FtZSB0aW1lLCBub2RlIEcgZ2VuZXJhdGVzIHRo
ZSBwcm90ZWN0aW9uIHN3aXRjaGluZyBldmVudCANCiAgICAgIG1lc3NhZ2Ugc2F5aW5nIHRoYXQg
YSBwcm90ZWN0aW9uIHN3aXRjaGluZyBldmVudCBoYXBwZW5lZCB0byBub2RlIA0KICAgICAgUCBh
bmQgUiwgd2hpY2ggYXJlIFNFTnMgZm9yIEotPkgtPkcuDQoNCiAgIGMuIFRoZSBTRU4gUCBjb21w
YXJlcyB0aGUgcHJvdGVjdGlvbiBzd2l0Y2hpbmcgcHJpb3JpdHkgb2YgTFBEMiB3aXRoIA0KICAg
ICAgdGhhdCBvZiBMUEQxLiBJbiB0aGlzIGV4YW1wbGUsIGFzIHRoZSBwcmlvcml0eSBvZiBMUEQx
IGlzIGhpZ2hlciANCiAgICAgIHRoYW4gTFBEMiwgU0VOIFAgZG9lcyBub3QgdGFrZSBhbiBhY3Rp
b24gdG8gbm9kZSBBLg0KICAgICAgVGhlIFNFTiBSIGNvbXBhcmVzIHRoZSBwcm90ZWN0aW9uIHN3
aXRjaGluZyBwcmlvcml0eSBvZiBMUEQyIHdpdGggDQogICAgICB0aGF0IG9mIExQRDMuIEluIHRo
aXMgZXhhbXBsZSwgYXMgdGhlIHByaW9yaXR5IG9mIExQRDMgaXMgbG93ZXIgDQogICAgICB0aGFu
IExQRDIsIFNFTiBSIHNlbmRzIHRoZSBwcm90ZWN0aW9uIGxvY2tpbmcgbWVzc2FnZSByZXF1ZXN0
aW5nIA0KICAgICAgTG9QIHRvIG5vZGUgRC4oaWYgdGhlIExvY2tpbmcgbWVzc2FnZSBpcyBhIHJl
c3BvbnNlIHRvIHRoZSANCnByb3RlY3Rpb24gDQogICAgICBzdGF0ZSBjaGFuZ2UgLCBJIHRoaW5r
IHRoZSBMb2NraW5nIG1lc3NhZ2Ugc2hvdWxkIHNlbmQgdG8gTm9kZSBHICwNCiAgICAgIG5vdCBu
b2RlIEQuIGJlY2F1c2UgYXQgdGhlIHRpbWUgdGhlcmUgaXMgbm8gcHJvdGVjdGlvbiBzdGF0ZSBj
aGFuZ2UgDQpmb3IgTFBEMiAuDQogICAgIE5vZGUgRCBjYW4ndCBzZW5kIGFueSBzdGF0ZSBjaGFu
Z2UgcmVxdWVzdCB0byBTRU4gbm9kZSBSIGZpcnN0bHkuDQogICAgIGRvIHlvdSB0aGluayBzbz8g
ICkNCg0KICAgZC4gTm9kZSBEIHRha2VzIHRoZSBwcm90ZWN0aW9uIGxvY2tpbmcgbWVzc2FnZSBh
cyBhbiBpbnB1dCB0byB0aGUgDQogICAgICBsaW5lYXIgcHJvdGVjdGlvbiBzd2l0Y2hpbmcsIGFu
ZCBmb2xsb3dzIHRoZSBsaW5lYXIgcHJvdGVjdGlvbiANCiAgICAgIHN3aXRjaGluZyBwcm9jZWR1
cmUgdG8gcHJvY2VzcyB0aGUgZW5kLXRvLWVuZCBMb1AgY29tbWFuZCANCg0KIG1heWJlIG15IHVu
ZGVyc3RhbmRpbmcgYmUgd3Jvbmc/DQoNCiAgYmVzdCByZWdhcmRzDQogICBsaXUgDQogDQoNCg0K
DQoNCg0KDQoNCg0KIlRhZXNpayBDaGV1bmciIDxjdHNAZXRyaS5yZS5rcj4gDQq3orz+yMs6ICBt
cGxzLWJvdW5jZXNAaWV0Zi5vcmcNCjIwMTAtMDctMzAgMTY6NDUNCsfrtPC4tCC4+A0KVGFlc2lr
IENoZXVuZyA8Y3RzQGV0cmkucmUua3I+DQoNCg0KytW8/sjLDQo8bGl1Lmd1b21hbkB6dGUuY29t
LmNuPiwgPHJ5b29AZXRyaS5yZS5rcj4NCrOty80NCm1wbHNAaWV0Zi5vcmcsIG1wbHMtdHBAaWV0
Zi5vcmcNCtb3zOINClJlOiBbbXBsc10gYSBxdWVzdGlvbiBhYm91dCBkcmFmdC1jaGV1bmctbXBs
cy10cC1tZXNoLXByb3RlY3Rpb24tMDENCg0KDQoNCg0KDQoNCkhpIExpdSwNCiANClRoYW5rIHlv
dSBmb3IgdGhlIGNvbW1lbnRzLg0KUGxlYXNlIHNlZSBpbi1saW5lLg0KIA0KUmVnYXJkcywNClRh
ZXNpaw0KIA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogImxpdS5ndW9tYW5A
enRlLmNvbS5jbiIgPGxpdS5ndW9tYW5AenRlLmNvbS5jbj4NCkZyb20gRGF0ZTogMjAxMC0wNy0z
MCBQTSA1OjA2OjMwDQpUbzogInJ5b29AZXRyaS5yZS5rciIgPHJ5b29AZXRyaS5yZS5rcj4sICJj
dHNAZXRyaS5yZS5rciIgPGN0c0BldHJpLnJlLmtyPg0KQ2M6ICJtcGxzQGlldGYub3JnIiA8bXBs
c0BpZXRmLm9yZz4sICJtcGxzLXRwQGlldGYub3JnIiA8bXBscy10cEBpZXRmLm9yZz4NClN1Ympl
Y3Q6IGEgcXVlc3Rpb24gYWJvdXQgZHJhZnQtY2hldW5nLW1wbHMtdHAtbWVzaC1wcm90ZWN0aW9u
LTAxDQoNCg0KIGhpLCANCiB0b2RheSBJIHJldmlld2VkIHlvdXIgdGhpcyBkcmFmdCwgSSBoYXZl
IGEgZmV3IHF1ZXN0aW9ucyBmb3IgbWVzaCANCnByb3RlY3Rpb24gDQogMSBpbiBzZWN0aW9uIDMs
IEluIG15IG1pbmQsIHRoZXJlIGlzIGEgc2VudGVuY2UgOiBJbiBib3RoIGNhc2VzLCAxOjEgb3Ig
DQoxKzEgcHJvdGVjdGlvbiBtYXkgYmUgdXNlZC4gDQogICBpZiB0aGVyZSB1c2UgMSsxIHByb3Rl
Y3Rpb24gZm9yIGVhY2ggd29ya2luZyBwYXRoLiBpdCBpcyBubyBuZWNlc3NhcnkgDQp0byBhcHBs
eSBtZXNoIHByb3RlY3Rpb24uIA0KICAgYmVhY2F1c2UgdGhlIGJhbmR3aWR0aCByZXNvdXJjZSBv
ZiBwcm90ZWN0aW9uIGlzIGVxdWFsIHRvIHRoZSBzdW0gb2YgDQpiYW5kd2lkdGggcmVzb3VyY2Ug
b2YgYWxsIA0KICAgcHJvdGVjdGVkIHBhdGguIHNvIEkgdGhpbmsgMSsxIHByb3RlY3Rpb24gc2hv
dWxkIG5vdCBiZSB1c2VkIGluIHRoZSANCm1lc2ggcHJvdGVjdGlvbi4gDQogICBkbyB5b3UgdGhp
bmsgc28/IA0KW1RhZXNpa10gWWVzLCBpZiAxKzEgcHJvdGVjdGlvbiBpcyB1c2VkLCBzaGFyZWQg
bWVzaCBwcm90ZWN0aW9uIGlzIG5vdCANCm5lY2Vzc2FyeS4gVGhlIHNlbnRlbmNlIGlzIGp1c3Qg
Z2VuZXJpYyBvbmUuIFJpZ2h0IGFmdGVyIHRoZSBzZW50ZW5jZSwgd2UgDQpkZXNjcmliZWQgdGhh
dCBpZiAxOjEgcHJvdGVjdGlvbiBpcyB1c2VkLCB0aGUgc2VnbWVudCBQUVIgY2FuIGJlIHNoYXJl
ZCBieSANCnR3byBwcm90ZWN0aW9uIHBhdGhzLg0KDQogMiBhYm91dCB0aGUgU2hhcmVkIG5vZGUg
U0VOIHdpbGwgc2VuZCB0aGUgcHJvdGVjdGlvbiBsb2NraW5nIG1lc3NhZ2UgDQpyZXF1ZXN0aW5n
IA0KICAgICAgTG9QIHRvIHRoZSBlbmQgbm9kZSBvZiBwcm90ZWN0ZWQgTFNQLiBJTU8sIGFzIFNF
TiBub2RlIGlzIE1JUCBvZiB0aGUgDQpwcm90ZWN0ZWQgDQogICAgICBMU1AgLCBpdCBjYW4ndCBn
ZW5lcmF0ZSB1bnNvbGljaXQgT0FNIHBhY2tldCB0byBzZW5kIG90aGVyIG5vZGUuIHNvIA0KaG93
IHRvIGdlbmVyYXRlIA0KICAgIHRoZSBwcm90ZWN0aW9uIGxvY2tpbmcgbWVzc2FnZSByZXF1ZXN0
aW5nIExPUCBpbiB0aGUgU0VOIG5vZGUgPyANCltUYWVzaWtdIFRoZSBwcm90ZWN0aW9uIGxvY2tp
bmcgbWVzc2FnZSBpcyBhIHJlc3BvbnNlIHRvIHRoZSBwcm90ZWN0aW9uIA0Kc3RhdGUgY2hhbmdl
IG5vdGlmaWNhdGlvbiBtZXNzYWdlIHNlbnQgZnJvbSBhIE1FUC4gSXQgaXMgc2ltaWxhciB0byAN
CkxUTS9MVFIgb3IgTG9jayBJbnRydWN0IC8gTG9jayBSZXBvcnQgcmVsYXRpb25zaGlwLg0KIA0K
DQogIE1heWJlIGkgbWlzcyBzb21ldGhpbmcgaW1wb3J0YW50PyANCiAgdGhhbmsgeW91IA0KDQog
IGJlc3QgcmVnYXJkcyANCiAgbGl1IA0KDQogDQogDQogDQogDQoNCg0KLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClpURSBJbmZvcm1hdGlv
biBTZWN1cml0eSBOb3RpY2U6IFRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaW4gdGhpcyBtYWls
IGlzIA0Kc29sZWx5IHByb3BlcnR5IG9mIHRoZSBzZW5kZXIncyBvcmdhbml6YXRpb24uIFRoaXMg
bWFpbCBjb21tdW5pY2F0aW9uIGlzIA0KY29uZmlkZW50aWFsLiBSZWNpcGllbnRzIG5hbWVkIGFi
b3ZlIGFyZSBvYmxpZ2F0ZWQgdG8gbWFpbnRhaW4gc2VjcmVjeSBhbmQgDQphcmUgbm90IHBlcm1p
dHRlZCB0byBkaXNjbG9zZSB0aGUgY29udGVudHMgb2YgdGhpcyBjb21tdW5pY2F0aW9uIHRvIA0K
b3RoZXJzLg0KVGhpcyBlbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgYXJl
IGNvbmZpZGVudGlhbCBhbmQgaW50ZW5kZWQgDQpzb2xlbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGlu
ZGl2aWR1YWwgb3IgZW50aXR5IHRvIHdob20gdGhleSBhcmUgYWRkcmVzc2VkLiANCklmIHlvdSBo
YXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3IgcGxlYXNlIG5vdGlmeSB0aGUgb3JpZ2lu
YXRvciBvZiANCnRoZSBtZXNzYWdlLiBBbnkgdmlld3MgZXhwcmVzc2VkIGluIHRoaXMgbWVzc2Fn
ZSBhcmUgdGhvc2Ugb2YgdGhlIA0KaW5kaXZpZHVhbCBzZW5kZXIuDQpUaGlzIG1lc3NhZ2UgaGFz
IGJlZW4gc2Nhbm5lZCBmb3IgdmlydXNlcyBhbmQgU3BhbSBieSBaVEUgQW50aS1TcGFtIA0Kc3lz
dGVtLg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1w
bHMgbWFpbGluZyBsaXN0DQptcGxzQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL21wbHMNCg0KDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClpURSBJbmZvcm1hdGlvbiBTZWN1cml0eSBOb3Rp
Y2U6IFRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaW4gdGhpcyBtYWlsIGlzIHNvbGVseSBwcm9w
ZXJ0eSBvZiB0aGUgc2VuZGVyJ3Mgb3JnYW5pemF0aW9uLiBUaGlzIG1haWwgY29tbXVuaWNhdGlv
biBpcyBjb25maWRlbnRpYWwuIFJlY2lwaWVudHMgbmFtZWQgYWJvdmUgYXJlIG9ibGlnYXRlZCB0
byBtYWludGFpbiBzZWNyZWN5IGFuZCBhcmUgbm90IHBlcm1pdHRlZCB0byBkaXNjbG9zZSB0aGUg
Y29udGVudHMgb2YgdGhpcyBjb21tdW5pY2F0aW9uIHRvIG90aGVycy4NClRoaXMgZW1haWwgYW5k
IGFueSBmaWxlcyB0cmFuc21pdHRlZCB3aXRoIGl0IGFyZSBjb25maWRlbnRpYWwgYW5kIGludGVu
ZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgdG8gd2hv
bSB0aGV5IGFyZSBhZGRyZXNzZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4g
ZXJyb3IgcGxlYXNlIG5vdGlmeSB0aGUgb3JpZ2luYXRvciBvZiB0aGUgbWVzc2FnZS4gQW55IHZp
ZXdzIGV4cHJlc3NlZCBpbiB0aGlzIG1lc3NhZ2UgYXJlIHRob3NlIG9mIHRoZSBpbmRpdmlkdWFs
IHNlbmRlci4NClRoaXMgbWVzc2FnZSBoYXMgYmVlbiBzY2FubmVkIGZvciB2aXJ1c2VzIGFuZCBT
cGFtIGJ5IFpURSBBbnRpLVNwYW0gc3lzdGVtLg0K
--=_alternative 00338D2848257770_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPlRhZXNpazwvZm9udD4NCjxicj48
Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+dGhhbmsgeW91IGZvciByZXBseWluZyAuYnV0
IEkgZG9uJ3QNCmFncmVlIHlvdXIgb3BpbmlvbnM8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zIGZh
Y2U9InNhbnMtc2VyaWYiPkFjY29yZGluZyB0byB5b3VyIGRlc2NyaWJsZXMgaW4gdGhlDQpkcmFm
dC4gPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJBcmlhbCI+SSB0aGluayB0aGUgcHJvdGVjdGlv
biBsb2NraW5nDQptZXNzYWdlIGlzbid0ICZuYnNwO2EgcmVzcG9uc2UgdG8gdGhlIHByb3RlY3Rp
b24gc3RhdGUgY2hhbmdlIG5vdGlmaWNhdGlvbg0KbWVzc2FnZSBzZW50IGZyb20gYSBNRVAuPC9m
b250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJBcmlhbCI+YW5kIGl0IGlzIGFjdGl2bGV5IGdl
bmVyYXRlIGEgTG9ja2luZyBSZXF1ZXN0DQptZXNzYWdlIGZvciB0aGUgU0VOIG5vZGUuPC9mb250
Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJBcmlhbCI+Zm9yIGV4YW1wbGUuIHRoZSBmb2xsb3dp
bmcgZmlndXJlIDogPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJBcmlhbCI+Jm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBBLS0tLS0tQi0tLS0tLUMNCiZuYnNwO0QtLS0t
LS1FLS0tLS0tRiA8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zIGZhY2U9IkFyaWFsIj4mbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KXCAmbmJzcDsgTFBEMSAmbmJzcDsg
LyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtcICZuYnNwOyBMUEQzICZuYnNwOy8NCjwvZm9u
dD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iQXJpYWwiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7DQombmJzcDsgXCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOy8gJm5ic3A7ICZuYnNwOyAmbmJzcDsNCiZuYnNwOyAmbmJzcDsgJm5ic3A7
XCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOy8gPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MyBmYWNlPSJBcmlhbCI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsNCiZuYnNwOyAmbmJzcDtQLS0tLS1RLS0tLS0tLS0tLVItLS0tLVMgPC9mb250
Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJBcmlhbCI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsNCiZuYnNwOyAvICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7DQombmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFwgPC9mb250Pg0KPGJyPjxmb250IHNp
emU9MyBmYWNlPSJBcmlhbCI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsNCiZuYnNwOy8gJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBMUEQyICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7XCA8L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0zIGZhY2U9IkFyaWFsIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOw0KLyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsNCiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO1wNCjwvZm9u
dD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iQXJpYWwiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7Ry0tLS0tLS0tLS0tLS0tSC0tLS0tLS0tLS0tLS0tLUoNCjwvZm9u
dD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iQXJpYWwiPmEuIE5vZGUgRyBkZXRlY3RzIHRoZSBm
YWlsdXJlLCBhbmQgaW5pdGlhdGVzDQp0aGUgbGluZWFyIHByb3RlY3Rpb24gPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MyBmYWNlPSJBcmlhbCI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgc3dpdGNoaW5n
IGZvciB0aGUgZmFpbGVkDQp3b3JraW5nIHBhdGggRy1ILUo7PC9mb250Pg0KPGJyPg0KPGJyPjxm
b250IHNpemU9MyBmYWNlPSJBcmlhbCI+Jm5ic3A7ICZuYnNwO2IuIEF0IHRoZSBzYW1lIHRpbWUs
IG5vZGUgRw0KZ2VuZXJhdGVzIHRoZSBwcm90ZWN0aW9uIHN3aXRjaGluZyBldmVudCA8L2ZvbnQ+
DQo8YnI+PGZvbnQgc2l6ZT0zIGZhY2U9IkFyaWFsIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyBtZXNz
YWdlIHNheWluZyB0aGF0DQphIHByb3RlY3Rpb24gc3dpdGNoaW5nIGV2ZW50IGhhcHBlbmVkIHRv
IG5vZGUgPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJBcmlhbCI+Jm5ic3A7ICZuYnNw
OyAmbmJzcDsgUCBhbmQgUiwgd2hpY2ggYXJlIFNFTnMNCmZvciBKLSZndDtILSZndDtHLjwvZm9u
dD4NCjxicj4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iQXJpYWwiPiZuYnNwOyAmbmJzcDtjLiBU
aGUgU0VOIFAgY29tcGFyZXMgdGhlIHByb3RlY3Rpb24NCnN3aXRjaGluZyBwcmlvcml0eSBvZiBM
UEQyIHdpdGggPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJBcmlhbCI+Jm5ic3A7ICZu
YnNwOyAmbmJzcDsgdGhhdCBvZiBMUEQxLiBJbiB0aGlzDQpleGFtcGxlLCBhcyB0aGUgcHJpb3Jp
dHkgb2YgTFBEMSBpcyBoaWdoZXIgPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJBcmlh
bCI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgdGhhbiBMUEQyLCBTRU4gUCBkb2VzDQpub3QgdGFrZSBh
biBhY3Rpb24gdG8gbm9kZSBBLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iQXJpYWwi
PiZuYnNwOyAmbmJzcDsgJm5ic3A7IFRoZSBTRU4gUiBjb21wYXJlcyB0aGUNCnByb3RlY3Rpb24g
c3dpdGNoaW5nIHByaW9yaXR5IG9mIExQRDIgd2l0aCA8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0z
IGZhY2U9IkFyaWFsIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyB0aGF0IG9mIExQRDMuIEluIHRoaXMN
CmV4YW1wbGUsIGFzIHRoZSBwcmlvcml0eSBvZiBMUEQzIGlzIGxvd2VyIDwvZm9udD4NCjxicj48
Zm9udCBzaXplPTMgZmFjZT0iQXJpYWwiPiZuYnNwOyAmbmJzcDsgJm5ic3A7IHRoYW4gTFBEMiwg
U0VOIFIgc2VuZHMNCnRoZSBwcm90ZWN0aW9uIGxvY2tpbmcgbWVzc2FnZSByZXF1ZXN0aW5nIDwv
Zm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iQXJpYWwiPiZuYnNwOyAmbmJzcDsgJm5ic3A7
IExvUCB0byBub2RlIEQuKDwvZm9udD48Zm9udCBzaXplPTMgY29sb3I9cmVkIGZhY2U9IkFyaWFs
Ij5pZg0KdGhlIExvY2tpbmcgbWVzc2FnZSBpcyBhIHJlc3BvbnNlIHRvIHRoZSBwcm90ZWN0aW9u
IDwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgY29sb3I9cmVkIGZhY2U9IkFyaWFsIj4mbmJzcDsg
Jm5ic3A7ICZuYnNwOyBzdGF0ZSBjaGFuZ2UNCiwgSSB0aGluayB0aGUgTG9ja2luZyBtZXNzYWdl
IHNob3VsZCBzZW5kIHRvIE5vZGUgRyAsPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBjb2xvcj1y
ZWQgZmFjZT0iQXJpYWwiPiZuYnNwOyAmbmJzcDsgJm5ic3A7IG5vdCBub2RlIEQ8L2ZvbnQ+PGZv
bnQgc2l6ZT0zIGZhY2U9IkFyaWFsIj4uDQo8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGNvbG9yPXJlZCBm
YWNlPSJBcmlhbCI+YmVjYXVzZSBhdCB0aGUgdGltZSB0aGVyZSBpcw0Kbm8gcHJvdGVjdGlvbiBz
dGF0ZSBjaGFuZ2UgZm9yIExQRDIgLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgY29sb3I9cmVk
IGZhY2U9IkFyaWFsIj4mbmJzcDsgJm5ic3A7ICZuYnNwO05vZGUgRCBjYW4ndA0Kc2VuZCBhbnkg
c3RhdGUgY2hhbmdlIHJlcXVlc3QgdG8gU0VOIG5vZGUgUiBmaXJzdGx5LjwvZm9udD4NCjxicj48
Zm9udCBzaXplPTMgY29sb3I9cmVkIGZhY2U9IkFyaWFsIj4mbmJzcDsgJm5ic3A7ICZuYnNwO2Rv
IHlvdSB0aGluaw0Kc28/ICZuYnNwOyk8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0zIGZh
Y2U9IkFyaWFsIj4mbmJzcDsgJm5ic3A7ZC4gTm9kZSBEIHRha2VzIHRoZSBwcm90ZWN0aW9uDQps
b2NraW5nIG1lc3NhZ2UgYXMgYW4gaW5wdXQgdG8gdGhlIDwvZm9udD4NCjxicj48Zm9udCBzaXpl
PTMgZmFjZT0iQXJpYWwiPiZuYnNwOyAmbmJzcDsgJm5ic3A7IGxpbmVhciBwcm90ZWN0aW9uIHN3
aXRjaGluZywNCmFuZCBmb2xsb3dzIHRoZSBsaW5lYXIgcHJvdGVjdGlvbiA8L2ZvbnQ+DQo8YnI+
PGZvbnQgc2l6ZT0zIGZhY2U9IkFyaWFsIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyBzd2l0Y2hpbmcg
cHJvY2VkdXJlDQp0byBwcm9jZXNzIHRoZSBlbmQtdG8tZW5kIExvUCBjb21tYW5kIDwvZm9udD4N
Cjxicj4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iQXJpYWwiPiZuYnNwO21heWJlIG15IHVuZGVy
c3RhbmRpbmcgYmUgd3Jvbmc/PC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJB
cmlhbCI+Jm5ic3A7IGJlc3QgcmVnYXJkczwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0i
QXJpYWwiPiZuYnNwOyAmbmJzcDtsaXUgPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJB
cmlhbCI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNl
PSJzYW5zLXNlcmlmIj48YnI+DQo8L2ZvbnQ+DQo8dGFibGU+DQo8dHI+DQo8dGQ+DQo8ZGl2IGFs
aWduPWNlbnRlcj48L2Rpdj4NCjx0ZD48L3RhYmxlPg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0K
PHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZCB3aWR0aD0zNSU+PGZvbnQg
c2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjxiPiZxdW90O1RhZXNpayBDaGV1bmcmcXVvdDsNCiZs
dDtjdHNAZXRyaS5yZS5rciZndDs8L2I+IDwvZm9udD4NCjxicj48Zm9udCBzaXplPTEgZmFjZT0i
c2Fucy1zZXJpZiI+t6K8/sjLOiAmbmJzcDttcGxzLWJvdW5jZXNAaWV0Zi5vcmc8L2ZvbnQ+DQo8
cD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+MjAxMC0wNy0zMCAxNjo0NTwvZm9udD4N
Cjx0YWJsZSBib3JkZXI+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZCBiZ2NvbG9yPXdoaXRlPg0KPGRp
diBhbGlnbj1jZW50ZXI+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPsfrtPC4tCC4+Dxi
cj4NClRhZXNpayBDaGV1bmcgJmx0O2N0c0BldHJpLnJlLmtyJmd0OzwvZm9udD48L2Rpdj48L3Rh
YmxlPg0KPGJyPg0KPHRkIHdpZHRoPTY0JT4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGln
bj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNl
cmlmIj7K1bz+yMs8L2ZvbnQ+PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2Vy
aWYiPiZsdDtsaXUuZ3VvbWFuQHp0ZS5jb20uY24mZ3Q7LCAmbHQ7cnlvb0BldHJpLnJlLmtyJmd0
OzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBz
aXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+s63LzTwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXpl
PTEgZmFjZT0ic2Fucy1zZXJpZiI+bXBsc0BpZXRmLm9yZywgbXBscy10cEBpZXRmLm9yZzwvZm9u
dD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEg
ZmFjZT0ic2Fucy1zZXJpZiI+1vfM4jwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEgZmFj
ZT0ic2Fucy1zZXJpZiI+UmU6IFttcGxzXSBhIHF1ZXN0aW9uIGFib3V0IGRyYWZ0LWNoZXVuZy1t
cGxzLXRwLW1lc2gtcHJvdGVjdGlvbi0wMTwvZm9udD48L3RhYmxlPg0KPGJyPg0KPHRhYmxlPg0K
PHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8dGQ+PC90YWJsZT4NCjxicj48L3RhYmxlPg0KPGJyPg0K
PGJyPg0KPGJyPjxmb250IHNpemU9Mj5IaSBMaXUsPC9mb250Pg0KPGJyPjxmb250IHNpemU9Mj4m
bmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yPlRoYW5rIHlvdSBmb3IgdGhlIGNvbW1lbnRz
LjwvZm9udD4NCjxicj48Zm9udCBzaXplPTI+UGxlYXNlIHNlZSBpbi1saW5lLjwvZm9udD4NCjxi
cj48Zm9udCBzaXplPTI+Jm5ic3A7PC9mb250Pg0KPGJyPjxmb250IHNpemU9Mj5SZWdhcmRzLDwv
Zm9udD4NCjxicj48Zm9udCBzaXplPTI+VGFlc2lrPC9mb250Pg0KPGJyPjxmb250IHNpemU9Mj4m
bmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkFyaWFsIj48YnI+DQotLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLTxiPjxicj4NCkZyb206PC9iPiAmcXVvdDtsaXUuZ3VvbWFuQHp0
ZS5jb20uY24mcXVvdDsgJmx0O2xpdS5ndW9tYW5AenRlLmNvbS5jbiZndDs8Yj48YnI+DQpGcm9t
IERhdGU6PC9iPiAyMDEwLTA3LTMwIFBNIDU6MDY6MzA8Yj48YnI+DQpUbzo8L2I+ICZxdW90O3J5
b29AZXRyaS5yZS5rciZxdW90OyAmbHQ7cnlvb0BldHJpLnJlLmtyJmd0OywgJnF1b3Q7Y3RzQGV0
cmkucmUua3ImcXVvdDsNCiZsdDtjdHNAZXRyaS5yZS5rciZndDs8Yj48YnI+DQpDYzo8L2I+ICZx
dW90O21wbHNAaWV0Zi5vcmcmcXVvdDsgJmx0O21wbHNAaWV0Zi5vcmcmZ3Q7LCAmcXVvdDttcGxz
LXRwQGlldGYub3JnJnF1b3Q7DQombHQ7bXBscy10cEBpZXRmLm9yZyZndDs8Yj48YnI+DQpTdWJq
ZWN0OjwvYj4gYSBxdWVzdGlvbiBhYm91dCBkcmFmdC1jaGV1bmctbXBscy10cC1tZXNoLXByb3Rl
Y3Rpb24tMDE8YnI+DQo8YnI+DQo8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYi
Pjxicj4NCiBoaSw8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9IkFyaWFsIj4gPC9mb250Pjxmb250
IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogdG9kYXkgSSByZXZpZXdlZCB5b3VyIHRo
aXMgZHJhZnQsIEkgaGF2ZSBhIGZldyBxdWVzdGlvbnMgZm9yIG1lc2ggcHJvdGVjdGlvbg0KPGJy
Pg0KIDEgaW4gc2VjdGlvbiAzLCBJbiBteSBtaW5kLCB0aGVyZSBpcyBhIHNlbnRlbmNlIDogPC9m
b250Pjxmb250IHNpemU9MyBjb2xvcj1yZWQgZmFjZT0ic2Fucy1zZXJpZiI+SW4NCmJvdGggY2Fz
ZXMsIDE6MSBvciAxKzEgcHJvdGVjdGlvbiBtYXkgYmUgdXNlZC4gPGJyPg0KICZuYnNwOzwvZm9u
dD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IGlmIHRoZXJlIHVzZSAxKzEgcHJvdGVj
dGlvbg0KZm9yIGVhY2ggd29ya2luZyBwYXRoLiBpdCBpcyBubyBuZWNlc3NhcnkgdG8gYXBwbHkg
bWVzaCBwcm90ZWN0aW9uLjwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPg0KPC9mb250
Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7IGJlYWNhdXNlIHRo
ZSBiYW5kd2lkdGggcmVzb3VyY2Ugb2YgcHJvdGVjdGlvbiBpcyBlcXVhbCB0byB0aGUgc3VtDQpv
ZiBiYW5kd2lkdGggcmVzb3VyY2Ugb2YgYWxsIDxicj4NCiAmbmJzcDsgcHJvdGVjdGVkIHBhdGgu
IHNvIEkgdGhpbmsgMSsxIHByb3RlY3Rpb24gc2hvdWxkIG5vdCBiZSB1c2VkIGluDQp0aGUgbWVz
aCBwcm90ZWN0aW9uLjwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPiA8L2ZvbnQ+PGZv
bnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgZG8geW91IHRoaW5rIHNv
PzwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPiA8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6
ZT0zIGZhY2U9IkFyaWFsIj5bVGFlc2lrXSBZZXMsIGlmIDErMSBwcm90ZWN0aW9uIGlzIHVzZWQs
DQpzaGFyZWQgbWVzaCBwcm90ZWN0aW9uIGlzIG5vdCBuZWNlc3NhcnkuIFRoZSBzZW50ZW5jZSBp
cyBqdXN0IGdlbmVyaWMgb25lLg0KUmlnaHQgYWZ0ZXIgdGhlIHNlbnRlbmNlLCB3ZSBkZXNjcmli
ZWQgdGhhdCBpZiAxOjEgcHJvdGVjdGlvbiBpcyB1c2VkLA0KdGhlIHNlZ21lbnQgUFFSIGNhbiBi
ZSBzaGFyZWQgYnkgdHdvIHByb3RlY3Rpb24gcGF0aHMuPC9mb250Pg0KPGJyPjxmb250IHNpemU9
MyBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogMiBhYm91dCB0aGUgU2hhcmVkIG5vZGUgU0VOIHdp
bGwgc2VuZCB0aGUgcHJvdGVjdGlvbiBsb2NraW5nIG1lc3NhZ2UgcmVxdWVzdGluZw0KPGJyPg0K
ICZuYnNwOyAmbmJzcDsgJm5ic3A7TG9QIHRvIHRoZSBlbmQgbm9kZSBvZiBwcm90ZWN0ZWQgTFNQ
LiBJTU8sIGFzIFNFTg0Kbm9kZSBpcyBNSVAgb2YgdGhlIHByb3RlY3RlZCA8YnI+DQogJm5ic3A7
ICZuYnNwOyAmbmJzcDtMU1AgLCBpdCBjYW4ndCBnZW5lcmF0ZSB1bnNvbGljaXQgT0FNIHBhY2tl
dCB0byBzZW5kDQpvdGhlciBub2RlLiBzbyBob3cgdG8gZ2VuZXJhdGU8L2ZvbnQ+PGZvbnQgc2l6
ZT0yIGZhY2U9IkFyaWFsIj4gPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj48
YnI+DQogJm5ic3A7ICZuYnNwO3RoZSBwcm90ZWN0aW9uIGxvY2tpbmcgbWVzc2FnZSByZXF1ZXN0
aW5nIExPUCBpbiB0aGUgU0VODQpub2RlID88L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9IkFyaWFs
Ij4gPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJBcmlhbCI+W1RhZXNpa10gVGhlIHBy
b3RlY3Rpb24gbG9ja2luZyBtZXNzYWdlIGlzDQphIHJlc3BvbnNlIHRvIHRoZSBwcm90ZWN0aW9u
IHN0YXRlIGNoYW5nZSBub3RpZmljYXRpb24gbWVzc2FnZSBzZW50IGZyb20NCmEgTUVQLiBJdCBp
cyBzaW1pbGFyIHRvIExUTS9MVFIgb3IgTG9jayBJbnRydWN0IC8gTG9jayBSZXBvcnQgcmVsYXRp
b25zaGlwLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPiZuYnNwOzwvZm9u
dD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwO01heWJl
IGkgbWlzcyBzb21ldGhpbmcgaW1wb3J0YW50PzwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0iQXJp
YWwiPg0KPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7
dGhhbmsgeW91PC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJBcmlhbCI+IDxicj4NCjwvZm9udD48
Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwO2Jlc3QgcmVnYXJkczwv
Zm9udD48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9
InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDtsaXU8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9IkFy
aWFsIj4gPGJyPg0KPC9mb250Pjxmb250IHNpemU9MyBjb2xvcj1yZWQgZmFjZT0ic2Fucy1zZXJp
ZiI+PGJyPg0KICZuYnNwOyAmbmJzcDs8YnI+DQogJm5ic3A7ICZuYnNwOzwvZm9udD4NCjx0YWJs
ZSB3aWR0aD0xMDAlPg0KPHRyPg0KPHRkIHdpZHRoPTYzJT48Zm9udCBzaXplPTM+Jm5ic3A7IDwv
Zm9udD4NCjx0ZCB3aWR0aD0zNiU+PGZvbnQgc2l6ZT0zPiZuYnNwOzwvZm9udD48L3RhYmxlPg0K
PGJyPjxmb250IHNpemU9MiBmYWNlPSJBcmlhbCI+PGJyPg0KPC9mb250Pg0KPGJyPjxmb250IHNp
emU9MiBmYWNlPSJBcmlhbCI+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS08YnI+DQpaVEUgSW5mb3JtYXRpb24gU2VjdXJpdHkgTm90aWNlOiBU
aGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWFpbA0KaXMgc29sZWx5IHByb3BlcnR5
IG9mIHRoZSBzZW5kZXIncyBvcmdhbml6YXRpb24uIFRoaXMgbWFpbCBjb21tdW5pY2F0aW9uDQpp
cyBjb25maWRlbnRpYWwuIFJlY2lwaWVudHMgbmFtZWQgYWJvdmUgYXJlIG9ibGlnYXRlZCB0byBt
YWludGFpbiBzZWNyZWN5DQphbmQgYXJlIG5vdCBwZXJtaXR0ZWQgdG8gZGlzY2xvc2UgdGhlIGNv
bnRlbnRzIG9mIHRoaXMgY29tbXVuaWNhdGlvbiB0bw0Kb3RoZXJzLjxicj4NClRoaXMgZW1haWwg
YW5kIGFueSBmaWxlcyB0cmFuc21pdHRlZCB3aXRoIGl0IGFyZSBjb25maWRlbnRpYWwgYW5kIGlu
dGVuZGVkDQpzb2xlbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IHRv
IHdob20gdGhleSBhcmUgYWRkcmVzc2VkLg0KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFp
bCBpbiBlcnJvciBwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIG9mDQp0aGUgbWVzc2FnZS4g
QW55IHZpZXdzIGV4cHJlc3NlZCBpbiB0aGlzIG1lc3NhZ2UgYXJlIHRob3NlIG9mIHRoZSBpbmRp
dmlkdWFsDQpzZW5kZXIuPGJyPg0KVGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNjYW5uZWQgZm9yIHZp
cnVzZXMgYW5kIFNwYW0gYnkgWlRFIEFudGktU3BhbSBzeXN0ZW0uPGJyPg0KPC9mb250Pjxmb250
IHNpemU9Mj48dHQ+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X188YnI+DQptcGxzIG1haWxpbmcgbGlzdDxicj4NCm1wbHNAaWV0Zi5vcmc8YnI+DQpodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHM8YnI+DQo8L3R0PjwvZm9udD4NCjxi
cj4NCjxicj48cHJlPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0NClpURSZuYnNwO0luZm9ybWF0aW9uJm5ic3A7U2VjdXJpdHkmbmJzcDtO
b3RpY2U6Jm5ic3A7VGhlJm5ic3A7aW5mb3JtYXRpb24mbmJzcDtjb250YWluZWQmbmJzcDtpbiZu
YnNwO3RoaXMmbmJzcDttYWlsJm5ic3A7aXMmbmJzcDtzb2xlbHkmbmJzcDtwcm9wZXJ0eSZuYnNw
O29mJm5ic3A7dGhlJm5ic3A7c2VuZGVyJ3MmbmJzcDtvcmdhbml6YXRpb24uJm5ic3A7VGhpcyZu
YnNwO21haWwmbmJzcDtjb21tdW5pY2F0aW9uJm5ic3A7aXMmbmJzcDtjb25maWRlbnRpYWwuJm5i
c3A7UmVjaXBpZW50cyZuYnNwO25hbWVkJm5ic3A7YWJvdmUmbmJzcDthcmUmbmJzcDtvYmxpZ2F0
ZWQmbmJzcDt0byZuYnNwO21haW50YWluJm5ic3A7c2VjcmVjeSZuYnNwO2FuZCZuYnNwO2FyZSZu
YnNwO25vdCZuYnNwO3Blcm1pdHRlZCZuYnNwO3RvJm5ic3A7ZGlzY2xvc2UmbmJzcDt0aGUmbmJz
cDtjb250ZW50cyZuYnNwO29mJm5ic3A7dGhpcyZuYnNwO2NvbW11bmljYXRpb24mbmJzcDt0byZu
YnNwO290aGVycy4NClRoaXMmbmJzcDtlbWFpbCZuYnNwO2FuZCZuYnNwO2FueSZuYnNwO2ZpbGVz
Jm5ic3A7dHJhbnNtaXR0ZWQmbmJzcDt3aXRoJm5ic3A7aXQmbmJzcDthcmUmbmJzcDtjb25maWRl
bnRpYWwmbmJzcDthbmQmbmJzcDtpbnRlbmRlZCZuYnNwO3NvbGVseSZuYnNwO2ZvciZuYnNwO3Ro
ZSZuYnNwO3VzZSZuYnNwO29mJm5ic3A7dGhlJm5ic3A7aW5kaXZpZHVhbCZuYnNwO29yJm5ic3A7
ZW50aXR5Jm5ic3A7dG8mbmJzcDt3aG9tJm5ic3A7dGhleSZuYnNwO2FyZSZuYnNwO2FkZHJlc3Nl
ZC4mbmJzcDtJZiZuYnNwO3lvdSZuYnNwO2hhdmUmbmJzcDtyZWNlaXZlZCZuYnNwO3RoaXMmbmJz
cDtlbWFpbCZuYnNwO2luJm5ic3A7ZXJyb3ImbmJzcDtwbGVhc2UmbmJzcDtub3RpZnkmbmJzcDt0
aGUmbmJzcDtvcmlnaW5hdG9yJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDttZXNzYWdlLiZuYnNwO0Fu
eSZuYnNwO3ZpZXdzJm5ic3A7ZXhwcmVzc2VkJm5ic3A7aW4mbmJzcDt0aGlzJm5ic3A7bWVzc2Fn
ZSZuYnNwO2FyZSZuYnNwO3Rob3NlJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtpbmRpdmlkdWFsJm5i
c3A7c2VuZGVyLg0KVGhpcyZuYnNwO21lc3NhZ2UmbmJzcDtoYXMmbmJzcDtiZWVuJm5ic3A7c2Nh
bm5lZCZuYnNwO2ZvciZuYnNwO3ZpcnVzZXMmbmJzcDthbmQmbmJzcDtTcGFtJm5ic3A7YnkmbmJz
cDtaVEUmbmJzcDtBbnRpLVNwYW0mbmJzcDtzeXN0ZW0uDQo8L3ByZT4=
--=_alternative 00338D2848257770_=--


From shane@castlepoint.net  Fri Jul 30 02:34:27 2010
Return-Path: <shane@castlepoint.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 046AB28C2D4; Fri, 30 Jul 2010 02:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g-2JKuEvyzOl; Fri, 30 Jul 2010 02:34:25 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 0B32528C28A; Fri, 30 Jul 2010 02:34:25 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id AAFF036817F; Fri, 30 Jul 2010 03:34:49 -0600 (MDT)
Received: from host2.tcb.net (64.78.235.218 [64.78.235.218]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Fri, 30 Jul 2010 03:34:49 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.235.218; client-port=53588; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <201007300906.o6U966Nt036645@harbor.orleans.occnc.com>
Date: Fri, 30 Jul 2010 11:34:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0DEFA7EF-8DC4-4EF2-ABDF-0404FC32B992@castlepoint.net>
References: <201007300906.o6U966Nt036645@harbor.orleans.occnc.com>
To: mpls@ietf.org
X-Mailer: Apple Mail (2.1081)
Cc: pwe3@ietf.org
Subject: Re: [mpls] ELI as a reserved label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jul 2010 09:34:27 -0000

Curtis,

On Jul 30, 2010, at 11:06 GMT+02:00, Curtis Villamizar wrote:
> The Entropy Label Indicator (ELI) is called for in
> draft-kompella-mpls-entropy-label-01.txt
>=20
> After brief discussion with Stewart and with Kireeti and Lucy Yong,
> there were three uses of ELI that would benefit from making the ELI a
> reserved label.  It may be premature to make any such request and the
> remaining reserved label number space is sparse, so this will be
> floated as a separate draft, and put on hold awaiting advancement of
> the drafts that depend on it.
>=20
> The three benefits of making ELI a reserved label are in:
>=20
>  1.  Extending any use of entropy-label to P2MP (where there are
>      multiple egress and the possibility of each egress requiring a
>      separate entropy label value is problematic for the ingress).
>=20
>  2.  Extending any use of entropy-label to any arbitrary position in
>      the label stack such that in an aggregation LSP with aggregates
>      both MPLS-TP and MPLS LSP, load split on the MPLS LSPs is
>      simplified and not impacted by limiting label stack depth for
>      the MPLS-TP LSPs.  This is when label stack hash is limited to
>      support MPLS-TP as proposed in
>      draft-villamizar-mpls-tp-multipath-00.txt .

I agree there are benefits to a reserved label for the above two =
applications.  Most importantly, a receiving node would have pretty =
clearly semantics that what [immediately] follows a reserved ELI is the =
entropy-label, regardless of where the ELI is in the MPLS label stack =
and without needing to be in the signaling path to know what is the ELI =
value.


>  3.  Providing a means to carry indication of large flow as described
>      in draft-yong-pwe3-enhance-ecmp-lfat-01.txt and
>      draft-yong-pwe3-lfc-fat-pw-01.txt without changing the use of TC
>      in a forwarding LSP label.

I'm unclear how a single, reserved label would be a means of signaling a =
large vs. small flow.  How can a single label represent two states =
(large vs. small flow)?

Thanks,

-shane



> This would reuse one reserved label for three purposes.
>=20
> This email is to gauge the reaction to this proposal (preferably among
> those familiar with these drafts) before taking the time to write a
> new draft proposing that a reserved label be allocated.
>=20
> Curtis
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From ryoo@etri.re.kr  Fri Jul 30 03:22:29 2010
Return-Path: <ryoo@etri.re.kr>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D952A3A67B7 for <mpls@core3.amsl.com>; Fri, 30 Jul 2010 03:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.038
X-Spam-Level: 
X-Spam-Status: No, score=-100.038 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, MPART_ALT_DIFF=0.739, 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 Fq27GHgUFhdb for <mpls@core3.amsl.com>; Fri, 30 Jul 2010 03:22:28 -0700 (PDT)
Received: from email1.etri.info (email1.etri.re.kr [129.254.16.131]) by core3.amsl.com (Postfix) with ESMTP id 2EC9D3A67E1 for <mpls@ietf.org>; Fri, 30 Jul 2010 03:22:28 -0700 (PDT)
Received: from mail pickup service by email1.etri.info with Microsoft SMTPSVC; Fri, 30 Jul 2010 19:22:47 +0900
Priority: normal
X-ReadCheckName: mpls%40ietf.org
Thread-Topic: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01
Content-Transfer-Encoding: 7bit
X-ReadCheckMessageID: <10e2c714-dd4a-46e1-a7b8-d6396974c4f5@etri.re.kr>
thread-index: Acsv0SgQEEEhwzLwQ5S4fDg6Srf+dg==
From: "Ryoo, Jeong-dong" <ryoo@etri.re.kr>
To: <liu.guoman@zte.com.cn>, "Taesik Cheung" <cts@etri.re.kr>
Date: Fri, 30 Jul 2010 19:22:47 +0900
Comment: ??, ??, 
Message-ID: <316EF0D7B3544623A6BB8FAFF544898B@etri.info>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_994B_01CB301C.97FC6830"
X-Mailer: Microsoft CDO for Exchange 2000
Content-class: urn:content-classes:message
Importance: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
X-OriginalArrivalTime: 30 Jul 2010 10:22:47.0950 (UTC) FILETIME=[28362AE0:01CB2FD1]
Cc: mpls@ietf.org, mpls-bounces@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "Ryoo, Jeong-dong" <ryoo@etri.re.kr>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jul 2010 10:22:29 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_994B_01CB301C.97FC6830
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64


------=_NextPart_000_994B_01CB301C.97FC6830
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PERJViBpZD1tc2dib2R5IHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBBcmlh
bCI+DQo8RElWPkxpdSw8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPldoYXQgeW91IGRl
c2NyaWJlZCBpbiB5b3VyIGVtYWlsIGlzIGFsaWduZWQgd2l0aCB0aGUgb3BlcmF0aW9ucyBzdGF0
ZWQgaW4gdGhlIE1QTFMtVFAgbWVzaCBwcm90ZWN0aW9uIGRyYWZ0LjwvRElWPg0KPERJVj5UaGUg
cHJvdGVjdGlvbiBsb2NraW5nIG1lc3NhZ2UgaXMgbm90IGV4YWN0bHkmbmJzcDthIHJlcGx5IG1l
c3NhZ2UsIHdoaWNoJm5ic3A7Z29lcyB0byB0aGUgb3JpZ2luYXRvciBvZiZuYnNwO3RoZSByZXF1
ZXN0IG1lc3NhZ2UuPC9ESVY+DQo8RElWPkl0IGlzIGNlcnRhaW5seSBkZXN0aW5lZCB0byBvdGhl
ciBub2Rlcywgd2hpY2gmbmJzcDtzaGFyZSB0aGUgY29tbW9uIGZhY2lsaXR5LDwvRElWPg0KPERJ
Vj5UaGlzIGlzIGFuIGFkZGl0aW9uYWwgZnVuY3Rpb24mbmJzcDtvZiBTRU4gdG8gcHJvdmlkZSB0
aGUgc2hhcmVkJm5ic3A7bWVzaCZuYnNwO3Byb3RlY3Rpb24uPC9ESVY+DQo8RElWPldoYXQgSSZu
YnNwO3dvdWxkIGxpa2UgdG8gZW1waGFzaXplJm5ic3A7aXMgdGhhdCB0aGlzIG1lc3NhZ2UgaXMg
bm90IG9yaWdpbmF0ZWQgYnkmbmJzcDthIFNFTiAoYSBNSVAgb2YgdGhlIHBhdGggZm9yIGxpbmVh
ciBwcm90ZWN0aW9uKSBpZiB0aGVyZSZuYnNwO2lzIG5vIHByb3RlY3Rpb24gc3dpdGNoaW5nIGV2
ZW50IG1lc3NhZ2UgYXJyaXZlZCBhdCB0aGUgU0VOLDwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4N
CjxESVY+QmVzdCByZWdhcmRzLDwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+SmVvbmct
ZG9uZyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxCUj48L0RJVj4NCjxESVYgc3R5bGU9IldPUkQt
QlJFQUs6IGJyZWFrLWFsbDsgRk9OVC1GQU1JTFk6ICI+DQo8RElWPg0KPERJViBzdHlsZT0iRk9O
VC1GQU1JTFk6ICI+DQo8RElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6ICI+DQo8RElWPg0K
PERJViBzdHlsZT0iRk9OVC1GQU1JTFk6ICI+DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0y
Pj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT08QlI+SmVvbmct
ZG9uZyBSeW9vLCBQaC5ELjxCUj5QcmluY2lwYWwgTWVtYmVyIG9mIFJlc2VhcmNoIFN0YWZmPEJS
Pk5ldHdvcmsgUmVzZWFyY2ggRGVwYXJ0bWVudDxCUj5FbGVjdHJvbmljcyBhbmQgVGVsZWNvbW11
bmljYXRpb25zIFJlc2VhcmNoIEluc3RpdHV0ZSAoRVRSSSkgPEJSPlBob25lOiArODItNDItODYw
LTUzODQsIEZheDogKzgyLTQyLTg2MC02MzQyPC9GT05UPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0y
PjxCUj5FbWFpbDogPC9GT05UPjxBIGhyZWY9Im1haWx0bzpyeW9vQGV0cmkucmUua3IiIHRhcmdl
dD1fYmxhbms+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+cnlvb0BldHJpLnJlLmtyPC9GT05UPjwv
QT48QlI+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PTwvRk9OVD48L0RJVj48L0RJVj48L0RJVj48L0RJVj48L0RJVj48
L0RJVj48L0RJVj48L0RJVj4NCjxESVY+PEJSPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPEJS
PjxCPkZyb206PC9CPiAibGl1Lmd1b21hbkB6dGUuY29tLmNuIiAmbHQ7bGl1Lmd1b21hbkB6dGUu
Y29tLmNuJmd0OzxCUj48Qj5Gcm9tIERhdGU6PC9CPiAyMDEwLTA3LTMwIFBNIDY6MjE6MDg8QlI+
PEI+VG86PC9CPiAiVGFlc2lrIENoZXVuZyIgJmx0O2N0c0BldHJpLnJlLmtyJmd0OzxCUj48Qj5D
Yzo8L0I+ICJtcGxzQGlldGYub3JnIiAmbHQ7bXBsc0BpZXRmLm9yZyZndDssICJtcGxzLWJvdW5j
ZXNAaWV0Zi5vcmciICZsdDttcGxzLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7LCAibXBscy10cEBpZXRm
Lm9yZyIgJmx0O21wbHMtdHBAaWV0Zi5vcmcmZ3Q7LCAicnlvb0BldHJpLnJlLmtyIiAmbHQ7cnlv
b0BldHJpLnJlLmtyJmd0OzxCUj48Qj5TdWJqZWN0OjwvQj4gUmU6IFttcGxzXSBhIHF1ZXN0aW9u
IGFib3V0IGRyYWZ0LWNoZXVuZy1tcGxzLXRwLW1lc2gtcHJvdGVjdGlvbi0wMTxCUj48QlI+PEJS
PjxGT05UIGZhY2U9c2Fucy1zZXJpZiBzaXplPTM+VGFlc2lrPC9GT05UPiA8QlI+PEZPTlQgZmFj
ZT1zYW5zLXNlcmlmIHNpemU9Mz50aGFuayB5b3UgZm9yIHJlcGx5aW5nIC5idXQgSSBkb24ndCBh
Z3JlZSB5b3VyIG9waW5pb25zPC9GT05UPiA8QlI+PEZPTlQgZmFjZT1zYW5zLXNlcmlmIHNpemU9
Mz5BY2NvcmRpbmcgdG8geW91ciBkZXNjcmlibGVzIGluIHRoZSBkcmFmdC4gPC9GT05UPjxGT05U
IGZhY2U9QXJpYWwgc2l6ZT0zPkkgdGhpbmsgdGhlIHByb3RlY3Rpb24gbG9ja2luZyBtZXNzYWdl
IGlzbid0ICZuYnNwO2EgcmVzcG9uc2UgdG8gdGhlIHByb3RlY3Rpb24gc3RhdGUgY2hhbmdlIG5v
dGlmaWNhdGlvbiBtZXNzYWdlIHNlbnQgZnJvbSBhIE1FUC48L0ZPTlQ+IDxCUj48Rk9OVCBmYWNl
PUFyaWFsIHNpemU9Mz5hbmQgaXQgaXMgYWN0aXZsZXkgZ2VuZXJhdGUgYSBMb2NraW5nIFJlcXVl
c3QgbWVzc2FnZSBmb3IgdGhlIFNFTiBub2RlLjwvRk9OVD4gPEJSPjxGT05UIGZhY2U9QXJpYWwg
c2l6ZT0zPmZvciBleGFtcGxlLiB0aGUgZm9sbG93aW5nIGZpZ3VyZSA6IDwvRk9OVD48QlI+PEZP
TlQgZmFjZT1BcmlhbCBzaXplPTM+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBB
LS0tLS0tQi0tLS0tLUMgJm5ic3A7RC0tLS0tLUUtLS0tLS1GIDwvRk9OVD48QlI+PEZPTlQgZmFj
ZT1BcmlhbCBzaXplPTM+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
XCAmbmJzcDsgTFBEMSAmbmJzcDsgLyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtcICZuYnNw
OyBMUEQzICZuYnNwOy8gPC9GT05UPjxCUj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mz4mbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgXCAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOy8gJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDtcICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
LyA8L0ZPTlQ+PEJSPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0zPiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtQLS0tLS1RLS0tLS0tLS0tLVItLS0t
LVMgPC9GT05UPjxCUj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mz4mbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgLyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFwgPC9GT05UPjxCUj48Rk9OVCBm
YWNlPUFyaWFsIHNpemU9Mz4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsvICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgTFBEMiAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7XCA8L0ZPTlQ+
PEJSPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0zPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7IC8gJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO1wgPC9GT05UPjxCUj48Rk9O
VCBmYWNlPUFyaWFsIHNpemU9Mz4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwO0ctLS0tLS0tLS0tLS0tLUgtLS0tLS0tLS0tLS0tLS1KIDwvRk9OVD48QlI+PEZPTlQgZmFj
ZT1BcmlhbCBzaXplPTM+YS4gTm9kZSBHIGRldGVjdHMgdGhlIGZhaWx1cmUsIGFuZCBpbml0aWF0
ZXMgdGhlIGxpbmVhciBwcm90ZWN0aW9uIDwvRk9OVD48QlI+PEZPTlQgZmFjZT1BcmlhbCBzaXpl
PTM+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgc3dpdGNoaW5nIGZvciB0aGUgZmFpbGVkIHdvcmtpbmcg
cGF0aCBHLUgtSjs8L0ZPTlQ+IDxCUj48QlI+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTM+Jm5ic3A7
ICZuYnNwO2IuIEF0IHRoZSBzYW1lIHRpbWUsIG5vZGUgRyBnZW5lcmF0ZXMgdGhlIHByb3RlY3Rp
b24gc3dpdGNoaW5nIGV2ZW50IDwvRk9OVD48QlI+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTM+Jm5i
c3A7ICZuYnNwOyAmbmJzcDsgbWVzc2FnZSBzYXlpbmcgdGhhdCBhIHByb3RlY3Rpb24gc3dpdGNo
aW5nIGV2ZW50IGhhcHBlbmVkIHRvIG5vZGUgPC9GT05UPjxCUj48Rk9OVCBmYWNlPUFyaWFsIHNp
emU9Mz4mbmJzcDsgJm5ic3A7ICZuYnNwOyBQIGFuZCBSLCB3aGljaCBhcmUgU0VOcyBmb3IgSi0m
Z3Q7SC0mZ3Q7Ry48L0ZPTlQ+IDxCUj48QlI+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTM+Jm5ic3A7
ICZuYnNwO2MuIFRoZSBTRU4gUCBjb21wYXJlcyB0aGUgcHJvdGVjdGlvbiBzd2l0Y2hpbmcgcHJp
b3JpdHkgb2YgTFBEMiB3aXRoIDwvRk9OVD48QlI+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTM+Jm5i
c3A7ICZuYnNwOyAmbmJzcDsgdGhhdCBvZiBMUEQxLiBJbiB0aGlzIGV4YW1wbGUsIGFzIHRoZSBw
cmlvcml0eSBvZiBMUEQxIGlzIGhpZ2hlciA8L0ZPTlQ+PEJSPjxGT05UIGZhY2U9QXJpYWwgc2l6
ZT0zPiZuYnNwOyAmbmJzcDsgJm5ic3A7IHRoYW4gTFBEMiwgU0VOIFAgZG9lcyBub3QgdGFrZSBh
biBhY3Rpb24gdG8gbm9kZSBBLjwvRk9OVD4gPEJSPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0zPiZu
YnNwOyAmbmJzcDsgJm5ic3A7IFRoZSBTRU4gUiBjb21wYXJlcyB0aGUgcHJvdGVjdGlvbiBzd2l0
Y2hpbmcgcHJpb3JpdHkgb2YgTFBEMiB3aXRoIDwvRk9OVD48QlI+PEZPTlQgZmFjZT1BcmlhbCBz
aXplPTM+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgdGhhdCBvZiBMUEQzLiBJbiB0aGlzIGV4YW1wbGUs
IGFzIHRoZSBwcmlvcml0eSBvZiBMUEQzIGlzIGxvd2VyIDwvRk9OVD48QlI+PEZPTlQgZmFjZT1B
cmlhbCBzaXplPTM+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgdGhhbiBMUEQyLCBTRU4gUiBzZW5kcyB0
aGUgcHJvdGVjdGlvbiBsb2NraW5nIG1lc3NhZ2UgcmVxdWVzdGluZyA8L0ZPTlQ+PEJSPjxGT05U
IGZhY2U9QXJpYWwgc2l6ZT0zPiZuYnNwOyAmbmJzcDsgJm5ic3A7IExvUCB0byBub2RlIEQuKDwv
Rk9OVD48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPXJlZCBzaXplPTM+aWYgdGhlIExvY2tpbmcgbWVz
c2FnZSBpcyBhIHJlc3BvbnNlIHRvIHRoZSBwcm90ZWN0aW9uIDwvRk9OVD48QlI+PEZPTlQgZmFj
ZT1BcmlhbCBjb2xvcj1yZWQgc2l6ZT0zPiZuYnNwOyAmbmJzcDsgJm5ic3A7IHN0YXRlIGNoYW5n
ZSAsIEkgdGhpbmsgdGhlIExvY2tpbmcgbWVzc2FnZSBzaG91bGQgc2VuZCB0byBOb2RlIEcgLDwv
Rk9OVD4gPEJSPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9cmVkIHNpemU9Mz4mbmJzcDsgJm5ic3A7
ICZuYnNwOyBub3Qgbm9kZSBEPC9GT05UPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0zPi4gPC9GT05U
PjxGT05UIGZhY2U9QXJpYWwgY29sb3I9cmVkIHNpemU9Mz5iZWNhdXNlIGF0IHRoZSB0aW1lIHRo
ZXJlIGlzIG5vIHByb3RlY3Rpb24gc3RhdGUgY2hhbmdlIGZvciBMUEQyIC48L0ZPTlQ+IDxCUj48
Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPXJlZCBzaXplPTM+Jm5ic3A7ICZuYnNwOyAmbmJzcDtOb2Rl
IEQgY2FuJ3Qgc2VuZCBhbnkgc3RhdGUgY2hhbmdlIHJlcXVlc3QgdG8gU0VOIG5vZGUgUiBmaXJz
dGx5LjwvRk9OVD4gPEJSPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9cmVkIHNpemU9Mz4mbmJzcDsg
Jm5ic3A7ICZuYnNwO2RvIHlvdSB0aGluayBzbz8gJm5ic3A7KTwvRk9OVD4gPEJSPjxCUj48Rk9O
VCBmYWNlPUFyaWFsIHNpemU9Mz4mbmJzcDsgJm5ic3A7ZC4gTm9kZSBEIHRha2VzIHRoZSBwcm90
ZWN0aW9uIGxvY2tpbmcgbWVzc2FnZSBhcyBhbiBpbnB1dCB0byB0aGUgPC9GT05UPjxCUj48Rk9O
VCBmYWNlPUFyaWFsIHNpemU9Mz4mbmJzcDsgJm5ic3A7ICZuYnNwOyBsaW5lYXIgcHJvdGVjdGlv
biBzd2l0Y2hpbmcsIGFuZCBmb2xsb3dzIHRoZSBsaW5lYXIgcHJvdGVjdGlvbiA8L0ZPTlQ+PEJS
PjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0zPiZuYnNwOyAmbmJzcDsgJm5ic3A7IHN3aXRjaGluZyBw
cm9jZWR1cmUgdG8gcHJvY2VzcyB0aGUgZW5kLXRvLWVuZCBMb1AgY29tbWFuZCA8L0ZPTlQ+PEJS
PjxCUj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mz4mbmJzcDttYXliZSBteSB1bmRlcnN0YW5kaW5n
IGJlIHdyb25nPzwvRk9OVD4gPEJSPjxCUj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mz4mbmJzcDsg
YmVzdCByZWdhcmRzPC9GT05UPiA8QlI+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTM+Jm5ic3A7ICZu
YnNwO2xpdSA8L0ZPTlQ+PEJSPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0zPiZuYnNwOyAmbmJzcDsg
Jm5ic3A7IDwvRk9OVD48QlI+PEZPTlQgZmFjZT1zYW5zLXNlcmlmIHNpemU9Mj48QlI+PC9ESVY+
PC9GT05UPg0KPERJVj4NCjxUQUJMRT4NCjxUQk9EWT4NCjxUUj4NCjxURD4mbmJzcDsNCjxURD4m
bmJzcDs8L1REPjwvVFI+PC9UQk9EWT48L1RBQkxFPjwvRElWPg0KPERJVj48QlI+PEJSPjxCUj48
QlI+PC9ESVY+DQo8RElWPg0KPFRBQkxFIHdpZHRoPSIxMDAlIj4NCjxUQk9EWT4NCjxUUiB2QWxp
Z249dG9wPg0KPFREIHdpZHRoPSIzNSUiPjxGT05UIGZhY2U9c2Fucy1zZXJpZiBzaXplPTE+PEI+
IlRhZXNpayBDaGV1bmciICZsdDtjdHNAZXRyaS5yZS5rciZndDs8L0I+IDwvRk9OVD48QlI+PEZP
TlQgZmFjZT1zYW5zLXNlcmlmIHNpemU9MT4/5Lu25Lq6OiAmbmJzcDttcGxzLWJvdW5jZXNAaWV0
Zi5vcmc8L0ZPTlQ+IA0KPFA+PEZPTlQgZmFjZT1zYW5zLXNlcmlmIHNpemU9MT4yMDEwLTA3LTMw
IDE2OjQ1PC9GT05UPiANCjxUQUJMRSBib3JkZXI9MT4NCjxUQk9EWT4NCjxUUiB2QWxpZ249dG9w
Pg0KPFREIGJnQ29sb3I9d2hpdGU+DQo8RElWIGFsaWduPWNlbnRlcj48Rk9OVCBmYWNlPXNhbnMt
c2VyaWYgc2l6ZT0xPj/nrZQ/ID88QlI+VGFlc2lrIENoZXVuZyAmbHQ7Y3RzQGV0cmkucmUua3Im
Z3Q7PC9GT05UPjwvRElWPjwvVEQ+PC9UUj48L1RCT0RZPjwvVEFCTEU+PEJSPjwvUD4NCjxURCB3
aWR0aD0iNjQlIj4NCjxUQUJMRSB3aWR0aD0iMTAwJSI+DQo8VEJPRFk+DQo8VFIgdkFsaWduPXRv
cD4NCjxURD4NCjxESVYgYWxpZ249cmlnaHQ+PEZPTlQgZmFjZT1zYW5zLXNlcmlmIHNpemU9MT7m
lLbku7bkuro8L0ZPTlQ+PC9ESVY+DQo8VEQ+PEZPTlQgZmFjZT1zYW5zLXNlcmlmIHNpemU9MT4m
bHQ7bGl1Lmd1b21hbkB6dGUuY29tLmNuJmd0OywgJmx0O3J5b29AZXRyaS5yZS5rciZndDs8L0ZP
TlQ+IA0KPFRSIHZBbGlnbj10b3A+DQo8VEQ+DQo8RElWIGFsaWduPXJpZ2h0PjxGT05UIGZhY2U9
c2Fucy1zZXJpZiBzaXplPTE+5oqE6YCBPC9GT05UPjwvRElWPg0KPFREPjxGT05UIGZhY2U9c2Fu
cy1zZXJpZiBzaXplPTE+bXBsc0BpZXRmLm9yZywgbXBscy10cEBpZXRmLm9yZzwvRk9OVD4gDQo8
VFIgdkFsaWduPXRvcD4NCjxURD4NCjxESVYgYWxpZ249cmlnaHQ+PEZPTlQgZmFjZT1zYW5zLXNl
cmlmIHNpemU9MT7kuLs/PC9GT05UPjwvRElWPg0KPFREPjxGT05UIGZhY2U9c2Fucy1zZXJpZiBz
aXplPTE+UmU6IFttcGxzXSBhIHF1ZXN0aW9uIGFib3V0IGRyYWZ0LWNoZXVuZy1tcGxzLXRwLW1l
c2gtcHJvdGVjdGlvbi0wMTwvRk9OVD48L1REPjwvVFI+PC9UQk9EWT48L1RBQkxFPjxCUj4NCjxU
QUJMRT4NCjxUQk9EWT4NCjxUUiB2QWxpZ249dG9wPg0KPFREPiZuYnNwOyANCjxURD4mbmJzcDs8
L1REPjwvVFI+PC9UQk9EWT48L1RBQkxFPjxCUj48L1REPjwvVFI+PC9UQk9EWT48L1RBQkxFPjwv
RElWPg0KPERJVj48QlI+PEJSPjxCUj48Rk9OVCBzaXplPTI+SGkgTGl1LDwvRk9OVD4gPEJSPjxG
T05UIHNpemU9Mj4mbmJzcDs8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+VGhhbmsgeW91IGZvciB0
aGUgY29tbWVudHMuPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPlBsZWFzZSBzZWUgaW4tbGluZS48
L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jm5ic3A7PC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPlJl
Z2FyZHMsPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPlRhZXNpazwvRk9OVD4gPEJSPjxGT05UIHNp
emU9Mj4mbmJzcDs8L0ZPTlQ+IDxCUj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48QlI+LS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS08Qj48QlI+RnJvbTo8L0I+ICJsaXUuZ3VvbWFuQHp0ZS5jb20u
Y24iICZsdDtsaXUuZ3VvbWFuQHp0ZS5jb20uY24mZ3Q7PEI+PEJSPkZyb20gRGF0ZTo8L0I+IDIw
MTAtMDctMzAgUE0gNTowNjozMDxCPjxCUj5Ubzo8L0I+ICJyeW9vQGV0cmkucmUua3IiICZsdDty
eW9vQGV0cmkucmUua3ImZ3Q7LCAiY3RzQGV0cmkucmUua3IiICZsdDtjdHNAZXRyaS5yZS5rciZn
dDs8Qj48QlI+Q2M6PC9CPiAibXBsc0BpZXRmLm9yZyIgJmx0O21wbHNAaWV0Zi5vcmcmZ3Q7LCAi
bXBscy10cEBpZXRmLm9yZyIgJmx0O21wbHMtdHBAaWV0Zi5vcmcmZ3Q7PEI+PEJSPlN1YmplY3Q6
PC9CPiBhIHF1ZXN0aW9uIGFib3V0IGRyYWZ0LWNoZXVuZy1tcGxzLXRwLW1lc2gtcHJvdGVjdGlv
bi0wMTxCUj48QlI+PC9GT05UPjxGT05UIGZhY2U9c2Fucy1zZXJpZiBzaXplPTM+PEJSPmhpLDwv
Rk9OVD48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj4gPC9GT05UPjxGT05UIGZhY2U9c2Fucy1zZXJp
ZiBzaXplPTM+PEJSPnRvZGF5IEkgcmV2aWV3ZWQgeW91ciB0aGlzIGRyYWZ0LCBJIGhhdmUgYSBm
ZXcgcXVlc3Rpb25zIGZvciBtZXNoIHByb3RlY3Rpb24gPEJSPjEgaW4gc2VjdGlvbiAzLCBJbiBt
eSBtaW5kLCB0aGVyZSBpcyBhIHNlbnRlbmNlIDogPC9GT05UPjxGT05UIGZhY2U9c2Fucy1zZXJp
ZiBjb2xvcj1yZWQgc2l6ZT0zPkluIGJvdGggY2FzZXMsIDE6MSBvciAxKzEgcHJvdGVjdGlvbiBt
YXkgYmUgdXNlZC4gPEJSPiZuYnNwOzwvRk9OVD48Rk9OVCBmYWNlPXNhbnMtc2VyaWYgc2l6ZT0z
PiBpZiB0aGVyZSB1c2UgMSsxIHByb3RlY3Rpb24gZm9yIGVhY2ggd29ya2luZyBwYXRoLiBpdCBp
cyBubyBuZWNlc3NhcnkgdG8gYXBwbHkgbWVzaCBwcm90ZWN0aW9uLjwvRk9OVD48Rk9OVCBmYWNl
PUFyaWFsIHNpemU9Mj4gPC9GT05UPjxGT05UIGZhY2U9c2Fucy1zZXJpZiBzaXplPTM+PEJSPiZu
YnNwOyBiZWFjYXVzZSB0aGUgYmFuZHdpZHRoIHJlc291cmNlIG9mIHByb3RlY3Rpb24gaXMgZXF1
YWwgdG8gdGhlIHN1bSBvZiBiYW5kd2lkdGggcmVzb3VyY2Ugb2YgYWxsIDxCUj4mbmJzcDsgcHJv
dGVjdGVkIHBhdGguIHNvIEkgdGhpbmsgMSsxIHByb3RlY3Rpb24gc2hvdWxkIG5vdCBiZSB1c2Vk
IGluIHRoZSBtZXNoIHByb3RlY3Rpb24uPC9GT05UPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPiA8
L0ZPTlQ+PEZPTlQgZmFjZT1zYW5zLXNlcmlmIHNpemU9Mz48QlI+Jm5ic3A7IGRvIHlvdSB0aGlu
ayBzbz88L0ZPTlQ+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+IDwvRk9OVD48QlI+PEZPTlQgZmFj
ZT1BcmlhbCBzaXplPTM+W1RhZXNpa10gWWVzLCBpZiAxKzEgcHJvdGVjdGlvbiBpcyB1c2VkLCBz
aGFyZWQgbWVzaCBwcm90ZWN0aW9uIGlzIG5vdCBuZWNlc3NhcnkuIFRoZSBzZW50ZW5jZSBpcyBq
dXN0IGdlbmVyaWMgb25lLiBSaWdodCBhZnRlciB0aGUgc2VudGVuY2UsIHdlIGRlc2NyaWJlZCB0
aGF0IGlmIDE6MSBwcm90ZWN0aW9uIGlzIHVzZWQsIHRoZSBzZWdtZW50IFBRUiBjYW4gYmUgc2hh
cmVkIGJ5IHR3byBwcm90ZWN0aW9uIHBhdGhzLjwvRk9OVD4gPEJSPjxGT05UIGZhY2U9c2Fucy1z
ZXJpZiBzaXplPTM+PEJSPjIgYWJvdXQgdGhlIFNoYXJlZCBub2RlIFNFTiB3aWxsIHNlbmQgdGhl
IHByb3RlY3Rpb24gbG9ja2luZyBtZXNzYWdlIHJlcXVlc3RpbmcgPEJSPiZuYnNwOyAmbmJzcDsg
Jm5ic3A7TG9QIHRvIHRoZSBlbmQgbm9kZSBvZiBwcm90ZWN0ZWQgTFNQLiBJTU8sIGFzIFNFTiBu
b2RlIGlzIE1JUCBvZiB0aGUgcHJvdGVjdGVkIDxCUj4mbmJzcDsgJm5ic3A7ICZuYnNwO0xTUCAs
IGl0IGNhbid0IGdlbmVyYXRlIHVuc29saWNpdCBPQU0gcGFja2V0IHRvIHNlbmQgb3RoZXIgbm9k
ZS4gc28gaG93IHRvIGdlbmVyYXRlPC9GT05UPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPiA8L0ZP
TlQ+PEZPTlQgZmFjZT1zYW5zLXNlcmlmIHNpemU9Mz48QlI+Jm5ic3A7ICZuYnNwO3RoZSBwcm90
ZWN0aW9uIGxvY2tpbmcgbWVzc2FnZSByZXF1ZXN0aW5nIExPUCBpbiB0aGUgU0VOIG5vZGUgPzwv
Rk9OVD48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj4gPC9GT05UPjxCUj48Rk9OVCBmYWNlPUFyaWFs
IHNpemU9Mz5bVGFlc2lrXSBUaGUgcHJvdGVjdGlvbiBsb2NraW5nIG1lc3NhZ2UgaXMgYSByZXNw
b25zZSB0byB0aGUgcHJvdGVjdGlvbiBzdGF0ZSBjaGFuZ2Ugbm90aWZpY2F0aW9uIG1lc3NhZ2Ug
c2VudCBmcm9tIGEgTUVQLiBJdCBpcyBzaW1pbGFyIHRvIExUTS9MVFIgb3IgTG9jayBJbnRydWN0
IC8gTG9jayBSZXBvcnQgcmVsYXRpb25zaGlwLjwvRk9OVD4gPEJSPjxGT05UIGZhY2U9QXJpYWwg
c2l6ZT0yPiZuYnNwOzwvRk9OVD4gPEJSPjxGT05UIGZhY2U9c2Fucy1zZXJpZiBzaXplPTM+PEJS
PiZuYnNwO01heWJlIGkgbWlzcyBzb21ldGhpbmcgaW1wb3J0YW50PzwvRk9OVD48Rk9OVCBmYWNl
PUFyaWFsIHNpemU9Mj4gPC9GT05UPjxGT05UIGZhY2U9c2Fucy1zZXJpZiBzaXplPTM+PEJSPiZu
YnNwO3RoYW5rIHlvdTwvRk9OVD48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj4gPEJSPjwvRk9OVD48
Rk9OVCBmYWNlPXNhbnMtc2VyaWYgc2l6ZT0zPjxCUj4mbmJzcDtiZXN0IHJlZ2FyZHM8L0ZPTlQ+
PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+IDwvRk9OVD48Rk9OVCBmYWNlPXNhbnMtc2VyaWYgc2l6
ZT0zPjxCUj4mbmJzcDtsaXU8L0ZPTlQ+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+IDxCUj48L0ZP
TlQ+PEZPTlQgZmFjZT1zYW5zLXNlcmlmIGNvbG9yPXJlZCBzaXplPTM+PEJSPiZuYnNwOyAmbmJz
cDs8QlI+Jm5ic3A7ICZuYnNwOzwvRk9OVD4gPC9ESVY+DQo8RElWPg0KPFRBQkxFIHdpZHRoPSIx
MDAlIj4NCjxUQk9EWT4NCjxUUj4NCjxURCB3aWR0aD0iNjMlIj48Rk9OVCBzaXplPTM+Jm5ic3A7
IDwvRk9OVD4NCjxURCB3aWR0aD0iMzYlIj48Rk9OVCBzaXplPTM+Jm5ic3A7PC9GT05UPjwvVEQ+
PC9UUj48L1RCT0RZPjwvVEFCTEU+PC9ESVY+DQo8RElWPjxCUj48Rk9OVCBmYWNlPUFyaWFsIHNp
emU9Mj48QlI+PC9GT05UPjxCUj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj4tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxCUj5aVEUgSW5mb3Jt
YXRpb24gU2VjdXJpdHkgTm90aWNlOiBUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMg
bWFpbCBpcyBzb2xlbHkgcHJvcGVydHkgb2YgdGhlIHNlbmRlcidzIG9yZ2FuaXphdGlvbi4gVGhp
cyBtYWlsIGNvbW11bmljYXRpb24gaXMgY29uZmlkZW50aWFsLiBSZWNpcGllbnRzIG5hbWVkIGFi
b3ZlIGFyZSBvYmxpZ2F0ZWQgdG8gbWFpbnRhaW4gc2VjcmVjeSBhbmQgYXJlIG5vdCBwZXJtaXR0
ZWQgdG8gZGlzY2xvc2UgdGhlIGNvbnRlbnRzIG9mIHRoaXMgY29tbXVuaWNhdGlvbiB0byBvdGhl
cnMuPEJSPlRoaXMgZW1haWwgYW5kIGFueSBmaWxlcyB0cmFuc21pdHRlZCB3aXRoIGl0IGFyZSBj
b25maWRlbnRpYWwgYW5kIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZp
ZHVhbCBvciBlbnRpdHkgdG8gd2hvbSB0aGV5IGFyZSBhZGRyZXNzZWQuIElmIHlvdSBoYXZlIHJl
Y2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3IgcGxlYXNlIG5vdGlmeSB0aGUgb3JpZ2luYXRvciBv
ZiB0aGUgbWVzc2FnZS4gQW55IHZpZXdzIGV4cHJlc3NlZCBpbiB0aGlzIG1lc3NhZ2UgYXJlIHRo
b3NlIG9mIHRoZSBpbmRpdmlkdWFsIHNlbmRlci48QlI+VGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNj
YW5uZWQgZm9yIHZpcnVzZXMgYW5kIFNwYW0gYnkgWlRFIEFudGktU3BhbSBzeXN0ZW0uPEJSPjwv
Rk9OVD48Rk9OVCBzaXplPTI+PFRUPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fPEJSPm1wbHMgbWFpbGluZyBsaXN0PEJSPm1wbHNAaWV0Zi5vcmc8QlI+aHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzPEJSPjwvVFQ+PC9GT05UPjxC
Uj48QlI+PC9ESVY+PFBSRT4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KWlRFJm5ic3A7SW5mb3JtYXRpb24mbmJzcDtTZWN1cml0eSZuYnNw
O05vdGljZTombmJzcDtUaGUmbmJzcDtpbmZvcm1hdGlvbiZuYnNwO2NvbnRhaW5lZCZuYnNwO2lu
Jm5ic3A7dGhpcyZuYnNwO21haWwmbmJzcDtpcyZuYnNwO3NvbGVseSZuYnNwO3Byb3BlcnR5Jm5i
c3A7b2YmbmJzcDt0aGUmbmJzcDtzZW5kZXIncyZuYnNwO29yZ2FuaXphdGlvbi4mbmJzcDtUaGlz
Jm5ic3A7bWFpbCZuYnNwO2NvbW11bmljYXRpb24mbmJzcDtpcyZuYnNwO2NvbmZpZGVudGlhbC4m
bmJzcDtSZWNpcGllbnRzJm5ic3A7bmFtZWQmbmJzcDthYm92ZSZuYnNwO2FyZSZuYnNwO29ibGln
YXRlZCZuYnNwO3RvJm5ic3A7bWFpbnRhaW4mbmJzcDtzZWNyZWN5Jm5ic3A7YW5kJm5ic3A7YXJl
Jm5ic3A7bm90Jm5ic3A7cGVybWl0dGVkJm5ic3A7dG8mbmJzcDtkaXNjbG9zZSZuYnNwO3RoZSZu
YnNwO2NvbnRlbnRzJm5ic3A7b2YmbmJzcDt0aGlzJm5ic3A7Y29tbXVuaWNhdGlvbiZuYnNwO3Rv
Jm5ic3A7b3RoZXJzLg0KVGhpcyZuYnNwO2VtYWlsJm5ic3A7YW5kJm5ic3A7YW55Jm5ic3A7Zmls
ZXMmbmJzcDt0cmFuc21pdHRlZCZuYnNwO3dpdGgmbmJzcDtpdCZuYnNwO2FyZSZuYnNwO2NvbmZp
ZGVudGlhbCZuYnNwO2FuZCZuYnNwO2ludGVuZGVkJm5ic3A7c29sZWx5Jm5ic3A7Zm9yJm5ic3A7
dGhlJm5ic3A7dXNlJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtpbmRpdmlkdWFsJm5ic3A7b3ImbmJz
cDtlbnRpdHkmbmJzcDt0byZuYnNwO3dob20mbmJzcDt0aGV5Jm5ic3A7YXJlJm5ic3A7YWRkcmVz
c2VkLiZuYnNwO0lmJm5ic3A7eW91Jm5ic3A7aGF2ZSZuYnNwO3JlY2VpdmVkJm5ic3A7dGhpcyZu
YnNwO2VtYWlsJm5ic3A7aW4mbmJzcDtlcnJvciZuYnNwO3BsZWFzZSZuYnNwO25vdGlmeSZuYnNw
O3RoZSZuYnNwO29yaWdpbmF0b3ImbmJzcDtvZiZuYnNwO3RoZSZuYnNwO21lc3NhZ2UuJm5ic3A7
QW55Jm5ic3A7dmlld3MmbmJzcDtleHByZXNzZWQmbmJzcDtpbiZuYnNwO3RoaXMmbmJzcDttZXNz
YWdlJm5ic3A7YXJlJm5ic3A7dGhvc2UmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO2luZGl2aWR1YWwm
bmJzcDtzZW5kZXIuDQpUaGlzJm5ic3A7bWVzc2FnZSZuYnNwO2hhcyZuYnNwO2JlZW4mbmJzcDtz
Y2FubmVkJm5ic3A7Zm9yJm5ic3A7dmlydXNlcyZuYnNwO2FuZCZuYnNwO1NwYW0mbmJzcDtieSZu
YnNwO1pURSZuYnNwO0FudGktU3BhbSZuYnNwO3N5c3RlbS4NCjwvUFJFPjwvRElWPjxpbWcgc3R5
bGU9ImRpc3BsYXk6bm9uZSIgd2lkdGg9MCBoZWlnaHQ9MCBzcmM9Imh0dHA6Ly91bWFpbC5ldHJp
LnJlLmtyL0V4dGVybmFsX1JlYWRDaGVjay5hc3B4P2VtYWlsPW1wbHNAaWV0Zi5vcmcmbmFtZT1t
cGxzJTQwaWV0Zi5vcmcmZnJvbWVtYWlsPXJ5b29AZXRyaS5yZS5rciZtZXNzYWdlaWQ9JTNDMTBl
MmM3MTQtZGQ0YS00NmUxLWE3YjgtZDYzOTY5NzRjNGY1QGV0cmkucmUua3IlM0UiPg==

------=_NextPart_000_994B_01CB301C.97FC6830--

From curtis@occnc.com  Fri Jul 30 05:02:25 2010
Return-Path: <curtis@occnc.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E4E03A67E6; Fri, 30 Jul 2010 05:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level: 
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599]
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 c64yARrvSEbh; Fri, 30 Jul 2010 05:02:23 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id A9E2D3A68E6; Fri, 30 Jul 2010 05:02:22 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o6UC2DP6039265; Fri, 30 Jul 2010 08:02:13 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201007301202.o6UC2DP6039265@harbor.orleans.occnc.com>
To: Shane Amante <shane@castlepoint.net>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Fri, 30 Jul 2010 11:34:45 +0200." <0DEFA7EF-8DC4-4EF2-ABDF-0404FC32B992@castlepoint.net> 
Date: Fri, 30 Jul 2010 08:02:13 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [PWE3]  ELI as a reserved label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jul 2010 12:02:25 -0000

In message <0DEFA7EF-8DC4-4EF2-ABDF-0404FC32B992@castlepoint.net>
Shane Amante writes:
>  
> Curtis,
>  
> On Jul 30, 2010, at 11:06 GMT+02:00, Curtis Villamizar wrote:
> > The Entropy Label Indicator (ELI) is called for in
> > draft-kompella-mpls-entropy-label-01.txt
> > 
> > After brief discussion with Stewart and with Kireeti and Lucy Yong,
> > there were three uses of ELI that would benefit from making the ELI a
> > reserved label.  It may be premature to make any such request and the
> > remaining reserved label number space is sparse, so this will be
> > floated as a separate draft, and put on hold awaiting advancement of
> > the drafts that depend on it.
> > 
> > The three benefits of making ELI a reserved label are in:
> > 
> >  1.  Extending any use of entropy-label to P2MP (where there are
> >      multiple egress and the possibility of each egress requiring a
> >      separate entropy label value is problematic for the ingress).
> > 
> >  2.  Extending any use of entropy-label to any arbitrary position in
> >      the label stack such that in an aggregation LSP with aggregates
> >      both MPLS-TP and MPLS LSP, load split on the MPLS LSPs is
> >      simplified and not impacted by limiting label stack depth for
> >      the MPLS-TP LSPs.  This is when label stack hash is limited to
> >      support MPLS-TP as proposed in
> >      draft-villamizar-mpls-tp-multipath-00.txt .
>  
> I agree there are benefits to a reserved label for the above two
> applications.  Most importantly, a receiving node would have pretty
> clearly semantics that what [immediately] follows a reserved ELI is
> the entropy-label, regardless of where the ELI is in the MPLS label
> stack and without needing to be in the signaling path to know what is
> the ELI value.

"Now don't be sad ... 'cause two out of three aint bad".  [meatloaf]

Its good to hear that you consider these to be useful.

Note that an ingress LSR still needs to determine that egress LSR
understands ELI to do anything.  To support MPLS-TP in MPLS the
ingress needs to veryify that all LSR on the path support MPLS in a
way that provides a compliant path for a contained TP LSP, but that is
out of scope of this discussion.


> >  3.  Providing a means to carry indication of large flow as described
> >      in draft-yong-pwe3-enhance-ecmp-lfat-01.txt and
> >      draft-yong-pwe3-lfc-fat-pw-01.txt without changing the use of TC
> >      in a forwarding LSP label.
>  
> I'm unclear how a single, reserved label would be a means of signaling
> a large vs. small flow.  How can a single label represent two states
> (large vs. small flow)?

That's the slightly ugly part.  If ELI carries a TTL=0 then it can't
be used to forward and among those that discussed this (in one of the
"hallway sessions" near the registration desk) it was not seen as too
horribly ugly if TC meaned something else in the ELI label stack entry
only.

Lucy has a different way to do multipath and this is an enabler.  If
your LSRs don't use it, then it does no harm as long as the hashed
entropy value is there too.


> Thanks,
>  
> -shane

Thanks for the input on this.

Curtis


> > This would reuse one reserved label for three purposes.
> > 
> > This email is to gauge the reaction to this proposal (preferably among
> > those familiar with these drafts) before taking the time to write a
> > new draft proposing that a reserved label be allocated.
> > 
> > Curtis
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
>  
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3


From shane@castlepoint.net  Fri Jul 30 08:31:14 2010
Return-Path: <shane@castlepoint.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C2393A69FF; Fri, 30 Jul 2010 08:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gr-4uEqFgtZh; Fri, 30 Jul 2010 08:31:11 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 3283C3A68B1; Fri, 30 Jul 2010 08:31:11 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 6F13336817D; Fri, 30 Jul 2010 09:31:35 -0600 (MDT)
Received: from host2.tcb.net (64.78.235.218 [64.78.235.218]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Fri, 30 Jul 2010 09:31:33 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.235.218; client-port=56562; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <201007301202.o6UC2DP6039265@harbor.orleans.occnc.com>
Date: Fri, 30 Jul 2010 17:31:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F8F5330-91F8-456F-BFDC-FF5735CFDD9E@castlepoint.net>
References: <201007301202.o6UC2DP6039265@harbor.orleans.occnc.com>
To: curtis@occnc.com
X-Mailer: Apple Mail (2.1081)
Cc: mpls@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [PWE3]  ELI as a reserved label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jul 2010 15:31:14 -0000

Curtis,

On Jul 30, 2010, at 14:02 GMT+02:00, Curtis Villamizar wrote:
> In message <0DEFA7EF-8DC4-4EF2-ABDF-0404FC32B992@castlepoint.net>
> Shane Amante writes:
>> On Jul 30, 2010, at 11:06 GMT+02:00, Curtis Villamizar wrote:

[--snip--]

>>> 3.  Providing a means to carry indication of large flow as described
>>>     in draft-yong-pwe3-enhance-ecmp-lfat-01.txt and
>>>     draft-yong-pwe3-lfc-fat-pw-01.txt without changing the use of TC
>>>     in a forwarding LSP label.
>>=20
>> I'm unclear how a single, reserved label would be a means of =
signaling
>> a large vs. small flow.  How can a single label represent two states
>> (large vs. small flow)?
>=20
> That's the slightly ugly part.  If ELI carries a TTL=3D0 then it can't
> be used to forward and among those that discussed this (in one of the
> "hallway sessions" near the registration desk) it was not seen as too
> horribly ugly if TC meaned something else in the ELI label stack entry
> only.
>=20
> Lucy has a different way to do multipath and this is an enabler.  If
> your LSRs don't use it, then it does no harm as long as the hashed
> entropy value is there too.

Understood.

I would note that in draft-kompella-mpls-entropy-label-01 it is NOT =
envisioned that there will be a "standalone ELI" in all cases.  =
Specifically, in the case where application labels are in use, (e.g.: =
2547 VPN's, 6PE, etc.), the application label itself is intended to =
serve the purpose of an ELI, indicating that the label that immediately =
follows the application label is an entropy-label, i.e.:

+----------------+
|  Tunnel Label  |
+----------------+
|   App. Label   |
+----------------+
| Entropy Label  |
+----------------+

In these cases, there wouldn't be a reserved label used for a ELI in the =
label stack.  Thus, I'm not sure you can count on the LFC-bit *only* =
being set in entropy-labels that are immediately preceded by a reserved =
ELI label.

So, with respect to LFC, IMO it's:
a)  orthogonal to the discussion of whether or not a reserved label for =
the ELI is absolutely _required_ or just nice-to-have; and,
b)  the MPLS WG needs to weigh in with a definitive answer on whether =
changing the semantics of the MPLS TC is appropriate to accommodate =
end-users who desire LFC.

-shane=

From shane@castlepoint.net  Sat Jul 31 19:38:08 2010
Return-Path: <shane@castlepoint.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A9A63A67F7; Sat, 31 Jul 2010 19:38:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
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 Zk4-Knp3tjhl; Sat, 31 Jul 2010 19:38:07 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 3214A3A67F8; Sat, 31 Jul 2010 19:38:06 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 23CC72684EA; Sat, 31 Jul 2010 20:38:33 -0600 (MDT)
Received: from mbpw.castlepoint.net (174-29-218-177.hlrn.qwest.net [174.29.218.177]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Sat, 31 Jul 2010 20:38:32 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=174.29.218.177; client-port=54448; syn-fingerprint=65535:56:1:64:M1452,N,W3,N,N,T,S; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <201007301202.o6UC2DP6039265@harbor.orleans.occnc.com>
Date: Sun, 1 Aug 2010 04:38:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B7721F4-8C12-4C88-9036-B19592BE686E@castlepoint.net>
References: <201007301202.o6UC2DP6039265@harbor.orleans.occnc.com>
To: curtis@occnc.com
X-Mailer: Apple Mail (2.1081)
Cc: mpls@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [PWE3]  ELI as a reserved label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Aug 2010 02:38:08 -0000

Hi Curtis,

I had some time to think about this some more on the plane ride home.  =
See below.

On Jul 30, 2010, at 14:02 GMT+02:00, Curtis Villamizar wrote:
> In message <0DEFA7EF-8DC4-4EF2-ABDF-0404FC32B992@castlepoint.net>
> Shane Amante writes:
>>=20
>> Curtis,
>>=20
>> On Jul 30, 2010, at 11:06 GMT+02:00, Curtis Villamizar wrote:
>>> The Entropy Label Indicator (ELI) is called for in
>>> draft-kompella-mpls-entropy-label-01.txt
>>>=20
>>> After brief discussion with Stewart and with Kireeti and Lucy Yong,
>>> there were three uses of ELI that would benefit from making the ELI =
a
>>> reserved label.  It may be premature to make any such request and =
the
>>> remaining reserved label number space is sparse, so this will be
>>> floated as a separate draft, and put on hold awaiting advancement of
>>> the drafts that depend on it.
>>>=20
>>> The three benefits of making ELI a reserved label are in:
>>>=20
>>> 1.  Extending any use of entropy-label to P2MP (where there are
>>>     multiple egress and the possibility of each egress requiring a
>>>     separate entropy label value is problematic for the ingress).
>>>=20
>>> 2.  Extending any use of entropy-label to any arbitrary position in
>>>     the label stack such that in an aggregation LSP with aggregates
>>>     both MPLS-TP and MPLS LSP, load split on the MPLS LSPs is
>>>     simplified and not impacted by limiting label stack depth for
>>>     the MPLS-TP LSPs.  This is when label stack hash is limited to
>>>     support MPLS-TP as proposed in
>>>     draft-villamizar-mpls-tp-multipath-00.txt .
>>=20
>> I agree there are benefits to a reserved label for the above two
>> applications.  Most importantly, a receiving node would have pretty
>> clearly semantics that what [immediately] follows a reserved ELI is
>> the entropy-label, regardless of where the ELI is in the MPLS label
>> stack and without needing to be in the signaling path to know what is
>> the ELI value.
>=20
> "Now don't be sad ... 'cause two out of three aint bad".  [meatloaf]
>=20
> Its good to hear that you consider these to be useful.
>=20
> Note that an ingress LSR still needs to determine that egress LSR
> understands ELI to do anything.  To support MPLS-TP in MPLS the
> ingress needs to veryify that all LSR on the path support MPLS in a
> way that provides a compliant path for a contained TP LSP, but that is
> out of scope of this discussion.

I need to revise my statements wrt entropy-labels and P2MP LSP's.  After =
thinking about this some more, I no longer believe it makes sense to use =
a reserved ELI value for P2MP LSP's.  More specifically, for a given =
P2MP LSP, all receivers /MUST/ agree to receive entropy labels, because =
it would be silly to (for example) expect core LSR's to strip-off the =
ELI and an entropy-label mid-flight toward receivers that don't =
understand (or, can't receive) entropy-labels.  The ramifications of =
this are that if a head-end detects any receivers of a P2MP LSP that =
can't receive entropy-labels, then the head-end LER/LSR must either: a) =
re-signal the whole P2MP LSP toward all receivers so that the head-end =
will not send any entropy-labels at all on the P2MP LSP; or, b) signal 2 =
separate P2MP LSP's: one for entropy-label capable receivers and a =
second for non-entropy-label capable receivers.  I don't know that we =
want to mandate one of those two behaviors over the other, because SP's =
may make separate choices depending on whether they want to avoid extra =
replication in the network at the expense of not being able to do =
flow-based load-balancing, i.e.: Option (a), or don't mind the extra =
replication of (potentially) 2 parallel P2MP trees on the same links in =
order to attain some amount of flow-based load-balancing of the P2MP =
traffic.

So, in summary, I no longer see that draft-kompella-mpls-entropy-label =
has a requirement for reserved labels for either P2P or P2MP LSP's =
(scenario 1 in your original e-mail).  Furthermore, I still maintain =
that discussion of LFC and use of the MPLS TC field for indication of =
large vs. small flows is orthogonal to draft-kompella-mpls-entropy-label =
(scenario 3 in your original e-mail).  I haven't read =
draft-villamizar-mpls-tp-multipath-00 (scenario 2 in your original =
e-mail) so I can't speak to whether or not there is a requirement for a =
reserved label there.

Anyway, perhaps this will save you some time in that you don't need to =
write a whole new draft as you originally proposed and, instead, may =
only need to look at modifying your original draft.  :-)

On a separate note, we intend to update =
draft-kompella-mpls-entropy-label shortly to cover P2MP LSP's (RSVP & =
mLDP), plus add details surrounding labelled BGP and RSVP P2P LSP's so =
that we have a more thorough treatment of all use cases to hopefully =
make all of this more clear.  (In fact, I got a good start on this text =
on this on the plane ride home :-).

-shane=
