
From bao.yuanlin@zte.com.cn  Tue Mar  1 00:08:34 2011
Return-Path: <bao.yuanlin@zte.com.cn>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CAEE3A6A97; Tue,  1 Mar 2011 00:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.993
X-Spam-Level: 
X-Spam-Status: No, score=-96.993 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 7rnjMEMnIRF6; Tue,  1 Mar 2011 00:08:33 -0800 (PST)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 93AE43A6A43; Tue,  1 Mar 2011 00:08:32 -0800 (PST)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35103491178658; Tue, 1 Mar 2011 16:07:19 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.15] with StormMail ESMTP id 84746.5982734957; Tue, 1 Mar 2011 16:07:01 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p2186tYg014211; Tue, 1 Mar 2011 16:06:55 +0800 (GMT-8) (envelope-from Bao.Yuanlin@zte.com.cn)
In-Reply-To: <4D6C1773.70406@cisco.com>
To: Andrew Malis <andrew.g.malis@verizon.com>, "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>, "pwe3@ietf.org" <pwe3@ietf.org>, pwe3-bounces@ietf.org
MIME-Version: 1.0
X-KeepSent: C6CCDF89:4B730A33-48257846:002C63E5; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFC6CCDF89.4B730A33-ON48257846.002C63E5-48257846.002C9649@zte.com.cn>
From: Bao.Yuanlin@zte.com.cn
Date: Tue, 1 Mar 2011 16:06:57 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-03-01 16:06:57, Serialize complete at 2011-03-01 16:06:57
Content-Type: multipart/alternative; boundary="=_alternative 002C964648257846_="
X-MAIL: mse02.zte.com.cn p2186tYg014211
Subject: [PWE3] =?gb2312?b?tPC4tDogUmU6ICBXRyBQb2xsIG9uIGRyYWZ0LWppbi1w?= =?gb2312?b?d2UzLWNiaXQtbmVnb3RpYXRpb24tMDMudHh0ICggY29tbWVudCAp?=
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 08:08:34 -0000

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

Support.

 
On 02/16/11 05:46, Bocci, Matthew (Matthew) wrote:

> WG,
>
> The authors of draft-jin-pwe3-cbit-negotiation-03 have asked that the
> WG adopt this as a PWE3 working group draft.
>
> This email begins a two week poll to help us judge if there is
> consensus to move forward with the draft.
>
> Please post any comments to the PWE3 list by Wednesday 2nd March.
>
> Regards,
>
> Matthew & Andy
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3



--=_alternative 002C964648257846_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>Support.</font></tt>
<br><tt><font size=2><br>
 <br>
On 02/16/11 05:46, Bocci, Matthew (Matthew) wrote:</font></tt>
<br><tt><font size=2><br>
&gt; WG,<br>
&gt;<br>
&gt; The authors of draft-jin-pwe3-cbit-negotiation-03 have asked that
the<br>
&gt; WG adopt this as a PWE3 working group draft.<br>
&gt;<br>
&gt; This email begins a two week poll to help us judge if there is<br>
&gt; consensus to move forward with the draft.<br>
&gt;<br>
&gt; Please post any comments to the PWE3 list by Wednesday 2nd March.<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Matthew &amp; Andy<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; pwe3 mailing list<br>
&gt; pwe3@ietf.org<br>
&gt; https://www.ietf.org/mailman/listinfo/pwe3<br>
<br>
<br>
</font></tt>
--=_alternative 002C964648257846_=--


From liuzh_gz@qq.com  Tue Mar  1 04:29:15 2011
Return-Path: <liuzh_gz@qq.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DB1D3A67AD for <pwe3@core3.amsl.com>; Tue,  1 Mar 2011 04:29:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.839
X-Spam-Level: 
X-Spam-Status: No, score=0.839 tagged_above=-999 required=5 tests=[AWL=1.684,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753]
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 EyxefJUrp7Fw for <pwe3@core3.amsl.com>; Tue,  1 Mar 2011 04:29:13 -0800 (PST)
Received: from smtpbg52.qq.com (smtpbg52.qq.com [64.71.138.43]) by core3.amsl.com (Postfix) with SMTP id 4D3943A67E2 for <pwe3@ietf.org>; Tue,  1 Mar 2011 04:29:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qq.com; s=s0907; t=1298982564; bh=lg+WCjd1uoounUvNtM6gZlbk0rpvBJ180bzriK+hPM4=; h=X-QQ-mid:Received:X-QQ-SSF:Date:From:To:Cc:References:Subject: Message-ID:X-mailer:Mime-Version:Content-Type; b=cecxuMq9FcVC5qnn9ILqAiM8mnxQt3RabZFvhP9VvYeCG16A9gxVoqE3UsShapJmN enokjR9qVIEuiuN2vOYw08p5qi+DkkqLshiuD2WDUbWhLTc/kHp0KmDXLHBCOiu
X-QQ-mid: esmtp3t1298982561t987t26477
Received: from GSTA-DATA (unknown [119.57.3.82]) by esmtp10.qq.com (ESMTP) with  id ; Tue, 01 Mar 2011 20:29:20 +0800 (CST)
X-QQ-SSF: 0000000000000010213100000000000
Date: Tue, 1 Mar 2011 20:29:19 +0800
From: "liuzh_gz" <liuzh_gz@qq.com>
To: "pwe3" <pwe3@ietf.org>
References: <201102282353546407066@qq.com>, <201103011310486870424@qq.com>
Message-ID: <201103012029177500386@qq.com>
X-mailer: Foxmail 6, 15, 201, 23 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon824572225828_====="
Cc: "andrew.g.malis" <andrew.g.malis@verizon.com>
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 12:29:15 -0000

This is a multi-part message in MIME format.

--=====003_Dragon824572225828_=====
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit

Support


Zhihua Liu  




From: matthew.bocci@alcatel-lucent.com
To: pwe3@ietf.org
Date: Wed, 16 Feb 2011 13:46:19 +0100
Subject: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt
WG,
The authors of draft-jin-pwe3-cbit-negotiation-03 have asked that the WG adopt this as a PWE3 working group draft.
This email begins a two week poll to help us judge if there is consensus to move forward with the draft.
Please post any comments to the PWE3 list by Wednesday 2nd March.
Regards,
Matthew & Andy
_______________________________________________ pwe3 mailing list pwe3@ietf.org https://www.ietf.org/mailman/listinfo/pwe3

2011-03-1

--=====003_Dragon824572225828_=====
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PUdCMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC42MDAwLjE3MDk1IiBuYW1lPUdFTkVSQVRPUj48TElOSyANCmhyZWY9IkJMT0NLUVVPVEV7bWFy
Z2luLVRvcDogMHB4OyBtYXJnaW4tQm90dG9tOiAwcHg7IG1hcmdpbi1MZWZ0OiAyZW19IiANCnJl
bD1zdHlsZXNoZWV0Pg0KPE1FVEEgY29udGVudD0iTVNIVE1MIDguMDAuNjAwMS4xODgxMiIgbmFt
ZT1HRU5FUkFUT1I+DQo8U1RZTEU+QGZvbnQtZmFjZSB7DQoJZm9udC1mYW1pbHk6IMvOzOU7DQp9
DQpAZm9udC1mYWNlIHsNCglmb250LWZhbWlseTogVmVyZGFuYTsNCn0NCkBmb250LWZhY2Ugew0K
CWZvbnQtZmFtaWx5OiBAy87M5TsNCn0NCkBwYWdlIFNlY3Rpb24xIHtzaXplOiA1OTUuM3B0IDg0
MS45cHQ7IG1hcmdpbjogNzIuMHB0IDkwLjBwdCA3Mi4wcHQgOTAuMHB0OyBsYXlvdXQtZ3JpZDog
MTUuNnB0OyB9DQpQLk1zb05vcm1hbCB7DQoJVEVYVC1KVVNUSUZZOiBpbnRlci1pZGVvZ3JhcGg7
IEZPTlQtU0laRTogMTAuNXB0OyBNQVJHSU46IDBjbSAwY20gMHB0OyBGT05ULUZBTUlMWTogIlRp
bWVzIE5ldyBSb21hbiI7IFRFWFQtQUxJR046IGp1c3RpZnkNCn0NCkxJLk1zb05vcm1hbCB7DQoJ
VEVYVC1KVVNUSUZZOiBpbnRlci1pZGVvZ3JhcGg7IEZPTlQtU0laRTogMTAuNXB0OyBNQVJHSU46
IDBjbSAwY20gMHB0OyBGT05ULUZBTUlMWTogIlRpbWVzIE5ldyBSb21hbiI7IFRFWFQtQUxJR046
IGp1c3RpZnkNCn0NCkRJVi5Nc29Ob3JtYWwgew0KCVRFWFQtSlVTVElGWTogaW50ZXItaWRlb2dy
YXBoOyBGT05ULVNJWkU6IDEwLjVwdDsgTUFSR0lOOiAwY20gMGNtIDBwdDsgRk9OVC1GQU1JTFk6
ICJUaW1lcyBOZXcgUm9tYW4iOyBURVhULUFMSUdOOiBqdXN0aWZ5DQp9DQpBOmxpbmsgew0KCUNP
TE9SOiBibHVlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZQ0KfQ0KU1BBTi5Nc29IeXBlcmxp
bmsgew0KCUNPTE9SOiBibHVlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZQ0KfQ0KQTp2aXNp
dGVkIHsNCglDT0xPUjogcHVycGxlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZQ0KfQ0KU1BB
Ti5Nc29IeXBlcmxpbmtGb2xsb3dlZCB7DQoJQ09MT1I6IHB1cnBsZTsgVEVYVC1ERUNPUkFUSU9O
OiB1bmRlcmxpbmUNCn0NClNQQU4uRW1haWxTdHlsZTE3IHsNCglGT05ULVdFSUdIVDogbm9ybWFs
OyBDT0xPUjogd2luZG93dGV4dDsgRk9OVC1TVFlMRTogbm9ybWFsOyBGT05ULUZBTUlMWTogVmVy
ZGFuYTsgVEVYVC1ERUNPUkFUSU9OOiBub25lOyBtc28tc3R5bGUtdHlwZTogcGVyc29uYWwtY29t
cG9zZQ0KfQ0KRElWLlNlY3Rpb24xIHsNCglwYWdlOiBTZWN0aW9uMQ0KfQ0KVU5LTk9XTiB7DQoJ
Rk9OVC1TSVpFOiAxMHB0DQp9DQpCTE9DS1FVT1RFIHsNCglNQVJHSU4tVE9QOiAwcHg7IE1BUkdJ
Ti1CT1RUT006IDBweDsgTUFSR0lOLUxFRlQ6IDJlbQ0KfQ0KT0wgew0KCU1BUkdJTi1UT1A6IDBw
eDsgTUFSR0lOLUJPVFRPTTogMHB4DQp9DQpVTCB7DQoJTUFSR0lOLVRPUDogMHB4OyBNQVJHSU4t
Qk9UVE9NOiAwcHgNCn0NCjwvU1RZTEU+DQoNCjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA4LjAwLjYw
MDEuMTg4MTIiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPkBmb250LWZhY2Ugew0KCWZvbnQtZmFt
aWx5OiDLzszlOw0KfQ0KQGZvbnQtZmFjZSB7DQoJZm9udC1mYW1pbHk6IFZlcmRhbmE7DQp9DQpA
Zm9udC1mYWNlIHsNCglmb250LWZhbWlseTogQMvOzOU7DQp9DQpAcGFnZSBTZWN0aW9uMSB7c2l6
ZTogNTk1LjNwdCA4NDEuOXB0OyBtYXJnaW46IDcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDsg
bGF5b3V0LWdyaWQ6IDE1LjZwdDsgfQ0KUC5Nc29Ob3JtYWwgew0KCVRFWFQtSlVTVElGWTogaW50
ZXItaWRlb2dyYXBoOyBGT05ULVNJWkU6IDEwLjVwdDsgTUFSR0lOOiAwY20gMGNtIDBwdDsgRk9O
VC1GQU1JTFk6ICJUaW1lcyBOZXcgUm9tYW4iOyBURVhULUFMSUdOOiBqdXN0aWZ5DQp9DQpMSS5N
c29Ob3JtYWwgew0KCVRFWFQtSlVTVElGWTogaW50ZXItaWRlb2dyYXBoOyBGT05ULVNJWkU6IDEw
LjVwdDsgTUFSR0lOOiAwY20gMGNtIDBwdDsgRk9OVC1GQU1JTFk6ICJUaW1lcyBOZXcgUm9tYW4i
OyBURVhULUFMSUdOOiBqdXN0aWZ5DQp9DQpESVYuTXNvTm9ybWFsIHsNCglURVhULUpVU1RJRlk6
IGludGVyLWlkZW9ncmFwaDsgRk9OVC1TSVpFOiAxMC41cHQ7IE1BUkdJTjogMGNtIDBjbSAwcHQ7
IEZPTlQtRkFNSUxZOiAiVGltZXMgTmV3IFJvbWFuIjsgVEVYVC1BTElHTjoganVzdGlmeQ0KfQ0K
QTpsaW5rIHsNCglDT0xPUjogYmx1ZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRlcmxpbmUNCn0NClNQ
QU4uTXNvSHlwZXJsaW5rIHsNCglDT0xPUjogYmx1ZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRlcmxp
bmUNCn0NCkE6dmlzaXRlZCB7DQoJQ09MT1I6IHB1cnBsZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRl
cmxpbmUNCn0NClNQQU4uTXNvSHlwZXJsaW5rRm9sbG93ZWQgew0KCUNPTE9SOiBwdXJwbGU7IFRF
WFQtREVDT1JBVElPTjogdW5kZXJsaW5lDQp9DQpTUEFOLkVtYWlsU3R5bGUxNyB7DQoJRk9OVC1X
RUlHSFQ6IG5vcm1hbDsgQ09MT1I6IHdpbmRvd3RleHQ7IEZPTlQtU1RZTEU6IG5vcm1hbDsgRk9O
VC1GQU1JTFk6IFZlcmRhbmE7IFRFWFQtREVDT1JBVElPTjogbm9uZTsgbXNvLXN0eWxlLXR5cGU6
IHBlcnNvbmFsLWNvbXBvc2UNCn0NCkRJVi5TZWN0aW9uMSB7DQoJcGFnZTogU2VjdGlvbjENCn0N
ClVOS05PV04gew0KCUZPTlQtU0laRTogMTBwdA0KfQ0KQkxPQ0tRVU9URSB7DQoJTUFSR0lOLVRP
UDogMHB4OyBNQVJHSU4tQk9UVE9NOiAwcHg7IE1BUkdJTi1MRUZUOiAyZW0NCn0NCk9MIHsNCglN
QVJHSU4tVE9QOiAwcHg7IE1BUkdJTi1CT1RUT006IDBweA0KfQ0KVUwgew0KCU1BUkdJTi1UT1A6
IDBweDsgTUFSR0lOLUJPVFRPTTogMHB4DQp9DQo8L1NUWUxFPg0KPC9IRUFEPg0KPEJPRFkgc3R5
bGU9IkZPTlQtU0laRTogMTBwdDsgTUFSR0lOOiAxMHB4OyBGT05ULUZBTUlMWTogdmVyZGFuYSI+
DQo8RElWPjxGT05UIGZhY2U9VmVyZGFuYSBzaXplPTI+PEZPTlQgZmFjZT1WZXJkYW5hIHNpemU9
Mj48Rk9OVCBmYWNlPVZlcmRhbmEgDQpzaXplPTI+U3VwcG9ydDwvRk9OVD48L0ZPTlQ+PC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPVZlcmRhbmEgc2l6ZT0yPjxGT05UIGZhY2U9VmVyZGFu
YSBzaXplPTI+PEZPTlQgZmFjZT1WZXJkYW5hIA0Kc2l6ZT0yPiZuYnNwOzwvRElWPg0KPERJVj4N
CjxESVY+DQo8RElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PC9GT05UPjxGT05UIGZhY2U9
VmVyZGFuYSBzaXplPTI+WmhpaHVhIExpdTwvRk9OVD48Rk9OVCBmYWNlPVZlcmRhbmEgDQpzaXpl
PTI+Jm5ic3A7IA0KPEhSIHN0eWxlPSJXSURUSDogMTIycHg7IEhFSUdIVDogMnB4IiBhbGlnbj1s
ZWZ0IFNJWkU9Mj4NCjwvRElWPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+Jm5ic3A7
PC9ESVY+DQo8RElWPkZyb206Jm5ic3A7bWF0dGhldy5ib2NjaUBhbGNhdGVsLWx1Y2VudC5jb208
L0RJVj4NCjxESVY+DQo8RElWPlRvOiZuYnNwO3B3ZTNAaWV0Zi5vcmc8L0RJVj4NCjxESVY+RGF0
ZTombmJzcDtXZWQsJm5ic3A7MTYmbmJzcDtGZWImbmJzcDsyMDExJm5ic3A7MTM6NDY6MTkmbmJz
cDsrMDEwMDwvRElWPg0KPERJVj5TdWJqZWN0OiZuYnNwO1tQV0UzXSZuYnNwO1dHJm5ic3A7UG9s
bCZuYnNwO29uJm5ic3A7ZHJhZnQtamluLXB3ZTMtY2JpdC1uZWdvdGlhdGlvbi0wMy50eHQ8L0RJ
Vj4NCjxESVY+PC9ESVY+DQo8RElWPjwvRElWPg0KPERJVj48L0RJVj4NCjxESVY+V0csPC9ESVY+
DQo8RElWPjwvRElWPg0KPERJVj48L0RJVj4NCjxESVY+VGhlJm5ic3A7YXV0aG9ycyZuYnNwO29m
Jm5ic3A7ZHJhZnQtamluLXB3ZTMtY2JpdC1uZWdvdGlhdGlvbi0wMyZuYnNwO2hhdmUmbmJzcDth
c2tlZCZuYnNwO3RoYXQmbmJzcDt0aGUmbmJzcDtXRyZuYnNwO2Fkb3B0Jm5ic3A7dGhpcyZuYnNw
O2FzJm5ic3A7YSZuYnNwO1BXRTMmbmJzcDt3b3JraW5nJm5ic3A7Z3JvdXAmbmJzcDtkcmFmdC48
L0RJVj4NCjxESVY+PC9ESVY+DQo8RElWPjwvRElWPg0KPERJVj5UaGlzJm5ic3A7ZW1haWwmbmJz
cDtiZWdpbnMmbmJzcDthJm5ic3A7dHdvJm5ic3A7d2VlayZuYnNwO3BvbGwmbmJzcDt0byZuYnNw
O2hlbHAmbmJzcDt1cyZuYnNwO2p1ZGdlJm5ic3A7aWYmbmJzcDt0aGVyZSZuYnNwO2lzJm5ic3A7
Y29uc2Vuc3VzJm5ic3A7dG8mbmJzcDttb3ZlJm5ic3A7Zm9yd2FyZCZuYnNwO3dpdGgmbmJzcDt0
aGUmbmJzcDtkcmFmdC48L0RJVj4NCjxESVY+PC9ESVY+DQo8RElWPjwvRElWPg0KPERJVj5QbGVh
c2UmbmJzcDtwb3N0Jm5ic3A7YW55Jm5ic3A7Y29tbWVudHMmbmJzcDt0byZuYnNwO3RoZSZuYnNw
O1BXRTMmbmJzcDtsaXN0Jm5ic3A7YnkmbmJzcDtXZWRuZXNkYXkmbmJzcDsybmQmbmJzcDtNYXJj
aC48L0RJVj4NCjxESVY+PC9ESVY+DQo8RElWPjwvRElWPg0KPERJVj5SZWdhcmRzLDwvRElWPg0K
PERJVj48L0RJVj4NCjxESVY+PC9ESVY+DQo8RElWPk1hdHRoZXcmbmJzcDsmYW1wOyZuYnNwO0Fu
ZHk8L0RJVj4NCjxESVY+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18mbmJzcDtwd2UzJm5ic3A7bWFpbGluZyZuYnNwO2xpc3QmbmJzcDtwd2UzQGlldGYub3Jn
Jm5ic3A7PEEgDQpocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3B3
ZTMiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHdlMzwvQT48Rk9OVCAN
CmZhY2U9VmVyZGFuYSBzaXplPTI+PC9ESVY+DQo8RElWPg0KPERJVj4mbmJzcDs8L0RJVj48L0ZP
TlQ+MjAxMS0wMy0xPC9ESVY+PC9ESVY+PC9GT05UPjwvRk9OVD48L0RJVj48L0ZPTlQ+PC9ESVY+
PC9CT0RZPjwvSFRNTD4NCg==

--=====003_Dragon824572225828_=====--
 

From lizhong.jin@zte.com.cn  Tue Mar  1 08:26:39 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FE463A6989 for <pwe3@core3.amsl.com>; Tue,  1 Mar 2011 08:26:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.838
X-Spam-Level: 
X-Spam-Status: No, score=-101.838 tagged_above=-999 required=5 tests=[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 QADiZK1XrYIr for <pwe3@core3.amsl.com>; Tue,  1 Mar 2011 08:26:36 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 139A53A6943 for <pwe3@ietf.org>; Tue,  1 Mar 2011 08:26:35 -0800 (PST)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 205951397396305; Wed, 2 Mar 2011 00:22:25 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.16] with StormMail ESMTP id 91645.4879443054; Wed, 2 Mar 2011 00:18:19 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p21GROUl025484; Wed, 2 Mar 2011 00:27:24 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
To: lmartini@cisco.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF2A6830E9.A42B0A6B-ON48257846.0045F488-48257846.005A66D6@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Wed, 2 Mar 2011 00:27:21 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-02 00:27:25, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-02 00:27:25, Serialize complete at 2011-03-02 00:27:25, S/MIME Sign failed at 2011-03-02 00:27:25: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-03-02 00:27:27, Serialize complete at 2011-03-02 00:27:27
Content-Type: multipart/alternative; boundary="=_alternative 005A66CE48257846_="
X-MAIL: mse02.zte.com.cn p21GROUl025484
Cc: pwe3@ietf.org, andrew.g.malis@verizon.com
Subject: Re: [PWE3] more comments on draft-jin-pwe3-cbit-negotiation-03
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 16:26:39 -0000

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

Hi Luca,
Thank you for the comments. 

If I understand correctly, we have discussed the possible race conditions 
in rare cases before, which is raised by Spike. And if we assume that the 
remote T-PE possiblly receive label request before label withdraw in MS-PW 
case, then local T-PE sends label request after receiving label release 
will not solve the issue.
T-PE1-------S-PE2-------S-PE3------T-PE4
If T-PE4 is the local T-PE, and send label withdraw to S-PE3; S-PE3 will 
recieve the label withdraw, reply with label release and send label 
withdraw to upstream; then T-PE4 will send label request to S-PE3. But if 
S-PE will not process the message by sequence (for example, S-PE2 receive 
label withdraw, delay to reply with label release and send label withdraw 
upstream, receive and process label request and send label request to 
upstream, then reply with label release and send label withdraw upstream), 
it is still possible for T-PE1 to receive label request before label 
withdraw in above MS-PW case.

Then we make one requriement for the message processing on S-PE to avoid 
such race condition in the draft section 3 paragraph 6: As local T-PE will 
send label withdraw before sending label request to remote peer, the S-PE 
MUST send the label withdraw upstream before it advertises the label 
request. Since TCP is as sequence transmission protocol, we require the 
S-PE to process the LDP message by: first received, first processed, which 
I think complys with possiblly most current implementation. When S-PE 
receive the label withdraw, it should process this message to send a label 
release as a response and a label withdraw to upstream S-PE/T-PE, then 
process the next LDP message, e.g, the label request message. By applying 
such behavior, the race condition can be avoided. However, it would be 
more secure to require PE to send label request after receiving label 
release.

Other comments, please see in line below.

Regards
Lizhong


-------send by Luca 
Martini----------------------------------------------------
Authors,

In section 3 on page 4 is the following text :

"The procedure of PE1 and PE2 for the case in figure 1 should be as
   follows:

       1. PE2 changes locally configured control word to PREFERRED.

       2. PE2 will then send label withdraw message to PE1.

       3. PE2 MUST send label request messages to PE1 although it
          already received the label mapping with C-bit=0.

       4. PE1 will send label release in reply to label withdraw message
          from PE2.

       5. PE1 will send label mapping message with C-bit=1 again to PE2
          (Note: PE1 MUST send label mapping with locally configured CW
           parameter).

       6. PE2 receives the label mapping from PE1 and updates the remote
          label binding information.  PE2 MUST wait for PE1 label
          binding before sending its label binding with C-bit set, only
          if it previously had a label binding with C-bit = 0 from PE1.

       7. PE2 will send label mapping to PE1 with C-bit=1.
"

First of all the steps above are asynchronous, so it seems that step 4
should appear before step 3 or the old label mapping might be sent.
Step 5 is in response to step 3 , but that is not clear from the above 
list.
[Lizhong] if agree, according to the explanation at the beginning of this 
email, we could swap step 3 and 4 for more secure. And yes, step 5 should 
be detailed to explicitly say the response of step 3.

Also what happens if PE1 cannot support the CW ?  The above descriptions
assumes PE1 can support the CW.
[Lizhong] the above description is the example of figure 1. We can add a 
sentance after the example as: If PE1 does not support the CW, following 
the above procedure, PE2 will receive the label mapping from PE1 with 
C-bit=0, and send label mapping to PE1 with C-bit=0. The CW negotiation 
result is still right.

Also this label withdraw + label request procedure is fully backward 
compatible with previous implementations. The document should explain
this point.
[Lizhong] agree, and to added in the updated draft.
 
The label withdraw should really wait for the label release, as in the
case of MS-PWs , sending an immediate label request can cause a race
condition , and result in the wrong state.
[Lizhong] do you mean the label request should wait for the label release, 
not label withdraw? And explained at the beginning of this email. And I 
tend to add more detail to make it clear in section 3: when S-PE receive 
the label withdraw, it should process this message to send a label release 
as a response and a label withdraw to upstream S-PE/T-PE, then process the 
next receving LDP message, e.g, the label request message.


Thanks.
Luca
 
 

--------------------------------------------------------
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 005A66CE48257846_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Luca,</font>
<br><font size=2 face="sans-serif">Thank you for the comments. </font>
<br>
<br><font size=2 face="sans-serif">If I understand correctly, we have discussed
the possible race conditions in rare cases before, which is raised by Spike.
And if we assume that the remote T-PE possiblly receive label request before
label withdraw in MS-PW case, then local T-PE sends label request after
receiving label release will not solve the issue.</font>
<br><font size=2 face="sans-serif">T-PE1-------S-PE2-------S-PE3------T-PE4</font>
<br><font size=2 face="sans-serif">If T-PE4 is the local T-PE, and send
label withdraw to S-PE3; S-PE3 will recieve the label withdraw, reply with
label release and send label withdraw to upstream; then T-PE4 will send
label request to S-PE3. But if S-PE will not process the message by sequence
(for example, S-PE2 receive label withdraw, delay to reply with label release
and send label withdraw upstream, receive and process label request and
send label request to upstream, then reply with label release and send
label withdraw upstream), it is still possible for T-PE1 to receive label
request before label withdraw in above MS-PW case.</font>
<br>
<br><font size=2 face="sans-serif">Then we make one requriement for the
message processing on S-PE to avoid such race condition in the draft section
3 paragraph 6: As local T-PE will send label withdraw before sending label
request to remote peer, the S-PE MUST send the label withdraw upstream
before it advertises the label request. Since TCP is as sequence transmission
protocol, we require the S-PE to process the LDP message by: first received,
first processed, which I think complys with possiblly most current implementation.
When S-PE receive the label withdraw, it should process this message to
send a label release as a response and a label withdraw to upstream S-PE/T-PE,
then process the next LDP message, e.g, the label request message. By applying
such behavior, the race condition can be avoided. However, it would be
more secure to require PE to send label request after receiving label release.</font>
<br>
<br><font size=2 face="sans-serif">Other comments, please see in line below.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br>
<br>
<br><font size=2 face="sans-serif">-------send by Luca Martini----------------------------------------------------<br>
Authors,</font>
<br>
<br><font size=2 face="sans-serif">In section 3 on page 4 is the following
text :</font>
<br>
<br><font size=2 face="sans-serif">&quot;The procedure of PE1 and PE2 for
the case in figure 1 should be as</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;follows:</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;1. PE2 changes
locally configured control word to PREFERRED.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;2. PE2 will
then send label withdraw message to PE1.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;3. PE2 MUST
send label request messages to PE1 although it</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; already
received the label mapping with C-bit=0.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;4. PE1 will
send label release in reply to label withdraw message</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; from
PE2.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;5. PE1 will
send label mapping message with C-bit=1 again to PE2</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Note:
PE1 MUST send label mapping with locally configured CW</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;parameter).</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;6. PE2 receives
the label mapping from PE1 and updates the remote</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; label
binding information. &nbsp;PE2 MUST wait for PE1 label</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; binding
before sending its label binding with C-bit set, only</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; if
it previously had a label binding with C-bit = 0 from PE1.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;7. PE2 will
send label mapping to PE1 with C-bit=1.</font>
<br><font size=2 face="sans-serif">&quot;</font>
<br>
<br><font size=2 face="sans-serif">First of all the steps above are asynchronous,
so it seems that step 4</font>
<br><font size=2 face="sans-serif">should appear before step 3 or the old
label mapping might be sent.</font>
<br><font size=2 face="sans-serif">Step 5 is in response to step 3 , but
that is not clear from the above list.</font>
<br><font size=2 face="sans-serif">[Lizhong] if agree, according to the
explanation at the beginning of this email, we could swap step 3 and 4
for more secure. And yes, step 5 should be detailed to explicitly say the
response of step 3.</font>
<br>
<br><font size=2 face="sans-serif">Also what happens if PE1 cannot support
the CW ? &nbsp;The above descriptions</font>
<br><font size=2 face="sans-serif">assumes PE1 can support the CW.</font>
<br><font size=2 face="sans-serif">[Lizhong] the above description is the
example of figure 1. We can add a sentance after the example as: If PE1
does not support the CW, following the above procedure, PE2 will receive
the label mapping from PE1 with C-bit=0, and send label mapping to PE1
with C-bit=0. The CW negotiation result is still right.</font>
<br>
<br><font size=2 face="sans-serif">Also this label withdraw + label request
procedure is fully backward </font>
<br><font size=2 face="sans-serif">compatible with previous implementations.
The document should explain</font>
<br><font size=2 face="sans-serif">this point.</font>
<br><font size=2 face="sans-serif">[Lizhong] agree, and to added in the
updated draft.</font>
<br><font size=2 face="sans-serif">&nbsp;</font>
<br><font size=2 face="sans-serif">The label withdraw should really wait
for the label release, as in the</font>
<br><font size=2 face="sans-serif">case of MS-PWs , sending an immediate
label request can cause a race</font>
<br><font size=2 face="sans-serif">condition , and result in the wrong
state.</font>
<br><font size=2 face="sans-serif">[Lizhong] do you mean the label request
should wait for the label release, not label withdraw? And explained at
the beginning of this email. And I tend to add more detail to make it clear
in section 3: when S-PE receive the label withdraw, it should process this
message to send a label release as a response and a label withdraw to upstream
S-PE/T-PE, then process the next receving LDP message, e.g, the label request
message.</font>
<br>
<br>
<br><font size=2 face="sans-serif">Thanks.</font>
<br><font size=2 face="sans-serif">Luca</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br><font size=1 face="Arial">&nbsp;</font><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 005A66CE48257846_=--


From dai.xuehui@zte.com.cn  Tue Mar  1 18:31:34 2011
Return-Path: <dai.xuehui@zte.com.cn>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 416043A6C11 for <pwe3@core3.amsl.com>; Tue,  1 Mar 2011 18:31:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.705
X-Spam-Level: 
X-Spam-Status: No, score=-96.705 tagged_above=-999 required=5 tests=[AWL=0.929, 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 cwKjetZAWa-U for <pwe3@core3.amsl.com>; Tue,  1 Mar 2011 18:31:33 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 86F6A3A6A16 for <pwe3@ietf.org>; Tue,  1 Mar 2011 18:31:32 -0800 (PST)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205951397396305; Wed, 2 Mar 2011 10:27:23 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 84746.2368962204; Wed, 2 Mar 2011 10:32:30 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p222WQTV097452; Wed, 2 Mar 2011 10:32:26 +0800 (GMT-8) (envelope-from dai.xuehui@zte.com.cn)
In-Reply-To: <C981779B.9722%matthew.bocci@alcatel-lucent.com>
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF15125802.47918270-ON48257847.000DE3ED-48257847.000DF577@zte.com.cn>
From: dai.xuehui@zte.com.cn
Date: Wed, 2 Mar 2011 10:32:00 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-03-02 10:32:26, Serialize complete at 2011-03-02 10:32:26
Content-Type: multipart/alternative; boundary="=_alternative 000DF57748257847_="
X-MAIL: mse01.zte.com.cn p222WQTV097452
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 02:31:34 -0000

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

U3VwcG9ydKOhDQoNCnh1ZWh1aQ0KDQoNCg0KDQoiQm9jY2ksIE1hdHRoZXcgKE1hdHRoZXcpIiA8
bWF0dGhldy5ib2NjaUBhbGNhdGVsLWx1Y2VudC5jb20+IA0Kt6K8/sjLOiAgcHdlMy1ib3VuY2Vz
QGlldGYub3JnDQoyMDExLTAyLTE2IDIwOjQ2DQoNCsrVvP7Iyw0KInB3ZTNAaWV0Zi5vcmciIDxw
d2UzQGlldGYub3JnPg0Ks63LzQ0KDQrW98ziDQpbUFdFM10gV0cgUG9sbCBvbiBkcmFmdC1qaW4t
cHdlMy1jYml0LW5lZ290aWF0aW9uLTAzLnR4dA0KDQoNCg0KDQoNCg0KV0csDQoNClRoZSBhdXRo
b3JzIG9mIGRyYWZ0LWppbi1wd2UzLWNiaXQtbmVnb3RpYXRpb24tMDMgaGF2ZSBhc2tlZCB0aGF0
IHRoZSBXRyANCmFkb3B0IHRoaXMgYXMgYSBQV0UzIHdvcmtpbmcgZ3JvdXAgZHJhZnQuDQoNClRo
aXMgZW1haWwgYmVnaW5zIGEgdHdvIHdlZWsgcG9sbCB0byBoZWxwIHVzIGp1ZGdlIGlmIHRoZXJl
IGlzIGNvbnNlbnN1cyANCnRvIG1vdmUgZm9yd2FyZCB3aXRoIHRoZSBkcmFmdC4NCg0KUGxlYXNl
IHBvc3QgYW55IGNvbW1lbnRzIHRvIHRoZSBQV0UzIGxpc3QgYnkgV2VkbmVzZGF5IDJuZCBNYXJj
aC4NCg0KUmVnYXJkcywNCg0KTWF0dGhldyAmIEFuZHlfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KcHdlMyBtYWlsaW5nIGxpc3QNCnB3ZTNAaWV0Zi5vcmcN
Cmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHdlMw0KDQoNCg==
--=_alternative 000DF57748257847_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlN1cHBvcnSjoTwvZm9udD4NCjxi
cj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+eHVlaHVpPC9mb250Pg0KPGJy
Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4N
Cjx0ZCB3aWR0aD0zNSU+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjxiPiZxdW90O0Jv
Y2NpLCBNYXR0aGV3IChNYXR0aGV3KSZxdW90Ow0KJmx0O21hdHRoZXcuYm9jY2lAYWxjYXRlbC1s
dWNlbnQuY29tJmd0OzwvYj4gPC9mb250Pg0KPGJyPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNl
cmlmIj63orz+yMs6ICZuYnNwO3B3ZTMtYm91bmNlc0BpZXRmLm9yZzwvZm9udD4NCjxwPjxmb250
IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj4yMDExLTAyLTE2IDIwOjQ2PC9mb250Pg0KPHRkIHdp
ZHRoPTY0JT4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2
IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7K1bz+yMs8L2ZvbnQ+
PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPiZxdW90O3B3ZTNAaWV0
Zi5vcmcmcXVvdDsgJmx0O3B3ZTNAaWV0Zi5vcmcmZ3Q7PC9mb250Pg0KPHRyIHZhbGlnbj10b3A+
DQo8dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj6z
rcvNPC9mb250PjwvZGl2Pg0KPHRkPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWdu
PXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7W98ziPC9mb250PjwvZGl2Pg0K
PHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5bUFdFM10gV0cgUG9sbCBvbiBkcmFm
dC1qaW4tcHdlMy1jYml0LW5lZ290aWF0aW9uLTAzLnR4dDwvZm9udD48L3RhYmxlPg0KPGJyPg0K
PHRhYmxlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8dGQ+PC90YWJsZT4NCjxicj48L3RhYmxl
Pg0KPGJyPg0KPGJyPg0KPGJyPjxmb250IHNpemU9MSBmYWNlPSJDYWxpYnJpIj5XRyw8L2ZvbnQ+
DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0xIGZhY2U9IkNhbGlicmkiPlRoZSBhdXRob3JzIG9mIDwv
Zm9udD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+ZHJhZnQtamluLXB3ZTMtY2JpdC1u
ZWdvdGlhdGlvbi0wMw0KaGF2ZSBhc2tlZCB0aGF0IHRoZSBXRyBhZG9wdCB0aGlzIGFzIGEgUFdF
MyB3b3JraW5nIGdyb3VwIGRyYWZ0LjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTEgZmFj
ZT0ic2Fucy1zZXJpZiI+VGhpcyBlbWFpbCBiZWdpbnMgYSB0d28gd2VlayBwb2xsIHRvDQpoZWxw
IHVzIGp1ZGdlIGlmIHRoZXJlIGlzIGNvbnNlbnN1cyB0byBtb3ZlIGZvcndhcmQgd2l0aCB0aGUg
ZHJhZnQuPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5Q
bGVhc2UgcG9zdCBhbnkgY29tbWVudHMgdG8gdGhlIFBXRTMNCmxpc3QgYnkgV2VkbmVzZGF5IDJu
ZCBNYXJjaC48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYi
PlJlZ2FyZHMsPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlm
Ij5NYXR0aGV3ICZhbXA7IEFuZHk8L2ZvbnQ+PHR0Pjxmb250IHNpemU9Mj5fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCnB3ZTMgbWFpbGluZyBsaXN0
PGJyPg0KcHdlM0BpZXRmLm9yZzxicj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vcHdlMzxicj4NCjwvZm9udD48L3R0Pg0KPGJyPg0K
--=_alternative 000DF57748257847_=--


From lucy.yong@huawei.com  Wed Mar  2 07:48:09 2011
Return-Path: <lucy.yong@huawei.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20AB13A6810 for <pwe3@core3.amsl.com>; Wed,  2 Mar 2011 07:48:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.394
X-Spam-Level: 
X-Spam-Status: No, score=-5.394 tagged_above=-999 required=5 tests=[AWL=-0.655, BAYES_20=-0.74, 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 0rQ9rYA-9LiO for <pwe3@core3.amsl.com>; Wed,  2 Mar 2011 07:48:08 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 529B83A683E for <pwe3@ietf.org>; Wed,  2 Mar 2011 07:48:08 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LHF001CITA142@usaga02-in.huawei.com> for pwe3@ietf.org; Wed, 02 Mar 2011 07:49:14 -0800 (PST)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LHF005GMTA1ZK@usaga02-in.huawei.com> for pwe3@ietf.org; Wed, 02 Mar 2011 07:49:13 -0800 (PST)
Received: from DFWEML402-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 02 Mar 2011 07:49:08 -0800
Received: from DFWEML501-MBX.china.huawei.com ([fe80::c52a:9e19:87eb:4531]) by DFWEML402-HUB.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Wed, 02 Mar 2011 07:49:12 -0800
Date: Wed, 02 Mar 2011 15:49:11 +0000
From: Lucy yong <lucy.yong@huawei.com>
In-reply-to: <C981779B.9722%matthew.bocci@alcatel-lucent.com>
X-Originating-IP: [10.124.12.68]
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Message-id: <2691CE0099834E4A9C5044EEC662BB9D2AD2AB@DFWEML501-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_5XVH5D0vmt+yLEeIl1cFKA)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt
Thread-index: AcvN14N/U4dKgzs0QU+tIbqk21be5gLGdM2g
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <C981779B.9722%matthew.bocci@alcatel-lucent.com>
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 15:48:09 -0000

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

Support!

Lucy

________________________________
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Bocci, Matthew (Matthew)
Sent: Wednesday, February 16, 2011 6:46 AM
To: pwe3@ietf.org
Subject: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt

WG,

The authors of draft-jin-pwe3-cbit-negotiation-03 have asked that the WG adopt this as a PWE3 working group draft.

This email begins a two week poll to help us judge if there is consensus to move forward with the draft.

Please post any comments to the PWE3 list by Wednesday 2nd March.

Regards,

Matthew & Andy

--Boundary_(ID_5XVH5D0vmt+yLEeIl1cFKA)
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)">
<!--[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: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:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:sans-serif;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Device Font 10cpi";
	panose-1:0 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;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0pt;
	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.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class="Section1">
<p class="MsoNormal"><font size="3" color="blue" face="Courier New"><span style="font-size:12.0pt;font-family:&quot;Courier New&quot;;color:blue">Support!<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:&quot;Courier New&quot;;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:&quot;Courier New&quot;;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:&quot;Courier New&quot;;color:blue"><o:p>&nbsp;</o:p></span></font></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0pt 0pt 0pt 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"> pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
<b><span style="font-weight:
bold">On Behalf Of </span></b>Bocci, Matthew (Matthew)<br>
<b><span style="font-weight:bold">Sent:</span></b> Wednesday, February 16, 2011 6:46 AM<br>
<b><span style="font-weight:bold">To:</span></b> pwe3@ietf.org<br>
<b><span style="font-weight:bold">Subject:</span></b> [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt</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>
<div>
<p class="MsoNormal"><span class="apple-style-span"><font size="1" color="black" face="Calibri"><span style="font-size:9.0pt;font-family:Calibri;color:black">WG,</span></font></span><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;
color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><font size="1" color="black" face="Calibri"><span style="font-size:9.0pt;font-family:Calibri;color:black">The authors of&nbsp;</span></font></span><span class="apple-style-span"><font size="1" color="black" face="sans-serif"><span style="font-size:9.0pt;font-family:sans-serif;
color:black">draft-jin-pwe3-cbit-negotiation-03
 have asked that the WG adopt this as a PWE3 working group draft.</span></font></span><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;
color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><font size="1" color="black" face="sans-serif"><span style="font-size:9.0pt;font-family:sans-serif;color:black">This email begins a two week poll to help us judge if there is consensus to move forward with
 the draft.</span></font></span><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><font size="1" color="black" face="sans-serif"><span style="font-size:9.0pt;font-family:sans-serif;color:black">Please post any comments to the PWE3 list by Wednesday 2nd March.</span></font></span><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;
color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><font size="1" color="black" face="sans-serif"><span style="font-size:9.0pt;font-family:sans-serif;color:black">Regards,</span></font></span><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;
color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><font size="1" color="black" face="sans-serif"><span style="font-size:9.0pt;font-family:sans-serif;color:black">Matthew &amp; Andy</span></font></span><font size="2" color="black" face="Calibri"><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p></o:p></span></font></p>
</div>
</div>
</div>
</body>
</html>

--Boundary_(ID_5XVH5D0vmt+yLEeIl1cFKA)--

From Internet-Drafts@ietf.org  Wed Mar  2 14:15:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7229E3A68C4; Wed,  2 Mar 2011 14:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, 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 xjNPUHwrw+00; Wed,  2 Mar 2011 14:15:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCCD53A67B5; Wed,  2 Mar 2011 14:15:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110302221501.32505.63905.idtracker@localhost>
Date: Wed, 02 Mar 2011 14:15:01 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-static-pw-status-02.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 22:15:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudowire Emulation Edge to Edge Working Group of the IETF.


	Title           : Pseudowire Status for Static Pseudowires
	Author(s)       : L. Martini, et al.
	Filename        : draft-ietf-pwe3-static-pw-status-02.txt
	Pages           : 13
	Date            : 2011-03-02

This document specifies a mechanism to signal Pseudowire (PW) status
messages using an PW associated channel (ACh). Such a mechanism is
suitable for use where no PW dynamic control plane exits, known as
static PWs, or where a Terminating Provider Edge (T-PE) needs to send
a PW status message directly to a far end T-PE. The mechanism allows
PW OAM message mapping and PW redundancy to operate on static PWs.

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

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


--NextPart--

From Internet-Drafts@ietf.org  Wed Mar  2 14:15:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94B773A67B5; Wed,  2 Mar 2011 14:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, 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 7gDsq82KXP0T; Wed,  2 Mar 2011 14:15:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D27423A6889; Wed,  2 Mar 2011 14:15:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110302221501.32505.75899.idtracker@localhost>
Date: Wed, 02 Mar 2011 14:15:01 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-p2mp-pw-02.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 22:15:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudowire Emulation Edge to Edge Working Group of the IETF.


	Title           : Signaling Root-Initiated Point-to-Multipoint Pseudowires using LDP
	Author(s)       : L. Martini, et al.
	Filename        : draft-ietf-pwe3-p2mp-pw-02.txt
	Pages           : 18
	Date            : 2011-03-02

This document specifies a mechanism to signal Point-to-Multipoint
(P2MP) Pseudowires (PW) tree using LDP. Such a mechanism is suitable
for any Layer 2 VPN service requiring P2MP connectivity over an IP or
MPLS-enabled PSN. A P2MP PW established via the proposed mechanism is
root initiated.

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

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


--NextPart--

From lizhong.jin@zte.com.cn  Thu Mar  3 07:40:20 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E2D83A69E9 for <pwe3@core3.amsl.com>; Thu,  3 Mar 2011 07:40:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.838
X-Spam-Level: 
X-Spam-Status: No, score=-101.838 tagged_above=-999 required=5 tests=[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 LE8hDJqozkDq for <pwe3@core3.amsl.com>; Thu,  3 Mar 2011 07:40:19 -0800 (PST)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 881503A699F for <pwe3@ietf.org>; Thu,  3 Mar 2011 07:40:18 -0800 (PST)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35101397396305; Thu, 3 Mar 2011 23:39:10 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.15] with StormMail ESMTP id 84746.6161798737; Thu, 3 Mar 2011 23:41:20 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p23FfCJ9007654; Thu, 3 Mar 2011 23:41:12 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
To: lmartini@cisco.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF1E77B4A7.8BFBB01F-ON48257847.00149D26-48257848.00562B1B@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Thu, 3 Mar 2011 23:41:00 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-03 23:41:11, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-03 23:41:11, Serialize complete at 2011-03-03 23:41:11, S/MIME Sign failed at 2011-03-03 23:41:11: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-03-03 23:41:15, Serialize complete at 2011-03-03 23:41:15
Content-Type: multipart/alternative; boundary="=_alternative 00562B1948257848_="
X-MAIL: mse02.zte.com.cn p23FfCJ9007654
Cc: pwe3@ietf.org, andrew.g.malis@verizon.com
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt ( comment )
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2011 15:40:20 -0000

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

Luca,
After discussing with the authors, we decide to add the wait for label 
release before sending label request, this wouldn't harm and bring some 
secure.

Then are you OK with the following text?

When Local PE changes its control word from NOT PREFERRED to PREFERRED and 
only if it already received the remote label mapping message with C-bit=0, 
additional procedure will be added as follow:
-i Local PE MUST send a label withdraw message to remote PE if it has 
previously sent a label mapping, and wait until receiving a label release 
from the remote PE.
-ii Local PE MUST send a label request message to remote PE, and wait 
until receiving a label mapping message containing the remote PE 
configured control word setting.
-iii After receiving remote PE label mapping with control word setting, 
Local PE MUST follow procedures defined in [RFC4447] section 6 when 
sending it's label mapping message.

Correspondingly, the modified procedure of PE in figure 1 will be as 
follows:

1. PE2 changes locally configured control word to PREFERRED. 
2. PE2 will then send label withdraw message to PE1. 
3. PE1 MUST send label release in reply to label withdraw message from 
PE2. 
4. Upon receipt of Label release message from PE1, PE2 MUST send label 
request messages to PE1 although it already received the label mapping 
with C-bit=0. 
5. PE1 MUST send label mapping message with C-bit=1 again to PE2 (Note: 
PE1 MUST send label mapping with locally configured CW parameter). 
6. PE2 receives the label mapping from PE1 and updates the remote label 
binding information. PE2 MUST wait for PE1 label binding before sending 
its label binding with C-bit set, only if it previously had a label 
binding with C-bit = 0 from PE1. 
7. PE2 will send label mapping to PE1 with C-bit=1. 

It is to be noted that the above assume that PE1 is configured to support 
CW, however in step 5 if PE1 doesn't support CW, PE1 would send the label 
mapping message with C-bit =0, this would result in PE2 in step 7 sending 
a label mapping with C-bit=0 as per [RFC4447] CW negotiation procedure.

Thanks
Lizhong


------------send by Luca 
Martini-------------------------------------------
Matthew & Andy,


Although I support clarifying this procedure , I believe this document
needs some work.
In section 3 for example :

   When Local PE changes its control word from NOT PREFERRED to
   PREFERRED and only if it already received the remote label mapping
   message with C-bit=0, additional procedure will be added as follow:

         -i. Local PE sends label withdraw message to the remote if it
             already sends label mapping message, for it has changed its
             control word parameter.

        -ii. Local PE MUST send a label request messages to peer PE to
             get peer's configured control word parameter before sending
             new label mapping message to peer PE.

       -iii. After receiving the new label mapping message from peer PE
             and updating the remote label binding information, the
             Local PE should send label mapping to peer PE according to
             procedures defined in [RFC4447].

What does the item i) mean ? the English is not clear.
Why does the PE have to do ii) ?

All we really need is a statement on how the c-bit negotiation state
machine can be reset if one end has changed "his mind" .

Can we fix this document before  issuing the -00 WG draft version ?

Thanks.
Luca
 

--------------------------------------------------------
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 00562B1948257848_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Luca,</font>
<br><font size=2 face="sans-serif">After discussing with the authors, we
decide to add the wait for label release before sending label request,
this wouldn't harm and bring some secure.</font>
<br>
<br><font size=2 face="sans-serif">Then are you OK with the following text?</font>
<br>
<br><font size=2 face="sans-serif">When Local PE changes its control word
from NOT PREFERRED to PREFERRED and only if it already received the remote
label mapping message with C-bit=0, additional procedure will be added
as follow:</font>
<br><font size=2 face="sans-serif">-i Local PE MUST send a label withdraw
message to remote PE if it has previously sent a label mapping, and wait
until receiving a label release from the remote PE.</font>
<br><font size=2 face="sans-serif">-ii Local PE MUST send a label request
message to remote PE, and wait until receiving a label mapping message
containing the remote PE configured control word setting.</font>
<br><font size=2 face="sans-serif">-iii After receiving remote PE label
mapping with control word setting, Local PE MUST follow procedures defined
in [RFC4447] section 6 when sending it's label mapping message.</font>
<br>
<br><font size=2 face="sans-serif">Correspondingly, the modified procedure
of PE in figure 1 will be as follows:</font>
<br>
<br><font size=2 face="sans-serif">1. PE2 changes locally configured control
word to PREFERRED. </font>
<br><font size=2 face="sans-serif">2. PE2 will then send label withdraw
message to PE1. </font>
<br><font size=2 face="sans-serif">3. PE1 MUST send label release in reply
to label withdraw message from PE2. </font>
<br><font size=2 face="sans-serif">4. Upon receipt of Label release message
from PE1, PE2 MUST send label request messages to PE1 although it already
received the label mapping with C-bit=0. </font>
<br><font size=2 face="sans-serif">5. PE1 MUST send label mapping message
with C-bit=1 again to PE2 (Note: PE1 MUST send label mapping with locally
configured CW parameter). </font>
<br><font size=2 face="sans-serif">6. PE2 receives the label mapping from
PE1 and updates the remote label binding information. PE2 MUST wait for
PE1 label binding before sending its label binding with C-bit set, only
if it previously had a label binding with C-bit = 0 from PE1. </font>
<br><font size=2 face="sans-serif">7. PE2 will send label mapping to PE1
with C-bit=1. </font>
<br>
<br><font size=2 face="sans-serif">It is to be noted that the above assume
that PE1 is configured to support CW, however in step 5 if PE1 doesn't
support CW, PE1 would send the label mapping message with C-bit =0, this
would result in PE2 in step 7 sending a label mapping with C-bit=0 as per
[RFC4447] CW negotiation procedure.</font>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br>
<br>
<br><font size=2 face="sans-serif">------------send by Luca Martini-------------------------------------------</font>
<br><font size=2 face="sans-serif">Matthew &amp; Andy,</font>
<br>
<br>
<br><font size=2 face="sans-serif">Although I support clarifying this procedure
, I believe this document</font>
<br><font size=2 face="sans-serif">needs some work.</font>
<br><font size=2 face="sans-serif">In section 3 for example :</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;When Local PE changes its
control word from NOT PREFERRED to</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;PREFERRED and only if it
already received the remote label mapping</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;message with C-bit=0, additional
procedure will be added as follow:</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;-i.
Local PE sends label withdraw message to the remote if it</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;already sends label mapping message, for it has changed its</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;control word parameter.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; -ii. Local
PE MUST send a label request messages to peer PE to</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;get peer's configured control word parameter before sending</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;new label mapping message to peer PE.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;-iii. After
receiving the new label mapping message from peer PE</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;and updating the remote label binding information, the</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;Local PE should send label mapping to peer PE according to</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;procedures defined in [RFC4447].</font>
<br>
<br><font size=2 face="sans-serif">What does the item i) mean ? the English
is not clear.</font>
<br><font size=2 face="sans-serif">Why does the PE have to do ii) ?</font>
<br>
<br><font size=2 face="sans-serif">All we really need is a statement on
how the c-bit negotiation state</font>
<br><font size=2 face="sans-serif">machine can be reset if one end has
changed &quot;his mind&quot; .</font>
<br>
<br><font size=2 face="sans-serif">Can we fix this document before &nbsp;issuing
the -00 WG draft version ?</font>
<br>
<br><font size=2 face="sans-serif">Thanks.</font>
<br><font size=2 face="sans-serif">Luca</font>
<br><font size=2 face="sans-serif">&nbsp;</font><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 00562B1948257848_=--


From matthew.bocci@alcatel-lucent.com  Thu Mar  3 08:47:03 2011
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AED233A6A04 for <pwe3@core3.amsl.com>; Thu,  3 Mar 2011 08:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.928
X-Spam-Level: 
X-Spam-Status: No, score=-105.928 tagged_above=-999 required=5 tests=[AWL=0.320, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, 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 XrG4klBJWqTK for <pwe3@core3.amsl.com>; Thu,  3 Mar 2011 08:47:03 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id A12613A6980 for <pwe3@ietf.org>; Thu,  3 Mar 2011 08:47:02 -0800 (PST)
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 p23GkdTm002067 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <pwe3@ietf.org>; Thu, 3 Mar 2011 17:48:09 +0100
Received: from FRMRSSXCHMBSA3.dc-m.alcatel-lucent.com ([135.120.45.36]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Thu, 3 Mar 2011 17:48:06 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Date: Thu, 3 Mar 2011 17:48:03 +0100
Thread-Topic: WG Last Call for draft-ietf-pwe3-mpls-eth-oam-iwk-04.txt
Thread-Index: AcvZwsThQMM12xuITbyzxEdmA6ZfmQ==
Message-ID: <C99576C3.A8DA%matthew.bocci@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C99576C3A8DAmatthewboccialcatellucentcom_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Subject: [PWE3] WG Last Call for draft-ietf-pwe3-mpls-eth-oam-iwk-04.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2011 16:47:03 -0000

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

This email begins a working group last call for draft-ietf-pwe3-mpls-eth-oa=
m-iwk-04.txt<http://tools.ietf.org/html/draft-ietf-pwe3-mpls-eth-oam-iwk-04=
.txt>.

We are running this LC for three weeks due to its proximity to the Prague I=
ETF.

This WG LC will end on 25th March 2011.

Please respond with any comments to the PWE3 mailing list.

Regards,

Matthew and Andy


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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-si=
ze: 14px; font-family: Calibri, sans-serif; "><div><span class=3D"Apple-sty=
le-span" style=3D"font-family: Times; font-size: medium; "><pre style=3D"wh=
ite-space: pre-wrap; word-wrap: break-word; width: 1123px; ">This email beg=
ins a working group last call for <a href=3D"http://tools.ietf.org/html/dra=
ft-ietf-pwe3-mpls-eth-oam-iwk-04.txt">draft-ietf-pwe3-mpls-eth-oam-iwk-04.t=
xt</a>.

We are running this LC for three weeks due to its proximity to the Prague I=
ETF.&nbsp;</pre><pre style=3D"white-space: pre-wrap; word-wrap: break-word;=
 width: 1123px; ">This WG LC will end on 25th March 2011.

Please respond with any comments to the PWE3 mailing list.

Regards,

Matthew and Andy
 </pre></span></div></body></html>

--_000_C99576C3A8DAmatthewboccialcatellucentcom_--

From amalis@gmail.com  Mon Mar  7 07:51:36 2011
Return-Path: <amalis@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 879033A67D3 for <pwe3@core3.amsl.com>; Mon,  7 Mar 2011 07:51:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 Nn+ROubIHoOB for <pwe3@core3.amsl.com>; Mon,  7 Mar 2011 07:51:34 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 155453A686E for <pwe3@ietf.org>; Mon,  7 Mar 2011 07:51:33 -0800 (PST)
Received: by eye13 with SMTP id 13so1789656eye.31 for <pwe3@ietf.org>; Mon, 07 Mar 2011 07:52:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=yPTTr+b1WYMXlhTHXCrWpYFrsANPTIBc5SJ6ivGhukQ=; b=Fh1sBzPTELu18XNdtxuCeaNGAR8j9NI48roRRrzB997VoW3nsIwWbiWdGirzIGrcQv 2e1jDfWo1M7+JxTYTSy5QLoOTPns5zRT07RbQ+efIKLiaZjz3t7mwHwyyVGxalp38eUN t97R/dq0l2p1I6EzUBhSjbS88FiZkhPbZRopk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=whMqIdU82XFJnh/IPX7VN8yBsqOiPkfBfcxlrdXDte7mMdVqr+MTlz2zbWvettCq+q xIjoWWKj9+ZiPCBMEbBtMKONIzyWAjF37h2SiuX0RZKpRHCyuuOzvDUUrsTW6dHgC5Ey KIVnfwBYwuncKDIObNn53nUZSfYzrrPuWFO6c=
Received: by 10.14.132.199 with SMTP id o47mr1520580eei.34.1299513166925; Mon, 07 Mar 2011 07:52:46 -0800 (PST)
MIME-Version: 1.0
Sender: amalis@gmail.com
Received: by 10.14.48.10 with HTTP; Mon, 7 Mar 2011 07:52:22 -0800 (PST)
In-Reply-To: <OF1E77B4A7.8BFBB01F-ON48257847.00149D26-48257848.00562B1B@zte.com.cn>
References: <OF1E77B4A7.8BFBB01F-ON48257847.00149D26-48257848.00562B1B@zte.com.cn>
From: "Andrew G. Malis" <andrew.g.malis@verizon.com>
Date: Mon, 7 Mar 2011 10:52:22 -0500
X-Google-Sender-Auth: EQVa35cvdBPjLU0zf1Y-QkaRlhI
Message-ID: <AANLkTimcc2-zCW_P2ONCtpR-kNxPhBLEY6mKAy6TmX-+@mail.gmail.com>
To: lizhong.jin@zte.com.cn
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable
Cc: pwe3@ietf.org, lmartini@cisco.com
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt ( comment )
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 15:51:36 -0000

Lizhong,

There's been a lot of support for WG adoption of this draft. Please
update the draft to -04 to reflect the discussion on the list (before
the window closes in a week) and we'll announce the adoption in
Prague, followed by having you issue the WG version of the draft.

Thanks,
Andy

On Thu, Mar 3, 2011 at 10:41 AM,  <lizhong.jin@zte.com.cn> wrote:
>
> Luca,
> After discussing with the authors, we decide to add the wait for label
> release before sending label request, this wouldn't harm and bring some
> secure.
>
> Then are you OK with the following text?
>
> When Local PE changes its control word from NOT PREFERRED to PREFERRED an=
d
> only if it already received the remote label mapping message with C-bit=
=3D0,
> additional procedure will be added as follow:
> -i Local PE MUST send a label withdraw message to remote PE if it has
> previously sent a label mapping, and wait until receiving a label release
> from the remote PE.
> -ii Local PE MUST send a label request message to remote PE, and wait unt=
il
> receiving a label mapping message containing the remote PE configured
> control word setting.
> -iii After receiving remote PE label mapping with control word setting,
> Local PE MUST follow procedures defined in [RFC4447] section 6 when sendi=
ng
> it's label mapping message.
>
> Correspondingly, the modified procedure of PE in figure 1 will be as
> follows:
>
> 1. PE2 changes locally configured control word to PREFERRED.
> 2. PE2 will then send label withdraw message to PE1.
> 3. PE1 MUST send label release in reply to label withdraw message from PE=
2.
> 4. Upon receipt of Label release message from PE1, PE2 MUST send label
> request messages to PE1 although it already received the label mapping wi=
th
> C-bit=3D0.
> 5. PE1 MUST send label mapping message with C-bit=3D1 again to PE2 (Note:=
 PE1
> MUST send label mapping with locally configured CW parameter).
> 6. PE2 receives the label mapping from PE1 and updates the remote label
> binding information. PE2 MUST wait for PE1 label binding before sending i=
ts
> label binding with C-bit set, only if it previously had a label binding w=
ith
> C-bit =3D 0 from PE1.
> 7. PE2 will send label mapping to PE1 with C-bit=3D1.
>
> It is to be noted that the above assume that PE1 is configured to support
> CW, however in step 5 if PE1 doesn't support CW, PE1 would send the label
> mapping message with C-bit =3D0, this would result in PE2 in step 7 sendi=
ng a
> label mapping with C-bit=3D0 as per [RFC4447] CW negotiation procedure.
>
> Thanks
> Lizhong
>
>
> ------------send by Luca Martini-----------------------------------------=
--
> Matthew & Andy,
>
>
> Although I support clarifying this procedure , I believe this document
> needs some work.
> In section 3 for example :
>
>    When Local PE changes its control word from NOT PREFERRED to
>    PREFERRED and only if it already received the remote label mapping
>    message with C-bit=3D0, additional procedure will be added as follow:
>
>          -i. Local PE sends label withdraw message to the remote if it
>              already sends label mapping message, for it has changed its
>              control word parameter.
>
>         -ii. Local PE MUST send a label request messages to peer PE to
>              get peer's configured control word parameter before sending
>              new label mapping message to peer PE.
>
>        -iii. After receiving the new label mapping message from peer PE
>              and updating the remote label binding information, the
>              Local PE should send label mapping to peer PE according to
>              procedures defined in [RFC4447].
>
> What does the item i) mean ? the English is not clear.
> Why does the PE have to do ii) ?
>
> All we really need is a statement on how the c-bit negotiation state
> machine can be reset if one end has changed "his mind" .
>
> Can we fix this document before  issuing the -00 WG draft version ?
>
> Thanks.
> Luca
>
>
> --------------------------------------------------------
> 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.
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>

From Internet-Drafts@ietf.org  Mon Mar  7 08:00:05 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E975B3A6948; Mon,  7 Mar 2011 08:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, 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 M3luMw7bted2; Mon,  7 Mar 2011 08:00:03 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 665F53A6960; Mon,  7 Mar 2011 08:00:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110307160002.14542.89219.idtracker@localhost>
Date: Mon, 07 Mar 2011 08:00:02 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-cep-mib-15.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 16:00:05 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudowire Emulation Edge to Edge Working Group of the IETF.


	Title           : SONET/SDH Circuit Emulation Service Over Packet (CEP) Management Information Base (MIB) Using SMIv2
	Author(s)       : D. Zelig, et al.
	Filename        : draft-ietf-pwe3-cep-mib-15.txt
	Pages           : 65
	Date            : 2011-03-07

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling SONET/SDH
circuits over a Packet Switch Network (PSN).

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

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


--NextPart--

From lmartini@cisco.com  Mon Mar  7 11:34:03 2011
Return-Path: <lmartini@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B7293A680E for <pwe3@core3.amsl.com>; Mon,  7 Mar 2011 11:34:03 -0800 (PST)
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 k0crs-Y5RWOv for <pwe3@core3.amsl.com>; Mon,  7 Mar 2011 11:34:02 -0800 (PST)
Received: from napoleon.monoski.com (napoleon.monoski.com [70.90.113.113]) by core3.amsl.com (Postfix) with ESMTP id 234253A6809 for <pwe3@ietf.org>; Mon,  7 Mar 2011 11:34:02 -0800 (PST)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id p27JZ9Fg017906 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 7 Mar 2011 12:35:11 -0700 (MST)
Message-ID: <4D75336C.2060505@cisco.com>
Date: Mon, 07 Mar 2011 12:35:08 -0700
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 ThunderBrowse/3.3.5
MIME-Version: 1.0
To: lizhong.jin@zte.com.cn
References: <OF1E77B4A7.8BFBB01F-ON48257847.00149D26-48257848.00562B1B@zte.com.cn>
In-Reply-To: <OF1E77B4A7.8BFBB01F-ON48257847.00149D26-48257848.00562B1B@zte.com.cn>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org, andrew.g.malis@verizon.com
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt ( comment )
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 19:34:03 -0000

Sorry for the late response , comments below:
Luca


On 03/03/11 08:41, lizhong.jin@zte.com.cn wrote:
>
> Luca,
> After discussing with the authors, we decide to add the wait for label
> release before sending label request, this wouldn't harm and bring
> some secure.
>
> Then are you OK with the following text?
>
> When Local PE changes its control word from NOT PREFERRED to PREFERRED
> and only if it already received the remote label mapping message with
> C-bit=0, additional procedure will be added as follow:
> -i Local PE MUST send a label withdraw message to remote PE if it has
> previously sent a label mapping, and wait until receiving a label
> release from the remote PE.
> -ii Local PE MUST send a label request message to remote PE, and wait
> until receiving a label mapping message containing the remote PE
> configured control word setting.
> -iii After receiving remote PE label mapping with control word
> setting, Local PE MUST follow procedures defined in [RFC4447] section
> 6 when sending it's label mapping message.
>
Ok the above text is fine.
However you need to address the case when the Local PE changes its
control word from  PREFERRED to NOT PREFERRED as well.


> Correspondingly, the modified procedure of PE in figure 1 will be as
> follows:
>
> 1. PE2 changes locally configured control word to PREFERRED.
> 2. PE2 will then send label withdraw message to PE1.
> 3. PE1 MUST send label release in reply to label withdraw message from
> PE2.
> 4. Upon receipt of Label release message from PE1, PE2 MUST send label
> request messages to PE1 although it already received the label mapping
> with C-bit=0.
> 5. PE1 MUST send label mapping message with C-bit=1 again to PE2
> (Note: PE1 MUST send label mapping with locally configured CW parameter).
> 6. PE2 receives the label mapping from PE1 and updates the remote
> label binding information. PE2 MUST wait for PE1 label binding before
> sending its label binding with C-bit set, only if it previously had a
> label binding with C-bit = 0 from PE1.
> 7. PE2 will send label mapping to PE1 with C-bit=1.
>
No, the above procedure will result in a LDP error and session shutdown.
In LDP you  cannot "update" the FEC.  In step 5 PE1 can only send the
label mapping message it has previously sent. So PE1 cannot change the
C-Bit without first issuing a label withdraw.

> It is to be noted that the above assume that PE1 is configured to
> support CW, however in step 5 if PE1 doesn't support CW, PE1 would
> send the label mapping message with C-bit =0, this would result in PE2
> in step 7 sending a label mapping with C-bit=0 as per [RFC4447] CW
> negotiation procedure.
>
What is needed is some way to send a message to the remote PE that the
C-bit negotiation procedure needs to be re-started.

Solution 1

one way to get this procedure working is to have PE2 release the label
mapping previously sent by PE1.
If you do this today, most implementations will simply go to a dead
state requiring operator intervention.
What should happen is that upon receiving the label release , PE1 should
withdraw it's label mapping , and reset the c-bit negotiation state
machine , and re-advertise the new label mapping restarting the
procedure described in rfc4447 from the beginning.

Solution 2

Whenever a PE withdraws a FEC mapping , the remote PE resets the C-bit
negotiation procedure. If this results in a different C-bit local value
then previously advertised , the local PE MUST go though a label
withdraw/label release/label advertisement cycle.


Both solutions above should work within the  LDP rules and are backward
compatible. I like solution 2 a bit better.

Luca

> Thanks
> Lizhong
>
>
> ------------send by Luca
> Martini-------------------------------------------
> Matthew & Andy,
>
>
> Although I support clarifying this procedure , I believe this document
> needs some work.
> In section 3 for example :
>
>    When Local PE changes its control word from NOT PREFERRED to
>    PREFERRED and only if it already received the remote label mapping
>    message with C-bit=0, additional procedure will be added as follow:
>
>          -i. Local PE sends label withdraw message to the remote if it
>              already sends label mapping message, for it has changed its
>              control word parameter.
>
>         -ii. Local PE MUST send a label request messages to peer PE to
>              get peer's configured control word parameter before sending
>              new label mapping message to peer PE.
>
>        -iii. After receiving the new label mapping message from peer PE
>              and updating the remote label binding information, the
>              Local PE should send label mapping to peer PE according to
>              procedures defined in [RFC4447].
>
> What does the item i) mean ? the English is not clear.
> Why does the PE have to do ii) ?
>
> All we really need is a statement on how the c-bit negotiation state
> machine can be reset if one end has changed "his mind" .
>
> Can we fix this document before  issuing the -00 WG draft version ?
>
> Thanks.
> Luca
>  
> --------------------------------------------------------
> 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.


From Internet-Drafts@ietf.org  Tue Mar  8 05:45:05 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4632F3A6892; Tue,  8 Mar 2011 05:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, 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 IDxO+BCxBvQb; Tue,  8 Mar 2011 05:45:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 987533A684F; Tue,  8 Mar 2011 05:45:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110308134501.12716.84916.idtracker@localhost>
Date: Tue, 08 Mar 2011 05:45:01 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-cep-mib-16.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 13:45:05 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudowire Emulation Edge to Edge Working Group of the IETF.


	Title           : SONET/SDH Circuit Emulation Service Over Packet (CEP) Management Information Base (MIB) Using SMIv2
	Author(s)       : D. Zelig, et al.
	Filename        : draft-ietf-pwe3-cep-mib-16.txt
	Pages           : 65
	Date            : 2011-03-08

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling SONET/SDH
circuits over a Packet Switch Network (PSN).

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

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


--NextPart--

From nick.delregno@verizon.com  Tue Mar  8 06:26:42 2011
Return-Path: <nick.delregno@verizon.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5ECF43A688F for <pwe3@core3.amsl.com>; Tue,  8 Mar 2011 06:26:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.341
X-Spam-Level: 
X-Spam-Status: No, score=-3.341 tagged_above=-999 required=5 tests=[AWL=0.258,  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 swymOk6S4ZoG for <pwe3@core3.amsl.com>; Tue,  8 Mar 2011 06:26:40 -0800 (PST)
Received: from ashesmtp03.verizonbusiness.com (ashesmtp03.verizonbusiness.com [198.4.8.167]) by core3.amsl.com (Postfix) with ESMTP id C99EC3A67B7 for <pwe3@ietf.org>; Tue,  8 Mar 2011 06:26:40 -0800 (PST)
Received: from pdcismtp03.vzbi.com ([unknown] [166.40.77.73]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LHQ0052WTHTDB40@firewall.verizonbusiness.com> for pwe3@ietf.org; Tue, 08 Mar 2011 14:27:29 +0000 (GMT)
Received: from pdcismtp03.vzbi.com ([unknown] [127.0.0.1]) by pdcismtp03.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LHQ00FKVTHSU200@pdcismtp03.vzbi.com> for pwe3@ietf.org; Tue, 08 Mar 2011 14:27:28 +0000 (GMT)
Received: from ASHSRV142.mcilink.com ([unknown] [153.39.68.168]) by pdcismtp03.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LHQ00F67THSUW00@pdcismtp03.vzbi.com> for pwe3@ietf.org; Tue, 08 Mar 2011 14:27:28 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV142.mcilink.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 08 Mar 2011 14:27:28 +0000
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: base64
Date: Tue, 08 Mar 2011 14:27:25 +0000
Message-id: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
Thread-index: Acvdm33bS8HQGFieTSSSyunk7NkzBAAABRxQ
From: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
To: pwe3 <pwe3@ietf.org>
X-OriginalArrivalTime: 08 Mar 2011 14:27:28.0716 (UTC) FILETIME=[F3EC08C0:01CBDD9C]
Subject: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 14:26:42 -0000

Rm9sa3M6DQoNClRoZSAwMCBkcmFmdCBvZiB0aGUgUFcvVkNDViBJbXBsZW1lbnRhdGlvbiBTdXJ2
ZXkgUmVzdWx0cyBoYXZlIGJlZW4gdXBsb2FkZWQuICBJIHdpbGwgYmUgcHJlc2VudGluZyB0aGUg
cmVzdWx0cyBhdCBJRVRGODAuDQoNCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWRlbHJlZ25vLXB3LXZjY3YtaW1wbC1zdXJ2ZXktcmVzdWx0cy8NCg0KVGhhbmtzLA0KTmlj
aw0KDQpDaHJpc3RvcGhlciBOLiBEZWwgUmVnbm8sIFBNVFMNCkMmVCwgRXRoZXJuZXQgTmV0d29y
ayBBcmNoaXRlY3R1cmUgJiBEZXNpZ24NCjQwMCBJbnRlcm5hdGlvbmFsIFBrd3kNClJpY2hhcmRz
b24sIFRYICA3NTA4MQ0KOTcyLTcyOS0zNDExDQpuaWNrLmRlbHJlZ25vQHZlcml6b24uY29tDQoN
Cg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBJRVRGIEktRCBTdWJtaXNz
aW9uIFRvb2wgW21haWx0bzppZHN1Ym1pc3Npb25AaWV0Zi5vcmddIA0KU2VudDogVHVlc2RheSwg
TWFyY2ggMDgsIDIwMTEgODoxNiBBTQ0KVG86IERlbHJlZ25vLCBDaHJpc3RvcGhlciBOIChOaWNr
IERlbFJlZ25vKQ0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1k
ZWxyZWduby1wdy12Y2N2LWltcGwtc3VydmV5LXJlc3VsdHMtMDANCg0KDQpBIG5ldyB2ZXJzaW9u
IG9mIEktRCwgZHJhZnQtZGVscmVnbm8tcHctdmNjdi1pbXBsLXN1cnZleS1yZXN1bHRzLTAwLnR4
dCBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IE5pY2sgRGVsIFJlZ25vIGFuZCBw
b3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6CSBkcmFmdC1kZWxyZWdu
by1wdy12Y2N2LWltcGwtc3VydmV5LXJlc3VsdHMNClJldmlzaW9uOgkgMDANClRpdGxlOgkJIFRo
ZSBQc2V1ZG93aXJlIChQVykgJiBWaXJ0dWFsIENpcmN1aXQgQ29ubmVjdGl2aXR5IFZlcmlmaWNh
dGlvbiAoVkNDVikgSW1wbGVtZW50YXRpb24gU3VydmV5IFJlc3VsdHMNCkNyZWF0aW9uX2RhdGU6
CSAyMDExLTAzLTA3DQpXRyBJRDoJCSBJbmRlcGVuZGVudCBTdWJtaXNzaW9uDQpOdW1iZXJfb2Zf
cGFnZXM6IDE2DQoNCkFic3RyYWN0Og0KTW9zdCBQc2V1ZG93aXJlIEVtdWxhdGlvbiBFZGdlLXRv
LUVkZ2UgKFBXRTMpIGVuY2Fwc3VsYXRpb25zIG1hbmRhdGUNCnRoZSB1c2Ugb2YgdGhlIENvbnRy
b2wgV29yZCAoQ1cpIGluIG9yZGVyIHRvIGJldHRlciBlbXVsYXRlIHRoZQ0Kc2VydmljZXMgZm9y
IHdoaWNoIHRoZSBlbmNhcHN1bGF0aW9ucyBoYXZlIGJlZW4gZGVmaW5lZC4gIEhvd2V2ZXIsDQpz
b21lIGVuY2FwdWxhdGlvbnMgdHJlYXQgdGhlIENvbnRyb2wgV29yZCBhcyBvcHRpb25hbC4gIEFz
IGEgcmVzdWx0LA0KaW1wbGVtZW50YXRpb25zIG9mIHRoZSBDVywgZm9yIGVuY2Fwc3VsYXRpb25z
IGZvciB3aGljaCBpdCBpcw0Kb3B0aW9uYWwsIHZhcnkgYnkgZXF1aXBtZW50IG1hbnVmYWN0dXJl
ciwgZXF1aXBtZW50IG1vZGVsIGFuZCBzZXJ2aWNlDQpwcm92aWRlciBuZXR3b3JrLiAgU2ltaWxh
cmx5LCBWaXJ0dWFsIENpcmN1aXQgQ29ubmVjdGl2aXR5DQpWZXJpZmljYXRpb24gKFZDQ1YpIHN1
cHBvcnRzIHRocmVlIENvbnRyb2wgQ2hhbm5lbCAoQ0MpIHR5cGVzIGFuZA0KbXVsdGlwbGUgQ29u
bmVjdGl2aXR5IFZlcmlmaWNhdGlvbiAoQ1YpIFR5cGVzLiAgVGhpcyBmbGV4aWJpbGl0eSBoYXMN
CmxlZCB0byByZXBvcnRzIG9mIGludGVyb3BlcmFiaWxpdHkgaXNzdWVzIHdpdGhpbiBkZXBsb3ll
ZCBuZXR3b3Jrcw0KYW5kIGFzc29jaWF0ZWQgZHJhZnRzIHRvIGF0dGVtcHQgdG8gcmVtZWR5IHRo
ZSBzaXR1YXRpb24uICBUaGlzDQpzdXJ2ZXkgb2YgdGhlIFBXL1ZDQ1YgdXNlciBjb21tdW5pdHkg
d2FzIGNvbmR1Y3RlZCB0byBkZXRlcm1pbmUNCmltcGxlbWVudGF0aW9uIHRyZW5kcy4gIFRoZSBz
dXJ2ZXkgYW5kIHJlc3VsdHMgaXMgcHJlc2VudGVkIGhlcmVpbi4NCiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICANCg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdC4NCg0KDQo=

From lizhong.jin@zte.com.cn  Tue Mar  8 08:06:22 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 955A13A68A7 for <pwe3@core3.amsl.com>; Tue,  8 Mar 2011 08:06:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.838
X-Spam-Level: 
X-Spam-Status: No, score=-101.838 tagged_above=-999 required=5 tests=[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 nPrOby7QVqwp for <pwe3@core3.amsl.com>; Tue,  8 Mar 2011 08:06:20 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 05C533A689A for <pwe3@ietf.org>; Tue,  8 Mar 2011 08:06:19 -0800 (PST)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205951397396305; Wed, 9 Mar 2011 00:02:15 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.15] with StormMail ESMTP id 84746.6161798737; Wed, 9 Mar 2011 00:07:28 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p28G7KXK028653; Wed, 9 Mar 2011 00:07:20 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <4D75336C.2060505@cisco.com>
To: Luca Martini <lmartini@cisco.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFF0D0A956.E47DE79C-ON4825784D.0020F561-8725784D.00589090@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Wed, 9 Mar 2011 00:06:45 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-08 09:07:22, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-08 09:07:22, Serialize complete at 2011-03-08 09:07:22, S/MIME Sign failed at 2011-03-08 09:07:22: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-03-09 00:07:24, Serialize complete at 2011-03-09 00:07:24
Content-Type: multipart/alternative; boundary="=_alternative 005890828725784D_="
X-MAIL: mse02.zte.com.cn p28G7KXK028653
Cc: pwe3@ietf.org, andrew.g.malis@verizon.com
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt ( comment )
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 16:06:22 -0000

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

Luca,
Thank you for the comments. Please see my reply in line.

Regards
Lizhong


Luca Martini <lmartini@cisco.com> wrote on 2011-03-08 03:35:08:

> Sorry for the late response , comments below:
> Luca
> 
> 
> On 03/03/11 08:41, lizhong.jin@zte.com.cn wrote:
> >
> > Luca,
> > After discussing with the authors, we decide to add the wait for label
> > release before sending label request, this wouldn't harm and bring
> > some secure.
> >
> > Then are you OK with the following text?
> >
> > When Local PE changes its control word from NOT PREFERRED to PREFERRED
> > and only if it already received the remote label mapping message with
> > C-bit=0, additional procedure will be added as follow:
> > -i Local PE MUST send a label withdraw message to remote PE if it has
> > previously sent a label mapping, and wait until receiving a label
> > release from the remote PE.
> > -ii Local PE MUST send a label request message to remote PE, and wait
> > until receiving a label mapping message containing the remote PE
> > configured control word setting.
> > -iii After receiving remote PE label mapping with control word
> > setting, Local PE MUST follow procedures defined in [RFC4447] section
> > 6 when sending it's label mapping message.
> >
> Ok the above text is fine.
> However you need to address the case when the Local PE changes its
> control word from  PREFERRED to NOT PREFERRED as well.
[Lizhong] yes, and already addressed in section 3 at the beginning of 
page4 of this draft.

> 
> 
> > Correspondingly, the modified procedure of PE in figure 1 will be as
> > follows:
> >
> > 1. PE2 changes locally configured control word to PREFERRED.
> > 2. PE2 will then send label withdraw message to PE1.
> > 3. PE1 MUST send label release in reply to label withdraw message from
> > PE2.
> > 4. Upon receipt of Label release message from PE1, PE2 MUST send label
> > request messages to PE1 although it already received the label mapping
> > with C-bit=0.
> > 5. PE1 MUST send label mapping message with C-bit=1 again to PE2
> > (Note: PE1 MUST send label mapping with locally configured CW 
parameter).
> > 6. PE2 receives the label mapping from PE1 and updates the remote
> > label binding information. PE2 MUST wait for PE1 label binding before
> > sending its label binding with C-bit set, only if it previously had a
> > label binding with C-bit = 0 from PE1.
> > 7. PE2 will send label mapping to PE1 with C-bit=1.
> >
> No, the above procedure will result in a LDP error and session shutdown.
> In LDP you  cannot "update" the FEC.  In step 5 PE1 can only send the
> label mapping message it has previously sent. So PE1 cannot change the
> C-Bit without first issuing a label withdraw.
[Lizhong] I don't think such procedure will result in a sesion down 
according to RFC5036. Actually, this is what we want to standardize for 
the PW-FEC processing, to add a way of updating PW-FEC. Another way to 
update PW-FEC is to let PE1 send label withdraw (maybe with wrong C-bit) 
before sending label mapping in step 5, as a reply to the label request. 
But this will lead to additional control message load and is not aligned 
with "receiving label request" behavior in A.1.1 in RFC5036, which makes 
us to abandon it.

> 
> > It is to be noted that the above assume that PE1 is configured to
> > support CW, however in step 5 if PE1 doesn't support CW, PE1 would
> > send the label mapping message with C-bit =0, this would result in PE2
> > in step 7 sending a label mapping with C-bit=0 as per [RFC4447] CW
> > negotiation procedure.
> >
> What is needed is some way to send a message to the remote PE that the
> C-bit negotiation procedure needs to be re-started.
> 
> Solution 1
> 
> one way to get this procedure working is to have PE2 release the label
> mapping previously sent by PE1.
> If you do this today, most implementations will simply go to a dead
> state requiring operator intervention.
> What should happen is that upon receiving the label release , PE1 should
> withdraw it's label mapping , and reset the c-bit negotiation state
> machine , and re-advertise the new label mapping restarting the
> procedure described in rfc4447 from the beginning.
[Lizhong] This solution has been discussed before on PWE3 mail list (
http://www.ietf.org/mail-archive/web/pwe3/current/msg11484.html), and I 
also do not prefer this option.


> 
> Solution 2
> 
> Whenever a PE withdraws a FEC mapping , the remote PE resets the C-bit
> negotiation procedure. If this results in a different C-bit local value
> then previously advertised , the local PE MUST go though a label
> withdraw/label release/label advertisement cycle.
[Lizhong] Solution 2 has already been discussed before on mail list (
http://www.ietf.org/mail-archive/web/pwe3/current/msg11497.html), and also 
addressed in 00 version of this draft (
http://tools.ietf.org/html/draft-jin-pwe3-cbit-negotiation-00). 
Unfortunately, the mechanism can not work in MS-PW case.

> 
> 
> Both solutions above should work within the  LDP rules and are backward
> compatible. I like solution 2 a bit better.
> 
> Luca
> 
> > Thanks
> > Lizhong
> >
> >
> > ------------send by Luca
> > Martini-------------------------------------------
> > Matthew & Andy,
> >
> >
> > Although I support clarifying this procedure , I believe this document
> > needs some work.
> > In section 3 for example :
> >
> >    When Local PE changes its control word from NOT PREFERRED to
> >    PREFERRED and only if it already received the remote label mapping
> >    message with C-bit=0, additional procedure will be added as follow:
> >
> >          -i. Local PE sends label withdraw message to the remote if it
> >              already sends label mapping message, for it has changed 
its
> >              control word parameter.
> >
> >         -ii. Local PE MUST send a label request messages to peer PE to
> >              get peer's configured control word parameter before 
sending
> >              new label mapping message to peer PE.
> >
> >        -iii. After receiving the new label mapping message from peer 
PE
> >              and updating the remote label binding information, the
> >              Local PE should send label mapping to peer PE according 
to
> >              procedures defined in [RFC4447].
> >
> > What does the item i) mean ? the English is not clear.
> > Why does the PE have to do ii) ?
> >
> > All we really need is a statement on how the c-bit negotiation state
> > machine can be reset if one end has changed "his mind" .
> >
> > Can we fix this document before  issuing the -00 WG draft version ?
> >
> > Thanks.
> > Luca
> > 
> > --------------------------------------------------------
> > 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.
> 
> 


--------------------------------------------------------
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 005890828725784D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Luca,</font>
<br><font size=2 face="sans-serif">Thank you for the comments. Please see
my reply in line.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Lizhong<br>
</font>
<br>
<br><tt><font size=2>Luca Martini &lt;lmartini@cisco.com&gt; wrote on 2011-03-08
03:35:08:<br>
<br>
&gt; Sorry for the late response , comments below:<br>
&gt; Luca<br>
&gt; <br>
&gt; <br>
&gt; On 03/03/11 08:41, lizhong.jin@zte.com.cn wrote:<br>
&gt; &gt;<br>
&gt; &gt; Luca,<br>
&gt; &gt; After discussing with the authors, we decide to add the wait
for label<br>
&gt; &gt; release before sending label request, this wouldn't harm and
bring<br>
&gt; &gt; some secure.<br>
&gt; &gt;<br>
&gt; &gt; Then are you OK with the following text?<br>
&gt; &gt;<br>
&gt; &gt; When Local PE changes its control word from NOT PREFERRED to
PREFERRED<br>
&gt; &gt; and only if it already received the remote label mapping message
with<br>
&gt; &gt; C-bit=0, additional procedure will be added as follow:<br>
&gt; &gt; -i Local PE MUST send a label withdraw message to remote PE if
it has<br>
&gt; &gt; previously sent a label mapping, and wait until receiving a label<br>
&gt; &gt; release from the remote PE.<br>
&gt; &gt; -ii Local PE MUST send a label request message to remote PE,
and wait<br>
&gt; &gt; until receiving a label mapping message containing the remote
PE<br>
&gt; &gt; configured control word setting.<br>
&gt; &gt; -iii After receiving remote PE label mapping with control word<br>
&gt; &gt; setting, Local PE MUST follow procedures defined in [RFC4447]
section<br>
&gt; &gt; 6 when sending it's label mapping message.<br>
&gt; &gt;<br>
&gt; Ok the above text is fine.<br>
&gt; However you need to address the case when the Local PE changes its<br>
&gt; control word from &nbsp;PREFERRED to NOT PREFERRED as well.</font></tt>
<br><tt><font size=2>[Lizhong] yes, and already addressed in section 3
at the beginning of page4 of this draft.</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; <br>
&gt; &gt; Correspondingly, the modified procedure of PE in figure 1 will
be as<br>
&gt; &gt; follows:<br>
&gt; &gt;<br>
&gt; &gt; 1. PE2 changes locally configured control word to PREFERRED.<br>
&gt; &gt; 2. PE2 will then send label withdraw message to PE1.<br>
&gt; &gt; 3. PE1 MUST send label release in reply to label withdraw message
from<br>
&gt; &gt; PE2.<br>
&gt; &gt; 4. Upon receipt of Label release message from PE1, PE2 MUST send
label<br>
&gt; &gt; request messages to PE1 although it already received the label
mapping<br>
&gt; &gt; with C-bit=0.<br>
&gt; &gt; 5. PE1 MUST send label mapping message with C-bit=1 again to
PE2<br>
&gt; &gt; (Note: PE1 MUST send label mapping with locally configured CW
parameter).<br>
&gt; &gt; 6. PE2 receives the label mapping from PE1 and updates the remote<br>
&gt; &gt; label binding information. PE2 MUST wait for PE1 label binding
before<br>
&gt; &gt; sending its label binding with C-bit set, only if it previously
had a<br>
&gt; &gt; label binding with C-bit = 0 from PE1.<br>
&gt; &gt; 7. PE2 will send label mapping to PE1 with C-bit=1.<br>
&gt; &gt;<br>
&gt; No, the above procedure will result in a LDP error and session shutdown.<br>
&gt; In LDP you &nbsp;cannot &quot;update&quot; the FEC. &nbsp;In step
5 PE1 can only send the<br>
&gt; label mapping message it has previously sent. So PE1 cannot change
the<br>
&gt; C-Bit without first issuing a label withdraw.</font></tt>
<br><tt><font size=2>[Lizhong] I don't think such procedure will result
in a sesion down according to RFC5036. Actually, this is what we want to
standardize for the PW-FEC processing, to add a way of updating PW-FEC.
Another way to update PW-FEC is to let PE1 send label withdraw (maybe with
wrong C-bit) before sending label mapping in step 5, as a reply to the
label request. But this will lead to additional control message load and
is not aligned with &quot;receiving label request&quot; behavior in A.1.1
in RFC5036, which makes us to abandon it.</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; &gt; It is to be noted that the above assume that PE1 is configured
to<br>
&gt; &gt; support CW, however in step 5 if PE1 doesn't support CW, PE1
would<br>
&gt; &gt; send the label mapping message with C-bit =0, this would result
in PE2<br>
&gt; &gt; in step 7 sending a label mapping with C-bit=0 as per [RFC4447]
CW<br>
&gt; &gt; negotiation procedure.<br>
&gt; &gt;<br>
&gt; What is needed is some way to send a message to the remote PE that
the<br>
&gt; C-bit negotiation procedure needs to be re-started.<br>
&gt; <br>
&gt; Solution 1<br>
&gt; <br>
&gt; one way to get this procedure working is to have PE2 release the label<br>
&gt; mapping previously sent by PE1.<br>
&gt; If you do this today, most implementations will simply go to a dead<br>
&gt; state requiring operator intervention.<br>
&gt; What should happen is that upon receiving the label release , PE1
should<br>
&gt; withdraw it's label mapping , and reset the c-bit negotiation state<br>
&gt; machine , and re-advertise the new label mapping restarting the<br>
&gt; procedure described in rfc4447 from the beginning.</font></tt>
<br><tt><font size=2>[Lizhong] This solution has been discussed before
on PWE3 mail list (http://www.ietf.org/mail-archive/web/pwe3/current/msg11484.html),
and I also do not prefer this option.</font></tt>
<br>
<br><tt><font size=2><br>
&gt; <br>
&gt; Solution 2<br>
&gt; <br>
&gt; Whenever a PE withdraws a FEC mapping , the remote PE resets the C-bit<br>
&gt; negotiation procedure. If this results in a different C-bit local
value<br>
&gt; then previously advertised , the local PE MUST go though a label<br>
&gt; withdraw/label release/label advertisement cycle.</font></tt>
<br><tt><font size=2>[Lizhong] Solution 2 has already been discussed before
on mail list (http://www.ietf.org/mail-archive/web/pwe3/current/msg11497.html),
and also addressed in 00 version of this draft (http://tools.ietf.org/html/draft-jin-pwe3-cbit-negotiation-00).
Unfortunately, the mechanism can not work in MS-PW case.</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; <br>
&gt; Both solutions above should work within the &nbsp;LDP rules and are
backward<br>
&gt; compatible. I like solution 2 a bit better.<br>
&gt; <br>
&gt; Luca<br>
&gt; <br>
&gt; &gt; Thanks<br>
&gt; &gt; Lizhong<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; ------------send by Luca<br>
&gt; &gt; Martini-------------------------------------------<br>
&gt; &gt; Matthew &amp; Andy,<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Although I support clarifying this procedure , I believe this
document<br>
&gt; &gt; needs some work.<br>
&gt; &gt; In section 3 for example :<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp;When Local PE changes its control word from NOT
PREFERRED to<br>
&gt; &gt; &nbsp; &nbsp;PREFERRED and only if it already received the remote
label mapping<br>
&gt; &gt; &nbsp; &nbsp;message with C-bit=0, additional procedure will
be added as follow:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;-i. Local PE sends label withdraw
message to the remote if it<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;already sends
label mapping message, for it has changed its<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;control word
parameter.<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; -ii. Local PE MUST send a label request
messages to peer PE to<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;get peer's configured
control word parameter before sending<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;new label mapping
message to peer PE.<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;-iii. After receiving the new label
mapping message from peer PE<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;and updating
the remote label binding information, the<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Local PE should
send label mapping to peer PE according to<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;procedures defined
in [RFC4447].<br>
&gt; &gt;<br>
&gt; &gt; What does the item i) mean ? the English is not clear.<br>
&gt; &gt; Why does the PE have to do ii) ?<br>
&gt; &gt;<br>
&gt; &gt; All we really need is a statement on how the c-bit negotiation
state<br>
&gt; &gt; machine can be reset if one end has changed &quot;his mind&quot;
.<br>
&gt; &gt;<br>
&gt; &gt; Can we fix this document before &nbsp;issuing the -00 WG draft
version ?<br>
&gt; &gt;<br>
&gt; &gt; Thanks.<br>
&gt; &gt; Luca<br>
&gt; &gt; &nbsp;<br>
&gt; &gt; --------------------------------------------------------<br>
&gt; &gt; ZTE Information Security Notice: The information contained in
this<br>
&gt; mail is solely property of the sender's organization. This mail <br>
&gt; communication is confidential. Recipients named above are obligated
<br>
&gt; to maintain secrecy and are not permitted to disclose the contents
<br>
&gt; of this communication to others.<br>
&gt; &gt; This email and any files transmitted with it are confidential
and <br>
&gt; intended solely for the use of the individual or entity to whom they<br>
&gt; are addressed. If you have received this email in error please <br>
&gt; notify the originator of the message. Any views expressed in this
<br>
&gt; message are those of the individual sender.<br>
&gt; &gt; This message has been scanned for viruses and Spam by ZTE Anti-Spam
system.<br>
&gt; <br>
&gt; <br>
</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 005890828725784D_=--


From iesg-secretary@ietf.org  Tue Mar  8 10:43:57 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D07183A68EA; Tue,  8 Mar 2011 10:43:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 BS3rX-vCEYx8; Tue,  8 Mar 2011 10:43:57 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C6AD3A6919; Tue,  8 Mar 2011 10:43:56 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110308184356.9141.16409.idtracker@localhost>
Date: Tue, 08 Mar 2011 10:43:56 -0800
Cc: Internet Architecture Board <iab@iab.org>, pwe3 mailing list <pwe3@ietf.org>, pwe3 chair <pwe3-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [PWE3] Protocol Action: 'SONET/SDH Circuit Emulation Service Over Packet	(CEP) Management Information Base (MIB) Using SMIv2' to	Proposed Standard (draft-ietf-pwe3-cep-mib-16.txt)
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 18:43:58 -0000

The IESG has approved the following document:
- 'SONET/SDH Circuit Emulation Service Over Packet (CEP) Management
   Information Base (MIB) Using SMIv2'
  (draft-ietf-pwe3-cep-mib-16.txt) as a Proposed Standard

This document is the product of the Pseudowire Emulation Edge to Edge
Working Group.

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-pwe3-cep-mib/




Technical Summary

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling SONET/SDH
circuits over a Packet Switch Network (PSN).

Working Group Summary

This document has been reviewed by the experts in the PWE3 WG
and there are no outstanding issues.

Protocol Quality

This is a very simple and well written, no protocol issues are
anticipated and no outstanding technical issues exist..

Personnel
Who is the Document Shepherd for this document?

Danny McPherson (danny@tcb.net)

Who is the Responsible Area Director?

Stewart Bryant (stbryant@cisco.com)

From lmartini@cisco.com  Tue Mar  8 12:42:50 2011
Return-Path: <lmartini@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C4763A6359 for <pwe3@core3.amsl.com>; Tue,  8 Mar 2011 12:42:50 -0800 (PST)
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 tz2X4+3C0qOt for <pwe3@core3.amsl.com>; Tue,  8 Mar 2011 12:42:48 -0800 (PST)
Received: from napoleon.monoski.com (napoleon.monoski.com [70.90.113.113]) by core3.amsl.com (Postfix) with ESMTP id A0BCD3A63D3 for <pwe3@ietf.org>; Tue,  8 Mar 2011 12:42:48 -0800 (PST)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id p28KeDP4011709 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 8 Mar 2011 13:40:15 -0700 (MST)
Message-ID: <4D76942D.50700@cisco.com>
Date: Tue, 08 Mar 2011 13:40:13 -0700
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 ThunderBrowse/3.3.5
MIME-Version: 1.0
To: lizhong.jin@zte.com.cn
References: <OFF0D0A956.E47DE79C-ON4825784D.0020F561-8725784D.00589090@zte.com.cn>
In-Reply-To: <OFF0D0A956.E47DE79C-ON4825784D.0020F561-8725784D.00589090@zte.com.cn>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org, andrew.g.malis@verizon.com
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt ( comment )
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 20:42:50 -0000

On 03/08/11 09:06, lizhong.jin@zte.com.cn wrote:
>
> Luca,
> Thank you for the comments. Please see my reply in line.
>
> Regards
> Lizhong
>
>
> Luca Martini <lmartini@cisco.com> wrote on 2011-03-08 03:35:08:
>
> > Sorry for the late response , comments below:
> > Luca
> >
> >
> > On 03/03/11 08:41, lizhong.jin@zte.com.cn wrote:
> > >
> > > Luca,
> > > After discussing with the authors, we decide to add the wait for label
> > > release before sending label request, this wouldn't harm and bring
> > > some secure.
> > >
> > > Then are you OK with the following text?
> > >
> > > When Local PE changes its control word from NOT PREFERRED to PREFERRED
> > > and only if it already received the remote label mapping message with
> > > C-bit=0, additional procedure will be added as follow:
> > > -i Local PE MUST send a label withdraw message to remote PE if it has
> > > previously sent a label mapping, and wait until receiving a label
> > > release from the remote PE.
> > > -ii Local PE MUST send a label request message to remote PE, and wait
> > > until receiving a label mapping message containing the remote PE
> > > configured control word setting.
> > > -iii After receiving remote PE label mapping with control word
> > > setting, Local PE MUST follow procedures defined in [RFC4447] section
> > > 6 when sending it's label mapping message.
> > >
> > Ok the above text is fine.
> > However you need to address the case when the Local PE changes its
> > control word from  PREFERRED to NOT PREFERRED as well.
> [Lizhong] yes, and already addressed in section 3 at the beginning of
> page4 of this draft.
>
> >
> >
> > > Correspondingly, the modified procedure of PE in figure 1 will be as
> > > follows:
> > >
> > > 1. PE2 changes locally configured control word to PREFERRED.
> > > 2. PE2 will then send label withdraw message to PE1.
> > > 3. PE1 MUST send label release in reply to label withdraw message from
> > > PE2.
> > > 4. Upon receipt of Label release message from PE1, PE2 MUST send label
> > > request messages to PE1 although it already received the label mapping
> > > with C-bit=0.
> > > 5. PE1 MUST send label mapping message with C-bit=1 again to PE2
> > > (Note: PE1 MUST send label mapping with locally configured CW
> parameter).
> > > 6. PE2 receives the label mapping from PE1 and updates the remote
> > > label binding information. PE2 MUST wait for PE1 label binding before
> > > sending its label binding with C-bit set, only if it previously had a
> > > label binding with C-bit = 0 from PE1.
> > > 7. PE2 will send label mapping to PE1 with C-bit=1.
> > >
> > No, the above procedure will result in a LDP error and session shutdown.
> > In LDP you  cannot "update" the FEC.  In step 5 PE1 can only send the
> > label mapping message it has previously sent. So PE1 cannot change the
> > C-Bit without first issuing a label withdraw.
> [Lizhong] I don't think such procedure will result in a sesion down
> according to RFC5036. Actually, this is what we want to standardize
> for the PW-FEC processing, to add a way of updating PW-FEC.
you cannot Just "update" a FEC , as it leads to confusion. The receiving
PE will not know how to handle the packet. The label MUST be released ,
and a new label advertised.
> Another way to update PW-FEC is to let PE1 send label withdraw (maybe
> with wrong C-bit) before sending label mapping in step 5, as a reply
> to the label request. But this will lead to additional control message
> load and is not aligned with "receiving label request" behavior in
> A.1.1 in RFC5036, which makes us to abandon it.
>
I do not see how the explanations in appendix A.1.1 in RFC5036 apply to
this problem.

> >
> > > It is to be noted that the above assume that PE1 is configured to
> > > support CW, however in step 5 if PE1 doesn't support CW, PE1 would
> > > send the label mapping message with C-bit =0, this would result in PE2
> > > in step 7 sending a label mapping with C-bit=0 as per [RFC4447] CW
> > > negotiation procedure.
> > >
> > What is needed is some way to send a message to the remote PE that the
> > C-bit negotiation procedure needs to be re-started.
> >
> > Solution 1
> >
> > one way to get this procedure working is to have PE2 release the label
> > mapping previously sent by PE1.
> > If you do this today, most implementations will simply go to a dead
> > state requiring operator intervention.
> > What should happen is that upon receiving the label release , PE1 should
> > withdraw it's label mapping , and reset the c-bit negotiation state
> > machine , and re-advertise the new label mapping restarting the
> > procedure described in rfc4447 from the beginning.
> [Lizhong] This solution has been discussed before on PWE3 mail list
> (http://www.ietf.org/mail-archive/web/pwe3/current/msg11484.html), and
> I also do not prefer this option.
>
No I disagree with Sasha. A label release can be sent anytime , and that
is a local PE decision. Liberal label retention only implies that labels
are usually stored. A label release can be sent for many reasons , like
for example no more local memory available.

>
> >
> > Solution 2
> >
> > Whenever a PE withdraws a FEC mapping , the remote PE resets the C-bit
> > negotiation procedure. If this results in a different C-bit local value
> > then previously advertised , the local PE MUST go though a label
> > withdraw/label release/label advertisement cycle.
> [Lizhong] Solution 2 has already been discussed before on mail list
> (http://www.ietf.org/mail-archive/web/pwe3/current/msg11497.html), and
> also addressed in 00 version of this draft
> (http://tools.ietf.org/html/draft-jin-pwe3-cbit-negotiation-00).
> Unfortunately, the mechanism can not work in MS-PW case.
>
Actually it works fine in the MS-PW case. S-PEs do not care how many
times the label is withdrawn and advertised.
This solution works perfectly fine within all existing LDP rules.

Luca

> >
> >
> > Both solutions above should work within the  LDP rules and are backward
> > compatible. I like solution 2 a bit better.
> >
> > Luca
> >
> > > Thanks
> > > Lizhong
> > >
> > >
> > > ------------send by Luca
> > > Martini-------------------------------------------
> > > Matthew & Andy,
> > >
> > >
> > > Although I support clarifying this procedure , I believe this document
> > > needs some work.
> > > In section 3 for example :
> > >
> > >    When Local PE changes its control word from NOT PREFERRED to
> > >    PREFERRED and only if it already received the remote label mapping
> > >    message with C-bit=0, additional procedure will be added as follow:
> > >
> > >          -i. Local PE sends label withdraw message to the remote if it
> > >              already sends label mapping message, for it has
> changed its
> > >              control word parameter.
> > >
> > >         -ii. Local PE MUST send a label request messages to peer PE to
> > >              get peer's configured control word parameter before
> sending
> > >              new label mapping message to peer PE.
> > >
> > >        -iii. After receiving the new label mapping message from
> peer PE
> > >              and updating the remote label binding information, the
> > >              Local PE should send label mapping to peer PE
> according to
> > >              procedures defined in [RFC4447].
> > >
> > > What does the item i) mean ? the English is not clear.
> > > Why does the PE have to do ii) ?
> > >
> > > All we really need is a statement on how the c-bit negotiation state
> > > machine can be reset if one end has changed "his mind" .
> > >
> > > Can we fix this document before  issuing the -00 WG draft version ?
> > >
> > > Thanks.
> > > Luca
> > >  
> > > --------------------------------------------------------
> > > 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.
> >
> >
>
> --------------------------------------------------------
> 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.


From Alexander.Vainshtein@ecitele.com  Thu Mar 10 23:13:54 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E65A3A68F7; Thu, 10 Mar 2011 23:13:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.037,  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 8IbEh7DiIlSK; Thu, 10 Mar 2011 23:13:49 -0800 (PST)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 52BD03A68C7; Thu, 10 Mar 2011 23:13:47 -0800 (PST)
X-AuditID: 93eaf2e7-b7c1dae000001449-90-4d79cbef525a
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 13.33.05193.FEBC97D4; Fri, 11 Mar 2011 09:14:56 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Fri, 11 Mar 2011 09:15:04 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "lmartini@cisco.com" <lmartini@cisco.com>
Date: Fri, 11 Mar 2011 09:15:03 +0200
Thread-Topic: A brief comment on draft-nadeau-pwe3-vccv-2-01.txt
Thread-Index: AQHL37wKa5PIJp6q3Emc88eiA340sQ==
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB1@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_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB1ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, Andrew Sergeev <Andrew.Sergeev@ecitele.com>, Robert, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, "pwe3@ietf.org" <pwe3@ietf.org>, Rennison <Robert.Rennison@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
Subject: [PWE3] A brief comment on draft-nadeau-pwe3-vccv-2-01.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 07:13:54 -0000

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB1ILPTMAIL02eci_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Tom, Luca and all,
I've read the draft.


The draft defines a new VCCV type for PWs that do not use the CW.
VCCV packets for this type look like following (copy and paste from the dra=
ft):

0                   1                   2                   3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                              GAL                              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                            PW Label                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 1|Version|   Reserved    |  Associated Channel Type      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
~                        VCCV Message Body                      ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+



The draft further says that "The PW Label must set the TTL field to 1.

In the case of multi-segment pseudo-wires, the PW Label TTL MUST be set

to the correct value to reach the intended destination PE as described
in [RFC6073]".

The proposed format seems to stretch to the limit the somewhat vague waiver=
 in RFC 5586 (highlighted in the quoted text):

<quote>

   In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
   Concatenated Segments of LSPs, and with Sections, and MUST NOT be
   used with PWs.  It MUST always be at the bottom of the label stack
   (i.e., S bit set to 1).  However, in other MPLS environments, this
   document places no restrictions on where the GAL may appear within
   the label stack or its use with PWs.  Where the GAL is at the bottom
   of the label stack (i.e., S bit set to 1), then it MUST always be
   followed by an ACH.
<end quote>



This format also seems to contradict draft-ietf-pwe3-mpls-tp-gal-in-pw (and=
, IMHO, makes it completely unnecessary).



Please note that:

 1.  The function of GAL in this case seems to be limited to forwarding the=
 packet to a control entity at the tail-end of the tunnel.
 2.  RFC 5586 does not define how the packets with GAL exposed are forwarde=
d (if at all) if GAL is exposed but is not at the bottom of the label stack=
.



Hence my comments:

 1.  The draft must explicitly define how the packets with the GAL exposed =
in the Label Stack are forwarded (similar to what has been done for the Rou=
ter Alert label in RFC 3032), and must state that it updates RFC 5586 in th=
is regard. Without such a change, VCCV Type 4 would not be applicable MS-PW=
s.
 2.  The ACH type for static PW status messages (as defined in draft-ietf-p=
we3-static-pw-status) should be added to the explicit lists of ACH types su=
pported with the new VCCV type. Such a list appears in Section 3 of the dra=
ft. Alternatively, explicit specification of allowed ACH types could be rem=
oved from the draft.

Regards,

     Sasha









--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB1ILPTMAIL02eci_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style id=3D"owaTempEditStyle"></style><style title=3D"owaParaStyle"><!--P =
{
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi=3D"x">
<p><font face=3D"Courier New">Tom, Luca and all,<br>
I've read the draft.<br>
<br>
<br>
The draft defines a new VCCV type for PWs that do not use the CW.<br>
VCCV packets for this type look like following (copy and paste from the dra=
ft):<br>
<br>
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<br>
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br>
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<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;&nbsp;&nbsp; GAL&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; |<br>
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<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; PW Label&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; |<br>
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<br>
|0 0 0 1|Version|&nbsp;&nbsp; Reserved&nbsp;&nbsp;&nbsp; |&nbsp; Associated=
 Channel Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<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;&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; |=
<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; VCCV Messa=
ge Body&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<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;&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; |=
<br>
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;</font></p>
<p><font face=3D"courier new"></font>&nbsp;</p>
<p><font face=3D"courier new">The draft further says that &quot;The PW Labe=
l must set the TTL field to 1.
</font></p>
<p><font face=3D"courier new">In the case of multi-segment pseudo-wires, th=
e PW Label TTL MUST
</font><font face=3D"courier new">be set </font></p>
<p><font face=3D"courier new">to the correct value to reach the intended de=
stination PE as described
<br>
in [RFC6073]&quot;.<br>
</font></p>
<p><font face=3D"courier new"><font face=3D"courier new">The proposed&nbsp;=
format seems to stretch to the limit the somewhat vague waiver in RFC 5586 =
(highlighted in the quoted text):</font></font></p>
<p><font face=3D"courier new">&lt;quote&gt;</font></p>
<p><font face=3D"courier new"><font face=3D"courier new">&nbsp;&nbsp; In MP=
LS-TP, the GAL MUST be used with packets on a G-ACh<a></a><a></a> on LSPs,<=
br>
&nbsp;&nbsp; Concatenated Segments of LSPs, and with Sections, and MUST NOT=
 be<br>
&nbsp;&nbsp; used with PWs.&nbsp; It MUST always be at the bottom of the la=
bel stack<br>
&nbsp;&nbsp; (i.e., S bit set to 1).&nbsp; <font style=3D"BACKGROUND-COLOR:=
 #ffff00">However, in other MPLS environments, this<br>
&nbsp;&nbsp; document places no restrictions on where the GAL may appear wi=
thin<br>
&nbsp;&nbsp; the label stack or its use with PWs.</font>&nbsp; Where the GA=
L is at the bottom<br>
&nbsp;&nbsp; of the label stack (i.e., S bit set to 1), then it MUST always=
 be<br>
&nbsp;&nbsp; followed by an ACH.<br>
&lt;end quote&gt;</font></font></p>
<p><font face=3D"courier new"><font face=3D"courier new"></font></font>&nbs=
p;</p>
<p><font face=3D"Courier New">This format also seems to contradict draft-ie=
tf-pwe3-mpls-tp-gal-in-pw (and, IMHO, makes it completely unnecessary).<spa=
n class=3D"Apple-style-span" style=3D"WORD-SPACING: 0px; FONT: medium 'Time=
s New Roman'; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WH=
ITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orpha=
ns: 2; widows: 2; -webkit-border-horizontal-spacing: 0px; -webkit-border-ve=
rtical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text=
-size-adjust: auto; -webkit-text-stroke-width: 0px"><span class=3D"Apple-st=
yle-span" style=3D"FONT-SIZE: 13px; LINE-HEIGHT: 16px; FONT-FAMILY: arial, =
helvetica, clean, sans-serif; -webkit-border-horizontal-spacing: 2px; -webk=
it-border-vertical-spacing: 2px"></p>
</span></span></font>
<p>&nbsp;</p>
<p><font face=3D"Courier New">Please note that:</font></p>
<ol style=3D"FONT-SIZE: 12pt; FONT-FAMILY: Courier New">
<li><font face=3D"courier new"><font face=3D"courier new">The function of G=
AL in this case seems to be limited to forwarding the packet to a control e=
ntity at the tail-end of the tunnel.
</font></font></li><li><font face=3D"courier new"><font face=3D"courier new=
">RFC 5586 does not define&nbsp;how the&nbsp;packets with GAL exposed are f=
orwarded (if at all) if GAL is exposed but is not at the bottom of the labe=
l stack.
</font></font></li></ol>
<p>&nbsp;</p>
<p><font face=3D"Courier New">Hence my comments:</font></p>
<ol style=3D"FONT-SIZE: 12pt; FONT-FAMILY: Courier New">
<li>The draft must explicitly define how the packets with the GAL exposed i=
n the Label Stack are forwarded (similar to what has been done for the Rout=
er Alert label in RFC 3032), and must state that it updates RFC 5586 in thi=
s regard. Without such a change,
 VCCV Type 4 would not be applicable MS-PWs. </li><li><font face=3D"courier=
 new">The ACH type for static PW status messages (as defined in draft-ietf-=
pwe3-static-pw-status) should be added to the explicit lists of ACH types s=
upported with the new VCCV type. Such a list appears in Section 3 of the dr=
aft. Alternatively,
 explicit specification&nbsp;of<a></a> allowed ACH types could be removed f=
rom the draft.</font></li></ol>
<p><font face=3D"courier new">Regards,</font></p>
<p><font face=3D"courier new">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</font></p>
<p><font face=3D"courier new"></font>&nbsp;</p>
<p><font face=3D"courier new"></font>&nbsp;</p>
<p><font face=3D"courier new"></font>&nbsp;</p>
<p><font face=3D"courier new"></font><font face=3D"courier new">&nbsp;</p>
</font>
</body>
</html>

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB1ILPTMAIL02eci_--

From lmartini@cisco.com  Fri Mar 11 05:37:04 2011
Return-Path: <lmartini@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 764153A6BE8; Fri, 11 Mar 2011 05:37:04 -0800 (PST)
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 wLUKklh89MY5; Fri, 11 Mar 2011 05:37:03 -0800 (PST)
Received: from napoleon.monoski.com (napoleon.monoski.com [70.90.113.113]) by core3.amsl.com (Postfix) with ESMTP id 13A103A69AE; Fri, 11 Mar 2011 05:37:03 -0800 (PST)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id p2BDVbhM014634 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 11 Mar 2011 06:31:38 -0700 (MST)
Message-ID: <4D7A2439.6010508@cisco.com>
Date: Fri, 11 Mar 2011 06:31:37 -0700
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 ThunderBrowse/3.3.5
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com>	<4D5E9442.3030101@cisco.com> <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com>
In-Reply-To: <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: lihan@chinamobile.com, mpls@ietf.org, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, mpls-tp@ietf.org
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 13:37:04 -0000

Greg ,
Some

On 02/18/11 11:15, Greg Mirsky wrote:
> Dear Luca,
> I see at least two issues:
>
>     * use of GAL for PW, in my view, is another VCCV CC type that has
>       to be negotiated as described in RFC 5085.
>
These are valid points, but this document in question does not define,
not discussed VCCV.
We have since posted a draft that proposes a new VCCV mode , and we
welcome comments regarding that document.
(draft-nadeau-pwe3-vccv-2-01.txt)

>     * use of GAL creates ambiguous situation when PW CW is used. The
>       benefit from extending GAL in PW, as I see, is for PWs that are
>       not required to use PW CW. That might be a good enough reason to
>       update RFC 5586 as proposed in the document but we must address
>       use cases of GAL in PWs that require presence PW CW. If we
>       prohibit or even discourage use of GAL for these PWs that have
>       PW VCCV as native Associated Channel, then architecture of ACh
>       for MPLS-TP PW not simplified as result of adopting the proposal.
>
> Regard
Greg,
The GAL is basically a notifier that the packet following the end of the
MPLS label stack, is explicitly defined as a G-ACH format.
Normally the packet would be decoded as an IP packet , unless the last
label on the stack indicated otherwise.

The GAL can certainly be applied  to a PW OAM packet on a PW that uses
the CW, and this document does not define that , nor restricts it.

The scope of this document is limited to removing an unnecessary
restriction in rfc5586, hence  this comment not applicable to this document.

Thanks.
Luca

> s,
> Greg
>
> On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com
> <mailto:lmartini@cisco.com>> wrote:
>
>     Greg,
>
>     Sorry, but I do not remember the point you mention.
>     Can you explain again here ?
>     Thanks.
>     Luca
>
>
>     On 02/17/11 23:47, Greg Mirsky wrote:
>     > Dear Authors and All,
>     > prior to the meeting in Bejing and acceptance of this proposal as WG
>     > document Luca and I agreed that use of GAL with PW VCCV presents a
>     > problem.
>     > I was not attending the IETF-79, nor I found discussion of this
>     issue
>     > in the minutes. I think that this issue should be specified,
>     > explained. In my view, this document updates not only RFC 5586
>     > but RFC 5085 too.
>     >
>     > Regards,
>     > Greg
>     >
>     > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>     >
>     > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
>     <lmartini@cisco.com <mailto:lmartini@cisco.com>
>     > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>> wrote:
>     >
>     >     Greg,
>     >
>     >     You are correct , the proposed update does not propose any
>     changes
>     >     to VCCV.
>     >     However the problem with vccv is not as simple as to ask for
>     a new
>     >     code point from IANA.
>     >     Given the good amount of discussion on this point, we should
>     >     probably have a discussion in Beijing.
>     >
>     >     Luca
>     >
>     >
>     >
>     >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
>     >>     Dear Authors,
>     >>     I think that proposed update of the Section 4.2. RFC 5586
>     makes it possible
>     >>     to use GAL on MPLS-TP PW that uses Control Word. I consider
>     it to be
>     >>     conflict between PW VCCV CC types because use of GAL is not
>     negotiated
>     >>     through PW VCCV negotiation. To avoid such situation I propose:
>     >>
>     >>        - in Section 5 request IANA to assign new CC Type "MPLS
>     Generic
>     >>        Associated Channel Label"
>     >>        - assign precedence to new CC Type that affects Section
>     7 RFC 5085
>     >>
>     >>     Regards,
>     >>     Greg
>     >>
>     >>
>     >>
>     >>     _______________________________________________
>     >>     mpls mailing list
>     >>     mpls@ietf.org <mailto:mpls@ietf.org> <mailto: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
>
>



From gregimirsky@gmail.com  Fri Mar 11 11:13:08 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 438603A6867; Fri, 11 Mar 2011 11:13:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level: 
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[AWL=-0.250, 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 G1G5tZuHkifu; Fri, 11 Mar 2011 11:13:07 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 808143A692A; Fri, 11 Mar 2011 11:13:06 -0800 (PST)
Received: by vxg33 with SMTP id 33so3436782vxg.31 for <multiple recipients>; Fri, 11 Mar 2011 11:14:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hGvMLrqnfDT5Md1LdED+ehD8g+nQWAU3R3U/eBsRAcs=; b=GdG4thn6MIrO/mPJX1qjVlh6rNDi5CGVW9g12aQfnvIukUeyEUDv8iXCyeRShbPN3g C8nutqTdt9YCQS/Vu7boh3ZVaRqyeREOeEFHKJSw6AJTbckzdSWzzusxaQHlCWdRu4WP 3xUmKdIodPGXO6GYCtsPt1cKrCjf/LKiclgk8=
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=pJh0kPAvixjbHbsmiMwq5URY9OlMIi5TdLUX2zLYa4WhHo/R/bFz98ifeKo1VaKkD3 Ii5JbmgLBMlOK3XNWgdGC8Y2sM4Pas/+hBgJPTZdYKn0bXiKSATdUE+GBp+6DMbKZGsn CR+IHdU9YC2XlhMBueJ3eNHqnML8SSdSor5bE=
MIME-Version: 1.0
Received: by 10.52.159.3 with SMTP id wy3mr14155643vdb.289.1299870865619; Fri, 11 Mar 2011 11:14:25 -0800 (PST)
Received: by 10.52.169.35 with HTTP; Fri, 11 Mar 2011 11:14:25 -0800 (PST)
In-Reply-To: <4D7A2439.6010508@cisco.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com> <4D5E9442.3030101@cisco.com> <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com> <4D7A2439.6010508@cisco.com>
Date: Fri, 11 Mar 2011 11:14:25 -0800
Message-ID: <AANLkTim+hqNFHi9xwuzG5_2qoKztEn9SJA9TDh-S-XUo@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Luca Martini <lmartini@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec53f97973306bd049e39c525
Cc: lihan@chinamobile.com, mpls@ietf.org, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, mpls-tp@ietf.org
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 19:13:08 -0000

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

Dear Luca,
thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. I'll
send my comments to it in a separate e-mail.
I'll have to miss another opportunity to discuss your proposal in a meeting.
Please add my comments below to my earlier expressed WG LC comments:

   - the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that
   addresses applicability of GAL in PW VCCV, e.g. solution proposed in
   draft-nadeau-pwe3-vccv-2-01;
   - the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such dependency
   and refer to any existing proposal;
   - I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced
   in lock with document that addresses use of GAL in PW VCCV.

Regards,
Greg

On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini <lmartini@cisco.com> wrote:

> Greg ,
> Some
>
> On 02/18/11 11:15, Greg Mirsky wrote:
> > Dear Luca,
> > I see at least two issues:
> >
> >     * use of GAL for PW, in my view, is another VCCV CC type that has
> >       to be negotiated as described in RFC 5085.
> >
> These are valid points, but this document in question does not define,
> not discussed VCCV.
> We have since posted a draft that proposes a new VCCV mode , and we
> welcome comments regarding that document.
> (draft-nadeau-pwe3-vccv-2-01.txt)
>
> >     * use of GAL creates ambiguous situation when PW CW is used. The
> >       benefit from extending GAL in PW, as I see, is for PWs that are
> >       not required to use PW CW. That might be a good enough reason to
> >       update RFC 5586 as proposed in the document but we must address
> >       use cases of GAL in PWs that require presence PW CW. If we
> >       prohibit or even discourage use of GAL for these PWs that have
> >       PW VCCV as native Associated Channel, then architecture of ACh
> >       for MPLS-TP PW not simplified as result of adopting the proposal.
> >
> > Regard
> Greg,
> The GAL is basically a notifier that the packet following the end of the
> MPLS label stack, is explicitly defined as a G-ACH format.
> Normally the packet would be decoded as an IP packet , unless the last
> label on the stack indicated otherwise.
>
> The GAL can certainly be applied  to a PW OAM packet on a PW that uses
> the CW, and this document does not define that , nor restricts it.
>
> The scope of this document is limited to removing an unnecessary
> restriction in rfc5586, hence  this comment not applicable to this
> document.
>
> Thanks.
> Luca
>
> > s,
> > Greg
> >
> > On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com
> > <mailto:lmartini@cisco.com>> wrote:
> >
> >     Greg,
> >
> >     Sorry, but I do not remember the point you mention.
> >     Can you explain again here ?
> >     Thanks.
> >     Luca
> >
> >
> >     On 02/17/11 23:47, Greg Mirsky wrote:
> >     > Dear Authors and All,
> >     > prior to the meeting in Bejing and acceptance of this proposal as
> WG
> >     > document Luca and I agreed that use of GAL with PW VCCV presents a
> >     > problem.
> >     > I was not attending the IETF-79, nor I found discussion of this
> >     issue
> >     > in the minutes. I think that this issue should be specified,
> >     > explained. In my view, this document updates not only RFC 5586
> >     > but RFC 5085 too.
> >     >
> >     > Regards,
> >     > Greg
> >     >
> >     > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> >     >
> >     > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
> >     <lmartini@cisco.com <mailto:lmartini@cisco.com>
> >     > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>> wrote:
> >     >
> >     >     Greg,
> >     >
> >     >     You are correct , the proposed update does not propose any
> >     changes
> >     >     to VCCV.
> >     >     However the problem with vccv is not as simple as to ask for
> >     a new
> >     >     code point from IANA.
> >     >     Given the good amount of discussion on this point, we should
> >     >     probably have a discussion in Beijing.
> >     >
> >     >     Luca
> >     >
> >     >
> >     >
> >     >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
> >     >>     Dear Authors,
> >     >>     I think that proposed update of the Section 4.2. RFC 5586
> >     makes it possible
> >     >>     to use GAL on MPLS-TP PW that uses Control Word. I consider
> >     it to be
> >     >>     conflict between PW VCCV CC types because use of GAL is not
> >     negotiated
> >     >>     through PW VCCV negotiation. To avoid such situation I
> propose:
> >     >>
> >     >>        - in Section 5 request IANA to assign new CC Type "MPLS
> >     Generic
> >     >>        Associated Channel Label"
> >     >>        - assign precedence to new CC Type that affects Section
> >     7 RFC 5085
> >     >>
> >     >>     Regards,
> >     >>     Greg
> >     >>
> >     >>
> >     >>
> >     >>     _______________________________________________
> >     >>     mpls mailing list
> >     >>     mpls@ietf.org <mailto:mpls@ietf.org> <mailto: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
> >
> >
>
>
>

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

Dear Luca,<br>thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my atte=
ntion. I&#39;ll send my comments to it in a separate e-mail.<br>I&#39;ll ha=
ve to miss another opportunity to discuss your proposal in a meeting. Pleas=
e add my comments below to my earlier expressed WG LC comments:<br>
<ul><li>the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that=
 addresses applicability of GAL in PW VCCV, e.g. solution proposed in draft=
-nadeau-pwe3-vccv-2-01;</li><li>the draft-lm-pwe3-mpls-tp-gal-in-pw-00 need=
s to mention such dependency and refer to any existing proposal;</li>
<li>I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced i=
n lock with document that addresses use of GAL in PW VCCV.</li></ul>Regards=
,<br>Greg<br><br><div class=3D"gmail_quote">On Fri, Mar 11, 2011 at 5:31 AM=
, Luca Martini <span dir=3D"ltr">&lt;<a href=3D"mailto:lmartini@cisco.com">=
lmartini@cisco.com</a>&gt;</span> wrote:<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;">Greg ,<br>
Some<br>
<div class=3D"im"><br>
On 02/18/11 11:15, Greg Mirsky wrote:<br>
&gt; Dear Luca,<br>
&gt; I see at least two issues:<br>
&gt;<br>
&gt; =A0 =A0 * use of GAL for PW, in my view, is another VCCV CC type that =
has<br>
&gt; =A0 =A0 =A0 to be negotiated as described in RFC 5085.<br>
&gt;<br>
</div>These are valid points, but this document in question does not define=
,<br>
not discussed VCCV.<br>
We have since posted a draft that proposes a new VCCV mode , and we<br>
welcome comments regarding that document.<br>
(draft-nadeau-pwe3-vccv-2-01.txt)<br>
<br>
&gt; =A0 =A0 * use of GAL creates ambiguous situation when PW CW is used. T=
he<br>
<div class=3D"im">&gt; =A0 =A0 =A0 benefit from extending GAL in PW, as I s=
ee, is for PWs that are<br>
&gt; =A0 =A0 =A0 not required to use PW CW. That might be a good enough rea=
son to<br>
&gt; =A0 =A0 =A0 update RFC 5586 as proposed in the document but we must ad=
dress<br>
&gt; =A0 =A0 =A0 use cases of GAL in PWs that require presence PW CW. If we=
<br>
&gt; =A0 =A0 =A0 prohibit or even discourage use of GAL for these PWs that =
have<br>
&gt; =A0 =A0 =A0 PW VCCV as native Associated Channel, then architecture of=
 ACh<br>
&gt; =A0 =A0 =A0 for MPLS-TP PW not simplified as result of adopting the pr=
oposal.<br>
&gt;<br>
&gt; Regard<br>
</div>Greg,<br>
The GAL is basically a notifier that the packet following the end of the<br=
>
MPLS label stack, is explicitly defined as a G-ACH format.<br>
Normally the packet would be decoded as an IP packet , unless the last<br>
label on the stack indicated otherwise.<br>
<br>
The GAL can certainly be applied =A0to a PW OAM packet on a PW that uses<br=
>
the CW, and this document does not define that , nor restricts it.<br>
<br>
The scope of this document is limited to removing an unnecessary<br>
restriction in rfc5586, hence =A0this comment not applicable to this docume=
nt.<br>
<br>
Thanks.<br>
Luca<br>
<div class=3D"im"><br>
&gt; s,<br>
&gt; Greg<br>
&gt;<br>
&gt; On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini &lt;<a href=3D"mailto:lm=
artini@cisco.com">lmartini@cisco.com</a><br>
</div><div class=3D"im">&gt; &lt;mailto:<a href=3D"mailto:lmartini@cisco.co=
m">lmartini@cisco.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt; =A0 =A0 Greg,<br>
&gt;<br>
&gt; =A0 =A0 Sorry, but I do not remember the point you mention.<br>
&gt; =A0 =A0 Can you explain again here ?<br>
&gt; =A0 =A0 Thanks.<br>
&gt; =A0 =A0 Luca<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 On 02/17/11 23:47, Greg Mirsky wrote:<br>
&gt; =A0 =A0 &gt; Dear Authors and All,<br>
&gt; =A0 =A0 &gt; prior to the meeting in Bejing and acceptance of this pro=
posal as WG<br>
&gt; =A0 =A0 &gt; document Luca and I agreed that use of GAL with PW VCCV p=
resents a<br>
&gt; =A0 =A0 &gt; problem.<br>
&gt; =A0 =A0 &gt; I was not attending the IETF-79, nor I found discussion o=
f this<br>
&gt; =A0 =A0 issue<br>
&gt; =A0 =A0 &gt; in the minutes. I think that this issue should be specifi=
ed,<br>
&gt; =A0 =A0 &gt; explained. In my view, this document updates not only RFC=
 5586<br>
&gt; =A0 =A0 &gt; but RFC 5085 too.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; Regards,<br>
&gt; =A0 =A0 &gt; Greg<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini<br>
&gt; =A0 =A0 &lt;<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</=
a> &lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a>&=
gt;<br>
</div><div><div></div><div class=3D"h5">&gt; =A0 =A0 &gt; &lt;mailto:<a hre=
f=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a> &lt;mailto:<a href=
=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;&gt;&gt; wrote:<br=
>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; =A0 =A0 Greg,<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; =A0 =A0 You are correct , the proposed update does not pr=
opose any<br>
&gt; =A0 =A0 changes<br>
&gt; =A0 =A0 &gt; =A0 =A0 to VCCV.<br>
&gt; =A0 =A0 &gt; =A0 =A0 However the problem with vccv is not as simple as=
 to ask for<br>
&gt; =A0 =A0 a new<br>
&gt; =A0 =A0 &gt; =A0 =A0 code point from IANA.<br>
&gt; =A0 =A0 &gt; =A0 =A0 Given the good amount of discussion on this point=
, we should<br>
&gt; =A0 =A0 &gt; =A0 =A0 probably have a discussion in Beijing.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; =A0 =A0 Luca<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; =A0 =A0 On 10/29/2010 05:07 PM, Greg Mirsky wrote:<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 Dear Authors,<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 I think that proposed update of the Section 4=
.2. RFC 5586<br>
&gt; =A0 =A0 makes it possible<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 to use GAL on MPLS-TP PW that uses Control Wo=
rd. I consider<br>
&gt; =A0 =A0 it to be<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 conflict between PW VCCV CC types because use=
 of GAL is not<br>
&gt; =A0 =A0 negotiated<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 through PW VCCV negotiation. To avoid such si=
tuation I propose:<br>
&gt; =A0 =A0 &gt;&gt;<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 =A0 =A0- in Section 5 request IANA to assign =
new CC Type &quot;MPLS<br>
&gt; =A0 =A0 Generic<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 =A0 =A0Associated Channel Label&quot;<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 =A0 =A0- assign precedence to new CC Type tha=
t affects Section<br>
&gt; =A0 =A0 7 RFC 5085<br>
&gt; =A0 =A0 &gt;&gt;<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 Regards,<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 Greg<br>
&gt; =A0 =A0 &gt;&gt;<br>
&gt; =A0 =A0 &gt;&gt;<br>
&gt; =A0 =A0 &gt;&gt;<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 _____________________________________________=
__<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 mpls mailing list<br>
</div></div>&gt; =A0 =A0 &gt;&gt; =A0 =A0 <a href=3D"mailto:mpls@ietf.org">=
mpls@ietf.org</a> &lt;mailto:<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org=
</a>&gt; &lt;mailto:<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<div><div></div><div class=3D"h5">&gt; =A0 =A0 &lt;mailto:<a href=3D"mailto=
:mpls@ietf.org">mpls@ietf.org</a>&gt;&gt;<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 <a href=3D"https://www.ietf.org/mailman/listi=
nfo/mpls" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><=
br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; _______________________________________________<br>
&gt; =A0 =A0 &gt; mpls mailing list<br>
&gt; =A0 =A0 &gt; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> &lt;ma=
ilto:<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<br>
&gt; =A0 =A0 &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mpls" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>
&gt;<br>
&gt;<br>
<br>
<br>
</div></div></blockquote></div><br>

--bcaec53f97973306bd049e39c525--

From Alexander.Vainshtein@ecitele.com  Fri Mar 11 11:20:46 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 275B23A6C7A; Fri, 11 Mar 2011 11:20:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.035,  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 9N6N97j9WH5O; Fri, 11 Mar 2011 11:20:36 -0800 (PST)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 8D7473A698D; Fri, 11 Mar 2011 11:20:34 -0800 (PST)
X-AuditID: 93eaf2e7-b7c1dae000001449-47-4d7a7648cc71
Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 96.2E.05193.8467A7D4; Fri, 11 Mar 2011 21:21:44 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Fri, 11 Mar 2011 21:21:52 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Greg Mirsky <gregimirsky@gmail.com>, Luca Martini <lmartini@cisco.com>
Date: Fri, 11 Mar 2011 21:21:49 +0200
Thread-Topic: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Thread-Index: AcvgIJCjINO9d7bvQ8uZXoqo8NcncgAAI1aw
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6FBBDD332@ILPTMAIL02.ecitele.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com> <4D5E9442.3030101@cisco.com> <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com> <4D7A2439.6010508@cisco.com> <AANLkTim+hqNFHi9xwuzG5_2qoKztEn9SJA9TDh-S-XUo@mail.gmail.com>
In-Reply-To: <AANLkTim+hqNFHi9xwuzG5_2qoKztEn9SJA9TDh-S-XUo@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_A3C5DF08D38B6049839A6F553B331C76D6FBBDD332ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "lihan@chinamobile.com" <lihan@chinamobile.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 19:20:46 -0000

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

Greg, Luca,
As I've already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO it m=
akes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.

My 2c,
     Sasha

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Gre=
g Mirsky
Sent: Friday, March 11, 2011 9:14 PM
To: Luca Martini
Cc: lihan@chinamobile.com; mpls@ietf.org; pwe3; HUANG Feng F; mpls-tp@ietf.=
org
Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

Dear Luca,
thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. I'll se=
nd my comments to it in a separate e-mail.
I'll have to miss another opportunity to discuss your proposal in a meeting=
. Please add my comments below to my earlier expressed WG LC comments:

 *   the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that ad=
dresses applicability of GAL in PW VCCV, e.g. solution proposed in draft-na=
deau-pwe3-vccv-2-01;
 *   the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such dependenc=
y and refer to any existing proposal;
 *   I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced =
in lock with document that addresses use of GAL in PW VCCV.
Regards,
Greg
On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini <lmartini@cisco.com<mailto:lm=
artini@cisco.com>> wrote:
Greg ,
Some

On 02/18/11 11:15, Greg Mirsky wrote:
> Dear Luca,
> I see at least two issues:
>
>     * use of GAL for PW, in my view, is another VCCV CC type that has
>       to be negotiated as described in RFC 5085.
>
These are valid points, but this document in question does not define,
not discussed VCCV.
We have since posted a draft that proposes a new VCCV mode , and we
welcome comments regarding that document.
(draft-nadeau-pwe3-vccv-2-01.txt)

>     * use of GAL creates ambiguous situation when PW CW is used. The
>       benefit from extending GAL in PW, as I see, is for PWs that are
>       not required to use PW CW. That might be a good enough reason to
>       update RFC 5586 as proposed in the document but we must address
>       use cases of GAL in PWs that require presence PW CW. If we
>       prohibit or even discourage use of GAL for these PWs that have
>       PW VCCV as native Associated Channel, then architecture of ACh
>       for MPLS-TP PW not simplified as result of adopting the proposal.
>
> Regard
Greg,
The GAL is basically a notifier that the packet following the end of the
MPLS label stack, is explicitly defined as a G-ACH format.
Normally the packet would be decoded as an IP packet , unless the last
label on the stack indicated otherwise.

The GAL can certainly be applied  to a PW OAM packet on a PW that uses
the CW, and this document does not define that , nor restricts it.

The scope of this document is limited to removing an unnecessary
restriction in rfc5586, hence  this comment not applicable to this document=
.

Thanks.
Luca

> s,
> Greg
>
> On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com<mailto:=
lmartini@cisco.com>
> <mailto:lmartini@cisco.com<mailto:lmartini@cisco.com>>> wrote:
>
>     Greg,
>
>     Sorry, but I do not remember the point you mention.
>     Can you explain again here ?
>     Thanks.
>     Luca
>
>
>     On 02/17/11 23:47, Greg Mirsky wrote:
>     > Dear Authors and All,
>     > prior to the meeting in Bejing and acceptance of this proposal as W=
G
>     > document Luca and I agreed that use of GAL with PW VCCV presents a
>     > problem.
>     > I was not attending the IETF-79, nor I found discussion of this
>     issue
>     > in the minutes. I think that this issue should be specified,
>     > explained. In my view, this document updates not only RFC 5586
>     > but RFC 5085 too.
>     >
>     > Regards,
>     > Greg
>     >
>     > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>     >
>     > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
>     <lmartini@cisco.com<mailto:lmartini@cisco.com> <mailto:lmartini@cisco=
.com<mailto:lmartini@cisco.com>>
>     > <mailto:lmartini@cisco.com<mailto:lmartini@cisco.com> <mailto:lmart=
ini@cisco.com<mailto:lmartini@cisco.com>>>> wrote:
>     >
>     >     Greg,
>     >
>     >     You are correct , the proposed update does not propose any
>     changes
>     >     to VCCV.
>     >     However the problem with vccv is not as simple as to ask for
>     a new
>     >     code point from IANA.
>     >     Given the good amount of discussion on this point, we should
>     >     probably have a discussion in Beijing.
>     >
>     >     Luca
>     >
>     >
>     >
>     >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
>     >>     Dear Authors,
>     >>     I think that proposed update of the Section 4.2. RFC 5586
>     makes it possible
>     >>     to use GAL on MPLS-TP PW that uses Control Word. I consider
>     it to be
>     >>     conflict between PW VCCV CC types because use of GAL is not
>     negotiated
>     >>     through PW VCCV negotiation. To avoid such situation I propose=
:
>     >>
>     >>        - in Section 5 request IANA to assign new CC Type "MPLS
>     Generic
>     >>        Associated Channel Label"
>     >>        - assign precedence to new CC Type that affects Section
>     7 RFC 5085
>     >>
>     >>     Regards,
>     >>     Greg
>     >>
>     >>
>     >>
>     >>     _______________________________________________
>     >>     mpls mailing list
>     >>     mpls@ietf.org<mailto:mpls@ietf.org> <mailto:mpls@ietf.org<mail=
to:mpls@ietf.org>> <mailto:mpls@ietf.org<mailto:mpls@ietf.org>
>     <mailto:mpls@ietf.org<mailto:mpls@ietf.org>>>
>     >>     https://www.ietf.org/mailman/listinfo/mpls
>     >
>     >
>     >
>     > _______________________________________________
>     > mpls mailing list
>     > mpls@ietf.org<mailto:mpls@ietf.org> <mailto:mpls@ietf.org<mailto:mp=
ls@ietf.org>>
>     > https://www.ietf.org/mailman/listinfo/mpls
>
>



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1800680213;
	mso-list-template-ids:-512447670;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Greg, Luc=
a,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>As I&#8217;ve already s=
tated in my comment on draft-nadeau-pwe3-vccv-2, IMHO it makes draft-lm-pwe=
3-mpls-tp-gal-in-pw completely useless.<o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#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'>My 2=
c,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp=
; Sasha<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:0c=
m 0cm 0cm 4.0pt'><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"'> mpls-bounces@ietf.=
org [mailto:mpls-bounces@ietf.org] <b>On Behalf Of </b>Greg Mirsky<br><b>Se=
nt:</b> Friday, March 11, 2011 9:14 PM<br><b>To:</b> Luca Martini<br><b>Cc:=
</b> lihan@chinamobile.com; mpls@ietf.org; pwe3; HUANG Feng F; mpls-tp@ietf=
.org<br><b>Subject:</b> Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00=
.txt<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p><p class=3DMsoNormal>Dear Luca,<br>thank you for bringing draft-nadeau=
-pwe3-vccv-2-01 to my attention. I'll send my comments to it in a separate =
e-mail.<br>I'll have to miss another opportunity to discuss your proposal i=
n a meeting. Please add my comments below to my earlier expressed WG LC com=
ments:<o:p></o:p></p><ul type=3Ddisc><li class=3DMsoNormal style=3D'mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>the dr=
aft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that addresses app=
licability of GAL in PW VCCV, e.g. solution proposed in draft-nadeau-pwe3-v=
ccv-2-01;<o:p></o:p></li><li class=3DMsoNormal style=3D'mso-margin-top-alt:=
auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>the draft-lm-pwe3-=
mpls-tp-gal-in-pw-00 needs to mention such dependency and refer to any exis=
ting proposal;<o:p></o:p></li><li class=3DMsoNormal style=3D'mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>I believe tha=
t the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced in lock with docum=
ent that addresses use of GAL in PW VCCV.<o:p></o:p></li></ul><p class=3DMs=
oNormal style=3D'margin-bottom:12.0pt'>Regards,<br>Greg<o:p></o:p></p><div>=
<p class=3DMsoNormal>On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini &lt;<a h=
ref=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt; wrote:<o:p></o=
:p></p><p class=3DMsoNormal>Greg ,<br>Some<o:p></o:p></p><div><p class=3DMs=
oNormal><br>On 02/18/11 11:15, Greg Mirsky wrote:<br>&gt; Dear Luca,<br>&gt=
; I see at least two issues:<br>&gt;<br>&gt; &nbsp; &nbsp; * use of GAL for=
 PW, in my view, is another VCCV CC type that has<br>&gt; &nbsp; &nbsp; &nb=
sp; to be negotiated as described in RFC 5085.<br>&gt;<o:p></o:p></p></div>=
<p class=3DMsoNormal>These are valid points, but this document in question =
does not define,<br>not discussed VCCV.<br>We have since posted a draft tha=
t proposes a new VCCV mode , and we<br>welcome comments regarding that docu=
ment.<br>(draft-nadeau-pwe3-vccv-2-01.txt)<br><br>&gt; &nbsp; &nbsp; * use =
of GAL creates ambiguous situation when PW CW is used. The<o:p></o:p></p><d=
iv><p class=3DMsoNormal>&gt; &nbsp; &nbsp; &nbsp; benefit from extending GA=
L in PW, as I see, is for PWs that are<br>&gt; &nbsp; &nbsp; &nbsp; not req=
uired to use PW CW. That might be a good enough reason to<br>&gt; &nbsp; &n=
bsp; &nbsp; update RFC 5586 as proposed in the document but we must address=
<br>&gt; &nbsp; &nbsp; &nbsp; use cases of GAL in PWs that require presence=
 PW CW. If we<br>&gt; &nbsp; &nbsp; &nbsp; prohibit or even discourage use =
of GAL for these PWs that have<br>&gt; &nbsp; &nbsp; &nbsp; PW VCCV as nati=
ve Associated Channel, then architecture of ACh<br>&gt; &nbsp; &nbsp; &nbsp=
; for MPLS-TP PW not simplified as result of adopting the proposal.<br>&gt;=
<br>&gt; Regard<o:p></o:p></p></div><p class=3DMsoNormal>Greg,<br>The GAL i=
s basically a notifier that the packet following the end of the<br>MPLS lab=
el stack, is explicitly defined as a G-ACH format.<br>Normally the packet w=
ould be decoded as an IP packet , unless the last<br>label on the stack ind=
icated otherwise.<br><br>The GAL can certainly be applied &nbsp;to a PW OAM=
 packet on a PW that uses<br>the CW, and this document does not define that=
 , nor restricts it.<br><br>The scope of this document is limited to removi=
ng an unnecessary<br>restriction in rfc5586, hence &nbsp;this comment not a=
pplicable to this document.<br><br>Thanks.<br>Luca<o:p></o:p></p><div><p cl=
ass=3DMsoNormal><br>&gt; s,<br>&gt; Greg<br>&gt;<br>&gt; On Fri, Feb 18, 20=
11 at 7:46 AM, Luca Martini &lt;<a href=3D"mailto:lmartini@cisco.com">lmart=
ini@cisco.com</a><o:p></o:p></p></div><div><p class=3DMsoNormal>&gt; &lt;ma=
ilto:<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;&gt; w=
rote:<br>&gt;<br>&gt; &nbsp; &nbsp; Greg,<br>&gt;<br>&gt; &nbsp; &nbsp; Sor=
ry, but I do not remember the point you mention.<br>&gt; &nbsp; &nbsp; Can =
you explain again here ?<br>&gt; &nbsp; &nbsp; Thanks.<br>&gt; &nbsp; &nbsp=
; Luca<br>&gt;<br>&gt;<br>&gt; &nbsp; &nbsp; On 02/17/11 23:47, Greg Mirsky=
 wrote:<br>&gt; &nbsp; &nbsp; &gt; Dear Authors and All,<br>&gt; &nbsp; &nb=
sp; &gt; prior to the meeting in Bejing and acceptance of this proposal as =
WG<br>&gt; &nbsp; &nbsp; &gt; document Luca and I agreed that use of GAL wi=
th PW VCCV presents a<br>&gt; &nbsp; &nbsp; &gt; problem.<br>&gt; &nbsp; &n=
bsp; &gt; I was not attending the IETF-79, nor I found discussion of this<b=
r>&gt; &nbsp; &nbsp; issue<br>&gt; &nbsp; &nbsp; &gt; in the minutes. I thi=
nk that this issue should be specified,<br>&gt; &nbsp; &nbsp; &gt; explaine=
d. In my view, this document updates not only RFC 5586<br>&gt; &nbsp; &nbsp=
; &gt; but RFC 5085 too.<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &=
gt; Regards,<br>&gt; &nbsp; &nbsp; &gt; Greg<br>&gt; &nbsp; &nbsp; &gt;<br>=
&gt; &nbsp; &nbsp; &gt; Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<b=
r>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; On Sat, Oct 30, 2010 a=
t 10:14 AM, Luca Martini<br>&gt; &nbsp; &nbsp; &lt;<a href=3D"mailto:lmarti=
ni@cisco.com">lmartini@cisco.com</a> &lt;mailto:<a href=3D"mailto:lmartini@=
cisco.com">lmartini@cisco.com</a>&gt;<o:p></o:p></p></div><div><div><p clas=
s=3DMsoNormal>&gt; &nbsp; &nbsp; &gt; &lt;mailto:<a href=3D"mailto:lmartini=
@cisco.com">lmartini@cisco.com</a> &lt;mailto:<a href=3D"mailto:lmartini@ci=
sco.com">lmartini@cisco.com</a>&gt;&gt;&gt; wrote:<br>&gt; &nbsp; &nbsp; &g=
t;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Greg,<br>&gt; &nbsp; &nbsp; &gt=
;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; You are correct , the proposed u=
pdate does not propose any<br>&gt; &nbsp; &nbsp; changes<br>&gt; &nbsp; &nb=
sp; &gt; &nbsp; &nbsp; to VCCV.<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Ho=
wever the problem with vccv is not as simple as to ask for<br>&gt; &nbsp; &=
nbsp; a new<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; code point from IANA.<=
br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Given the good amount of discussio=
n on this point, we should<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; probabl=
y have a discussion in Beijing.<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &=
nbsp; &gt; &nbsp; &nbsp; Luca<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nb=
sp; &gt;<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp=
; On 10/29/2010 05:07 PM, Greg Mirsky wrote:<br>&gt; &nbsp; &nbsp; &gt;&gt;=
 &nbsp; &nbsp; Dear Authors,<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; I=
 think that proposed update of the Section 4.2. RFC 5586<br>&gt; &nbsp; &nb=
sp; makes it possible<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; to use G=
AL on MPLS-TP PW that uses Control Word. I consider<br>&gt; &nbsp; &nbsp; i=
t to be<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; conflict between PW VC=
CV CC types because use of GAL is not<br>&gt; &nbsp; &nbsp; negotiated<br>&=
gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; through PW VCCV negotiation. To av=
oid such situation I propose:<br>&gt; &nbsp; &nbsp; &gt;&gt;<br>&gt; &nbsp;=
 &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;- in Section 5 request IANA to =
assign new CC Type &quot;MPLS<br>&gt; &nbsp; &nbsp; Generic<br>&gt; &nbsp; =
&nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;Associated Channel Label&quot;<b=
r>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;- assign precedenc=
e to new CC Type that affects Section<br>&gt; &nbsp; &nbsp; 7 RFC 5085<br>&=
gt; &nbsp; &nbsp; &gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Reg=
ards,<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Greg<br>&gt; &nbsp; &nbs=
p; &gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt;<b=
r>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; _______________________________=
________________<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; mpls mailing =
list<o:p></o:p></p></div></div><p class=3DMsoNormal>&gt; &nbsp; &nbsp; &gt;=
&gt; &nbsp; &nbsp; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> &lt;m=
ailto:<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt; &lt;mailto:<a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></p><div><div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>&gt; &nbsp; &nbsp; &lt;mai=
lto:<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;&gt;<br>&gt; &nbs=
p; &nbsp; &gt;&gt; &nbsp; &nbsp; <a href=3D"https://www.ietf.org/mailman/li=
stinfo/mpls" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</=
a><br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nb=
sp; &gt;<br>&gt; &nbsp; &nbsp; &gt; _______________________________________=
________<br>&gt; &nbsp; &nbsp; &gt; mpls mailing list<br>&gt; &nbsp; &nbsp;=
 &gt; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> &lt;mailto:<a href=
=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<br>&gt; &nbsp; &nbsp; &gt; =
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>&gt;<br>&gt;<br><br><o:p></=
o:p></p></div></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><=
/div></body></html>=

--_000_A3C5DF08D38B6049839A6F553B331C76D6FBBDD332ILPTMAIL02eci_--

From venkatflex@gmail.com  Fri Mar 11 12:11:39 2011
Return-Path: <venkatflex@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10CBC3A6A63; Fri, 11 Mar 2011 12:11:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.558
X-Spam-Level: 
X-Spam-Status: No, score=-3.558 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 AclshglcZ15n; Fri, 11 Mar 2011 12:11:33 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 7669C3A6A13; Fri, 11 Mar 2011 12:11:32 -0800 (PST)
Received: by qyk29 with SMTP id 29so5768229qyk.10 for <multiple recipients>; Fri, 11 Mar 2011 12:12:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Fn42uvlStrWIca7gwqedlwhWSf5nw5TZ4X0jBYl4qPA=; b=Yw8UrmjTYbuem3csujknmwiIn6ic+lGsgUTn6iR48xJ/pXIjTgCAaG/NtWTz39uCBf udJlIjhl49x3KV2jeB923WM/gPIJX5+s6KSbHQTY4YTae+xgsz7waoKBHI8IdpXrsaNb dHelOXYzL8F3mAJZ18SMWXOfhsxhKyT/5Vq5E=
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=xxUAL3zQ4AneBCNUFb70uPymMLhDVmkO7uD/MLgbw5nqzcTAGCQ34W1Po0fA1Q2Cl1 9+BX+4XxhXL9nMkmjcP6OUDoW/qQYLejbsQnVo4nV3WJNFfQV1jxCq/7995Pmi1onjvw kb56q6CZ4ECktM1jeEUyZJK0MUOqB2hemo8Tk=
MIME-Version: 1.0
Received: by 10.224.213.193 with SMTP id gx1mr5574898qab.44.1299874371694; Fri, 11 Mar 2011 12:12:51 -0800 (PST)
Received: by 10.224.20.71 with HTTP; Fri, 11 Mar 2011 12:12:51 -0800 (PST)
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D6FBBDD332@ILPTMAIL02.ecitele.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com> <4D5E9442.3030101@cisco.com> <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com> <4D7A2439.6010508@cisco.com> <AANLkTim+hqNFHi9xwuzG5_2qoKztEn9SJA9TDh-S-XUo@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D6FBBDD332@ILPTMAIL02.ecitele.com>
Date: Fri, 11 Mar 2011 15:12:51 -0500
Message-ID: <AANLkTiksdHNcsN6PKet48Ps1gDuCWWhcJcaLEQ3npVC+@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, Greg Mirsky <gregimirsky@gmail.com>, Luca Martini <lmartini@cisco.com>, "lihan@chinamobile.com" <lihan@chinamobile.com>,  "mpls-tp@ietf.org" <mpls-tp@ietf.org>, pwe3 <pwe3@ietf.org>,  HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, "mpls@ietf.org" <mpls@ietf.org>
Content-Type: multipart/alternative; boundary=20cf3005dccc2d70e2049e3a9686
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 20:11:40 -0000

--20cf3005dccc2d70e2049e3a9686
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,
AFAIK, ACH can't be used without supporting the CW in HW.

As per RFC-5085, 5.1.1.  In-Band VCCV (Type 1)
CC Type-1 mode of VCCV operation MUST be supported when the control word is
present.

Are we implicitly mandating the CW (ACH) in HW by configuring/negotiating
the CC type-4?
It looks to me that CC type-1 for ACH without GAL and CC type-4 for ACH wit=
h
GAL.

IMO, if we support CC type-4, CC type-1 support is implicitly attained.

IMHO, it should be possible to get the MPLS-TP OAM control packets with or
without GAL from HW to CP by negotiating CC type-1 itself.

Some editorial comments for the draft-nadeau-pwe3-vccv-2-01.txt draft,
"
4.1.1.  MPLS VCCV Control Channel (CC) Type 4

   IANA is requested to augment the registry of "MPLS VCCV Control
   Channel Types" with the new type defined below. As defined in
   RFC5058, this new bitfield is to be assigned by IANA using
"
Replace the RFC5058 as RFC5085.

Thanks,
Venkat.

On Fri, Mar 11, 2011 at 2:21 PM, Alexander Vainshtein <
Alexander.Vainshtein@ecitele.com> wrote:

> Greg, Luca,
>
> As I=92ve already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO =
it
> makes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.
>
>
>
> My 2c,
>
>      Sasha
>
>
>
> *From:* mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] *On Behalf O=
f
> *Greg Mirsky
> *Sent:* Friday, March 11, 2011 9:14 PM
> *To:* Luca Martini
> *Cc:* lihan@chinamobile.com; mpls@ietf.org; pwe3; HUANG Feng F;
> mpls-tp@ietf.org
> *Subject:* Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>
>
>
> Dear Luca,
> thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. I'll
> send my comments to it in a separate e-mail.
> I'll have to miss another opportunity to discuss your proposal in a
> meeting. Please add my comments below to my earlier expressed WG LC
> comments:
>
>    - the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that
>    addresses applicability of GAL in PW VCCV, e.g. solution proposed in
>    draft-nadeau-pwe3-vccv-2-01;
>    - the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such
>    dependency and refer to any existing proposal;
>    - I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advance=
d
>    in lock with document that addresses use of GAL in PW VCCV.
>
> Regards,
> Greg
>
> On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini <lmartini@cisco.com> wrote:
>
> Greg ,
> Some
>
>
> On 02/18/11 11:15, Greg Mirsky wrote:
> > Dear Luca,
> > I see at least two issues:
> >
> >     * use of GAL for PW, in my view, is another VCCV CC type that has
> >       to be negotiated as described in RFC 5085.
> >
>
> These are valid points, but this document in question does not define,
> not discussed VCCV.
> We have since posted a draft that proposes a new VCCV mode , and we
> welcome comments regarding that document.
> (draft-nadeau-pwe3-vccv-2-01.txt)
>
> >     * use of GAL creates ambiguous situation when PW CW is used. The
>
> >       benefit from extending GAL in PW, as I see, is for PWs that are
> >       not required to use PW CW. That might be a good enough reason to
> >       update RFC 5586 as proposed in the document but we must address
> >       use cases of GAL in PWs that require presence PW CW. If we
> >       prohibit or even discourage use of GAL for these PWs that have
> >       PW VCCV as native Associated Channel, then architecture of ACh
> >       for MPLS-TP PW not simplified as result of adopting the proposal.
> >
> > Regard
>
> Greg,
> The GAL is basically a notifier that the packet following the end of the
> MPLS label stack, is explicitly defined as a G-ACH format.
> Normally the packet would be decoded as an IP packet , unless the last
> label on the stack indicated otherwise.
>
> The GAL can certainly be applied  to a PW OAM packet on a PW that uses
> the CW, and this document does not define that , nor restricts it.
>
> The scope of this document is limited to removing an unnecessary
> restriction in rfc5586, hence  this comment not applicable to this
> document.
>
> Thanks.
> Luca
>
>
> > s,
> > Greg
> >
> > On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com
>
> > <mailto:lmartini@cisco.com>> wrote:
> >
> >     Greg,
> >
> >     Sorry, but I do not remember the point you mention.
> >     Can you explain again here ?
> >     Thanks.
> >     Luca
> >
> >
> >     On 02/17/11 23:47, Greg Mirsky wrote:
> >     > Dear Authors and All,
> >     > prior to the meeting in Bejing and acceptance of this proposal as
> WG
> >     > document Luca and I agreed that use of GAL with PW VCCV presents =
a
> >     > problem.
> >     > I was not attending the IETF-79, nor I found discussion of this
> >     issue
> >     > in the minutes. I think that this issue should be specified,
> >     > explained. In my view, this document updates not only RFC 5586
> >     > but RFC 5085 too.
> >     >
> >     > Regards,
> >     > Greg
> >     >
> >     > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> >     >
> >     > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
> >     <lmartini@cisco.com <mailto:lmartini@cisco.com>
>
> >     > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>> wrote:
> >     >
> >     >     Greg,
> >     >
> >     >     You are correct , the proposed update does not propose any
> >     changes
> >     >     to VCCV.
> >     >     However the problem with vccv is not as simple as to ask for
> >     a new
> >     >     code point from IANA.
> >     >     Given the good amount of discussion on this point, we should
> >     >     probably have a discussion in Beijing.
> >     >
> >     >     Luca
> >     >
> >     >
> >     >
> >     >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
> >     >>     Dear Authors,
> >     >>     I think that proposed update of the Section 4.2. RFC 5586
> >     makes it possible
> >     >>     to use GAL on MPLS-TP PW that uses Control Word. I consider
> >     it to be
> >     >>     conflict between PW VCCV CC types because use of GAL is not
> >     negotiated
> >     >>     through PW VCCV negotiation. To avoid such situation I
> propose:
> >     >>
> >     >>        - in Section 5 request IANA to assign new CC Type "MPLS
> >     Generic
> >     >>        Associated Channel Label"
> >     >>        - assign precedence to new CC Type that affects Section
> >     7 RFC 5085
> >     >>
> >     >>     Regards,
> >     >>     Greg
> >     >>
> >     >>
> >     >>
> >     >>     _______________________________________________
> >     >>     mpls mailing list
>
> >     >>     mpls@ietf.org <mailto:mpls@ietf.org> <mailto: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
> https://www.ietf.org/mailman/listinfo/mpls
>
>


--=20
Best Regards,
Venkatesan Mahalingam.

--20cf3005dccc2d70e2049e3a9686
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,<div><div>AFAIK, ACH can&#39;t be used without supporting the CW in HW.<=
/div><div><br></div><div>As per RFC-5085, 5.1.1. =A0In-Band VCCV (Type 1)</=
div><div>CC Type-1 mode of VCCV operation MUST be supported when the contro=
l word is present.</div>
<div><br></div><div>Are we implicitly mandating the CW (ACH) in HW by confi=
guring/negotiating the CC type-4?</div><div>It looks to me that CC type-1 f=
or ACH without GAL and CC type-4 for ACH with GAL.</div><div><br></div>
<div>IMO, if we support CC type-4, CC type-1 support is implicitly attained=
.</div><div><br></div><div>IMHO, it should be possible to get the MPLS-TP O=
AM control packets with or without GAL from HW to CP by negotiating CC type=
-1 itself.</div>
<div><br></div><div><div>Some editorial comments for the draft-nadeau-pwe3-=
vccv-2-01.txt draft,</div><div>&quot;</div><div>4.1.1. =A0MPLS VCCV Control=
 Channel (CC) Type 4</div><div><br></div><div>=A0=A0 IANA is requested to a=
ugment the registry of &quot;MPLS VCCV Control</div>
<div>=A0=A0 Channel Types&quot; with the new type defined below. As defined=
 in</div><div>=A0=A0 RFC5058, this new bitfield is to be assigned by IANA u=
sing</div><div>&quot;</div><div>Replace the RFC5058 as RFC5085.</div></div>=
<div>
<br></div><div>Thanks,</div><div>Venkat.</div><br><div class=3D"gmail_quote=
">On Fri, Mar 11, 2011 at 2:21 PM, Alexander Vainshtein <span dir=3D"ltr">&=
lt;<a href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshtein=
@ecitele.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div lang=3D"EN-US" link=3D"blue" vlink=3D"=
purple"><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#=
1F497D">Greg, Luca,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">As I=
=92ve already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO it mak=
es draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.</span></p><p class=
=3D"MsoNormal">
<span style=3D"font-size:11.0pt;color:#1F497D">=A0</span></p><p class=3D"Ms=
oNormal"><span style=3D"font-size:11.0pt;color:#1F497D">My 2c,</span></p><p=
 class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">=A0=A0=
=A0=A0 Sasha</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">=A0</=
span></p><div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm=
 0cm 0cm 4.0pt"><div><div style=3D"border:none;border-top:solid #B5C4DF 1.0=
pt;padding:3.0pt 0cm 0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">From:</span></b>=
<span style=3D"font-size:10.0pt"> <a href=3D"mailto:mpls-bounces@ietf.org" =
target=3D"_blank">mpls-bounces@ietf.org</a> [mailto:<a href=3D"mailto:mpls-=
bounces@ietf.org" target=3D"_blank">mpls-bounces@ietf.org</a>] <b>On Behalf=
 Of </b>Greg Mirsky<br>
<b>Sent:</b> Friday, March 11, 2011 9:14 PM<br><b>To:</b> Luca Martini<br><=
b>Cc:</b> <a href=3D"mailto:lihan@chinamobile.com" target=3D"_blank">lihan@=
chinamobile.com</a>; <a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpl=
s@ietf.org</a>; pwe3; HUANG Feng F; <a href=3D"mailto:mpls-tp@ietf.org" tar=
get=3D"_blank">mpls-tp@ietf.org</a><br>
<b>Subject:</b> Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt</sp=
an></p></div></div><div><div></div><div class=3D"h5"><p class=3D"MsoNormal"=
>=A0</p><p class=3D"MsoNormal">Dear Luca,<br>thank you for bringing draft-n=
adeau-pwe3-vccv-2-01 to my attention. I&#39;ll send my comments to it in a =
separate e-mail.<br>
I&#39;ll have to miss another opportunity to discuss your proposal in a mee=
ting. Please add my comments below to my earlier expressed WG LC comments:<=
/p><ul type=3D"disc"><li class=3D"MsoNormal">the draft-lm-pwe3-mpls-tp-gal-=
in-pw-00 depends on any solution that addresses applicability of GAL in PW =
VCCV, e.g. solution proposed in draft-nadeau-pwe3-vccv-2-01;</li>
<li class=3D"MsoNormal">the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to men=
tion such dependency and refer to any existing proposal;</li><li class=3D"M=
soNormal">I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be adva=
nced in lock with document that addresses use of GAL in PW VCCV.</li>
</ul><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Regards,<br>Greg=
</p><div><p class=3D"MsoNormal">On Fri, Mar 11, 2011 at 5:31 AM, Luca Marti=
ni &lt;<a href=3D"mailto:lmartini@cisco.com" target=3D"_blank">lmartini@cis=
co.com</a>&gt; wrote:</p>
<p class=3D"MsoNormal">Greg ,<br>Some</p><div><p class=3D"MsoNormal"><br>On=
 02/18/11 11:15, Greg Mirsky wrote:<br>&gt; Dear Luca,<br>&gt; I see at lea=
st two issues:<br>&gt;<br>&gt; =A0 =A0 * use of GAL for PW, in my view, is =
another VCCV CC type that has<br>
&gt; =A0 =A0 =A0 to be negotiated as described in RFC 5085.<br>&gt;</p></di=
v><p class=3D"MsoNormal">These are valid points, but this document in quest=
ion does not define,<br>not discussed VCCV.<br>We have since posted a draft=
 that proposes a new VCCV mode , and we<br>
welcome comments regarding that document.<br>(draft-nadeau-pwe3-vccv-2-01.t=
xt)<br><br>&gt; =A0 =A0 * use of GAL creates ambiguous situation when PW CW=
 is used. The</p><div><p class=3D"MsoNormal">&gt; =A0 =A0 =A0 benefit from =
extending GAL in PW, as I see, is for PWs that are<br>
&gt; =A0 =A0 =A0 not required to use PW CW. That might be a good enough rea=
son to<br>&gt; =A0 =A0 =A0 update RFC 5586 as proposed in the document but =
we must address<br>&gt; =A0 =A0 =A0 use cases of GAL in PWs that require pr=
esence PW CW. If we<br>
&gt; =A0 =A0 =A0 prohibit or even discourage use of GAL for these PWs that =
have<br>&gt; =A0 =A0 =A0 PW VCCV as native Associated Channel, then archite=
cture of ACh<br>&gt; =A0 =A0 =A0 for MPLS-TP PW not simplified as result of=
 adopting the proposal.<br>
&gt;<br>&gt; Regard</p></div><p class=3D"MsoNormal">Greg,<br>The GAL is bas=
ically a notifier that the packet following the end of the<br>MPLS label st=
ack, is explicitly defined as a G-ACH format.<br>Normally the packet would =
be decoded as an IP packet , unless the last<br>
label on the stack indicated otherwise.<br><br>The GAL can certainly be app=
lied =A0to a PW OAM packet on a PW that uses<br>the CW, and this document d=
oes not define that , nor restricts it.<br><br>The scope of this document i=
s limited to removing an unnecessary<br>
restriction in rfc5586, hence =A0this comment not applicable to this docume=
nt.<br><br>Thanks.<br>Luca</p><div><p class=3D"MsoNormal"><br>&gt; s,<br>&g=
t; Greg<br>&gt;<br>&gt; On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini &lt;<=
a href=3D"mailto:lmartini@cisco.com" target=3D"_blank">lmartini@cisco.com</=
a></p>
</div><div><p class=3D"MsoNormal">&gt; &lt;mailto:<a href=3D"mailto:lmartin=
i@cisco.com" target=3D"_blank">lmartini@cisco.com</a>&gt;&gt; wrote:<br>&gt=
;<br>&gt; =A0 =A0 Greg,<br>&gt;<br>&gt; =A0 =A0 Sorry, but I do not remembe=
r the point you mention.<br>
&gt; =A0 =A0 Can you explain again here ?<br>&gt; =A0 =A0 Thanks.<br>&gt; =
=A0 =A0 Luca<br>&gt;<br>&gt;<br>&gt; =A0 =A0 On 02/17/11 23:47, Greg Mirsky=
 wrote:<br>&gt; =A0 =A0 &gt; Dear Authors and All,<br>&gt; =A0 =A0 &gt; pri=
or to the meeting in Bejing and acceptance of this proposal as WG<br>
&gt; =A0 =A0 &gt; document Luca and I agreed that use of GAL with PW VCCV p=
resents a<br>&gt; =A0 =A0 &gt; problem.<br>&gt; =A0 =A0 &gt; I was not atte=
nding the IETF-79, nor I found discussion of this<br>&gt; =A0 =A0 issue<br>=
&gt; =A0 =A0 &gt; in the minutes. I think that this issue should be specifi=
ed,<br>
&gt; =A0 =A0 &gt; explained. In my view, this document updates not only RFC=
 5586<br>&gt; =A0 =A0 &gt; but RFC 5085 too.<br>&gt; =A0 =A0 &gt;<br>&gt; =
=A0 =A0 &gt; Regards,<br>&gt; =A0 =A0 &gt; Greg<br>&gt; =A0 =A0 &gt;<br>&gt=
; =A0 =A0 &gt; Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br>
&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt; On Sat, Oct 30, 2010 at 10:14 AM, Lu=
ca Martini<br>&gt; =A0 =A0 &lt;<a href=3D"mailto:lmartini@cisco.com" target=
=3D"_blank">lmartini@cisco.com</a> &lt;mailto:<a href=3D"mailto:lmartini@ci=
sco.com" target=3D"_blank">lmartini@cisco.com</a>&gt;</p>
</div><div><div><p class=3D"MsoNormal">&gt; =A0 =A0 &gt; &lt;mailto:<a href=
=3D"mailto:lmartini@cisco.com" target=3D"_blank">lmartini@cisco.com</a> &lt=
;mailto:<a href=3D"mailto:lmartini@cisco.com" target=3D"_blank">lmartini@ci=
sco.com</a>&gt;&gt;&gt; wrote:<br>
&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt; =A0 =A0 Greg,<br>&gt; =A0 =A0 &gt;<b=
r>&gt; =A0 =A0 &gt; =A0 =A0 You are correct , the proposed update does not =
propose any<br>&gt; =A0 =A0 changes<br>&gt; =A0 =A0 &gt; =A0 =A0 to VCCV.<b=
r>&gt; =A0 =A0 &gt; =A0 =A0 However the problem with vccv is not as simple =
as to ask for<br>
&gt; =A0 =A0 a new<br>&gt; =A0 =A0 &gt; =A0 =A0 code point from IANA.<br>&g=
t; =A0 =A0 &gt; =A0 =A0 Given the good amount of discussion on this point, =
we should<br>&gt; =A0 =A0 &gt; =A0 =A0 probably have a discussion in Beijin=
g.<br>&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt; =A0 =A0 Luca<br>
&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0=
 &gt; =A0 =A0 On 10/29/2010 05:07 PM, Greg Mirsky wrote:<br>&gt; =A0 =A0 &g=
t;&gt; =A0 =A0 Dear Authors,<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 I think that =
proposed update of the Section 4.2. RFC 5586<br>
&gt; =A0 =A0 makes it possible<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 to use GAL =
on MPLS-TP PW that uses Control Word. I consider<br>&gt; =A0 =A0 it to be<b=
r>&gt; =A0 =A0 &gt;&gt; =A0 =A0 conflict between PW VCCV CC types because u=
se of GAL is not<br>
&gt; =A0 =A0 negotiated<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 through PW VCCV ne=
gotiation. To avoid such situation I propose:<br>&gt; =A0 =A0 &gt;&gt;<br>&=
gt; =A0 =A0 &gt;&gt; =A0 =A0 =A0 =A0- in Section 5 request IANA to assign n=
ew CC Type &quot;MPLS<br>
&gt; =A0 =A0 Generic<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 =A0 =A0Associated Cha=
nnel Label&quot;<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 =A0 =A0- assign precedenc=
e to new CC Type that affects Section<br>&gt; =A0 =A0 7 RFC 5085<br>&gt; =
=A0 =A0 &gt;&gt;<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 Regards,<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 Greg<br>&gt; =A0 =A0 &gt;&gt;<br>&gt; =A0 =A0=
 &gt;&gt;<br>&gt; =A0 =A0 &gt;&gt;<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 _______=
________________________________________<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 m=
pls mailing list</p></div></div>
<p class=3D"MsoNormal">&gt; =A0 =A0 &gt;&gt; =A0 =A0 <a href=3D"mailto:mpls=
@ietf.org" target=3D"_blank">mpls@ietf.org</a> &lt;mailto:<a href=3D"mailto=
:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>&gt; &lt;mailto:<a href=
=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a></p>
<div><div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt; =A0 =
=A0 &lt;mailto:<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf=
.org</a>&gt;&gt;<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 <a href=3D"https://www.ie=
tf.org/mailman/listinfo/mpls" target=3D"_blank">https://www.ietf.org/mailma=
n/listinfo/mpls</a><br>
&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0=
 &gt; _______________________________________________<br>&gt; =A0 =A0 &gt; =
mpls mailing list<br>&gt; =A0 =A0 &gt; <a href=3D"mailto:mpls@ietf.org" tar=
get=3D"_blank">mpls@ietf.org</a> &lt;mailto:<a href=3D"mailto:mpls@ietf.org=
" target=3D"_blank">mpls@ietf.org</a>&gt;<br>
&gt; =A0 =A0 &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mpls" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>&gt;<br>&=
gt;<br><br></p></div></div></div><p class=3D"MsoNormal">=A0</p></div></div>=
</div></div>
</div><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></blockquote></div><br><br clear=3D"all"><br>-- <br>Best Regards,<br>Ve=
nkatesan Mahalingam.<br>
</div>

--20cf3005dccc2d70e2049e3a9686--

From tnadeau@lucidvision.com  Fri Mar 11 12:57:09 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E5913A6941; Fri, 11 Mar 2011 12:57:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.913
X-Spam-Level: 
X-Spam-Status: No, score=-1.913 tagged_above=-999 required=5 tests=[AWL=0.685,  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 VyhIxur3WG+h; Fri, 11 Mar 2011 12:57:07 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by core3.amsl.com (Postfix) with ESMTP id 05FD73A6962; Fri, 11 Mar 2011 12:57:05 -0800 (PST)
Received: from [192.168.1.133] (unknown [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id E6C261A68122; Fri, 11 Mar 2011 15:58:22 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-5--552644677
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <AANLkTiksdHNcsN6PKet48Ps1gDuCWWhcJcaLEQ3npVC+@mail.gmail.com>
Date: Fri, 11 Mar 2011 15:58:22 -0500
Message-Id: <88290F42-76E9-4403-87F6-9F5BEDA7D59F@lucidvision.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com> <4D5E9442.3030101@cisco.com> <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com> <4D7A2439.6010508@cisco.com> <AANLkTim+hqNFHi9xwuzG5_2qoKztEn9SJA9TDh-S-XUo@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D6FBBDD332@ILPTMAIL02.ecitele.com> <AANLkTiksdHNcsN6PKet48Ps1gDuCWWhcJcaLEQ3npVC+@mail.gmail.com>
To: venkatesan mahalingam <venkatflex@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "mpls@ietf.org" <mpls@ietf.org>, Luca Martini <lmartini@cisco.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 20:57:09 -0000

--Apple-Mail-5--552644677
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252



> Hi,
> AFAIK, ACH can't be used without supporting the CW in HW.
>=20
> As per RFC-5085, 5.1.1.  In-Band VCCV (Type 1)
> CC Type-1 mode of VCCV operation MUST be supported when the control =
word is present.
>=20
> Are we implicitly mandating the CW (ACH) in HW by =
configuring/negotiating the CC type-4?
> It looks to me that CC type-1 for ACH without GAL and CC type-4 for =
ACH with GAL.

	The IETF's protocols do not mandate how they are to be =
implemented per se (i.e.:
in HW or not). The draft addresses the operational concerns of =
configuration/complexity=20
by having 1 mode for each of the major operational scenarios: with or =
without the CW.

> IMO, if we support CC type-4, CC type-1 support is implicitly =
attained.
>=20
> IMHO, it should be possible to get the MPLS-TP OAM control packets =
with or without GAL from HW to CP by negotiating CC type-1 itself.

	There is no negotiation; VCCV uses a capability advertisement. =
But more to the point,=20
the proposed operation rule here is simple and straight-forward: if you =
have configured the CW and advertised=20
that as per the rules for use of the CW, then Type 1 MUST be used. If =
not, use Type 4 (if both sides are capable). =20

> Some editorial comments for the draft-nadeau-pwe3-vccv-2-01.txt draft,
> "
> 4.1.1.  MPLS VCCV Control Channel (CC) Type 4
>=20
>    IANA is requested to augment the registry of "MPLS VCCV Control
>    Channel Types" with the new type defined below. As defined in
>    RFC5058, this new bitfield is to be assigned by IANA using
> "
> Replace the RFC5058 as RFC5085.

	Cool, thanks. We will fix this in the next rev.

	--Tom


>=20
> Thanks,
> Venkat.
>=20
> On Fri, Mar 11, 2011 at 2:21 PM, Alexander Vainshtein =
<Alexander.Vainshtein@ecitele.com> wrote:
> Greg, Luca,
>=20
> As I=92ve already stated in my comment on draft-nadeau-pwe3-vccv-2, =
IMHO it makes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.
>=20
> =20
> My 2c,
>=20
>      Sasha
>=20
> =20
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =
Of Greg Mirsky
> Sent: Friday, March 11, 2011 9:14 PM
> To: Luca Martini
> Cc: lihan@chinamobile.com; mpls@ietf.org; pwe3; HUANG Feng F; =
mpls-tp@ietf.org
> Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>=20
> =20
> Dear Luca,
> thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. =
I'll send my comments to it in a separate e-mail.
> I'll have to miss another opportunity to discuss your proposal in a =
meeting. Please add my comments below to my earlier expressed WG LC =
comments:
>=20
> the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that =
addresses applicability of GAL in PW VCCV, e.g. solution proposed in =
draft-nadeau-pwe3-vccv-2-01;
> the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such =
dependency and refer to any existing proposal;
> I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced =
in lock with document that addresses use of GAL in PW VCCV.
> Regards,
> Greg
>=20
> On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini <lmartini@cisco.com> =
wrote:
>=20
> Greg ,
> Some
>=20
>=20
> On 02/18/11 11:15, Greg Mirsky wrote:
> > Dear Luca,
> > I see at least two issues:
> >
> >     * use of GAL for PW, in my view, is another VCCV CC type that =
has
> >       to be negotiated as described in RFC 5085.
> >
>=20
> These are valid points, but this document in question does not define,
> not discussed VCCV.
> We have since posted a draft that proposes a new VCCV mode , and we
> welcome comments regarding that document.
> (draft-nadeau-pwe3-vccv-2-01.txt)
>=20
> >     * use of GAL creates ambiguous situation when PW CW is used. The
>=20
> >       benefit from extending GAL in PW, as I see, is for PWs that =
are
> >       not required to use PW CW. That might be a good enough reason =
to
> >       update RFC 5586 as proposed in the document but we must =
address
> >       use cases of GAL in PWs that require presence PW CW. If we
> >       prohibit or even discourage use of GAL for these PWs that have
> >       PW VCCV as native Associated Channel, then architecture of ACh
> >       for MPLS-TP PW not simplified as result of adopting the =
proposal.
> >
> > Regard
>=20
> Greg,
> The GAL is basically a notifier that the packet following the end of =
the
> MPLS label stack, is explicitly defined as a G-ACH format.
> Normally the packet would be decoded as an IP packet , unless the last
> label on the stack indicated otherwise.
>=20
> The GAL can certainly be applied  to a PW OAM packet on a PW that uses
> the CW, and this document does not define that , nor restricts it.
>=20
> The scope of this document is limited to removing an unnecessary
> restriction in rfc5586, hence  this comment not applicable to this =
document.
>=20
> Thanks.
> Luca
>=20
>=20
> > s,
> > Greg
> >
> > On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com
>=20
> > <mailto:lmartini@cisco.com>> wrote:
> >
> >     Greg,
> >
> >     Sorry, but I do not remember the point you mention.
> >     Can you explain again here ?
> >     Thanks.
> >     Luca
> >
> >
> >     On 02/17/11 23:47, Greg Mirsky wrote:
> >     > Dear Authors and All,
> >     > prior to the meeting in Bejing and acceptance of this proposal =
as WG
> >     > document Luca and I agreed that use of GAL with PW VCCV =
presents a
> >     > problem.
> >     > I was not attending the IETF-79, nor I found discussion of =
this
> >     issue
> >     > in the minutes. I think that this issue should be specified,
> >     > explained. In my view, this document updates not only RFC 5586
> >     > but RFC 5085 too.
> >     >
> >     > Regards,
> >     > Greg
> >     >
> >     > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> >     >
> >     > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
> >     <lmartini@cisco.com <mailto:lmartini@cisco.com>
>=20
> >     > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>> =
wrote:
> >     >
> >     >     Greg,
> >     >
> >     >     You are correct , the proposed update does not propose any
> >     changes
> >     >     to VCCV.
> >     >     However the problem with vccv is not as simple as to ask =
for
> >     a new
> >     >     code point from IANA.
> >     >     Given the good amount of discussion on this point, we =
should
> >     >     probably have a discussion in Beijing.
> >     >
> >     >     Luca
> >     >
> >     >
> >     >
> >     >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
> >     >>     Dear Authors,
> >     >>     I think that proposed update of the Section 4.2. RFC 5586
> >     makes it possible
> >     >>     to use GAL on MPLS-TP PW that uses Control Word. I =
consider
> >     it to be
> >     >>     conflict between PW VCCV CC types because use of GAL is =
not
> >     negotiated
> >     >>     through PW VCCV negotiation. To avoid such situation I =
propose:
> >     >>
> >     >>        - in Section 5 request IANA to assign new CC Type =
"MPLS
> >     Generic
> >     >>        Associated Channel Label"
> >     >>        - assign precedence to new CC Type that affects =
Section
> >     7 RFC 5085
> >     >>
> >     >>     Regards,
> >     >>     Greg
> >     >>
> >     >>
> >     >>
> >     >>     _______________________________________________
> >     >>     mpls mailing list
>=20
> >     >>     mpls@ietf.org <mailto:mpls@ietf.org> =
<mailto:mpls@ietf.org
>=20
> >     <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
> >
> >
>=20
>=20
> =20
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=20
>=20
>=20
>=20
> --=20
> Best Regards,
> Venkatesan Mahalingam.
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3


--Apple-Mail-5--552644677
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; =
"><br><div><div><br></div><blockquote type=3D"cite">Hi,<div><div>AFAIK, =
ACH can't be used without supporting the CW in =
HW.</div><div><br></div><div>As per RFC-5085, 5.1.1. &nbsp;In-Band VCCV =
(Type 1)</div><div>CC Type-1 mode of VCCV operation MUST be supported =
when the control word is present.</div>
<div><br></div><div>Are we implicitly mandating the CW (ACH) in HW by =
configuring/negotiating the CC type-4?</div><div>It looks to me that CC =
type-1 for ACH without GAL and CC type-4 for ACH with =
GAL.</div></div></blockquote><div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>The =
IETF's protocols do not mandate how they are to be implemented per se =
(i.e.:</div><div>in HW or not). The draft&nbsp;addresses the operational =
concerns of configuration/complexity&nbsp;</div><div>by&nbsp;having 1 =
mode for each of the major operational scenarios: with or without the =
CW.</div><br><blockquote type=3D"cite"><div><div>IMO, if we support CC =
type-4, CC type-1 support is implicitly =
attained.</div><div><br></div><div>IMHO, it should be possible to get =
the MPLS-TP OAM control packets with or without GAL from HW to CP by =
negotiating CC type-1 =
itself.</div></div></blockquote><div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>There is =
no negotiation; VCCV uses a capability advertisement. But more to the =
point,&nbsp;</div><div>the proposed operation rule here is simple and =
straight-forward: if you have configured the CW and =
advertised&nbsp;</div><div>that as per&nbsp;the&nbsp;rules for use of =
the CW, then Type 1 MUST be used. If not, use Type 4 (if both =
sides&nbsp;are capable). &nbsp;</div><br><blockquote type=3D"cite"><div>
<div>Some editorial comments for the draft-nadeau-pwe3-vccv-2-01.txt =
draft,</div><div><div>"</div><div>4.1.1. &nbsp;MPLS VCCV Control Channel =
(CC) Type 4</div><div><br></div><div>&nbsp;&nbsp; IANA is requested to =
augment the registry of "MPLS VCCV Control</div>
<div>&nbsp;&nbsp; Channel Types" with the new type defined below. As =
defined in</div><div>&nbsp;&nbsp; RFC5058, this new bitfield is to be =
assigned by IANA using</div><div>"</div><div>Replace the RFC5058 as =
RFC5085.</div></div></div></blockquote><div><br></div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Cool, =
thanks. We will fix this in the next rev.</div><div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>--Tom</div><div><br></div><div><br><blockquote =
type=3D"cite"><div><div>
<br></div><div>Thanks,</div><div>Venkat.</div><br><div =
class=3D"gmail_quote">On Fri, Mar 11, 2011 at 2:21 PM, Alexander =
Vainshtein <span dir=3D"ltr">&lt;<a =
href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshtein@ecit=
ele.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;"><div lang=3D"EN-US" =
link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;color:#1F497D">Greg, Luca,</span></p><p =
class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">As =
I=92ve already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO it =
makes draft-lm-pwe3-mpls-tp-gal-in-pw completely =
useless.</span></p><div>
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span><br =
class=3D"webkit-block-placeholder"></div><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;color:#1F497D">My 2c,</span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp; =
Sasha</span></p><div><span =
style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span><br =
class=3D"webkit-block-placeholder"></div><div =
style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt"><div><div style=3D"border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class=3D"MsoNormal"><b><span =
style=3D"font-size:10.0pt">From:</span></b><span =
style=3D"font-size:10.0pt"> <a href=3D"mailto:mpls-bounces@ietf.org" =
target=3D"_blank">mpls-bounces@ietf.org</a> [mailto:<a =
href=3D"mailto:mpls-bounces@ietf.org" =
target=3D"_blank">mpls-bounces@ietf.org</a>] <b>On Behalf Of </b>Greg =
Mirsky<br>
<b>Sent:</b> Friday, March 11, 2011 9:14 PM<br><b>To:</b> Luca =
Martini<br><b>Cc:</b> <a href=3D"mailto:lihan@chinamobile.com" =
target=3D"_blank">lihan@chinamobile.com</a>; <a =
href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>; pwe3; =
HUANG Feng F; <a href=3D"mailto:mpls-tp@ietf.org" =
target=3D"_blank">mpls-tp@ietf.org</a><br>
<b>Subject:</b> Re: [mpls] WG LC =
draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt</span></p></div></div><div><div></d=
iv><div class=3D"h5"><div>&nbsp;<br =
class=3D"webkit-block-placeholder"></div><p class=3D"MsoNormal">Dear =
Luca,<br>thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my =
attention. I'll send my comments to it in a separate e-mail.<br>
I'll have to miss another opportunity to discuss your proposal in a =
meeting. Please add my comments below to my earlier expressed WG LC =
comments:</p><ul type=3D"disc"><li class=3D"MsoNormal">the =
draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that =
addresses applicability of GAL in PW VCCV, e.g. solution proposed in =
draft-nadeau-pwe3-vccv-2-01;</li>
<li class=3D"MsoNormal">the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to =
mention such dependency and refer to any existing proposal;</li><li =
class=3D"MsoNormal">I believe that the =
draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced in lock with document =
that addresses use of GAL in PW VCCV.</li>
</ul><p class=3D"MsoNormal" =
style=3D"margin-bottom:12.0pt">Regards,<br>Greg</p><div><p =
class=3D"MsoNormal">On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini &lt;<a =
href=3D"mailto:lmartini@cisco.com" =
target=3D"_blank">lmartini@cisco.com</a>&gt; wrote:</p><p =
class=3D"MsoNormal">Greg ,<br>Some</p><div><p class=3D"MsoNormal"><br>On =
02/18/11 11:15, Greg Mirsky wrote:<br>&gt; Dear Luca,<br>&gt; I see at =
least two issues:<br>&gt;<br>&gt; &nbsp; &nbsp; * use of GAL for PW, in =
my view, is another VCCV CC type that has<br>
&gt; &nbsp; &nbsp; &nbsp; to be negotiated as described in RFC =
5085.<br>&gt;</p></div><p class=3D"MsoNormal">These are valid points, =
but this document in question does not define,<br>not discussed =
VCCV.<br>We have since posted a draft that proposes a new VCCV mode , =
and we<br>
welcome comments regarding that =
document.<br>(draft-nadeau-pwe3-vccv-2-01.txt)<br><br>&gt; &nbsp; &nbsp; =
* use of GAL creates ambiguous situation when PW CW is used. =
The</p><div><p class=3D"MsoNormal">&gt; &nbsp; &nbsp; &nbsp; benefit =
from extending GAL in PW, as I see, is for PWs that are<br>
&gt; &nbsp; &nbsp; &nbsp; not required to use PW CW. That might be a =
good enough reason to<br>&gt; &nbsp; &nbsp; &nbsp; update RFC 5586 as =
proposed in the document but we must address<br>&gt; &nbsp; &nbsp; =
&nbsp; use cases of GAL in PWs that require presence PW CW. If we<br>
&gt; &nbsp; &nbsp; &nbsp; prohibit or even discourage use of GAL for =
these PWs that have<br>&gt; &nbsp; &nbsp; &nbsp; PW VCCV as native =
Associated Channel, then architecture of ACh<br>&gt; &nbsp; &nbsp; =
&nbsp; for MPLS-TP PW not simplified as result of adopting the =
proposal.<br>
&gt;<br>&gt; Regard</p></div><p class=3D"MsoNormal">Greg,<br>The GAL is =
basically a notifier that the packet following the end of the<br>MPLS =
label stack, is explicitly defined as a G-ACH format.<br>Normally the =
packet would be decoded as an IP packet , unless the last<br>
label on the stack indicated otherwise.<br><br>The GAL can certainly be =
applied &nbsp;to a PW OAM packet on a PW that uses<br>the CW, and this =
document does not define that , nor restricts it.<br><br>The scope of =
this document is limited to removing an unnecessary<br>
restriction in rfc5586, hence &nbsp;this comment not applicable to this =
document.<br><br>Thanks.<br>Luca</p><div><p class=3D"MsoNormal"><br>&gt; =
s,<br>&gt; Greg<br>&gt;<br>&gt; On Fri, Feb 18, 2011 at 7:46 AM, Luca =
Martini &lt;<a href=3D"mailto:lmartini@cisco.com" =
target=3D"_blank">lmartini@cisco.com</a></p>
</div><div><p class=3D"MsoNormal">&gt; &lt;mailto:<a =
href=3D"mailto:lmartini@cisco.com" =
target=3D"_blank">lmartini@cisco.com</a>&gt;&gt; wrote:<br>&gt;<br>&gt; =
&nbsp; &nbsp; Greg,<br>&gt;<br>&gt; &nbsp; &nbsp; Sorry, but I do not =
remember the point you mention.<br>
&gt; &nbsp; &nbsp; Can you explain again here ?<br>&gt; &nbsp; &nbsp; =
Thanks.<br>&gt; &nbsp; &nbsp; Luca<br>&gt;<br>&gt;<br>&gt; &nbsp; &nbsp; =
On 02/17/11 23:47, Greg Mirsky wrote:<br>&gt; &nbsp; &nbsp; &gt; Dear =
Authors and All,<br>&gt; &nbsp; &nbsp; &gt; prior to the meeting in =
Bejing and acceptance of this proposal as WG<br>
&gt; &nbsp; &nbsp; &gt; document Luca and I agreed that use of GAL with =
PW VCCV presents a<br>&gt; &nbsp; &nbsp; &gt; problem.<br>&gt; &nbsp; =
&nbsp; &gt; I was not attending the IETF-79, nor I found discussion of =
this<br>&gt; &nbsp; &nbsp; issue<br>&gt; &nbsp; &nbsp; &gt; in the =
minutes. I think that this issue should be specified,<br>
&gt; &nbsp; &nbsp; &gt; explained. In my view, this document updates not =
only RFC 5586<br>&gt; &nbsp; &nbsp; &gt; but RFC 5085 too.<br>&gt; =
&nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; Regards,<br>&gt; &nbsp; =
&nbsp; &gt; Greg<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; =
Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br>
&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; On Sat, Oct 30, 2010 =
at 10:14 AM, Luca Martini<br>&gt; &nbsp; &nbsp; &lt;<a =
href=3D"mailto:lmartini@cisco.com" =
target=3D"_blank">lmartini@cisco.com</a> &lt;mailto:<a =
href=3D"mailto:lmartini@cisco.com" =
target=3D"_blank">lmartini@cisco.com</a>&gt;</p>
</div><div><div><p class=3D"MsoNormal">&gt; &nbsp; &nbsp; &gt; =
&lt;mailto:<a href=3D"mailto:lmartini@cisco.com" =
target=3D"_blank">lmartini@cisco.com</a> &lt;mailto:<a =
href=3D"mailto:lmartini@cisco.com" =
target=3D"_blank">lmartini@cisco.com</a>&gt;&gt;&gt; wrote:<br>
&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; =
Greg,<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; =
&nbsp; You are correct , the proposed update does not propose =
any<br>&gt; &nbsp; &nbsp; changes<br>&gt; &nbsp; &nbsp; &gt; &nbsp; =
&nbsp; to VCCV.<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; However the =
problem with vccv is not as simple as to ask for<br>
&gt; &nbsp; &nbsp; a new<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; code =
point from IANA.<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Given the good =
amount of discussion on this point, we should<br>&gt; &nbsp; &nbsp; &gt; =
&nbsp; &nbsp; probably have a discussion in Beijing.<br>&gt; &nbsp; =
&nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Luca<br>
&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; =
&gt;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; On 10/29/2010 05:07 PM, =
Greg Mirsky wrote:<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Dear =
Authors,<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; I think that =
proposed update of the Section 4.2. RFC 5586<br>
&gt; &nbsp; &nbsp; makes it possible<br>&gt; &nbsp; &nbsp; &gt;&gt; =
&nbsp; &nbsp; to use GAL on MPLS-TP PW that uses Control Word. I =
consider<br>&gt; &nbsp; &nbsp; it to be<br>&gt; &nbsp; &nbsp; &gt;&gt; =
&nbsp; &nbsp; conflict between PW VCCV CC types because use of GAL is =
not<br>
&gt; &nbsp; &nbsp; negotiated<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; =
&nbsp; through PW VCCV negotiation. To avoid such situation I =
propose:<br>&gt; &nbsp; &nbsp; &gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt; =
&nbsp; &nbsp; &nbsp; &nbsp;- in Section 5 request IANA to assign new CC =
Type "MPLS<br>
&gt; &nbsp; &nbsp; Generic<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; =
&nbsp; &nbsp;Associated Channel Label"<br>&gt; &nbsp; &nbsp; &gt;&gt; =
&nbsp; &nbsp; &nbsp; &nbsp;- assign precedence to new CC Type that =
affects Section<br>&gt; &nbsp; &nbsp; 7 RFC 5085<br>&gt; &nbsp; &nbsp; =
&gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Regards,<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Greg<br>&gt; &nbsp; &nbsp; =
&gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt;<br>&gt; &nbsp; &nbsp; =
&gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; =
_______________________________________________<br>&gt; &nbsp; &nbsp; =
&gt;&gt; &nbsp; &nbsp; mpls mailing list</p></div></div><p =
class=3D"MsoNormal">&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; <a =
href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a> =
&lt;mailto:<a href=3D"mailto:mpls@ietf.org" =
target=3D"_blank">mpls@ietf.org</a>&gt; &lt;mailto:<a =
href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a></p>
<div><div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt; =
&nbsp; &nbsp; &lt;mailto:<a href=3D"mailto:mpls@ietf.org" =
target=3D"_blank">mpls@ietf.org</a>&gt;&gt;<br>&gt; &nbsp; &nbsp; =
&gt;&gt; &nbsp; &nbsp; <a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>
&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; =
&gt;<br>&gt; &nbsp; &nbsp; &gt; =
_______________________________________________<br>&gt; &nbsp; &nbsp; =
&gt; mpls mailing list<br>&gt; &nbsp; &nbsp; &gt; <a =
href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a> =
&lt;mailto:<a href=3D"mailto:mpls@ietf.org" =
target=3D"_blank">mpls@ietf.org</a>&gt;<br>
&gt; &nbsp; &nbsp; &gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>&gt;<b=
r>&gt;<br><br></p></div></div></div><div>&nbsp;<br =
class=3D"webkit-block-placeholder"></div></div></div></div></div>
</div><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>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Best =
Regards,<br>Venkatesan Mahalingam.<br>
</div>
_______________________________________________<br>pwe3 mailing =
list<br><a =
href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/pwe3<br></blockquote></div><br></body></html>=

--Apple-Mail-5--552644677--

From gregimirsky@gmail.com  Fri Mar 11 14:25:16 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E99B83A6A35; Fri, 11 Mar 2011 14:25:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level: 
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[AWL=-0.200, 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 wgm9dbpUjnG3; Fri, 11 Mar 2011 14:25:16 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id CA0073A6A33; Fri, 11 Mar 2011 14:25:15 -0800 (PST)
Received: by vxg33 with SMTP id 33so3633815vxg.31 for <multiple recipients>; Fri, 11 Mar 2011 14:26:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=2GrZGr9yDED+6AhRbC4GZkBBarxuS5Cb/vMPyFJUJVw=; b=cjUd4wLgtt8GEGz1ZPmueWRecd5wVMu3rw8zoZV3xD7qOywQF45mW/2uC+QTbkIuf/ 78/pmq7ES+xUpWrxIPw6BmcRMGRwFLvug/+R4imH4p/8LrSvEIazXtxgG6E9adlPbhi3 RTYAtMezTOKjJyLtS/gOOwR55uzVfIS768ld8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=YeOPp/xYEezSXaUlAE95Lu6IP/7QoDPsSZGqqUlFl11fFr50Ik4/M2XmD6QYx6eBIw aHFxSXOViyGqTHMxkzn1qJEDoacs/1Bl0yoqlS4wN8HS54Ery955BCdSaauOGuGD1RG8 Yza/sSb49py3cuQ7mIhzsoUOKvgUxqJ5h7D4Y=
MIME-Version: 1.0
Received: by 10.52.0.34 with SMTP id 2mr14634365vdb.9.1299882395425; Fri, 11 Mar 2011 14:26:35 -0800 (PST)
Received: by 10.52.169.35 with HTTP; Fri, 11 Mar 2011 14:26:35 -0800 (PST)
Date: Fri, 11 Mar 2011 14:26:35 -0800
Message-ID: <AANLkTik5HhC9piYN1nShWEtGWnKwH81DLin9C1+m972W@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>, Luca Martini <lmartini@cisco.com>, pwe3 <pwe3@ietf.org>, mpls@ietf.org
Content-Type: multipart/alternative; boundary=20cf3054aa2b6ddb57049e3c7486
Subject: [PWE3] Comments to draft-nadeau-pwe3-vccv-2-01
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 22:25:17 -0000

--20cf3054aa2b6ddb57049e3c7486
Content-Type: text/plain; charset=ISO-8859-1

Dear Authors,
please find my comments below.

   - this proposal is closely related to changes to RFC 5586 put forward in
   draft-lm-pwe3-mpls-tp-gal-in-pw-00 but there's no reference to the draft.
   - RFC 5586 states and the draft-lm-pwe3-mpls-tp-gal-in-pw-00 maintains
   that in MPLS-TP network the GAL must be BoS. Only in non-TP MPLS netowrks
   GAL might be not a BoS. In your proposal the GAL precedes the PW and thus is
   not BoS. But the document's scope is for all MPLS PWs, including over
   MPLS-TP PSN. Unless statement in Section 4.2 RFC 5586 "In MPLS-TP (GAL) ...
   MUST always be at the bottom of the label stack (i.e., S bit set to 1)"
   updated proposed use of GAL is allowed only in non-TP MPLS PSN.
   - Section 2 lists of allowed ACH. Since these are hexadecimal numbers I'd
   suggest prepending them with '0x' to make as "0x07, 0x21, and 0x57". And I'd
   ask for clarification of "allowed". Is it "MAY", "SHOULD" or "MUST" be
   limited to ... A, B, C"?
   - In Section 3 stated that TTL in PW LSE must be set to 1 for SS-PW and
   to appropriate value in MS-PW to reach intended PE. Hence my question, Is
   this mechanism to reach MIP, i.e. S-PE, or this is mechanism to generate
   exception? But that is how PW VCCV Control Channel Type 3 works. What is the
   interpretation of GAL in a label stack? To indicate PW CW after the PW LSE?
   - editorial - in Abstract s/The MPLS/the MPLS or a reference to, perhaps,
   RFC 5654.


Regards,
Greg

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

Dear Authors,<br>please find my comments below.<br><ul><li>this proposal is=
 closely related to changes to RFC 5586 put forward in draft-lm-pwe3-mpls-t=
p-gal-in-pw-00 but there&#39;s no reference to the draft.</li><li>RFC 5586 =
states and the draft-lm-pwe3-mpls-tp-gal-in-pw-00 maintains that in MPLS-TP=
 network the GAL must be BoS. Only in non-TP MPLS netowrks GAL might be not=
 a BoS. In your proposal the GAL precedes the PW and thus is not BoS. But t=
he document&#39;s scope is for all MPLS PWs, including over MPLS-TP PSN. Un=
less statement in Section 4.2 RFC 5586 &quot;In MPLS-TP (GAL) ... MUST alwa=
ys be at the bottom of the label stack   (i.e., S bit set to 1)&quot; updat=
ed proposed use of GAL is allowed only in non-TP MPLS PSN.</li>
<li>Section 2 lists of allowed ACH. Since these are hexadecimal numbers I&#=
39;d suggest prepending them with &#39;0x&#39; to make as &quot;0x07, 0x21,=
 and 0x57&quot;. And I&#39;d ask for clarification of &quot;allowed&quot;. =
Is it &quot;MAY&quot;, &quot;SHOULD&quot; or &quot;MUST&quot; be limited to=
 ... A, B, C&quot;?</li>
<li>In Section 3 stated that TTL in PW LSE must be set to 1 for SS-PW and t=
o appropriate value in MS-PW to reach intended PE. Hence my question, Is th=
is mechanism to reach MIP, i.e. S-PE, or this is mechanism to generate exce=
ption? But that is how PW VCCV Control Channel Type 3 works. What is the in=
terpretation of GAL in a label stack? To indicate PW CW after the PW LSE?</=
li>
<li>editorial - in Abstract s/The MPLS/the MPLS or a reference to, perhaps,=
 RFC 5654.<br></li></ul><br>Regards,<br>Greg<br><br><br><pre><span class=3D=
"h1"><h1><br></h1></span></pre>

--20cf3054aa2b6ddb57049e3c7486--

From aldrin.ietf@gmail.com  Fri Mar 11 16:27:24 2011
Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B90423A67B6 for <pwe3@core3.amsl.com>; Fri, 11 Mar 2011 16:27:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 LJmyIMwCQ0JJ for <pwe3@core3.amsl.com>; Fri, 11 Mar 2011 16:27:24 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id DF2A73A67B2 for <pwe3@ietf.org>; Fri, 11 Mar 2011 16:27:23 -0800 (PST)
Received: by yxk30 with SMTP id 30so1785653yxk.31 for <pwe3@ietf.org>; Fri, 11 Mar 2011 16:28:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:content-type:x-mailer:message-id :date:to:content-transfer-encoding:mime-version; bh=SOjrmYxUAfDE2XD540nBHsZs2VxCicHd61E7KO1uVWg=; b=pra4oB+C7zIU+Y8dJtUM0SF3QCM1gNhPMW8vgb6aIKoSZ6nEis70ayGi3znMUIv7n6 HTXK0qf2zVKMEGPIIYH4+uOM4nDooMP99pw9f4jvhb85F5ekx2GO2BTV2BnQoRCUxPB9 U3fmviDqDExFFTM/Me6MrzzNOc1om9IndePZY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:content-type:x-mailer:message-id:date:to :content-transfer-encoding:mime-version; b=ARiy7AU6yPeGRDHeygi8ZMB/Vunz2+KT78Ae4VhZ4F0hDkH64CGEAtN1lZp4NMG1ip lcG9JSTcBF7ebym9rDCdZNa5gnzxVq3FqDvH4cZbhlRNNWKbYMki9JHPAKGgylk7cd8/ UXwvvs2VMOkOWP9sWNAWpIAAeGiKAaFZJPJS8=
Received: by 10.90.19.32 with SMTP id 32mr563293ags.16.1299889723608; Fri, 11 Mar 2011 16:28:43 -0800 (PST)
Received: from [10.53.102.216] ([166.205.137.194]) by mx.google.com with ESMTPS id 35sm6027668ano.11.2011.03.11.16.28.42 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 11 Mar 2011 16:28:42 -0800 (PST)
From: Sam Aldrin <aldrin.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPhone Mail (8F190)
Message-Id: <65158912-7C9B-4DC1-9AD1-750070ABF591@gmail.com>
Date: Fri, 11 Mar 2011 16:28:35 -0800
To: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (iPhone Mail 8F190)
Subject: [PWE3] draft-nadeau-pwe3-vccv-2-01 - comments
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Mar 2011 00:27:24 -0000

Tom and Luca,

Here are few comments

- the existing format defined in sec 3 will break Mspw. GAL should be bottom=
 of the stack with s bit =3D 1.

- do you plan to add/modify text to rfc6073 sec 9, to highlight the type4 an=
d it's preference?

-sam

Sent from my iPhone=

From Alexander.Vainshtein@ecitele.com  Fri Mar 11 20:43:33 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED87E3A688F; Fri, 11 Mar 2011 20:43:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level: 
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.033,  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 jOVDqHDbc8-I; Fri, 11 Mar 2011 20:43:32 -0800 (PST)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id D63E93A6860; Fri, 11 Mar 2011 20:43:30 -0800 (PST)
X-AuditID: 93eaf2e7-b7ba1ae000007bf7-35-4d7afa384233
Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id D4.C0.31735.83AFA7D4; Sat, 12 Mar 2011 06:44:40 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Sat, 12 Mar 2011 06:44:48 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: venkatesan mahalingam <venkatflex@gmail.com>, "mpls@ietf.org" <mpls@ietf.org>
Date: Sat, 12 Mar 2011 06:44:47 +0200
Thread-Topic: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Thread-Index: AcvgKLRR/QDnyQIyQ9GTo8TU7K+rhgARpxhw
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB3@ILPTMAIL02.ecitele.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com> <4D5E9442.3030101@cisco.com> <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com> <4D7A2439.6010508@cisco.com> <AANLkTim+hqNFHi9xwuzG5_2qoKztEn9SJA9TDh-S-XUo@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D6FBBDD332@ILPTMAIL02.ecitele.com>, <AANLkTiksdHNcsN6PKet48Ps1gDuCWWhcJcaLEQ3npVC+@mail.gmail.com>
In-Reply-To: <AANLkTiksdHNcsN6PKet48Ps1gDuCWWhcJcaLEQ3npVC+@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_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB3ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: Luca Martini <lmartini@cisco.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Mar 2011 04:43:34 -0000

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB3ILPTMAIL02eci_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Venkat,

You have asked "Are we implicitly mandating the CW (ACH) in HW by configuri=
ng/negotiating the CC type-4?"

IMO the answer is "No".
In VCCV Type 1 the first nibble of the CW is a data path (HW if you wish) e=
xception mechanism forwarding the packets to an OAM entity.

In VCCV Type 4 GAL acts as such an exception mechanism. ACH is actually onl=
y needed to decide on the ACH Type. And it would not even be examined if th=
e TTL in the PW label has not expired.

My 2c,
     Sasha



________________________________
From: venkatesan mahalingam [venkatflex@gmail.com]
Sent: Friday, March 11, 2011 10:12 PM
To: Alexander Vainshtein; Greg Mirsky; Luca Martini; lihan@chinamobile.com;=
 mpls-tp@ietf.org; pwe3; HUANG Feng F; mpls@ietf.org
Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

Hi,
AFAIK, ACH can't be used without supporting the CW in HW.

As per RFC-5085, 5.1.1.  In-Band VCCV (Type 1)
CC Type-1 mode of VCCV operation MUST be supported when the control word is=
 present.

It looks to me that CC type-1 for ACH without GAL and CC type-4 for ACH wit=
h GAL.

IMO, if we support CC type-4, CC type-1 support is implicitly attained.

IMHO, it should be possible to get the MPLS-TP OAM control packets with or =
without GAL from HW to CP by negotiating CC type-1 itself.

Some editorial comments for the draft-nadeau-pwe3-vccv-2-01.txt draft,
"
4.1.1.  MPLS VCCV Control Channel (CC) Type 4

   IANA is requested to augment the registry of "MPLS VCCV Control
   Channel Types" with the new type defined below. As defined in
   RFC5058, this new bitfield is to be assigned by IANA using
"
Replace the RFC5058 as RFC5085.

Thanks,
Venkat.

On Fri, Mar 11, 2011 at 2:21 PM, Alexander Vainshtein <Alexander.Vainshtein=
@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
Greg, Luca,
As I=92ve already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO it=
 makes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.

My 2c,
     Sasha

From: mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org> [mailto:mpls-boun=
ces@ietf.org<mailto:mpls-bounces@ietf.org>] On Behalf Of Greg Mirsky
Sent: Friday, March 11, 2011 9:14 PM
To: Luca Martini
Cc: lihan@chinamobile.com<mailto:lihan@chinamobile.com>; mpls@ietf.org<mail=
to:mpls@ietf.org>; pwe3; HUANG Feng F; mpls-tp@ietf.org<mailto:mpls-tp@ietf=
.org>
Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

Dear Luca,
thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. I'll se=
nd my comments to it in a separate e-mail.
I'll have to miss another opportunity to discuss your proposal in a meeting=
. Please add my comments below to my earlier expressed WG LC comments:

 *   the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that ad=
dresses applicability of GAL in PW VCCV, e.g. solution proposed in draft-na=
deau-pwe3-vccv-2-01;
 *   the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such dependenc=
y and refer to any existing proposal;
 *   I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced =
in lock with document that addresses use of GAL in PW VCCV.
Regards,
Greg
On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini <lmartini@cisco.com<mailto:lm=
artini@cisco.com>> wrote:
Greg ,
Some

On 02/18/11 11:15, Greg Mirsky wrote:
> Dear Luca,
> I see at least two issues:
>
>     * use of GAL for PW, in my view, is another VCCV CC type that has
>       to be negotiated as described in RFC 5085.
>
These are valid points, but this document in question does not define,
not discussed VCCV.
We have since posted a draft that proposes a new VCCV mode , and we
welcome comments regarding that document.
(draft-nadeau-pwe3-vccv-2-01.txt)

>     * use of GAL creates ambiguous situation when PW CW is used. The
>       benefit from extending GAL in PW, as I see, is for PWs that are
>       not required to use PW CW. That might be a good enough reason to
>       update RFC 5586 as proposed in the document but we must address
>       use cases of GAL in PWs that require presence PW CW. If we
>       prohibit or even discourage use of GAL for these PWs that have
>       PW VCCV as native Associated Channel, then architecture of ACh
>       for MPLS-TP PW not simplified as result of adopting the proposal.
>
> Regard
Greg,
The GAL is basically a notifier that the packet following the end of the
MPLS label stack, is explicitly defined as a G-ACH format.
Normally the packet would be decoded as an IP packet , unless the last
label on the stack indicated otherwise.

The GAL can certainly be applied  to a PW OAM packet on a PW that uses
the CW, and this document does not define that , nor restricts it.

The scope of this document is limited to removing an unnecessary
restriction in rfc5586, hence  this comment not applicable to this document=
.

Thanks.
Luca

> s,
> Greg
>
> On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com<mailto:=
lmartini@cisco.com>
> <mailto:lmartini@cisco.com<mailto:lmartini@cisco.com>>> wrote:
>
>     Greg,
>
>     Sorry, but I do not remember the point you mention.
>     Can you explain again here ?
>     Thanks.
>     Luca
>
>
>     On 02/17/11 23:47, Greg Mirsky wrote:
>     > Dear Authors and All,
>     > prior to the meeting in Bejing and acceptance of this proposal as W=
G
>     > document Luca and I agreed that use of GAL with PW VCCV presents a
>     > problem.
>     > I was not attending the IETF-79, nor I found discussion of this
>     issue
>     > in the minutes. I think that this issue should be specified,
>     > explained. In my view, this document updates not only RFC 5586
>     > but RFC 5085 too.
>     >
>     > Regards,
>     > Greg
>     >
>     > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>     >
>     > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
>     <lmartini@cisco.com<mailto:lmartini@cisco.com> <mailto:lmartini@cisco=
.com<mailto:lmartini@cisco.com>>
>     > <mailto:lmartini@cisco.com<mailto:lmartini@cisco.com> <mailto:lmart=
ini@cisco.com<mailto:lmartini@cisco.com>>>> wrote:
>     >
>     >     Greg,
>     >
>     >     You are correct , the proposed update does not propose any
>     changes
>     >     to VCCV.
>     >     However the problem with vccv is not as simple as to ask for
>     a new
>     >     code point from IANA.
>     >     Given the good amount of discussion on this point, we should
>     >     probably have a discussion in Beijing.
>     >
>     >     Luca
>     >
>     >
>     >
>     >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
>     >>     Dear Authors,
>     >>     I think that proposed update of the Section 4.2. RFC 5586
>     makes it possible
>     >>     to use GAL on MPLS-TP PW that uses Control Word. I consider
>     it to be
>     >>     conflict between PW VCCV CC types because use of GAL is not
>     negotiated
>     >>     through PW VCCV negotiation. To avoid such situation I propose=
:
>     >>
>     >>        - in Section 5 request IANA to assign new CC Type "MPLS
>     Generic
>     >>        Associated Channel Label"
>     >>        - assign precedence to new CC Type that affects Section
>     7 RFC 5085
>     >>
>     >>     Regards,
>     >>     Greg
>     >>
>     >>
>     >>
>     >>     _______________________________________________
>     >>     mpls mailing list
>     >>     mpls@ietf.org<mailto:mpls@ietf.org> <mailto:mpls@ietf.org<mail=
to:mpls@ietf.org>> <mailto:mpls@ietf.org<mailto:mpls@ietf.org>
>     <mailto:mpls@ietf.org<mailto:mpls@ietf.org>>>
>     >>     https://www.ietf.org/mailman/listinfo/mpls
>     >
>     >
>     >
>     > _______________________________________________
>     > mpls mailing list
>     > mpls@ietf.org<mailto:mpls@ietf.org> <mailto:mpls@ietf.org<mailto:mp=
ls@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




--
Best Regards,
Venkatesan Mahalingam.

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB3ILPTMAIL02eci_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta content=3D"MSHTML 6.00.6000.17063" name=3D"GENERATOR">
<style id=3D"owaTempEditStyle"></style><style title=3D"owaParaStyle"><!--P =
{
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi=3D"x">
<div style=3D"FONT-SIZE: 16px; COLOR: #000000; DIRECTION: ltr; FONT-FAMILY:=
 Times New Roman">
<div><a></a>Venkat<a></a>,</div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">You have asked&nbsp;&quot;Are we implic=
itly mandating the CW (ACH) in HW by configuring/negotiating the CC type-4?=
&quot;</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">IMO the answer is &quot;No&quot;. </fon=
t></div>
<div><font face=3D"times new roman">In VCCV Type 1 the first nibble of the =
CW is a data path (HW if you wish) exception mechanism forwarding the packe=
ts to an OAM entity.</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">In VCCV Type 4 GAL acts as such an exce=
ption mechanism. ACH is actually only needed to decide on the ACH Type. And=
 it&nbsp;would<a></a> not even be examined if the TTL in the PW label has n=
ot expired.</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">My 2c,</font></div>
<div><font face=3D"times new roman">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</font></=
div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"Times New Roman" color=3D"#000000" size=3D"3=
"></font>&nbsp;</div>
<div id=3D"divRpF494853" style=3D"DIRECTION: ltr">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" color=3D"#000000" size=3D"2"><b>From:</b> venkatesan =
mahalingam [venkatflex@gmail.com]<br>
<b>Sent:</b> Friday, March 11, 2011 10:12 PM<br>
<b>To:</b> Alexander Vainshtein; Greg Mirsky; Luca Martini; lihan@chinamobi=
le.com; mpls-tp@ietf.org; pwe3; HUANG Feng F; mpls@ietf.org<br>
<b>Subject:</b> Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br>
</font><br>
</div>
<div></div>
<div>Hi,
<div>
<div>AFAIK, ACH can't be used without supporting the CW in HW.</div>
<div><br>
</div>
<div>As per RFC-5085, 5.1.1. &nbsp;In-Band VCCV (Type 1)</div>
<div>CC Type-1 mode of VCCV operation MUST be supported when the control wo=
rd is present.</div>
<div><br>
</div>
<div>It looks to me that CC type-1 for ACH without GAL and CC type-4 for AC=
H with GAL.</div>
<div><br>
</div>
<div>IMO, if we support CC type-4, CC type-1 support is implicitly attained=
.</div>
<div><br>
</div>
<div>IMHO, it should be possible to get the MPLS-TP OAM control packets wit=
h or without GAL from HW to CP by negotiating CC type-1 itself.</div>
<div><br>
</div>
<div>
<div>Some editorial comments for the draft-nadeau-pwe3-vccv-2-01.txt draft,=
</div>
<div>&quot;</div>
<div>4.1.1. &nbsp;MPLS VCCV Control Channel (CC) Type 4</div>
<div><br>
</div>
<div>&nbsp;&nbsp; IANA is requested to augment the registry of &quot;MPLS V=
CCV Control</div>
<div>&nbsp;&nbsp; Channel Types&quot; with the new type defined below. As d=
efined in</div>
<div>&nbsp;&nbsp; RFC5058, this new bitfield is to be assigned by IANA usin=
g</div>
<div>&quot;</div>
<div>Replace the RFC5058 as RFC5085.</div>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Venkat.</div>
<br>
<div class=3D"gmail_quote">On Fri, Mar 11, 2011 at 2:21 PM, Alexander Vains=
htein <span dir=3D"ltr">
&lt;<a href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshtei=
n@ecitele.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">Greg=
, Luca,</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">As I=
=92ve already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO it mak=
es draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d"></sp=
an>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">My 2=
c,</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d">&nbs=
p;&nbsp;&nbsp;&nbsp; Sasha</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d"></sp=
an>&nbsp;</p>
<div style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: me=
dium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: blue 1.5pt =
solid; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none">
<div>
<div style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b=
5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: mediu=
m none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class=3D"MsoNormal"><b><span style=3D"FONT-SIZE: 10pt">From:</span></b><=
span style=3D"FONT-SIZE: 10pt">
<a href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a> [mailto:=
<a href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a>]
<b>On Behalf Of </b>Greg Mirsky<br>
<b>Sent:</b> Friday, March 11, 2011 9:14 PM<br>
<b>To:</b> Luca Martini<br>
<b>Cc:</b> <a href=3D"mailto:lihan@chinamobile.com">lihan@chinamobile.com</=
a>; <a href=3D"mailto:mpls@ietf.org">
mpls@ietf.org</a>; pwe3; HUANG Feng F; <a href=3D"mailto:mpls-tp@ietf.org">=
mpls-tp@ietf.org</a><br>
<b>Subject:</b> Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt</sp=
an></p>
</div>
</div>
<div>
<div></div>
<div class=3D"h5">
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Dear Luca,<br>
thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. I'll se=
nd my comments to it in a separate e-mail.<br>
I'll have to miss another opportunity to discuss your proposal in a meeting=
. Please add my comments below to my earlier expressed WG LC comments:</p>
<ul type=3D"disc">
<li class=3D"MsoNormal">the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on a=
ny solution that addresses applicability of GAL in PW VCCV, e.g. solution p=
roposed in draft-nadeau-pwe3-vccv-2-01;
</li><li class=3D"MsoNormal">the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs t=
o mention such dependency and refer to any existing proposal;
</li><li class=3D"MsoNormal">I believe that the draft-lm-pwe3-mpls-tp-gal-i=
n-pw-00 can be advanced in lock with document that addresses use of GAL in =
PW VCCV.
</li></ul>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 12pt">Regards,<br>
Greg</p>
<div>
<p class=3D"MsoNormal">On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini &lt;<a=
 href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt; wrote:</p>
<p class=3D"MsoNormal">Greg ,<br>
Some</p>
<div>
<p class=3D"MsoNormal"><br>
On 02/18/11 11:15, Greg Mirsky wrote:<br>
&gt; Dear Luca,<br>
&gt; I see at least two issues:<br>
&gt;<br>
&gt; &nbsp; &nbsp; * use of GAL for PW, in my view, is another VCCV CC type=
 that has<br>
&gt; &nbsp; &nbsp; &nbsp; to be negotiated as described in RFC 5085.<br>
&gt;</p>
</div>
<p class=3D"MsoNormal">These are valid points, but this document in questio=
n does not define,<br>
not discussed VCCV.<br>
We have since posted a draft that proposes a new VCCV mode , and we<br>
welcome comments regarding that document.<br>
(draft-nadeau-pwe3-vccv-2-01.txt)<br>
<br>
&gt; &nbsp; &nbsp; * use of GAL creates ambiguous situation when PW CW is u=
sed. The</p>
<div>
<p class=3D"MsoNormal">&gt; &nbsp; &nbsp; &nbsp; benefit from extending GAL=
 in PW, as I see, is for PWs that are<br>
&gt; &nbsp; &nbsp; &nbsp; not required to use PW CW. That might be a good e=
nough reason to<br>
&gt; &nbsp; &nbsp; &nbsp; update RFC 5586 as proposed in the document but w=
e must address<br>
&gt; &nbsp; &nbsp; &nbsp; use cases of GAL in PWs that require presence PW =
CW. If we<br>
&gt; &nbsp; &nbsp; &nbsp; prohibit or even discourage use of GAL for these =
PWs that have<br>
&gt; &nbsp; &nbsp; &nbsp; PW VCCV as native Associated Channel, then archit=
ecture of ACh<br>
&gt; &nbsp; &nbsp; &nbsp; for MPLS-TP PW not simplified as result of adopti=
ng the proposal.<br>
&gt;<br>
&gt; Regard</p>
</div>
<p class=3D"MsoNormal">Greg,<br>
The GAL is basically a notifier that the packet following the end of the<br=
>
MPLS label stack, is explicitly defined as a G-ACH format.<br>
Normally the packet would be decoded as an IP packet , unless the last<br>
label on the stack indicated otherwise.<br>
<br>
The GAL can certainly be applied &nbsp;to a PW OAM packet on a PW that uses=
<br>
the CW, and this document does not define that , nor restricts it.<br>
<br>
The scope of this document is limited to removing an unnecessary<br>
restriction in rfc5586, hence &nbsp;this comment not applicable to this doc=
ument.<br>
<br>
Thanks.<br>
Luca</p>
<div>
<p class=3D"MsoNormal"><br>
&gt; s,<br>
&gt; Greg<br>
&gt;<br>
&gt; On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini &lt;<a href=3D"mailto:lm=
artini@cisco.com">lmartini@cisco.com</a></p>
</div>
<div>
<p class=3D"MsoNormal">&gt; &lt;mailto:<a href=3D"mailto:lmartini@cisco.com=
">lmartini@cisco.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt; &nbsp; &nbsp; Greg,<br>
&gt;<br>
&gt; &nbsp; &nbsp; Sorry, but I do not remember the point you mention.<br>
&gt; &nbsp; &nbsp; Can you explain again here ?<br>
&gt; &nbsp; &nbsp; Thanks.<br>
&gt; &nbsp; &nbsp; Luca<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; On 02/17/11 23:47, Greg Mirsky wrote:<br>
&gt; &nbsp; &nbsp; &gt; Dear Authors and All,<br>
&gt; &nbsp; &nbsp; &gt; prior to the meeting in Bejing and acceptance of th=
is proposal as WG<br>
&gt; &nbsp; &nbsp; &gt; document Luca and I agreed that use of GAL with PW =
VCCV presents a<br>
&gt; &nbsp; &nbsp; &gt; problem.<br>
&gt; &nbsp; &nbsp; &gt; I was not attending the IETF-79, nor I found discus=
sion of this<br>
&gt; &nbsp; &nbsp; issue<br>
&gt; &nbsp; &nbsp; &gt; in the minutes. I think that this issue should be s=
pecified,<br>
&gt; &nbsp; &nbsp; &gt; explained. In my view, this document updates not on=
ly RFC 5586<br>
&gt; &nbsp; &nbsp; &gt; but RFC 5085 too.<br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt; Regards,<br>
&gt; &nbsp; &nbsp; &gt; Greg<br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt; Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<b=
r>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt; On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini<br>
&gt; &nbsp; &nbsp; &lt;<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco=
.com</a> &lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.co=
m</a>&gt;</p>
</div>
<div>
<div>
<p class=3D"MsoNormal">&gt; &nbsp; &nbsp; &gt; &lt;mailto:<a href=3D"mailto=
:lmartini@cisco.com">lmartini@cisco.com</a> &lt;mailto:<a href=3D"mailto:lm=
artini@cisco.com">lmartini@cisco.com</a>&gt;&gt;&gt; wrote:<br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Greg,<br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; You are correct , the proposed update=
 does not propose any<br>
&gt; &nbsp; &nbsp; changes<br>
&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; to VCCV.<br>
&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; However the problem with vccv is not =
as simple as to ask for<br>
&gt; &nbsp; &nbsp; a new<br>
&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; code point from IANA.<br>
&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Given the good amount of discussion o=
n this point, we should<br>
&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; probably have a discussion in Beijing=
.<br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Luca<br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; On 10/29/2010 05:07 PM, Greg Mirsky w=
rote:<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Dear Authors,<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; I think that proposed update of t=
he Section 4.2. RFC 5586<br>
&gt; &nbsp; &nbsp; makes it possible<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; to use GAL on MPLS-TP PW that use=
s Control Word. I consider<br>
&gt; &nbsp; &nbsp; it to be<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; conflict between PW VCCV CC types=
 because use of GAL is not<br>
&gt; &nbsp; &nbsp; negotiated<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; through PW VCCV negotiation. To a=
void such situation I propose:<br>
&gt; &nbsp; &nbsp; &gt;&gt;<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;- in Section 5 reque=
st IANA to assign new CC Type &quot;MPLS<br>
&gt; &nbsp; &nbsp; Generic<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;Associated Channel L=
abel&quot;<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;- assign precedence =
to new CC Type that affects Section<br>
&gt; &nbsp; &nbsp; 7 RFC 5085<br>
&gt; &nbsp; &nbsp; &gt;&gt;<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Regards,<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Greg<br>
&gt; &nbsp; &nbsp; &gt;&gt;<br>
&gt; &nbsp; &nbsp; &gt;&gt;<br>
&gt; &nbsp; &nbsp; &gt;&gt;<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; _________________________________=
______________<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; mpls mailing list</p>
</div>
</div>
<p class=3D"MsoNormal">&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; <a href=3D=
"mailto:mpls@ietf.org">mpls@ietf.org</a> &lt;mailto:<a href=3D"mailto:mpls@=
ietf.org">mpls@ietf.org</a>&gt; &lt;mailto:<a href=3D"mailto:mpls@ietf.org"=
>mpls@ietf.org</a></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 12pt">&gt; &nbsp; &nbsp; &lt=
;mailto:<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;&gt;<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; <a href=3D"https://www.ietf.org/m=
ailman/listinfo/mpls" target=3D"_blank">
https://www.ietf.org/mailman/listinfo/mpls</a><br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt;<br>
&gt; &nbsp; &nbsp; &gt; _______________________________________________<br>
&gt; &nbsp; &nbsp; &gt; mpls mailing list<br>
&gt; &nbsp; &nbsp; &gt; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> =
&lt;mailto:<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<br>
&gt; &nbsp; &nbsp; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mp=
ls" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>
&gt;<br>
&gt;<br>
<br>
</p>
</div>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
</div>
</div>
</div>
</div>
<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>
</blockquote>
</div>
<br>
<br clear=3D"all">
<br>
-- <br>
Best Regards,<br>
Venkatesan Mahalingam.<br>
</div>
</div>
</div>
</body>
</html>

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB3ILPTMAIL02eci_--

From lamberto.sterling@gmail.com  Sat Mar 12 19:34:56 2011
Return-Path: <lamberto.sterling@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6F573A6AA7; Sat, 12 Mar 2011 19:34:56 -0800 (PST)
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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, 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 RxjaALs0P4S4; Sat, 12 Mar 2011 19:34:53 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 537F93A67FC; Sat, 12 Mar 2011 19:34:52 -0800 (PST)
Received: by bwz13 with SMTP id 13so4078015bwz.31 for <multiple recipients>; Sat, 12 Mar 2011 19:36:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=pvK2MZT2ouEhIqLP89nQ2D5nUAynfHRNHNgMGN12mHo=; b=l4wlgmfqo4tIQBO1LWiwQcU5dItCN2LrVMCJ2RZYQS7bT+UNYT823JUE8wBka0ad2+ JOVnufhz0ByRUW2Q2bDbeAeC+YVc7xK08fQx5X56XBgn6wu83SU5I6ir49/l4wZrJuxo 7jl4xtaXbixR32207upVTXARgVPQouhRj0eFA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=a9AZvQRbUvOFjfvOpPNTPWdHyVL7baVnEVhSbRKZWZ5MeK7W905dAD/WIok5f4iqB7 tEtOOVbcQcnH+7c3kWfWgHd+BEW7kQQ1eybTKjdIQRHHjHCxpUir48DmoQH9fs/JnZYb v/4WpuvI3zcJAabPStoOh+i5VDTiRlyt9c1Hk=
MIME-Version: 1.0
Received: by 10.204.141.14 with SMTP id k14mr5060633bku.37.1299987372957; Sat, 12 Mar 2011 19:36:12 -0800 (PST)
Received: by 10.204.35.65 with HTTP; Sat, 12 Mar 2011 19:36:12 -0800 (PST)
Date: Sun, 13 Mar 2011 04:36:12 +0100
Message-ID: <AANLkTikTscU63fsbww6sOW4K7bvNJeE_vdm6QTVj6TSS@mail.gmail.com>
From: Lamberto Sterling <lamberto.sterling@gmail.com>
To: Alexander.Vainshtein@ecitele.com, Luca Martini <lmartini@cisco.com>
Content-Type: multipart/alternative; boundary=00151759367093e25f049e54e566
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, venkatesan mahalingam <venkatflex@gmail.com>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Mar 2011 03:34:57 -0000

--00151759367093e25f049e54e566
Content-Type: text/plain; charset=ISO-8859-1

Hi all,
I do not see the benefit that GAL in PW can bring while current three CC
type does not own. If there is no agreed benefit, why we add overload to the
indurstry (more HW design), and complexity to the interoperability by
ourself? When IETF refuse draft-bhh-1731 as OAM tool for MPLS-TP, the reason
is again interoperability and indurstry HW cost, and personally agree with
that.

Lamberto



> ------------------------------
>
> Date: Sat, 12 Mar 2011 06:44:47 +0200
> From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
> Subject: Re: [PWE3] [mpls] WG LC
>        draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> To: venkatesan mahalingam <venkatflex@gmail.com>, "mpls@ietf.org"
>        <mpls@ietf.org>
> Cc: Luca Martini <lmartini@cisco.com>, "mpls-tp@ietf.org"
>        <mpls-tp@ietf.org>,     "lihan@chinamobile.com" <
> lihan@chinamobile.com>,
>        pwe3 <pwe3@ietf.org>,   HUANG Feng F <
> Feng.f.Huang@alcatel-sbell.com.cn>
> Message-ID:
>        <A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB3@ILPTMAIL02.ecitele.com>
> Content-Type: text/plain; charset="windows-1252"
>
> Venkat,
>
> You have asked "Are we implicitly mandating the CW (ACH) in HW by
> configuring/negotiating the CC type-4?"
>
> IMO the answer is "No".
> In VCCV Type 1 the first nibble of the CW is a data path (HW if you wish)
> exception mechanism forwarding the packets to an OAM entity.
>
> In VCCV Type 4 GAL acts as such an exception mechanism. ACH is actually
> only needed to decide on the ACH Type. And it would not even be examined if
> the TTL in the PW label has not expired.
>
> My 2c,
>     Sasha
>
>
>
> ________________________________
> From: venkatesan mahalingam [venkatflex@gmail.com]
> Sent: Friday, March 11, 2011 10:12 PM
> To: Alexander Vainshtein; Greg Mirsky; Luca Martini; lihan@chinamobile.com;
> mpls-tp@ietf.org; pwe3; HUANG Feng F; mpls@ietf.org
> Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>
> Hi,
> AFAIK, ACH can't be used without supporting the CW in HW.
>
> As per RFC-5085, 5.1.1.  In-Band VCCV (Type 1)
> CC Type-1 mode of VCCV operation MUST be supported when the control word is
> present.
>
> It looks to me that CC type-1 for ACH without GAL and CC type-4 for ACH
> with GAL.
>
> IMO, if we support CC type-4, CC type-1 support is implicitly attained.
>
> IMHO, it should be possible to get the MPLS-TP OAM control packets with or
> without GAL from HW to CP by negotiating CC type-1 itself.
>
> Some editorial comments for the draft-nadeau-pwe3-vccv-2-01.txt draft,
> "
> 4.1.1.  MPLS VCCV Control Channel (CC) Type 4
>
>   IANA is requested to augment the registry of "MPLS VCCV Control
>   Channel Types" with the new type defined below. As defined in
>   RFC5058, this new bitfield is to be assigned by IANA using
> "
> Replace the RFC5058 as RFC5085.
>
> Thanks,
> Venkat.
>
> On Fri, Mar 11, 2011 at 2:21 PM, Alexander Vainshtein <
> Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>
> wrote:
> Greg, Luca,
> As I?ve already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO it
> makes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.
>
> My 2c,
>     Sasha
>
> From: mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org> [mailto:
> mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org>] On Behalf Of Greg
> Mirsky
> Sent: Friday, March 11, 2011 9:14 PM
> To: Luca Martini
> Cc: lihan@chinamobile.com<mailto:lihan@chinamobile.com>; mpls@ietf.org
> <mailto:mpls@ietf.org>; pwe3; HUANG Feng F; mpls-tp@ietf.org<mailto:
> mpls-tp@ietf.org>
> Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>
> Dear Luca,
> thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. I'll
> send my comments to it in a separate e-mail.
> I'll have to miss another opportunity to discuss your proposal in a
> meeting. Please add my comments below to my earlier expressed WG LC
> comments:
>
>  *   the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that
> addresses applicability of GAL in PW VCCV, e.g. solution proposed in
> draft-nadeau-pwe3-vccv-2-01;
>  *   the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such
> dependency and refer to any existing proposal;
>  *   I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced
> in lock with document that addresses use of GAL in PW VCCV.
> Regards,
> Greg
> On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini <lmartini@cisco.com<mailto:
> lmartini@cisco.com>> wrote:
> Greg ,
> Some
>
> On 02/18/11 11:15, Greg Mirsky wrote:
> > Dear Luca,
> > I see at least two issues:
> >
> >     * use of GAL for PW, in my view, is another VCCV CC type that has
> >       to be negotiated as described in RFC 5085.
> >
> These are valid points, but this document in question does not define,
> not discussed VCCV.
> We have since posted a draft that proposes a new VCCV mode , and we
> welcome comments regarding that document.
> (draft-nadeau-pwe3-vccv-2-01.txt)
>
> >     * use of GAL creates ambiguous situation when PW CW is used. The
> >       benefit from extending GAL in PW, as I see, is for PWs that are
> >       not required to use PW CW. That might be a good enough reason to
> >       update RFC 5586 as proposed in the document but we must address
> >       use cases of GAL in PWs that require presence PW CW. If we
> >       prohibit or even discourage use of GAL for these PWs that have
> >       PW VCCV as native Associated Channel, then architecture of ACh
> >       for MPLS-TP PW not simplified as result of adopting the proposal.
> >
> > Regard
> Greg,
> The GAL is basically a notifier that the packet following the end of the
> MPLS label stack, is explicitly defined as a G-ACH format.
> Normally the packet would be decoded as an IP packet , unless the last
> label on the stack indicated otherwise.
>
> The GAL can certainly be applied  to a PW OAM packet on a PW that uses
> the CW, and this document does not define that , nor restricts it.
>
> The scope of this document is limited to removing an unnecessary
> restriction in rfc5586, hence  this comment not applicable to this
> document.
>
> Thanks.
> Luca
>
> > s,
> > Greg
> >
> > On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com
> <mailto:lmartini@cisco.com>
> > <mailto:lmartini@cisco.com<mailto:lmartini@cisco.com>>> wrote:
> >
> >     Greg,
> >
> >     Sorry, but I do not remember the point you mention.
> >     Can you explain again here ?
> >     Thanks.
> >     Luca
> >
> >
> >     On 02/17/11 23:47, Greg Mirsky wrote:
> >     > Dear Authors and All,
> >     > prior to the meeting in Bejing and acceptance of this proposal as
> WG
> >     > document Luca and I agreed that use of GAL with PW VCCV presents a
> >     > problem.
> >     > I was not attending the IETF-79, nor I found discussion of this
> >     issue
> >     > in the minutes. I think that this issue should be specified,
> >     > explained. In my view, this document updates not only RFC 5586
> >     > but RFC 5085 too.
> >     >
> >     > Regards,
> >     > Greg
> >     >
> >     > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> >     >
> >     > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
> >     <lmartini@cisco.com<mailto:lmartini@cisco.com> <mailto:
> lmartini@cisco.com<mailto:lmartini@cisco.com>>
> >     > <mailto:lmartini@cisco.com<mailto:lmartini@cisco.com> <mailto:
> lmartini@cisco.com<mailto:lmartini@cisco.com>>>> wrote:
> >     >
> >     >     Greg,
> >     >
> >     >     You are correct , the proposed update does not propose any
> >     changes
> >     >     to VCCV.
> >     >     However the problem with vccv is not as simple as to ask for
> >     a new
> >     >     code point from IANA.
> >     >     Given the good amount of discussion on this point, we should
> >     >     probably have a discussion in Beijing.
> >     >
> >     >     Luca
> >     >
> >     >
> >     >
> >     >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
> >     >>     Dear Authors,
> >     >>     I think that proposed update of the Section 4.2. RFC 5586
> >     makes it possible
> >     >>     to use GAL on MPLS-TP PW that uses Control Word. I consider
> >     it to be
> >     >>     conflict between PW VCCV CC types because use of GAL is not
> >     negotiated
> >     >>     through PW VCCV negotiation. To avoid such situation I
> propose:
> >     >>
> >     >>        - in Section 5 request IANA to assign new CC Type "MPLS
> >     Generic
> >     >>        Associated Channel Label"
> >     >>        - assign precedence to new CC Type that affects Section
> >     7 RFC 5085
> >     >>
> >     >>     Regards,
> >     >>     Greg
> >     >>
> >     >>
> >     >>

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

<div>Hi all,</div>
<div>I do not see the benefit that GAL in PW can bring while current three =
CC type does not own. If there is no agreed benefit, why we add overload to=
 the indurstry (more HW design), and complexity to the interoperability by =
ourself? When IETF refuse draft-bhh-1731 as OAM tool for MPLS-TP, the reaso=
n is again interoperability and indurstry HW cost, and personally agree wit=
h that.</div>

<div>=A0</div>
<div>Lamberto</div>
<div><br>=A0</div>
<div class=3D"gmail_quote">
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">------------------------------<b=
r><br>Date: Sat, 12 Mar 2011 06:44:47 +0200<br>From: Alexander Vainshtein &=
lt;<a href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshtein=
@ecitele.com</a>&gt;<br>
Subject: Re: [PWE3] [mpls] WG LC<br>=A0 =A0 =A0 =A0draft-lm-pwe3-mpls-tp-ga=
l-in-pw-00.txt<br>To: venkatesan mahalingam &lt;<a href=3D"mailto:venkatfle=
x@gmail.com">venkatflex@gmail.com</a>&gt;, &quot;<a href=3D"mailto:mpls@iet=
f.org">mpls@ietf.org</a>&quot;<br>
=A0 =A0 =A0 =A0&lt;<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<b=
r>Cc: Luca Martini &lt;<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco=
.com</a>&gt;, &quot;<a href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a=
>&quot;<br>
=A0 =A0 =A0 =A0&lt;<a href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a>=
&gt;, =A0 =A0 &quot;<a href=3D"mailto:lihan@chinamobile.com">lihan@chinamob=
ile.com</a>&quot; &lt;<a href=3D"mailto:lihan@chinamobile.com">lihan@chinam=
obile.com</a>&gt;,<br>
=A0 =A0 =A0 =A0pwe3 &lt;<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a>&=
gt;, =A0 HUANG Feng F &lt;<a href=3D"mailto:Feng.f.Huang@alcatel-sbell.com.=
cn">Feng.f.Huang@alcatel-sbell.com.cn</a>&gt;<br>Message-ID:<br>=A0 =A0 =A0=
 =A0&lt;<a href=3D"mailto:A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB3@ILPTMA=
IL02.ecitele.com">A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB3@ILPTMAIL02.eci=
tele.com</a>&gt;<br>
Content-Type: text/plain; charset=3D&quot;windows-1252&quot;<br><br>Venkat,=
<br><br>You have asked &quot;Are we implicitly mandating the CW (ACH) in HW=
 by configuring/negotiating the CC type-4?&quot;<br><br>IMO the answer is &=
quot;No&quot;.<br>
In VCCV Type 1 the first nibble of the CW is a data path (HW if you wish) e=
xception mechanism forwarding the packets to an OAM entity.<br><br>In VCCV =
Type 4 GAL acts as such an exception mechanism. ACH is actually only needed=
 to decide on the ACH Type. And it would not even be examined if the TTL in=
 the PW label has not expired.<br>
<br>My 2c,<br>=A0 =A0 Sasha<br><br><br><br>________________________________=
<br>From: venkatesan mahalingam [<a href=3D"mailto:venkatflex@gmail.com">ve=
nkatflex@gmail.com</a>]<br>Sent: Friday, March 11, 2011 10:12 PM<br>To: Ale=
xander Vainshtein; Greg Mirsky; Luca Martini; <a href=3D"mailto:lihan@china=
mobile.com">lihan@chinamobile.com</a>; <a href=3D"mailto:mpls-tp@ietf.org">=
mpls-tp@ietf.org</a>; pwe3; HUANG Feng F; <a href=3D"mailto:mpls@ietf.org">=
mpls@ietf.org</a><br>
Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br><br>Hi,=
<br>AFAIK, ACH can&#39;t be used without supporting the CW in HW.<br><br>As=
 per RFC-5085, 5.1.1. =A0In-Band VCCV (Type 1)<br>CC Type-1 mode of VCCV op=
eration MUST be supported when the control word is present.<br>
<br>It looks to me that CC type-1 for ACH without GAL and CC type-4 for ACH=
 with GAL.<br><br>IMO, if we support CC type-4, CC type-1 support is implic=
itly attained.<br><br>IMHO, it should be possible to get the MPLS-TP OAM co=
ntrol packets with or without GAL from HW to CP by negotiating CC type-1 it=
self.<br>
<br>Some editorial comments for the draft-nadeau-pwe3-vccv-2-01.txt draft,<=
br>&quot;<br>4.1.1. =A0MPLS VCCV Control Channel (CC) Type 4<br><br>=A0 IAN=
A is requested to augment the registry of &quot;MPLS VCCV Control<br>=A0 Ch=
annel Types&quot; with the new type defined below. As defined in<br>
=A0 RFC5058, this new bitfield is to be assigned by IANA using<br>&quot;<br=
>Replace the RFC5058 as RFC5085.<br><br>Thanks,<br>Venkat.<br><br>On Fri, M=
ar 11, 2011 at 2:21 PM, Alexander Vainshtein &lt;<a href=3D"mailto:Alexande=
r.Vainshtein@ecitele.com">Alexander.Vainshtein@ecitele.com</a>&lt;mailto:<a=
 href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshtein@ecit=
ele.com</a>&gt;&gt; wrote:<br>
Greg, Luca,<br>As I?ve already stated in my comment on draft-nadeau-pwe3-vc=
cv-2, IMHO it makes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.<br>=
<br>My 2c,<br>=A0 =A0 Sasha<br><br>From: <a href=3D"mailto:mpls-bounces@iet=
f.org">mpls-bounces@ietf.org</a>&lt;mailto:<a href=3D"mailto:mpls-bounces@i=
etf.org">mpls-bounces@ietf.org</a>&gt; [mailto:<a href=3D"mailto:mpls-bounc=
es@ietf.org">mpls-bounces@ietf.org</a>&lt;mailto:<a href=3D"mailto:mpls-bou=
nces@ietf.org">mpls-bounces@ietf.org</a>&gt;] On Behalf Of Greg Mirsky<br>
Sent: Friday, March 11, 2011 9:14 PM<br>To: Luca Martini<br>Cc: <a href=3D"=
mailto:lihan@chinamobile.com">lihan@chinamobile.com</a>&lt;mailto:<a href=
=3D"mailto:lihan@chinamobile.com">lihan@chinamobile.com</a>&gt;; <a href=3D=
"mailto:mpls@ietf.org">mpls@ietf.org</a>&lt;mailto:<a href=3D"mailto:mpls@i=
etf.org">mpls@ietf.org</a>&gt;; pwe3; HUANG Feng F; <a href=3D"mailto:mpls-=
tp@ietf.org">mpls-tp@ietf.org</a>&lt;mailto:<a href=3D"mailto:mpls-tp@ietf.=
org">mpls-tp@ietf.org</a>&gt;<br>
Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br><br>Dea=
r Luca,<br>thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attenti=
on. I&#39;ll send my comments to it in a separate e-mail.<br>I&#39;ll have =
to miss another opportunity to discuss your proposal in a meeting. Please a=
dd my comments below to my earlier expressed WG LC comments:<br>
<br>=A0* =A0 the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution=
 that addresses applicability of GAL in PW VCCV, e.g. solution proposed in =
draft-nadeau-pwe3-vccv-2-01;<br>=A0* =A0 the draft-lm-pwe3-mpls-tp-gal-in-p=
w-00 needs to mention such dependency and refer to any existing proposal;<b=
r>
=A0* =A0 I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advan=
ced in lock with document that addresses use of GAL in PW VCCV.<br>Regards,=
<br>Greg<br>On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini &lt;<a href=3D"ma=
ilto:lmartini@cisco.com">lmartini@cisco.com</a>&lt;mailto:<a href=3D"mailto=
:lmartini@cisco.com">lmartini@cisco.com</a>&gt;&gt; wrote:<br>
Greg ,<br>Some<br><br>On 02/18/11 11:15, Greg Mirsky wrote:<br>&gt; Dear Lu=
ca,<br>&gt; I see at least two issues:<br>&gt;<br>&gt; =A0 =A0 * use of GAL=
 for PW, in my view, is another VCCV CC type that has<br>&gt; =A0 =A0 =A0 t=
o be negotiated as described in RFC 5085.<br>
&gt;<br>These are valid points, but this document in question does not defi=
ne,<br>not discussed VCCV.<br>We have since posted a draft that proposes a =
new VCCV mode , and we<br>welcome comments regarding that document.<br>
(draft-nadeau-pwe3-vccv-2-01.txt)<br><br>&gt; =A0 =A0 * use of GAL creates =
ambiguous situation when PW CW is used. The<br>&gt; =A0 =A0 =A0 benefit fro=
m extending GAL in PW, as I see, is for PWs that are<br>&gt; =A0 =A0 =A0 no=
t required to use PW CW. That might be a good enough reason to<br>
&gt; =A0 =A0 =A0 update RFC 5586 as proposed in the document but we must ad=
dress<br>&gt; =A0 =A0 =A0 use cases of GAL in PWs that require presence PW =
CW. If we<br>&gt; =A0 =A0 =A0 prohibit or even discourage use of GAL for th=
ese PWs that have<br>
&gt; =A0 =A0 =A0 PW VCCV as native Associated Channel, then architecture of=
 ACh<br>&gt; =A0 =A0 =A0 for MPLS-TP PW not simplified as result of adoptin=
g the proposal.<br>&gt;<br>&gt; Regard<br>Greg,<br>The GAL is basically a n=
otifier that the packet following the end of the<br>
MPLS label stack, is explicitly defined as a G-ACH format.<br>Normally the =
packet would be decoded as an IP packet , unless the last<br>label on the s=
tack indicated otherwise.<br><br>The GAL can certainly be applied =A0to a P=
W OAM packet on a PW that uses<br>
the CW, and this document does not define that , nor restricts it.<br><br>T=
he scope of this document is limited to removing an unnecessary<br>restrict=
ion in rfc5586, hence =A0this comment not applicable to this document.<br>
<br>Thanks.<br>Luca<br><br>&gt; s,<br>&gt; Greg<br>&gt;<br>&gt; On Fri, Feb=
 18, 2011 at 7:46 AM, Luca Martini &lt;<a href=3D"mailto:lmartini@cisco.com=
">lmartini@cisco.com</a>&lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lm=
artini@cisco.com</a>&gt;<br>
&gt; &lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a=
>&lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt=
;&gt;&gt; wrote:<br>&gt;<br>&gt; =A0 =A0 Greg,<br>&gt;<br>&gt; =A0 =A0 Sorr=
y, but I do not remember the point you mention.<br>
&gt; =A0 =A0 Can you explain again here ?<br>&gt; =A0 =A0 Thanks.<br>&gt; =
=A0 =A0 Luca<br>&gt;<br>&gt;<br>&gt; =A0 =A0 On 02/17/11 23:47, Greg Mirsky=
 wrote:<br>&gt; =A0 =A0 &gt; Dear Authors and All,<br>&gt; =A0 =A0 &gt; pri=
or to the meeting in Bejing and acceptance of this proposal as WG<br>
&gt; =A0 =A0 &gt; document Luca and I agreed that use of GAL with PW VCCV p=
resents a<br>&gt; =A0 =A0 &gt; problem.<br>&gt; =A0 =A0 &gt; I was not atte=
nding the IETF-79, nor I found discussion of this<br>&gt; =A0 =A0 issue<br>=
&gt; =A0 =A0 &gt; in the minutes. I think that this issue should be specifi=
ed,<br>
&gt; =A0 =A0 &gt; explained. In my view, this document updates not only RFC=
 5586<br>&gt; =A0 =A0 &gt; but RFC 5085 too.<br>&gt; =A0 =A0 &gt;<br>&gt; =
=A0 =A0 &gt; Regards,<br>&gt; =A0 =A0 &gt; Greg<br>&gt; =A0 =A0 &gt;<br>&gt=
; =A0 =A0 &gt; Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br>
&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt; On Sat, Oct 30, 2010 at 10:14 AM, Lu=
ca Martini<br>&gt; =A0 =A0 &lt;<a href=3D"mailto:lmartini@cisco.com">lmarti=
ni@cisco.com</a>&lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini@c=
isco.com</a>&gt; &lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini@=
cisco.com</a>&lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini@cisc=
o.com</a>&gt;&gt;<br>
&gt; =A0 =A0 &gt; &lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini=
@cisco.com</a>&lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini@cis=
co.com</a>&gt; &lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini@ci=
sco.com</a>&lt;mailto:<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.=
com</a>&gt;&gt;&gt;&gt; wrote:<br>
&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt; =A0 =A0 Greg,<br>&gt; =A0 =A0 &gt;<b=
r>&gt; =A0 =A0 &gt; =A0 =A0 You are correct , the proposed update does not =
propose any<br>&gt; =A0 =A0 changes<br>&gt; =A0 =A0 &gt; =A0 =A0 to VCCV.<b=
r>&gt; =A0 =A0 &gt; =A0 =A0 However the problem with vccv is not as simple =
as to ask for<br>
&gt; =A0 =A0 a new<br>&gt; =A0 =A0 &gt; =A0 =A0 code point from IANA.<br>&g=
t; =A0 =A0 &gt; =A0 =A0 Given the good amount of discussion on this point, =
we should<br>&gt; =A0 =A0 &gt; =A0 =A0 probably have a discussion in Beijin=
g.<br>&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt; =A0 =A0 Luca<br>
&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0 &gt;<br>&gt; =A0 =A0=
 &gt; =A0 =A0 On 10/29/2010 05:07 PM, Greg Mirsky wrote:<br>&gt; =A0 =A0 &g=
t;&gt; =A0 =A0 Dear Authors,<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 I think that =
proposed update of the Section 4.2. RFC 5586<br>
&gt; =A0 =A0 makes it possible<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 to use GAL =
on MPLS-TP PW that uses Control Word. I consider<br>&gt; =A0 =A0 it to be<b=
r>&gt; =A0 =A0 &gt;&gt; =A0 =A0 conflict between PW VCCV CC types because u=
se of GAL is not<br>
&gt; =A0 =A0 negotiated<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 through PW VCCV ne=
gotiation. To avoid such situation I propose:<br>&gt; =A0 =A0 &gt;&gt;<br>&=
gt; =A0 =A0 &gt;&gt; =A0 =A0 =A0 =A0- in Section 5 request IANA to assign n=
ew CC Type &quot;MPLS<br>
&gt; =A0 =A0 Generic<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 =A0 =A0Associated Cha=
nnel Label&quot;<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 =A0 =A0- assign precedenc=
e to new CC Type that affects Section<br>&gt; =A0 =A0 7 RFC 5085<br>&gt; =
=A0 =A0 &gt;&gt;<br>&gt; =A0 =A0 &gt;&gt; =A0 =A0 Regards,<br>
&gt; =A0 =A0 &gt;&gt; =A0 =A0 Greg<br>&gt; =A0 =A0 &gt;&gt;<br>&gt; =A0 =A0=
 &gt;&gt;<br>&gt; =A0 =A0 &gt;&gt;</blockquote></div>

--00151759367093e25f049e54e566--

From hffellow@hotmail.com  Sun Mar 13 20:17:52 2011
Return-Path: <hffellow@hotmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C0143A6C0D; Sun, 13 Mar 2011 20:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.848
X-Spam-Level: *
X-Spam-Status: No, score=1.848 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, MIME_CHARSET_FARAWAY=2.45, 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 BPPV597yg-hA; Sun, 13 Mar 2011 20:17:50 -0700 (PDT)
Received: from blu0-omc2-s7.blu0.hotmail.com (blu0-omc2-s7.blu0.hotmail.com [65.55.111.82]) by core3.amsl.com (Postfix) with ESMTP id 97C8C3A6AB7; Sun, 13 Mar 2011 20:17:50 -0700 (PDT)
Received: from BLU0-SMTP161 ([65.55.111.71]) by blu0-omc2-s7.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 13 Mar 2011 20:19:13 -0700
X-Originating-IP: [112.64.190.32]
X-Originating-Email: [hffellow@hotmail.com]
Message-ID: <BLU0-SMTP161B3504EFD3D201F43F492DACC0@phx.gbl>
Received: from [172.18.10.66] ([112.64.190.32]) by BLU0-SMTP161.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Sun, 13 Mar 2011 20:19:00 -0700
References: <AANLkTikTscU63fsbww6sOW4K7bvNJeE_vdm6QTVj6TSS@mail.gmail.com>
In-Reply-To: <AANLkTikTscU63fsbww6sOW4K7bvNJeE_vdm6QTVj6TSS@mail.gmail.com>
MIME-Version: 1.0 (iPhone Mail 8C148)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="Apple-Mail-1--356993280"
X-Mailer: iPhone Mail (8C148)
From: Huang Feng <hffellow@hotmail.com>
Date: Mon, 14 Mar 2011 11:18:56 +0800
To: Lamberto Sterling <lamberto.sterling@gmail.com>
X-OriginalArrivalTime: 14 Mar 2011 03:19:09.0374 (UTC) FILETIME=[955485E0:01CBE1F6]
X-Mailman-Approved-At: Mon, 14 Mar 2011 08:22:54 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, Luca Martini <lmartini@cisco.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>
Subject: Re: [PWE3] [mpls]   WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 03:17:52 -0000

--Apple-Mail-1--356993280
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="GB2312"

Support GAL both in LSP and PW=A3=ACcommon HW can be used, it save cost.

BR
Feng

=D4=DA 2011-3-13=A3=AC11:36=A3=ACLamberto Sterling <lamberto.sterling@gmail.=
com> =D0=B4=B5=C0=A3=BA

> Hi all,
> I do not see the benefit that GAL in PW can bring while current three CC t=
ype does not own. If there is no agreed benefit, why we add overload to the i=
ndurstry (more HW design), and complexity to the interoperability by ourself=
? When IETF refuse draft-bhh-1731 as OAM tool for MPLS-TP, the reason is aga=
in interoperability and indurstry HW cost, and personally agree with that.
> =20
> Lamberto
>=20
> =20
> ------------------------------
>=20
> Date: Sat, 12 Mar 2011 06:44:47 +0200
> From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
> Subject: Re: [PWE3] [mpls] WG LC
>        draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> To: venkatesan mahalingam <venkatflex@gmail.com>, "mpls@ietf.org"
>        <mpls@ietf.org>
> Cc: Luca Martini <lmartini@cisco.com>, "mpls-tp@ietf.org"
>        <mpls-tp@ietf.org>,     "lihan@chinamobile.com" <lihan@chinamobile.=
com>,
>        pwe3 <pwe3@ietf.org>,   HUANG Feng F <Feng.f.Huang@alcatel-sbell.co=
m.cn>
> Message-ID:
>        <A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB3@ILPTMAIL02.ecitele.com>=

> Content-Type: text/plain; charset=3D"windows-1252"
>=20
> Venkat,
>=20
> You have asked "Are we implicitly mandating the CW (ACH) in HW by configur=
ing/negotiating the CC type-4?"
>=20
> IMO the answer is "No".
> In VCCV Type 1 the first nibble of the CW is a data path (HW if you wish) e=
xception mechanism forwarding the packets to an OAM entity.
>=20
> In VCCV Type 4 GAL acts as such an exception mechanism. ACH is actually on=
ly needed to decide on the ACH Type. And it would not even be examined if th=
e TTL in the PW label has not expired.
>=20
> My 2c,
>     Sasha
>=20
>=20
>=20
> ________________________________
> From: venkatesan mahalingam [venkatflex@gmail.com]
> Sent: Friday, March 11, 2011 10:12 PM
> To: Alexander Vainshtein; Greg Mirsky; Luca Martini; lihan@chinamobile.com=
; mpls-tp@ietf.org; pwe3; HUANG Feng F; mpls@ietf.org
> Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>=20
> Hi,
> AFAIK, ACH can't be used without supporting the CW in HW.
>=20
> As per RFC-5085, 5.1.1.  In-Band VCCV (Type 1)
> CC Type-1 mode of VCCV operation MUST be supported when the control word i=
s present.
>=20
> It looks to me that CC type-1 for ACH without GAL and CC type-4 for ACH wi=
th GAL.
>=20
> IMO, if we support CC type-4, CC type-1 support is implicitly attained.
>=20
> IMHO, it should be possible to get the MPLS-TP OAM control packets with or=
 without GAL from HW to CP by negotiating CC type-1 itself.
>=20
> Some editorial comments for the draft-nadeau-pwe3-vccv-2-01.txt draft,
> "
> 4.1.1.  MPLS VCCV Control Channel (CC) Type 4
>=20
>   IANA is requested to augment the registry of "MPLS VCCV Control
>   Channel Types" with the new type defined below. As defined in
>   RFC5058, this new bitfield is to be assigned by IANA using
> "
> Replace the RFC5058 as RFC5085.
>=20
> Thanks,
> Venkat.
>=20
> On Fri, Mar 11, 2011 at 2:21 PM, Alexander Vainshtein <Alexander.Vainshtei=
n@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
> Greg, Luca,
> As I?ve already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO it m=
akes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.
>=20
> My 2c,
>     Sasha
>=20
> From: mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org> [mailto:mpls-bou=
nces@ietf.org<mailto:mpls-bounces@ietf.org>] On Behalf Of Greg Mirsky
> Sent: Friday, March 11, 2011 9:14 PM
> To: Luca Martini
> Cc: lihan@chinamobile.com<mailto:lihan@chinamobile.com>; mpls@ietf.org<mai=
lto:mpls@ietf.org>; pwe3; HUANG Feng F; mpls-tp@ietf.org<mailto:mpls-tp@ietf=
.org>
> Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>=20
> Dear Luca,
> thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. I'll s=
end my comments to it in a separate e-mail.
> I'll have to miss another opportunity to discuss your proposal in a meetin=
g. Please add my comments below to my earlier expressed WG LC comments:
>=20
>  *   the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that a=
ddresses applicability of GAL in PW VCCV, e.g. solution proposed in draft-na=
deau-pwe3-vccv-2-01;
>  *   the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such dependen=
cy and refer to any existing proposal;
>  *   I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced=
 in lock with document that addresses use of GAL in PW VCCV.
> Regards,
> Greg
> On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini <lmartini@cisco.com<mailto:l=
martini@cisco.com>> wrote:
> Greg ,
> Some
>=20
> On 02/18/11 11:15, Greg Mirsky wrote:
> > Dear Luca,
> > I see at least two issues:
> >
> >     * use of GAL for PW, in my view, is another VCCV CC type that has
> >       to be negotiated as described in RFC 5085.
> >
> These are valid points, but this document in question does not define,
> not discussed VCCV.
> We have since posted a draft that proposes a new VCCV mode , and we
> welcome comments regarding that document.
> (draft-nadeau-pwe3-vccv-2-01.txt)
>=20
> >     * use of GAL creates ambiguous situation when PW CW is used. The
> >       benefit from extending GAL in PW, as I see, is for PWs that are
> >       not required to use PW CW. That might be a good enough reason to
> >       update RFC 5586 as proposed in the document but we must address
> >       use cases of GAL in PWs that require presence PW CW. If we
> >       prohibit or even discourage use of GAL for these PWs that have
> >       PW VCCV as native Associated Channel, then architecture of ACh
> >       for MPLS-TP PW not simplified as result of adopting the proposal.
> >
> > Regard
> Greg,
> The GAL is basically a notifier that the packet following the end of the
> MPLS label stack, is explicitly defined as a G-ACH format.
> Normally the packet would be decoded as an IP packet , unless the last
> label on the stack indicated otherwise.
>=20
> The GAL can certainly be applied  to a PW OAM packet on a PW that uses
> the CW, and this document does not define that , nor restricts it.
>=20
> The scope of this document is limited to removing an unnecessary
> restriction in rfc5586, hence  this comment not applicable to this documen=
t.
>=20
> Thanks.
> Luca
>=20
> > s,
> > Greg
> >
> > On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com<mailto=
:lmartini@cisco.com>
> > <mailto:lmartini@cisco.com<mailto:lmartini@cisco.com>>> wrote:
> >
> >     Greg,
> >
> >     Sorry, but I do not remember the point you mention.
> >     Can you explain again here ?
> >     Thanks.
> >     Luca
> >
> >
> >     On 02/17/11 23:47, Greg Mirsky wrote:
> >     > Dear Authors and All,
> >     > prior to the meeting in Bejing and acceptance of this proposal as W=
G
> >     > document Luca and I agreed that use of GAL with PW VCCV presents a=

> >     > problem.
> >     > I was not attending the IETF-79, nor I found discussion of this
> >     issue
> >     > in the minutes. I think that this issue should be specified,
> >     > explained. In my view, this document updates not only RFC 5586
> >     > but RFC 5085 too.
> >     >
> >     > Regards,
> >     > Greg
> >     >
> >     > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> >     >
> >     > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
> >     <lmartini@cisco.com<mailto:lmartini@cisco.com> <mailto:lmartini@cisc=
o.com<mailto:lmartini@cisco.com>>
> >     > <mailto:lmartini@cisco.com<mailto:lmartini@cisco.com> <mailto:lmar=
tini@cisco.com<mailto:lmartini@cisco.com>>>> wrote:
> >     >
> >     >     Greg,
> >     >
> >     >     You are correct , the proposed update does not propose any
> >     changes
> >     >     to VCCV.
> >     >     However the problem with vccv is not as simple as to ask for
> >     a new
> >     >     code point from IANA.
> >     >     Given the good amount of discussion on this point, we should
> >     >     probably have a discussion in Beijing.
> >     >
> >     >     Luca
> >     >
> >     >
> >     >
> >     >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
> >     >>     Dear Authors,
> >     >>     I think that proposed update of the Section 4.2. RFC 5586
> >     makes it possible
> >     >>     to use GAL on MPLS-TP PW that uses Control Word. I consider
> >     it to be
> >     >>     conflict between PW VCCV CC types because use of GAL is not
> >     negotiated
> >     >>     through PW VCCV negotiation. To avoid such situation I propos=
e:
> >     >>
> >     >>        - in Section 5 request IANA to assign new CC Type "MPLS
> >     Generic
> >     >>        Associated Channel Label"
> >     >>        - assign precedence to new CC Type that affects Section
> >     7 RFC 5085
> >     >>
> >     >>     Regards,
> >     >>     Greg
> >     >>
> >     >>
> >     >>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

--Apple-Mail-1--356993280
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html><body bgcolor=3D"#FFFFFF"><div>Support GAL both in LSP and PW=EF=BC=8C=
common HW can be used, it save cost.<br><span class=3D"Apple-style-span" sty=
le=3D"-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-compo=
sition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-=
color: rgba(77, 128, 180, 0.230469);"><br></span></div><div><span class=3D"A=
pple-style-span" style=3D"-webkit-tap-highlight-color: rgba(26, 26, 26, 0.29=
6875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webki=
t-composition-frame-color: rgba(77, 128, 180, 0.230469);">BR</span></div><di=
v><span class=3D"Apple-style-span" style=3D"-webkit-tap-highlight-color: rgb=
a(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227,=
 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);">=
Feng</span></div><div><br>=E5=9C=A8 2011-3-13=EF=BC=8C11:36=EF=BC=8CLamberto=
 Sterling &lt;<a href=3D"mailto:lamberto.sterling@gmail.com">lamberto.sterli=
ng@gmail.com</a>&gt; =E5=86=99=E9=81=93=EF=BC=9A<br><br></div><div></div><bl=
ockquote type=3D"cite"><div><div>Hi all,</div>
<div>I do not see the benefit that GAL in PW can bring while current three C=
C type does not own. If there is no agreed benefit, why we add overload to t=
he indurstry (more HW design), and complexity to the interoperability by our=
self? When IETF refuse draft-bhh-1731 as OAM tool for MPLS-TP, the reason is=
 again interoperability and indurstry HW cost, and personally agree with tha=
t.</div>

<div>&nbsp;</div>
<div>Lamberto</div>
<div><br>&nbsp;</div>
<div class=3D"gmail_quote">
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex;=
 PADDING-LEFT: 1ex" class=3D"gmail_quote">------------------------------<br>=
<br>Date: Sat, 12 Mar 2011 06:44:47 +0200<br>From: Alexander Vainshtein &lt;=
<a href=3D"mailto:Alexander.Vainshtein@ecitele.com"><a href=3D"mailto:Alexan=
der.Vainshtein@ecitele.com">Alexander.Vainshtein@ecitele.com</a></a>&gt;<br>=

Subject: Re: [PWE3] [mpls] WG LC<br>&nbsp; &nbsp; &nbsp; &nbsp;draft-lm-pwe3=
-mpls-tp-gal-in-pw-00.txt<br>To: venkatesan mahalingam &lt;<a href=3D"mailto=
:venkatflex@gmail.com"><a href=3D"mailto:venkatflex@gmail.com">venkatflex@gm=
ail.com</a></a>&gt;, "<a href=3D"mailto:mpls@ietf.org"><a href=3D"mailto:mpl=
s@ietf.org">mpls@ietf.org</a></a>"<br>
&nbsp; &nbsp; &nbsp; &nbsp;&lt;<a href=3D"mailto:mpls@ietf.org"><a href=3D"m=
ailto:mpls@ietf.org">mpls@ietf.org</a></a>&gt;<br>Cc: Luca Martini &lt;<a hr=
ef=3D"mailto:lmartini@cisco.com"><a href=3D"mailto:lmartini@cisco.com">lmart=
ini@cisco.com</a></a>&gt;, "<a href=3D"mailto:mpls-tp@ietf.org"><a href=3D"m=
ailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a></a>"<br>
&nbsp; &nbsp; &nbsp; &nbsp;&lt;<a href=3D"mailto:mpls-tp@ietf.org"><a href=3D=
"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a></a>&gt;, &nbsp; &nbsp; "<a hr=
ef=3D"mailto:lihan@chinamobile.com"><a href=3D"mailto:lihan@chinamobile.com"=
>lihan@chinamobile.com</a></a>" &lt;<a href=3D"mailto:lihan@chinamobile.com"=
><a href=3D"mailto:lihan@chinamobile.com">lihan@chinamobile.com</a></a>&gt;,=
<br>
&nbsp; &nbsp; &nbsp; &nbsp;pwe3 &lt;<a href=3D"mailto:pwe3@ietf.org"><a href=
=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a></a>&gt;, &nbsp; HUANG Feng F &lt=
;<a href=3D"mailto:Feng.f.Huang@alcatel-sbell.com.cn"><a href=3D"mailto:Feng=
.f.Huang@alcatel-sbell.com.cn">Feng.f.Huang@alcatel-sbell.com.cn</a></a>&gt;=
<br>Message-ID:<br>&nbsp; &nbsp; &nbsp; &nbsp;&lt;<a href=3D"mailto:A3C5DF08=
D38B6049839A6F553B331C76D6FB8BEAB3@ILPTMAIL02.ecitele.com"><a href=3D"mailto=
:A3C5DF08D38B6049839A6F553B331C76D6FB8BEAB3@ILPTMAIL02.ecitele.com">A3C5DF08=
D38B6049839A6F553B331C76D6FB8BEAB3@ILPTMAIL02.ecitele.com</a></a>&gt;<br>
Content-Type: text/plain; charset=3D"windows-1252"<br><br>Venkat,<br><br>You=
 have asked "Are we implicitly mandating the CW (ACH) in HW by configuring/n=
egotiating the CC type-4?"<br><br>IMO the answer is "No".<br>
In VCCV Type 1 the first nibble of the CW is a data path (HW if you wish) ex=
ception mechanism forwarding the packets to an OAM entity.<br><br>In VCCV Ty=
pe 4 GAL acts as such an exception mechanism. ACH is actually only needed to=
 decide on the ACH Type. And it would not even be examined if the TTL in the=
 PW label has not expired.<br>
<br>My 2c,<br>&nbsp; &nbsp; Sasha<br><br><br><br>___________________________=
_____<br>From: venkatesan mahalingam [<a href=3D"mailto:venkatflex@gmail.com=
"><a href=3D"mailto:venkatflex@gmail.com">venkatflex@gmail.com</a></a>]<br>S=
ent: Friday, March 11, 2011 10:12 PM<br>To: Alexander Vainshtein; Greg Mirsk=
y; Luca Martini; <a href=3D"mailto:lihan@chinamobile.com"><a href=3D"mailto:=
lihan@chinamobile.com">lihan@chinamobile.com</a></a>; <a href=3D"mailto:mpls=
-tp@ietf.org"><a href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a></a>; p=
we3; HUANG Feng F; <a href=3D"mailto:mpls@ietf.org"><a href=3D"mailto:mpls@i=
etf.org">mpls@ietf.org</a></a><br>
Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br><br>Hi,<=
br>AFAIK, ACH can't be used without supporting the CW in HW.<br><br>As per R=
FC-5085, 5.1.1. &nbsp;In-Band VCCV (Type 1)<br>CC Type-1 mode of VCCV operat=
ion MUST be supported when the control word is present.<br>
<br>It looks to me that CC type-1 for ACH without GAL and CC type-4 for ACH w=
ith GAL.<br><br>IMO, if we support CC type-4, CC type-1 support is implicitl=
y attained.<br><br>IMHO, it should be possible to get the MPLS-TP OAM contro=
l packets with or without GAL from HW to CP by negotiating CC type-1 itself.=
<br>
<br>Some editorial comments for the draft-nadeau-pwe3-vccv-2-01.txt draft,<b=
r>"<br>4.1.1. &nbsp;MPLS VCCV Control Channel (CC) Type 4<br><br>&nbsp; IANA=
 is requested to augment the registry of "MPLS VCCV Control<br>&nbsp; Channe=
l Types" with the new type defined below. As defined in<br>
&nbsp; RFC5058, this new bitfield is to be assigned by IANA using<br>"<br>Re=
place the RFC5058 as RFC5085.<br><br>Thanks,<br>Venkat.<br><br>On Fri, Mar 1=
1, 2011 at 2:21 PM, Alexander Vainshtein &lt;<a href=3D"mailto:Alexander.Vai=
nshtein@ecitele.com"><a href=3D"mailto:Alexander.Vainshtein@ecitele.com">Ale=
xander.Vainshtein@ecitele.com</a></a>&lt;mailto:<a href=3D"mailto:Alexander.=
Vainshtein@ecitele.com"><a href=3D"mailto:Alexander.Vainshtein@ecitele.com">=
Alexander.Vainshtein@ecitele.com</a></a>&gt;&gt; wrote:<br>
Greg, Luca,<br>As I?ve already stated in my comment on draft-nadeau-pwe3-vcc=
v-2, IMHO it makes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.<br><b=
r>My 2c,<br>&nbsp; &nbsp; Sasha<br><br>From: <a href=3D"mailto:mpls-bounces@=
ietf.org"><a href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a>=
</a>&lt;mailto:<a href=3D"mailto:mpls-bounces@ietf.org"><a href=3D"mailto:mp=
ls-bounces@ietf.org">mpls-bounces@ietf.org</a></a>&gt; [mailto:<a href=3D"ma=
ilto:mpls-bounces@ietf.org"><a href=3D"mailto:mpls-bounces@ietf.org">mpls-bo=
unces@ietf.org</a></a>&lt;mailto:<a href=3D"mailto:mpls-bounces@ietf.org"><a=
 href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a></a>&gt;] On=
 Behalf Of Greg Mirsky<br>
Sent: Friday, March 11, 2011 9:14 PM<br>To: Luca Martini<br>Cc: <a href=3D"m=
ailto:lihan@chinamobile.com"><a href=3D"mailto:lihan@chinamobile.com">lihan@=
chinamobile.com</a></a>&lt;mailto:<a href=3D"mailto:lihan@chinamobile.com"><=
a href=3D"mailto:lihan@chinamobile.com">lihan@chinamobile.com</a></a>&gt;; <=
a href=3D"mailto:mpls@ietf.org"><a href=3D"mailto:mpls@ietf.org">mpls@ietf.o=
rg</a></a>&lt;mailto:<a href=3D"mailto:mpls@ietf.org"><a href=3D"mailto:mpls=
@ietf.org">mpls@ietf.org</a></a>&gt;; pwe3; HUANG Feng F; <a href=3D"mailto:=
mpls-tp@ietf.org"><a href=3D"mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a></=
a>&lt;mailto:<a href=3D"mailto:mpls-tp@ietf.org"><a href=3D"mailto:mpls-tp@i=
etf.org">mpls-tp@ietf.org</a></a>&gt;<br>
Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br><br>Dear=
 Luca,<br>thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention=
. I'll send my comments to it in a separate e-mail.<br>I'll have to miss ano=
ther opportunity to discuss your proposal in a meeting. Please add my commen=
ts below to my earlier expressed WG LC comments:<br>
<br>&nbsp;* &nbsp; the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any sol=
ution that addresses applicability of GAL in PW VCCV, e.g. solution proposed=
 in draft-nadeau-pwe3-vccv-2-01;<br>&nbsp;* &nbsp; the draft-lm-pwe3-mpls-tp=
-gal-in-pw-00 needs to mention such dependency and refer to any existing pro=
posal;<br>
&nbsp;* &nbsp; I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be a=
dvanced in lock with document that addresses use of GAL in PW VCCV.<br>Regar=
ds,<br>Greg<br>On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini &lt;<a href=3D"=
mailto:lmartini@cisco.com"><a href=3D"mailto:lmartini@cisco.com">lmartini@ci=
sco.com</a></a>&lt;mailto:<a href=3D"mailto:lmartini@cisco.com"><a href=3D"m=
ailto:lmartini@cisco.com">lmartini@cisco.com</a></a>&gt;&gt; wrote:<br>
Greg ,<br>Some<br><br>On 02/18/11 11:15, Greg Mirsky wrote:<br>&gt; Dear Luc=
a,<br>&gt; I see at least two issues:<br>&gt;<br>&gt; &nbsp; &nbsp; * use of=
 GAL for PW, in my view, is another VCCV CC type that has<br>&gt; &nbsp; &nb=
sp; &nbsp; to be negotiated as described in RFC 5085.<br>
&gt;<br>These are valid points, but this document in question does not defin=
e,<br>not discussed VCCV.<br>We have since posted a draft that proposes a ne=
w VCCV mode , and we<br>welcome comments regarding that document.<br>
(draft-nadeau-pwe3-vccv-2-01.txt)<br><br>&gt; &nbsp; &nbsp; * use of GAL cre=
ates ambiguous situation when PW CW is used. The<br>&gt; &nbsp; &nbsp; &nbsp=
; benefit from extending GAL in PW, as I see, is for PWs that are<br>&gt; &n=
bsp; &nbsp; &nbsp; not required to use PW CW. That might be a good enough re=
ason to<br>
&gt; &nbsp; &nbsp; &nbsp; update RFC 5586 as proposed in the document but we=
 must address<br>&gt; &nbsp; &nbsp; &nbsp; use cases of GAL in PWs that requ=
ire presence PW CW. If we<br>&gt; &nbsp; &nbsp; &nbsp; prohibit or even disc=
ourage use of GAL for these PWs that have<br>
&gt; &nbsp; &nbsp; &nbsp; PW VCCV as native Associated Channel, then archite=
cture of ACh<br>&gt; &nbsp; &nbsp; &nbsp; for MPLS-TP PW not simplified as r=
esult of adopting the proposal.<br>&gt;<br>&gt; Regard<br>Greg,<br>The GAL i=
s basically a notifier that the packet following the end of the<br>
MPLS label stack, is explicitly defined as a G-ACH format.<br>Normally the p=
acket would be decoded as an IP packet , unless the last<br>label on the sta=
ck indicated otherwise.<br><br>The GAL can certainly be applied &nbsp;to a P=
W OAM packet on a PW that uses<br>
the CW, and this document does not define that , nor restricts it.<br><br>Th=
e scope of this document is limited to removing an unnecessary<br>restrictio=
n in rfc5586, hence &nbsp;this comment not applicable to this document.<br>
<br>Thanks.<br>Luca<br><br>&gt; s,<br>&gt; Greg<br>&gt;<br>&gt; On Fri, Feb 1=
8, 2011 at 7:46 AM, Luca Martini &lt;<a href=3D"mailto:lmartini@cisco.com"><=
a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a></a>&lt;mailto:<a=
 href=3D"mailto:lmartini@cisco.com"><a href=3D"mailto:lmartini@cisco.com">lm=
artini@cisco.com</a></a>&gt;<br>
&gt; &lt;mailto:<a href=3D"mailto:lmartini@cisco.com"><a href=3D"mailto:lmar=
tini@cisco.com">lmartini@cisco.com</a></a>&lt;mailto:<a href=3D"mailto:lmart=
ini@cisco.com"><a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a><=
/a>&gt;&gt;&gt; wrote:<br>&gt;<br>&gt; &nbsp; &nbsp; Greg,<br>&gt;<br>&gt; &=
nbsp; &nbsp; Sorry, but I do not remember the point you mention.<br>
&gt; &nbsp; &nbsp; Can you explain again here ?<br>&gt; &nbsp; &nbsp; Thanks=
.<br>&gt; &nbsp; &nbsp; Luca<br>&gt;<br>&gt;<br>&gt; &nbsp; &nbsp; On 02/17/=
11 23:47, Greg Mirsky wrote:<br>&gt; &nbsp; &nbsp; &gt; Dear Authors and All=
,<br>&gt; &nbsp; &nbsp; &gt; prior to the meeting in Bejing and acceptance o=
f this proposal as WG<br>
&gt; &nbsp; &nbsp; &gt; document Luca and I agreed that use of GAL with PW V=
CCV presents a<br>&gt; &nbsp; &nbsp; &gt; problem.<br>&gt; &nbsp; &nbsp; &gt=
; I was not attending the IETF-79, nor I found discussion of this<br>&gt; &n=
bsp; &nbsp; issue<br>&gt; &nbsp; &nbsp; &gt; in the minutes. I think that th=
is issue should be specified,<br>
&gt; &nbsp; &nbsp; &gt; explained. In my view, this document updates not onl=
y RFC 5586<br>&gt; &nbsp; &nbsp; &gt; but RFC 5085 too.<br>&gt; &nbsp; &nbsp=
; &gt;<br>&gt; &nbsp; &nbsp; &gt; Regards,<br>&gt; &nbsp; &nbsp; &gt; Greg<b=
r>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; Comment to draft-lm-pwe=
3-mpls-tp-gal-in-pw-00.txt<br>
&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; On Sat, Oct 30, 2010 at 1=
0:14 AM, Luca Martini<br>&gt; &nbsp; &nbsp; &lt;<a href=3D"mailto:lmartini@c=
isco.com"><a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a></a>&l=
t;mailto:<a href=3D"mailto:lmartini@cisco.com"><a href=3D"mailto:lmartini@ci=
sco.com">lmartini@cisco.com</a></a>&gt; &lt;mailto:<a href=3D"mailto:lmartin=
i@cisco.com"><a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a></a=
>&lt;mailto:<a href=3D"mailto:lmartini@cisco.com"><a href=3D"mailto:lmartini=
@cisco.com">lmartini@cisco.com</a></a>&gt;&gt;<br>
&gt; &nbsp; &nbsp; &gt; &lt;mailto:<a href=3D"mailto:lmartini@cisco.com"><a h=
ref=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a></a>&lt;mailto:<a hr=
ef=3D"mailto:lmartini@cisco.com"><a href=3D"mailto:lmartini@cisco.com">lmart=
ini@cisco.com</a></a>&gt; &lt;mailto:<a href=3D"mailto:lmartini@cisco.com"><=
a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a></a>&lt;mailto:<a=
 href=3D"mailto:lmartini@cisco.com"><a href=3D"mailto:lmartini@cisco.com">lm=
artini@cisco.com</a></a>&gt;&gt;&gt;&gt; wrote:<br>
&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Greg,<br>&g=
t; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; You are corre=
ct , the proposed update does not propose any<br>&gt; &nbsp; &nbsp; changes<=
br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; to VCCV.<br>&gt; &nbsp; &nbsp; &gt;=
 &nbsp; &nbsp; However the problem with vccv is not as simple as to ask for<=
br>
&gt; &nbsp; &nbsp; a new<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; code point=
 from IANA.<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Given the good amount o=
f discussion on this point, we should<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbs=
p; probably have a discussion in Beijing.<br>&gt; &nbsp; &nbsp; &gt;<br>&gt;=
 &nbsp; &nbsp; &gt; &nbsp; &nbsp; Luca<br>
&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt=
;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; On 10/29/2010 05:07 PM, Greg Mirs=
ky wrote:<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Dear Authors,<br>&gt;=
 &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; I think that proposed update of the Se=
ction 4.2. RFC 5586<br>
&gt; &nbsp; &nbsp; makes it possible<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &=
nbsp; to use GAL on MPLS-TP PW that uses Control Word. I consider<br>&gt; &n=
bsp; &nbsp; it to be<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; conflict b=
etween PW VCCV CC types because use of GAL is not<br>
&gt; &nbsp; &nbsp; negotiated<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; t=
hrough PW VCCV negotiation. To avoid such situation I propose:<br>&gt; &nbsp=
; &nbsp; &gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;=
- in Section 5 request IANA to assign new CC Type "MPLS<br>
&gt; &nbsp; &nbsp; Generic<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbs=
p; &nbsp;Associated Channel Label"<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nb=
sp; &nbsp; &nbsp;- assign precedence to new CC Type that affects Section<br>=
&gt; &nbsp; &nbsp; 7 RFC 5085<br>&gt; &nbsp; &nbsp; &gt;&gt;<br>&gt; &nbsp; &=
nbsp; &gt;&gt; &nbsp; &nbsp; Regards,<br>
&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Greg<br>&gt; &nbsp; &nbsp; &gt;&gt=
;<br>&gt; &nbsp; &nbsp; &gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt;</blockquote>=
</div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>mpls mailing list</span><br><spa=
n><a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a></span><br><span><a href=
=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/mailman=
/listinfo/mpls</a></span><br></div></blockquote></body></html>=

--Apple-Mail-1--356993280--

From Internet-Drafts@ietf.org  Mon Mar 14 09:15:03 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 004983A6D54; Mon, 14 Mar 2011 09:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 DgU3w3SL+QLo; Mon, 14 Mar 2011 09:15:01 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FC2A3A6D0D; Mon, 14 Mar 2011 09:15:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314161501.21193.48750.idtracker@localhost>
Date: Mon, 14 Mar 2011 09:15:01 -0700
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-redundancy-bit-04.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 16:15:03 -0000

--NextPart

A new Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudowire Emulation Edge to Edge Working Group of the IETF.

    Title         : Pseudowire Preferential Forwarding Status Bit 
    Author(s)     : P. Muley, et al
    Filename      : draft-ietf-pwe3-redundancy-bit-04.txt
    Pages         : 34
    Date          : 2011-03-14
    
   This document describes a mechanism for standby status signaling of 
   redundant pseudowires (PWs) between their termination points. A set 
   of redundant PWs is configured between provider edge (PE) nodes in 
   single-segment pseudowire (SS-PW) applications, or between 
   terminating provider edge (T-PE) nodes in multi-segment pseudowire 
   (MS-PW) applications.  

   In order for the PE/T-PE nodes to indicate the preferred PW to use 
   for forwarding PW packets to one another, a new status bit is needed 
   to indicate a preferential forwarding status of Active or Standby for 
   each PW in a redundant set.  

   In addition, a second status bit is defined to allow peer PE nodes to 
   coordinate a switchover operation of the PW. 

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

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


--NextPart--

From Internet-Drafts@ietf.org  Mon Mar 14 14:15:10 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEA173A6F18; Mon, 14 Mar 2011 14:15:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, 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 EvVGLlnZ9ags; Mon, 14 Mar 2011 14:15:08 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FBB93A6F1B; Mon, 14 Mar 2011 14:15:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314211503.16840.9204.idtracker@localhost>
Date: Mon, 14 Mar 2011 14:15:03 -0700
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-fc-encap-15.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 21:15:10 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudowire Emulation Edge to Edge Working Group of the IETF.


	Title           : Encapsulation Methods for Transport of Fibre Channel Traffic over MPLS Networks
	Author(s)       : D. Black, et al.
	Filename        : draft-ietf-pwe3-fc-encap-15.txt
	Pages           : 23
	Date            : 2011-03-14

A Fibre Channel pseudowire (PW) is used to carry Fibre Channel
traffic over an MPLS network. This enables service providers to take
advantage of MPLS-TP to offer "emulated" Fibre Channel services. This
document specifies the encapsulation of Fibre Channel traffic within
a pseudowire. It also specifies the common procedures for using a PW
to provide a Fibre Channel service. The mechanisms controlling the
transport of Fibre Channel PW over MPLS networks can be provided by
MPLS-TP.

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

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


--NextPart--

From david.black@emc.com  Mon Mar 14 15:16:49 2011
Return-Path: <david.black@emc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 773933A6DB9 for <pwe3@core3.amsl.com>; Mon, 14 Mar 2011 15:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.42
X-Spam-Level: 
X-Spam-Status: No, score=-106.42 tagged_above=-999 required=5 tests=[AWL=0.179, 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 PUqNWAhKlIci for <pwe3@core3.amsl.com>; Mon, 14 Mar 2011 15:16:48 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id DDFAF3A6978 for <pwe3@ietf.org>; Mon, 14 Mar 2011 15:16:45 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p2EMI8iY007423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <pwe3@ietf.org>; Mon, 14 Mar 2011 18:18:08 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor) for <pwe3@ietf.org>; Mon, 14 Mar 2011 18:17:56 -0400
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p2EMHPou004567 for <pwe3@ietf.org>; Mon, 14 Mar 2011 18:17:25 -0400
Received: from mx14a.corp.emc.com ([169.254.1.143]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Mon, 14 Mar 2011 18:17:25 -0400
From: <david.black@emc.com>
To: <pwe3@ietf.org>
Date: Mon, 14 Mar 2011 18:17:24 -0400
Thread-Topic: [PWE3] I-D Action:draft-ietf-pwe3-fc-encap-15.txt
Thread-Index: AcvijavnS8WjlwdLQRWb1mL30CLQbQAB5jmw
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E03E5D3E3B2@MX14A.corp.emc.com>
References: <20110314211503.16840.9204.idtracker@localhost>
In-Reply-To: <20110314211503.16840.9204.idtracker@localhost>
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-EMM-MHVC: 1
Subject: Re: [PWE3] I-D Action:draft-ietf-pwe3-fc-encap-15.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 22:16:49 -0000

The -15 version of this draft should contain text to address all of the IET=
F Last Call comments on this draft, but I completed the editing work too cl=
ose in time to the submission cutoff for Prague to allow the reviewers adeq=
uate time to check my work.  There will be a -16 version during the Prague =
meeting week if anything is found that needs attention.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of I=
nternet-Drafts@ietf.org
> Sent: Monday, March 14, 2011 5:15 PM
> To: i-d-announce@ietf.org
> Cc: pwe3@ietf.org
> Subject: [PWE3] I-D Action:draft-ietf-pwe3-fc-encap-15.txt
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Pseudowire Emulation Edge to Edge Workin=
g Group of the IETF.
>=20
>=20
> 	Title           : Encapsulation Methods for Transport of Fibre Channel T=
raffic over MPLS
> Networks
> 	Author(s)       : D. Black, et al.
> 	Filename        : draft-ietf-pwe3-fc-encap-15.txt
> 	Pages           : 23
> 	Date            : 2011-03-14
>=20
> A Fibre Channel pseudowire (PW) is used to carry Fibre Channel traffic ov=
er an MPLS network. This
> enables service providers to take advantage of MPLS-TP to offer "emulated=
" Fibre Channel services.
> This document specifies the encapsulation of Fibre Channel traffic within=
 a pseudowire. It also
> specifies the common procedures for using a PW to provide a Fibre Channel=
 service. The mechanisms
> controlling the transport of Fibre Channel PW over MPLS networks can be p=
rovided by MPLS-TP.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-fc-encap-15.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader implemen=
tation to automatically
> retrieve the ASCII version of the Internet-Draft.

From Internet-Drafts@ietf.org  Mon Mar 14 16:45:05 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF47C3A702F; Mon, 14 Mar 2011 16:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 zkmtUCJ8xcOt; Mon, 14 Mar 2011 16:45:02 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B18473A6A4E; Mon, 14 Mar 2011 16:45:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314234501.17995.78723.idtracker@localhost>
Date: Mon, 14 Mar 2011 16:45:01 -0700
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-static-pw-status-03.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 23:45:05 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudowire Emulation Edge to Edge Working Group of the IETF.


	Title           : Pseudowire Status for Static Pseudowires
	Author(s)       : L. Martini, et al.
	Filename        : draft-ietf-pwe3-static-pw-status-03.txt
	Pages           : 12
	Date            : 2011-03-14

This document specifies a mechanism to signal Pseudowire (PW) status
messages using an PW associated channel (ACh). Such a mechanism is
suitable for use where no PW dynamic control plane exits, known as
static PWs, or where a Terminating Provider Edge (T-PE) needs to send
a PW status message directly to a far end T-PE. The mechanism allows
PW OAM message mapping and PW redundancy to operate on static PWs.

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

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


--NextPart--

From wwwrun@core3.amsl.com  Tue Mar 15 07:51:01 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 38C853A6E1E; Tue, 15 Mar 2011 07:51:00 -0700 (PDT)
From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: andrew.g.malis@verizon.com,matthew.bocci@alcatel-lucent.com
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110315145101.38C853A6E1E@core3.amsl.com>
Date: Tue, 15 Mar 2011 07:51:00 -0700 (PDT)
Cc: Huub.van.Helvoort@huawei.com, hiroshi.ota@itu.int, greg.jones@itu.int, Steve.Trowbridge@alcatel-lucent.com, yoichi.maeda@ttc.or.jp, pwe3@ietf.org, adrian.farrel@huawei.com, tsbsg15@itu.int, paf@cisco.com, stbryant@cisco.com
Subject: [PWE3] New Liaison Statement, "LS296 - Reply to the IETF PWE3 WG LC on draft-ietf-pwe3-mpls-tp-gal-in-pw-00"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tsbsg15@itu.int
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 14:51:01 -0000

Title: LS296 - Reply to the IETF PWE3 WG LC on draft-ietf-pwe3-mpls-tp-gal-in-pw-00
Submission Date: 2011-03-15
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=1034 

From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: IETF PWE3 WG(andrew.g.malis@verizon.com,matthew.bocci@alcatel-lucent.com)
Cc: paf@cisco.com
stbryant@cisco.com
adrian.farrel@huawei.com
pwe3@ietf.org
yoichi.maeda@ttc.or.jp
Steve.Trowbridge@alcatel-lucent.com
Reponse Contact: tsbsg15@itu.int
greg.jones@itu.int
hiroshi.ota@itu.int
Technical Contact: Huub.van.Helvoort@huawei.com
Purpose: For information 
Body: Thank you for your liaison statement: IETF PWE3 Working Group Last Call on draft-ietf-pwe3-mpls-tp-gal-in-pw-00 ï¿½Using the Generic Associated Channel Label for Pseudowire in MPLS-TP".
The Q10/15 experts have reviewed draft and have no comments.
Q10/15 supports the publication of this draft as an RFC.
Attachment(s):
     LS296 - Reply to the IETF PWE3 WG LC on draft-ietf-pwe3-mpls-tp-gal-in-pw-00 - pdf body (https://datatracker.ietf.org/documents/LIAISON/file1211.pdf)




From yaakov_s@rad.com  Tue Mar 15 08:40:35 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E788B3A6D4B for <pwe3@core3.amsl.com>; Tue, 15 Mar 2011 08:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.168
X-Spam-Level: 
X-Spam-Status: No, score=-102.168 tagged_above=-999 required=5 tests=[AWL=0.431, 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 apYzkM5pzp-O for <pwe3@core3.amsl.com>; Tue, 15 Mar 2011 08:40:34 -0700 (PDT)
Received: from antivir1.rad.co.il (antivir1.rad.co.il [62.0.23.193]) by core3.amsl.com (Postfix) with ESMTP id 05EE53A6C5B for <pwe3@ietf.org>; Tue, 15 Mar 2011 08:40:31 -0700 (PDT)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 15 Mar 2011 17:41:35 +0200
Received: from EXUS4-DRP.ad.rad.co.il (192.114.24.119) by EXRAD5.ad.rad.co.il (192.114.24.28) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 15 Mar 2011 17:41:34 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Tue, 15 Mar 2011 17:41:34 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
Thread-Topic: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
Thread-Index: Acvdm33bS8HQGFieTSSSyunk7NkzBAAABRxQAWJa3CA=
Date: Tue, 15 Mar 2011 15:41:33 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il>
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com>
In-Reply-To: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 15:40:36 -0000

Nick,=20

In section 2.2 the percentages make sense under the assumption of 18 respon=
dents :
5.6%   =3D  1 / 18
11.1%  =3D  2 / 18
16.7%  =3D  3 / 18
22.2%  =3D  4 / 18
44.4%  =3D  8 / 18
77.8%  =3D 14 / 18=20

but section 2.1 only lists 17 :
1.	Time Warner Cable
2.	Bright House Networks
3.	Tinet
4.	AboveNet
5.	Telecom New Zealand
6.	Cox Communications
7.	MTN South Africa
8.	Wipro Technologies
9.	Verizon
10.	AMS-IX
11.	Superonline
12.	Deutsche Telekom AG
13.	Internet Solution
14.	Easynet Global Services
15.	Telstra Corporation
16.	OJSC MegaFon
17.	France Telecom Orange

Did you leave someone off, or did someone answer twice ?

Y(J)S


-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Del=
regno, Christopher N (Nick DelRegno)
Sent: Tuesday, March 08, 2011 16:27
To: pwe3
Subject: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-imp=
l-survey-results-00

Folks:

The 00 draft of the PW/VCCV Implementation Survey Results have been uploade=
d.  I will be presenting the results at IETF80.

https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-results=
/

Thanks,
Nick

Christopher N. Del Regno, PMTS
C&T, Ethernet Network Architecture & Design
400 International Pkwy
Richardson, TX  75081
972-729-3411
nick.delregno@verizon.com




-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20
Sent: Tuesday, March 08, 2011 8:16 AM
To: Delregno, Christopher N (Nick DelRegno)
Subject: New Version Notification for draft-delregno-pw-vccv-impl-survey-re=
sults-00


A new version of I-D, draft-delregno-pw-vccv-impl-survey-results-00.txt has=
 been successfully submitted by Nick Del Regno and posted to the IETF repos=
itory.

Filename:	 draft-delregno-pw-vccv-impl-survey-results
Revision:	 00
Title:		 The Pseudowire (PW) & Virtual Circuit Connectivity Verification (V=
CCV) Implementation Survey Results
Creation_date:	 2011-03-07
WG ID:		 Independent Submission
Number_of_pages: 16

Abstract:
Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate
the use of the Control Word (CW) in order to better emulate the
services for which the encapsulations have been defined.  However,
some encapulations treat the Control Word as optional.  As a result,
implementations of the CW, for encapsulations for which it is
optional, vary by equipment manufacturer, equipment model and service
provider network.  Similarly, Virtual Circuit Connectivity
Verification (VCCV) supports three Control Channel (CC) types and
multiple Connectivity Verification (CV) Types.  This flexibility has
led to reports of interoperability issues within deployed networks
and associated drafts to attempt to remedy the situation.  This
survey of the PW/VCCV user community was conducted to determine
implementation trends.  The survey and results is presented herein.
                                                                           =
      =20


The IETF Secretariat.


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

From Alexander.Vainshtein@ecitele.com  Tue Mar 15 09:20:04 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2BC2B3A6D8F for <pwe3@core3.amsl.com>; Tue, 15 Mar 2011 09:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.571
X-Spam-Level: 
X-Spam-Status: No, score=-2.571 tagged_above=-999 required=5 tests=[AWL=0.028,  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 X+hekvfkeUPB for <pwe3@core3.amsl.com>; Tue, 15 Mar 2011 09:20:03 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id 84A2D3A6B89 for <pwe3@ietf.org>; Tue, 15 Mar 2011 09:20:02 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bc9ae000002803-1f-4d7f91a0443d
Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id D1.8E.10243.0A19F7D4; Tue, 15 Mar 2011 18:19:44 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Tue, 15 Mar 2011 18:21:26 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
Date: Tue, 15 Mar 2011 18:21:21 +0200
Thread-Topic: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
Thread-Index: Acvdm33bS8HQGFieTSSSyunk7NkzBAAABRxQAWJa3CAAAffTcA==
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6FBC4D80C@ILPTMAIL02.ecitele.com>
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com> <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il>
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-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: Yaakov Stein <yaakov_s@rad.com>, pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 16:20:04 -0000

Nick,
I also remember that 18 respondents have been mentioned when you've announc=
ed that the survey has been completed...=20

Regards,
     Sasha

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> Yaakov Stein
> Sent: Tuesday, March 15, 2011 5:42 PM
> To: Delregno, Christopher N (Nick DelRegno)
> Cc: pwe3
> Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-
> vccv-impl-survey-results-00
>=20
> Nick,
>=20
> In section 2.2 the percentages make sense under the assumption of 18
> respondents :
> 5.6%   =3D  1 / 18
> 11.1%  =3D  2 / 18
> 16.7%  =3D  3 / 18
> 22.2%  =3D  4 / 18
> 44.4%  =3D  8 / 18
> 77.8%  =3D 14 / 18
>=20
> but section 2.1 only lists 17 :
> 1.	Time Warner Cable
> 2.	Bright House Networks
> 3.	Tinet
> 4.	AboveNet
> 5.	Telecom New Zealand
> 6.	Cox Communications
> 7.	MTN South Africa
> 8.	Wipro Technologies
> 9.	Verizon
> 10.	AMS-IX
> 11.	Superonline
> 12.	Deutsche Telekom AG
> 13.	Internet Solution
> 14.	Easynet Global Services
> 15.	Telstra Corporation
> 16.	OJSC MegaFon
> 17.	France Telecom Orange
>=20
> Did you leave someone off, or did someone answer twice ?
>=20
> Y(J)S
>=20
>=20
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> Delregno, Christopher N (Nick DelRegno)
> Sent: Tuesday, March 08, 2011 16:27
> To: pwe3
> Subject: [PWE3] FW: New Version Notification for draft-delregno-pw-
> vccv-impl-survey-results-00
>=20
> Folks:
>=20
> The 00 draft of the PW/VCCV Implementation Survey Results have been
> uploaded.  I will be presenting the results at IETF80.
>=20
> https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-
> results/
>=20
> Thanks,
> Nick
>=20
> Christopher N. Del Regno, PMTS
> C&T, Ethernet Network Architecture & Design
> 400 International Pkwy
> Richardson, TX  75081
> 972-729-3411
> nick.delregno@verizon.com
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> Sent: Tuesday, March 08, 2011 8:16 AM
> To: Delregno, Christopher N (Nick DelRegno)
> Subject: New Version Notification for draft-delregno-pw-vccv-impl-
> survey-results-00
>=20
>=20
> A new version of I-D, draft-delregno-pw-vccv-impl-survey-results-00.txt
> has been successfully submitted by Nick Del Regno and posted to the
> IETF repository.
>=20
> Filename:	 draft-delregno-pw-vccv-impl-survey-results
> Revision:	 00
> Title:		 The Pseudowire (PW) & Virtual Circuit Connectivity
> Verification (VCCV) Implementation Survey Results
> Creation_date:	 2011-03-07
> WG ID:		 Independent Submission
> Number_of_pages: 16
>=20
> Abstract:
> Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate
> the use of the Control Word (CW) in order to better emulate the
> services for which the encapsulations have been defined.  However,
> some encapulations treat the Control Word as optional.  As a result,
> implementations of the CW, for encapsulations for which it is
> optional, vary by equipment manufacturer, equipment model and service
> provider network.  Similarly, Virtual Circuit Connectivity
> Verification (VCCV) supports three Control Channel (CC) types and
> multiple Connectivity Verification (CV) Types.  This flexibility has
> led to reports of interoperability issues within deployed networks
> and associated drafts to attempt to remedy the situation.  This
> survey of the PW/VCCV user community was conducted to determine
> implementation trends.  The survey and results is presented herein.
>=20
>=20
>=20
> The IETF Secretariat.
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

From lmartini@cisco.com  Tue Mar 15 09:29:54 2011
Return-Path: <lmartini@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB1183A6D52 for <pwe3@core3.amsl.com>; Tue, 15 Mar 2011 09:29: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 7Cb0ArKe6YHi for <pwe3@core3.amsl.com>; Tue, 15 Mar 2011 09:29:53 -0700 (PDT)
Received: from napoleon.monoski.com (napoleon.monoski.com [70.90.113.113]) by core3.amsl.com (Postfix) with ESMTP id 4C30A3A6D3C for <pwe3@ietf.org>; Tue, 15 Mar 2011 09:29:53 -0700 (PDT)
Received: from seven.monoski.com (dhcp-171-70-247-65.cisco.com [171.70.247.65]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id p2FGVGH4019997 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 15 Mar 2011 10:31:17 -0600 (MDT)
Message-ID: <4D7F944E.2040903@cisco.com>
Date: Tue, 15 Mar 2011 10:31:10 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com> <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Yaakov Stein <yaakov_s@rad.com>, pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 16:29:54 -0000

Nick,
Good survey, thanks for the work.

Are we going to publish this as informational ?
I think we should .
Also there is a mention of AToM in section 2.7 item 5 . It should be
changed to PWE ( AToM is a cisco marketing term , so we want o keep this
anonymous )
Thanks.
Luca



On 03/15/2011 09:41 AM, Yaakov Stein wrote:
> Nick, 
>
> In section 2.2 the percentages make sense under the assumption of 18 respondents :
> 5.6%   =  1 / 18
> 11.1%  =  2 / 18
> 16.7%  =  3 / 18
> 22.2%  =  4 / 18
> 44.4%  =  8 / 18
> 77.8%  = 14 / 18 
>
> but section 2.1 only lists 17 :
> 1.	Time Warner Cable
> 2.	Bright House Networks
> 3.	Tinet
> 4.	AboveNet
> 5.	Telecom New Zealand
> 6.	Cox Communications
> 7.	MTN South Africa
> 8.	Wipro Technologies
> 9.	Verizon
> 10.	AMS-IX
> 11.	Superonline
> 12.	Deutsche Telekom AG
> 13.	Internet Solution
> 14.	Easynet Global Services
> 15.	Telstra Corporation
> 16.	OJSC MegaFon
> 17.	France Telecom Orange
>
> Did you leave someone off, or did someone answer twice ?
>
> Y(J)S
>
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Delregno, Christopher N (Nick DelRegno)
> Sent: Tuesday, March 08, 2011 16:27
> To: pwe3
> Subject: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
>
> Folks:
>
> The 00 draft of the PW/VCCV Implementation Survey Results have been uploaded.  I will be presenting the results at IETF80.
>
> https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-results/
>
> Thanks,
> Nick
>
> Christopher N. Del Regno, PMTS
> C&T, Ethernet Network Architecture & Design
> 400 International Pkwy
> Richardson, TX  75081
> 972-729-3411
> nick.delregno@verizon.com
>
>
>
>
> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
> Sent: Tuesday, March 08, 2011 8:16 AM
> To: Delregno, Christopher N (Nick DelRegno)
> Subject: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
>
>
> A new version of I-D, draft-delregno-pw-vccv-impl-survey-results-00.txt has been successfully submitted by Nick Del Regno and posted to the IETF repository.
>
> Filename:	 draft-delregno-pw-vccv-impl-survey-results
> Revision:	 00
> Title:		 The Pseudowire (PW) & Virtual Circuit Connectivity Verification (VCCV) Implementation Survey Results
> Creation_date:	 2011-03-07
> WG ID:		 Independent Submission
> Number_of_pages: 16
>
> Abstract:
> Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate
> the use of the Control Word (CW) in order to better emulate the
> services for which the encapsulations have been defined.  However,
> some encapulations treat the Control Word as optional.  As a result,
> implementations of the CW, for encapsulations for which it is
> optional, vary by equipment manufacturer, equipment model and service
> provider network.  Similarly, Virtual Circuit Connectivity
> Verification (VCCV) supports three Control Channel (CC) types and
> multiple Connectivity Verification (CV) Types.  This flexibility has
> led to reports of interoperability issues within deployed networks
> and associated drafts to attempt to remedy the situation.  This
> survey of the PW/VCCV user community was conducted to determine
> implementation trends.  The survey and results is presented herein.
>                                                                                   
>
>
> The IETF Secretariat.
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3


From tnadeau@lucidvision.com  Tue Mar 15 12:16:37 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA2B03A6ACD for <pwe3@core3.amsl.com>; Tue, 15 Mar 2011 12:16:37 -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=[AWL=0.600,  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 gZ4mci8h5Ryo for <pwe3@core3.amsl.com>; Tue, 15 Mar 2011 12:16:37 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by core3.amsl.com (Postfix) with ESMTP id B85483A6A40 for <pwe3@ietf.org>; Tue, 15 Mar 2011 12:16:36 -0700 (PDT)
Received: from [192.168.1.133] (unknown [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 18A781A75E46; Tue, 15 Mar 2011 15:18:01 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <4D7F944E.2040903@cisco.com>
Date: Tue, 15 Mar 2011 15:18:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <538B1799-C583-4192-B170-170F00FEDA7D@lucidvision.com>
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com> <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il> <4D7F944E.2040903@cisco.com>
To: Luca Martini <lmartini@cisco.com>
X-Mailer: Apple Mail (2.1082)
Cc: Yaakov Stein <yaakov_s@rad.com>, pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 19:16:38 -0000

	One thing I'd ask is that we augment the survey to ask about the =
BFD mode for=20
VCCV. It seems to have been left out of the survey, potentially skewing =
the results.=20
As I understand it, this is the most popular mode.

	--Tom




On Mar 15, 2011, at 12:31 PM, Luca Martini wrote:

> Nick,
> Good survey, thanks for the work.
>=20
> Are we going to publish this as informational ?
> I think we should .
> Also there is a mention of AToM in section 2.7 item 5 . It should be
> changed to PWE ( AToM is a cisco marketing term , so we want o keep =
this
> anonymous )
> Thanks.
> Luca
>=20
>=20
>=20
> On 03/15/2011 09:41 AM, Yaakov Stein wrote:
>> Nick,=20
>>=20
>> In section 2.2 the percentages make sense under the assumption of 18 =
respondents :
>> 5.6%   =3D  1 / 18
>> 11.1%  =3D  2 / 18
>> 16.7%  =3D  3 / 18
>> 22.2%  =3D  4 / 18
>> 44.4%  =3D  8 / 18
>> 77.8%  =3D 14 / 18=20
>>=20
>> but section 2.1 only lists 17 :
>> 1.	Time Warner Cable
>> 2.	Bright House Networks
>> 3.	Tinet
>> 4.	AboveNet
>> 5.	Telecom New Zealand
>> 6.	Cox Communications
>> 7.	MTN South Africa
>> 8.	Wipro Technologies
>> 9.	Verizon
>> 10.	AMS-IX
>> 11.	Superonline
>> 12.	Deutsche Telekom AG
>> 13.	Internet Solution
>> 14.	Easynet Global Services
>> 15.	Telstra Corporation
>> 16.	OJSC MegaFon
>> 17.	France Telecom Orange
>>=20
>> Did you leave someone off, or did someone answer twice ?
>>=20
>> Y(J)S
>>=20
>>=20
>> -----Original Message-----
>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf =
Of Delregno, Christopher N (Nick DelRegno)
>> Sent: Tuesday, March 08, 2011 16:27
>> To: pwe3
>> Subject: [PWE3] FW: New Version Notification for =
draft-delregno-pw-vccv-impl-survey-results-00
>>=20
>> Folks:
>>=20
>> The 00 draft of the PW/VCCV Implementation Survey Results have been =
uploaded.  I will be presenting the results at IETF80.
>>=20
>> =
https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-result=
s/
>>=20
>> Thanks,
>> Nick
>>=20
>> Christopher N. Del Regno, PMTS
>> C&T, Ethernet Network Architecture & Design
>> 400 International Pkwy
>> Richardson, TX  75081
>> 972-729-3411
>> nick.delregno@verizon.com
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20
>> Sent: Tuesday, March 08, 2011 8:16 AM
>> To: Delregno, Christopher N (Nick DelRegno)
>> Subject: New Version Notification for =
draft-delregno-pw-vccv-impl-survey-results-00
>>=20
>>=20
>> A new version of I-D, =
draft-delregno-pw-vccv-impl-survey-results-00.txt has been successfully =
submitted by Nick Del Regno and posted to the IETF repository.
>>=20
>> Filename:	 draft-delregno-pw-vccv-impl-survey-results
>> Revision:	 00
>> Title:		 The Pseudowire (PW) & Virtual Circuit =
Connectivity Verification (VCCV) Implementation Survey Results
>> Creation_date:	 2011-03-07
>> WG ID:		 Independent Submission
>> Number_of_pages: 16
>>=20
>> Abstract:
>> Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate
>> the use of the Control Word (CW) in order to better emulate the
>> services for which the encapsulations have been defined.  However,
>> some encapulations treat the Control Word as optional.  As a result,
>> implementations of the CW, for encapsulations for which it is
>> optional, vary by equipment manufacturer, equipment model and service
>> provider network.  Similarly, Virtual Circuit Connectivity
>> Verification (VCCV) supports three Control Channel (CC) types and
>> multiple Connectivity Verification (CV) Types.  This flexibility has
>> led to reports of interoperability issues within deployed networks
>> and associated drafts to attempt to remedy the situation.  This
>> survey of the PW/VCCV user community was conducted to determine
>> implementation trends.  The survey and results is presented herein.
>>=20
>>=20
>>=20
>> The IETF Secretariat.
>>=20
>>=20
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>=20


From zhang.fei3@zte.com.cn  Wed Mar 16 02:56:42 2011
Return-Path: <zhang.fei3@zte.com.cn>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB2363A68E0; Wed, 16 Mar 2011 02:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.75
X-Spam-Level: 
X-Spam-Status: No, score=-100.75 tagged_above=-999 required=5 tests=[AWL=1.088, 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 vSdan1JKQ8Uf; Wed, 16 Mar 2011 02:56:42 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 0BFD13A68C8; Wed, 16 Mar 2011 02:56:40 -0700 (PDT)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35102967892178; Wed, 16 Mar 2011 17:55:42 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.15] with StormMail ESMTP id 84746.2967892178; Wed, 16 Mar 2011 17:53:20 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p2G9rDmS059824; Wed, 16 Mar 2011 17:53:13 +0800 (GMT-8) (envelope-from zhang.fei3@zte.com.cn)
To: pwe3 <pwe3@ietf.org>, mpls@ietf.org, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
MIME-Version: 1.0
X-KeepSent: A1CBEEB2:AE53C172-48257855:003575BA; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFA1CBEEB2.AE53C172-ON48257855.003575BA-48257855.00365084@zte.com.cn>
From: zhang.fei3@zte.com.cn
Date: Wed, 16 Mar 2011 17:53:28 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-03-16 17:53:16, Serialize complete at 2011-03-16 17:53:16
Content-Type: multipart/alternative; boundary="=_alternative 0036508048257855_="
X-MAIL: mse02.zte.com.cn p2G9rDmS059824
Subject: [PWE3] draft-zhang-mpls-tp-pw-oam-config-04
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2011 09:56:43 -0000

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

Hi all,
 
We have updated the document about the MPLS-TP PW OAM configuration, below 
is the link:

http://tools.ietf.org/html/draft-zhang-mpls-tp-pw-oam-config-04

Comapred to last version, we put the MPLS-TP PW OAM capability negotiation 
into the LDP initializaiton message, and the other parts are almost 
editoral in nature.

We will be apprecaited if you can  review and give any comments. 

Thanks
 
Fei
--=_alternative 0036508048257855_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=3 face="Calibri">Hi all,</font>
<br><font size=3 face="sans-serif">&nbsp;</font>
<br><font size=3 face="Calibri">We have updated the document about the
MPLS-TP PW OAM configuration, below is the link:</font>
<br>
<br><font size=3 face="Calibri">http://tools.ietf.org/html/draft-zhang-mpls-tp-pw-oam-config-04</font>
<br>
<br><font size=3 face="Calibri">Comapred to last version, we put the MPLS-TP
PW OAM capability negotiation into the LDP initializaiton message, and
the other parts are almost editoral in nature.</font>
<br>
<br><font size=3 face="Calibri">We will be apprecaited if you can &nbsp;review
and give any comments.</font><font size=3 face="sans-serif"> </font>
<br><font size=3 face="Calibri"><br>
Thanks<br>
 <br>
Fei</font>
--=_alternative 0036508048257855_=--


From lizhong.jin@zte.com.cn  Wed Mar 16 20:05:59 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D2333A6A21 for <pwe3@core3.amsl.com>; Wed, 16 Mar 2011 20:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.838
X-Spam-Level: 
X-Spam-Status: No, score=-101.838 tagged_above=-999 required=5 tests=[AWL=0.000, 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 KY98Y46mI8QZ for <pwe3@core3.amsl.com>; Wed, 16 Mar 2011 20:05:58 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 6D9323A6A16 for <pwe3@ietf.org>; Wed, 16 Mar 2011 20:05:57 -0700 (PDT)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35101397396305; Thu, 17 Mar 2011 11:04:29 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 85806.6174352124; Thu, 17 Mar 2011 10:57:23 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p2H37E92081723; Thu, 17 Mar 2011 11:07:14 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <AANLkTimcc2-zCW_P2ONCtpR-kNxPhBLEY6mKAy6TmX-+@mail.gmail.com>
To: "Andrew G. Malis" <andrew.g.malis@verizon.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF31C57E6E.B57B805F-ON48257856.00109DB4-48257856.001123D0@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Thu, 17 Mar 2011 11:07:00 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-17 11:07:12, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-17 11:07:12, Serialize complete at 2011-03-17 11:07:12, S/MIME Sign failed at 2011-03-17 11:07:12: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-03-17 11:07:14, Serialize complete at 2011-03-17 11:07:14
Content-Type: multipart/alternative; boundary="=_alternative 001123CD48257856_="
X-MAIL: mse01.zte.com.cn p2H37E92081723
Cc: pwe3@ietf.org, lmartini@cisco.com
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt ( comment )
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 03:05:59 -0000

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

Hi Andy,
Thank you very much. We have uploaded the 04 version. Please get it from 
the following link:
http://tools.ietf.org/html/draft-jin-pwe3-cbit-negotiation-04.txt

Regards
Lizhong


amalis@gmail.com wrote on 2011-03-07 23:52:22:

> Lizhong,
> 
> There's been a lot of support for WG adoption of this draft. Please
> update the draft to -04 to reflect the discussion on the list (before
> the window closes in a week) and we'll announce the adoption in
> Prague, followed by having you issue the WG version of the draft.
> 
> Thanks,
> Andy
> 
> On Thu, Mar 3, 2011 at 10:41 AM,  <lizhong.jin@zte.com.cn> wrote:
> >
> > Luca,
> > After discussing with the authors, we decide to add the wait for label
> > release before sending label request, this wouldn't harm and bring 
some
> > secure.
> >
> > Then are you OK with the following text?
> >
> > When Local PE changes its control word from NOT PREFERRED to PREFERRED 
and
> > only if it already received the remote label mapping message with 
C-bit=0,
> > additional procedure will be added as follow:
> > -i Local PE MUST send a label withdraw message to remote PE if it has
> > previously sent a label mapping, and wait until receiving a label 
release
> > from the remote PE.
> > -ii Local PE MUST send a label request message to remote PE, and wait 
until
> > receiving a label mapping message containing the remote PE configured
> > control word setting.
> > -iii After receiving remote PE label mapping with control word 
setting,
> > Local PE MUST follow procedures defined in [RFC4447] section 6 when 
sending
> > it's label mapping message.
> >
> > Correspondingly, the modified procedure of PE in figure 1 will be as
> > follows:
> >
> > 1. PE2 changes locally configured control word to PREFERRED.
> > 2. PE2 will then send label withdraw message to PE1.
> > 3. PE1 MUST send label release in reply to label withdraw message from 
PE2.
> > 4. Upon receipt of Label release message from PE1, PE2 MUST send label
> > request messages to PE1 although it already received the label mapping 
with
> > C-bit=0.
> > 5. PE1 MUST send label mapping message with C-bit=1 again to PE2 
(Note: PE1
> > MUST send label mapping with locally configured CW parameter).
> > 6. PE2 receives the label mapping from PE1 and updates the remote 
label
> > binding information. PE2 MUST wait for PE1 label binding before 
sending its
> > label binding with C-bit set, only if it previously had a label 
binding with
> > C-bit = 0 from PE1.
> > 7. PE2 will send label mapping to PE1 with C-bit=1.
> >
> > It is to be noted that the above assume that PE1 is configured to 
support
> > CW, however in step 5 if PE1 doesn't support CW, PE1 would send the 
label
> > mapping message with C-bit =0, this would result in PE2 in step 7 
sending a
> > label mapping with C-bit=0 as per [RFC4447] CW negotiation procedure.
> >
> > Thanks
> > Lizhong
> >
> >
> > ------------send by Luca 
Martini-------------------------------------------
> > Matthew & Andy,
> >
> >
> > Although I support clarifying this procedure , I believe this document
> > needs some work.
> > In section 3 for example :
> >
> >    When Local PE changes its control word from NOT PREFERRED to
> >    PREFERRED and only if it already received the remote label mapping
> >    message with C-bit=0, additional procedure will be added as follow:
> >
> >          -i. Local PE sends label withdraw message to the remote if it
> >              already sends label mapping message, for it has changed 
its
> >              control word parameter.
> >
> >         -ii. Local PE MUST send a label request messages to peer PE to
> >              get peer's configured control word parameter before 
sending
> >              new label mapping message to peer PE.
> >
> >        -iii. After receiving the new label mapping message from peer 
PE
> >              and updating the remote label binding information, the
> >              Local PE should send label mapping to peer PE according 
to
> >              procedures defined in [RFC4447].
> >
> > What does the item i) mean ? the English is not clear.
> > Why does the PE have to do ii) ?
> >
> > All we really need is a statement on how the c-bit negotiation state
> > machine can be reset if one end has changed "his mind" .
> >
> > Can we fix this document before  issuing the -00 WG draft version ?
> >
> > Thanks.
> > Luca
> >

--------------------------------------------------------
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 001123CD48257856_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Andy,</font>
<br><font size=2 face="sans-serif">Thank you very much. We have uploaded
the 04 version. Please get it from the following link:</font>
<br><font size=2 face="sans-serif">http://tools.ietf.org/html/draft-jin-pwe3-cbit-negotiation-04.txt</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br>
<br>
<br><tt><font size=2>amalis@gmail.com wrote on 2011-03-07 23:52:22:<br>
<br>
&gt; Lizhong,<br>
&gt; <br>
&gt; There's been a lot of support for WG adoption of this draft. Please<br>
&gt; update the draft to -04 to reflect the discussion on the list (before<br>
&gt; the window closes in a week) and we'll announce the adoption in<br>
&gt; Prague, followed by having you issue the WG version of the draft.<br>
&gt; <br>
&gt; Thanks,<br>
&gt; Andy<br>
&gt; <br>
&gt; On Thu, Mar 3, 2011 at 10:41 AM, &nbsp;&lt;lizhong.jin@zte.com.cn&gt;
wrote:<br>
&gt; &gt;<br>
&gt; &gt; Luca,<br>
&gt; &gt; After discussing with the authors, we decide to add the wait
for label<br>
&gt; &gt; release before sending label request, this wouldn't harm and
bring some<br>
&gt; &gt; secure.<br>
&gt; &gt;<br>
&gt; &gt; Then are you OK with the following text?<br>
&gt; &gt;<br>
&gt; &gt; When Local PE changes its control word from NOT PREFERRED to
PREFERRED and<br>
&gt; &gt; only if it already received the remote label mapping message
with C-bit=0,<br>
&gt; &gt; additional procedure will be added as follow:<br>
&gt; &gt; -i Local PE MUST send a label withdraw message to remote PE if
it has<br>
&gt; &gt; previously sent a label mapping, and wait until receiving a label
release<br>
&gt; &gt; from the remote PE.<br>
&gt; &gt; -ii Local PE MUST send a label request message to remote PE,
and wait until<br>
&gt; &gt; receiving a label mapping message containing the remote PE configured<br>
&gt; &gt; control word setting.<br>
&gt; &gt; -iii After receiving remote PE label mapping with control word
setting,<br>
&gt; &gt; Local PE MUST follow procedures defined in [RFC4447] section
6 when sending<br>
&gt; &gt; it's label mapping message.<br>
&gt; &gt;<br>
&gt; &gt; Correspondingly, the modified procedure of PE in figure 1 will
be as<br>
&gt; &gt; follows:<br>
&gt; &gt;<br>
&gt; &gt; 1. PE2 changes locally configured control word to PREFERRED.<br>
&gt; &gt; 2. PE2 will then send label withdraw message to PE1.<br>
&gt; &gt; 3. PE1 MUST send label release in reply to label withdraw message
from PE2.<br>
&gt; &gt; 4. Upon receipt of Label release message from PE1, PE2 MUST send
label<br>
&gt; &gt; request messages to PE1 although it already received the label
mapping with<br>
&gt; &gt; C-bit=0.<br>
&gt; &gt; 5. PE1 MUST send label mapping message with C-bit=1 again to
PE2 (Note: PE1<br>
&gt; &gt; MUST send label mapping with locally configured CW parameter).<br>
&gt; &gt; 6. PE2 receives the label mapping from PE1 and updates the remote
label<br>
&gt; &gt; binding information. PE2 MUST wait for PE1 label binding before
sending its<br>
&gt; &gt; label binding with C-bit set, only if it previously had a label
binding with<br>
&gt; &gt; C-bit = 0 from PE1.<br>
&gt; &gt; 7. PE2 will send label mapping to PE1 with C-bit=1.<br>
&gt; &gt;<br>
&gt; &gt; It is to be noted that the above assume that PE1 is configured
to support<br>
&gt; &gt; CW, however in step 5 if PE1 doesn't support CW, PE1 would send
the label<br>
&gt; &gt; mapping message with C-bit =0, this would result in PE2 in step
7 sending a<br>
&gt; &gt; label mapping with C-bit=0 as per [RFC4447] CW negotiation procedure.<br>
&gt; &gt;<br>
&gt; &gt; Thanks<br>
&gt; &gt; Lizhong<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; ------------send by Luca Martini-------------------------------------------<br>
&gt; &gt; Matthew &amp; Andy,<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Although I support clarifying this procedure , I believe this
document<br>
&gt; &gt; needs some work.<br>
&gt; &gt; In section 3 for example :<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp;When Local PE changes its control word from NOT
PREFERRED to<br>
&gt; &gt; &nbsp; &nbsp;PREFERRED and only if it already received the remote
label mapping<br>
&gt; &gt; &nbsp; &nbsp;message with C-bit=0, additional procedure will
be added as follow:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;-i. Local PE sends label withdraw
message to the remote if it<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;already sends
label mapping message, for it has changed its<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;control word
parameter.<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; -ii. Local PE MUST send a label request
messages to peer PE to<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;get peer's configured
control word parameter before sending<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;new label mapping
message to peer PE.<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;-iii. After receiving the new label
mapping message from peer PE<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;and updating
the remote label binding information, the<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Local PE should
send label mapping to peer PE according to<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;procedures defined
in [RFC4447].<br>
&gt; &gt;<br>
&gt; &gt; What does the item i) mean ? the English is not clear.<br>
&gt; &gt; Why does the PE have to do ii) ?<br>
&gt; &gt;<br>
&gt; &gt; All we really need is a statement on how the c-bit negotiation
state<br>
&gt; &gt; machine can be reset if one end has changed &quot;his mind&quot;
.<br>
&gt; &gt;<br>
&gt; &gt; Can we fix this document before &nbsp;issuing the -00 WG draft
version ?<br>
&gt; &gt;<br>
&gt; &gt; Thanks.<br>
&gt; &gt; Luca<br>
&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 001123CD48257856_=--


From lizhong.jin@zte.com.cn  Thu Mar 17 08:22:54 2011
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BC3C3A6954 for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 08:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.962
X-Spam-Level: 
X-Spam-Status: No, score=-100.962 tagged_above=-999 required=5 tests=[AWL=-0.877, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, 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 cxlf0SA6xxco for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 08:22:53 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 785BC3A6920 for <pwe3@ietf.org>; Thu, 17 Mar 2011 08:22:51 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 50831397396305; Thu, 17 Mar 2011 23:23:30 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.15] with StormMail ESMTP id 84746.8276511994; Thu, 17 Mar 2011 23:24:15 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p2HFO8So094616; Thu, 17 Mar 2011 23:24:08 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <C9A769B4.185D0%andrew.g.malis@one.verizon.com>
To: "Malis, Andrew G. (Andy)" <andrew.g.malis@verizon.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF180D60E5.9BB7A5F8-ON48257856.00547ABE-48257856.00549BDD@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Thu, 17 Mar 2011 23:23:54 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-17 23:24:10, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-17 23:24:10, Serialize complete at 2011-03-17 23:24:10, S/MIME Sign failed at 2011-03-17 23:24:10: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-03-17 23:24:12, Serialize complete at 2011-03-17 23:24:12
Content-Type: multipart/alternative; boundary="=_alternative 00549BDA48257856_="
X-MAIL: mse02.zte.com.cn p2HFO8So094616
Cc: Loa Andersson <loa.andersson@ericsson.com>, "lmartini@cisco.com" <lmartini@cisco.com>, "pwe3@ietf.org" <pwe3@ietf.org>, George Swallow <swallow@cisco.com>, Ross Callon <rcallon@juniper.net>, "Malis, Andrew G. \(Andy\)" <andrew.g.malis@verizon.com>
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt ( comment )
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 15:22:54 -0000

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

QW5keSwNClRoYW5rcyBmb3IgdGhlIHN1Z2dlc3Rpb24sIGFuZCB3aWxsIGRvIHRoZSBwcmVzZW50
YXRpb24gYXQgTVBMUy4NCg0KTGl6aG9uZw0KIA0KDQoiTWFsaXMsIEFuZHJldyBHLiAoQW5keSki
IDxhbmRyZXcuZy5tYWxpc0B2ZXJpem9uLmNvbT4gd3JvdGUgb24gMjAxMS0wMy0xNyANCjE5OjMz
OjA4Og0KDQo+IExpemhvbmcsDQo+IA0KPiBUaGFua3MuIFNpbmNlIHRoaXMgYWZmZWN0cyBMRFAs
IHlvdSBzaG91bGQgYXNrIGZvciB0aW1lIG9uIHRoZSBNUExTIA0KPiBXR6GvcyBhZ2VuZGEgdG8g
cHJlc2VudCBpdCB0aGVyZSBpbiBhZGRpdGlvbiB0byBwcmVzZW50aW5nIGl0IGluIFBXRTMuDQo+
IA0KPiBDaGVlcnMsDQo+IEFuZHkNCj4gDQo+IE9uIDMvMTYvMTEgMjM6MDcgLCAibGl6aG9uZy5q
aW5AenRlLmNvbS5jbiIgPGxpemhvbmcuamluQHp0ZS5jb20uY24+IA0Kd3JvdGU6DQoNCj4gDQo+
IEhpIEFuZHksIA0KPiBUaGFuayB5b3UgdmVyeSBtdWNoLiBXZSBoYXZlIHVwbG9hZGVkIHRoZSAw
NCB2ZXJzaW9uLiBQbGVhc2UgZ2V0IGl0IA0KPiBmcm9tIHRoZSBmb2xsb3dpbmcgbGluazogDQo+
IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWppbi1wd2UzLWNiaXQtbmVnb3RpYXRp
b24tMDQudHh0IA0KPiANCj4gUmVnYXJkcyANCj4gTGl6aG9uZyANCj4gDQo+IA0KPiBhbWFsaXNA
Z21haWwuY29tIHdyb3RlIG9uIDIwMTEtMDMtMDcgMjM6NTI6MjI6DQo+IA0KPiA+IExpemhvbmcs
DQo+ID4gDQo+ID4gVGhlcmUncyBiZWVuIGEgbG90IG9mIHN1cHBvcnQgZm9yIFdHIGFkb3B0aW9u
IG9mIHRoaXMgZHJhZnQuIFBsZWFzZQ0KPiA+IHVwZGF0ZSB0aGUgZHJhZnQgdG8gLTA0IHRvIHJl
ZmxlY3QgdGhlIGRpc2N1c3Npb24gb24gdGhlIGxpc3QgKGJlZm9yZQ0KPiA+IHRoZSB3aW5kb3cg
Y2xvc2VzIGluIGEgd2VlaykgYW5kIHdlJ2xsIGFubm91bmNlIHRoZSBhZG9wdGlvbiBpbg0KPiA+
IFByYWd1ZSwgZm9sbG93ZWQgYnkgaGF2aW5nIHlvdSBpc3N1ZSB0aGUgV0cgdmVyc2lvbiBvZiB0
aGUgZHJhZnQuDQo+ID4gDQo+ID4gVGhhbmtzLA0KPiA+IEFuZHkNCj4gPiANCj4gPiBPbiBUaHUs
IE1hciAzLCAyMDExIGF0IDEwOjQxIEFNLCAgPGxpemhvbmcuamluQHp0ZS5jb20uY24+IHdyb3Rl
Og0KPiA+ID4NCj4gPiA+IEx1Y2EsDQo+ID4gPiBBZnRlciBkaXNjdXNzaW5nIHdpdGggdGhlIGF1
dGhvcnMsIHdlIGRlY2lkZSB0byBhZGQgdGhlIHdhaXQgZm9yIA0KbGFiZWwNCj4gPiA+IHJlbGVh
c2UgYmVmb3JlIHNlbmRpbmcgbGFiZWwgcmVxdWVzdCwgdGhpcyB3b3VsZG4ndCBoYXJtIGFuZCBi
cmluZyANCnNvbWUNCj4gPiA+IHNlY3VyZS4NCj4gPiA+DQo+ID4gPiBUaGVuIGFyZSB5b3UgT0sg
d2l0aCB0aGUgZm9sbG93aW5nIHRleHQ/DQo+ID4gPg0KPiA+ID4gV2hlbiBMb2NhbCBQRSBjaGFu
Z2VzIGl0cyBjb250cm9sIHdvcmQgZnJvbSBOT1QgUFJFRkVSUkVEIHRvIA0KUFJFRkVSUkVEIGFu
ZA0KPiA+ID4gb25seSBpZiBpdCBhbHJlYWR5IHJlY2VpdmVkIHRoZSByZW1vdGUgbGFiZWwgbWFw
cGluZyBtZXNzYWdlIHdpdGggDQpDLWJpdD0wLA0KPiA+ID4gYWRkaXRpb25hbCBwcm9jZWR1cmUg
d2lsbCBiZSBhZGRlZCBhcyBmb2xsb3c6DQo+ID4gPiAtaSBMb2NhbCBQRSBNVVNUIHNlbmQgYSBs
YWJlbCB3aXRoZHJhdyBtZXNzYWdlIHRvIHJlbW90ZSBQRSBpZiBpdCANCmhhcw0KPiA+ID4gcHJl
dmlvdXNseSBzZW50IGEgbGFiZWwgbWFwcGluZywgYW5kIHdhaXQgdW50aWwgcmVjZWl2aW5nIGEg
bGFiZWwgDQpyZWxlYXNlDQo+ID4gPiBmcm9tIHRoZSByZW1vdGUgUEUuDQo+ID4gPiAtaWkgTG9j
YWwgUEUgTVVTVCBzZW5kIGEgbGFiZWwgcmVxdWVzdCBtZXNzYWdlIHRvIHJlbW90ZSBQRSwgYW5k
d2FpdCANCnVudGlsDQo+ID4gPiByZWNlaXZpbmcgYSBsYWJlbCBtYXBwaW5nIG1lc3NhZ2UgY29u
dGFpbmluZyB0aGUgcmVtb3RlIFBFIA0KY29uZmlndXJlZA0KPiA+ID4gY29udHJvbCB3b3JkIHNl
dHRpbmcuDQo+ID4gPiAtaWlpIEFmdGVyIHJlY2VpdmluZyByZW1vdGUgUEUgbGFiZWwgbWFwcGlu
ZyB3aXRoIGNvbnRyb2wgd29yZCANCnNldHRpbmcsDQo+ID4gPiBMb2NhbCBQRSBNVVNUIGZvbGxv
dyBwcm9jZWR1cmVzIGRlZmluZWQgaW4gW1JGQzQ0NDddIHNlY3Rpb24gNiANCj4gd2hlbiBzZW5k
aW5nDQo+ID4gPiBpdCdzIGxhYmVsIG1hcHBpbmcgbWVzc2FnZS4NCj4gPiA+DQo+ID4gPiBDb3Jy
ZXNwb25kaW5nbHksIHRoZSBtb2RpZmllZCBwcm9jZWR1cmUgb2YgUEUgaW4gZmlndXJlIDEgd2ls
bCBiZSBhcw0KPiA+ID4gZm9sbG93czoNCj4gPiA+DQo+ID4gPiAxLiBQRTIgY2hhbmdlcyBsb2Nh
bGx5IGNvbmZpZ3VyZWQgY29udHJvbCB3b3JkIHRvIFBSRUZFUlJFRC4NCj4gPiA+IDIuIFBFMiB3
aWxsIHRoZW4gc2VuZCBsYWJlbCB3aXRoZHJhdyBtZXNzYWdlIHRvIFBFMS4NCj4gPiA+IDMuIFBF
MSBNVVNUIHNlbmQgbGFiZWwgcmVsZWFzZSBpbiByZXBseSB0byBsYWJlbCB3aXRoZHJhdyANCj4g
bWVzc2FnZSBmcm9tIFBFMi4NCj4gPiA+IDQuIFVwb24gcmVjZWlwdCBvZiBMYWJlbCByZWxlYXNl
IG1lc3NhZ2UgZnJvbSBQRTEsIFBFMiBNVVNUIHNlbmQgDQpsYWJlbA0KPiA+ID4gcmVxdWVzdCBt
ZXNzYWdlcyB0byBQRTEgYWx0aG91Z2ggaXQgYWxyZWFkeSByZWNlaXZlZCB0aGUgbGFiZWwgDQo+
IG1hcHBpbmcgd2l0aA0KPiA+ID4gQy1iaXQ9MC4NCj4gPiA+IDUuIFBFMSBNVVNUIHNlbmQgbGFi
ZWwgbWFwcGluZyBtZXNzYWdlIHdpdGggQy1iaXQ9MSBhZ2FpbiB0byANClBFMihOb3RlOiBQRTEN
Cj4gPiA+IE1VU1Qgc2VuZCBsYWJlbCBtYXBwaW5nIHdpdGggbG9jYWxseSBjb25maWd1cmVkIENX
IHBhcmFtZXRlcikuDQo+ID4gPiA2LiBQRTIgcmVjZWl2ZXMgdGhlIGxhYmVsIG1hcHBpbmcgZnJv
bSBQRTEgYW5kIHVwZGF0ZXMgdGhlIHJlbW90ZSANCmxhYmVsDQo+ID4gPiBiaW5kaW5nIGluZm9y
bWF0aW9uLiBQRTIgTVVTVCB3YWl0IGZvciBQRTEgbGFiZWwgYmluZGluZyBiZWZvcmUgDQo+IHNl
bmRpbmcgaXRzDQo+ID4gPiBsYWJlbCBiaW5kaW5nIHdpdGggQy1iaXQgc2V0LCBvbmx5IGlmIGl0
IHByZXZpb3VzbHkgaGFkIGEgbGFiZWwgDQo+IGJpbmRpbmcgd2l0aA0KPiA+ID4gQy1iaXQgPSAw
IGZyb20gUEUxLg0KPiA+ID4gNy4gUEUyIHdpbGwgc2VuZCBsYWJlbCBtYXBwaW5nIHRvIFBFMSB3
aXRoIEMtYml0PTEuDQo+ID4gPg0KPiA+ID4gSXQgaXMgdG8gYmUgbm90ZWQgdGhhdCB0aGUgYWJv
dmUgYXNzdW1lIHRoYXQgUEUxIGlzIGNvbmZpZ3VyZWQgdG8gDQpzdXBwb3J0DQo+ID4gPiBDVywg
aG93ZXZlciBpbiBzdGVwIDUgaWYgUEUxIGRvZXNuJ3Qgc3VwcG9ydCBDVywgUEUxIHdvdWxkIHNl
bmQgdGhlIA0KbGFiZWwNCj4gPiA+IG1hcHBpbmcgbWVzc2FnZSB3aXRoIEMtYml0ID0wLCB0aGlz
IHdvdWxkIHJlc3VsdCBpbiBQRTIgaW4gc3RlcCANCj4gNyBzZW5kaW5nIGENCj4gPiA+IGxhYmVs
IG1hcHBpbmcgd2l0aCBDLWJpdD0wIGFzIHBlciBbUkZDNDQ0N10gQ1cgbmVnb3RpYXRpb24gDQpw
cm9jZWR1cmUuDQo+ID4gPg0KPiA+ID4gVGhhbmtzDQo+ID4gPiBMaXpob25nDQo+ID4gPg0KPiA+
ID4NCj4gPiA+IC0tLS0tLS0tLS0tLXNlbmQgYnkgTHVjYSANCj4gTWFydGluaS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gPiA+IE1hdHRoZXcgJiBBbmR5LA0K
PiA+ID4NCj4gPiA+DQo+ID4gPiBBbHRob3VnaCBJIHN1cHBvcnQgY2xhcmlmeWluZyB0aGlzIHBy
b2NlZHVyZSAsIEkgYmVsaWV2ZSB0aGlzIA0KZG9jdW1lbnQNCj4gPiA+IG5lZWRzIHNvbWUgd29y
ay4NCj4gPiA+IEluIHNlY3Rpb24gMyBmb3IgZXhhbXBsZSA6DQo+ID4gPg0KPiA+ID4gICAgV2hl
biBMb2NhbCBQRSBjaGFuZ2VzIGl0cyBjb250cm9sIHdvcmQgZnJvbSBOT1QgUFJFRkVSUkVEIHRv
DQo+ID4gPiAgICBQUkVGRVJSRUQgYW5kIG9ubHkgaWYgaXQgYWxyZWFkeSByZWNlaXZlZCB0aGUg
cmVtb3RlIGxhYmVsIA0KbWFwcGluZw0KPiA+ID4gICAgbWVzc2FnZSB3aXRoIEMtYml0PTAsIGFk
ZGl0aW9uYWwgcHJvY2VkdXJlIHdpbGwgYmUgYWRkZWQgYXMgDQpmb2xsb3c6DQo+ID4gPg0KPiA+
ID4gICAgICAgICAgLWkuIExvY2FsIFBFIHNlbmRzIGxhYmVsIHdpdGhkcmF3IG1lc3NhZ2UgdG8g
dGhlIHJlbW90ZSBpZiANCml0DQo+ID4gPiAgICAgICAgICAgICAgYWxyZWFkeSBzZW5kcyBsYWJl
bCBtYXBwaW5nIG1lc3NhZ2UsIGZvciBpdCBoYXMgY2hhbmdlZCANCml0cw0KPiA+ID4gICAgICAg
ICAgICAgIGNvbnRyb2wgd29yZCBwYXJhbWV0ZXIuDQo+ID4gPg0KPiA+ID4gICAgICAgICAtaWku
IExvY2FsIFBFIE1VU1Qgc2VuZCBhIGxhYmVsIHJlcXVlc3QgbWVzc2FnZXMgdG8gcGVlciBQRSAN
CnRvDQo+ID4gPiAgICAgICAgICAgICAgZ2V0IHBlZXIncyBjb25maWd1cmVkIGNvbnRyb2wgd29y
ZCBwYXJhbWV0ZXIgYmVmb3JlIA0Kc2VuZGluZw0KPiA+ID4gICAgICAgICAgICAgIG5ldyBsYWJl
bCBtYXBwaW5nIG1lc3NhZ2UgdG8gcGVlciBQRS4NCj4gPiA+DQo+ID4gPiAgICAgICAgLWlpaS4g
QWZ0ZXIgcmVjZWl2aW5nIHRoZSBuZXcgbGFiZWwgbWFwcGluZyBtZXNzYWdlIGZyb20gcGVlciAN
ClBFDQo+ID4gPiAgICAgICAgICAgICAgYW5kIHVwZGF0aW5nIHRoZSByZW1vdGUgbGFiZWwgYmlu
ZGluZyBpbmZvcm1hdGlvbiwgdGhlDQo+ID4gPiAgICAgICAgICAgICAgTG9jYWwgUEUgc2hvdWxk
IHNlbmQgbGFiZWwgbWFwcGluZyB0byBwZWVyIFBFIGFjY29yZGluZyANCnRvDQo+ID4gPiAgICAg
ICAgICAgICAgcHJvY2VkdXJlcyBkZWZpbmVkIGluIFtSRkM0NDQ3XS4NCj4gPiA+DQo+ID4gPiBX
aGF0IGRvZXMgdGhlIGl0ZW0gaSkgbWVhbiA/IHRoZSBFbmdsaXNoIGlzIG5vdCBjbGVhci4NCj4g
PiA+IFdoeSBkb2VzIHRoZSBQRSBoYXZlIHRvIGRvIGlpKSA/DQo+ID4gPg0KPiA+ID4gQWxsIHdl
IHJlYWxseSBuZWVkIGlzIGEgc3RhdGVtZW50IG9uIGhvdyB0aGUgYy1iaXQgbmVnb3RpYXRpb24g
c3RhdGUNCj4gPiA+IG1hY2hpbmUgY2FuIGJlIHJlc2V0IGlmIG9uZSBlbmQgaGFzIGNoYW5nZWQg
ImhpcyBtaW5kIiAuDQo+ID4gPg0KPiA+ID4gQ2FuIHdlIGZpeCB0aGlzIGRvY3VtZW50IGJlZm9y
ZSAgaXNzdWluZyB0aGUgLTAwIFdHIGRyYWZ0IHZlcnNpb24gPw0KPiA+ID4NCj4gPiA+IFRoYW5r
cy4NCj4gPiA+IEx1Y2ENCj4gPiA+DQo+IA0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpaVEUgSW5mb3JtYXRpb24gU2VjdXJpdHkg
Tm90aWNlOiBUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWFpbCBpcyBzb2xlbHkg
cHJvcGVydHkgb2YgdGhlIHNlbmRlcidzIG9yZ2FuaXphdGlvbi4gVGhpcyBtYWlsIGNvbW11bmlj
YXRpb24gaXMgY29uZmlkZW50aWFsLiBSZWNpcGllbnRzIG5hbWVkIGFib3ZlIGFyZSBvYmxpZ2F0
ZWQgdG8gbWFpbnRhaW4gc2VjcmVjeSBhbmQgYXJlIG5vdCBwZXJtaXR0ZWQgdG8gZGlzY2xvc2Ug
dGhlIGNvbnRlbnRzIG9mIHRoaXMgY29tbXVuaWNhdGlvbiB0byBvdGhlcnMuDQpUaGlzIGVtYWls
IGFuZCBhbnkgZmlsZXMgdHJhbnNtaXR0ZWQgd2l0aCBpdCBhcmUgY29uZmlkZW50aWFsIGFuZCBp
bnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IHRv
IHdob20gdGhleSBhcmUgYWRkcmVzc2VkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWls
IGluIGVycm9yIHBsZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3Igb2YgdGhlIG1lc3NhZ2UuIEFu
eSB2aWV3cyBleHByZXNzZWQgaW4gdGhpcyBtZXNzYWdlIGFyZSB0aG9zZSBvZiB0aGUgaW5kaXZp
ZHVhbCBzZW5kZXIuDQpUaGlzIG1lc3NhZ2UgaGFzIGJlZW4gc2Nhbm5lZCBmb3IgdmlydXNlcyBh
bmQgU3BhbSBieSBaVEUgQW50aS1TcGFtIHN5c3RlbS4NCg==
--=_alternative 00549BDA48257856_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkFuZHksPC9mb250Pg0KPGJyPjxm
b250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5UaGFua3MgZm9yIHRoZSBzdWdnZXN0aW9uLCBh
bmQgd2lsbA0KZG8gdGhlIHByZXNlbnRhdGlvbiBhdCBNUExTLjwvZm9udD4NCjxicj4NCjxicj48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+TGl6aG9uZzwvZm9udD4NCjxicj48Zm9udCBz
aXplPTEgZmFjZT0iQXJpYWwiPiZuYnNwOzwvZm9udD4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6
ZT0yPiZxdW90O01hbGlzLCBBbmRyZXcgRy4gKEFuZHkpJnF1b3Q7ICZsdDthbmRyZXcuZy5tYWxp
c0B2ZXJpem9uLmNvbSZndDsNCndyb3RlIG9uIDIwMTEtMDMtMTcgMTk6MzM6MDg6PGJyPg0KPGJy
Pg0KJmd0OyBMaXpob25nLDxicj4NCiZndDsgPGJyPg0KJmd0OyBUaGFua3MuIFNpbmNlIHRoaXMg
YWZmZWN0cyBMRFAsIHlvdSBzaG91bGQgYXNrIGZvciB0aW1lIG9uIHRoZSBNUExTDQo8YnI+DQom
Z3Q7IFdHoa9zIGFnZW5kYSB0byBwcmVzZW50IGl0IHRoZXJlIGluIGFkZGl0aW9uIHRvIHByZXNl
bnRpbmcgaXQgaW4NClBXRTMuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IENoZWVycyw8YnI+DQomZ3Q7
IEFuZHk8YnI+DQomZ3Q7IDxicj4NCiZndDsgT24gMy8xNi8xMSAyMzowNyAsICZxdW90O2xpemhv
bmcuamluQHp0ZS5jb20uY24mcXVvdDsgJmx0O2xpemhvbmcuamluQHp0ZS5jb20uY24mZ3Q7DQp3
cm90ZTo8YnI+DQo8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0K
Jmd0OyBIaSBBbmR5LCA8YnI+DQomZ3Q7IFRoYW5rIHlvdSB2ZXJ5IG11Y2guIFdlIGhhdmUgdXBs
b2FkZWQgdGhlIDA0IHZlcnNpb24uIFBsZWFzZSBnZXQgaXQNCjxicj4NCiZndDsgZnJvbSB0aGUg
Zm9sbG93aW5nIGxpbms6IDxicj4NCiZndDsgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJh
ZnQtamluLXB3ZTMtY2JpdC1uZWdvdGlhdGlvbi0wNC50eHQNCjxicj4NCiZndDsgPGJyPg0KJmd0
OyBSZWdhcmRzIDxicj4NCiZndDsgTGl6aG9uZyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0K
Jmd0OyBhbWFsaXNAZ21haWwuY29tIHdyb3RlIG9uIDIwMTEtMDMtMDcgMjM6NTI6MjI6PGJyPg0K
Jmd0OyA8YnI+DQomZ3Q7ICZndDsgTGl6aG9uZyw8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAm
Z3Q7IFRoZXJlJ3MgYmVlbiBhIGxvdCBvZiBzdXBwb3J0IGZvciBXRyBhZG9wdGlvbiBvZiB0aGlz
IGRyYWZ0Lg0KUGxlYXNlPGJyPg0KJmd0OyAmZ3Q7IHVwZGF0ZSB0aGUgZHJhZnQgdG8gLTA0IHRv
IHJlZmxlY3QgdGhlIGRpc2N1c3Npb24gb24gdGhlIGxpc3QNCihiZWZvcmU8YnI+DQomZ3Q7ICZn
dDsgdGhlIHdpbmRvdyBjbG9zZXMgaW4gYSB3ZWVrKSBhbmQgd2UnbGwgYW5ub3VuY2UgdGhlIGFk
b3B0aW9uDQppbjxicj4NCiZndDsgJmd0OyBQcmFndWUsIGZvbGxvd2VkIGJ5IGhhdmluZyB5b3Ug
aXNzdWUgdGhlIFdHIHZlcnNpb24gb2YgdGhlIGRyYWZ0Ljxicj4NCiZndDsgJmd0OyA8YnI+DQom
Z3Q7ICZndDsgVGhhbmtzLDxicj4NCiZndDsgJmd0OyBBbmR5PGJyPg0KJmd0OyAmZ3Q7IDxicj4N
CiZndDsgJmd0OyBPbiBUaHUsIE1hciAzLCAyMDExIGF0IDEwOjQxIEFNLCAmbmJzcDsmbHQ7bGl6
aG9uZy5qaW5AenRlLmNvbS5jbiZndDsNCndyb3RlOjxicj4NCiZndDsgJmd0OyAmZ3Q7PGJyPg0K
Jmd0OyAmZ3Q7ICZndDsgTHVjYSw8YnI+DQomZ3Q7ICZndDsgJmd0OyBBZnRlciBkaXNjdXNzaW5n
IHdpdGggdGhlIGF1dGhvcnMsIHdlIGRlY2lkZSB0byBhZGQgdGhlDQp3YWl0IGZvciBsYWJlbDxi
cj4NCiZndDsgJmd0OyAmZ3Q7IHJlbGVhc2UgYmVmb3JlIHNlbmRpbmcgbGFiZWwgcmVxdWVzdCwg
dGhpcyB3b3VsZG4ndCBoYXJtDQphbmQgYnJpbmcgc29tZTxicj4NCiZndDsgJmd0OyAmZ3Q7IHNl
Y3VyZS48YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IFRoZW4gYXJlIHlv
dSBPSyB3aXRoIHRoZSBmb2xsb3dpbmcgdGV4dD88YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZn
dDsgJmd0OyAmZ3Q7IFdoZW4gTG9jYWwgUEUgY2hhbmdlcyBpdHMgY29udHJvbCB3b3JkIGZyb20g
Tk9UIFBSRUZFUlJFRA0KdG8gUFJFRkVSUkVEIGFuZDxicj4NCiZndDsgJmd0OyAmZ3Q7IG9ubHkg
aWYgaXQgYWxyZWFkeSByZWNlaXZlZCB0aGUgcmVtb3RlIGxhYmVsIG1hcHBpbmcgbWVzc2FnZQ0K
d2l0aCBDLWJpdD0wLDxicj4NCiZndDsgJmd0OyAmZ3Q7IGFkZGl0aW9uYWwgcHJvY2VkdXJlIHdp
bGwgYmUgYWRkZWQgYXMgZm9sbG93Ojxicj4NCiZndDsgJmd0OyAmZ3Q7IC1pIExvY2FsIFBFIE1V
U1Qgc2VuZCBhIGxhYmVsIHdpdGhkcmF3IG1lc3NhZ2UgdG8gcmVtb3RlDQpQRSBpZiBpdCBoYXM8
YnI+DQomZ3Q7ICZndDsgJmd0OyBwcmV2aW91c2x5IHNlbnQgYSBsYWJlbCBtYXBwaW5nLCBhbmQg
d2FpdCB1bnRpbCByZWNlaXZpbmcNCmEgbGFiZWwgcmVsZWFzZTxicj4NCiZndDsgJmd0OyAmZ3Q7
IGZyb20gdGhlIHJlbW90ZSBQRS48YnI+DQomZ3Q7ICZndDsgJmd0OyAtaWkgTG9jYWwgUEUgTVVT
VCBzZW5kIGEgbGFiZWwgcmVxdWVzdCBtZXNzYWdlIHRvIHJlbW90ZQ0KUEUsIGFuZHdhaXQgdW50
aWw8YnI+DQomZ3Q7ICZndDsgJmd0OyByZWNlaXZpbmcgYSBsYWJlbCBtYXBwaW5nIG1lc3NhZ2Ug
Y29udGFpbmluZyB0aGUgcmVtb3RlDQpQRSBjb25maWd1cmVkPGJyPg0KJmd0OyAmZ3Q7ICZndDsg
Y29udHJvbCB3b3JkIHNldHRpbmcuPGJyPg0KJmd0OyAmZ3Q7ICZndDsgLWlpaSBBZnRlciByZWNl
aXZpbmcgcmVtb3RlIFBFIGxhYmVsIG1hcHBpbmcgd2l0aCBjb250cm9sDQp3b3JkIHNldHRpbmcs
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgTG9jYWwgUEUgTVVTVCBmb2xsb3cgcHJvY2VkdXJlcyBkZWZp
bmVkIGluIFtSRkM0NDQ3XSBzZWN0aW9uDQo2IDxicj4NCiZndDsgd2hlbiBzZW5kaW5nPGJyPg0K
Jmd0OyAmZ3Q7ICZndDsgaXQncyBsYWJlbCBtYXBwaW5nIG1lc3NhZ2UuPGJyPg0KJmd0OyAmZ3Q7
ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyBDb3JyZXNwb25kaW5nbHksIHRoZSBtb2RpZmllZCBw
cm9jZWR1cmUgb2YgUEUgaW4gZmlndXJlDQoxIHdpbGwgYmUgYXM8YnI+DQomZ3Q7ICZndDsgJmd0
OyBmb2xsb3dzOjxicj4NCiZndDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgMS4gUEUy
IGNoYW5nZXMgbG9jYWxseSBjb25maWd1cmVkIGNvbnRyb2wgd29yZCB0byBQUkVGRVJSRUQuPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgMi4gUEUyIHdpbGwgdGhlbiBzZW5kIGxhYmVsIHdpdGhkcmF3IG1l
c3NhZ2UgdG8gUEUxLjxicj4NCiZndDsgJmd0OyAmZ3Q7IDMuIFBFMSBNVVNUIHNlbmQgbGFiZWwg
cmVsZWFzZSBpbiByZXBseSB0byBsYWJlbCB3aXRoZHJhdw0KPGJyPg0KJmd0OyBtZXNzYWdlIGZy
b20gUEUyLjxicj4NCiZndDsgJmd0OyAmZ3Q7IDQuIFVwb24gcmVjZWlwdCBvZiBMYWJlbCByZWxl
YXNlIG1lc3NhZ2UgZnJvbSBQRTEsIFBFMiBNVVNUDQpzZW5kIGxhYmVsPGJyPg0KJmd0OyAmZ3Q7
ICZndDsgcmVxdWVzdCBtZXNzYWdlcyB0byBQRTEgYWx0aG91Z2ggaXQgYWxyZWFkeSByZWNlaXZl
ZCB0aGUNCmxhYmVsIDxicj4NCiZndDsgbWFwcGluZyB3aXRoPGJyPg0KJmd0OyAmZ3Q7ICZndDsg
Qy1iaXQ9MC48YnI+DQomZ3Q7ICZndDsgJmd0OyA1LiBQRTEgTVVTVCBzZW5kIGxhYmVsIG1hcHBp
bmcgbWVzc2FnZSB3aXRoIEMtYml0PTEgYWdhaW4NCnRvIFBFMihOb3RlOiBQRTE8YnI+DQomZ3Q7
ICZndDsgJmd0OyBNVVNUIHNlbmQgbGFiZWwgbWFwcGluZyB3aXRoIGxvY2FsbHkgY29uZmlndXJl
ZCBDVyBwYXJhbWV0ZXIpLjxicj4NCiZndDsgJmd0OyAmZ3Q7IDYuIFBFMiByZWNlaXZlcyB0aGUg
bGFiZWwgbWFwcGluZyBmcm9tIFBFMSBhbmQgdXBkYXRlcyB0aGUNCnJlbW90ZSBsYWJlbDxicj4N
CiZndDsgJmd0OyAmZ3Q7IGJpbmRpbmcgaW5mb3JtYXRpb24uIFBFMiBNVVNUIHdhaXQgZm9yIFBF
MSBsYWJlbCBiaW5kaW5nDQpiZWZvcmUgPGJyPg0KJmd0OyBzZW5kaW5nIGl0czxicj4NCiZndDsg
Jmd0OyAmZ3Q7IGxhYmVsIGJpbmRpbmcgd2l0aCBDLWJpdCBzZXQsIG9ubHkgaWYgaXQgcHJldmlv
dXNseSBoYWQNCmEgbGFiZWwgPGJyPg0KJmd0OyBiaW5kaW5nIHdpdGg8YnI+DQomZ3Q7ICZndDsg
Jmd0OyBDLWJpdCA9IDAgZnJvbSBQRTEuPGJyPg0KJmd0OyAmZ3Q7ICZndDsgNy4gUEUyIHdpbGwg
c2VuZCBsYWJlbCBtYXBwaW5nIHRvIFBFMSB3aXRoIEMtYml0PTEuPGJyPg0KJmd0OyAmZ3Q7ICZn
dDs8YnI+DQomZ3Q7ICZndDsgJmd0OyBJdCBpcyB0byBiZSBub3RlZCB0aGF0IHRoZSBhYm92ZSBh
c3N1bWUgdGhhdCBQRTEgaXMgY29uZmlndXJlZA0KdG8gc3VwcG9ydDxicj4NCiZndDsgJmd0OyAm
Z3Q7IENXLCBob3dldmVyIGluIHN0ZXAgNSBpZiBQRTEgZG9lc24ndCBzdXBwb3J0IENXLCBQRTEg
d291bGQNCnNlbmQgdGhlIGxhYmVsPGJyPg0KJmd0OyAmZ3Q7ICZndDsgbWFwcGluZyBtZXNzYWdl
IHdpdGggQy1iaXQgPTAsIHRoaXMgd291bGQgcmVzdWx0IGluIFBFMg0KaW4gc3RlcCA8YnI+DQom
Z3Q7IDcgc2VuZGluZyBhPGJyPg0KJmd0OyAmZ3Q7ICZndDsgbGFiZWwgbWFwcGluZyB3aXRoIEMt
Yml0PTAgYXMgcGVyIFtSRkM0NDQ3XSBDVyBuZWdvdGlhdGlvbg0KcHJvY2VkdXJlLjxicj4NCiZn
dDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgVGhhbmtzPGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgTGl6aG9uZzxicj4NCiZndDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDs8YnI+DQom
Z3Q7ICZndDsgJmd0OyAtLS0tLS0tLS0tLS1zZW5kIGJ5IEx1Y2EgPGJyPg0KJmd0OyBNYXJ0aW5p
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCiZndDsgJmd0
OyAmZ3Q7IE1hdHRoZXcgJmFtcDsgQW5keSw8YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsg
Jmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgQWx0aG91Z2ggSSBzdXBwb3J0IGNsYXJpZnlp
bmcgdGhpcyBwcm9jZWR1cmUgLCBJIGJlbGlldmUNCnRoaXMgZG9jdW1lbnQ8YnI+DQomZ3Q7ICZn
dDsgJmd0OyBuZWVkcyBzb21lIHdvcmsuPGJyPg0KJmd0OyAmZ3Q7ICZndDsgSW4gc2VjdGlvbiAz
IGZvciBleGFtcGxlIDo8YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7ICZu
YnNwOyAmbmJzcDtXaGVuIExvY2FsIFBFIGNoYW5nZXMgaXRzIGNvbnRyb2wgd29yZCBmcm9tDQpO
T1QgUFJFRkVSUkVEIHRvPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO1BSRUZFUlJF
RCBhbmQgb25seSBpZiBpdCBhbHJlYWR5IHJlY2VpdmVkIHRoZQ0KcmVtb3RlIGxhYmVsIG1hcHBp
bmc8YnI+DQomZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7bWVzc2FnZSB3aXRoIEMtYml0PTAs
IGFkZGl0aW9uYWwgcHJvY2VkdXJlDQp3aWxsIGJlIGFkZGVkIGFzIGZvbGxvdzo8YnI+DQomZ3Q7
ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDstaS4gTG9jYWwgUEUgc2VuZHMgbGFiZWwNCndpdGhkcmF3IG1lc3NhZ2UgdG8gdGhl
IHJlbW90ZSBpZiBpdDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2FscmVhZHkNCnNlbmRzIGxhYmVsIG1hcHBpbmcgbWVz
c2FnZSwgZm9yIGl0IGhhcyBjaGFuZ2VkIGl0czxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2NvbnRyb2wNCndvcmQgcGFy
YW1ldGVyLjxicj4NCiZndDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7IC1paS4gTG9jYWwgUEUgTVVTVCBzZW5kIGEgbGFiZWwNCnJlcXVl
c3QgbWVzc2FnZXMgdG8gcGVlciBQRSB0bzxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2dldCBwZWVyJ3MNCmNvbmZpZ3Vy
ZWQgY29udHJvbCB3b3JkIHBhcmFtZXRlciBiZWZvcmUgc2VuZGluZzxicj4NCiZndDsgJmd0OyAm
Z3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO25ldyBs
YWJlbA0KbWFwcGluZyBtZXNzYWdlIHRvIHBlZXIgUEUuPGJyPg0KJmd0OyAmZ3Q7ICZndDs8YnI+
DQomZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDstaWlpLiBBZnRlciBy
ZWNlaXZpbmcgdGhlIG5ldw0KbGFiZWwgbWFwcGluZyBtZXNzYWdlIGZyb20gcGVlciBQRTxicj4N
CiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwO2FuZCB1cGRhdGluZw0KdGhlIHJlbW90ZSBsYWJlbCBiaW5kaW5nIGluZm9ybWF0aW9u
LCB0aGU8YnI+DQomZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDtMb2NhbCBQRQ0Kc2hvdWxkIHNlbmQgbGFiZWwgbWFwcGluZyB0byBw
ZWVyIFBFIGFjY29yZGluZyB0bzxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3Byb2NlZHVyZXMNCmRlZmluZWQgaW4gW1JG
QzQ0NDddLjxicj4NCiZndDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgV2hhdCBkb2Vz
IHRoZSBpdGVtIGkpIG1lYW4gPyB0aGUgRW5nbGlzaCBpcyBub3QgY2xlYXIuPGJyPg0KJmd0OyAm
Z3Q7ICZndDsgV2h5IGRvZXMgdGhlIFBFIGhhdmUgdG8gZG8gaWkpID88YnI+DQomZ3Q7ICZndDsg
Jmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IEFsbCB3ZSByZWFsbHkgbmVlZCBpcyBhIHN0YXRlbWVu
dCBvbiBob3cgdGhlIGMtYml0IG5lZ290aWF0aW9uDQpzdGF0ZTxicj4NCiZndDsgJmd0OyAmZ3Q7
IG1hY2hpbmUgY2FuIGJlIHJlc2V0IGlmIG9uZSBlbmQgaGFzIGNoYW5nZWQgJnF1b3Q7aGlzIG1p
bmQmcXVvdDsNCi48YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IENhbiB3
ZSBmaXggdGhpcyBkb2N1bWVudCBiZWZvcmUgJm5ic3A7aXNzdWluZyB0aGUgLTAwIFdHDQpkcmFm
dCB2ZXJzaW9uID88YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IFRoYW5r
cy48YnI+DQomZ3Q7ICZndDsgJmd0OyBMdWNhPGJyPg0KJmd0OyAmZ3Q7ICZndDs8YnI+DQomZ3Q7
IDwvZm9udD48L3R0Pg0KPGJyPjxwcmU+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFJm5ic3A7SW5mb3JtYXRpb24mbmJzcDtTZWN1
cml0eSZuYnNwO05vdGljZTombmJzcDtUaGUmbmJzcDtpbmZvcm1hdGlvbiZuYnNwO2NvbnRhaW5l
ZCZuYnNwO2luJm5ic3A7dGhpcyZuYnNwO21haWwmbmJzcDtpcyZuYnNwO3NvbGVseSZuYnNwO3By
b3BlcnR5Jm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtzZW5kZXIncyZuYnNwO29yZ2FuaXphdGlvbi4m
bmJzcDtUaGlzJm5ic3A7bWFpbCZuYnNwO2NvbW11bmljYXRpb24mbmJzcDtpcyZuYnNwO2NvbmZp
ZGVudGlhbC4mbmJzcDtSZWNpcGllbnRzJm5ic3A7bmFtZWQmbmJzcDthYm92ZSZuYnNwO2FyZSZu
YnNwO29ibGlnYXRlZCZuYnNwO3RvJm5ic3A7bWFpbnRhaW4mbmJzcDtzZWNyZWN5Jm5ic3A7YW5k
Jm5ic3A7YXJlJm5ic3A7bm90Jm5ic3A7cGVybWl0dGVkJm5ic3A7dG8mbmJzcDtkaXNjbG9zZSZu
YnNwO3RoZSZuYnNwO2NvbnRlbnRzJm5ic3A7b2YmbmJzcDt0aGlzJm5ic3A7Y29tbXVuaWNhdGlv
biZuYnNwO3RvJm5ic3A7b3RoZXJzLg0KVGhpcyZuYnNwO2VtYWlsJm5ic3A7YW5kJm5ic3A7YW55
Jm5ic3A7ZmlsZXMmbmJzcDt0cmFuc21pdHRlZCZuYnNwO3dpdGgmbmJzcDtpdCZuYnNwO2FyZSZu
YnNwO2NvbmZpZGVudGlhbCZuYnNwO2FuZCZuYnNwO2ludGVuZGVkJm5ic3A7c29sZWx5Jm5ic3A7
Zm9yJm5ic3A7dGhlJm5ic3A7dXNlJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtpbmRpdmlkdWFsJm5i
c3A7b3ImbmJzcDtlbnRpdHkmbmJzcDt0byZuYnNwO3dob20mbmJzcDt0aGV5Jm5ic3A7YXJlJm5i
c3A7YWRkcmVzc2VkLiZuYnNwO0lmJm5ic3A7eW91Jm5ic3A7aGF2ZSZuYnNwO3JlY2VpdmVkJm5i
c3A7dGhpcyZuYnNwO2VtYWlsJm5ic3A7aW4mbmJzcDtlcnJvciZuYnNwO3BsZWFzZSZuYnNwO25v
dGlmeSZuYnNwO3RoZSZuYnNwO29yaWdpbmF0b3ImbmJzcDtvZiZuYnNwO3RoZSZuYnNwO21lc3Nh
Z2UuJm5ic3A7QW55Jm5ic3A7dmlld3MmbmJzcDtleHByZXNzZWQmbmJzcDtpbiZuYnNwO3RoaXMm
bmJzcDttZXNzYWdlJm5ic3A7YXJlJm5ic3A7dGhvc2UmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO2lu
ZGl2aWR1YWwmbmJzcDtzZW5kZXIuDQpUaGlzJm5ic3A7bWVzc2FnZSZuYnNwO2hhcyZuYnNwO2Jl
ZW4mbmJzcDtzY2FubmVkJm5ic3A7Zm9yJm5ic3A7dmlydXNlcyZuYnNwO2FuZCZuYnNwO1NwYW0m
bmJzcDtieSZuYnNwO1pURSZuYnNwO0FudGktU3BhbSZuYnNwO3N5c3RlbS4NCjwvcHJlPg==
--=_alternative 00549BDA48257856_=--


From nick.delregno@verizon.com  Thu Mar 17 08:53:27 2011
Return-Path: <nick.delregno@verizon.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 873BD3A69A4 for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 08:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.194
X-Spam-Level: 
X-Spam-Status: No, score=-3.194 tagged_above=-999 required=5 tests=[AWL=0.405,  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 N79C1LFNjaR7 for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 08:53:26 -0700 (PDT)
Received: from ashesmtp03.verizonbusiness.com (ashesmtp03.verizonbusiness.com [198.4.8.167]) by core3.amsl.com (Postfix) with ESMTP id 9A0BA3A69A3 for <pwe3@ietf.org>; Thu, 17 Mar 2011 08:53:26 -0700 (PDT)
Received: from omzismtp01.vzbi.com ([unknown] [165.122.46.164]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI700DVHLJAY220@firewall.verizonbusiness.com> for pwe3@ietf.org; Thu, 17 Mar 2011 15:54:52 +0000 (GMT)
Received: from omzismtp01.vzbi.com ([unknown] [127.0.0.1]) by omzismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI700N2YLJE3100@omzismtp01.vzbi.com> for pwe3@ietf.org; Thu, 17 Mar 2011 15:54:51 +0000 (GMT)
Received: from ASHSRV140.mcilink.com ([unknown] [153.39.68.166]) by omzismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI700NBULJD2C00@omzismtp01.vzbi.com> for pwe3@ietf.org; Thu, 17 Mar 2011 15:54:50 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV140.mcilink.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 17 Mar 2011 15:54:50 +0000
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, 17 Mar 2011 15:54:44 +0000
Message-id: <14584D6EE26B314187A4F68BA206060006E29781@ASHEVS008.mcilink.com>
In-reply-to: <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
Thread-index: Acvdm33bS8HQGFieTSSSyunk7NkzBAAABRxQAWJa3CAAZZvvwA==
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com> <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il>
From: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
To: Yaakov Stein <yaakov_s@rad.com>
X-OriginalArrivalTime: 17 Mar 2011 15:54:50.0584 (UTC) FILETIME=[A6095D80:01CBE4BB]
Cc: pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 15:53:27 -0000

Yaakov:

I'll take a look.  We did have one respondent answer twice, with the
second the same as the first except for one addition and a response to
the open-ended question.  I merged the response and the results of that
should have been reflected in the results, but I'll double check.

Thanks,
Nick

-----Original Message-----
From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
Sent: Tuesday, March 15, 2011 10:42 AM
To: Delregno, Christopher N (Nick DelRegno)
Cc: pwe3
Subject: RE: [PWE3] FW: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00

Nick,=20

In section 2.2 the percentages make sense under the assumption of 18
respondents :
5.6%   =3D  1 / 18
11.1%  =3D  2 / 18
16.7%  =3D  3 / 18
22.2%  =3D  4 / 18
44.4%  =3D  8 / 18
77.8%  =3D 14 / 18=20

but section 2.1 only lists 17 :
1.	Time Warner Cable
2.	Bright House Networks
3.	Tinet
4.	AboveNet
5.	Telecom New Zealand
6.	Cox Communications
7.	MTN South Africa
8.	Wipro Technologies
9.	Verizon
10.	AMS-IX
11.	Superonline
12.	Deutsche Telekom AG
13.	Internet Solution
14.	Easynet Global Services
15.	Telstra Corporation
16.	OJSC MegaFon
17.	France Telecom Orange

Did you leave someone off, or did someone answer twice ?

Y(J)S


-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Delregno, Christopher N (Nick DelRegno)
Sent: Tuesday, March 08, 2011 16:27
To: pwe3
Subject: [PWE3] FW: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00

Folks:

The 00 draft of the PW/VCCV Implementation Survey Results have been
uploaded.  I will be presenting the results at IETF80.

https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-resu
lts/

Thanks,
Nick

Christopher N. Del Regno, PMTS
C&T, Ethernet Network Architecture & Design
400 International Pkwy
Richardson, TX  75081
972-729-3411
nick.delregno@verizon.com




-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20
Sent: Tuesday, March 08, 2011 8:16 AM
To: Delregno, Christopher N (Nick DelRegno)
Subject: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00


A new version of I-D, draft-delregno-pw-vccv-impl-survey-results-00.txt
has been successfully submitted by Nick Del Regno and posted to the IETF
repository.

Filename:	 draft-delregno-pw-vccv-impl-survey-results
Revision:	 00
Title:		 The Pseudowire (PW) & Virtual Circuit Connectivity
Verification (VCCV) Implementation Survey Results
Creation_date:	 2011-03-07
WG ID:		 Independent Submission
Number_of_pages: 16

Abstract:
Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate
the use of the Control Word (CW) in order to better emulate the
services for which the encapsulations have been defined.  However,
some encapulations treat the Control Word as optional.  As a result,
implementations of the CW, for encapsulations for which it is
optional, vary by equipment manufacturer, equipment model and service
provider network.  Similarly, Virtual Circuit Connectivity
Verification (VCCV) supports three Control Channel (CC) types and
multiple Connectivity Verification (CV) Types.  This flexibility has
led to reports of interoperability issues within deployed networks
and associated drafts to attempt to remedy the situation.  This
survey of the PW/VCCV user community was conducted to determine
implementation trends.  The survey and results is presented herein.
=20



The IETF Secretariat.


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

From nick.delregno@verizon.com  Thu Mar 17 08:59:16 2011
Return-Path: <nick.delregno@verizon.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79EEB3A69FF for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 08:59:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.239
X-Spam-Level: 
X-Spam-Status: No, score=-3.239 tagged_above=-999 required=5 tests=[AWL=0.360,  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 RCszUaw1rTtb for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 08:59:15 -0700 (PDT)
Received: from ashesmtp02.verizonbusiness.com (ashesmtp02.verizonbusiness.com [198.4.8.166]) by core3.amsl.com (Postfix) with ESMTP id 54A163A6A50 for <pwe3@ietf.org>; Thu, 17 Mar 2011 08:59:15 -0700 (PDT)
Received: from omzismtp01.vzbi.com ([unknown] [165.122.46.164]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI7004J4LT62U30@firewall.verizonbusiness.com> for pwe3@ietf.org; Thu, 17 Mar 2011 16:00:43 +0000 (GMT)
Received: from omzismtp01.vzbi.com ([unknown] [127.0.0.1]) by omzismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI700NMXLT64200@omzismtp01.vzbi.com> for pwe3@ietf.org; Thu, 17 Mar 2011 16:00:42 +0000 (GMT)
Received: from ASHSRV140.mcilink.com ([unknown] [153.39.68.166]) by omzismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI700N6DLT54G00@omzismtp01.vzbi.com> for pwe3@ietf.org; Thu, 17 Mar 2011 16:00:42 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV140.mcilink.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 17 Mar 2011 16:00:41 +0000
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, 17 Mar 2011 16:00:35 +0000
Message-id: <14584D6EE26B314187A4F68BA206060006E29798@ASHEVS008.mcilink.com>
In-reply-to: <4D7F944E.2040903@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
Thread-index: AcvjLnPWT1ZSW6eOStCj2s8R0VDQzwBjTU9w
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com> <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il> <4D7F944E.2040903@cisco.com>
From: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
To: Luca Martini <lmartini@cisco.com>
X-OriginalArrivalTime: 17 Mar 2011 16:00:41.0658 (UTC) FILETIME=[774B01A0:01CBE4BC]
Cc: Yaakov Stein <yaakov_s@rad.com>, pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 15:59:16 -0000

Luca:

Yes, the plan is to publish as informational.

Regarding Section 2.7 Item 5, this was verbatim response from the
open-ended question.  As such, I didn't edit the responses for anything
other than explicit company names as denoted by "COMPANY" and "EQUIPMENT
MANUFACTURER".

I agree that AToM is a Cisco marketing term.  I believe the respondent
used the term loosely since there was no specific reference to the
EQUIPMENT MANUFACTURER providing that service.

Nick

-----Original Message-----
From: Luca Martini [mailto:lmartini@cisco.com]=20
Sent: Tuesday, March 15, 2011 11:31 AM
To: Delregno, Christopher N (Nick DelRegno)
Cc: Yaakov Stein; pwe3
Subject: Re: [PWE3] FW: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00

Nick,
Good survey, thanks for the work.

Are we going to publish this as informational ?
I think we should .
Also there is a mention of AToM in section 2.7 item 5 . It should be
changed to PWE ( AToM is a cisco marketing term , so we want o keep this
anonymous )
Thanks.
Luca



On 03/15/2011 09:41 AM, Yaakov Stein wrote:
> Nick,=20
>
> In section 2.2 the percentages make sense under the assumption of 18
respondents :
> 5.6%   =3D  1 / 18
> 11.1%  =3D  2 / 18
> 16.7%  =3D  3 / 18
> 22.2%  =3D  4 / 18
> 44.4%  =3D  8 / 18
> 77.8%  =3D 14 / 18=20
>
> but section 2.1 only lists 17 :
> 1.	Time Warner Cable
> 2.	Bright House Networks
> 3.	Tinet
> 4.	AboveNet
> 5.	Telecom New Zealand
> 6.	Cox Communications
> 7.	MTN South Africa
> 8.	Wipro Technologies
> 9.	Verizon
> 10.	AMS-IX
> 11.	Superonline
> 12.	Deutsche Telekom AG
> 13.	Internet Solution
> 14.	Easynet Global Services
> 15.	Telstra Corporation
> 16.	OJSC MegaFon
> 17.	France Telecom Orange
>
> Did you leave someone off, or did someone answer twice ?
>
> Y(J)S
>
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf
Of Delregno, Christopher N (Nick DelRegno)
> Sent: Tuesday, March 08, 2011 16:27
> To: pwe3
> Subject: [PWE3] FW: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00
>
> Folks:
>
> The 00 draft of the PW/VCCV Implementation Survey Results have been
uploaded.  I will be presenting the results at IETF80.
>
>
https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-resu
lts/
>
> Thanks,
> Nick
>
> Christopher N. Del Regno, PMTS
> C&T, Ethernet Network Architecture & Design
> 400 International Pkwy
> Richardson, TX  75081
> 972-729-3411
> nick.delregno@verizon.com
>
>
>
>
> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20
> Sent: Tuesday, March 08, 2011 8:16 AM
> To: Delregno, Christopher N (Nick DelRegno)
> Subject: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00
>
>
> A new version of I-D,
draft-delregno-pw-vccv-impl-survey-results-00.txt has been successfully
submitted by Nick Del Regno and posted to the IETF repository.
>
> Filename:	 draft-delregno-pw-vccv-impl-survey-results
> Revision:	 00
> Title:		 The Pseudowire (PW) & Virtual Circuit
Connectivity Verification (VCCV) Implementation Survey Results
> Creation_date:	 2011-03-07
> WG ID:		 Independent Submission
> Number_of_pages: 16
>
> Abstract:
> Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate
> the use of the Control Word (CW) in order to better emulate the
> services for which the encapsulations have been defined.  However,
> some encapulations treat the Control Word as optional.  As a result,
> implementations of the CW, for encapsulations for which it is
> optional, vary by equipment manufacturer, equipment model and service
> provider network.  Similarly, Virtual Circuit Connectivity
> Verification (VCCV) supports three Control Channel (CC) types and
> multiple Connectivity Verification (CV) Types.  This flexibility has
> led to reports of interoperability issues within deployed networks
> and associated drafts to attempt to remedy the situation.  This
> survey of the PW/VCCV user community was conducted to determine
> implementation trends.  The survey and results is presented herein.
>

>
>
> The IETF Secretariat.
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3


From nick.delregno@verizon.com  Thu Mar 17 09:08:23 2011
Return-Path: <nick.delregno@verizon.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C023A3A69B3 for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 09:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.275
X-Spam-Level: 
X-Spam-Status: No, score=-3.275 tagged_above=-999 required=5 tests=[AWL=0.324,  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 MwGizCiO01gp for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 09:08:22 -0700 (PDT)
Received: from ashesmtp03.verizonbusiness.com (ashesmtp03.verizonbusiness.com [198.4.8.167]) by core3.amsl.com (Postfix) with ESMTP id A882D3A698C for <pwe3@ietf.org>; Thu, 17 Mar 2011 09:08:22 -0700 (PDT)
Received: from pdcismtp01.vzbi.com ([unknown] [166.40.77.67]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI700D7HLXFY260@firewall.verizonbusiness.com> for pwe3@ietf.org; Thu, 17 Mar 2011 16:03:16 +0000 (GMT)
Received: from pdcismtp01.vzbi.com ([unknown] [127.0.0.1]) by pdcismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI7007HLLXFDV00@pdcismtp01.vzbi.com> for pwe3@ietf.org; Thu, 17 Mar 2011 16:03:15 +0000 (GMT)
Received: from ASHSRV139.mcilink.com ([unknown] [153.39.68.165]) by pdcismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI70077MLXFI700@pdcismtp01.vzbi.com> for pwe3@ietf.org; Thu, 17 Mar 2011 16:03:15 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV139.mcilink.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 17 Mar 2011 16:03:15 +0000
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, 17 Mar 2011 16:03:09 +0000
Message-id: <14584D6EE26B314187A4F68BA206060006E297A0@ASHEVS008.mcilink.com>
In-reply-to: <538B1799-C583-4192-B170-170F00FEDA7D@lucidvision.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
Thread-index: AcvjRbaSRUqIhBMGSDOKn0hAPrBRPwBdscoQ
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com> <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il> <4D7F944E.2040903@cisco.com> <538B1799-C583-4192-B170-170F00FEDA7D@lucidvision.com>
From: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>, Luca Martini <lmartini@cisco.com>
X-OriginalArrivalTime: 17 Mar 2011 16:03:15.0536 (UTC) FILETIME=[D302ED00:01CBE4BC]
Cc: Yaakov Stein <yaakov_s@rad.com>, pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 16:08:23 -0000

Tom:

Please pose that question to the WG (maybe that's what you were doing).
When we crafted the survey, omitting BFD was an oversight.  However, the
list of questions was sent to the WG for comment before the survey was
conducted.  If the WG would like, I can contact the respondents directly
to inquire of their BFD usage as well.  However, I don't think the
survey should be reopened.

Thanks,
Nick

-----Original Message-----
From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]=20
Sent: Tuesday, March 15, 2011 2:18 PM
To: Luca Martini
Cc: Delregno, Christopher N (Nick DelRegno); Yaakov Stein; pwe3
Subject: Re: [PWE3] FW: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00


	One thing I'd ask is that we augment the survey to ask about the
BFD mode for=20
VCCV. It seems to have been left out of the survey, potentially skewing
the results.=20
As I understand it, this is the most popular mode.

	--Tom




On Mar 15, 2011, at 12:31 PM, Luca Martini wrote:

> Nick,
> Good survey, thanks for the work.
>=20
> Are we going to publish this as informational ?
> I think we should .
> Also there is a mention of AToM in section 2.7 item 5 . It should be
> changed to PWE ( AToM is a cisco marketing term , so we want o keep
this
> anonymous )
> Thanks.
> Luca
>=20
>=20
>=20
> On 03/15/2011 09:41 AM, Yaakov Stein wrote:
>> Nick,=20
>>=20
>> In section 2.2 the percentages make sense under the assumption of 18
respondents :
>> 5.6%   =3D  1 / 18
>> 11.1%  =3D  2 / 18
>> 16.7%  =3D  3 / 18
>> 22.2%  =3D  4 / 18
>> 44.4%  =3D  8 / 18
>> 77.8%  =3D 14 / 18=20
>>=20
>> but section 2.1 only lists 17 :
>> 1.	Time Warner Cable
>> 2.	Bright House Networks
>> 3.	Tinet
>> 4.	AboveNet
>> 5.	Telecom New Zealand
>> 6.	Cox Communications
>> 7.	MTN South Africa
>> 8.	Wipro Technologies
>> 9.	Verizon
>> 10.	AMS-IX
>> 11.	Superonline
>> 12.	Deutsche Telekom AG
>> 13.	Internet Solution
>> 14.	Easynet Global Services
>> 15.	Telstra Corporation
>> 16.	OJSC MegaFon
>> 17.	France Telecom Orange
>>=20
>> Did you leave someone off, or did someone answer twice ?
>>=20
>> Y(J)S
>>=20
>>=20
>> -----Original Message-----
>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf
Of Delregno, Christopher N (Nick DelRegno)
>> Sent: Tuesday, March 08, 2011 16:27
>> To: pwe3
>> Subject: [PWE3] FW: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00
>>=20
>> Folks:
>>=20
>> The 00 draft of the PW/VCCV Implementation Survey Results have been
uploaded.  I will be presenting the results at IETF80.
>>=20
>>
https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-resu
lts/
>>=20
>> Thanks,
>> Nick
>>=20
>> Christopher N. Del Regno, PMTS
>> C&T, Ethernet Network Architecture & Design
>> 400 International Pkwy
>> Richardson, TX  75081
>> 972-729-3411
>> nick.delregno@verizon.com
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20
>> Sent: Tuesday, March 08, 2011 8:16 AM
>> To: Delregno, Christopher N (Nick DelRegno)
>> Subject: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00
>>=20
>>=20
>> A new version of I-D,
draft-delregno-pw-vccv-impl-survey-results-00.txt has been successfully
submitted by Nick Del Regno and posted to the IETF repository.
>>=20
>> Filename:	 draft-delregno-pw-vccv-impl-survey-results
>> Revision:	 00
>> Title:		 The Pseudowire (PW) & Virtual Circuit
Connectivity Verification (VCCV) Implementation Survey Results
>> Creation_date:	 2011-03-07
>> WG ID:		 Independent Submission
>> Number_of_pages: 16
>>=20
>> Abstract:
>> Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate
>> the use of the Control Word (CW) in order to better emulate the
>> services for which the encapsulations have been defined.  However,
>> some encapulations treat the Control Word as optional.  As a result,
>> implementations of the CW, for encapsulations for which it is
>> optional, vary by equipment manufacturer, equipment model and service
>> provider network.  Similarly, Virtual Circuit Connectivity
>> Verification (VCCV) supports three Control Channel (CC) types and
>> multiple Connectivity Verification (CV) Types.  This flexibility has
>> led to reports of interoperability issues within deployed networks
>> and associated drafts to attempt to remedy the situation.  This
>> survey of the PW/VCCV user community was conducted to determine
>> implementation trends.  The survey and results is presented herein.
>>=20
>>=20
>>=20
>> The IETF Secretariat.
>>=20
>>=20
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>=20


From tnadeau@lucidvision.com  Thu Mar 17 10:02:16 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41DCC3A6AD0 for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 10:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 0LX3lTl2AYcq for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 10:02:15 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by core3.amsl.com (Postfix) with ESMTP id 03D7B3A6AC9 for <pwe3@ietf.org>; Thu, 17 Mar 2011 10:02:15 -0700 (PDT)
Received: from [10.66.110.196] (mobile-166-137-136-251.mycingular.net [166.137.136.251]) by lucidvision.com (Postfix) with ESMTP id BEDD11A7D421; Thu, 17 Mar 2011 13:03:39 -0400 (EDT)
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com> <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il> <4D7F944E.2040903@cisco.com> <538B1799-C583-4192-B170-170F00FEDA7D@lucidvision.com> <14584D6EE26B314187A4F68BA206060006E297A0@ASHEVS008.mcilink.com>
In-Reply-To: <14584D6EE26B314187A4F68BA206060006E297A0@ASHEVS008.mcilink.com>
Mime-Version: 1.0 (iPhone Mail 8F190)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <4CC0A1A4-E6C1-40D6-B05E-508D26C1C0BD@lucidvision.com>
X-Mailer: iPhone Mail (8F190)
From: Thomas Nadeau <tnadeau@lucidvision.com>
Date: Thu, 17 Mar 2011 13:03:28 -0400
To: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
Cc: pwe3 <pwe3@ietf.org>, Yaakov Stein <yaakov_s@rad.com>, Luca Martini <lmartini@cisco.com>
Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 17:02:16 -0000

That's precisely what I'm asking for: for the wg to agree to augment the exi=
sting survey with a short additional one that focuses in the missing bfd mod=
e only.

Tom

On Mar 17, 2011, at 12:03 PM, "Delregno, Christopher N (Nick DelRegno)" <nic=
k.delregno@verizon.com> wrote:

> Tom:
>=20
> Please pose that question to the WG (maybe that's what you were doing).
> When we crafted the survey, omitting BFD was an oversight.  However, the
> list of questions was sent to the WG for comment before the survey was
> conducted.  If the WG would like, I can contact the respondents directly
> to inquire of their BFD usage as well.  However, I don't think the
> survey should be reopened.
>=20
> Thanks,
> Nick
>=20
> -----Original Message-----
> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]=20
> Sent: Tuesday, March 15, 2011 2:18 PM
> To: Luca Martini
> Cc: Delregno, Christopher N (Nick DelRegno); Yaakov Stein; pwe3
> Subject: Re: [PWE3] FW: New Version Notification for
> draft-delregno-pw-vccv-impl-survey-results-00
>=20
>=20
>    One thing I'd ask is that we augment the survey to ask about the
> BFD mode for=20
> VCCV. It seems to have been left out of the survey, potentially skewing
> the results.=20
> As I understand it, this is the most popular mode.
>=20
>    --Tom
>=20
>=20
>=20
>=20
> On Mar 15, 2011, at 12:31 PM, Luca Martini wrote:
>=20
>> Nick,
>> Good survey, thanks for the work.
>>=20
>> Are we going to publish this as informational ?
>> I think we should .
>> Also there is a mention of AToM in section 2.7 item 5 . It should be
>> changed to PWE ( AToM is a cisco marketing term , so we want o keep
> this
>> anonymous )
>> Thanks.
>> Luca
>>=20
>>=20
>>=20
>> On 03/15/2011 09:41 AM, Yaakov Stein wrote:
>>> Nick,=20
>>>=20
>>> In section 2.2 the percentages make sense under the assumption of 18
> respondents :
>>> 5.6%   =3D  1 / 18
>>> 11.1%  =3D  2 / 18
>>> 16.7%  =3D  3 / 18
>>> 22.2%  =3D  4 / 18
>>> 44.4%  =3D  8 / 18
>>> 77.8%  =3D 14 / 18=20
>>>=20
>>> but section 2.1 only lists 17 :
>>> 1.    Time Warner Cable
>>> 2.    Bright House Networks
>>> 3.    Tinet
>>> 4.    AboveNet
>>> 5.    Telecom New Zealand
>>> 6.    Cox Communications
>>> 7.    MTN South Africa
>>> 8.    Wipro Technologies
>>> 9.    Verizon
>>> 10.    AMS-IX
>>> 11.    Superonline
>>> 12.    Deutsche Telekom AG
>>> 13.    Internet Solution
>>> 14.    Easynet Global Services
>>> 15.    Telstra Corporation
>>> 16.    OJSC MegaFon
>>> 17.    France Telecom Orange
>>>=20
>>> Did you leave someone off, or did someone answer twice ?
>>>=20
>>> Y(J)S
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf
> Of Delregno, Christopher N (Nick DelRegno)
>>> Sent: Tuesday, March 08, 2011 16:27
>>> To: pwe3
>>> Subject: [PWE3] FW: New Version Notification for
> draft-delregno-pw-vccv-impl-survey-results-00
>>>=20
>>> Folks:
>>>=20
>>> The 00 draft of the PW/VCCV Implementation Survey Results have been
> uploaded.  I will be presenting the results at IETF80.
>>>=20
>>>=20
> https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-resu
> lts/
>>>=20
>>> Thanks,
>>> Nick
>>>=20
>>> Christopher N. Del Regno, PMTS
>>> C&T, Ethernet Network Architecture & Design
>>> 400 International Pkwy
>>> Richardson, TX  75081
>>> 972-729-3411
>>> nick.delregno@verizon.com
>>>=20
>>>=20
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20
>>> Sent: Tuesday, March 08, 2011 8:16 AM
>>> To: Delregno, Christopher N (Nick DelRegno)
>>> Subject: New Version Notification for
> draft-delregno-pw-vccv-impl-survey-results-00
>>>=20
>>>=20
>>> A new version of I-D,
> draft-delregno-pw-vccv-impl-survey-results-00.txt has been successfully
> submitted by Nick Del Regno and posted to the IETF repository.
>>>=20
>>> Filename:     draft-delregno-pw-vccv-impl-survey-results
>>> Revision:     00
>>> Title:         The Pseudowire (PW) & Virtual Circuit
> Connectivity Verification (VCCV) Implementation Survey Results
>>> Creation_date:     2011-03-07
>>> WG ID:         Independent Submission
>>> Number_of_pages: 16
>>>=20
>>> Abstract:
>>> Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate
>>> the use of the Control Word (CW) in order to better emulate the
>>> services for which the encapsulations have been defined.  However,
>>> some encapulations treat the Control Word as optional.  As a result,
>>> implementations of the CW, for encapsulations for which it is
>>> optional, vary by equipment manufacturer, equipment model and service
>>> provider network.  Similarly, Virtual Circuit Connectivity
>>> Verification (VCCV) supports three Control Channel (CC) types and
>>> multiple Connectivity Verification (CV) Types.  This flexibility has
>>> led to reports of interoperability issues within deployed networks
>>> and associated drafts to attempt to remedy the situation.  This
>>> survey of the PW/VCCV user community was conducted to determine
>>> implementation trends.  The survey and results is presented herein.
>>>=20
>>>=20
>>>=20
>>> The IETF Secretariat.
>>>=20
>>>=20
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>=20
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>=20
>=20
>=20

From nick.delregno@verizon.com  Thu Mar 17 13:33:15 2011
Return-Path: <nick.delregno@verizon.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B339A3A6B0B for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 13:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.304
X-Spam-Level: 
X-Spam-Status: No, score=-3.304 tagged_above=-999 required=5 tests=[AWL=0.295,  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 Rs78pFM87JeH for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 13:33:14 -0700 (PDT)
Received: from ashesmtp03.verizonbusiness.com (ashesmtp03.verizonbusiness.com [198.4.8.167]) by core3.amsl.com (Postfix) with ESMTP id 570633A6B06 for <pwe3@ietf.org>; Thu, 17 Mar 2011 13:33:14 -0700 (PDT)
Received: from omzismtp02.vzbi.com ([unknown] [165.122.46.167]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI700ME8YDVC5A0@firewall.verizonbusiness.com> for pwe3@ietf.org; Thu, 17 Mar 2011 20:32:21 +0000 (GMT)
Received: from omzismtp02.vzbi.com ([unknown] [127.0.0.1]) by omzismtp02.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI700HCZYDXRI00@omzismtp02.vzbi.com> for pwe3@ietf.org; Thu, 17 Mar 2011 20:32:21 +0000 (GMT)
Received: from ASHSRV141.mcilink.com ([unknown] [153.39.68.167]) by omzismtp02.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LI700I4RYDX3C00@omzismtp02.vzbi.com> for pwe3@ietf.org; Thu, 17 Mar 2011 20:32:21 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV141.mcilink.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 17 Mar 2011 20:32:20 +0000
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, 17 Mar 2011 20:32:15 +0000
Message-id: <14584D6EE26B314187A4F68BA206060006E29AA0@ASHEVS008.mcilink.com>
In-reply-to: <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
Thread-index: Acvdm33bS8HQGFieTSSSyunk7NkzBAAABRxQAWJa3CAAb1DukA==
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com> <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il>
From: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
To: Yaakov Stein <yaakov_s@rad.com>
X-OriginalArrivalTime: 17 Mar 2011 20:32:20.0768 (UTC) FILETIME=[6A51D200:01CBE4E2]
Cc: pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 20:33:15 -0000

Yaakov:

Yep, looks like that section was based on the 18 responses as you
deduced.  Nice catch.

I will update based on the 17 results and also scrub the rest of the
results as well.

I will post an updated version when complete.

Thanks,
Nick

-----Original Message-----
From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
Sent: Tuesday, March 15, 2011 10:42 AM
To: Delregno, Christopher N (Nick DelRegno)
Cc: pwe3
Subject: RE: [PWE3] FW: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00

Nick,=20

In section 2.2 the percentages make sense under the assumption of 18
respondents :
5.6%   =3D  1 / 18
11.1%  =3D  2 / 18
16.7%  =3D  3 / 18
22.2%  =3D  4 / 18
44.4%  =3D  8 / 18
77.8%  =3D 14 / 18=20

but section 2.1 only lists 17 :
1.	Time Warner Cable
2.	Bright House Networks
3.	Tinet
4.	AboveNet
5.	Telecom New Zealand
6.	Cox Communications
7.	MTN South Africa
8.	Wipro Technologies
9.	Verizon
10.	AMS-IX
11.	Superonline
12.	Deutsche Telekom AG
13.	Internet Solution
14.	Easynet Global Services
15.	Telstra Corporation
16.	OJSC MegaFon
17.	France Telecom Orange

Did you leave someone off, or did someone answer twice ?

Y(J)S


-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Delregno, Christopher N (Nick DelRegno)
Sent: Tuesday, March 08, 2011 16:27
To: pwe3
Subject: [PWE3] FW: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00

Folks:

The 00 draft of the PW/VCCV Implementation Survey Results have been
uploaded.  I will be presenting the results at IETF80.

https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-resu
lts/

Thanks,
Nick

Christopher N. Del Regno, PMTS
C&T, Ethernet Network Architecture & Design
400 International Pkwy
Richardson, TX  75081
972-729-3411
nick.delregno@verizon.com




-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20
Sent: Tuesday, March 08, 2011 8:16 AM
To: Delregno, Christopher N (Nick DelRegno)
Subject: New Version Notification for
draft-delregno-pw-vccv-impl-survey-results-00


A new version of I-D, draft-delregno-pw-vccv-impl-survey-results-00.txt
has been successfully submitted by Nick Del Regno and posted to the IETF
repository.

Filename:	 draft-delregno-pw-vccv-impl-survey-results
Revision:	 00
Title:		 The Pseudowire (PW) & Virtual Circuit Connectivity
Verification (VCCV) Implementation Survey Results
Creation_date:	 2011-03-07
WG ID:		 Independent Submission
Number_of_pages: 16

Abstract:
Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate
the use of the Control Word (CW) in order to better emulate the
services for which the encapsulations have been defined.  However,
some encapulations treat the Control Word as optional.  As a result,
implementations of the CW, for encapsulations for which it is
optional, vary by equipment manufacturer, equipment model and service
provider network.  Similarly, Virtual Circuit Connectivity
Verification (VCCV) supports three Control Channel (CC) types and
multiple Connectivity Verification (CV) Types.  This flexibility has
led to reports of interoperability issues within deployed networks
and associated drafts to attempt to remedy the situation.  This
survey of the PW/VCCV user community was conducted to determine
implementation trends.  The survey and results is presented herein.
=20



The IETF Secretariat.


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

From david.sinicrope@ericsson.com  Thu Mar 17 16:24:45 2011
Return-Path: <david.sinicrope@ericsson.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A75123A6B44 for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 16:24:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6kuaH4e6NKF for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 16:24:45 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id D908B3A6B37 for <pwe3@ietf.org>; Thu, 17 Mar 2011 16:24:44 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2HNQBdY012537 for <pwe3@ietf.org>; Thu, 17 Mar 2011 18:26:13 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.208]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Thu, 17 Mar 2011 19:26:12 -0400
From: David Sinicrope <david.sinicrope@ericsson.com>
To: "IETF.PWE3" <pwe3@ietf.org>
Date: Thu, 17 Mar 2011 19:26:07 -0400
Thread-Topic: Draft PWE3 Agenda for IETF 80 - Prague
Thread-Index: Acvk+rPh3ZU1qFm6QPO7Nug2AAmN5A==
Message-ID: <C9A810CF.41687%david.sinicrope@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [PWE3] Draft PWE3 Agenda for IETF 80 - Prague
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 23:24:45 -0000

I posted the draft agenda for the PWE3 session of IETF 80 in Prague.
Please check and ensure I reflected your slot request.  Order of presentati=
ons is subject to change.
Those who have slots, please start sending me your presentations for upload=
.
Thanks!
Dave



From amalis@gmail.com  Thu Mar 17 16:40:08 2011
Return-Path: <amalis@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 784403A6B43 for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 16:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XfDFuykHqAQ9 for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 16:40:06 -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 2508F3A6A77 for <pwe3@ietf.org>; Thu, 17 Mar 2011 16:40:05 -0700 (PDT)
Received: by ewy19 with SMTP id 19so994633ewy.31 for <pwe3@ietf.org>; Thu, 17 Mar 2011 16:41:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=iawCYsiGXNJG/YDle88ODWW3v0g3m9DLjAOBH5CsnxY=; b=pAgFJd2mWb4xuEdM34MIXFB2W/dB2hRnyK33Bg+i+tbhlBgnWUUgwAhTpzKB5sSxeK oapZmLRRRHG1hLDNzW5wRwC4abvhsVV92boAArCR6YgNkCu7dAs7Nzbd+sxQxv82b21f sd7VfWhqpGH+Xx0qBfjUtWKIxe2i8IOfS69v4=
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=CG2YOyFaTfKQVZ2XbEKNmtZGmeytNTsmM1spYfZLRT6VU55yfvK0NUky/fzw0Qy311 Lv5sk2yBRh0hz1IcgyctdWqu77babHG9STLFHs7t0/FxSb6mpijTCwdsPF+5BvRKHIAL QYpKzUdKxWTWGTaq1PlmMh4op1qpji5W6gVek=
Received: by 10.213.15.141 with SMTP id k13mr457108eba.144.1300405292240; Thu, 17 Mar 2011 16:41:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.49.147 with HTTP; Thu, 17 Mar 2011 16:41:12 -0700 (PDT)
In-Reply-To: <C9A810CF.41687%david.sinicrope@ericsson.com>
References: <C9A810CF.41687%david.sinicrope@ericsson.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Date: Thu, 17 Mar 2011 19:41:12 -0400
Message-ID: <AANLkTimTqspTfxteZg0-ZHGYzuo8n3xDdJFdX=PVKHeK@mail.gmail.com>
To: David Sinicrope <david.sinicrope@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "IETF.PWE3" <pwe3@ietf.org>
Subject: Re: [PWE3] Draft PWE3 Agenda for IETF 80 - Prague
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 23:40:08 -0000

Dave, thanks!

To reiterate Dave's request for presentations, we will be using Webex
and audio streaming for remote participation, so having your talk
submitted in advance is required so that we can have all of the
presentations loaded on a single laptop, plus online for remote
download.

Since we're meeting the first thing Monday morning, you MUST have your
presentation submitted to Dave by 5 PM Thursday PDT (8 PM Thursday
EDT, 2 AM Friday Prague time) , or be in danger of having your slot
pulled. This will give Dave time to get the talks online in time for
Monday morning.

if you don't expect to use slides, let Dave know that as well.

Also, don't forget that Europe moves to Summer Time on the Sunday
morning immediately preceding the IETF meeting, or you'll end up an
hour late for the PWE3 meeting on Monday morning!

Thanks,
Andy and Matthew

On Thu, Mar 17, 2011 at 7:26 PM, David Sinicrope
<david.sinicrope@ericsson.com> wrote:
> I posted the draft agenda for the PWE3 session of IETF 80 in Prague.
> Please check and ensure I reflected your slot request. =A0Order of presen=
tations is subject to change.
> Those who have slots, please start sending me your presentations for uplo=
ad.
> Thanks!
> Dave
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

From gregimirsky@gmail.com  Thu Mar 17 21:32:31 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E7B583A6A17; Thu, 17 Mar 2011 21:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.741
X-Spam-Level: 
X-Spam-Status: No, score=-2.741 tagged_above=-999 required=5 tests=[AWL=-0.143, 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 GDR35FozUpjx; Thu, 17 Mar 2011 21:32:30 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 136E93A69D3; Thu, 17 Mar 2011 21:32:29 -0700 (PDT)
Received: by vxg33 with SMTP id 33so3807059vxg.31 for <multiple recipients>; Thu, 17 Mar 2011 21:33:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=dZR1m8JO3m+/i1NIMPhOEgQqZ2QbbL/gChQTNDEEOOo=; b=htU3LVk32CjgxUw+Uk8gqWYlrIz96PhX0NC0dnU9Z5KAxfmBiU65VIWhanjNzWlEpZ Zt0A8lGkwxTzli+MSYQcSpP0bCkDRuLEZLUFbwxSYhkYonKX/1KsAWA0ftwfuehOYy2V 02kUcCgEeT9s2Bc/Lrg/J+p7Y+x/q2AGT9Xkc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=kDI2ZiBlD11va9fsX7M1jRcOVla9Opkei91Y55SjqpxmrfEDrhnoj+IQZ2+1Pvmwwc fkpe74Mb6znvmdwi18FbXMeYhZHRDu1BP6M7IQuk5otaQ/wN+qE17EYTxJNdQaKiSYsw N4XpmpIo7oiq6hUql0gF1Fg8aRll3fOOOIcuk=
MIME-Version: 1.0
Received: by 10.52.159.3 with SMTP id wy3mr835884vdb.289.1300422838577; Thu, 17 Mar 2011 21:33:58 -0700 (PDT)
Received: by 10.52.169.35 with HTTP; Thu, 17 Mar 2011 21:33:58 -0700 (PDT)
Date: Thu, 17 Mar 2011 21:33:58 -0700
Message-ID: <AANLkTimXnrVSWzwMxinaXukhpidhhFGLPGrG0FjXA718@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: zhang.fei3@zte.com.cn, wu.bo@zte.com.cn,  Elisa Bellagamba <elisa.bellagamba@ericsson.com>, Attila Takacs <Attila.Takacs@ericsson.com>,  dai.xuehui@zte.com.cn, xiao.min2@zte.com.cn, mpls@ietf.org,  pwe3 <pwe3@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec53f979759f0a2049eba49b8
Subject: [PWE3] Comments on draft-zhang-mpls-tp-pw-oam-config-04
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2011 04:32:32 -0000

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

Dear Authors, Editors, and All,
Please kindly find my comments to the document below

   - Editorial. In Introduction, para 2 's/In contract/In contrast/'
   - section 4.1 positions proactive CC-CV-RDI as extension of BFD and
   states that BFD should evolve to close gaps existing between if and OAM
   solutions defined in ietf-mpls-tp-cc-cv-rdi. I don't consider solution
   described for proactive CC/CV/RDI as extension of VCCV BFD, RFC 5885 and I
   think that mechanisms defined for proactive CC/CV/RDI can be applied for
   SS-PW and MS-PW as well as they are applicable to p2p bi-directional LSPs,
   co-routed and associated. If that's the case, then VCCV BFD can be used as
   defined in RFC 5885, without modifications and the ietf-mpls-tp-cc-cv-rdi
   will address proactive CV gap for PW.
   - Section 7.1 I'd propose to define 'C' bit to indicate support of
   CC/CV/RDI in addition to bits L, D, and F because support of VCCV BFD not
   necessarily equates to support of ietf-mpls-tp-cc-cv-rdi.

Regards,
Greg

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

Dear Authors, Editors, and All,<br>Please kindly find my comments to the do=
cument below<br><ul><li>Editorial. In Introduction, para 2 &#39;s/In contra=
ct/In contrast/&#39;</li><li>section 4.1 positions proactive CC-CV-RDI as e=
xtension of BFD and states that BFD should evolve to close gaps existing be=
tween if and OAM solutions defined in ietf-mpls-tp-cc-cv-rdi. I don&#39;t c=
onsider solution described for proactive CC/CV/RDI as extension of VCCV BFD=
, RFC 5885 and I think that mechanisms defined for proactive CC/CV/RDI can =
be applied for SS-PW and MS-PW as well as they are applicable to p2p bi-dir=
ectional LSPs, co-routed and associated. If that&#39;s the case, then VCCV =
BFD can be used as defined in RFC 5885, without modifications and the ietf-=
mpls-tp-cc-cv-rdi will address proactive CV gap for PW.</li>

<li>Section 7.1 I&#39;d propose to define &#39;C&#39; bit to indicate suppo=
rt of CC/CV/RDI in addition to bits L, D, and F because support of VCCV BFD=
 not necessarily equates to support of ietf-mpls-tp-cc-cv-rdi.</li></ul>

Regards,<br>Greg<br>

--bcaec53f979759f0a2049eba49b8--

From zhang.fei3@zte.com.cn  Fri Mar 18 00:55:43 2011
Return-Path: <zhang.fei3@zte.com.cn>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F9133A680A; Fri, 18 Mar 2011 00:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.163
X-Spam-Level: 
X-Spam-Status: No, score=-98.163 tagged_above=-999 required=5 tests=[AWL=-0.529, 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 YcT8zjV2UGeE; Fri, 18 Mar 2011 00:55:42 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 091BC3A67F7; Fri, 18 Mar 2011 00:55:41 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 50832203882679; Fri, 18 Mar 2011 15:56:19 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 96281.6544722859; Fri, 18 Mar 2011 15:47:08 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id p2I7usCI018693; Fri, 18 Mar 2011 15:56:54 +0800 (GMT-8) (envelope-from zhang.fei3@zte.com.cn)
In-Reply-To: <AANLkTimXnrVSWzwMxinaXukhpidhhFGLPGrG0FjXA718@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
MIME-Version: 1.0
X-KeepSent: 88A79A88:1B81C977-48257857:0029F3BE; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF88A79A88.1B81C977-ON48257857.0029F3BE-48257857.002BA946@zte.com.cn>
From: zhang.fei3@zte.com.cn
Date: Fri, 18 Mar 2011 15:56:56 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-03-18 15:56:55, Serialize complete at 2011-03-18 15:56:55
Content-Type: multipart/alternative; boundary="=_alternative 002BA94248257857_="
X-MAIL: mse01.zte.com.cn p2I7usCI018693
Cc: mpls@ietf.org, wu.bo@zte.com.cn, Attila Takacs <Attila.Takacs@ericsson.com>, pwe3 <pwe3@ietf.org>, Elisa Bellagamba <elisa.bellagamba@ericsson.com>
Subject: Re: [PWE3] Comments on draft-zhang-mpls-tp-pw-oam-config-04
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2011 07:55:43 -0000

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

SGkgR3JlZw0KDQpUaGFua3MgZm9yIHlvdXIgY29tbWVudHMsIHBsZWFzZSBzZWUgdGhlIHJlc3Bv
bnNlIGZvciB0aGVtLg0KDQogQ29tbWVudHMgMTogVGhpcyB3aWxsIGJlIHJldmlzZWQgaW4gdGhl
IG5leHQgdmVyc2lvbg0KIENvbW1lbnRzIDI6IEp1c3QgYXMgeW91IHNhaWQsIHRoZSBmdW5jdGlv
biBvZiBDQyBtb2RlIGRlZmluZSBpbiANCltDQy1DVi1SREldIGlzIHRvdGFsbHkgdGhlIHNhbWUg
YXMgVkNDViBCRkQsIHNvIHRoZXJlIGFyZSB0d28gY2hvaWNlcyBmb3IgDQpNUExTLVRQIFBXLg0K
ICAgICAgICAgICAgICgxKVZDQ1YgQkZEIGlzIHVzZWQgZm9yIHRoZSBDQyBtb2RlLCBhbmQgQ0Mt
Q1YtUkRJIHVzZWQgZm9yIA0KdGhlIENWIG1vZGUNCiAgICAgICAgICAgICAoMilDQy1DVi1SREkg
aXMgdXNlZCBmb3IgYm90aCB0aGUgQ0MgYW5kIENWIG1vZGVzLCBhbmQgVkNDViANCkJGRCBpcyBu
b3QgdXNlZC4NCiAgICAgICAgICAgICBGb3IgYmFrd2FyZCBjb21wYXRpYmlsaXR5LCBjaG9pY2Ug
MSBpcyB0aGUgYmV0dGVyIGNob2ljZTsgYW5kIA0KdGhpcyB3aWxsIGJlIHJldmlzZWQgaW4gdGhl
IG5leHQgdmVyc2lvbiANCkNvbW1lbnRzIDM6IEFncmVlLCBpZiBWQ0NWIEJGRCBpcyBub3QgdXNl
ZCwgYm90aCBDQyBhbmQgQ1YgYml0cyBTSE9VTEQgYmUgDQpkZWZpbmVkOyBpZiBWQ0NWIEJGRCBp
cyB1c2VkIGZvciB0aGUgQ0MgbW9kZSwgb25seSBDViBiaXQgU0hPVUxEIGJlIA0KZGVmaW5lZC4N
Cg0KDQpCLlIuDQoNCkZlaQ0KDQoNCg0KR3JlZyBNaXJza3kgPGdyZWdpbWlyc2t5QGdtYWlsLmNv
bT4gDQoyMDExLTAzLTE4IDEyOjMzDQoNCsrVvP7Iyw0KemhhbmcuZmVpM0B6dGUuY29tLmNuLCB3
dS5ib0B6dGUuY29tLmNuLCBFbGlzYSBCZWxsYWdhbWJhIA0KPGVsaXNhLmJlbGxhZ2FtYmFAZXJp
Y3Nzb24uY29tPiwgQXR0aWxhIFRha2FjcyANCjxBdHRpbGEuVGFrYWNzQGVyaWNzc29uLmNvbT4s
IGRhaS54dWVodWlAenRlLmNvbS5jbiwgeGlhby5taW4yQHp0ZS5jb20uY24sIA0KbXBsc0BpZXRm
Lm9yZywgcHdlMyA8cHdlM0BpZXRmLm9yZz4NCrOty80NCg0K1vfM4g0KQ29tbWVudHMgb24gZHJh
ZnQtemhhbmctbXBscy10cC1wdy1vYW0tY29uZmlnLTA0DQoNCg0KDQoNCg0KDQpEZWFyIEF1dGhv
cnMsIEVkaXRvcnMsIGFuZCBBbGwsDQpQbGVhc2Uga2luZGx5IGZpbmQgbXkgY29tbWVudHMgdG8g
dGhlIGRvY3VtZW50IGJlbG93DQpFZGl0b3JpYWwuIEluIEludHJvZHVjdGlvbiwgcGFyYSAyICdz
L0luIGNvbnRyYWN0L0luIGNvbnRyYXN0LycNCnNlY3Rpb24gNC4xIHBvc2l0aW9ucyBwcm9hY3Rp
dmUgQ0MtQ1YtUkRJIGFzIGV4dGVuc2lvbiBvZiBCRkQgYW5kIHN0YXRlcyANCnRoYXQgQkZEIHNo
b3VsZCBldm9sdmUgdG8gY2xvc2UgZ2FwcyBleGlzdGluZyBiZXR3ZWVuIGlmIGFuZCBPQU0gc29s
dXRpb25zIA0KZGVmaW5lZCBpbiBpZXRmLW1wbHMtdHAtY2MtY3YtcmRpLiBJIGRvbid0IGNvbnNp
ZGVyIHNvbHV0aW9uIGRlc2NyaWJlZCBmb3IgDQpwcm9hY3RpdmUgQ0MvQ1YvUkRJIGFzIGV4dGVu
c2lvbiBvZiBWQ0NWIEJGRCwgUkZDIDU4ODUgYW5kIEkgdGhpbmsgdGhhdCANCm1lY2hhbmlzbXMg
ZGVmaW5lZCBmb3IgcHJvYWN0aXZlIENDL0NWL1JESSBjYW4gYmUgYXBwbGllZCBmb3IgU1MtUFcg
YW5kIA0KTVMtUFcgYXMgd2VsbCBhcyB0aGV5IGFyZSBhcHBsaWNhYmxlIHRvIHAycCBiaS1kaXJl
Y3Rpb25hbCBMU1BzLCBjby1yb3V0ZWQgDQphbmQgYXNzb2NpYXRlZC4gSWYgdGhhdCdzIHRoZSBj
YXNlLCB0aGVuIFZDQ1YgQkZEIGNhbiBiZSB1c2VkIGFzIGRlZmluZWQgDQppbiBSRkMgNTg4NSwg
d2l0aG91dCBtb2RpZmljYXRpb25zIGFuZCB0aGUgaWV0Zi1tcGxzLXRwLWNjLWN2LXJkaSB3aWxs
IA0KYWRkcmVzcyBwcm9hY3RpdmUgQ1YgZ2FwIGZvciBQVy4NClNlY3Rpb24gNy4xIEknZCBwcm9w
b3NlIHRvIGRlZmluZSAnQycgYml0IHRvIGluZGljYXRlIHN1cHBvcnQgb2YgQ0MvQ1YvUkRJIA0K
aW4gYWRkaXRpb24gdG8gYml0cyBMLCBELCBhbmQgRiBiZWNhdXNlIHN1cHBvcnQgb2YgVkNDViBC
RkQgbm90IA0KbmVjZXNzYXJpbHkgZXF1YXRlcyB0byBzdXBwb3J0IG9mIGlldGYtbXBscy10cC1j
Yy1jdi1yZGkuDQpSZWdhcmRzLA0KR3JlZw0KDQo=
--=_alternative 002BA94248257857_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIEdyZWc8L2ZvbnQ+DQo8YnI+
DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlRoYW5rcyBmb3IgeW91ciBjb21t
ZW50cywgcGxlYXNlIHNlZQ0KdGhlIHJlc3BvbnNlIGZvciB0aGVtLjwvZm9udD4NCjxicj4NCjxi
cj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7Q29tbWVudHMgMTogVGhpcyB3
aWxsIGJlIHJldmlzZWQNCmluIHRoZSBuZXh0IHZlcnNpb248L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6
ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwO0NvbW1lbnRzIDI6IEp1c3QgYXMgeW91IHNhaWQs
DQp0aGUgZnVuY3Rpb24gb2YgQ0MgbW9kZSBkZWZpbmUgaW4gW0NDLUNWLVJESV0gaXMgdG90YWxs
eSB0aGUgc2FtZSBhcyBWQ0NWDQpCRkQsIHNvIHRoZXJlIGFyZSB0d28gY2hvaWNlcyBmb3IgTVBM
Uy1UUCBQVy48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7DQombmJzcDsoMSlWQ0NWIEJGRCBp
cyB1c2VkIGZvciB0aGUgQ0MgbW9kZSwgYW5kIENDLUNWLVJESSB1c2VkIGZvciB0aGUgQ1YNCm1v
ZGU8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7DQombmJzcDsoMilDQy1DVi1SREkgaXMgdXNl
ZCBmb3IgYm90aCB0aGUgQ0MgYW5kIENWIG1vZGVzLCBhbmQgVkNDViBCRkQgaXMNCm5vdCB1c2Vk
LjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsNCiZuYnNwO0ZvciBiYWt3YXJkIGNvbXBhdGli
aWxpdHksIGNob2ljZSAxIGlzIHRoZSBiZXR0ZXIgY2hvaWNlOyBhbmQgdGhpcw0Kd2lsbCBiZSBy
ZXZpc2VkIGluIHRoZSBuZXh0IHZlcnNpb24gPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNl
PSJzYW5zLXNlcmlmIj5Db21tZW50cyAzOiBBZ3JlZSwgaWYgVkNDViBCRkQgaXMgbm90DQp1c2Vk
LCBib3RoIENDIGFuZCBDViBiaXRzIFNIT1VMRCBiZSBkZWZpbmVkOyBpZiBWQ0NWIEJGRCBpcyB1
c2VkIGZvciB0aGUNCkNDIG1vZGUsIG9ubHkgQ1YgYml0IFNIT1VMRCBiZSBkZWZpbmVkLjwvZm9u
dD4NCjxicj4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Qi5SLjwv
Zm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+RmVpPC9mb250
Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4N
Cjx0ZCB3aWR0aD0zNSU+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjxiPkdyZWcgTWly
c2t5ICZsdDtncmVnaW1pcnNreUBnbWFpbC5jb20mZ3Q7PC9iPg0KPC9mb250Pg0KPHA+PGZvbnQg
c2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjIwMTEtMDMtMTggMTI6MzM8L2ZvbnQ+DQo8dGQgd2lk
dGg9NjQlPg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYg
YWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPsrVvP7IyzwvZm9udD48
L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+emhhbmcuZmVpM0B6dGUu
Y29tLmNuLCB3dS5ib0B6dGUuY29tLmNuLA0KRWxpc2EgQmVsbGFnYW1iYSAmbHQ7ZWxpc2EuYmVs
bGFnYW1iYUBlcmljc3Nvbi5jb20mZ3Q7LCBBdHRpbGEgVGFrYWNzICZsdDtBdHRpbGEuVGFrYWNz
QGVyaWNzc29uLmNvbSZndDssDQpkYWkueHVlaHVpQHp0ZS5jb20uY24sIHhpYW8ubWluMkB6dGUu
Y29tLmNuLCBtcGxzQGlldGYub3JnLCBwd2UzICZsdDtwd2UzQGlldGYub3JnJmd0OzwvZm9udD4N
Cjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFj
ZT0ic2Fucy1zZXJpZiI+s63LzTwvZm9udD48L2Rpdj4NCjx0ZD4NCjx0ciB2YWxpZ249dG9wPg0K
PHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+1vfM
4jwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+Q29tbWVu
dHMgb24gZHJhZnQtemhhbmctbXBscy10cC1wdy1vYW0tY29uZmlnLTA0PC9mb250PjwvdGFibGU+
DQo8YnI+DQo8dGFibGU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjx0ZD48L3RhYmxlPg0KPGJy
PjwvdGFibGU+DQo8YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0zPkRlYXIgQXV0aG9ycywgRWRp
dG9ycywgYW5kIEFsbCw8YnI+DQpQbGVhc2Uga2luZGx5IGZpbmQgbXkgY29tbWVudHMgdG8gdGhl
IGRvY3VtZW50IGJlbG93PC9mb250Pg0KPHVsPg0KPGxpPjxmb250IHNpemU9Mz5FZGl0b3JpYWwu
IEluIEludHJvZHVjdGlvbiwgcGFyYSAyICdzL0luIGNvbnRyYWN0L0luIGNvbnRyYXN0Lyc8L2Zv
bnQ+DQo8bGk+PGZvbnQgc2l6ZT0zPnNlY3Rpb24gNC4xIHBvc2l0aW9ucyBwcm9hY3RpdmUgQ0Mt
Q1YtUkRJIGFzIGV4dGVuc2lvbg0Kb2YgQkZEIGFuZCBzdGF0ZXMgdGhhdCBCRkQgc2hvdWxkIGV2
b2x2ZSB0byBjbG9zZSBnYXBzIGV4aXN0aW5nIGJldHdlZW4NCmlmIGFuZCBPQU0gc29sdXRpb25z
IGRlZmluZWQgaW4gaWV0Zi1tcGxzLXRwLWNjLWN2LXJkaS4gSSBkb24ndCBjb25zaWRlcg0Kc29s
dXRpb24gZGVzY3JpYmVkIGZvciBwcm9hY3RpdmUgQ0MvQ1YvUkRJIGFzIGV4dGVuc2lvbiBvZiBW
Q0NWIEJGRCwgUkZDDQo1ODg1IGFuZCBJIHRoaW5rIHRoYXQgbWVjaGFuaXNtcyBkZWZpbmVkIGZv
ciBwcm9hY3RpdmUgQ0MvQ1YvUkRJIGNhbiBiZQ0KYXBwbGllZCBmb3IgU1MtUFcgYW5kIE1TLVBX
IGFzIHdlbGwgYXMgdGhleSBhcmUgYXBwbGljYWJsZSB0byBwMnAgYmktZGlyZWN0aW9uYWwNCkxT
UHMsIGNvLXJvdXRlZCBhbmQgYXNzb2NpYXRlZC4gSWYgdGhhdCdzIHRoZSBjYXNlLCB0aGVuIFZD
Q1YgQkZEIGNhbiBiZQ0KdXNlZCBhcyBkZWZpbmVkIGluIFJGQyA1ODg1LCB3aXRob3V0IG1vZGlm
aWNhdGlvbnMgYW5kIHRoZSBpZXRmLW1wbHMtdHAtY2MtY3YtcmRpDQp3aWxsIGFkZHJlc3MgcHJv
YWN0aXZlIENWIGdhcCBmb3IgUFcuPC9mb250Pg0KPGxpPjxmb250IHNpemU9Mz5TZWN0aW9uIDcu
MSBJJ2QgcHJvcG9zZSB0byBkZWZpbmUgJ0MnIGJpdCB0byBpbmRpY2F0ZQ0Kc3VwcG9ydCBvZiBD
Qy9DVi9SREkgaW4gYWRkaXRpb24gdG8gYml0cyBMLCBELCBhbmQgRiBiZWNhdXNlIHN1cHBvcnQg
b2YNClZDQ1YgQkZEIG5vdCBuZWNlc3NhcmlseSBlcXVhdGVzIHRvIHN1cHBvcnQgb2YgaWV0Zi1t
cGxzLXRwLWNjLWN2LXJkaS48L2ZvbnQ+PC91bD48Zm9udCBzaXplPTM+UmVnYXJkcyw8YnI+DQpH
cmVnPC9mb250Pg0KPGJyPg0K
--=_alternative 002BA94248257857_=--


From amalis@gmail.com  Fri Mar 18 09:55:49 2011
Return-Path: <amalis@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 39B6C3A696F for <pwe3@core3.amsl.com>; Fri, 18 Mar 2011 09:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41RKS2mdKBU3 for <pwe3@core3.amsl.com>; Fri, 18 Mar 2011 09:55:48 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id AF74F3A6955 for <pwe3@ietf.org>; Fri, 18 Mar 2011 09:55:47 -0700 (PDT)
Received: by eye13 with SMTP id 13so1166380eye.31 for <pwe3@ietf.org>; Fri, 18 Mar 2011 09:57:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=EThJFcLR56ihF7DPKrvJ9IKLLu4xojrIDx4+qRKFVjw=; b=ZKnfWJZOz9eaIrK0IiauJ3Y+QVydx2RSmJT2mtTfypp1lkuw4OfOj4BCx3+M+so4qS oskoKjevC9ls6vD0fB5XHh8ZZuQ3lWkAoHPqSCoekZBYHS2l0IE8st03dCJFxgMgrQ93 TezF9ZXVSixxp9Rjzuzz6aqVWDTkpLMmNnXl0=
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=Sc7hYkYjhaZuZM3u0n8D/ndzarlIu+t+447ZqJB/3U5LAFpecH1qSbv0NyKEsFLeVU 4XwG+JRKaQHzyvg+Sw6o6/6EsRyTppjSL5WY6YZLauJLn9PI85dFGf9mSn8r1y3Ng/SA cTrQc8MT1YHieIf9NXX3wsJdH8gsXCfFRxo8g=
Received: by 10.14.8.210 with SMTP id 58mr66203eer.112.1300467436281; Fri, 18 Mar 2011 09:57:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.49.147 with HTTP; Fri, 18 Mar 2011 09:56:56 -0700 (PDT)
In-Reply-To: <4CC0A1A4-E6C1-40D6-B05E-508D26C1C0BD@lucidvision.com>
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com> <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il> <4D7F944E.2040903@cisco.com> <538B1799-C583-4192-B170-170F00FEDA7D@lucidvision.com> <14584D6EE26B314187A4F68BA206060006E297A0@ASHEVS008.mcilink.com> <4CC0A1A4-E6C1-40D6-B05E-508D26C1C0BD@lucidvision.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Date: Fri, 18 Mar 2011 12:56:56 -0400
Message-ID: <AANLkTinCpnvfszZ0VfFDt7EUh_ezZ0+A-zKhyPZZjXe_@mail.gmail.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Luca Martini <lmartini@cisco.com>, Yaakov Stein <yaakov_s@rad.com>, pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2011 16:55:49 -0000

Are there any objections in the WG to Tom's suggestion?

Thanks,
Andy

On Thu, Mar 17, 2011 at 1:03 PM, Thomas Nadeau <tnadeau@lucidvision.com> wr=
ote:
> That's precisely what I'm asking for: for the wg to agree to augment the =
existing survey with a short additional one that focuses in the missing bfd=
 mode only.
>
> Tom
>
> On Mar 17, 2011, at 12:03 PM, "Delregno, Christopher N (Nick DelRegno)" <=
nick.delregno@verizon.com> wrote:
>
>> Tom:
>>
>> Please pose that question to the WG (maybe that's what you were doing).
>> When we crafted the survey, omitting BFD was an oversight. =A0However, t=
he
>> list of questions was sent to the WG for comment before the survey was
>> conducted. =A0If the WG would like, I can contact the respondents direct=
ly
>> to inquire of their BFD usage as well. =A0However, I don't think the
>> survey should be reopened.
>>
>> Thanks,
>> Nick
>>
>> -----Original Message-----
>> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
>> Sent: Tuesday, March 15, 2011 2:18 PM
>> To: Luca Martini
>> Cc: Delregno, Christopher N (Nick DelRegno); Yaakov Stein; pwe3
>> Subject: Re: [PWE3] FW: New Version Notification for
>> draft-delregno-pw-vccv-impl-survey-results-00
>>
>>
>> =A0 =A0One thing I'd ask is that we augment the survey to ask about the
>> BFD mode for
>> VCCV. It seems to have been left out of the survey, potentially skewing
>> the results.
>> As I understand it, this is the most popular mode.
>>
>> =A0 =A0--Tom
>>
>>
>>
>>
>> On Mar 15, 2011, at 12:31 PM, Luca Martini wrote:
>>
>>> Nick,
>>> Good survey, thanks for the work.
>>>
>>> Are we going to publish this as informational ?
>>> I think we should .
>>> Also there is a mention of AToM in section 2.7 item 5 . It should be
>>> changed to PWE ( AToM is a cisco marketing term , so we want o keep
>> this
>>> anonymous )
>>> Thanks.
>>> Luca
>>>
>>>
>>>
>>> On 03/15/2011 09:41 AM, Yaakov Stein wrote:
>>>> Nick,
>>>>
>>>> In section 2.2 the percentages make sense under the assumption of 18
>> respondents :
>>>> 5.6% =A0 =3D =A01 / 18
>>>> 11.1% =A0=3D =A02 / 18
>>>> 16.7% =A0=3D =A03 / 18
>>>> 22.2% =A0=3D =A04 / 18
>>>> 44.4% =A0=3D =A08 / 18
>>>> 77.8% =A0=3D 14 / 18
>>>>
>>>> but section 2.1 only lists 17 :
>>>> 1. =A0 =A0Time Warner Cable
>>>> 2. =A0 =A0Bright House Networks
>>>> 3. =A0 =A0Tinet
>>>> 4. =A0 =A0AboveNet
>>>> 5. =A0 =A0Telecom New Zealand
>>>> 6. =A0 =A0Cox Communications
>>>> 7. =A0 =A0MTN South Africa
>>>> 8. =A0 =A0Wipro Technologies
>>>> 9. =A0 =A0Verizon
>>>> 10. =A0 =A0AMS-IX
>>>> 11. =A0 =A0Superonline
>>>> 12. =A0 =A0Deutsche Telekom AG
>>>> 13. =A0 =A0Internet Solution
>>>> 14. =A0 =A0Easynet Global Services
>>>> 15. =A0 =A0Telstra Corporation
>>>> 16. =A0 =A0OJSC MegaFon
>>>> 17. =A0 =A0France Telecom Orange
>>>>
>>>> Did you leave someone off, or did someone answer twice ?
>>>>
>>>> Y(J)S
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf
>> Of Delregno, Christopher N (Nick DelRegno)
>>>> Sent: Tuesday, March 08, 2011 16:27
>>>> To: pwe3
>>>> Subject: [PWE3] FW: New Version Notification for
>> draft-delregno-pw-vccv-impl-survey-results-00
>>>>
>>>> Folks:
>>>>
>>>> The 00 draft of the PW/VCCV Implementation Survey Results have been
>> uploaded. =A0I will be presenting the results at IETF80.
>>>>
>>>>
>> https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-resu
>> lts/
>>>>
>>>> Thanks,
>>>> Nick
>>>>
>>>> Christopher N. Del Regno, PMTS
>>>> C&T, Ethernet Network Architecture & Design
>>>> 400 International Pkwy
>>>> Richardson, TX =A075081
>>>> 972-729-3411
>>>> nick.delregno@verizon.com
>>>>
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
>>>> Sent: Tuesday, March 08, 2011 8:16 AM
>>>> To: Delregno, Christopher N (Nick DelRegno)
>>>> Subject: New Version Notification for
>> draft-delregno-pw-vccv-impl-survey-results-00
>>>>
>>>>
>>>> A new version of I-D,
>> draft-delregno-pw-vccv-impl-survey-results-00.txt has been successfully
>> submitted by Nick Del Regno and posted to the IETF repository.
>>>>
>>>> Filename: =A0 =A0 draft-delregno-pw-vccv-impl-survey-results
>>>> Revision: =A0 =A0 00
>>>> Title: =A0 =A0 =A0 =A0 The Pseudowire (PW) & Virtual Circuit
>> Connectivity Verification (VCCV) Implementation Survey Results
>>>> Creation_date: =A0 =A0 2011-03-07
>>>> WG ID: =A0 =A0 =A0 =A0 Independent Submission
>>>> Number_of_pages: 16
>>>>
>>>> Abstract:
>>>> Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate
>>>> the use of the Control Word (CW) in order to better emulate the
>>>> services for which the encapsulations have been defined. =A0However,
>>>> some encapulations treat the Control Word as optional. =A0As a result,
>>>> implementations of the CW, for encapsulations for which it is
>>>> optional, vary by equipment manufacturer, equipment model and service
>>>> provider network. =A0Similarly, Virtual Circuit Connectivity
>>>> Verification (VCCV) supports three Control Channel (CC) types and
>>>> multiple Connectivity Verification (CV) Types. =A0This flexibility has
>>>> led to reports of interoperability issues within deployed networks
>>>> and associated drafts to attempt to remedy the situation. =A0This
>>>> survey of the PW/VCCV user community was conducted to determine
>>>> implementation trends. =A0The survey and results is presented herein.
>>>>
>>>>
>>>>
>>>> The IETF Secretariat.
>>>>
>>>>
>>>> _______________________________________________
>>>> pwe3 mailing list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>> _______________________________________________
>>>> pwe3 mailing list
>>>> pwe3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>>
>>
>>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

From amalis@gmail.com  Fri Mar 18 09:59:22 2011
Return-Path: <amalis@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7ED73A6990 for <pwe3@core3.amsl.com>; Fri, 18 Mar 2011 09:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 dx2Tixvydtie for <pwe3@core3.amsl.com>; Fri, 18 Mar 2011 09:59:21 -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 A0F0D3A698F for <pwe3@ietf.org>; Fri, 18 Mar 2011 09:59:21 -0700 (PDT)
Received: by ewy19 with SMTP id 19so1164916ewy.31 for <pwe3@ietf.org>; Fri, 18 Mar 2011 10:00:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=qYPl5zm0pkLhHLd54S2zcYDfoUGuHcObyzA8g+FYTc8=; b=Pw1wTcmkDeOe/5vXsVI+u5g87kAsZqBNZJeWVkV0ao+F5RBWB7Im4TNMN21/k2smoQ CQxUKTLTC7T2FeQK0BvX0lCUsA79/kom0LN2VKNx+eb21i1f+m+Cr6ioYxYMyrewiJgW xUKDxZZX/h17s9zdSOy6kH8qmrUvBLs145hAg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=LdBfVNLJaL/RwEZmgxLVxTJXkNdmZNr88nj6kywV9LQ8ULYyyvMk+ZXZfWrtIepF10 vI58+CmitJLNnV5cRikIzYgeApFZal17kSnrJVuqgU7kHtn+vrgq9BgiqdFNKbYr054n bJnHsxJt8USLbDiQ32MPZPMm84SrFABzmWgoc=
Received: by 10.14.121.82 with SMTP id q58mr74718eeh.144.1300467650236; Fri, 18 Mar 2011 10:00:50 -0700 (PDT)
MIME-Version: 1.0
Sender: amalis@gmail.com
Received: by 10.14.49.147 with HTTP; Fri, 18 Mar 2011 10:00:30 -0700 (PDT)
In-Reply-To: <20110315145101.38C853A6E1E@core3.amsl.com>
References: <20110315145101.38C853A6E1E@core3.amsl.com>
From: "Andrew G. Malis" <andrew.g.malis@verizon.com>
Date: Fri, 18 Mar 2011 13:00:30 -0400
X-Google-Sender-Auth: ZstqUDFvqIfS2NN_UFgH7gaEjjM
Message-ID: <AANLkTimc6399exTHY9WV7ZMSAjSZgCWcPwb9cq_7B_N2@mail.gmail.com>
To: tsbsg15@itu.int
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Huub.van.Helvoort@huawei.com, greg.jones@itu.int, Steve.Trowbridge@alcatel-lucent.com, yoichi.maeda@ttc.or.jp, hiroshi.ota@itu.int, adrian.farrel@huawei.com, pwe3@ietf.org, paf@cisco.com, stbryant@cisco.com
Subject: Re: [PWE3] New Liaison Statement, "LS296 - Reply to the IETF PWE3 WG LC on draft-ietf-pwe3-mpls-tp-gal-in-pw-00"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2011 16:59:22 -0000

Greg,

Many thanks for the liaison.

Regards,
Andy

On Tue, Mar 15, 2011 at 10:51 AM, Greg Jones <tsbsg15@itu.int> wrote:
>
> Title: LS296 - Reply to the IETF PWE3 WG LC on draft-ietf-pwe3-mpls-tp-ga=
l-in-pw-00
> Submission Date: 2011-03-15
> URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_det=
ail.cgi?detail_id=3D1034
>
> From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
> To: IETF PWE3 WG(andrew.g.malis@verizon.com,matthew.bocci@alcatel-lucent.=
com)
> Cc: paf@cisco.com
> stbryant@cisco.com
> adrian.farrel@huawei.com
> pwe3@ietf.org
> yoichi.maeda@ttc.or.jp
> Steve.Trowbridge@alcatel-lucent.com
> Reponse Contact: tsbsg15@itu.int
> greg.jones@itu.int
> hiroshi.ota@itu.int
> Technical Contact: Huub.van.Helvoort@huawei.com
> Purpose: For information
> Body: Thank you for your liaison statement: IETF PWE3 Working Group Last =
Call on draft-ietf-pwe3-mpls-tp-gal-in-pw-00 =EF=BF=BDUsing the Generic Ass=
ociated Channel Label for Pseudowire in MPLS-TP".
> The Q10/15 experts have reviewed draft and have no comments.
> Q10/15 supports the publication of this draft as an RFC.
> Attachment(s):
> =C2=A0 =C2=A0 LS296 - Reply to the IETF PWE3 WG LC on draft-ietf-pwe3-mpl=
s-tp-gal-in-pw-00 - pdf body (https://datatracker.ietf.org/documents/LIAISO=
N/file1211.pdf)
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

From Robert.Rennison@ecitele.com  Tue Mar 22 09:20:54 2011
Return-Path: <Robert.Rennison@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C67353A6864; Tue, 22 Mar 2011 09:20: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 FOv9b1iy6P0G; Tue, 22 Mar 2011 09:20:42 -0700 (PDT)
Received: from uspitbmg01.ecitele.com (uspitbmg01-out.ecitele.com [63.94.127.136]) by core3.amsl.com (Postfix) with ESMTP id D74903A684D; Tue, 22 Mar 2011 09:20:41 -0700 (PDT)
X-AuditID: 3f5e7f87-b7bf5ae000004c45-7f-4d88f422f96d
Received: from uspitexch02.ecitele.com ( [10.0.0.72]) by uspitbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id B1.60.19525.224F88D4; Tue, 22 Mar 2011 15:10:26 -0400 (EDT)
Received: from USPITMAIL01.ecitele.com ([10.0.0.81]) by uspitexch02.ecitele.com ([10.0.0.72]) with mapi; Tue, 22 Mar 2011 12:22:13 -0400
From: Robert Rennison <Robert.Rennison@ecitele.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, Greg Mirsky <gregimirsky@gmail.com>, Luca Martini <lmartini@cisco.com>
Date: Tue, 22 Mar 2011 12:22:12 -0400
Thread-Topic: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Thread-Index: AcvgIJCjINO9d7bvQ8uZXoqo8NcncgAAI1awAiJ1VXA=
Message-ID: <786AD2EC3D80A1428B921CDC9BE9EE546569F9F8E1@USPITMAIL01.ecitele.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com> <4D5E9442.3030101@cisco.com> <AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com> <4D7A2439.6010508@cisco.com> <AANLkTim+hqNFHi9xwuzG5_2qoKztEn9SJA9TDh-S-XUo@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D6FBBDD332@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D6FBBDD332@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_786AD2EC3D80A1428B921CDC9BE9EE546569F9F8E1USPITMAIL01ec_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "lihan@chinamobile.com" <lihan@chinamobile.com>, "mpls@ietf.org" <mpls@ietf.org>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2011 16:20:54 -0000

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

Luca, Thomas,

A couple of clarification questions.

I'm trying to understand what the combination of the two drafts, -lm-pwe3-m=
pls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2 amounts to.

So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it's saying u=
se VCCV type 1 where possible and if not then use the new type 4, whereby  =
in type 4 the exception mechanism is triggered by the use of the GAL,  and =
I appreciated the diagram in section 3 to lock this is, so far so good.

Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these two drafts c=
ould work together since this one is trying to lay the "legal framework" i.=
e fix up the RFCs which mandated that the GAL could not be used with the PW=
.

Then I get hit with a brick wall in the form of the statements in the last =
2 paras of section 3 of tp-gal-in-pw which state.

- Section 4.2<http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00=
#section-4.2>. (GAL Applicability and Usage) in [RFC5586<http://tools.ietf.=
org/html/rfc5586>], the
      original text:

          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
          LSPs, Concatenated Segments of LSPs, and with Sections, and
          MUST NOT be used with PWs. It MUST always be at the bottom of
          the label stack (i.e., S bit set to 1). However, in other MPLS
          environments, this document places no restrictions on where
          the GAL may appear within the label stack or its use with PWs.

      is replaced by:

          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
          LSPs, Concatenated Segments of LSPs, and with Sections, and
          MAY be used with PWs. It MUST always be at the bottom of the
          label stack (i.e., S bit set to 1). However, in other MPLS
          environments, this document places no restrictions on where
          the GAL may appear within the label stack.


It's the bit about the GAL MUST be at the bottom of the label stack,  this =
is clearly inconsistent with what is proposed in the draft-nadeau-pwe3 wher=
e one can clearly see the GAL above the PW label and if one has to use  a G=
AL with a PW this would be the place to put it,

Now I can hear you saying "oh but look at the text below this, where we sta=
te .."However, in other MPLS environments , this document places no restric=
tions on where the GAL may appear within the label stack. This is consisten=
t with draft-nadeau "   In which case I'd retort with ; what are we to do f=
or PWs in   MPLS-TP, since what's in draft-nadeau would not be allowed ?

Clarification /explanation appreciated.

Cheers

Rob Rennison


From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Ale=
xander Vainshtein
Sent: Friday, March 11, 2011 2:22 PM
To: Greg Mirsky; Luca Martini
Cc: lihan@chinamobile.com; mpls-tp@ietf.org; pwe3; HUANG Feng F; mpls@ietf.=
org
Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

Greg, Luca,
As I've already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO it m=
akes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.

My 2c,
     Sasha

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Gre=
g Mirsky
Sent: Friday, March 11, 2011 9:14 PM
To: Luca Martini
Cc: lihan@chinamobile.com; mpls@ietf.org; pwe3; HUANG Feng F; mpls-tp@ietf.=
org
Subject: Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt

Dear Luca,
thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. I'll se=
nd my comments to it in a separate e-mail.
I'll have to miss another opportunity to discuss your proposal in a meeting=
. Please add my comments below to my earlier expressed WG LC comments:

 *   the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that ad=
dresses applicability of GAL in PW VCCV, e.g. solution proposed in draft-na=
deau-pwe3-vccv-2-01;
 *   the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such dependenc=
y and refer to any existing proposal;
 *   I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced =
in lock with document that addresses use of GAL in PW VCCV.
Regards,
Greg
On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini <lmartini@cisco.com<mailto:lm=
artini@cisco.com>> wrote:
Greg ,
Some

On 02/18/11 11:15, Greg Mirsky wrote:
> Dear Luca,
> I see at least two issues:
>
>     * use of GAL for PW, in my view, is another VCCV CC type that has
>       to be negotiated as described in RFC 5085.
>
These are valid points, but this document in question does not define,
not discussed VCCV.
We have since posted a draft that proposes a new VCCV mode , and we
welcome comments regarding that document.
(draft-nadeau-pwe3-vccv-2-01.txt)

>     * use of GAL creates ambiguous situation when PW CW is used. The
>       benefit from extending GAL in PW, as I see, is for PWs that are
>       not required to use PW CW. That might be a good enough reason to
>       update RFC 5586 as proposed in the document but we must address
>       use cases of GAL in PWs that require presence PW CW. If we
>       prohibit or even discourage use of GAL for these PWs that have
>       PW VCCV as native Associated Channel, then architecture of ACh
>       for MPLS-TP PW not simplified as result of adopting the proposal.
>
> Regard
Greg,
The GAL is basically a notifier that the packet following the end of the
MPLS label stack, is explicitly defined as a G-ACH format.
Normally the packet would be decoded as an IP packet , unless the last
label on the stack indicated otherwise.

The GAL can certainly be applied  to a PW OAM packet on a PW that uses
the CW, and this document does not define that , nor restricts it.

The scope of this document is limited to removing an unnecessary
restriction in rfc5586, hence  this comment not applicable to this document=
.

Thanks.
Luca

> s,
> Greg
>
> On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com<mailto:=
lmartini@cisco.com>
> <mailto:lmartini@cisco.com<mailto:lmartini@cisco.com>>> wrote:
>
>     Greg,
>
>     Sorry, but I do not remember the point you mention.
>     Can you explain again here ?
>     Thanks.
>     Luca
>
>
>     On 02/17/11 23:47, Greg Mirsky wrote:
>     > Dear Authors and All,
>     > prior to the meeting in Bejing and acceptance of this proposal as W=
G
>     > document Luca and I agreed that use of GAL with PW VCCV presents a
>     > problem.
>     > I was not attending the IETF-79, nor I found discussion of this
>     issue
>     > in the minutes. I think that this issue should be specified,
>     > explained. In my view, this document updates not only RFC 5586
>     > but RFC 5085 too.
>     >
>     > Regards,
>     > Greg
>     >
>     > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>     >
>     > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
>     <lmartini@cisco.com<mailto:lmartini@cisco.com> <mailto:lmartini@cisco=
.com<mailto:lmartini@cisco.com>>
>     > <mailto:lmartini@cisco.com<mailto:lmartini@cisco.com> <mailto:lmart=
ini@cisco.com<mailto:lmartini@cisco.com>>>> wrote:
>     >
>     >     Greg,
>     >
>     >     You are correct , the proposed update does not propose any
>     changes
>     >     to VCCV.
>     >     However the problem with vccv is not as simple as to ask for
>     a new
>     >     code point from IANA.
>     >     Given the good amount of discussion on this point, we should
>     >     probably have a discussion in Beijing.
>     >
>     >     Luca
>     >
>     >
>     >
>     >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
>     >>     Dear Authors,
>     >>     I think that proposed update of the Section 4.2. RFC 5586
>     makes it possible
>     >>     to use GAL on MPLS-TP PW that uses Control Word. I consider
>     it to be
>     >>     conflict between PW VCCV CC types because use of GAL is not
>     negotiated
>     >>     through PW VCCV negotiation. To avoid such situation I propose=
:
>     >>
>     >>        - in Section 5 request IANA to assign new CC Type "MPLS
>     Generic
>     >>        Associated Channel Label"
>     >>        - assign precedence to new CC Type that affects Section
>     7 RFC 5085
>     >>
>     >>     Regards,
>     >>     Greg
>     >>
>     >>
>     >>
>     >>     _______________________________________________
>     >>     mpls mailing list
>     >>     mpls@ietf.org<mailto:mpls@ietf.org> <mailto:mpls@ietf.org<mail=
to:mpls@ietf.org>> <mailto:mpls@ietf.org<mailto:mpls@ietf.org>
>     <mailto:mpls@ietf.org<mailto:mpls@ietf.org>>>
>     >>     https://www.ietf.org/mailman/listinfo/mpls
>     >
>     >
>     >
>     > _______________________________________________
>     > mpls mailing list
>     > mpls@ietf.org<mailto:mpls@ietf.org> <mailto:mpls@ietf.org<mailto:mp=
ls@ietf.org>>
>     > https://www.ietf.org/mailman/listinfo/mpls
>
>


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><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;}
/* 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.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
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;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1278948757;
	mso-list-template-ids:-1227977334;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1800680213;
	mso-list-template-ids:-512447670;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	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"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Luca, Tho=
mas,<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></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'>A couple of clarification questions.<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'>I&#8217;m trying to understand what the combinat=
ion of the two drafts, </span><span style=3D'font-size:11.0pt;font-family:"=
Calibri","sans-serif";color:#1F497D'>-lm-pwe3-mpls-tp-gal-in-pw, and draft-=
nadeau-pwe3-vccv-2</span><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'> amounts to.<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";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'=
>So, I think I understood the </span><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>draft-nadeau-pwe3-vccv-2 in tha=
t it&#8217;s saying use VCCV type 1 where possible and if not then use the =
new type 4, whereby &nbsp;in type 4 the exception mechanism is triggered by=
 the use of the GAL, &nbsp;and I appreciated the diagram in section 3 to lo=
ck this is, so far so good.<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'>Now I read -pwe3-=
mpls-tp-gal-in-pw and I&#8217;m thinking , Ok these two drafts could work t=
ogether since this one is trying to lay the &#8220;legal framework&#8221; i=
.e fix up the RFCs which mandated that the GAL could not be used with the P=
W. <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'>Then I get hit with a brick wall in the f=
orm of the statements in the last 2 paras of section 3 of tp-gal-in-pw whic=
h state.<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 style=3D'page-break-before:always'><span st=
yle=3D'font-family:"Courier New";color:black'>- <a href=3D"http://tools.iet=
f.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2">Section 4.2</a>.=
 (GAL Applicability and Usage) in [<a href=3D"http://tools.ietf.org/html/rf=
c5586" title=3D"&quot;MPLS Generic Associated Channel&quot;">RFC5586</a>], =
the<o:p></o:p></span></p><p class=3DMsoNormal style=3D'page-break-before:al=
ways'><span style=3D'font-family:"Courier New";color:black'>&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; original text:<o:p></o:p></span></p><p class=3DMsoNormal st=
yle=3D'page-break-before:always'><span style=3D'font-family:"Courier New";c=
olor:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'page-=
break-before:always'><span style=3D'font-family:"Courier New";color:black'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In MPLS-TP, the GAL =
MUST be used with packets on a G-ACh on<o:p></o:p></span></p><p class=3DMso=
Normal style=3D'page-break-before:always'><span style=3D'font-family:"Couri=
er New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 LSPs, Concatenated Segments of LSPs, and with Sections, and<o:p></o:p></sp=
an></p><p class=3DMsoNormal style=3D'page-break-before:always'><span style=
=3D'font-family:"Courier New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; MUST NOT be used with PWs. It MUST always be at the =
bottom of<o:p></o:p></span></p><p class=3DMsoNormal style=3D'page-break-bef=
ore:always'><span style=3D'font-family:"Courier New";color:black'>&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the label stack (i.e., S bit =
set to 1). However, in other MPLS<o:p></o:p></span></p><p class=3DMsoNormal=
 style=3D'page-break-before:always'><span style=3D'font-family:"Courier New=
";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; envir=
onments, this document places no restrictions on where<o:p></o:p></span></p=
><p class=3DMsoNormal style=3D'page-break-before:always'><span style=3D'fon=
t-family:"Courier New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; the GAL may appear within the label stack or its use with P=
Ws.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'page-break-before:al=
ways'><span style=3D'font-family:"Courier New";color:black'><o:p>&nbsp;</o:=
p></span></p><p class=3DMsoNormal style=3D'page-break-before:always'><span =
style=3D'font-family:"Courier New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; is replaced by:<o:p></o:p></span></p><p class=3DMsoNormal style=3D'page=
-break-before:always'><span style=3D'font-family:"Courier New";color:black'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'page-break-befor=
e:always'><span style=3D'font-family:"Courier New";color:black'>&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In MPLS-TP, the GAL MUST be use=
d with packets on a G-ACh on<o:p></o:p></span></p><p class=3DMsoNormal styl=
e=3D'page-break-before:always'><span style=3D'font-family:"Courier New";col=
or:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LSPs, Conc=
atenated Segments of LSPs, and with Sections, and<o:p></o:p></span></p><p c=
lass=3DMsoNormal style=3D'page-break-before:always'><span style=3D'font-fam=
ily:"Courier New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; MAY be used with PWs. It MUST always be at the bottom of the<o:p=
></o:p></span></p><p class=3DMsoNormal style=3D'page-break-before:always'><=
span style=3D'font-family:"Courier New";color:black'>&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; label stack (i.e., S bit set to 1). Howeve=
r, in other MPLS<o:p></o:p></span></p><p class=3DMsoNormal style=3D'page-br=
eak-before:always'><span style=3D'font-family:"Courier New";color:black'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; environments, this doc=
ument places no restrictions on where<o:p></o:p></span></p><p class=3DMsoNo=
rmal style=3D'page-break-before:always'><span style=3D'font-family:"Courier=
 New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; t=
he GAL may appear within the label stack.<o:p></o:p></span></p><p class=3DM=
soNormal><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 styl=
e=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.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>It&#8217;s the bit abo=
ut the GAL MUST be at the bottom of the label stack,&nbsp; this is clearly =
inconsistent with what is proposed in the draft-nadeau-pwe3 where one can c=
learly see the GAL above the PW label and if one has to use&nbsp; a GAL wit=
h a PW this would be the place to put it,<o:p></o:p></span></p><p class=3DM=
soNormal><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 styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Now=
 I can hear you saying &#8220;oh but look at the text below this, where we =
state ..&#8221;However, in other MPLS environments , this document places n=
o restrictions on where the GAL may appear within the label stack. This is =
consistent with draft-nadeau &#8220;&nbsp; &nbsp;In which case I&#8217;d re=
tort with ; what are we to do for PWs in &nbsp;&nbsp;MPLS-TP, since what&#8=
217;s in draft-nadeau would not be allowed ?<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";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'=
>Clarification /explanation appreciated. <o:p></o:p></span></p><p class=3DM=
soNormal><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 styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Che=
ers<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'>Rob Rennison<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";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=
'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;border-top:sol=
id #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span s=
tyle=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-b=
ounces@ietf.org [mailto:mpls-bounces@ietf.org] <b>On Behalf Of </b>Alexande=
r Vainshtein<br><b>Sent:</b> Friday, March 11, 2011 2:22 PM<br><b>To:</b> G=
reg Mirsky; Luca Martini<br><b>Cc:</b> lihan@chinamobile.com; mpls-tp@ietf.=
org; pwe3; HUANG Feng F; mpls@ietf.org<br><b>Subject:</b> Re: [mpls] WG LC =
draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<o:p></o:p></span></p></div></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'>Greg, Lu=
ca,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>As I&#8217;ve already =
stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO it makes draft-lm-pw=
e3-mpls-tp-gal-in-pw completely useless.<o:p></o:p></span></p><p class=3DMs=
oNormal><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'>My 2=
c,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp=
; Sasha<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:0i=
n 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>Greg Mirsky<br><b>Se=
nt:</b> Friday, March 11, 2011 9:14 PM<br><b>To:</b> Luca Martini<br><b>Cc:=
</b> lihan@chinamobile.com; mpls@ietf.org; pwe3; HUANG Feng F; mpls-tp@ietf=
.org<br><b>Subject:</b> Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00=
.txt<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p><p class=3DMsoNormal>Dear Luca,<br>thank you for bringing draft-nadeau=
-pwe3-vccv-2-01 to my attention. I'll send my comments to it in a separate =
e-mail.<br>I'll have to miss another opportunity to discuss your proposal i=
n a meeting. Please add my comments below to my earlier expressed WG LC com=
ments:<o:p></o:p></p><ul type=3Ddisc><li class=3DMsoNormal style=3D'mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3'>the dr=
aft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution that addresses app=
licability of GAL in PW VCCV, e.g. solution proposed in draft-nadeau-pwe3-v=
ccv-2-01;<o:p></o:p></li><li class=3DMsoNormal style=3D'mso-margin-top-alt:=
auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3'>the draft-lm-pwe3-=
mpls-tp-gal-in-pw-00 needs to mention such dependency and refer to any exis=
ting proposal;<o:p></o:p></li><li class=3DMsoNormal style=3D'mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3'>I believe tha=
t the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced in lock with docum=
ent that addresses use of GAL in PW VCCV.<o:p></o:p></li></ul><p class=3DMs=
oNormal style=3D'margin-bottom:12.0pt'>Regards,<br>Greg<o:p></o:p></p><div>=
<p class=3DMsoNormal>On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini &lt;<a h=
ref=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt; wrote:<o:p></o=
:p></p><p class=3DMsoNormal>Greg ,<br>Some<o:p></o:p></p><div><p class=3DMs=
oNormal><br>On 02/18/11 11:15, Greg Mirsky wrote:<br>&gt; Dear Luca,<br>&gt=
; I see at least two issues:<br>&gt;<br>&gt; &nbsp; &nbsp; * use of GAL for=
 PW, in my view, is another VCCV CC type that has<br>&gt; &nbsp; &nbsp; &nb=
sp; to be negotiated as described in RFC 5085.<br>&gt;<o:p></o:p></p></div>=
<p class=3DMsoNormal>These are valid points, but this document in question =
does not define,<br>not discussed VCCV.<br>We have since posted a draft tha=
t proposes a new VCCV mode , and we<br>welcome comments regarding that docu=
ment.<br>(draft-nadeau-pwe3-vccv-2-01.txt)<br><br>&gt; &nbsp; &nbsp; * use =
of GAL creates ambiguous situation when PW CW is used. The<o:p></o:p></p><d=
iv><p class=3DMsoNormal>&gt; &nbsp; &nbsp; &nbsp; benefit from extending GA=
L in PW, as I see, is for PWs that are<br>&gt; &nbsp; &nbsp; &nbsp; not req=
uired to use PW CW. That might be a good enough reason to<br>&gt; &nbsp; &n=
bsp; &nbsp; update RFC 5586 as proposed in the document but we must address=
<br>&gt; &nbsp; &nbsp; &nbsp; use cases of GAL in PWs that require presence=
 PW CW. If we<br>&gt; &nbsp; &nbsp; &nbsp; prohibit or even discourage use =
of GAL for these PWs that have<br>&gt; &nbsp; &nbsp; &nbsp; PW VCCV as nati=
ve Associated Channel, then architecture of ACh<br>&gt; &nbsp; &nbsp; &nbsp=
; for MPLS-TP PW not simplified as result of adopting the proposal.<br>&gt;=
<br>&gt; Regard<o:p></o:p></p></div><p class=3DMsoNormal>Greg,<br>The GAL i=
s basically a notifier that the packet following the end of the<br>MPLS lab=
el stack, is explicitly defined as a G-ACH format.<br>Normally the packet w=
ould be decoded as an IP packet , unless the last<br>label on the stack ind=
icated otherwise.<br><br>The GAL can certainly be applied &nbsp;to a PW OAM=
 packet on a PW that uses<br>the CW, and this document does not define that=
 , nor restricts it.<br><br>The scope of this document is limited to removi=
ng an unnecessary<br>restriction in rfc5586, hence &nbsp;this comment not a=
pplicable to this document.<br><br>Thanks.<br>Luca<o:p></o:p></p><div><p cl=
ass=3DMsoNormal><br>&gt; s,<br>&gt; Greg<br>&gt;<br>&gt; On Fri, Feb 18, 20=
11 at 7:46 AM, Luca Martini &lt;<a href=3D"mailto:lmartini@cisco.com">lmart=
ini@cisco.com</a><o:p></o:p></p></div><div><p class=3DMsoNormal>&gt; &lt;ma=
ilto:<a href=3D"mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;&gt; w=
rote:<br>&gt;<br>&gt; &nbsp; &nbsp; Greg,<br>&gt;<br>&gt; &nbsp; &nbsp; Sor=
ry, but I do not remember the point you mention.<br>&gt; &nbsp; &nbsp; Can =
you explain again here ?<br>&gt; &nbsp; &nbsp; Thanks.<br>&gt; &nbsp; &nbsp=
; Luca<br>&gt;<br>&gt;<br>&gt; &nbsp; &nbsp; On 02/17/11 23:47, Greg Mirsky=
 wrote:<br>&gt; &nbsp; &nbsp; &gt; Dear Authors and All,<br>&gt; &nbsp; &nb=
sp; &gt; prior to the meeting in Bejing and acceptance of this proposal as =
WG<br>&gt; &nbsp; &nbsp; &gt; document Luca and I agreed that use of GAL wi=
th PW VCCV presents a<br>&gt; &nbsp; &nbsp; &gt; problem.<br>&gt; &nbsp; &n=
bsp; &gt; I was not attending the IETF-79, nor I found discussion of this<b=
r>&gt; &nbsp; &nbsp; issue<br>&gt; &nbsp; &nbsp; &gt; in the minutes. I thi=
nk that this issue should be specified,<br>&gt; &nbsp; &nbsp; &gt; explaine=
d. In my view, this document updates not only RFC 5586<br>&gt; &nbsp; &nbsp=
; &gt; but RFC 5085 too.<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &=
gt; Regards,<br>&gt; &nbsp; &nbsp; &gt; Greg<br>&gt; &nbsp; &nbsp; &gt;<br>=
&gt; &nbsp; &nbsp; &gt; Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<b=
r>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; On Sat, Oct 30, 2010 a=
t 10:14 AM, Luca Martini<br>&gt; &nbsp; &nbsp; &lt;<a href=3D"mailto:lmarti=
ni@cisco.com">lmartini@cisco.com</a> &lt;mailto:<a href=3D"mailto:lmartini@=
cisco.com">lmartini@cisco.com</a>&gt;<o:p></o:p></p></div><div><div><p clas=
s=3DMsoNormal>&gt; &nbsp; &nbsp; &gt; &lt;mailto:<a href=3D"mailto:lmartini=
@cisco.com">lmartini@cisco.com</a> &lt;mailto:<a href=3D"mailto:lmartini@ci=
sco.com">lmartini@cisco.com</a>&gt;&gt;&gt; wrote:<br>&gt; &nbsp; &nbsp; &g=
t;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Greg,<br>&gt; &nbsp; &nbsp; &gt=
;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; You are correct , the proposed u=
pdate does not propose any<br>&gt; &nbsp; &nbsp; changes<br>&gt; &nbsp; &nb=
sp; &gt; &nbsp; &nbsp; to VCCV.<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Ho=
wever the problem with vccv is not as simple as to ask for<br>&gt; &nbsp; &=
nbsp; a new<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; code point from IANA.<=
br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Given the good amount of discussio=
n on this point, we should<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; probabl=
y have a discussion in Beijing.<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &=
nbsp; &gt; &nbsp; &nbsp; Luca<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nb=
sp; &gt;<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp=
; On 10/29/2010 05:07 PM, Greg Mirsky wrote:<br>&gt; &nbsp; &nbsp; &gt;&gt;=
 &nbsp; &nbsp; Dear Authors,<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; I=
 think that proposed update of the Section 4.2. RFC 5586<br>&gt; &nbsp; &nb=
sp; makes it possible<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; to use G=
AL on MPLS-TP PW that uses Control Word. I consider<br>&gt; &nbsp; &nbsp; i=
t to be<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; conflict between PW VC=
CV CC types because use of GAL is not<br>&gt; &nbsp; &nbsp; negotiated<br>&=
gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; through PW VCCV negotiation. To av=
oid such situation I propose:<br>&gt; &nbsp; &nbsp; &gt;&gt;<br>&gt; &nbsp;=
 &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;- in Section 5 request IANA to =
assign new CC Type &quot;MPLS<br>&gt; &nbsp; &nbsp; Generic<br>&gt; &nbsp; =
&nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;Associated Channel Label&quot;<b=
r>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;- assign precedenc=
e to new CC Type that affects Section<br>&gt; &nbsp; &nbsp; 7 RFC 5085<br>&=
gt; &nbsp; &nbsp; &gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Reg=
ards,<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Greg<br>&gt; &nbsp; &nbs=
p; &gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt;<br>&gt; &nbsp; &nbsp; &gt;&gt;<b=
r>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; _______________________________=
________________<br>&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; mpls mailing =
list<o:p></o:p></p></div></div><p class=3DMsoNormal>&gt; &nbsp; &nbsp; &gt;=
&gt; &nbsp; &nbsp; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> &lt;m=
ailto:<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt; &lt;mailto:<a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></p><div><div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>&gt; &nbsp; &nbsp; &lt;mai=
lto:<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;&gt;<br>&gt; &nbs=
p; &nbsp; &gt;&gt; &nbsp; &nbsp; <a href=3D"https://www.ietf.org/mailman/li=
stinfo/mpls" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mpls</=
a><br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nbsp; &gt;<br>&gt; &nbsp; &nb=
sp; &gt;<br>&gt; &nbsp; &nbsp; &gt; _______________________________________=
________<br>&gt; &nbsp; &nbsp; &gt; mpls mailing list<br>&gt; &nbsp; &nbsp;=
 &gt; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a> &lt;mailto:<a href=
=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<br>&gt; &nbsp; &nbsp; &gt; =
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>&gt;<br>&gt;<o:p></o:p></p>=
</div></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></b=
ody></html>=

--_000_786AD2EC3D80A1428B921CDC9BE9EE546569F9F8E1USPITMAIL01ec_--

From stbryant@cisco.com  Tue Mar 22 10:58:49 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7103B28C159; Tue, 22 Mar 2011 10:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.465
X-Spam-Level: 
X-Spam-Status: No, score=-110.465 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 LmlzcuiIo6vA; Tue, 22 Mar 2011 10:58:40 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id C3A8228C150; Tue, 22 Mar 2011 10:58:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=44897; q=dns/txt; s=iport; t=1300816812; x=1302026412; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=ldUhwkW5m/3VnHP2DGVxUIPuh2f/nr/FUsRSr+lnMaA=; b=OXUjKhjekI9mjjb3GIon8Sd7FgPiedAYKFm4wVSuW7tTrsS8qRlcGYCV DigVSoTYk7ebm2qQSR/qj3qdDk2gjz3YOSkauVWOuWHM4WD+YwGkZjctk By+bPrX0l+X9WqBO74p7M3xnTOPsM1Q9GS3N+Cu3GUL5wmxAZWQFJ0RdO Y=;
X-IronPort-AV: E=Sophos;i="4.63,226,1299456000"; d="scan'208,217";a="22723818"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 22 Mar 2011 18:00:11 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2MI0BaE011913; Tue, 22 Mar 2011 18:00:11 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p2MI08U07504; Tue, 22 Mar 2011 18:00:08 GMT
Message-ID: <4D88E3A7.4040502@cisco.com>
Date: Tue, 22 Mar 2011 18:00:07 +0000
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.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Robert Rennison <Robert.Rennison@ecitele.com>
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com>	<4D5E9442.3030101@cisco.com>	<AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com>	<4D7A2439.6010508@cisco.com>	<AANLkTim+hqNFHi9xwuzG5_2qoKztEn9SJA9TDh-S-XUo@mail.gmail.com>	<A3C5DF08D38B6049839A6F553B331C76D6FBBDD332@ILPTMAIL02.ecitele.com> <786AD2EC3D80A1428B921CDC9BE9EE546569F9F8E1@USPITMAIL01.ecitele.com>
In-Reply-To: <786AD2EC3D80A1428B921CDC9BE9EE546569F9F8E1@USPITMAIL01.ecitele.com>
Content-Type: multipart/alternative; boundary="------------050303000603040509070000"
Cc: "mpls@ietf.org" <mpls@ietf.org>, Luca Martini <lmartini@cisco.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2011 17:58:49 -0000

This is a multi-part message in MIME format.
--------------050303000603040509070000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

If there is IETF consensus to update RFC5586 with this change then the 
process is relatively simple:

The document making the update notes that it does the update, and the AD 
draws attention to
this in the IETF LC.

Stewart



On 22/03/2011 16:22, Robert Rennison wrote:
>
> Luca, Thomas,
>
> A couple of clarification questions.
>
> I'm trying to understand what the combination of the two drafts, 
> -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts to.
>
> So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it's 
> saying use VCCV type 1 where possible and if not then use the new type 
> 4, whereby  in type 4 the exception mechanism is triggered by the use 
> of the GAL,  and I appreciated the diagram in section 3 to lock this 
> is, so far so good.
>
> Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these two 
> drafts could work together since this one is trying to lay the "legal 
> framework" i.e fix up the RFCs which mandated that the GAL could not 
> be used with the PW.
>
> Then I get hit with a brick wall in the form of the statements in the 
> last 2 paras of section 3 of tp-gal-in-pw which state.
>
> - Section 4.2 
> <http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2>. 
> (GAL Applicability and Usage) in [RFC5586 
> <http://tools.ietf.org/html/rfc5586>], the
>
>       original text:
>
>           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>
>           LSPs, Concatenated Segments of LSPs, and with Sections, and
>
>           MUST NOT be used with PWs. It MUST always be at the bottom of
>
>           the label stack (i.e., S bit set to 1). However, in other MPLS
>
>           environments, this document places no restrictions on where
>
>           the GAL may appear within the label stack or its use with PWs.
>
>       is replaced by:
>
>           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>
>           LSPs, Concatenated Segments of LSPs, and with Sections, and
>
>           MAY be used with PWs. It MUST always be at the bottom of the
>
>           label stack (i.e., S bit set to 1). However, in other MPLS
>
>           environments, this document places no restrictions on where
>
>           the GAL may appear within the label stack.
>
> It's the bit about the GAL MUST be at the bottom of the label stack,  
> this is clearly inconsistent with what is proposed in the 
> draft-nadeau-pwe3 where one can clearly see the GAL above the PW label 
> and if one has to use  a GAL with a PW this would be the place to put it,
>
> Now I can hear you saying "oh but look at the text below this, where 
> we state .."However, in other MPLS environments , this document places 
> no restrictions on where the GAL may appear within the label stack. 
> This is consistent with draft-nadeau "   In which case I'd retort with 
> ; what are we to do for PWs in   MPLS-TP, since what's in draft-nadeau 
> would not be allowed ?
>
> Clarification /explanation appreciated.
>
> Cheers
>
> Rob Rennison
>
> *From:*mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] *On Behalf 
> Of *Alexander Vainshtein
> *Sent:* Friday, March 11, 2011 2:22 PM
> *To:* Greg Mirsky; Luca Martini
> *Cc:* lihan@chinamobile.com; mpls-tp@ietf.org; pwe3; HUANG Feng F; 
> mpls@ietf.org
> *Subject:* Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>
> Greg, Luca,
>
> As I've already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO 
> it makes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.
>
> My 2c,
>
>      Sasha
>
> *From:*mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] *On Behalf 
> Of *Greg Mirsky
> *Sent:* Friday, March 11, 2011 9:14 PM
> *To:* Luca Martini
> *Cc:* lihan@chinamobile.com; mpls@ietf.org; pwe3; HUANG Feng F; 
> mpls-tp@ietf.org
> *Subject:* Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>
> Dear Luca,
> thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. 
> I'll send my comments to it in a separate e-mail.
> I'll have to miss another opportunity to discuss your proposal in a 
> meeting. Please add my comments below to my earlier expressed WG LC 
> comments:
>
>     * the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution
>       that addresses applicability of GAL in PW VCCV, e.g. solution
>       proposed in draft-nadeau-pwe3-vccv-2-01;
>     * the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such
>       dependency and refer to any existing proposal;
>     * I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be
>       advanced in lock with document that addresses use of GAL in PW VCCV.
>
> Regards,
> Greg
>
> On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini <lmartini@cisco.com 
> <mailto:lmartini@cisco.com>> wrote:
>
> Greg ,
> Some
>
>
> On 02/18/11 11:15, Greg Mirsky wrote:
> > Dear Luca,
> > I see at least two issues:
> >
> >     * use of GAL for PW, in my view, is another VCCV CC type that has
> >       to be negotiated as described in RFC 5085.
> >
>
> These are valid points, but this document in question does not define,
> not discussed VCCV.
> We have since posted a draft that proposes a new VCCV mode , and we
> welcome comments regarding that document.
> (draft-nadeau-pwe3-vccv-2-01.txt)
>
> >     * use of GAL creates ambiguous situation when PW CW is used. The
>
> >       benefit from extending GAL in PW, as I see, is for PWs that are
> >       not required to use PW CW. That might be a good enough reason to
> >       update RFC 5586 as proposed in the document but we must address
> >       use cases of GAL in PWs that require presence PW CW. If we
> >       prohibit or even discourage use of GAL for these PWs that have
> >       PW VCCV as native Associated Channel, then architecture of ACh
> >       for MPLS-TP PW not simplified as result of adopting the proposal.
> >
> > Regard
>
> Greg,
> The GAL is basically a notifier that the packet following the end of the
> MPLS label stack, is explicitly defined as a G-ACH format.
> Normally the packet would be decoded as an IP packet , unless the last
> label on the stack indicated otherwise.
>
> The GAL can certainly be applied  to a PW OAM packet on a PW that uses
> the CW, and this document does not define that , nor restricts it.
>
> The scope of this document is limited to removing an unnecessary
> restriction in rfc5586, hence  this comment not applicable to this 
> document.
>
> Thanks.
> Luca
>
>
> > s,
> > Greg
> >
> > On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com 
> <mailto:lmartini@cisco.com>
>
> > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>> wrote:
> >
> >     Greg,
> >
> >     Sorry, but I do not remember the point you mention.
> >     Can you explain again here ?
> >     Thanks.
> >     Luca
> >
> >
> >     On 02/17/11 23:47, Greg Mirsky wrote:
> > > Dear Authors and All,
> > > prior to the meeting in Bejing and acceptance of this proposal as WG
> > > document Luca and I agreed that use of GAL with PW VCCV presents a
> > > problem.
> > > I was not attending the IETF-79, nor I found discussion of this
> >     issue
> > > in the minutes. I think that this issue should be specified,
> > > explained. In my view, this document updates not only RFC 5586
> > > but RFC 5085 too.
> > >
> > > Regards,
> > > Greg
> > >
> > > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> > >
> > > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
> > <lmartini@cisco.com <mailto:lmartini@cisco.com> 
> <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>
>
> > > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com> 
> <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>>> wrote:
> > >
> > >     Greg,
> > >
> > >     You are correct , the proposed update does not propose any
> >     changes
> > >     to VCCV.
> > >     However the problem with vccv is not as simple as to ask for
> >     a new
> > >     code point from IANA.
> > >     Given the good amount of discussion on this point, we should
> > >     probably have a discussion in Beijing.
> > >
> > >     Luca
> > >
> > >
> > >
> > >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
> > >>     Dear Authors,
> > >>     I think that proposed update of the Section 4.2. RFC 5586
> >     makes it possible
> > >>     to use GAL on MPLS-TP PW that uses Control Word. I consider
> >     it to be
> > >>     conflict between PW VCCV CC types because use of GAL is not
> >     negotiated
> > >>     through PW VCCV negotiation. To avoid such situation I propose:
> > >>
> > >>        - in Section 5 request IANA to assign new CC Type "MPLS
> >     Generic
> > >>        Associated Channel Label"
> > >>        - assign precedence to new CC Type that affects Section
> >     7 RFC 5085
> > >>
> > >>     Regards,
> > >>     Greg
> > >>
> > >>
> > >>
> > >>     _______________________________________________
> > >>     mpls mailing list
>
> > >> mpls@ietf.org <mailto:mpls@ietf.org> <mailto:mpls@ietf.org 
> <mailto:mpls@ietf.org>> <mailto:mpls@ietf.org <mailto:mpls@ietf.org>
>
> > <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>>
> > >> https://www.ietf.org/mailman/listinfo/mpls
> > >
> > >
> > >
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org <mailto:mpls@ietf.org> <mailto:mpls@ietf.org 
> <mailto:mpls@ietf.org>>
> > > https://www.ietf.org/mailman/listinfo/mpls
> >
> >
>
>
> _______________________________________________
> 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



--------------050303000603040509070000
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 text="#000000" bgcolor="#ffffff">
    If there is IETF consensus to update RFC5586 with this change then
    the process is relatively simple:<br>
    <br>
    The document making the update notes that it does the update, and
    the AD draws attention to<br>
    this in the IETF LC.<br>
    <br>
    Stewart<br>
    <br>
    <br>
    <br>
    On 22/03/2011 16:22, Robert Rennison wrote:
    <blockquote
cite="mid:786AD2EC3D80A1428B921CDC9BE9EE546569F9F8E1@USPITMAIL01.ecitele.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <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;}
/* 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.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
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;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1278948757;
	mso-list-template-ids:-1227977334;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1800680213;
	mso-list-template-ids:-512447670;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	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="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);">Luca, Thomas,<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);">A couple of clarification questions.<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);">I&#8217;m trying to understand what the combination of
            the two drafts, </span><span style="font-size: 11pt;
            font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;
            color: rgb(31, 73, 125);">-lm-pwe3-mpls-tp-gal-in-pw, and
            draft-nadeau-pwe3-vccv-2</span><span style="font-size: 11pt;
            font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;
            color: rgb(31, 73, 125);"> amounts to.<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);">So, I think I understood the </span><span
            style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">draft-nadeau-pwe3-vccv-2 in that it&#8217;s saying use
            VCCV type 1 where possible and if not then use the new type
            4, whereby &nbsp;in type 4 the exception mechanism is triggered
            by the use of the GAL, &nbsp;and I appreciated the diagram in
            section 3 to lock this is, so far so good.<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);">Now I read -pwe3-mpls-tp-gal-in-pw and I&#8217;m
            thinking , Ok these two drafts could work together since
            this one is trying to lay the &#8220;legal framework&#8221; i.e fix up
            the RFCs which mandated that the GAL could not be used with
            the PW. <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);">Then I get hit with a brick wall in the form of
            the statements in the last 2 paras of section 3 of
            tp-gal-in-pw which state.<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" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">-
            <a moz-do-not-send="true"
href="http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2">Section
              4.2</a>. (GAL Applicability and Usage) in [<a
              moz-do-not-send="true"
              href="http://tools.ietf.org/html/rfc5586"
              title="&quot;MPLS Generic Associated Channel&quot;">RFC5586</a>],
            the<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            original text:<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            In MPLS-TP, the GAL MUST be used with packets on a G-ACh on<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            LSPs, Concatenated Segments of LSPs, and with Sections, and<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            MUST NOT be used with PWs. It MUST always be at the bottom
            of<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            the label stack (i.e., S bit set to 1). However, in other
            MPLS<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            environments, this document places no restrictions on where<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            the GAL may appear within the label stack or its use with
            PWs.<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            is replaced by:<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            In MPLS-TP, the GAL MUST be used with packets on a G-ACh on<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            LSPs, Concatenated Segments of LSPs, and with Sections, and<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            MAY be used with PWs. It MUST always be at the bottom of the<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            label stack (i.e., S bit set to 1). However, in other MPLS<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            environments, this document places no restrictions on where<o:p></o:p></span></p>
        <p class="MsoNormal" style="page-break-before: always;"><span
            style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            the GAL may appear within the label stack.<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);"><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);">It&#8217;s the bit about the GAL MUST be at the bottom
            of the label stack,&nbsp; this is clearly inconsistent with what
            is proposed in the draft-nadeau-pwe3 where one can clearly
            see the GAL above the PW label and if one has to use&nbsp; a GAL
            with a PW this would be the place to put it,<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);">Now I can hear you saying &#8220;oh but look at the
            text below this, where we state ..&#8221;However, in other MPLS
            environments , this document places no restrictions on where
            the GAL may appear within the label stack. This is
            consistent with draft-nadeau &#8220;&nbsp; &nbsp;In which case I&#8217;d retort
            with ; what are we to do for PWs in &nbsp;&nbsp;MPLS-TP, since what&#8217;s
            in draft-nadeau would not be allowed ?<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);">Clarification /explanation appreciated. <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);">Cheers<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);">Rob Rennison<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);"><o:p>&nbsp;</o:p></span></p>
        <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>Alexander Vainshtein<br>
                <b>Sent:</b> Friday, March 11, 2011 2:22 PM<br>
                <b>To:</b> Greg Mirsky; Luca Martini<br>
                <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:lihan@chinamobile.com">lihan@chinamobile.com</a>; <a class="moz-txt-link-abbreviated" href="mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a>;
                pwe3; HUANG Feng F; <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
                <b>Subject:</b> Re: [mpls] WG LC
                draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<o:p></o:p></span></p>
          </div>
        </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);">Greg, Luca,<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);">As I&#8217;ve already stated in my comment on
            draft-nadeau-pwe3-vccv-2, IMHO it makes
            draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.<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);">My 2c,<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);">&nbsp;&nbsp;&nbsp;&nbsp; Sasha<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>Greg Mirsky<br>
                  <b>Sent:</b> Friday, March 11, 2011 9:14 PM<br>
                  <b>To:</b> Luca Martini<br>
                  <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:lihan@chinamobile.com">lihan@chinamobile.com</a>; <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a>; pwe3;
                  HUANG Feng F; <a class="moz-txt-link-abbreviated" href="mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a><br>
                  <b>Subject:</b> Re: [mpls] WG LC
                  draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          <p class="MsoNormal">Dear Luca,<br>
            thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my
            attention. I'll send my comments to it in a separate e-mail.<br>
            I'll have to miss another opportunity to discuss your
            proposal in a meeting. Please add my comments below to my
            earlier expressed WG LC comments:<o:p></o:p></p>
          <ul type="disc">
            <li class="MsoNormal" style="">the
              draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution
              that addresses applicability of GAL in PW VCCV, e.g.
              solution proposed in draft-nadeau-pwe3-vccv-2-01;<o:p></o:p></li>
            <li class="MsoNormal" style="">the
              draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such
              dependency and refer to any existing proposal;<o:p></o:p></li>
            <li class="MsoNormal" style="">I believe that the
              draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced in lock
              with document that addresses use of GAL in PW VCCV.<o:p></o:p></li>
          </ul>
          <p class="MsoNormal" style="margin-bottom: 12pt;">Regards,<br>
            Greg<o:p></o:p></p>
          <div>
            <p class="MsoNormal">On Fri, Mar 11, 2011 at 5:31 AM, Luca
              Martini &lt;<a moz-do-not-send="true"
                href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;
              wrote:<o:p></o:p></p>
            <p class="MsoNormal">Greg ,<br>
              Some<o:p></o:p></p>
            <div>
              <p class="MsoNormal"><br>
                On 02/18/11 11:15, Greg Mirsky wrote:<br>
                &gt; Dear Luca,<br>
                &gt; I see at least two issues:<br>
                &gt;<br>
                &gt; &nbsp; &nbsp; * use of GAL for PW, in my view, is another
                VCCV CC type that has<br>
                &gt; &nbsp; &nbsp; &nbsp; to be negotiated as described in RFC 5085.<br>
                &gt;<o:p></o:p></p>
            </div>
            <p class="MsoNormal">These are valid points, but this
              document in question does not define,<br>
              not discussed VCCV.<br>
              We have since posted a draft that proposes a new VCCV mode
              , and we<br>
              welcome comments regarding that document.<br>
              (draft-nadeau-pwe3-vccv-2-01.txt)<br>
              <br>
              &gt; &nbsp; &nbsp; * use of GAL creates ambiguous situation when PW
              CW is used. The<o:p></o:p></p>
            <div>
              <p class="MsoNormal">&gt; &nbsp; &nbsp; &nbsp; benefit from extending GAL
                in PW, as I see, is for PWs that are<br>
                &gt; &nbsp; &nbsp; &nbsp; not required to use PW CW. That might be a
                good enough reason to<br>
                &gt; &nbsp; &nbsp; &nbsp; update RFC 5586 as proposed in the document
                but we must address<br>
                &gt; &nbsp; &nbsp; &nbsp; use cases of GAL in PWs that require presence
                PW CW. If we<br>
                &gt; &nbsp; &nbsp; &nbsp; prohibit or even discourage use of GAL for
                these PWs that have<br>
                &gt; &nbsp; &nbsp; &nbsp; PW VCCV as native Associated Channel, then
                architecture of ACh<br>
                &gt; &nbsp; &nbsp; &nbsp; for MPLS-TP PW not simplified as result of
                adopting the proposal.<br>
                &gt;<br>
                &gt; Regard<o:p></o:p></p>
            </div>
            <p class="MsoNormal">Greg,<br>
              The GAL is basically a notifier that the packet following
              the end of the<br>
              MPLS label stack, is explicitly defined as a G-ACH format.<br>
              Normally the packet would be decoded as an IP packet ,
              unless the last<br>
              label on the stack indicated otherwise.<br>
              <br>
              The GAL can certainly be applied &nbsp;to a PW OAM packet on a
              PW that uses<br>
              the CW, and this document does not define that , nor
              restricts it.<br>
              <br>
              The scope of this document is limited to removing an
              unnecessary<br>
              restriction in rfc5586, hence &nbsp;this comment not applicable
              to this document.<br>
              <br>
              Thanks.<br>
              Luca<o:p></o:p></p>
            <div>
              <p class="MsoNormal"><br>
                &gt; s,<br>
                &gt; Greg<br>
                &gt;<br>
                &gt; On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini &lt;<a
                  moz-do-not-send="true"
                  href="mailto:lmartini@cisco.com">lmartini@cisco.com</a><o:p></o:p></p>
            </div>
            <div>
              <p class="MsoNormal">&gt; &lt;mailto:<a
                  moz-do-not-send="true"
                  href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;&gt;
                wrote:<br>
                &gt;<br>
                &gt; &nbsp; &nbsp; Greg,<br>
                &gt;<br>
                &gt; &nbsp; &nbsp; Sorry, but I do not remember the point you
                mention.<br>
                &gt; &nbsp; &nbsp; Can you explain again here ?<br>
                &gt; &nbsp; &nbsp; Thanks.<br>
                &gt; &nbsp; &nbsp; Luca<br>
                &gt;<br>
                &gt;<br>
                &gt; &nbsp; &nbsp; On 02/17/11 23:47, Greg Mirsky wrote:<br>
                &gt; &nbsp; &nbsp; &gt; Dear Authors and All,<br>
                &gt; &nbsp; &nbsp; &gt; prior to the meeting in Bejing and
                acceptance of this proposal as WG<br>
                &gt; &nbsp; &nbsp; &gt; document Luca and I agreed that use of GAL
                with PW VCCV presents a<br>
                &gt; &nbsp; &nbsp; &gt; problem.<br>
                &gt; &nbsp; &nbsp; &gt; I was not attending the IETF-79, nor I
                found discussion of this<br>
                &gt; &nbsp; &nbsp; issue<br>
                &gt; &nbsp; &nbsp; &gt; in the minutes. I think that this issue
                should be specified,<br>
                &gt; &nbsp; &nbsp; &gt; explained. In my view, this document
                updates not only RFC 5586<br>
                &gt; &nbsp; &nbsp; &gt; but RFC 5085 too.<br>
                &gt; &nbsp; &nbsp; &gt;<br>
                &gt; &nbsp; &nbsp; &gt; Regards,<br>
                &gt; &nbsp; &nbsp; &gt; Greg<br>
                &gt; &nbsp; &nbsp; &gt;<br>
                &gt; &nbsp; &nbsp; &gt; Comment to
                draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br>
                &gt; &nbsp; &nbsp; &gt;<br>
                &gt; &nbsp; &nbsp; &gt; On Sat, Oct 30, 2010 at 10:14 AM, Luca
                Martini<br>
                &gt; &nbsp; &nbsp; &lt;<a moz-do-not-send="true"
                  href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>
                &lt;mailto:<a moz-do-not-send="true"
                  href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;<o:p></o:p></p>
            </div>
            <div>
              <div>
                <p class="MsoNormal">&gt; &nbsp; &nbsp; &gt; &lt;mailto:<a
                    moz-do-not-send="true"
                    href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>
                  &lt;mailto:<a moz-do-not-send="true"
                    href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;&gt;&gt;
                  wrote:<br>
                  &gt; &nbsp; &nbsp; &gt;<br>
                  &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Greg,<br>
                  &gt; &nbsp; &nbsp; &gt;<br>
                  &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; You are correct , the proposed
                  update does not propose any<br>
                  &gt; &nbsp; &nbsp; changes<br>
                  &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; to VCCV.<br>
                  &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; However the problem with vccv is not
                  as simple as to ask for<br>
                  &gt; &nbsp; &nbsp; a new<br>
                  &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; code point from IANA.<br>
                  &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Given the good amount of discussion
                  on this point, we should<br>
                  &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; probably have a discussion in
                  Beijing.<br>
                  &gt; &nbsp; &nbsp; &gt;<br>
                  &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Luca<br>
                  &gt; &nbsp; &nbsp; &gt;<br>
                  &gt; &nbsp; &nbsp; &gt;<br>
                  &gt; &nbsp; &nbsp; &gt;<br>
                  &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; On 10/29/2010 05:07 PM, Greg Mirsky
                  wrote:<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Dear Authors,<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; I think that proposed update of
                  the Section 4.2. RFC 5586<br>
                  &gt; &nbsp; &nbsp; makes it possible<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; to use GAL on MPLS-TP PW that
                  uses Control Word. I consider<br>
                  &gt; &nbsp; &nbsp; it to be<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; conflict between PW VCCV CC
                  types because use of GAL is not<br>
                  &gt; &nbsp; &nbsp; negotiated<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; through PW VCCV negotiation. To
                  avoid such situation I propose:<br>
                  &gt; &nbsp; &nbsp; &gt;&gt;<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;- in Section 5 request IANA
                  to assign new CC Type "MPLS<br>
                  &gt; &nbsp; &nbsp; Generic<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;Associated Channel Label"<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;- assign precedence to new CC
                  Type that affects Section<br>
                  &gt; &nbsp; &nbsp; 7 RFC 5085<br>
                  &gt; &nbsp; &nbsp; &gt;&gt;<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Regards,<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Greg<br>
                  &gt; &nbsp; &nbsp; &gt;&gt;<br>
                  &gt; &nbsp; &nbsp; &gt;&gt;<br>
                  &gt; &nbsp; &nbsp; &gt;&gt;<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp;
                  _______________________________________________<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; mpls mailing list<o:p></o:p></p>
              </div>
            </div>
            <p class="MsoNormal">&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; <a
                moz-do-not-send="true" href="mailto:mpls@ietf.org">mpls@ietf.org</a>
              &lt;mailto:<a moz-do-not-send="true"
                href="mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;
              &lt;mailto:<a moz-do-not-send="true"
                href="mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></p>
            <div>
              <div>
                <p class="MsoNormal" style="margin-bottom: 12pt;">&gt; &nbsp;
                  &nbsp; &lt;mailto:<a moz-do-not-send="true"
                    href="mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;&gt;<br>
                  &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; <a moz-do-not-send="true"
                    href="https://www.ietf.org/mailman/listinfo/mpls"
                    target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>
                  &gt; &nbsp; &nbsp; &gt;<br>
                  &gt; &nbsp; &nbsp; &gt;<br>
                  &gt; &nbsp; &nbsp; &gt;<br>
                  &gt; &nbsp; &nbsp; &gt;
                  _______________________________________________<br>
                  &gt; &nbsp; &nbsp; &gt; mpls mailing list<br>
                  &gt; &nbsp; &nbsp; &gt; <a moz-do-not-send="true"
                    href="mailto:mpls@ietf.org">mpls@ietf.org</a>
                  &lt;mailto:<a moz-do-not-send="true"
                    href="mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<br>
                  &gt; &nbsp; &nbsp; &gt; <a moz-do-not-send="true"
                    href="https://www.ietf.org/mailman/listinfo/mpls"
                    target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>
                  &gt;<br>
                  &gt;<o:p></o:p></p>
              </div>
            </div>
          </div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </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>

--------------050303000603040509070000--

From curtis@occnc.com  Wed Mar 23 13:24:26 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12AC328C0F1 for <pwe3@core3.amsl.com>; Wed, 23 Mar 2011 13:24: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=[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 6fcB3HaT-NSJ for <pwe3@core3.amsl.com>; Wed, 23 Mar 2011 13:24:22 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 8BDDE3A68D5 for <pwe3@ietf.org>; Wed, 23 Mar 2011 13:24: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 p2NKPr2t076600; Wed, 23 Mar 2011 16:25:53 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103232025.p2NKPr2t076600@harbor.orleans.occnc.com>
To: stbryant@cisco.com
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Tue, 22 Mar 2011 18:00:07 -0000." <4D88E3A7.4040502@cisco.com> 
Date: Wed, 23 Mar 2011 16:25:53 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, Robert Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2011 20:24:26 -0000

In message <4D88E3A7.4040502@cisco.com>
Stewart Bryant writes:
>  
> If there is IETF consensus to update RFC5586 with this change then the 
> process is relatively simple:
>  
> The document making the update notes that it does the update, and the AD 
> draws attention to
> this in the IETF LC.
>  
> Stewart


Stewart,

The restriction that GAL be at the bottom of stack was simply a
mistake IMHO.  I stated that during MPLS WG discussion before it
became an RFC but it went through as is anyway with that restriction.
Even then it was said that if there were a strong reason to relax it
that it could be considered later.  That time may have come.

There are a number of reasons that labels might want to go below GAL,
including to use OAM to diagnose the connectivity (or lack of) that is
experienced only for a specific label stack combinations where
multipath (link bundle, LAG, less applicable is ECMP in this case) is
used.

In this case though, the GAL under the LSP label currently indicates
that after the POP that OAM needs to be done (or more accurately that
a G-Ach of some type is being carried).  If the GAL is put above the
PW label it is in that same place and there is an ambiguity.  It is an
ambiguity that for some but not all defined OAM can be resolved by
looking at information in BFD that makes it unambiguous.  Unless I'm
mistaken, in CC/CV the label stack above GAL provides the context.

Another solution would be to put GAL under the PW label.  It would
probably be best to put GAL under PW but over the fat-pw label.  The
PW implementation, seeing the PW was not BOS, could look at the next
label to see if the label is reserved and specifically if it is GAL,
and if not process as payload (unless CW is also used).  If CW was not
used the only advantage is 4 bytes less in payload but the same size
in OAM packets.  This is an advantage though.

On a related topic, if we must put ELI plus entropy label on the stack
we have saved nothing relative to fat-pw plus CW.  ELI as a
termination of hash search may have other uses though (MPLS-TP).

I would be in favor of a very short draft just relaxing the
requirement that GAL be at the bottom of stack, independent of the
reason for doing so, since a number of reasons have emerged.  The
behavior would be to throw away the rest of the label stack when the
GAL label is exposed and look at the MPLS payload interpreting it as
an G-Ach channel (most often, but not exclusively, as OAM).  This
relaxation of the BOS restriction would be independent of usage.

Curtis


> On 22/03/2011 16:22, Robert Rennison wrote:
> >
> > Luca, Thomas,
> >
> > A couple of clarification questions.
> >
> > I'm trying to understand what the combination of the two drafts, 
> > -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts to.
> >
> > So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it's 
> > saying use VCCV type 1 where possible and if not then use the new type 
> > 4, whereby  in type 4 the exception mechanism is triggered by the use 
> > of the GAL,  and I appreciated the diagram in section 3 to lock this 
> > is, so far so good.
> >
> > Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these two 
> > drafts could work together since this one is trying to lay the "legal 
> > framework" i.e fix up the RFCs which mandated that the GAL could not 
> > be used with the PW.
> >
> > Then I get hit with a brick wall in the form of the statements in the 
> > last 2 paras of section 3 of tp-gal-in-pw which state.
> >
> > - Section 4.2 
> > <http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2>. 
> > (GAL Applicability and Usage) in [RFC5586 
> > <http://tools.ietf.org/html/rfc5586>], the
> >
> >       original text:
> >
> >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> >
> >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> >
> >           MUST NOT be used with PWs. It MUST always be at the bottom of
> >
> >           the label stack (i.e., S bit set to 1). However, in other MPLS
> >
> >           environments, this document places no restrictions on where
> >
> >           the GAL may appear within the label stack or its use with PWs.
> >
> >       is replaced by:
> >
> >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> >
> >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> >
> >           MAY be used with PWs. It MUST always be at the bottom of the
> >
> >           label stack (i.e., S bit set to 1). However, in other MPLS
> >
> >           environments, this document places no restrictions on where
> >
> >           the GAL may appear within the label stack.
> >
> > It's the bit about the GAL MUST be at the bottom of the label stack,  
> > this is clearly inconsistent with what is proposed in the 
> > draft-nadeau-pwe3 where one can clearly see the GAL above the PW label 
> > and if one has to use  a GAL with a PW this would be the place to put it,
> >
> > Now I can hear you saying "oh but look at the text below this, where 
> > we state .."However, in other MPLS environments , this document places 
> > no restrictions on where the GAL may appear within the label stack. 
> > This is consistent with draft-nadeau "   In which case I'd retort with 
> > ; what are we to do for PWs in   MPLS-TP, since what's in draft-nadeau 
> > would not be allowed ?
> >
> > Clarification /explanation appreciated.
> >
> > Cheers
> >
> > Rob Rennison
> >
> > *From:*mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] *On Behalf 
> > Of *Alexander Vainshtein
> > *Sent:* Friday, March 11, 2011 2:22 PM
> > *To:* Greg Mirsky; Luca Martini
> > *Cc:* lihan@chinamobile.com; mpls-tp@ietf.org; pwe3; HUANG Feng F; 
> > mpls@ietf.org
> > *Subject:* Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> >
> > Greg, Luca,
> >
> > As I've already stated in my comment on draft-nadeau-pwe3-vccv-2, IMHO 
> > it makes draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.
> >
> > My 2c,
> >
> >      Sasha
> >
> > *From:*mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] *On Behalf 
> > Of *Greg Mirsky
> > *Sent:* Friday, March 11, 2011 9:14 PM
> > *To:* Luca Martini
> > *Cc:* lihan@chinamobile.com; mpls@ietf.org; pwe3; HUANG Feng F; 
> > mpls-tp@ietf.org
> > *Subject:* Re: [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> >
> > Dear Luca,
> > thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my attention. 
> > I'll send my comments to it in a separate e-mail.
> > I'll have to miss another opportunity to discuss your proposal in a 
> > meeting. Please add my comments below to my earlier expressed WG LC 
> > comments:
> >
> >     * the draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution
> >       that addresses applicability of GAL in PW VCCV, e.g. solution
> >       proposed in draft-nadeau-pwe3-vccv-2-01;
> >     * the draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such
> >       dependency and refer to any existing proposal;
> >     * I believe that the draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be
> >       advanced in lock with document that addresses use of GAL in PW VCCV.
> >
> > Regards,
> > Greg
> >
> > On Fri, Mar 11, 2011 at 5:31 AM, Luca Martini <lmartini@cisco.com 
> > <mailto:lmartini@cisco.com>> wrote:
> >
> > Greg ,
> > Some
> >
> >
> > On 02/18/11 11:15, Greg Mirsky wrote:
> > > Dear Luca,
> > > I see at least two issues:
> > >
> > >     * use of GAL for PW, in my view, is another VCCV CC type that has
> > >       to be negotiated as described in RFC 5085.
> > >
> >
> > These are valid points, but this document in question does not define,
> > not discussed VCCV.
> > We have since posted a draft that proposes a new VCCV mode , and we
> > welcome comments regarding that document.
> > (draft-nadeau-pwe3-vccv-2-01.txt)
> >
> > >     * use of GAL creates ambiguous situation when PW CW is used. The
> >
> > >       benefit from extending GAL in PW, as I see, is for PWs that are
> > >       not required to use PW CW. That might be a good enough reason to
> > >       update RFC 5586 as proposed in the document but we must address
> > >       use cases of GAL in PWs that require presence PW CW. If we
> > >       prohibit or even discourage use of GAL for these PWs that have
> > >       PW VCCV as native Associated Channel, then architecture of ACh
> > >       for MPLS-TP PW not simplified as result of adopting the proposal.
> > >
> > > Regard
> >
> > Greg,
> > The GAL is basically a notifier that the packet following the end of the
> > MPLS label stack, is explicitly defined as a G-ACH format.
> > Normally the packet would be decoded as an IP packet , unless the last
> > label on the stack indicated otherwise.
> >
> > The GAL can certainly be applied  to a PW OAM packet on a PW that uses
> > the CW, and this document does not define that , nor restricts it.
> >
> > The scope of this document is limited to removing an unnecessary
> > restriction in rfc5586, hence  this comment not applicable to this 
> > document.
> >
> > Thanks.
> > Luca
> >
> >
> > > s,
> > > Greg
> > >
> > > On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini <lmartini@cisco.com 
> > <mailto:lmartini@cisco.com>
> >
> > > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>> wrote:
> > >
> > >     Greg,
> > >
> > >     Sorry, but I do not remember the point you mention.
> > >     Can you explain again here ?
> > >     Thanks.
> > >     Luca
> > >
> > >
> > >     On 02/17/11 23:47, Greg Mirsky wrote:
> > > > Dear Authors and All,
> > > > prior to the meeting in Bejing and acceptance of this proposal as WG
> > > > document Luca and I agreed that use of GAL with PW VCCV presents a
> > > > problem.
> > > > I was not attending the IETF-79, nor I found discussion of this
> > >     issue
> > > > in the minutes. I think that this issue should be specified,
> > > > explained. In my view, this document updates not only RFC 5586
> > > > but RFC 5085 too.
> > > >
> > > > Regards,
> > > > Greg
> > > >
> > > > Comment to draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
> > > >
> > > > On Sat, Oct 30, 2010 at 10:14 AM, Luca Martini
> > > <lmartini@cisco.com <mailto:lmartini@cisco.com> 
> > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>
> >
> > > > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com> 
> > <mailto:lmartini@cisco.com <mailto:lmartini@cisco.com>>>> wrote:
> > > >
> > > >     Greg,
> > > >
> > > >     You are correct , the proposed update does not propose any
> > >     changes
> > > >     to VCCV.
> > > >     However the problem with vccv is not as simple as to ask for
> > >     a new
> > > >     code point from IANA.
> > > >     Given the good amount of discussion on this point, we should
> > > >     probably have a discussion in Beijing.
> > > >
> > > >     Luca
> > > >
> > > >
> > > >
> > > >     On 10/29/2010 05:07 PM, Greg Mirsky wrote:
> > > >>     Dear Authors,
> > > >>     I think that proposed update of the Section 4.2. RFC 5586
> > >     makes it possible
> > > >>     to use GAL on MPLS-TP PW that uses Control Word. I consider
> > >     it to be
> > > >>     conflict between PW VCCV CC types because use of GAL is not
> > >     negotiated
> > > >>     through PW VCCV negotiation. To avoid such situation I propose:
> > > >>
> > > >>        - in Section 5 request IANA to assign new CC Type "MPLS
> > >     Generic
> > > >>        Associated Channel Label"
> > > >>        - assign precedence to new CC Type that affects Section
> > >     7 RFC 5085
> > > >>
> > > >>     Regards,
> > > >>     Greg
> > > >>
> > > >>
> > > >>
> > > >>     _______________________________________________
> > > >>     mpls mailing list
> >
> > > >> mpls@ietf.org <mailto:mpls@ietf.org> <mailto:mpls@ietf.org 
> > <mailto:mpls@ietf.org>> <mailto:mpls@ietf.org <mailto:mpls@ietf.org>
> >
> > > <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>>
> > > >> https://www.ietf.org/mailman/listinfo/mpls
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > mpls mailing list
> > > > mpls@ietf.org <mailto:mpls@ietf.org> <mailto:mpls@ietf.org 
> > <mailto:mpls@ietf.org>>
> > > > https://www.ietf.org/mailman/listinfo/mpls
> > >
> > >
> >
> >
> > _______________________________________________
> > 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
>  
>  
>  
> --------------050303000603040509070000
> 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 text="#000000" bgcolor="#ffffff">
>     If there is IETF consensus to update RFC5586 with this change then
>     the process is relatively simple:<br>
>     <br>
>     The document making the update notes that it does the update, and
>     the AD draws attention to<br>
>     this in the IETF LC.<br>
>     <br>
>     Stewart<br>
>     <br>
>     <br>
>     <br>
>     On 22/03/2011 16:22, Robert Rennison wrote:
>     <blockquote
> cite="mid:786AD2EC3D80A1428B921CDC9BE9EE546569F9F8E1@USPITMAIL01.ecitele.com"
>       type="cite">
>       <meta http-equiv="Content-Type" content="text/html;
>         charset=ISO-8859-1">
>       <meta name="Generator" content="Microsoft Word 12 (filtered
>         medium)">
>       <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;}
> /* 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.EmailStyle17
> 	{mso-style-type:personal;
> 	font-family:"Calibri","sans-serif";
> 	color:#1F497D;}
> 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;
> 	font-size:10.0pt;}
> @page WordSection1
> 	{size:8.5in 11.0in;
> 	margin:1.0in 1.25in 1.0in 1.25in;}
> div.WordSection1
> 	{page:WordSection1;}
> /* List Definitions */
> @list l0
> 	{mso-list-id:1278948757;
> 	mso-list-template-ids:-1227977334;}
> @list l0:level1
> 	{mso-level-number-format:bullet;
> 	mso-level-text:\F0B7;
> 	mso-level-tab-stop:.5in;
> 	mso-level-number-position:left;
> 	text-indent:-.25in;
> 	mso-ansi-font-size:10.0pt;
> 	font-family:Symbol;}
> @list l1
> 	{mso-list-id:1800680213;
> 	mso-list-template-ids:-512447670;}
> @list l1:level1
> 	{mso-level-number-format:bullet;
> 	mso-level-text:\F0B7;
> 	mso-level-tab-stop:.5in;
> 	mso-level-number-position:left;
> 	text-indent:-.25in;
> 	mso-ansi-font-size:10.0pt;
> 	font-family:Symbol;}
> @list l1:level2
> 	{mso-level-tab-stop:1.0in;
> 	mso-level-number-position:left;
> 	text-indent:-.25in;}
> @list l1:level3
> 	{mso-level-tab-stop:1.5in;
> 	mso-level-number-position:left;
> 	text-indent:-.25in;}
> @list l1:level4
> 	{mso-level-tab-stop:2.0in;
> 	mso-level-number-position:left;
> 	text-indent:-.25in;}
> @list l1:level5
> 	{mso-level-tab-stop:2.5in;
> 	mso-level-number-position:left;
> 	text-indent:-.25in;}
> @list l1:level6
> 	{mso-level-tab-stop:3.0in;
> 	mso-level-number-position:left;
> 	text-indent:-.25in;}
> @list l1:level7
> 	{mso-level-tab-stop:3.5in;
> 	mso-level-number-position:left;
> 	text-indent:-.25in;}
> @list l1:level8
> 	{mso-level-tab-stop:4.0in;
> 	mso-level-number-position:left;
> 	text-indent:-.25in;}
> @list l1:level9
> 	{mso-level-tab-stop:4.5in;
> 	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="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);">Luca, Thomas,<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);">A couple of clarification questions.<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);">I&#8217;m trying to understand what the combination of
>             the two drafts, </span><span style="font-size: 11pt;
>             font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;
>             color: rgb(31, 73, 125);">-lm-pwe3-mpls-tp-gal-in-pw, and
>             draft-nadeau-pwe3-vccv-2</span><span style="font-size: 11pt;
>             font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;
>             color: rgb(31, 73, 125);"> amounts to.<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);">So, I think I understood the </span><span
>             style="font-size: 11pt; font-family:
>             &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
>             73, 125);">draft-nadeau-pwe3-vccv-2 in that it&#8217;s saying use
>             VCCV type 1 where possible and if not then use the new type
>             4, whereby &nbsp;in type 4 the exception mechanism is triggered
>             by the use of the GAL, &nbsp;and I appreciated the diagram in
>             section 3 to lock this is, so far so good.<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);">Now I read -pwe3-mpls-tp-gal-in-pw and I&#8217;m
>             thinking , Ok these two drafts could work together since
>             this one is trying to lay the &#8220;legal framework&#8221; i.e fix up
>             the RFCs which mandated that the GAL could not be used with
>             the PW. <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);">Then I get hit with a brick wall in the form of
>             the statements in the last 2 paras of section 3 of
>             tp-gal-in-pw which state.<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" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">-
>             <a moz-do-not-send="true"
> href="http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2">Section
>               4.2</a>. (GAL Applicability and Usage) in [<a
>               moz-do-not-send="true"
>               href="http://tools.ietf.org/html/rfc5586"
>               title="&quot;MPLS Generic Associated Channel&quot;">RFC5586</a>],
>             the<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             original text:<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;"><o:p>&nbsp;</o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             In MPLS-TP, the GAL MUST be used with packets on a G-ACh on<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             LSPs, Concatenated Segments of LSPs, and with Sections, and<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             MUST NOT be used with PWs. It MUST always be at the bottom
>             of<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             the label stack (i.e., S bit set to 1). However, in other
>             MPLS<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             environments, this document places no restrictions on where<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             the GAL may appear within the label stack or its use with
>             PWs.<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;"><o:p>&nbsp;</o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             is replaced by:<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;"><o:p>&nbsp;</o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             In MPLS-TP, the GAL MUST be used with packets on a G-ACh on<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             LSPs, Concatenated Segments of LSPs, and with Sections, and<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             MAY be used with PWs. It MUST always be at the bottom of the<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             label stack (i.e., S bit set to 1). However, in other MPLS<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             environments, this document places no restrictions on where<o:p></o:p></span></p>
>         <p class="MsoNormal" style="page-break-before: always;"><span
>             style="font-family: &quot;Courier New&quot;; color: black;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>             the GAL may appear within the label stack.<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);"><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);">It&#8217;s the bit about the GAL MUST be at the bottom
>             of the label stack,&nbsp; this is clearly inconsistent with what
>             is proposed in the draft-nadeau-pwe3 where one can clearly
>             see the GAL above the PW label and if one has to use&nbsp; a GAL
>             with a PW this would be the place to put it,<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);">Now I can hear you saying &#8220;oh but look at the
>             text below this, where we state ..&#8221;However, in other MPLS
>             environments , this document places no restrictions on where
>             the GAL may appear within the label stack. This is
>             consistent with draft-nadeau &#8220;&nbsp; &nbsp;In which case I&#8217;d retort
>             with ; what are we to do for PWs in &nbsp;&nbsp;MPLS-TP, since what&#8217;s
>             in draft-nadeau would not be allowed ?<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);">Clarification /explanation appreciated. <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);">Cheers<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);">Rob Rennison<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);"><o:p>&nbsp;</o:p></span></p>
>         <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>Alexander Vainshtein<br>
>                 <b>Sent:</b> Friday, March 11, 2011 2:22 PM<br>
>                 <b>To:</b> Greg Mirsky; Luca Martini<br>
>                 <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:lihan@chinamobile.com">lihan@chinamobile.com</a>; <a class="moz-txt-link-abbreviated" href="mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a>;
>                 pwe3; HUANG Feng F; <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a><br>
>                 <b>Subject:</b> Re: [mpls] WG LC
>                 draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<o:p></o:p></span></p>
>           </div>
>         </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);">Greg, Luca,<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);">As I&#8217;ve already stated in my comment on
>             draft-nadeau-pwe3-vccv-2, IMHO it makes
>             draft-lm-pwe3-mpls-tp-gal-in-pw completely useless.<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);">My 2c,<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);">&nbsp;&nbsp;&nbsp;&nbsp; Sasha<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>Greg Mirsky<br>
>                   <b>Sent:</b> Friday, March 11, 2011 9:14 PM<br>
>                   <b>To:</b> Luca Martini<br>
>                   <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:lihan@chinamobile.com">lihan@chinamobile.com</a>; <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a>; pwe3;
>                   HUANG Feng F; <a class="moz-txt-link-abbreviated" href="mailto:mpls-tp@ietf.org">mpls-tp@ietf.org</a><br>
>                   <b>Subject:</b> Re: [mpls] WG LC
>                   draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<o:p></o:p></span></p>
>             </div>
>           </div>
>           <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
>           <p class="MsoNormal">Dear Luca,<br>
>             thank you for bringing draft-nadeau-pwe3-vccv-2-01 to my
>             attention. I'll send my comments to it in a separate e-mail.<br>
>             I'll have to miss another opportunity to discuss your
>             proposal in a meeting. Please add my comments below to my
>             earlier expressed WG LC comments:<o:p></o:p></p>
>           <ul type="disc">
>             <li class="MsoNormal" style="">the
>               draft-lm-pwe3-mpls-tp-gal-in-pw-00 depends on any solution
>               that addresses applicability of GAL in PW VCCV, e.g.
>               solution proposed in draft-nadeau-pwe3-vccv-2-01;<o:p></o:p></li>
>             <li class="MsoNormal" style="">the
>               draft-lm-pwe3-mpls-tp-gal-in-pw-00 needs to mention such
>               dependency and refer to any existing proposal;<o:p></o:p></li>
>             <li class="MsoNormal" style="">I believe that the
>               draft-lm-pwe3-mpls-tp-gal-in-pw-00 can be advanced in lock
>               with document that addresses use of GAL in PW VCCV.<o:p></o:p></li>
>           </ul>
>           <p class="MsoNormal" style="margin-bottom: 12pt;">Regards,<br>
>             Greg<o:p></o:p></p>
>           <div>
>             <p class="MsoNormal">On Fri, Mar 11, 2011 at 5:31 AM, Luca
>               Martini &lt;<a moz-do-not-send="true"
>                 href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;
>               wrote:<o:p></o:p></p>
>             <p class="MsoNormal">Greg ,<br>
>               Some<o:p></o:p></p>
>             <div>
>               <p class="MsoNormal"><br>
>                 On 02/18/11 11:15, Greg Mirsky wrote:<br>
>                 &gt; Dear Luca,<br>
>                 &gt; I see at least two issues:<br>
>                 &gt;<br>
>                 &gt; &nbsp; &nbsp; * use of GAL for PW, in my view, is another
>                 VCCV CC type that has<br>
>                 &gt; &nbsp; &nbsp; &nbsp; to be negotiated as described in RFC 5085.<br>
>                 &gt;<o:p></o:p></p>
>             </div>
>             <p class="MsoNormal">These are valid points, but this
>               document in question does not define,<br>
>               not discussed VCCV.<br>
>               We have since posted a draft that proposes a new VCCV mode
>               , and we<br>
>               welcome comments regarding that document.<br>
>               (draft-nadeau-pwe3-vccv-2-01.txt)<br>
>               <br>
>               &gt; &nbsp; &nbsp; * use of GAL creates ambiguous situation when PW
>               CW is used. The<o:p></o:p></p>
>             <div>
>               <p class="MsoNormal">&gt; &nbsp; &nbsp; &nbsp; benefit from extending GAL
>                 in PW, as I see, is for PWs that are<br>
>                 &gt; &nbsp; &nbsp; &nbsp; not required to use PW CW. That might be a
>                 good enough reason to<br>
>                 &gt; &nbsp; &nbsp; &nbsp; update RFC 5586 as proposed in the document
>                 but we must address<br>
>                 &gt; &nbsp; &nbsp; &nbsp; use cases of GAL in PWs that require presence
>                 PW CW. If we<br>
>                 &gt; &nbsp; &nbsp; &nbsp; prohibit or even discourage use of GAL for
>                 these PWs that have<br>
>                 &gt; &nbsp; &nbsp; &nbsp; PW VCCV as native Associated Channel, then
>                 architecture of ACh<br>
>                 &gt; &nbsp; &nbsp; &nbsp; for MPLS-TP PW not simplified as result of
>                 adopting the proposal.<br>
>                 &gt;<br>
>                 &gt; Regard<o:p></o:p></p>
>             </div>
>             <p class="MsoNormal">Greg,<br>
>               The GAL is basically a notifier that the packet following
>               the end of the<br>
>               MPLS label stack, is explicitly defined as a G-ACH format.<br>
>               Normally the packet would be decoded as an IP packet ,
>               unless the last<br>
>               label on the stack indicated otherwise.<br>
>               <br>
>               The GAL can certainly be applied &nbsp;to a PW OAM packet on a
>               PW that uses<br>
>               the CW, and this document does not define that , nor
>               restricts it.<br>
>               <br>
>               The scope of this document is limited to removing an
>               unnecessary<br>
>               restriction in rfc5586, hence &nbsp;this comment not applicable
>               to this document.<br>
>               <br>
>               Thanks.<br>
>               Luca<o:p></o:p></p>
>             <div>
>               <p class="MsoNormal"><br>
>                 &gt; s,<br>
>                 &gt; Greg<br>
>                 &gt;<br>
>                 &gt; On Fri, Feb 18, 2011 at 7:46 AM, Luca Martini &lt;<a
>                   moz-do-not-send="true"
>                   href="mailto:lmartini@cisco.com">lmartini@cisco.com</a><o:p></o:p></p>
>             </div>
>             <div>
>               <p class="MsoNormal">&gt; &lt;mailto:<a
>                   moz-do-not-send="true"
>                   href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;&gt;
>                 wrote:<br>
>                 &gt;<br>
>                 &gt; &nbsp; &nbsp; Greg,<br>
>                 &gt;<br>
>                 &gt; &nbsp; &nbsp; Sorry, but I do not remember the point you
>                 mention.<br>
>                 &gt; &nbsp; &nbsp; Can you explain again here ?<br>
>                 &gt; &nbsp; &nbsp; Thanks.<br>
>                 &gt; &nbsp; &nbsp; Luca<br>
>                 &gt;<br>
>                 &gt;<br>
>                 &gt; &nbsp; &nbsp; On 02/17/11 23:47, Greg Mirsky wrote:<br>
>                 &gt; &nbsp; &nbsp; &gt; Dear Authors and All,<br>
>                 &gt; &nbsp; &nbsp; &gt; prior to the meeting in Bejing and
>                 acceptance of this proposal as WG<br>
>                 &gt; &nbsp; &nbsp; &gt; document Luca and I agreed that use of GAL
>                 with PW VCCV presents a<br>
>                 &gt; &nbsp; &nbsp; &gt; problem.<br>
>                 &gt; &nbsp; &nbsp; &gt; I was not attending the IETF-79, nor I
>                 found discussion of this<br>
>                 &gt; &nbsp; &nbsp; issue<br>
>                 &gt; &nbsp; &nbsp; &gt; in the minutes. I think that this issue
>                 should be specified,<br>
>                 &gt; &nbsp; &nbsp; &gt; explained. In my view, this document
>                 updates not only RFC 5586<br>
>                 &gt; &nbsp; &nbsp; &gt; but RFC 5085 too.<br>
>                 &gt; &nbsp; &nbsp; &gt;<br>
>                 &gt; &nbsp; &nbsp; &gt; Regards,<br>
>                 &gt; &nbsp; &nbsp; &gt; Greg<br>
>                 &gt; &nbsp; &nbsp; &gt;<br>
>                 &gt; &nbsp; &nbsp; &gt; Comment to
>                 draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<br>
>                 &gt; &nbsp; &nbsp; &gt;<br>
>                 &gt; &nbsp; &nbsp; &gt; On Sat, Oct 30, 2010 at 10:14 AM, Luca
>                 Martini<br>
>                 &gt; &nbsp; &nbsp; &lt;<a moz-do-not-send="true"
>                   href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>
>                 &lt;mailto:<a moz-do-not-send="true"
>                   href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;<o:p></o:p></p>
>             </div>
>             <div>
>               <div>
>                 <p class="MsoNormal">&gt; &nbsp; &nbsp; &gt; &lt;mailto:<a
>                     moz-do-not-send="true"
>                     href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>
>                   &lt;mailto:<a moz-do-not-send="true"
>                     href="mailto:lmartini@cisco.com">lmartini@cisco.com</a>&gt;&gt;&gt;
>                   wrote:<br>
>                   &gt; &nbsp; &nbsp; &gt;<br>
>                   &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Greg,<br>
>                   &gt; &nbsp; &nbsp; &gt;<br>
>                   &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; You are correct , the proposed
>                   update does not propose any<br>
>                   &gt; &nbsp; &nbsp; changes<br>
>                   &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; to VCCV.<br>
>                   &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; However the problem with vccv is not
>                   as simple as to ask for<br>
>                   &gt; &nbsp; &nbsp; a new<br>
>                   &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; code point from IANA.<br>
>                   &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Given the good amount of discussion
>                   on this point, we should<br>
>                   &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; probably have a discussion in
>                   Beijing.<br>
>                   &gt; &nbsp; &nbsp; &gt;<br>
>                   &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; Luca<br>
>                   &gt; &nbsp; &nbsp; &gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;<br>
>                   &gt; &nbsp; &nbsp; &gt; &nbsp; &nbsp; On 10/29/2010 05:07 PM, Greg Mirsky
>                   wrote:<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Dear Authors,<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; I think that proposed update of
>                   the Section 4.2. RFC 5586<br>
>                   &gt; &nbsp; &nbsp; makes it possible<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; to use GAL on MPLS-TP PW that
>                   uses Control Word. I consider<br>
>                   &gt; &nbsp; &nbsp; it to be<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; conflict between PW VCCV CC
>                   types because use of GAL is not<br>
>                   &gt; &nbsp; &nbsp; negotiated<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; through PW VCCV negotiation. To
>                   avoid such situation I propose:<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;- in Section 5 request IANA
>                   to assign new CC Type "MPLS<br>
>                   &gt; &nbsp; &nbsp; Generic<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;Associated Channel Label"<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp;- assign precedence to new CC
>                   Type that affects Section<br>
>                   &gt; &nbsp; &nbsp; 7 RFC 5085<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Regards,<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; Greg<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp;
>                   _______________________________________________<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; mpls mailing list<o:p></o:p></p>
>               </div>
>             </div>
>             <p class="MsoNormal">&gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; <a
>                 moz-do-not-send="true" href="mailto:mpls@ietf.org">mpls@ietf.org</a>
>               &lt;mailto:<a moz-do-not-send="true"
>                 href="mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;
>               &lt;mailto:<a moz-do-not-send="true"
>                 href="mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></p>
>             <div>
>               <div>
>                 <p class="MsoNormal" style="margin-bottom: 12pt;">&gt; &nbsp;
>                   &nbsp; &lt;mailto:<a moz-do-not-send="true"
>                     href="mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;&gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;&gt; &nbsp; &nbsp; <a moz-do-not-send="true"
>                     href="https://www.ietf.org/mailman/listinfo/mpls"
>                     target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>
>                   &gt; &nbsp; &nbsp; &gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;<br>
>                   &gt; &nbsp; &nbsp; &gt;
>                   _______________________________________________<br>
>                   &gt; &nbsp; &nbsp; &gt; mpls mailing list<br>
>                   &gt; &nbsp; &nbsp; &gt; <a moz-do-not-send="true"
>                     href="mailto:mpls@ietf.org">mpls@ietf.org</a>
>                   &lt;mailto:<a moz-do-not-send="true"
>                     href="mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<br>
>                   &gt; &nbsp; &nbsp; &gt; <a moz-do-not-send="true"
>                     href="https://www.ietf.org/mailman/listinfo/mpls"
>                     target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br>
>                   &gt;<br>
>                   &gt;<o:p></o:p></p>
>               </div>
>             </div>
>           </div>
>           <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
>         </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>
>  
> --------------050303000603040509070000--
>  
> --===============1692597272==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>  
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>  
> --===============1692597272==--


From gregimirsky@gmail.com  Wed Mar 23 13:55:44 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0609C3A694C; Wed, 23 Mar 2011 13:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.723
X-Spam-Level: 
X-Spam-Status: No, score=-2.723 tagged_above=-999 required=5 tests=[AWL=-0.125, 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 s87bvyV0xvNg; Wed, 23 Mar 2011 13:55:42 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id CC3923A68D6; Wed, 23 Mar 2011 13:55:41 -0700 (PDT)
Received: by vxg33 with SMTP id 33so7539893vxg.31 for <multiple recipients>; Wed, 23 Mar 2011 13:57:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=NATeo5XlpGZjwKhbS8DSmt+xmeeeS6PxwljJdmX/Lb8=; b=aKWN0f/v5jdXOL7vKGrnEOvs7roOATLrTQxzbZzQ/dxUH8eMd3DreItestBsdmv3fg nZoXDlDVF1eeeeSMy48akcPOBNTAFTwFttVZCoxiz3A7+rtTrthAKMtZOKqssIrxt+J3 53pi/vk4dw8emxVUxTmkPjRlqydHwVeTxnaCk=
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=gSqBhoGDxJLTTUB4rH+akqz2yPlrggnRbrRLWIovu9zl6CL/z+0H7admn5+qON3m5u Irbsu8EP+lwpKkU2gKXEOe1dwk6IbgT9Fsje2Wjs24ZT5SCZPrHCWXZgEt53DlwCOaQZ odXVGNW5DfWFTYdOqQ8S9HcZT176drjE449hI=
MIME-Version: 1.0
Received: by 10.52.67.73 with SMTP id l9mr7406761vdt.287.1300913835406; Wed, 23 Mar 2011 13:57:15 -0700 (PDT)
Received: by 10.52.168.6 with HTTP; Wed, 23 Mar 2011 13:57:15 -0700 (PDT)
In-Reply-To: <201103232025.p2NKPr2t076600@harbor.orleans.occnc.com>
References: <4D88E3A7.4040502@cisco.com> <201103232025.p2NKPr2t076600@harbor.orleans.occnc.com>
Date: Wed, 23 Mar 2011 13:57:15 -0700
Message-ID: <AANLkTikNZH9w2iNRVwUAMmzJ2ktkjSfcdssNbEFvgNpr@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: curtis@occnc.com
Content-Type: multipart/alternative; boundary=20cf307f32040af5a2049f2c9b4c
Cc: Robert Rennison <Robert.Rennison@ecitele.com>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, stbryant@cisco.com
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2011 20:55:44 -0000

--20cf307f32040af5a2049f2c9b4c
Content-Type: text/plain; charset=ISO-8859-1

Dear Curtis and All,
I believe that any restriction on placing GAL in a label stack set in
Section 4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs
there are no restrictions set in RFC 5886 on where in a label stack GAL
might appear. Some of use cases mentioned by Curtis are outside of MPLS-TP
scope and, as I understand, use of GAL in these cases is not regulated by
the RFC 5886.
As to the issue of using GAL in PW there would not be a problem if not for
possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4,
properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886 -
we might be good.

Regards,
Greg

On Wed, Mar 23, 2011 at 1:25 PM, Curtis Villamizar <curtis@occnc.com> wrote:

>
> In message <4D88E3A7.4040502@cisco.com>
> Stewart Bryant writes:
> >
> > If there is IETF consensus to update RFC5586 with this change then the
> > process is relatively simple:
> >
> > The document making the update notes that it does the update, and the AD
> > draws attention to
> > this in the IETF LC.
> >
> > Stewart
>
>
> Stewart,
>
> The restriction that GAL be at the bottom of stack was simply a
> mistake IMHO.  I stated that during MPLS WG discussion before it
> became an RFC but it went through as is anyway with that restriction.
> Even then it was said that if there were a strong reason to relax it
> that it could be considered later.  That time may have come.
>
> There are a number of reasons that labels might want to go below GAL,
> including to use OAM to diagnose the connectivity (or lack of) that is
> experienced only for a specific label stack combinations where
> multipath (link bundle, LAG, less applicable is ECMP in this case) is
> used.
>
> In this case though, the GAL under the LSP label currently indicates
> that after the POP that OAM needs to be done (or more accurately that
> a G-Ach of some type is being carried).  If the GAL is put above the
> PW label it is in that same place and there is an ambiguity.  It is an
> ambiguity that for some but not all defined OAM can be resolved by
> looking at information in BFD that makes it unambiguous.  Unless I'm
> mistaken, in CC/CV the label stack above GAL provides the context.
>
> Another solution would be to put GAL under the PW label.  It would
> probably be best to put GAL under PW but over the fat-pw label.  The
> PW implementation, seeing the PW was not BOS, could look at the next
> label to see if the label is reserved and specifically if it is GAL,
> and if not process as payload (unless CW is also used).  If CW was not
> used the only advantage is 4 bytes less in payload but the same size
> in OAM packets.  This is an advantage though.
>
> On a related topic, if we must put ELI plus entropy label on the stack
> we have saved nothing relative to fat-pw plus CW.  ELI as a
> termination of hash search may have other uses though (MPLS-TP).
>
> I would be in favor of a very short draft just relaxing the
> requirement that GAL be at the bottom of stack, independent of the
> reason for doing so, since a number of reasons have emerged.  The
> behavior would be to throw away the rest of the label stack when the
> GAL label is exposed and look at the MPLS payload interpreting it as
> an G-Ach channel (most often, but not exclusively, as OAM).  This
> relaxation of the BOS restriction would be independent of usage.
>
> Curtis
>
>
> > On 22/03/2011 16:22, Robert Rennison wrote:
> > >
> > > Luca, Thomas,
> > >
> > > A couple of clarification questions.
> > >
> > > I'm trying to understand what the combination of the two drafts,
> > > -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts to.
> > >
> > > So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it's
> > > saying use VCCV type 1 where possible and if not then use the new type
> > > 4, whereby  in type 4 the exception mechanism is triggered by the use
> > > of the GAL,  and I appreciated the diagram in section 3 to lock this
> > > is, so far so good.
> > >
> > > Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these two
> > > drafts could work together since this one is trying to lay the "legal
> > > framework" i.e fix up the RFCs which mandated that the GAL could not
> > > be used with the PW.
> > >
> > > Then I get hit with a brick wall in the form of the statements in the
> > > last 2 paras of section 3 of tp-gal-in-pw which state.
> > >
> > > - Section 4.2
> > > <
> http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2
> >.
> > > (GAL Applicability and Usage) in [RFC5586
> > > <http://tools.ietf.org/html/rfc5586>], the
> > >
> > >       original text:
> > >
> > >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> > >
> > >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> > >
> > >           MUST NOT be used with PWs. It MUST always be at the bottom of
> > >
> > >           the label stack (i.e., S bit set to 1). However, in other
> MPLS
> > >
> > >           environments, this document places no restrictions on where
> > >
> > >           the GAL may appear within the label stack or its use with
> PWs.
> > >
> > >       is replaced by:
> > >
> > >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> > >
> > >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> > >
> > >           MAY be used with PWs. It MUST always be at the bottom of the
> > >
> > >           label stack (i.e., S bit set to 1). However, in other MPLS
> > >
> > >           environments, this document places no restrictions on where
> > >
> > >           the GAL may appear within the label stack.
> > >
> > > It's the bit about the GAL MUST be at the bottom of the label stack,
> > > this is clearly inconsistent with what is proposed in the
> > > draft-nadeau-pwe3 where one can clearly see the GAL above the PW label
> > > and if one has to use  a GAL with a PW this would be the place to put
> it,
> > >
> > > Now I can hear you saying "oh but look at the text below this, where
> > > we state .."However, in other MPLS environments , this document places
> > > no restrictions on where the GAL may appear within the label stack.
> > > This is consistent with draft-nadeau "   In which case I'd retort with
> > > ; what are we to do for PWs in   MPLS-TP, since what's in draft-nadeau
> > > would not be allowed ?
> > >
> > > Clarification /explanation appreciated.
> > >
> > > Cheers
> > >
> > > Rob Rennison
> > >
>
[snipped ...]

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

Dear Curtis and All,<br>I believe that any restriction on placing GAL in a =
label stack set in Section 4.2, RFC 5886 is relevant only for MPLS-TP PSN. =
For non-TP PSNs there are no restrictions set in RFC 5886 on where in a lab=
el stack GAL might appear. Some of use cases mentioned by Curtis are outsid=
e of MPLS-TP scope and, as I understand, use of GAL in these cases is not r=
egulated by the RFC 5886.<br>
As to the issue of using GAL in PW there would not be a problem if not for =
possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4=
, properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886=
 - we might be good.<br>
<br>Regards,<br>Greg<br><br><div class=3D"gmail_quote">On Wed, Mar 23, 2011=
 at 1:25 PM, Curtis Villamizar <span dir=3D"ltr">&lt;<a href=3D"mailto:curt=
is@occnc.com">curtis@occnc.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid=
 rgb(204, 204, 204); padding-left: 1ex;">
<br>
In message &lt;<a href=3D"mailto:4D88E3A7.4040502@cisco.com">4D88E3A7.40405=
02@cisco.com</a>&gt;<br>
<div class=3D"im">Stewart Bryant writes:<br>
&gt;<br>
&gt; If there is IETF consensus to update RFC5586 with this change then the=
<br>
&gt; process is relatively simple:<br>
&gt;<br>
&gt; The document making the update notes that it does the update, and the =
AD<br>
&gt; draws attention to<br>
&gt; this in the IETF LC.<br>
&gt;<br>
&gt; Stewart<br>
<br>
<br>
</div>Stewart,<br>
<br>
The restriction that GAL be at the bottom of stack was simply a<br>
mistake IMHO. =A0I stated that during MPLS WG discussion before it<br>
became an RFC but it went through as is anyway with that restriction.<br>
Even then it was said that if there were a strong reason to relax it<br>
that it could be considered later. =A0That time may have come.<br>
<br>
There are a number of reasons that labels might want to go below GAL,<br>
including to use OAM to diagnose the connectivity (or lack of) that is<br>
experienced only for a specific label stack combinations where<br>
multipath (link bundle, LAG, less applicable is ECMP in this case) is<br>
used.<br>
<br>
In this case though, the GAL under the LSP label currently indicates<br>
that after the POP that OAM needs to be done (or more accurately that<br>
a G-Ach of some type is being carried). =A0If the GAL is put above the<br>
PW label it is in that same place and there is an ambiguity. =A0It is an<br=
>
ambiguity that for some but not all defined OAM can be resolved by<br>
looking at information in BFD that makes it unambiguous. =A0Unless I&#39;m<=
br>
mistaken, in CC/CV the label stack above GAL provides the context.<br>
<br>
Another solution would be to put GAL under the PW label. =A0It would<br>
probably be best to put GAL under PW but over the fat-pw label. =A0The<br>
PW implementation, seeing the PW was not BOS, could look at the next<br>
label to see if the label is reserved and specifically if it is GAL,<br>
and if not process as payload (unless CW is also used). =A0If CW was not<br=
>
used the only advantage is 4 bytes less in payload but the same size<br>
in OAM packets. =A0This is an advantage though.<br>
<br>
On a related topic, if we must put ELI plus entropy label on the stack<br>
we have saved nothing relative to fat-pw plus CW. =A0ELI as a<br>
termination of hash search may have other uses though (MPLS-TP).<br>
<br>
I would be in favor of a very short draft just relaxing the<br>
requirement that GAL be at the bottom of stack, independent of the<br>
reason for doing so, since a number of reasons have emerged. =A0The<br>
behavior would be to throw away the rest of the label stack when the<br>
GAL label is exposed and look at the MPLS payload interpreting it as<br>
an G-Ach channel (most often, but not exclusively, as OAM). =A0This<br>
relaxation of the BOS restriction would be independent of usage.<br>
<br>
Curtis<br>
<div class=3D"im"><br>
<br>
&gt; On 22/03/2011 16:22, Robert Rennison wrote:<br>
&gt; &gt;<br>
&gt; &gt; Luca, Thomas,<br>
&gt; &gt;<br>
&gt; &gt; A couple of clarification questions.<br>
&gt; &gt;<br>
&gt; &gt; I&#39;m trying to understand what the combination of the two draf=
ts,<br>
</div>&gt; &gt; -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amo=
unts to.<br>
<div class=3D"im">&gt; &gt;<br>
&gt; &gt; So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it&=
#39;s<br>
&gt; &gt; saying use VCCV type 1 where possible and if not then use the new=
 type<br>
&gt; &gt; 4, whereby =A0in type 4 the exception mechanism is triggered by t=
he use<br>
&gt; &gt; of the GAL, =A0and I appreciated the diagram in section 3 to lock=
 this<br>
&gt; &gt; is, so far so good.<br>
&gt; &gt;<br>
&gt; &gt; Now I read -pwe3-mpls-tp-gal-in-pw and I&#39;m thinking , Ok thes=
e two<br>
&gt; &gt; drafts could work together since this one is trying to lay the &q=
uot;legal<br>
&gt; &gt; framework&quot; i.e fix up the RFCs which mandated that the GAL c=
ould not<br>
&gt; &gt; be used with the PW.<br>
&gt; &gt;<br>
&gt; &gt; Then I get hit with a brick wall in the form of the statements in=
 the<br>
&gt; &gt; last 2 paras of section 3 of tp-gal-in-pw which state.<br>
&gt; &gt;<br>
&gt; &gt; - Section 4.2<br>
</div>&gt; &gt; &lt;<a href=3D"http://tools.ietf.org/html/draft-lm-pwe3-mpl=
s-tp-gal-in-pw-00#section-4.2" target=3D"_blank">http://tools.ietf.org/html=
/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2</a>&gt;.<br>
<div class=3D"im">&gt; &gt; (GAL Applicability and Usage) in [RFC5586<br>
</div>&gt; &gt; &lt;<a href=3D"http://tools.ietf.org/html/rfc5586" target=
=3D"_blank">http://tools.ietf.org/html/rfc5586</a>&gt;], the<br>
<div><div></div><div class=3D"h5">&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 original text:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 In MPLS-TP, the GAL MUST be used with packets=
 on a G-ACh on<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 LSPs, Concatenated Segments of LSPs, and with=
 Sections, and<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 MUST NOT be used with PWs. It MUST always be =
at the bottom of<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 the label stack (i.e., S bit set to 1). Howev=
er, in other MPLS<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 environments, this document places no restric=
tions on where<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 the GAL may appear within the label stack or =
its use with PWs.<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 is replaced by:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 In MPLS-TP, the GAL MUST be used with packets=
 on a G-ACh on<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 LSPs, Concatenated Segments of LSPs, and with=
 Sections, and<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 MAY be used with PWs. It MUST always be at th=
e bottom of the<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 label stack (i.e., S bit set to 1). However, =
in other MPLS<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 environments, this document places no restric=
tions on where<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 the GAL may appear within the label stack.<br=
>
&gt; &gt;<br>
&gt; &gt; It&#39;s the bit about the GAL MUST be at the bottom of the label=
 stack,<br>
&gt; &gt; this is clearly inconsistent with what is proposed in the<br>
&gt; &gt; draft-nadeau-pwe3 where one can clearly see the GAL above the PW =
label<br>
&gt; &gt; and if one has to use =A0a GAL with a PW this would be the place =
to put it,<br>
&gt; &gt;<br>
&gt; &gt; Now I can hear you saying &quot;oh but look at the text below thi=
s, where<br>
&gt; &gt; we state ..&quot;However, in other MPLS environments , this docum=
ent places<br>
&gt; &gt; no restrictions on where the GAL may appear within the label stac=
k.<br>
&gt; &gt; This is consistent with draft-nadeau &quot; =A0 In which case I&#=
39;d retort with<br>
&gt; &gt; ; what are we to do for PWs in =A0 MPLS-TP, since what&#39;s in d=
raft-nadeau<br>
&gt; &gt; would not be allowed ?<br>
&gt; &gt;<br>
&gt; &gt; Clarification /explanation appreciated.<br>
&gt; &gt;<br>
&gt; &gt; Cheers<br>
&gt; &gt;<br>
&gt; &gt; Rob Rennison<br>
&gt; &gt;<br></div></div></blockquote></div>[snipped ...]<br>

--20cf307f32040af5a2049f2c9b4c--

From lufang@cisco.com  Wed Mar 23 18:15:55 2011
Return-Path: <lufang@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 680FA3A67A2 for <pwe3@core3.amsl.com>; Wed, 23 Mar 2011 18:15:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uWX76T6ibxkb for <pwe3@core3.amsl.com>; Wed, 23 Mar 2011 18:15:54 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 913BE3A67AA for <pwe3@ietf.org>; Wed, 23 Mar 2011 18:15:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lufang@cisco.com; l=6333; q=dns/txt; s=iport; t=1300929448; x=1302139048; h=mime-version:subject:date:message-id:in-reply-to: references:from:to; bh=AvqIYh9th56Q4Bia+B/XbBR+zrh6BQFzM6Va+gYig5M=; b=j0Ig0+O8+xGAPUbIsB7q1o3klOAEdGeaVCu7cGqM0SvJMOXfbTB5oQ4k I3DnOS8LHOAfCajxbKFywQsqOe+CCqCwDPAjATUZWU2F8OGt6NH6OmXHU 6jJRbIVqr3zUTrxsonWToJG6qgKAJdvAaeYkmecr+8v8EUXuYwzXApcCT 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAC44ik2tJV2a/2dsb2JhbACCX6Jjd6Y2nDWFaQSBeIM/ixA
X-IronPort-AV: E=Sophos;i="4.63,234,1299456000";  d="scan'208,217";a="281774413"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by sj-iport-3.cisco.com with ESMTP; 24 Mar 2011 01:17:27 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2O1HSaT010655 for <pwe3@ietf.org>; Thu, 24 Mar 2011 01:17:28 GMT
Received: from xmb-rcd-201.cisco.com ([72.163.62.208]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Mar 2011 20:17:27 -0500
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_01CBE9C1.3D8B5168"
Date: Wed, 23 Mar 2011 20:17:26 -0500
Message-ID: <238542D917511A45B6B8AA806E875E25050C3372@XMB-RCD-201.cisco.com>
In-Reply-To: <4D88E3A7.4040502@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: MPLS 2011 International Conference - Call for Papers
Thread-Index: AcvpeE/0avrTqDUMRhi/ppMO2lBJawAR6Hwg
References: <AANLkTikcnCa5DQZyGgD_QawiQ_57KKA4BXQm7iRRayKA@mail.gmail.com>	<4D5E9442.3030101@cisco.com>	<AANLkTikmTjBZgtxNQRrAbBVQEmEKFAvyvAapk7Qbdf9O@mail.gmail.com>	<4D7A2439.6010508@cisco.com>	<AANLkTim+hqNFHi9xwuzG5_2qoKztEn9SJA9TDh-S-XUo@mail.gmail.com>	<A3C5DF08D38B6049839A6F553B331C76D6FBBDD332@ILPTMAIL02.ecitele.com><786AD2EC3D80A1428B921CDC9BE9EE546569F9F8E1@USPITMAIL01.ecitele.com> <4D88E3A7.4040502@cisco.com>
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: "pwe3" <pwe3@ietf.org>
X-OriginalArrivalTime: 24 Mar 2011 01:17:27.0937 (UTC) FILETIME=[3D772710:01CBE9C1]
Subject: [PWE3] MPLS 2011 International Conference - Call for Papers
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 01:15:55 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBE9C1.3D8B5168
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear colleagues,

=20

The MPLS 2011 International Conference, the 14th Annual International
Conference on MPLS and Related Technologies, will be held October 16 -
19, 2011, in Washington, DC. The Technical Program Committee is
soliciting abstracts summarizing a proposed presentation representing
original/unpublished work covering cutting-edge topics.

=20

Presentations covering new technologies and operational experience are
solicited from network equipment vendors, service/transport providers,
government agencies, the research community, and enterprise users.

=20

The deadline for submission of presentation proposals is April 29, 2011.

If you want further information on MPLS 2010 or want to submit a
presentation abstract, please see the following URL:

=20

http://www.isocore.com/mpls2011/call_for_papers/cfp.htm

=20

Many of these topics have been of interest to members of this community
in the past, and many people active on this list have been presenters at
past events.

=20

Regards,

Luyuan

=20


------_=_NextPart_001_01CBE9C1.3D8B5168
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: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:"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:Consolas;
	panose-1:2 11 6 9 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","serif";
	color:black;}
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:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:137459209;
	mso-list-template-ids:727736002;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	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 bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoPlainText>Dear colleagues,<o:p></o:p></p>

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

<p class=3DMsoPlainText>The MPLS 2011 International Conference, the 14th =
Annual
International Conference on MPLS and Related Technologies, will be held =
October
16 - 19, 2011, in Washington, DC. The Technical Program Committee is =
soliciting
abstracts summarizing a proposed presentation representing =
original/unpublished
work covering cutting-edge topics.<o:p></o:p></p>

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

<p class=3DMsoPlainText>Presentations covering new technologies and =
operational
experience are solicited from network equipment vendors, =
service/transport
providers, government agencies, the research community, and enterprise =
users.<o:p></o:p></p>

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

<p class=3DMsoPlainText>The deadline for submission of presentation =
proposals is
April 29, 2011.<o:p></o:p></p>

<p class=3DMsoPlainText>If you want further information on MPLS 2010 or =
want to
submit a presentation abstract, please see the following =
URL:<o:p></o:p></p>

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

<p class=3DMsoPlainText><a
href=3D"http://www.isocore.com/mpls2011/call_for_papers/cfp.htm">http://w=
ww.isocore.com/mpls2011/call_for_papers/cfp.htm</a><o:p></o:p></p>

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

<p class=3DMsoPlainText>Many of these topics have been of interest to =
members of
this community in the past, and many people active on this list have =
been
presenters at past events.<o:p></o:p></p>

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

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

<p class=3DMsoPlainText>Luyuan<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>

</body>

</html>

------_=_NextPart_001_01CBE9C1.3D8B5168--

From Alexander.Vainshtein@ecitele.com  Wed Mar 23 22:43:12 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCBCC3A67EE; Wed, 23 Mar 2011 22:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.025,  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 vHFHunwhl07F; Wed, 23 Mar 2011 22:43:09 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id 5F0673A67EC; Wed, 23 Mar 2011 22:43:07 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-7a-4d8ad9e27c25
Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id D1.C9.19639.2E9DA8D4; Thu, 24 Mar 2011 07:42:58 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Thu, 24 Mar 2011 07:44:40 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Greg Mirsky <gregimirsky@gmail.com>, "curtis@occnc.com" <curtis@occnc.com>
Date: Thu, 24 Mar 2011 07:44:39 +0200
Thread-Topic: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Thread-Index: AcvpnOiGGRabzLeyRbyIkrfThDWZpQARrqfo
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6FB8BEACE@ILPTMAIL02.ecitele.com>
References: <4D88E3A7.4040502@cisco.com> <201103232025.p2NKPr2t076600@harbor.orleans.occnc.com>, <AANLkTikNZH9w2iNRVwUAMmzJ2ktkjSfcdssNbEFvgNpr@mail.gmail.com>
In-Reply-To: <AANLkTikNZH9w2iNRVwUAMmzJ2ktkjSfcdssNbEFvgNpr@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_A3C5DF08D38B6049839A6F553B331C76D6FB8BEACEILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG, Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, Robert Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [PWE3] [mpls-tp] [mpls] WG LC	draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 05:43:12 -0000

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEACEILPTMAIL02eci_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Greg, Curtis and all,
I think that the linkage between TP/non-TP differentiation and restrictions=
 on GAL usage is highly problematic.

E.g., consider an MS-PW with some segments crossing TP domains and some - n=
on-TP ones (this is a realistic example).

IMHO GAL is part of the data plane that is shared by IP/MPLS and MPLS-TP-TP=
, and hence the same restrictions should apply uniformly. IMHO RFC 5960 com=
plies with this principle.

RFC 5960 also seems to impose the restriction on GAL being at the bottom of=
 stack. E.g., please look at the following text fragment:


   If the TTL of an LSP label expires, then the label with the
   S (Bottom of Stack) bit set is inspected to determine if it is a
   reserved label.  If it is a reserved label, the packet is processed
   according to the rules of that reserved label.  For example, if it is
   a Generic Associated Channel Label (GAL), then it is processed as a
   packet on the Generic Associated Channel (G-ACh); see Section 4.  If
   the TTL of a PW expires at an S-PE or T-PE, then the packet is
   examined to determine if a Generic Associated Channel Header (ACH) is
   present immediately below the PW label.  If so, then the packet is
   processed as a packet on the G-ACh.

And, last but not least, if we decide to allow GAL in the middle of the lab=
el stack (overriding RFC 5586 and RFC 5960), we must also define how a pack=
et with GAL in the middle of the label stack is forwarded when GAL is expos=
ed, similar to what has been done in RFC 3032 for RAL.

My 2c,
     Sasha


________________________________
From: mpls-tp-bounces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of Greg=
 Mirsky [gregimirsky@gmail.com]
Sent: Wednesday, March 23, 2011 10:57 PM
To: curtis@occnc.com
Cc: Robert Rennison; mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.com=
; pwe3; HUANG Feng F
Subject: Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-=
00.txt

Dear Curtis and All,
I believe that any restriction on placing GAL in a label stack set in Secti=
on 4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs there ar=
e no restrictions set in RFC 5886 on where in a label stack GAL might appea=
r. Some of use cases mentioned by Curtis are outside of MPLS-TP scope and, =
as I understand, use of GAL in these cases is not regulated by the RFC 5886=
.
As to the issue of using GAL in PW there would not be a problem if not for =
possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4=
, properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886=
 - we might be good.

Regards,
Greg

On Wed, Mar 23, 2011 at 1:25 PM, Curtis Villamizar <curtis@occnc.com<mailto=
:curtis@occnc.com>> wrote:

In message <4D88E3A7.4040502@cisco.com<mailto:4D88E3A7.4040502@cisco.com>>
Stewart Bryant writes:
>
> If there is IETF consensus to update RFC5586 with this change then the
> process is relatively simple:
>
> The document making the update notes that it does the update, and the AD
> draws attention to
> this in the IETF LC.
>
> Stewart


Stewart,

The restriction that GAL be at the bottom of stack was simply a
mistake IMHO.  I stated that during MPLS WG discussion before it
became an RFC but it went through as is anyway with that restriction.
Even then it was said that if there were a strong reason to relax it
that it could be considered later.  That time may have come.

There are a number of reasons that labels might want to go below GAL,
including to use OAM to diagnose the connectivity (or lack of) that is
experienced only for a specific label stack combinations where
multipath (link bundle, LAG, less applicable is ECMP in this case) is
used.

In this case though, the GAL under the LSP label currently indicates
that after the POP that OAM needs to be done (or more accurately that
a G-Ach of some type is being carried).  If the GAL is put above the
PW label it is in that same place and there is an ambiguity.  It is an
ambiguity that for some but not all defined OAM can be resolved by
looking at information in BFD that makes it unambiguous.  Unless I'm
mistaken, in CC/CV the label stack above GAL provides the context.

Another solution would be to put GAL under the PW label.  It would
probably be best to put GAL under PW but over the fat-pw label.  The
PW implementation, seeing the PW was not BOS, could look at the next
label to see if the label is reserved and specifically if it is GAL,
and if not process as payload (unless CW is also used).  If CW was not
used the only advantage is 4 bytes less in payload but the same size
in OAM packets.  This is an advantage though.

On a related topic, if we must put ELI plus entropy label on the stack
we have saved nothing relative to fat-pw plus CW.  ELI as a
termination of hash search may have other uses though (MPLS-TP).

I would be in favor of a very short draft just relaxing the
requirement that GAL be at the bottom of stack, independent of the
reason for doing so, since a number of reasons have emerged.  The
behavior would be to throw away the rest of the label stack when the
GAL label is exposed and look at the MPLS payload interpreting it as
an G-Ach channel (most often, but not exclusively, as OAM).  This
relaxation of the BOS restriction would be independent of usage.

Curtis


> On 22/03/2011 16:22, Robert Rennison wrote:
> >
> > Luca, Thomas,
> >
> > A couple of clarification questions.
> >
> > I'm trying to understand what the combination of the two drafts,
> > -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts to.
> >
> > So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it's
> > saying use VCCV type 1 where possible and if not then use the new type
> > 4, whereby  in type 4 the exception mechanism is triggered by the use
> > of the GAL,  and I appreciated the diagram in section 3 to lock this
> > is, so far so good.
> >
> > Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these two
> > drafts could work together since this one is trying to lay the "legal
> > framework" i.e fix up the RFCs which mandated that the GAL could not
> > be used with the PW.
> >
> > Then I get hit with a brick wall in the form of the statements in the
> > last 2 paras of section 3 of tp-gal-in-pw which state.
> >
> > - Section 4.2
> > <http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-=
4.2>.
> > (GAL Applicability and Usage) in [RFC5586
> > <http://tools.ietf.org/html/rfc5586>], the
> >
> >       original text:
> >
> >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> >
> >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> >
> >           MUST NOT be used with PWs. It MUST always be at the bottom of
> >
> >           the label stack (i.e., S bit set to 1). However, in other MPL=
S
> >
> >           environments, this document places no restrictions on where
> >
> >           the GAL may appear within the label stack or its use with PWs=
.
> >
> >       is replaced by:
> >
> >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> >
> >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> >
> >           MAY be used with PWs. It MUST always be at the bottom of the
> >
> >           label stack (i.e., S bit set to 1). However, in other MPLS
> >
> >           environments, this document places no restrictions on where
> >
> >           the GAL may appear within the label stack.
> >
> > It's the bit about the GAL MUST be at the bottom of the label stack,
> > this is clearly inconsistent with what is proposed in the
> > draft-nadeau-pwe3 where one can clearly see the GAL above the PW label
> > and if one has to use  a GAL with a PW this would be the place to put i=
t,
> >
> > Now I can hear you saying "oh but look at the text below this, where
> > we state .."However, in other MPLS environments , this document places
> > no restrictions on where the GAL may appear within the label stack.
> > This is consistent with draft-nadeau "   In which case I'd retort with
> > ; what are we to do for PWs in   MPLS-TP, since what's in draft-nadeau
> > would not be allowed ?
> >
> > Clarification /explanation appreciated.
> >
> > Cheers
> >
> > Rob Rennison
> >
[snipped ...]

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEACEILPTMAIL02eci_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta content=3D"MSHTML 6.00.6000.17063" name=3D"GENERATOR">
<style id=3D"owaTempEditStyle"></style><style title=3D"owaParaStyle"><!--P =
{
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi=3D"x">
<div style=3D"FONT-SIZE: 16px; COLOR: #000000; DIRECTION: ltr; FONT-FAMILY:=
 Times New Roman">
<div>Greg, Curtis and all,</div>
<div><font face=3D"times new roman">I think that the linkage between TP/non=
-TP differentiation and restrictions on GAL usage is highly problematic.</f=
ont></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">E.g., consider an MS-PW with some segme=
nts crossing TP domains and some - non-TP ones (this is a realistic example=
).&nbsp;
</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">IMHO GAL is part of the data plane that=
 is&nbsp;shared by IP/MPLS&nbsp;and<a></a> MPLS-TP-TP, and hence the same r=
estrictions&nbsp;should<a></a> apply uniformly. IMHO RFC 5960 complies with=
 this principle.</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">RFC 5960 also seems to impose the restr=
iction on GAL being at the bottom of stack. E.g., please look at&nbsp;the<a=
></a> following text fragment:</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<blockquote dir=3D"ltr" style=3D"MARGIN-RIGHT: 0px">
<div><font face=3D"times new roman"><span class=3D"Apple-style-span" style=
=3D"WORD-SPACING: 0px; FONT: medium 'Times New Roman'; TEXT-TRANSFORM: none=
; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING:=
 normal; BORDER-COLLAPSE: separate; orphans: 2; widows: 2; -webkit-border-h=
orizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-=
decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-s=
troke-width: 0px"><span class=3D"Apple-style-span" style=3D"FONT-SIZE: 13px=
; LINE-HEIGHT: 16px; FONT-FAMILY: arial, helvetica, clean, sans-serif; -web=
kit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px">
<pre style=3D"MARGIN: 0px; LINE-HEIGHT: 1.2em; FONT-FAMILY: monospace">   I=
f the TTL of an LSP label expires, then the label with the=20
   S (Bottom of Stack) bit set is inspected to determine if it is a
   reserved label.  If it is a reserved label, the packet is processed
   according to the rules of that reserved label.  For example, if it is
   a Generic Associated Channel Label (GAL), then it is processed as a
   packet on the Generic Associated Channel (G-ACh<a></a><a></a>); see Sect=
ion 4.  If
   the TTL of a PW expires at an S-PE or T-PE, then the packet is
   examined to determine if a Generic Associated Channel Header (ACH) is
   present immediately below the PW label.  If so, then the packet is
   processed as a packet on the G-ACh<a></a><a></a>.</pre>
</span></span></font></div>
</blockquote>
<div><font face=3D"times new roman">And, last but not least, if we decide t=
o allow GAL in the middle of the label stack (overriding RFC 5586 and RFC 5=
960), we must also define how a packet with GAL in the middle of the label =
stack is forwarded when GAL is exposed,
 similar to what has been done in RFC 3032 for RAL.</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">My 2c,</font></div>
<div><font face=3D"times new roman">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</font></=
div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"Times New Roman" color=3D"#000000" size=3D"3=
"></font>&nbsp;</div>
<div id=3D"divRpF811070" style=3D"DIRECTION: ltr">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" color=3D"#000000" size=3D"2"><b>From:</b> mpls-tp-bou=
nces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of Greg Mirsky [gregimir=
sky@gmail.com]<br>
<b>Sent:</b> Wednesday, March 23, 2011 10:57 PM<br>
<b>To:</b> curtis@occnc.com<br>
<b>Cc:</b> Robert Rennison; mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamob=
ile.com; pwe3; HUANG Feng F<br>
<b>Subject:</b> Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal=
-in-pw-00.txt<br>
</font><br>
</div>
<div></div>
<div>Dear Curtis and All,<br>
I believe that any restriction on placing GAL in a label stack set in Secti=
on 4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs there ar=
e no restrictions set in RFC 5886 on where in a label stack GAL might appea=
r. Some of use cases mentioned by
 Curtis are outside of MPLS-TP scope and, as I understand, use of GAL in th=
ese cases is not regulated by the RFC 5886.<br>
As to the issue of using GAL in PW there would not be a problem if not for =
possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4=
, properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886=
 - we might be good.<br>
<br>
Regards,<br>
Greg<br>
<br>
<div class=3D"gmail_quote">On Wed, Mar 23, 2011 at 1:25 PM, Curtis Villamiz=
ar <span dir=3D"ltr">
&lt;<a href=3D"mailto:curtis@occnc.com">curtis@occnc.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0=
pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<br>
In message &lt;<a href=3D"mailto:4D88E3A7.4040502@cisco.com">4D88E3A7.40405=
02@cisco.com</a>&gt;<br>
<div class=3D"im">Stewart Bryant writes:<br>
&gt;<br>
&gt; If there is IETF consensus to update RFC5586 with this change then the=
<br>
&gt; process is relatively simple:<br>
&gt;<br>
&gt; The document making the update notes that it does the update, and the =
AD<br>
&gt; draws attention to<br>
&gt; this in the IETF LC.<br>
&gt;<br>
&gt; Stewart<br>
<br>
<br>
</div>
Stewart,<br>
<br>
The restriction that GAL be at the bottom of stack was simply a<br>
mistake IMHO. &nbsp;I stated that during MPLS WG discussion before it<br>
became an RFC but it went through as is anyway with that restriction.<br>
Even then it was said that if there were a strong reason to relax it<br>
that it could be considered later. &nbsp;That time may have come.<br>
<br>
There are a number of reasons that labels might want to go below GAL,<br>
including to use OAM to diagnose the connectivity (or lack of) that is<br>
experienced only for a specific label stack combinations where<br>
multipath (link bundle, LAG, less applicable is ECMP in this case) is<br>
used.<br>
<br>
In this case though, the GAL under the LSP label currently indicates<br>
that after the POP that OAM needs to be done (or more accurately that<br>
a G-Ach of some type is being carried). &nbsp;If the GAL is put above the<b=
r>
PW label it is in that same place and there is an ambiguity. &nbsp;It is an=
<br>
ambiguity that for some but not all defined OAM can be resolved by<br>
looking at information in BFD that makes it unambiguous. &nbsp;Unless I'm<b=
r>
mistaken, in CC/CV the label stack above GAL provides the context.<br>
<br>
Another solution would be to put GAL under the PW label. &nbsp;It would<br>
probably be best to put GAL under PW but over the fat-pw label. &nbsp;The<b=
r>
PW implementation, seeing the PW was not BOS, could look at the next<br>
label to see if the label is reserved and specifically if it is GAL,<br>
and if not process as payload (unless CW is also used). &nbsp;If CW was not=
<br>
used the only advantage is 4 bytes less in payload but the same size<br>
in OAM packets. &nbsp;This is an advantage though.<br>
<br>
On a related topic, if we must put ELI plus entropy label on the stack<br>
we have saved nothing relative to fat-pw plus CW. &nbsp;ELI as a<br>
termination of hash search may have other uses though (MPLS-TP).<br>
<br>
I would be in favor of a very short draft just relaxing the<br>
requirement that GAL be at the bottom of stack, independent of the<br>
reason for doing so, since a number of reasons have emerged. &nbsp;The<br>
behavior would be to throw away the rest of the label stack when the<br>
GAL label is exposed and look at the MPLS payload interpreting it as<br>
an G-Ach channel (most often, but not exclusively, as OAM). &nbsp;This<br>
relaxation of the BOS restriction would be independent of usage.<br>
<br>
Curtis<br>
<div class=3D"im"><br>
<br>
&gt; On 22/03/2011 16:22, Robert Rennison wrote:<br>
&gt; &gt;<br>
&gt; &gt; Luca, Thomas,<br>
&gt; &gt;<br>
&gt; &gt; A couple of clarification questions.<br>
&gt; &gt;<br>
&gt; &gt; I'm trying to understand what the combination of the two drafts,<=
br>
</div>
&gt; &gt; -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts t=
o.<br>
<div class=3D"im">&gt; &gt;<br>
&gt; &gt; So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it'=
s<br>
&gt; &gt; saying use VCCV type 1 where possible and if not then use the new=
 type<br>
&gt; &gt; 4, whereby &nbsp;in type 4 the exception mechanism is triggered b=
y the use<br>
&gt; &gt; of the GAL, &nbsp;and I appreciated the diagram in section 3 to l=
ock this<br>
&gt; &gt; is, so far so good.<br>
&gt; &gt;<br>
&gt; &gt; Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these tw=
o<br>
&gt; &gt; drafts could work together since this one is trying to lay the &q=
uot;legal<br>
&gt; &gt; framework&quot; i.e fix up the RFCs which mandated that the GAL c=
ould not<br>
&gt; &gt; be used with the PW.<br>
&gt; &gt;<br>
&gt; &gt; Then I get hit with a brick wall in the form of the statements in=
 the<br>
&gt; &gt; last 2 paras of section 3 of tp-gal-in-pw which state.<br>
&gt; &gt;<br>
&gt; &gt; - Section 4.2<br>
</div>
&gt; &gt; &lt;<a href=3D"http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-g=
al-in-pw-00#section-4.2" target=3D"_blank">http://tools.ietf.org/html/draft=
-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2</a>&gt;.<br>
<div class=3D"im">&gt; &gt; (GAL Applicability and Usage) in [RFC5586<br>
</div>
&gt; &gt; &lt;<a href=3D"http://tools.ietf.org/html/rfc5586" target=3D"_bla=
nk">http://tools.ietf.org/html/rfc5586</a>&gt;], the<br>
<div>
<div></div>
<div class=3D"h5">&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; original text:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; In MPLS-TP, the GAL MUST be us=
ed with packets on a G-ACh on<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; LSPs, Concatenated Segments of=
 LSPs, and with Sections, and<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; MUST NOT be used with PWs. It =
MUST always be at the bottom of<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the label stack (i.e., S bit s=
et to 1). However, in other MPLS<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; environments, this document pl=
aces no restrictions on where<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the GAL may appear within the =
label stack or its use with PWs.<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; is replaced by:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; In MPLS-TP, the GAL MUST be us=
ed with packets on a G-ACh on<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; LSPs, Concatenated Segments of=
 LSPs, and with Sections, and<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; MAY be used with PWs. It MUST =
always be at the bottom of the<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; label stack (i.e., S bit set t=
o 1). However, in other MPLS<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; environments, this document pl=
aces no restrictions on where<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the GAL may appear within the =
label stack.<br>
&gt; &gt;<br>
&gt; &gt; It's the bit about the GAL MUST be at the bottom of the label sta=
ck,<br>
&gt; &gt; this is clearly inconsistent with what is proposed in the<br>
&gt; &gt; draft-nadeau-pwe3 where one can clearly see the GAL above the PW =
label<br>
&gt; &gt; and if one has to use &nbsp;a GAL with a PW this would be the pla=
ce to put it,<br>
&gt; &gt;<br>
&gt; &gt; Now I can hear you saying &quot;oh but look at the text below thi=
s, where<br>
&gt; &gt; we state ..&quot;However, in other MPLS environments , this docum=
ent places<br>
&gt; &gt; no restrictions on where the GAL may appear within the label stac=
k.<br>
&gt; &gt; This is consistent with draft-nadeau &quot; &nbsp; In which case =
I'd retort with<br>
&gt; &gt; ; what are we to do for PWs in &nbsp; MPLS-TP, since what's in dr=
aft-nadeau<br>
&gt; &gt; would not be allowed ?<br>
&gt; &gt;<br>
&gt; &gt; Clarification /explanation appreciated.<br>
&gt; &gt;<br>
&gt; &gt; Cheers<br>
&gt; &gt;<br>
&gt; &gt; Rob Rennison<br>
&gt; &gt;<br>
</div>
</div>
</blockquote>
</div>
[snipped ...]<br>
</div>
</div>
</body>
</html>

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEACEILPTMAIL02eci_--

From gregimirsky@gmail.com  Wed Mar 23 23:32:16 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 906A03A6808; Wed, 23 Mar 2011 23:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.213
X-Spam-Level: 
X-Spam-Status: No, score=-3.213 tagged_above=-999 required=5 tests=[AWL=0.385,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 xcFFyHjZer5a; Wed, 23 Mar 2011 23:32:14 -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 231B23A67EE; Wed, 23 Mar 2011 23:32:13 -0700 (PDT)
Received: by vws12 with SMTP id 12so7319701vws.31 for <multiple recipients>; Wed, 23 Mar 2011 23:33:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Ie+9k5NnCumygPyA4nifKt5f2LogXDebqXOozZsCLtQ=; b=egBGjsFHgggyDHUsmHrJnQlLvVWUd5nNkYJ1zVk4dI/Afg8UiZCZrDfp/2TDBuE54M YatqBJOhC2c3cGeW4Yi1XEUEOKYMZBJvRYeATwongnJ58HRQWSSUvigsN0s1x6V48bMp Frw7UJf/0HY5wd4cU/Biw2b3vXd7dj47MD9R4=
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=pbuQvzAx/AIDMt8IsSUzYdcG+E7yqMEWZKnktZL0IHiPnvczG5kcdSSST+uvnnlzjr 4iLga03kKehqck+uSg0RioaTV1nINgfzBJWViZndBEES7AP/7hKUMRvMh7QTQpnTzM3R 7MtSNrlOaEKRL+HLqmCKNDMV+/gyBhGaLUIBc=
MIME-Version: 1.0
Received: by 10.52.65.195 with SMTP id z3mr7998753vds.175.1300948426212; Wed, 23 Mar 2011 23:33:46 -0700 (PDT)
Received: by 10.52.161.198 with HTTP; Wed, 23 Mar 2011 23:33:45 -0700 (PDT)
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D6FB8BEACE@ILPTMAIL02.ecitele.com>
References: <4D88E3A7.4040502@cisco.com> <201103232025.p2NKPr2t076600@harbor.orleans.occnc.com> <AANLkTikNZH9w2iNRVwUAMmzJ2ktkjSfcdssNbEFvgNpr@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D6FB8BEACE@ILPTMAIL02.ecitele.com>
Date: Wed, 23 Mar 2011 23:33:45 -0700
Message-ID: <AANLkTikEKexHXCLyemCXM8u-H_UUpFAChAjBbEwCz_+1@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Content-Type: multipart/alternative; boundary=20cf307abd5fd0c651049f34a871
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, Robert Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [PWE3] [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 06:32:16 -0000

--20cf307abd5fd0c651049f34a871
Content-Type: text/plain; charset=ISO-8859-1

Dear Sasha,
I don't think that TP and non-TP networks should be peers, not server and
client to each other. Even though nothing precludes them from being peers. I
think that allowing TP and non-TP to be peers would create many, for
example, OAM issues since much of MPLS, i.e. IP/MPLS, is outside of scope of
MPLS-TP OAM. For instance, what is ME of merged LSP? Is it between LER's or
between LER and MP?

Regards,
Greg

On Wed, Mar 23, 2011 at 10:44 PM, Alexander Vainshtein <
Alexander.Vainshtein@ecitele.com> wrote:

>  Greg, Curtis and all,
> I think that the linkage between TP/non-TP differentiation and restrictions
> on GAL usage is highly problematic.
>
> E.g., consider an MS-PW with some segments crossing TP domains and some -
> non-TP ones (this is a realistic example).
>
> IMHO GAL is part of the data plane that is shared by IP/MPLS andMPLS-TP-TP, and hence the same restrictions shouldapply uniformly. IMHO RFC 5960 complies with this principle.
>
> RFC 5960 also seems to impose the restriction on GAL being at the bottom of
> stack. E.g., please look at the following text fragment:
>
>
>     If the TTL of an LSP label expires, then the label with the
>    S (Bottom of Stack) bit set is inspected to determine if it is a
>    reserved label.  If it is a reserved label, the packet is processed
>    according to the rules of that reserved label.  For example, if it is
>    a Generic Associated Channel Label (GAL), then it is processed as a
>    packet on the Generic Associated Channel (G-ACh); see Section 4.  If
>    the TTL of a PW expires at an S-PE or T-PE, then the packet is
>    examined to determine if a Generic Associated Channel Header (ACH) is
>    present immediately below the PW label.  If so, then the packet is
>    processed as a packet on the G-ACh.
>
>  And, last but not least, if we decide to allow GAL in the middle of the
> label stack (overriding RFC 5586 and RFC 5960), we must also define how a
> packet with GAL in the middle of the label stack is forwarded when GAL is
> exposed, similar to what has been done in RFC 3032 for RAL.
>
> My 2c,
>      Sasha
>
>
>  ------------------------------
> *From:* mpls-tp-bounces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of
> Greg Mirsky [gregimirsky@gmail.com]
> *Sent:* Wednesday, March 23, 2011 10:57 PM
> *To:* curtis@occnc.com
> *Cc:* Robert Rennison; mpls@ietf.org; mpls-tp@ietf.org;
> lihan@chinamobile.com; pwe3; HUANG Feng F
> *Subject:* Re: [mpls-tp] [PWE3] [mpls] WG LC
> draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>
>  Dear Curtis and All,
> I believe that any restriction on placing GAL in a label stack set in
> Section 4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs
> there are no restrictions set in RFC 5886 on where in a label stack GAL
> might appear. Some of use cases mentioned by Curtis are outside of MPLS-TP
> scope and, as I understand, use of GAL in these cases is not regulated by
> the RFC 5886.
> As to the issue of using GAL in PW there would not be a problem if not for
> possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4,
> properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886 -
> we might be good.
>
> Regards,
> Greg
>
> On Wed, Mar 23, 2011 at 1:25 PM, Curtis Villamizar <curtis@occnc.com>wrote:
>
>>
>> In message <4D88E3A7.4040502@cisco.com>
>> Stewart Bryant writes:
>> >
>> > If there is IETF consensus to update RFC5586 with this change then the
>> > process is relatively simple:
>> >
>> > The document making the update notes that it does the update, and the AD
>> > draws attention to
>> > this in the IETF LC.
>> >
>> > Stewart
>>
>>
>>  Stewart,
>>
>> The restriction that GAL be at the bottom of stack was simply a
>> mistake IMHO.  I stated that during MPLS WG discussion before it
>> became an RFC but it went through as is anyway with that restriction.
>> Even then it was said that if there were a strong reason to relax it
>> that it could be considered later.  That time may have come.
>>
>> There are a number of reasons that labels might want to go below GAL,
>> including to use OAM to diagnose the connectivity (or lack of) that is
>> experienced only for a specific label stack combinations where
>> multipath (link bundle, LAG, less applicable is ECMP in this case) is
>> used.
>>
>> In this case though, the GAL under the LSP label currently indicates
>> that after the POP that OAM needs to be done (or more accurately that
>> a G-Ach of some type is being carried).  If the GAL is put above the
>> PW label it is in that same place and there is an ambiguity.  It is an
>> ambiguity that for some but not all defined OAM can be resolved by
>> looking at information in BFD that makes it unambiguous.  Unless I'm
>> mistaken, in CC/CV the label stack above GAL provides the context.
>>
>> Another solution would be to put GAL under the PW label.  It would
>> probably be best to put GAL under PW but over the fat-pw label.  The
>> PW implementation, seeing the PW was not BOS, could look at the next
>> label to see if the label is reserved and specifically if it is GAL,
>> and if not process as payload (unless CW is also used).  If CW was not
>> used the only advantage is 4 bytes less in payload but the same size
>> in OAM packets.  This is an advantage though.
>>
>> On a related topic, if we must put ELI plus entropy label on the stack
>> we have saved nothing relative to fat-pw plus CW.  ELI as a
>> termination of hash search may have other uses though (MPLS-TP).
>>
>> I would be in favor of a very short draft just relaxing the
>> requirement that GAL be at the bottom of stack, independent of the
>> reason for doing so, since a number of reasons have emerged.  The
>> behavior would be to throw away the rest of the label stack when the
>> GAL label is exposed and look at the MPLS payload interpreting it as
>> an G-Ach channel (most often, but not exclusively, as OAM).  This
>> relaxation of the BOS restriction would be independent of usage.
>>
>> Curtis
>>
>>
>> > On 22/03/2011 16:22, Robert Rennison wrote:
>> > >
>> > > Luca, Thomas,
>> > >
>> > > A couple of clarification questions.
>> > >
>> > > I'm trying to understand what the combination of the two drafts,
>>  > > -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts to.
>> > >
>> > > So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it's
>> > > saying use VCCV type 1 where possible and if not then use the new type
>> > > 4, whereby  in type 4 the exception mechanism is triggered by the use
>> > > of the GAL,  and I appreciated the diagram in section 3 to lock this
>> > > is, so far so good.
>> > >
>> > > Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these two
>> > > drafts could work together since this one is trying to lay the "legal
>> > > framework" i.e fix up the RFCs which mandated that the GAL could not
>> > > be used with the PW.
>> > >
>> > > Then I get hit with a brick wall in the form of the statements in the
>> > > last 2 paras of section 3 of tp-gal-in-pw which state.
>> > >
>> > > - Section 4.2
>>  > > <
>> http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2
>> >.
>> > > (GAL Applicability and Usage) in [RFC5586
>>  > > <http://tools.ietf.org/html/rfc5586>], the
>>  > >
>> > >       original text:
>> > >
>> > >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>> > >
>> > >           LSPs, Concatenated Segments of LSPs, and with Sections, and
>> > >
>> > >           MUST NOT be used with PWs. It MUST always be at the bottom
>> of
>> > >
>> > >           the label stack (i.e., S bit set to 1). However, in other
>> MPLS
>> > >
>> > >           environments, this document places no restrictions on where
>> > >
>> > >           the GAL may appear within the label stack or its use with
>> PWs.
>> > >
>> > >       is replaced by:
>> > >
>> > >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>> > >
>> > >           LSPs, Concatenated Segments of LSPs, and with Sections, and
>> > >
>> > >           MAY be used with PWs. It MUST always be at the bottom of the
>> > >
>> > >           label stack (i.e., S bit set to 1). However, in other MPLS
>> > >
>> > >           environments, this document places no restrictions on where
>> > >
>> > >           the GAL may appear within the label stack.
>> > >
>> > > It's the bit about the GAL MUST be at the bottom of the label stack,
>> > > this is clearly inconsistent with what is proposed in the
>> > > draft-nadeau-pwe3 where one can clearly see the GAL above the PW label
>> > > and if one has to use  a GAL with a PW this would be the place to put
>> it,
>> > >
>> > > Now I can hear you saying "oh but look at the text below this, where
>> > > we state .."However, in other MPLS environments , this document places
>> > > no restrictions on where the GAL may appear within the label stack.
>> > > This is consistent with draft-nadeau "   In which case I'd retort with
>> > > ; what are we to do for PWs in   MPLS-TP, since what's in draft-nadeau
>> > > would not be allowed ?
>> > >
>> > > Clarification /explanation appreciated.
>> > >
>> > > Cheers
>> > >
>> > > Rob Rennison
>> > >
>>
>  [snipped ...]
>

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

Dear Sasha,<br>I don&#39;t think that TP and non-TP networks should be peer=
s, not server and client to each other. Even though nothing precludes them =
from being peers. I think that allowing TP and non-TP to be peers would cre=
ate many, for example, OAM issues since much of MPLS, i.e. IP/MPLS, is outs=
ide of scope of MPLS-TP OAM. For instance, what is ME of merged LSP? Is it =
between LER&#39;s or between LER and MP?<br>
<br>Regards,<br>Greg<br><br><div class=3D"gmail_quote">On Wed, Mar 23, 2011=
 at 10:44 PM, Alexander Vainshtein <span dir=3D"ltr">&lt;<a href=3D"mailto:=
Alexander.Vainshtein@ecitele.com">Alexander.Vainshtein@ecitele.com</a>&gt;<=
/span> wrote:<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 style=3D"font-size: 16px; color: rgb(0, 0, 0); direction: ltr; font-fa=
mily: Times New Roman;">
<div>Greg, Curtis and all,</div>
<div><font face=3D"times new roman">I think that the linkage between TP/non=
-TP differentiation and restrictions on GAL usage is highly problematic.</f=
ont></div>
<div><font face=3D"times new roman"></font>=A0</div>
<div><font face=3D"times new roman">E.g., consider an MS-PW with some segme=
nts crossing TP domains and some - non-TP ones (this is a realistic example=
).=A0
</font></div>
<div><font face=3D"times new roman"></font>=A0</div>
<div><font face=3D"times new roman">IMHO GAL is part of the data plane that=
 is=A0shared by IP/MPLS=A0and<a></a> MPLS-TP-TP, and hence the same restric=
tions=A0should<a></a> apply uniformly. IMHO RFC 5960 complies with this pri=
nciple.</font></div>

<div><font face=3D"times new roman"></font>=A0</div>
<div><font face=3D"times new roman">RFC 5960 also seems to impose the restr=
iction on GAL being at the bottom of stack. E.g., please look at=A0the<a></=
a> following text fragment:</font></div>
<div><font face=3D"times new roman"></font>=A0</div>
<blockquote dir=3D"ltr" style=3D"margin-right: 0px;">
<div><font face=3D"times new roman"><span style=3D"word-spacing: 0px; font:=
 medium &#39;Times New Roman&#39;; text-transform: none; color: rgb(0, 0, 0=
); text-indent: 0px; white-space: normal; letter-spacing: normal; border-co=
llapse: separate;"><span style=3D"font-size: 13px; line-height: 16px; font-=
family: arial,helvetica,clean,sans-serif;">
<pre style=3D"margin: 0px; line-height: 1.2em; font-family: monospace;">   =
If the TTL of an LSP label expires, then the label with the=20
   S (Bottom of Stack) bit set is inspected to determine if it is a
   reserved label.  If it is a reserved label, the packet is processed
   according to the rules of that reserved label.  For example, if it is
   a Generic Associated Channel Label (GAL), then it is processed as a
   packet on the Generic Associated Channel (G-ACh<a></a><a></a>); see Sect=
ion 4.  If
   the TTL of a PW expires at an S-PE or T-PE, then the packet is
   examined to determine if a Generic Associated Channel Header (ACH) is
   present immediately below the PW label.  If so, then the packet is
   processed as a packet on the G-ACh<a></a><a></a>.</pre>
</span></span></font></div>
</blockquote>
<div><font face=3D"times new roman">And, last but not least, if we decide t=
o allow GAL in the middle of the label stack (overriding RFC 5586 and RFC 5=
960), we must also define how a packet with GAL in the middle of the label =
stack is forwarded when GAL is exposed,
 similar to what has been done in RFC 3032 for RAL.</font></div>
<div><font face=3D"times new roman"></font>=A0</div>
<div><font face=3D"times new roman">My 2c,</font></div>
<div><font face=3D"times new roman">=A0=A0=A0=A0 Sasha</font></div>
<div><font face=3D"times new roman"></font>=A0</div>
<div dir=3D"ltr"><font color=3D"#000000" face=3D"Times New Roman" size=3D"3=
"></font>=A0</div>
<div style=3D"direction: ltr;">
<hr>
<font color=3D"#000000" face=3D"Tahoma" size=3D"2"><b>From:</b> <a href=3D"=
mailto:mpls-tp-bounces@ietf.org" target=3D"_blank">mpls-tp-bounces@ietf.org=
</a> [<a href=3D"mailto:mpls-tp-bounces@ietf.org" target=3D"_blank">mpls-tp=
-bounces@ietf.org</a>] On Behalf Of Greg Mirsky [<a href=3D"mailto:gregimir=
sky@gmail.com" target=3D"_blank">gregimirsky@gmail.com</a>]<br>

<b>Sent:</b> Wednesday, March 23, 2011 10:57 PM<br>
<b>To:</b> <a href=3D"mailto:curtis@occnc.com" target=3D"_blank">curtis@occ=
nc.com</a><br>
<b>Cc:</b> Robert Rennison; <a href=3D"mailto:mpls@ietf.org" target=3D"_bla=
nk">mpls@ietf.org</a>; <a href=3D"mailto:mpls-tp@ietf.org" target=3D"_blank=
">mpls-tp@ietf.org</a>; <a href=3D"mailto:lihan@chinamobile.com" target=3D"=
_blank">lihan@chinamobile.com</a>; pwe3; HUANG Feng F<br>

<b>Subject:</b> Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal=
-in-pw-00.txt<br>
</font><br>
</div><div><div></div><div class=3D"h5">
<div></div>
<div>Dear Curtis and All,<br>
I believe that any restriction on placing GAL in a label stack set in Secti=
on 4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs there ar=
e no restrictions set in RFC 5886 on where in a label stack GAL might appea=
r. Some of use cases mentioned by
 Curtis are outside of MPLS-TP scope and, as I understand, use of GAL in th=
ese cases is not regulated by the RFC 5886.<br>
As to the issue of using GAL in PW there would not be a problem if not for =
possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4=
, properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886=
 - we might be good.<br>

<br>
Regards,<br>
Greg<br>
<br>
<div class=3D"gmail_quote">On Wed, Mar 23, 2011 at 1:25 PM, Curtis Villamiz=
ar <span dir=3D"ltr">
&lt;<a href=3D"mailto:curtis@occnc.com" target=3D"_blank">curtis@occnc.com<=
/a>&gt;</span> 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);">
<br>
In message &lt;<a href=3D"mailto:4D88E3A7.4040502@cisco.com" target=3D"_bla=
nk">4D88E3A7.4040502@cisco.com</a>&gt;<br>
<div>Stewart Bryant writes:<br>
&gt;<br>
&gt; If there is IETF consensus to update RFC5586 with this change then the=
<br>
&gt; process is relatively simple:<br>
&gt;<br>
&gt; The document making the update notes that it does the update, and the =
AD<br>
&gt; draws attention to<br>
&gt; this in the IETF LC.<br>
&gt;<br>
&gt; Stewart<br>
<br>
<br>
</div>
Stewart,<br>
<br>
The restriction that GAL be at the bottom of stack was simply a<br>
mistake IMHO. =A0I stated that during MPLS WG discussion before it<br>
became an RFC but it went through as is anyway with that restriction.<br>
Even then it was said that if there were a strong reason to relax it<br>
that it could be considered later. =A0That time may have come.<br>
<br>
There are a number of reasons that labels might want to go below GAL,<br>
including to use OAM to diagnose the connectivity (or lack of) that is<br>
experienced only for a specific label stack combinations where<br>
multipath (link bundle, LAG, less applicable is ECMP in this case) is<br>
used.<br>
<br>
In this case though, the GAL under the LSP label currently indicates<br>
that after the POP that OAM needs to be done (or more accurately that<br>
a G-Ach of some type is being carried). =A0If the GAL is put above the<br>
PW label it is in that same place and there is an ambiguity. =A0It is an<br=
>
ambiguity that for some but not all defined OAM can be resolved by<br>
looking at information in BFD that makes it unambiguous. =A0Unless I&#39;m<=
br>
mistaken, in CC/CV the label stack above GAL provides the context.<br>
<br>
Another solution would be to put GAL under the PW label. =A0It would<br>
probably be best to put GAL under PW but over the fat-pw label. =A0The<br>
PW implementation, seeing the PW was not BOS, could look at the next<br>
label to see if the label is reserved and specifically if it is GAL,<br>
and if not process as payload (unless CW is also used). =A0If CW was not<br=
>
used the only advantage is 4 bytes less in payload but the same size<br>
in OAM packets. =A0This is an advantage though.<br>
<br>
On a related topic, if we must put ELI plus entropy label on the stack<br>
we have saved nothing relative to fat-pw plus CW. =A0ELI as a<br>
termination of hash search may have other uses though (MPLS-TP).<br>
<br>
I would be in favor of a very short draft just relaxing the<br>
requirement that GAL be at the bottom of stack, independent of the<br>
reason for doing so, since a number of reasons have emerged. =A0The<br>
behavior would be to throw away the rest of the label stack when the<br>
GAL label is exposed and look at the MPLS payload interpreting it as<br>
an G-Ach channel (most often, but not exclusively, as OAM). =A0This<br>
relaxation of the BOS restriction would be independent of usage.<br>
<br>
Curtis<br>
<div><br>
<br>
&gt; On 22/03/2011 16:22, Robert Rennison wrote:<br>
&gt; &gt;<br>
&gt; &gt; Luca, Thomas,<br>
&gt; &gt;<br>
&gt; &gt; A couple of clarification questions.<br>
&gt; &gt;<br>
&gt; &gt; I&#39;m trying to understand what the combination of the two draf=
ts,<br>
</div>
&gt; &gt; -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts t=
o.<br>
<div>&gt; &gt;<br>
&gt; &gt; So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it&=
#39;s<br>
&gt; &gt; saying use VCCV type 1 where possible and if not then use the new=
 type<br>
&gt; &gt; 4, whereby =A0in type 4 the exception mechanism is triggered by t=
he use<br>
&gt; &gt; of the GAL, =A0and I appreciated the diagram in section 3 to lock=
 this<br>
&gt; &gt; is, so far so good.<br>
&gt; &gt;<br>
&gt; &gt; Now I read -pwe3-mpls-tp-gal-in-pw and I&#39;m thinking , Ok thes=
e two<br>
&gt; &gt; drafts could work together since this one is trying to lay the &q=
uot;legal<br>
&gt; &gt; framework&quot; i.e fix up the RFCs which mandated that the GAL c=
ould not<br>
&gt; &gt; be used with the PW.<br>
&gt; &gt;<br>
&gt; &gt; Then I get hit with a brick wall in the form of the statements in=
 the<br>
&gt; &gt; last 2 paras of section 3 of tp-gal-in-pw which state.<br>
&gt; &gt;<br>
&gt; &gt; - Section 4.2<br>
</div>
&gt; &gt; &lt;<a href=3D"http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-g=
al-in-pw-00#section-4.2" target=3D"_blank">http://tools.ietf.org/html/draft=
-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2</a>&gt;.<br>
<div>&gt; &gt; (GAL Applicability and Usage) in [RFC5586<br>
</div>
&gt; &gt; &lt;<a href=3D"http://tools.ietf.org/html/rfc5586" target=3D"_bla=
nk">http://tools.ietf.org/html/rfc5586</a>&gt;], the<br>
<div>
<div></div>
<div>&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 original text:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 In MPLS-TP, the GAL MUST be used with packets=
 on a G-ACh on<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 LSPs, Concatenated Segments of LSPs, and with=
 Sections, and<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 MUST NOT be used with PWs. It MUST always be =
at the bottom of<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 the label stack (i.e., S bit set to 1). Howev=
er, in other MPLS<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 environments, this document places no restric=
tions on where<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 the GAL may appear within the label stack or =
its use with PWs.<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 is replaced by:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 In MPLS-TP, the GAL MUST be used with packets=
 on a G-ACh on<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 LSPs, Concatenated Segments of LSPs, and with=
 Sections, and<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 MAY be used with PWs. It MUST always be at th=
e bottom of the<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 label stack (i.e., S bit set to 1). However, =
in other MPLS<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 environments, this document places no restric=
tions on where<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0 the GAL may appear within the label stack.<br=
>
&gt; &gt;<br>
&gt; &gt; It&#39;s the bit about the GAL MUST be at the bottom of the label=
 stack,<br>
&gt; &gt; this is clearly inconsistent with what is proposed in the<br>
&gt; &gt; draft-nadeau-pwe3 where one can clearly see the GAL above the PW =
label<br>
&gt; &gt; and if one has to use =A0a GAL with a PW this would be the place =
to put it,<br>
&gt; &gt;<br>
&gt; &gt; Now I can hear you saying &quot;oh but look at the text below thi=
s, where<br>
&gt; &gt; we state ..&quot;However, in other MPLS environments , this docum=
ent places<br>
&gt; &gt; no restrictions on where the GAL may appear within the label stac=
k.<br>
&gt; &gt; This is consistent with draft-nadeau &quot; =A0 In which case I&#=
39;d retort with<br>
&gt; &gt; ; what are we to do for PWs in =A0 MPLS-TP, since what&#39;s in d=
raft-nadeau<br>
&gt; &gt; would not be allowed ?<br>
&gt; &gt;<br>
&gt; &gt; Clarification /explanation appreciated.<br>
&gt; &gt;<br>
&gt; &gt; Cheers<br>
&gt; &gt;<br>
&gt; &gt; Rob Rennison<br>
&gt; &gt;<br>
</div>
</div>
</blockquote>
</div>
[snipped ...]<br>
</div>
</div></div></div>
</div>

</blockquote></div><br>

--20cf307abd5fd0c651049f34a871--

From Alexander.Vainshtein@ecitele.com  Wed Mar 23 23:57:42 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6217A28B56A; Wed, 23 Mar 2011 23:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.024,  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 N9wEiVOHewle; Wed, 23 Mar 2011 23:57:40 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id D0C023A681B; Wed, 23 Mar 2011 23:57:34 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-e9-4d8aeb555937
Received: from ilptexch01.ecitele.com ( [172.31.244.40]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id 3B.FB.19639.55BEA8D4; Thu, 24 Mar 2011 08:57:25 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ilptexch01.ecitele.com ([172.31.244.40]) with mapi; Thu, 24 Mar 2011 08:59:07 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 24 Mar 2011 08:59:06 +0200
Thread-Topic: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Thread-Index: Acvp7W+jtuI8lyY6RYaU9LJSDSFsMAAAWBCJ
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6FB8BEAD0@ILPTMAIL02.ecitele.com>
References: <4D88E3A7.4040502@cisco.com> <201103232025.p2NKPr2t076600@harbor.orleans.occnc.com> <AANLkTikNZH9w2iNRVwUAMmzJ2ktkjSfcdssNbEFvgNpr@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D6FB8BEACE@ILPTMAIL02.ecitele.com>, <AANLkTikEKexHXCLyemCXM8u-H_UUpFAChAjBbEwCz_+1@mail.gmail.com>
In-Reply-To: <AANLkTikEKexHXCLyemCXM8u-H_UUpFAChAjBbEwCz_+1@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_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAD0ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, Robert Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [PWE3] [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 06:57:42 -0000

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAD0ILPTMAIL02eci_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Greg,
Lots of thanks for a prompt response.

I see the problem a bit differently:

 1.  RFC 5654 explicitly states that data plane interoperability between IP=
/MPLS and MPLS-TP "MUST NOT require a gateway function". I.e., nothing in t=
he data plane prevents the people from peering IP/MPLS and MPLS-TP domains.
 2.  Some forms of peering may be indeed problematic when it comes to OAM. =
But IMHO these problems do not exist in the case of MS-PWs  which perfectly=
 fit the definition of a co-routed bi-directional LSP in MPLS-TP (even if t=
hey have been defined before the MPLS-TP work has began).
 3.  I think it is high time to state explicitly that when it comes to PWs,=
 the IP/MPLS vs. MPLS-TP differentiation does not exist, be it in the data =
plane, OAM toolset, control plane or management plane. And, BTW, I believe =
that the original restriction of non-usage of GAL with PWs has been driven =
by implicit understanding of this fact.

My 2c,

     Sasha

________________________________
From: Greg Mirsky [gregimirsky@gmail.com]
Sent: Thursday, March 24, 2011 8:33 AM
To: Alexander Vainshtein
Cc: curtis@occnc.com; Robert Rennison; mpls@ietf.org; mpls-tp@ietf.org; lih=
an@chinamobile.com; pwe3; HUANG Feng F
Subject: Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-=
00.txt

Dear Sasha,
I don't think that TP and non-TP networks should be peers, not server and c=
lient to each other. Even though nothing precludes them from being peers. I=
 think that allowing TP and non-TP to be peers would create many, for examp=
le, OAM issues since much of MPLS, i.e. IP/MPLS, is outside of scope of MPL=
S-TP OAM. For instance, what is ME of merged LSP? Is it between LER's or be=
tween LER and MP?

Regards,
Greg

On Wed, Mar 23, 2011 at 10:44 PM, Alexander Vainshtein <Alexander.Vainshtei=
n@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
Greg, Curtis and all,
I think that the linkage between TP/non-TP differentiation and restrictions=
 on GAL usage is highly problematic.

E.g., consider an MS-PW with some segments crossing TP domains and some - n=
on-TP ones (this is a realistic example).

IMHO GAL is part of the data plane that is shared by IP/MPLS and MPLS-TP-TP=
, and hence the same restrictions should apply uniformly. IMHO RFC 5960 com=
plies with this principle.

RFC 5960 also seems to impose the restriction on GAL being at the bottom of=
 stack. E.g., please look at the following text fragment:


   If the TTL of an LSP label expires, then the label with the
   S (Bottom of Stack) bit set is inspected to determine if it is a
   reserved label.  If it is a reserved label, the packet is processed
   according to the rules of that reserved label.  For example, if it is
   a Generic Associated Channel Label (GAL), then it is processed as a
   packet on the Generic Associated Channel (G-ACh); see Section 4.  If
   the TTL of a PW expires at an S-PE or T-PE, then the packet is
   examined to determine if a Generic Associated Channel Header (ACH) is
   present immediately below the PW label.  If so, then the packet is
   processed as a packet on the G-ACh.

And, last but not least, if we decide to allow GAL in the middle of the lab=
el stack (overriding RFC 5586 and RFC 5960), we must also define how a pack=
et with GAL in the middle of the label stack is forwarded when GAL is expos=
ed, similar to what has been done in RFC 3032 for RAL.

My 2c,
     Sasha


________________________________
From: mpls-tp-bounces@ietf.org<mailto:mpls-tp-bounces@ietf.org> [mpls-tp-bo=
unces@ietf.org<mailto:mpls-tp-bounces@ietf.org>] On Behalf Of Greg Mirsky [=
gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>]
Sent: Wednesday, March 23, 2011 10:57 PM
To: curtis@occnc.com<mailto:curtis@occnc.com>
Cc: Robert Rennison; mpls@ietf.org<mailto:mpls@ietf.org>; mpls-tp@ietf.org<=
mailto:mpls-tp@ietf.org>; lihan@chinamobile.com<mailto:lihan@chinamobile.co=
m>; pwe3; HUANG Feng F
Subject: Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-=
00.txt

Dear Curtis and All,
I believe that any restriction on placing GAL in a label stack set in Secti=
on 4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs there ar=
e no restrictions set in RFC 5886 on where in a label stack GAL might appea=
r. Some of use cases mentioned by Curtis are outside of MPLS-TP scope and, =
as I understand, use of GAL in these cases is not regulated by the RFC 5886=
.
As to the issue of using GAL in PW there would not be a problem if not for =
possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4=
, properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886=
 - we might be good.

Regards,
Greg

On Wed, Mar 23, 2011 at 1:25 PM, Curtis Villamizar <curtis@occnc.com<mailto=
:curtis@occnc.com>> wrote:

In message <4D88E3A7.4040502@cisco.com<mailto:4D88E3A7.4040502@cisco.com>>
Stewart Bryant writes:
>
> If there is IETF consensus to update RFC5586 with this change then the
> process is relatively simple:
>
> The document making the update notes that it does the update, and the AD
> draws attention to
> this in the IETF LC.
>
> Stewart


Stewart,

The restriction that GAL be at the bottom of stack was simply a
mistake IMHO.  I stated that during MPLS WG discussion before it
became an RFC but it went through as is anyway with that restriction.
Even then it was said that if there were a strong reason to relax it
that it could be considered later.  That time may have come.

There are a number of reasons that labels might want to go below GAL,
including to use OAM to diagnose the connectivity (or lack of) that is
experienced only for a specific label stack combinations where
multipath (link bundle, LAG, less applicable is ECMP in this case) is
used.

In this case though, the GAL under the LSP label currently indicates
that after the POP that OAM needs to be done (or more accurately that
a G-Ach of some type is being carried).  If the GAL is put above the
PW label it is in that same place and there is an ambiguity.  It is an
ambiguity that for some but not all defined OAM can be resolved by
looking at information in BFD that makes it unambiguous.  Unless I'm
mistaken, in CC/CV the label stack above GAL provides the context.

Another solution would be to put GAL under the PW label.  It would
probably be best to put GAL under PW but over the fat-pw label.  The
PW implementation, seeing the PW was not BOS, could look at the next
label to see if the label is reserved and specifically if it is GAL,
and if not process as payload (unless CW is also used).  If CW was not
used the only advantage is 4 bytes less in payload but the same size
in OAM packets.  This is an advantage though.

On a related topic, if we must put ELI plus entropy label on the stack
we have saved nothing relative to fat-pw plus CW.  ELI as a
termination of hash search may have other uses though (MPLS-TP).

I would be in favor of a very short draft just relaxing the
requirement that GAL be at the bottom of stack, independent of the
reason for doing so, since a number of reasons have emerged.  The
behavior would be to throw away the rest of the label stack when the
GAL label is exposed and look at the MPLS payload interpreting it as
an G-Ach channel (most often, but not exclusively, as OAM).  This
relaxation of the BOS restriction would be independent of usage.

Curtis


> On 22/03/2011 16:22, Robert Rennison wrote:
> >
> > Luca, Thomas,
> >
> > A couple of clarification questions.
> >
> > I'm trying to understand what the combination of the two drafts,
> > -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts to.
> >
> > So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it's
> > saying use VCCV type 1 where possible and if not then use the new type
> > 4, whereby  in type 4 the exception mechanism is triggered by the use
> > of the GAL,  and I appreciated the diagram in section 3 to lock this
> > is, so far so good.
> >
> > Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these two
> > drafts could work together since this one is trying to lay the "legal
> > framework" i.e fix up the RFCs which mandated that the GAL could not
> > be used with the PW.
> >
> > Then I get hit with a brick wall in the form of the statements in the
> > last 2 paras of section 3 of tp-gal-in-pw which state.
> >
> > - Section 4.2
> > <http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-=
4.2>.
> > (GAL Applicability and Usage) in [RFC5586
> > <http://tools.ietf.org/html/rfc5586>], the
> >
> >       original text:
> >
> >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> >
> >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> >
> >           MUST NOT be used with PWs. It MUST always be at the bottom of
> >
> >           the label stack (i.e., S bit set to 1). However, in other MPL=
S
> >
> >           environments, this document places no restrictions on where
> >
> >           the GAL may appear within the label stack or its use with PWs=
.
> >
> >       is replaced by:
> >
> >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> >
> >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> >
> >           MAY be used with PWs. It MUST always be at the bottom of the
> >
> >           label stack (i.e., S bit set to 1). However, in other MPLS
> >
> >           environments, this document places no restrictions on where
> >
> >           the GAL may appear within the label stack.
> >
> > It's the bit about the GAL MUST be at the bottom of the label stack,
> > this is clearly inconsistent with what is proposed in the
> > draft-nadeau-pwe3 where one can clearly see the GAL above the PW label
> > and if one has to use  a GAL with a PW this would be the place to put i=
t,
> >
> > Now I can hear you saying "oh but look at the text below this, where
> > we state .."However, in other MPLS environments , this document places
> > no restrictions on where the GAL may appear within the label stack.
> > This is consistent with draft-nadeau "   In which case I'd retort with
> > ; what are we to do for PWs in   MPLS-TP, since what's in draft-nadeau
> > would not be allowed ?
> >
> > Clarification /explanation appreciated.
> >
> > Cheers
> >
> > Rob Rennison
> >
[snipped ...]


--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAD0ILPTMAIL02eci_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta content=3D"MSHTML 6.00.6000.17063" name=3D"GENERATOR">
<style id=3D"owaTempEditStyle"></style><style title=3D"owaParaStyle"><!--P =
{
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi=3D"x">
<div style=3D"FONT-SIZE: 16px; COLOR: #000000; DIRECTION: ltr; FONT-FAMILY:=
 Times New Roman">
<div>Greg,</div>
<div><font face=3D"times new roman">Lots of thanks for a prompt response.</=
font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">I see the problem a bit differently:</f=
ont></div>
<ol>
<li><font face=3D"times new roman">RFC 5654 explicitly states that data pla=
ne interoperability between IP/MPLS and MPLS-TP &quot;MUST NOT require a ga=
teway function&quot;. I.e., nothing in the data plane prevents the people f=
rom peering IP/MPLS and MPLS-TP domains.</font>
</li><li><font face=3D"times new roman">Some forms of peering may be indeed=
 problematic when it comes to OAM. But IMHO these problems do not exist in =
the case of MS-PWs&nbsp; which perfectly fit the definition of a co-routed =
bi-directional LSP in MPLS-TP (even if they
 have been defined before the MPLS-TP work has began). </font></li><li><fon=
t face=3D"times new roman">I think it is high time to state explicitly that=
 when it comes to PWs, the IP/MPLS vs. MPLS-TP differentiation does not exi=
st, be it in the data plane, OAM toolset, control plane or management plane=
. And, BTW, I believe that
 the original restriction of non-usage of GAL with PWs has been driven by i=
mplicit understanding of this fact.</font></li></ol>
<p><font face=3D"times new roman"></font><font face=3D"Times New Roman" col=
or=3D"#000000" size=3D"3">My 2c,</font></p>
<p><font face=3D"times new roman">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</font></p>
<div id=3D"divRpF949719" style=3D"DIRECTION: ltr">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" color=3D"#000000" size=3D"2"><b>From:</b> Greg Mirsky=
 [gregimirsky@gmail.com]<br>
<b>Sent:</b> Thursday, March 24, 2011 8:33 AM<br>
<b>To:</b> Alexander Vainshtein<br>
<b>Cc:</b> curtis@occnc.com; Robert Rennison; mpls@ietf.org; mpls-tp@ietf.o=
rg; lihan@chinamobile.com; pwe3; HUANG Feng F<br>
<b>Subject:</b> Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal=
-in-pw-00.txt<br>
</font><br>
</div>
<div></div>
<div>Dear Sasha,<br>
I don't think that TP and non-TP networks should be peers, not server and c=
lient to each other. Even though nothing precludes them from being peers. I=
 think that allowing TP and non-TP to be peers would create many, for examp=
le, OAM issues since much of MPLS,
 i.e. IP/MPLS, is outside of scope of MPLS-TP OAM. For instance, what is ME=
 of merged LSP? Is it between LER's or between LER and MP?<br>
<br>
Regards,<br>
Greg<br>
<br>
<div class=3D"gmail_quote">On Wed, Mar 23, 2011 at 10:44 PM, Alexander Vain=
shtein <span dir=3D"ltr">
&lt;<a href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshtei=
n@ecitele.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0=
pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<div>
<div style=3D"FONT-SIZE: 16px; COLOR: rgb(0,0,0); DIRECTION: ltr; FONT-FAMI=
LY: Times New Roman">
<div>Greg, Curtis and all,</div>
<div><font face=3D"times new roman">I think that the linkage between TP/non=
-TP differentiation and restrictions on GAL usage is highly problematic.</f=
ont></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">E.g., consider an MS-PW with some segme=
nts crossing TP domains and some - non-TP ones (this is a realistic example=
).&nbsp;
</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">IMHO GAL is part of the data plane that=
 is&nbsp;shared by IP/MPLS&nbsp;and<a></a> MPLS-TP-TP, and hence the same r=
estrictions&nbsp;should<a></a> apply uniformly. IMHO RFC 5960 complies with=
 this principle.</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">RFC 5960 also seems to impose the restr=
iction on GAL being at the bottom of stack. E.g., please look at&nbsp;the<a=
></a> following text fragment:</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<blockquote dir=3D"ltr" style=3D"MARGIN-RIGHT: 0px">
<div><font face=3D"times new roman"><span style=3D"WORD-SPACING: 0px; FONT:=
 medium 'Times New Roman'; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-IN=
DENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: se=
parate"><span style=3D"FONT-SIZE: 13px; LINE-HEIGHT: 16px; FONT-FAMILY: ari=
al,helvetica,clean,sans-serif">
<pre style=3D"MARGIN: 0px; LINE-HEIGHT: 1.2em; FONT-FAMILY: monospace">   I=
f the TTL of an LSP label expires, then the label with the=20
   S (Bottom of Stack) bit set is inspected to determine if it is a
   reserved label.  If it is a reserved label, the packet is processed
   according to the rules of that reserved label.  For example, if it is
   a Generic Associated Channel Label (GAL), then it is processed as a
   packet on the Generic Associated Channel (G-ACh<a></a><a></a>); see Sect=
ion 4.  If
   the TTL of a PW expires at an S-PE or T-PE, then the packet is
   examined to determine if a Generic Associated Channel Header (ACH) is
   present immediately below the PW label.  If so, then the packet is
   processed as a packet on the G-ACh<a></a><a></a>.</pre>
</span></span></font></div>
</blockquote>
<div><font face=3D"times new roman">And, last but not least, if we decide t=
o allow GAL in the middle of the label stack (overriding RFC 5586 and RFC 5=
960), we must also define how a packet with GAL in the middle of the label =
stack is forwarded when GAL is exposed,
 similar to what has been done in RFC 3032 for RAL.</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">My 2c,</font></div>
<div><font face=3D"times new roman">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</font></=
div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"Times New Roman" color=3D"#000000" size=3D"3=
"></font>&nbsp;</div>
<div style=3D"DIRECTION: ltr">
<hr>
<font face=3D"Tahoma" color=3D"#000000" size=3D"2"><b>From:</b> <a href=3D"=
mailto:mpls-tp-bounces@ietf.org">
mpls-tp-bounces@ietf.org</a> [<a href=3D"mailto:mpls-tp-bounces@ietf.org">m=
pls-tp-bounces@ietf.org</a>] On Behalf Of Greg Mirsky [<a href=3D"mailto:gr=
egimirsky@gmail.com">gregimirsky@gmail.com</a>]<br>
<b>Sent:</b> Wednesday, March 23, 2011 10:57 PM<br>
<b>To:</b> <a href=3D"mailto:curtis@occnc.com">curtis@occnc.com</a><br>
<b>Cc:</b> Robert Rennison; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org<=
/a>; <a href=3D"mailto:mpls-tp@ietf.org">
mpls-tp@ietf.org</a>; <a href=3D"mailto:lihan@chinamobile.com">lihan@chinam=
obile.com</a>; pwe3; HUANG Feng F<br>
<b>Subject:</b> Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal=
-in-pw-00.txt<br>
</font><br>
</div>
<div>
<div></div>
<div class=3D"h5">
<div></div>
<div>Dear Curtis and All,<br>
I believe that any restriction on placing GAL in a label stack set in Secti=
on 4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs there ar=
e no restrictions set in RFC 5886 on where in a label stack GAL might appea=
r. Some of use cases mentioned by
 Curtis are outside of MPLS-TP scope and, as I understand, use of GAL in th=
ese cases is not regulated by the RFC 5886.<br>
As to the issue of using GAL in PW there would not be a problem if not for =
possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4=
, properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886=
 - we might be good.<br>
<br>
Regards,<br>
Greg<br>
<br>
<div class=3D"gmail_quote">On Wed, Mar 23, 2011 at 1:25 PM, Curtis Villamiz=
ar <span dir=3D"ltr">
&lt;<a href=3D"mailto:curtis@occnc.com">curtis@occnc.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0=
pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<br>
In message &lt;<a href=3D"mailto:4D88E3A7.4040502@cisco.com">4D88E3A7.40405=
02@cisco.com</a>&gt;<br>
<div>Stewart Bryant writes:<br>
&gt;<br>
&gt; If there is IETF consensus to update RFC5586 with this change then the=
<br>
&gt; process is relatively simple:<br>
&gt;<br>
&gt; The document making the update notes that it does the update, and the =
AD<br>
&gt; draws attention to<br>
&gt; this in the IETF LC.<br>
&gt;<br>
&gt; Stewart<br>
<br>
<br>
</div>
Stewart,<br>
<br>
The restriction that GAL be at the bottom of stack was simply a<br>
mistake IMHO. &nbsp;I stated that during MPLS WG discussion before it<br>
became an RFC but it went through as is anyway with that restriction.<br>
Even then it was said that if there were a strong reason to relax it<br>
that it could be considered later. &nbsp;That time may have come.<br>
<br>
There are a number of reasons that labels might want to go below GAL,<br>
including to use OAM to diagnose the connectivity (or lack of) that is<br>
experienced only for a specific label stack combinations where<br>
multipath (link bundle, LAG, less applicable is ECMP in this case) is<br>
used.<br>
<br>
In this case though, the GAL under the LSP label currently indicates<br>
that after the POP that OAM needs to be done (or more accurately that<br>
a G-Ach of some type is being carried). &nbsp;If the GAL is put above the<b=
r>
PW label it is in that same place and there is an ambiguity. &nbsp;It is an=
<br>
ambiguity that for some but not all defined OAM can be resolved by<br>
looking at information in BFD that makes it unambiguous. &nbsp;Unless I'm<b=
r>
mistaken, in CC/CV the label stack above GAL provides the context.<br>
<br>
Another solution would be to put GAL under the PW label. &nbsp;It would<br>
probably be best to put GAL under PW but over the fat-pw label. &nbsp;The<b=
r>
PW implementation, seeing the PW was not BOS, could look at the next<br>
label to see if the label is reserved and specifically if it is GAL,<br>
and if not process as payload (unless CW is also used). &nbsp;If CW was not=
<br>
used the only advantage is 4 bytes less in payload but the same size<br>
in OAM packets. &nbsp;This is an advantage though.<br>
<br>
On a related topic, if we must put ELI plus entropy label on the stack<br>
we have saved nothing relative to fat-pw plus CW. &nbsp;ELI as a<br>
termination of hash search may have other uses though (MPLS-TP).<br>
<br>
I would be in favor of a very short draft just relaxing the<br>
requirement that GAL be at the bottom of stack, independent of the<br>
reason for doing so, since a number of reasons have emerged. &nbsp;The<br>
behavior would be to throw away the rest of the label stack when the<br>
GAL label is exposed and look at the MPLS payload interpreting it as<br>
an G-Ach channel (most often, but not exclusively, as OAM). &nbsp;This<br>
relaxation of the BOS restriction would be independent of usage.<br>
<br>
Curtis<br>
<div><br>
<br>
&gt; On 22/03/2011 16:22, Robert Rennison wrote:<br>
&gt; &gt;<br>
&gt; &gt; Luca, Thomas,<br>
&gt; &gt;<br>
&gt; &gt; A couple of clarification questions.<br>
&gt; &gt;<br>
&gt; &gt; I'm trying to understand what the combination of the two drafts,<=
br>
</div>
&gt; &gt; -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts t=
o.<br>
<div>&gt; &gt;<br>
&gt; &gt; So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it'=
s<br>
&gt; &gt; saying use VCCV type 1 where possible and if not then use the new=
 type<br>
&gt; &gt; 4, whereby &nbsp;in type 4 the exception mechanism is triggered b=
y the use<br>
&gt; &gt; of the GAL, &nbsp;and I appreciated the diagram in section 3 to l=
ock this<br>
&gt; &gt; is, so far so good.<br>
&gt; &gt;<br>
&gt; &gt; Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these tw=
o<br>
&gt; &gt; drafts could work together since this one is trying to lay the &q=
uot;legal<br>
&gt; &gt; framework&quot; i.e fix up the RFCs which mandated that the GAL c=
ould not<br>
&gt; &gt; be used with the PW.<br>
&gt; &gt;<br>
&gt; &gt; Then I get hit with a brick wall in the form of the statements in=
 the<br>
&gt; &gt; last 2 paras of section 3 of tp-gal-in-pw which state.<br>
&gt; &gt;<br>
&gt; &gt; - Section 4.2<br>
</div>
&gt; &gt; &lt;<a href=3D"http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-g=
al-in-pw-00#section-4.2" target=3D"_blank">http://tools.ietf.org/html/draft=
-lm-pwe3-mpls-tp-gal-in-pw-00#section-4.2</a>&gt;.<br>
<div>&gt; &gt; (GAL Applicability and Usage) in [RFC5586<br>
</div>
&gt; &gt; &lt;<a href=3D"http://tools.ietf.org/html/rfc5586" target=3D"_bla=
nk">http://tools.ietf.org/html/rfc5586</a>&gt;], the<br>
<div>
<div></div>
<div>&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; original text:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; In MPLS-TP, the GAL MUST be us=
ed with packets on a G-ACh on<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; LSPs, Concatenated Segments of=
 LSPs, and with Sections, and<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; MUST NOT be used with PWs. It =
MUST always be at the bottom of<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the label stack (i.e., S bit s=
et to 1). However, in other MPLS<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; environments, this document pl=
aces no restrictions on where<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the GAL may appear within the =
label stack or its use with PWs.<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; is replaced by:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; In MPLS-TP, the GAL MUST be us=
ed with packets on a G-ACh on<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; LSPs, Concatenated Segments of=
 LSPs, and with Sections, and<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; MAY be used with PWs. It MUST =
always be at the bottom of the<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; label stack (i.e., S bit set t=
o 1). However, in other MPLS<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; environments, this document pl=
aces no restrictions on where<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the GAL may appear within the =
label stack.<br>
&gt; &gt;<br>
&gt; &gt; It's the bit about the GAL MUST be at the bottom of the label sta=
ck,<br>
&gt; &gt; this is clearly inconsistent with what is proposed in the<br>
&gt; &gt; draft-nadeau-pwe3 where one can clearly see the GAL above the PW =
label<br>
&gt; &gt; and if one has to use &nbsp;a GAL with a PW this would be the pla=
ce to put it,<br>
&gt; &gt;<br>
&gt; &gt; Now I can hear you saying &quot;oh but look at the text below thi=
s, where<br>
&gt; &gt; we state ..&quot;However, in other MPLS environments , this docum=
ent places<br>
&gt; &gt; no restrictions on where the GAL may appear within the label stac=
k.<br>
&gt; &gt; This is consistent with draft-nadeau &quot; &nbsp; In which case =
I'd retort with<br>
&gt; &gt; ; what are we to do for PWs in &nbsp; MPLS-TP, since what's in dr=
aft-nadeau<br>
&gt; &gt; would not be allowed ?<br>
&gt; &gt;<br>
&gt; &gt; Clarification /explanation appreciated.<br>
&gt; &gt;<br>
&gt; &gt; Cheers<br>
&gt; &gt;<br>
&gt; &gt; Rob Rennison<br>
&gt; &gt;<br>
</div>
</div>
</blockquote>
</div>
[snipped ...]<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</body>
</html>

--_000_A3C5DF08D38B6049839A6F553B331C76D6FB8BEAD0ILPTMAIL02eci_--

From neil.2.harrison@bt.com  Thu Mar 24 01:31:39 2011
Return-Path: <neil.2.harrison@bt.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5007D3A6833; Thu, 24 Mar 2011 01:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.445
X-Spam-Level: 
X-Spam-Status: No, score=-1.445 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_21=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 Im9BHqaNxZ9z; Thu, 24 Mar 2011 01:31:24 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp61.intersmtp.COM [62.239.224.234]) by core3.amsl.com (Postfix) with ESMTP id E6F5A3A6781; Thu, 24 Mar 2011 01:31:22 -0700 (PDT)
Received: from EVMHT63-UKRD.domain1.systemhost.net (10.36.3.100) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.3.106.1; Thu, 24 Mar 2011 08:32:56 +0000
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.1.172]) by EVMHT63-UKRD.domain1.systemhost.net ([10.36.3.100]) with mapi; Thu, 24 Mar 2011 08:32:56 +0000
From: <neil.2.harrison@bt.com>
To: <gregimirsky@gmail.com>, <Alexander.Vainshtein@ecitele.com>
Date: Thu, 24 Mar 2011 08:32:51 +0000
Thread-Topic: [PWE3] [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
Thread-Index: Acvp7Xexw6I54ApFRpaCTLho1fXt9wAC0BDw
Message-ID: <6D3D47CB84BDE349BC23BF1C94E316E44019726CA5@EMV62-UKRD.domain1.systemhost.net>
References: <4D88E3A7.4040502@cisco.com> <201103232025.p2NKPr2t076600@harbor.orleans.occnc.com> <AANLkTikNZH9w2iNRVwUAMmzJ2ktkjSfcdssNbEFvgNpr@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D6FB8BEACE@ILPTMAIL02.ecitele.com> <AANLkTikEKexHXCLyemCXM8u-H_UUpFAChAjBbEwCz_+1@mail.gmail.com>
In-Reply-To: <AANLkTikEKexHXCLyemCXM8u-H_UUpFAChAjBbEwCz_+1@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: multipart/alternative; boundary="_000_6D3D47CB84BDE349BC23BF1C94E316E44019726CA5EMV62UKRDdoma_"
MIME-Version: 1.0
Cc: mpls@ietf.org, Feng.f.Huang@alcatel-sbell.com.cn, lihan@chinamobile.com, pwe3@ietf.org, mpls-tp@ietf.org, Robert.Rennison@ecitele.com
Subject: Re: [PWE3] [mpls-tp] [mpls] WG LC	draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 08:31:39 -0000

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

Guys, some hints on what is architecturally at fault here and why folks are=
 seeing problems:

1      First, we have the rather important observation that in a properly d=
esigned MPLS co-ps mode transport network there should not be traditional L=
SP sublayering and there should never be PWs.  I'm not going to go over thi=
s again here, but the fundamental service a transport network provides to i=
ts clients is *transparency*.....and whether folks like it or not tradition=
al LSP sublayering and PWs are clear evidence that we do not have a transpa=
rent layer network specification in MPLS-TP.


2      Secondly, Greg is semi-correct below when he has there is no need fo=
r peering in TP with non-TP.  In fact the more general/accurate architectur=
al point here is that there is no need for peering in any layer network mod=
e/technology that is not TOS (Top-of-Stack) and does not interface directly=
 (via suitable adaptation functions) with external message/file/stream appl=
ications.  MPLS (any spin) is NOT a TOS layer network (indeed most layer ne=
tworks are not TOS)...IP can be TOS of course, though there are problems in=
 ensuring deterministic resource management which is why we don't generally=
 use the cl-ps mode as a transport network for client layer topology build.


3      Thirdly, all layer networks should have consistent Characteristic In=
formation (CI).....in other words we know a priori the structure of PDUs an=
d the semantics of the fields contained therein.  This is rather important =
when things go wrong and traffic gets misdirected, ie wrt to correct proces=
sing of the PDUs at some arbitrary trail termination point where they might=
 arrive.  Sadly the notion of consistent CI is compromised in MPLS as the t=
raffic unit is so functionally sparse that the label field ends up stunt-do=
ubling for lots of different functions (besides the key one of a forwarding=
 DA proxy semantic).

Now the reason I mention this is that the special labels 0-15 should have a=
n immediate and well-known global CI semantic...one should not have go delv=
ing under the label here to infer meaning.

One of the key design behaviours of a transport network is the logical sepa=
ration of the DP from the CP/MP (this is actually a forced behaviour in the=
 co-cs mode (eg see GMPLS), but has to be consciously designed in the co-ps=
 mode).  Now the GAL should IMO only have this logical OOB CP/MP function..=
.it should not also be being used as a DP OAM indicate function....this is =
muddying-up the consistent CI point up again when there is no need to.

The right way to do the latter should be by using a single bit of the norma=
l *DP* traffic unit overhead.  Of course, in any properly designed transpor=
t network one has no need for a TTL function as the CP/MP MUST ensure a loo=
p-free scenario before establishing a connection...indeed there is no TTL f=
unction in GMPLS networks.  So in MPLS-TP we have essentially 8 wasted bits=
 of scarce overhead, so one of these bits should have been used as an OAM i=
ndicate function.  However, given this is deemed too unpalatable (even thou=
gh a TTL function is clearly a technical nonsense in a transport network) w=
e should have a different reserved label for the DP OAM from that of the CP=
/MP.


regards, Neil

Email: neil.2.harrison@bt.com<mailto:neil.2.harrison@bt.com>
Web: www.bt.com<http://www.bt.com/>
This email contains BT information, which may be privileged or confidential=
.
It's meant only for the individual(s) or entity named above. If you're not =
the intended
recipient, note that disclosing, copying, distributing or using this inform=
ation
is prohibited. If you've received this email in error, please let me know i=
mmediately
on the email address above. Thank you.
We monitor our email system, and may record your emails.
British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no: 1800000





From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Gre=
g Mirsky
Sent: 24 March 2011 06:34
To: Alexander Vainshtein
Cc: mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.com; pwe3; HUANG Fen=
g F; Robert Rennison
Subject: Re: [PWE3] [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-=
00.txt

Dear Sasha,
I don't think that TP and non-TP networks should be peers, not server and c=
lient to each other. Even though nothing precludes them from being peers. I=
 think that allowing TP and non-TP to be peers would create many, for examp=
le, OAM issues since much of MPLS, i.e. IP/MPLS, is outside of scope of MPL=
S-TP OAM. For instance, what is ME of merged LSP? Is it between LER's or be=
tween LER and MP?

Regards,
Greg
On Wed, Mar 23, 2011 at 10:44 PM, Alexander Vainshtein <Alexander.Vainshtei=
n@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
Greg, Curtis and all,
I think that the linkage between TP/non-TP differentiation and restrictions=
 on GAL usage is highly problematic.

E.g., consider an MS-PW with some segments crossing TP domains and some - n=
on-TP ones (this is a realistic example).

IMHO GAL is part of the data plane that is shared by IP/MPLS and MPLS-TP-TP=
, and hence the same restrictions should apply uniformly. IMHO RFC 5960 com=
plies with this principle.

RFC 5960 also seems to impose the restriction on GAL being at the bottom of=
 stack. E.g., please look at the following text fragment:


   If the TTL of an LSP label expires, then the label with the

   S (Bottom of Stack) bit set is inspected to determine if it is a

   reserved label.  If it is a reserved label, the packet is processed

   according to the rules of that reserved label.  For example, if it is

   a Generic Associated Channel Label (GAL), then it is processed as a

   packet on the Generic Associated Channel (G-ACh); see Section 4.  If

   the TTL of a PW expires at an S-PE or T-PE, then the packet is

   examined to determine if a Generic Associated Channel Header (ACH) is

   present immediately below the PW label.  If so, then the packet is

   processed as a packet on the G-ACh.
And, last but not least, if we decide to allow GAL in the middle of the lab=
el stack (overriding RFC 5586 and RFC 5960), we must also define how a pack=
et with GAL in the middle of the label stack is forwarded when GAL is expos=
ed, similar to what has been done in RFC 3032 for RAL.

My 2c,
     Sasha


________________________________
From: mpls-tp-bounces@ietf.org<mailto:mpls-tp-bounces@ietf.org> [mpls-tp-bo=
unces@ietf.org<mailto:mpls-tp-bounces@ietf.org>] On Behalf Of Greg Mirsky [=
gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>]
Sent: Wednesday, March 23, 2011 10:57 PM
To: curtis@occnc.com<mailto:curtis@occnc.com>
Cc: Robert Rennison; mpls@ietf.org<mailto:mpls@ietf.org>; mpls-tp@ietf.org<=
mailto:mpls-tp@ietf.org>; lihan@chinamobile.com<mailto:lihan@chinamobile.co=
m>; pwe3; HUANG Feng F
Subject: Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-=
00.txt
Dear Curtis and All,
I believe that any restriction on placing GAL in a label stack set in Secti=
on 4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs there ar=
e no restrictions set in RFC 5886 on where in a label stack GAL might appea=
r. Some of use cases mentioned by Curtis are outside of MPLS-TP scope and, =
as I understand, use of GAL in these cases is not regulated by the RFC 5886=
.
As to the issue of using GAL in PW there would not be a problem if not for =
possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4=
, properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886=
 - we might be good.

Regards,
Greg
On Wed, Mar 23, 2011 at 1:25 PM, Curtis Villamizar <curtis@occnc.com<mailto=
:curtis@occnc.com>> wrote:

In message <4D88E3A7.4040502@cisco.com<mailto:4D88E3A7.4040502@cisco.com>>
Stewart Bryant writes:
>
> If there is IETF consensus to update RFC5586 with this change then the
> process is relatively simple:
>
> The document making the update notes that it does the update, and the AD
> draws attention to
> this in the IETF LC.
>
> Stewart

Stewart,

The restriction that GAL be at the bottom of stack was simply a
mistake IMHO.  I stated that during MPLS WG discussion before it
became an RFC but it went through as is anyway with that restriction.
Even then it was said that if there were a strong reason to relax it
that it could be considered later.  That time may have come.

There are a number of reasons that labels might want to go below GAL,
including to use OAM to diagnose the connectivity (or lack of) that is
experienced only for a specific label stack combinations where
multipath (link bundle, LAG, less applicable is ECMP in this case) is
used.

In this case though, the GAL under the LSP label currently indicates
that after the POP that OAM needs to be done (or more accurately that
a G-Ach of some type is being carried).  If the GAL is put above the
PW label it is in that same place and there is an ambiguity.  It is an
ambiguity that for some but not all defined OAM can be resolved by
looking at information in BFD that makes it unambiguous.  Unless I'm
mistaken, in CC/CV the label stack above GAL provides the context.

Another solution would be to put GAL under the PW label.  It would
probably be best to put GAL under PW but over the fat-pw label.  The
PW implementation, seeing the PW was not BOS, could look at the next
label to see if the label is reserved and specifically if it is GAL,
and if not process as payload (unless CW is also used).  If CW was not
used the only advantage is 4 bytes less in payload but the same size
in OAM packets.  This is an advantage though.

On a related topic, if we must put ELI plus entropy label on the stack
we have saved nothing relative to fat-pw plus CW.  ELI as a
termination of hash search may have other uses though (MPLS-TP).

I would be in favor of a very short draft just relaxing the
requirement that GAL be at the bottom of stack, independent of the
reason for doing so, since a number of reasons have emerged.  The
behavior would be to throw away the rest of the label stack when the
GAL label is exposed and look at the MPLS payload interpreting it as
an G-Ach channel (most often, but not exclusively, as OAM).  This
relaxation of the BOS restriction would be independent of usage.

Curtis


> On 22/03/2011 16:22, Robert Rennison wrote:
> >
> > Luca, Thomas,
> >
> > A couple of clarification questions.
> >
> > I'm trying to understand what the combination of the two drafts,
> > -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts to.
> >
> > So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it's
> > saying use VCCV type 1 where possible and if not then use the new type
> > 4, whereby  in type 4 the exception mechanism is triggered by the use
> > of the GAL,  and I appreciated the diagram in section 3 to lock this
> > is, so far so good.
> >
> > Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these two
> > drafts could work together since this one is trying to lay the "legal
> > framework" i.e fix up the RFCs which mandated that the GAL could not
> > be used with the PW.
> >
> > Then I get hit with a brick wall in the form of the statements in the
> > last 2 paras of section 3 of tp-gal-in-pw which state.
> >
> > - Section 4.2
> > <http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-=
4.2>.
> > (GAL Applicability and Usage) in [RFC5586
> > <http://tools.ietf.org/html/rfc5586>], the
> >
> >       original text:
> >
> >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> >
> >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> >
> >           MUST NOT be used with PWs. It MUST always be at the bottom of
> >
> >           the label stack (i.e., S bit set to 1). However, in other MPL=
S
> >
> >           environments, this document places no restrictions on where
> >
> >           the GAL may appear within the label stack or its use with PWs=
.
> >
> >       is replaced by:
> >
> >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> >
> >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> >
> >           MAY be used with PWs. It MUST always be at the bottom of the
> >
> >           label stack (i.e., S bit set to 1). However, in other MPLS
> >
> >           environments, this document places no restrictions on where
> >
> >           the GAL may appear within the label stack.
> >
> > It's the bit about the GAL MUST be at the bottom of the label stack,
> > this is clearly inconsistent with what is proposed in the
> > draft-nadeau-pwe3 where one can clearly see the GAL above the PW label
> > and if one has to use  a GAL with a PW this would be the place to put i=
t,
> >
> > Now I can hear you saying "oh but look at the text below this, where
> > we state .."However, in other MPLS environments , this document places
> > no restrictions on where the GAL may appear within the label stack.
> > This is consistent with draft-nadeau "   In which case I'd retort with
> > ; what are we to do for PWs in   MPLS-TP, since what's in draft-nadeau
> > would not be allowed ?
> >
> > Clarification /explanation appreciated.
> >
> > Cheers
> >
> > Rob Rennison
> >
[snipped ...]


--_000_6D3D47CB84BDE349BC23BF1C94E316E44019726CA5EMV62UKRDdoma_
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:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Verdana","sans-serif";
	color:#632423;
	font-weight:normal;
	font-style:normal;}
.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-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'>Guys,
some hints on what is architecturally at fault here and why folks are seein=
g
problems:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'>1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; First,
we have the rather important observation that in a properly designed MPLS c=
o-ps
mode transport network there should not be traditional LSP sublayering and =
there
should never be PWs.&nbsp; I&#8217;m not going to go over this again here, =
but
the fundamental service a transport network provides to its clients is *tra=
nsparency*.....and
whether folks like it or not traditional LSP sublayering and PWs are clear =
evidence
that we do not have a transparent layer network specification in MPLS-TP.<o=
:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'>2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Secondly,
Greg is semi-correct below when he has there is no need for peering in TP w=
ith
non-TP.&nbsp; In fact the more general/accurate architectural point here is
that there is no need for peering in any layer network mode/technology that=
 is
not TOS (Top-of-Stack) and does not interface directly (via suitable adapta=
tion
functions) with external message/file/stream applications.&nbsp; MPLS (any
spin) is NOT a TOS layer network (indeed most layer networks are not TOS)..=
.IP
can be TOS of course, though there are problems in ensuring deterministic
resource management which is why we don&#8217;t generally use the cl-ps mod=
e as
a transport network for client layer topology build.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'>3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thirdly,
all layer networks should have consistent Characteristic Information (CI)..=
...in
other words we know a priori the structure of PDUs and the semantics of the=
 fields
contained therein.&nbsp; This is rather important when things go wrong and
traffic gets misdirected, ie wrt to correct processing of the PDUs at some =
arbitrary
trail termination point where they might arrive.&nbsp; Sadly the notion of
consistent CI is compromised in MPLS as the traffic unit is so functionally=
 sparse
that the label field ends up stunt-doubling for lots of different functions=
 (besides
the key one of a forwarding DA proxy semantic).<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'>Now
the reason I mention this is that the special labels 0-15 should have an im=
mediate
and well-known global CI semantic...one should not have go delving under th=
e
label here to infer meaning. <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'>One
of the key design behaviours of a transport network is the logical separati=
on of
the DP from the CP/MP (this is actually a forced behaviour in the co-cs mod=
e
(eg see GMPLS), but has to be consciously designed in the co-ps mode).&nbsp=
;
Now the GAL should IMO only have this logical OOB CP/MP function...it shoul=
d
not also be being used as a DP OAM indicate function....this is muddying-up=
 the
consistent CI point up again when there is no need to.<o:p></o:p></span></p=
>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'>The
right way to do the latter should be by using a single bit of the normal *D=
P* traffic
unit overhead.&nbsp; Of course, in any properly designed transport network =
one
has no need for a TTL function as the CP/MP MUST ensure a loop-free scenari=
o
before establishing a connection...indeed there is no TTL function in GMPLS
networks.&nbsp; So in MPLS-TP we have essentially 8 wasted bits of scarce
overhead, so one of these bits should have been used as an OAM indicate
function. &nbsp;However, given this is deemed too unpalatable (even though =
a TTL
function is clearly a technical nonsense in a transport network) we should =
have
a different reserved label for the DP OAM from that of the CP/MP.<o:p></o:p=
></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'>regards,
Neil<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:5.0pt;margin-right:0cm;mar=
gin-bottom:
5.0pt;margin-left:0cm;text-autospace:none'><span style=3D'font-size:9.0pt;
font-family:"Calibri","sans-serif";color:gray'>Email: <a
href=3D"mailto:neil.2.harrison@bt.com"><span style=3D'color:gray'>neil.2.ha=
rrison@bt.com</span></a><br>
Web: <a href=3D"http://www.bt.com/"><span style=3D'color:gray'>www.bt.com</=
span></a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:5.0pt;margin-right:0cm;mar=
gin-bottom:
5.0pt;margin-left:0cm;text-autospace:none'><span style=3D'font-size:7.0pt;
font-family:"Calibri","sans-serif";color:gray'>This email contains BT
information, which may be privileged or confidential.<br>
It's meant only for the individual(s) or entity named above. If you're not =
the
intended<br>
recipient, note that disclosing, copying, distributing or using this
information<br>
is prohibited. If you've received this email in error, please let me know
immediately<br>
on the email address above. Thank you.<br>
We monitor our email system, and may record your emails.<o:p></o:p></span><=
/p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span style=3D'font-size=
:7.0pt;
font-family:"Calibri","sans-serif";color:gray'>British Telecommunications p=
lc<br>
Registered office: 81 Newgate Street London EC1A 7AJ<br>
Registered in England no: 1800000</span><span style=3D'font-size:10.0pt;
font-family:"Comic Sans MS";color:maroon'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-family:"Verdana","sans-serif";colo=
r:#632423'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font-f=
amily:
"Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US style=3D'font-siz=
e:10.0pt;
font-family:"Tahoma","sans-serif"'> pwe3-bounces@ietf.org
[mailto:pwe3-bounces@ietf.org] <b>On Behalf Of </b>Greg Mirsky<br>
<b>Sent:</b> 24 March 2011 06:34<br>
<b>To:</b> Alexander Vainshtein<br>
<b>Cc:</b> mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.com; pwe3; HU=
ANG
Feng F; Robert Rennison<br>
<b>Subject:</b> Re: [PWE3] [mpls-tp] [mpls] WG LC
draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Dear Sasha,<br>
I don't think that TP and non-TP networks should be peers, not server and
client to each other. Even though nothing precludes them from being peers. =
I
think that allowing TP and non-TP to be peers would create many, for exampl=
e,
OAM issues since much of MPLS, i.e. IP/MPLS, is outside of scope of MPLS-TP
OAM. For instance, what is ME of merged LSP? Is it between LER's or between=
 LER
and MP?<br>
<br>
Regards,<br>
Greg<o:p></o:p></p>

<div>

<p class=3DMsoNormal>On Wed, Mar 23, 2011 at 10:44 PM, Alexander Vainshtein=
 &lt;<a
href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshtein@ecite=
le.com</a>&gt;
wrote:<o:p></o:p></p>

<div>

<div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>Greg, Curtis and all,<o:p>=
</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>I think that the linkage b=
etween
TP/non-TP differentiation and restrictions on GAL usage is highly problemat=
ic.<o:p></o:p></span></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>E.g., consider an MS-PW wi=
th some
segments crossing TP domains and some - non-TP ones (this is a realistic
example).&nbsp; <o:p></o:p></span></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>IMHO GAL is part of the da=
ta plane
that is&nbsp;shared by IP/MPLS&nbsp;and MPLS-TP-TP, and hence the same
restrictions&nbsp;should apply uniformly. IMHO RFC 5960 complies with this
principle.<o:p></o:p></span></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>RFC 5960 also seems to imp=
ose the
restriction on GAL being at the bottom of stack. E.g., please look at&nbsp;=
the
following text fragment:<o:p></o:p></span></p>

</div>

<div>

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

</div>

<blockquote style=3D'margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'=
>

<div><pre style=3D'line-height:14.4pt'><span style=3D'color:black'>&nbsp;&n=
bsp; If the TTL of an LSP label expires, then the label with the <o:p></o:p=
></span></pre><pre
style=3D'line-height:14.4pt'><span style=3D'color:black'>&nbsp;&nbsp;&nbsp;=
S (Bottom of Stack) bit set is inspected to determine if it is a<o:p></o:p>=
</span></pre><pre
style=3D'line-height:14.4pt'><span style=3D'color:black'>&nbsp;&nbsp; reser=
ved label.&nbsp; If it is a reserved label, the packet is processed<o:p></o=
:p></span></pre><pre
style=3D'line-height:14.4pt'><span style=3D'color:black'>&nbsp;&nbsp; accor=
ding to the rules of that reserved label.&nbsp; For example, if it is<o:p><=
/o:p></span></pre><pre
style=3D'line-height:14.4pt'><span style=3D'color:black'>&nbsp;&nbsp; a Gen=
eric Associated Channel Label (GAL), then it is processed as a<o:p></o:p></=
span></pre><pre
style=3D'line-height:14.4pt'><span style=3D'color:black'>&nbsp;&nbsp; packe=
t on the Generic Associated Channel (G-ACh); see Section 4.&nbsp; If<o:p></=
o:p></span></pre><pre
style=3D'line-height:14.4pt'><span style=3D'color:black'>&nbsp;&nbsp; the T=
TL of a PW expires at an S-PE or T-PE, then the packet is<o:p></o:p></span>=
</pre><pre
style=3D'line-height:14.4pt'><span style=3D'color:black'>&nbsp;&nbsp; exami=
ned to determine if a Generic Associated Channel Header (ACH) is<o:p></o:p>=
</span></pre><pre
style=3D'line-height:14.4pt'><span style=3D'color:black'>&nbsp;&nbsp; prese=
nt immediately below the PW label.&nbsp; If so, then the packet is<o:p></o:=
p></span></pre><pre
style=3D'line-height:14.4pt'><span style=3D'color:black'>&nbsp;&nbsp; proce=
ssed as a packet on the G-ACh.<o:p></o:p></span></pre></div>

</blockquote>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>And, last but not least, i=
f we
decide to allow GAL in the middle of the label stack (overriding RFC 5586 a=
nd
RFC 5960), we must also define how a packet with GAL in the middle of the l=
abel
stack is forwarded when GAL is exposed, similar to what has been done in RF=
C
3032 for RAL.<o:p></o:p></span></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>My 2c,<o:p></o:p></span></=
p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>&nbsp;&nbsp;&nbsp;&nbsp; S=
asha<o:p></o:p></span></p>

</div>

<div>

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

</div>

<div>

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

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'color:black'>

<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";color:black'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> <=
a
href=3D"mailto:mpls-tp-bounces@ietf.org" target=3D"_blank">mpls-tp-bounces@=
ietf.org</a>
[<a href=3D"mailto:mpls-tp-bounces@ietf.org" target=3D"_blank">mpls-tp-boun=
ces@ietf.org</a>]
On Behalf Of Greg Mirsky [<a href=3D"mailto:gregimirsky@gmail.com" target=
=3D"_blank">gregimirsky@gmail.com</a>]<br>
<b>Sent:</b> Wednesday, March 23, 2011 10:57 PM<br>
<b>To:</b> <a href=3D"mailto:curtis@occnc.com" target=3D"_blank">curtis@occ=
nc.com</a><br>
<b>Cc:</b> Robert Rennison; <a href=3D"mailto:mpls@ietf.org" target=3D"_bla=
nk">mpls@ietf.org</a>;
<a href=3D"mailto:mpls-tp@ietf.org" target=3D"_blank">mpls-tp@ietf.org</a>;=
 <a
href=3D"mailto:lihan@chinamobile.com" target=3D"_blank">lihan@chinamobile.c=
om</a>;
pwe3; HUANG Feng F<br>
<b>Subject:</b> Re: [mpls-tp] [PWE3] [mpls] WG LC
draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt</span><span style=3D'color:black'><o=
:p></o:p></span></p>

</div>

<div>

<div>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span style=3D'color:bl=
ack'>Dear
Curtis and All,<br>
I believe that any restriction on placing GAL in a label stack set in Secti=
on
4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs there are n=
o
restrictions set in RFC 5886 on where in a label stack GAL might appear. So=
me
of use cases mentioned by Curtis are outside of MPLS-TP scope and, as I
understand, use of GAL in these cases is not regulated by the RFC 5886.<br>
As to the issue of using GAL in PW there would not be a problem if not for
possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4=
, properly
updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886 - we might=
 be
good.<br>
<br>
Regards,<br>
Greg<o:p></o:p></span></p>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>On Wed, Mar 23, 2011 at 1:=
25 PM,
Curtis Villamizar &lt;<a href=3D"mailto:curtis@occnc.com" target=3D"_blank"=
>curtis@occnc.com</a>&gt;
wrote:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><br>
In message &lt;<a href=3D"mailto:4D88E3A7.4040502@cisco.com" target=3D"_bla=
nk">4D88E3A7.4040502@cisco.com</a>&gt;<o:p></o:p></span></p>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span style=3D'color:bl=
ack'>Stewart
Bryant writes:<br>
&gt;<br>
&gt; If there is IETF consensus to update RFC5586 with this change then the=
<br>
&gt; process is relatively simple:<br>
&gt;<br>
&gt; The document making the update notes that it does the update, and the =
AD<br>
&gt; draws attention to<br>
&gt; this in the IETF LC.<br>
&gt;<br>
&gt; Stewart<br>
<br>
<o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><span style=3D'color:black'>Stewart,<br>
<br>
The restriction that GAL be at the bottom of stack was simply a<br>
mistake IMHO. &nbsp;I stated that during MPLS WG discussion before it<br>
became an RFC but it went through as is anyway with that restriction.<br>
Even then it was said that if there were a strong reason to relax it<br>
that it could be considered later. &nbsp;That time may have come.<br>
<br>
There are a number of reasons that labels might want to go below GAL,<br>
including to use OAM to diagnose the connectivity (or lack of) that is<br>
experienced only for a specific label stack combinations where<br>
multipath (link bundle, LAG, less applicable is ECMP in this case) is<br>
used.<br>
<br>
In this case though, the GAL under the LSP label currently indicates<br>
that after the POP that OAM needs to be done (or more accurately that<br>
a G-Ach of some type is being carried). &nbsp;If the GAL is put above the<b=
r>
PW label it is in that same place and there is an ambiguity. &nbsp;It is an=
<br>
ambiguity that for some but not all defined OAM can be resolved by<br>
looking at information in BFD that makes it unambiguous. &nbsp;Unless I'm<b=
r>
mistaken, in CC/CV the label stack above GAL provides the context.<br>
<br>
Another solution would be to put GAL under the PW label. &nbsp;It would<br>
probably be best to put GAL under PW but over the fat-pw label. &nbsp;The<b=
r>
PW implementation, seeing the PW was not BOS, could look at the next<br>
label to see if the label is reserved and specifically if it is GAL,<br>
and if not process as payload (unless CW is also used). &nbsp;If CW was not=
<br>
used the only advantage is 4 bytes less in payload but the same size<br>
in OAM packets. &nbsp;This is an advantage though.<br>
<br>
On a related topic, if we must put ELI plus entropy label on the stack<br>
we have saved nothing relative to fat-pw plus CW. &nbsp;ELI as a<br>
termination of hash search may have other uses though (MPLS-TP).<br>
<br>
I would be in favor of a very short draft just relaxing the<br>
requirement that GAL be at the bottom of stack, independent of the<br>
reason for doing so, since a number of reasons have emerged. &nbsp;The<br>
behavior would be to throw away the rest of the label stack when the<br>
GAL label is exposed and look at the MPLS payload interpreting it as<br>
an G-Ach channel (most often, but not exclusively, as OAM). &nbsp;This<br>
relaxation of the BOS restriction would be independent of usage.<br>
<br>
Curtis<o:p></o:p></span></p>

<div>

<p class=3DMsoNormal><span style=3D'color:black'><br>
<br>
&gt; On 22/03/2011 16:22, Robert Rennison wrote:<br>
&gt; &gt;<br>
&gt; &gt; Luca, Thomas,<br>
&gt; &gt;<br>
&gt; &gt; A couple of clarification questions.<br>
&gt; &gt;<br>
&gt; &gt; I'm trying to understand what the combination of the two drafts,<=
o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><span style=3D'color:black'>&gt; &gt;
-lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts to.<o:p></o=
:p></span></p>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>&gt; &gt;<br>
&gt; &gt; So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it'=
s<br>
&gt; &gt; saying use VCCV type 1 where possible and if not then use the new
type<br>
&gt; &gt; 4, whereby &nbsp;in type 4 the exception mechanism is triggered b=
y
the use<br>
&gt; &gt; of the GAL, &nbsp;and I appreciated the diagram in section 3 to l=
ock
this<br>
&gt; &gt; is, so far so good.<br>
&gt; &gt;<br>
&gt; &gt; Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these tw=
o<br>
&gt; &gt; drafts could work together since this one is trying to lay the
&quot;legal<br>
&gt; &gt; framework&quot; i.e fix up the RFCs which mandated that the GAL c=
ould
not<br>
&gt; &gt; be used with the PW.<br>
&gt; &gt;<br>
&gt; &gt; Then I get hit with a brick wall in the form of the statements in=
 the<br>
&gt; &gt; last 2 paras of section 3 of tp-gal-in-pw which state.<br>
&gt; &gt;<br>
&gt; &gt; - Section 4.2<o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><span style=3D'color:black'>&gt; &gt; &lt;<a
href=3D"http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#secti=
on-4.2"
target=3D"_blank">http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-p=
w-00#section-4.2</a>&gt;.<o:p></o:p></span></p>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>&gt; &gt; (GAL Applicabili=
ty and
Usage) in [RFC5586<o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><span style=3D'color:black'>&gt; &gt; &lt;<a
href=3D"http://tools.ietf.org/html/rfc5586" target=3D"_blank">http://tools.=
ietf.org/html/rfc5586</a>&gt;],
the<o:p></o:p></span></p>

<div>

<div>

<p class=3DMsoNormal><span style=3D'color:black'>&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; original text:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; In MPLS-TP, the GAL MUST be us=
ed
with packets on a G-ACh on<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; LSPs, Concatenated Segments of
LSPs, and with Sections, and<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; MUST NOT be used with PWs. It =
MUST
always be at the bottom of<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the label stack (i.e., S bit s=
et
to 1). However, in other MPLS<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; environments, this document pl=
aces
no restrictions on where<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the GAL may appear within the
label stack or its use with PWs.<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; is replaced by:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; In MPLS-TP, the GAL MUST be us=
ed
with packets on a G-ACh on<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; LSPs, Concatenated Segments of
LSPs, and with Sections, and<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; MAY be used with PWs. It MUST
always be at the bottom of the<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; label stack (i.e., S bit set t=
o
1). However, in other MPLS<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; environments, this document pl=
aces
no restrictions on where<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the GAL may appear within the
label stack.<br>
&gt; &gt;<br>
&gt; &gt; It's the bit about the GAL MUST be at the bottom of the label sta=
ck,<br>
&gt; &gt; this is clearly inconsistent with what is proposed in the<br>
&gt; &gt; draft-nadeau-pwe3 where one can clearly see the GAL above the PW =
label<br>
&gt; &gt; and if one has to use &nbsp;a GAL with a PW this would be the pla=
ce
to put it,<br>
&gt; &gt;<br>
&gt; &gt; Now I can hear you saying &quot;oh but look at the text below thi=
s,
where<br>
&gt; &gt; we state ..&quot;However, in other MPLS environments , this docum=
ent
places<br>
&gt; &gt; no restrictions on where the GAL may appear within the label stac=
k.<br>
&gt; &gt; This is consistent with draft-nadeau &quot; &nbsp; In which case =
I'd
retort with<br>
&gt; &gt; ; what are we to do for PWs in &nbsp; MPLS-TP, since what's in
draft-nadeau<br>
&gt; &gt; would not be allowed ?<br>
&gt; &gt;<br>
&gt; &gt; Clarification /explanation appreciated.<br>
&gt; &gt;<br>
&gt; &gt; Cheers<br>
&gt; &gt;<br>
&gt; &gt; Rob Rennison<br>
&gt; &gt;<o:p></o:p></span></p>

</div>

</div>

</div>

<p class=3DMsoNormal><span style=3D'color:black'>[snipped ...]<o:p></o:p></=
span></p>

</div>

</div>

</div>

</div>

</div>

</div>

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

</div>

</div>

</body>

</html>

--_000_6D3D47CB84BDE349BC23BF1C94E316E44019726CA5EMV62UKRDdoma_--

From david.sinicrope@ericsson.com  Thu Mar 24 10:19:48 2011
Return-Path: <david.sinicrope@ericsson.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F12383A68F0 for <pwe3@core3.amsl.com>; Thu, 24 Mar 2011 10:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, 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 8D+StncI3mgl for <pwe3@core3.amsl.com>; Thu, 24 Mar 2011 10:19:47 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id D43A73A67FC for <pwe3@ietf.org>; Thu, 24 Mar 2011 10:19:46 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2OHLIwl001499 for <pwe3@ietf.org>; Thu, 24 Mar 2011 12:21:21 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.203]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Thu, 24 Mar 2011 13:21:17 -0400
From: David Sinicrope <david.sinicrope@ericsson.com>
To: "IETF.PWE3" <pwe3@ietf.org>
Date: Thu, 24 Mar 2011 13:21:15 -0400
Thread-Topic: [PWE3] Draft PWE3 Agenda for IETF 80 - Prague
Thread-Index: AcvqR+J9MclMAUw1T8udZSqL1AgJXg==
Message-ID: <C9B0F585.42050%david.sinicrope@ericsson.com>
In-Reply-To: <C9A810CF.41687%david.sinicrope@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PWE3] Draft PWE3 Agenda for IETF 80 - Prague
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 17:19:48 -0000

I received 3 sets of slides so far... Presenters please send me your
slides for the meeting.
Thanks,
Dave

-----Original Message-----
From: David Sinicrope  <david.sinicrope@ericsson.com>
Date: Thu, 17 Mar 2011 19:26:07 -0400
To: "IETF.PWE3" <pwe3@ietf.org>
Subject: [PWE3] Draft PWE3 Agenda for IETF 80 - Prague

>I posted the draft agenda for the PWE3 session of IETF 80 in Prague.
>Please check and ensure I reflected your slot request.  Order of
>presentations is subject to change.
>Those who have slots, please start sending me your presentations for
>upload.
>Thanks!
>Dave
>
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www.ietf.org/mailman/listinfo/pwe3


From stbryant@cisco.com  Fri Mar 25 01:57:07 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EAA43A6985 for <pwe3@core3.amsl.com>; Fri, 25 Mar 2011 01:57:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.467
X-Spam-Level: 
X-Spam-Status: No, score=-110.467 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 9PMCtolJpB3N for <pwe3@core3.amsl.com>; Fri, 25 Mar 2011 01:57:06 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id D74F93A6984 for <pwe3@ietf.org>; Fri, 25 Mar 2011 01:57:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=2349; q=dns/txt; s=iport; t=1301043521; x=1302253121; h=message-id:date:from:reply-to:mime-version:to:cc:subject: content-transfer-encoding; bh=pY8XBU4zNIjoARYXGfDb+kGLxIRXD213juIBK3/wtGI=; b=AI6Makm+qDoB96enHA2zZCc/mXPqryxUIQiRrLYugrWa6XLIgLvdfa82 93oWaVzaXVU4gd2dRk6peZ2DmNGftNa6TayiGhnFmiRES6CRw5RezWeiT LCVNCbs8O2koKXtOL7A2e8MlDYPs7sFOxQvSU1Cuq3CECJecoaynnkR07 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AosEAPBYjE2Q/khMgWdsb2JhbACERKENFAEBFiYlp2SCbw4BiD2RHoEng0t3BIx1
X-IronPort-AV: E=Sophos;i="4.63,242,1299456000"; d="scan'208";a="80777089"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 25 Mar 2011 08:58:25 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2P8wP4V026994; Fri, 25 Mar 2011 08:58:25 GMT
Received: from dhcp-1222.meeting.ietf.org (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p2P8wKU17145; Fri, 25 Mar 2011 08:58:25 GMT
Message-ID: <4D8C592C.6010802@cisco.com>
Date: Fri, 25 Mar 2011 08:58:20 +0000
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.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-li-pwe3-ms-pw-pon@tools.ietf.org
Subject: [PWE3] draft-li-pwe3-ms-pw-pon-03
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2011 08:57:07 -0000

I have received a request to sponsor this draft to publication,
and believe that the draft is worth publication.

The draft is not within the scope of PWE3, but none-the-less,
review by members of the PWE3 WG would be useful.

Please can I have any review comments  by 18th April.

Thanks

Stewart


> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> Sent: 11 March 2011 14:27
> To: hongyu.lihongyu@huawei.com
> Cc: robin@huawei.com; Adrian.Farrel@huawei.com
> Subject: New Version Notification for draft-li-pwe3-ms-pw-pon-03
>
>
> A new version of I-D, draft-li-pwe3-ms-pw-pon-03.txt has been successfully
> submitted by Li Hongyu and posted to the IETF repository.
>
> Filename:	 draft-li-pwe3-ms-pw-pon
> Revision:	 03
> Title:		 Multisegment Pseudowires in Passive Optical Networks
> Creation_date:	 2011-03-11
> WG ID:		 Independent Submission
> Number_of_pages: 12
>
> Abstract:
> This document describes the application of MPLS multi-segment
> pseudowires (MS-PWs) in a dual-technology environment comprising a
> Passive Optical Network (PON) and an MPLS Packet Switched Network
> (PSN).
>
> PON technology may be used in mobile backhaul networks to support the
> end segments closest to the aggregation devices.  In these cases,
> there may be a very large number of PW Terminating Provider Edge
> nodes (T-PEs).  The MPLS control plane could be used to provision
> these end segments, but support for the necessary protocols would
> complicate the management of the T-PEs and would significantly
> increase their expense.  Alternatively, static, or management plane,
> configuration could be used to configure the end segments, but the
> very large number of such segments in a PON places a very heavy
> burden on the network manager.
>
> This document describes how to set up the end segment of an end-to-
> end MPLS PW over a Gigabit-capable Passive Optical Network (GPON)
> using the GPON management protocol, Optical Network Termination
> Management and Control Interface (OMCI).  This simplifies and speeds
> up PW provisioning.
>
> This document also shows how a MS-PW may be constructed from an end
> segment supported over a PON, and stitched to one or more segments
> supported over an MPLS PSN.
>
>
>
> The IETF Secretariat.




From curtis@occnc.com  Fri Mar 25 19:01:44 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C23928C0D6; Fri, 25 Mar 2011 19:01:44 -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 cokGVTy6vMtH; Fri, 25 Mar 2011 19:01: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 70DAE3A6877; Fri, 25 Mar 2011 19:01:42 -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 p2Q22vsK065505; Fri, 25 Mar 2011 22:02:57 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103260202.p2Q22vsK065505@harbor.orleans.occnc.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 24 Mar 2011 07:44:39 +0200." <A3C5DF08D38B6049839A6F553B331C76D6FB8BEACE@ILPTMAIL02.ecitele.com> 
Date: Fri, 25 Mar 2011 22:02:57 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, Robert Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [PWE3] [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Mar 2011 02:01:44 -0000

In message <A3C5DF08D38B6049839A6F553B331C76D6FB8BEACE@ILPTMAIL02.ecitele.com>
Alexander Vainshtein writes:
>  
> Greg, Curtis and all,
> I think that the linkage between TP/non-TP differentiation and restrictions=
>  on GAL usage is highly problematic.

Yes.  I agree.

> E.g., consider an MS-PW with some segments crossing TP domains and some - n=
> on-TP ones (this is a realistic example).
>  
> IMHO GAL is part of the data plane that is shared by IP/MPLS and MPLS-TP-TP=
> , and hence the same restrictions should apply uniformly. IMHO RFC 5960 com=
> plies with this principle.
>  
> RFC 5960 also seems to impose the restriction on GAL being at the bottom of=
>  stack. E.g., please look at the following text fragment:
>  
>  
>    If the TTL of an LSP label expires, then the label with the
>    S (Bottom of Stack) bit set is inspected to determine if it is a
>    reserved label.  If it is a reserved label, the packet is processed
>    according to the rules of that reserved label.  For example, if it is
>    a Generic Associated Channel Label (GAL), then it is processed as a
>    packet on the Generic Associated Channel (G-ACh); see Section 4.  If
>    the TTL of a PW expires at an S-PE or T-PE, then the packet is
>    examined to determine if a Generic Associated Channel Header (ACH) is
>    present immediately below the PW label.  If so, then the packet is
>    processed as a packet on the G-ACh.

This is used in the traceroute cacpability where TTL is set to a low
value and increased until the egress is reached.

This would have to be changed to look for GAL in any position, not
just at the bottom of stack.  If each label entry has to be inspected,
this is about the same effort as looking for the S bit (bit test vs
mask and 20 bit compare).  This only occurs on TTL expired, which is
always more work than normal forwarding.

The alternate, to keep fate-sharing, is to put GAL under the fat-pw
label in a PW.  This requires more work on every packet forwarded to
check for this additional label.  Some hardware (none I've had a hand
in designing) assumes that a PW has a fixed overhead below it and
looks for zero in CW at a fixed offset from the PW label.

Keeping GAL on the bottom, trying to acheive fate-sharing with fat-pw,
and putting GAL below the fat-pw, would burden the common case of
forwarding.  Allowing GAL anywhere burdens the far less common TTL
expired processing operation.

> And, last but not least, if we decide to allow GAL in the middle of the lab=
> el stack (overriding RFC 5586 and RFC 5960), we must also define how a pack=
> et with GAL in the middle of the label stack is forwarded when GAL is expos=
> ed, similar to what has been done in RFC 3032 for RAL.
>  
> My 2c,
>      Sasha

If GAL is encountered, then it is processed just as it would be if TTL
was set high and GAL was encountered as a result of the final POP in a
containing LSP exposing only the GAL.  The G-Ach is after the bottom
of stack, where ever bottom of stack is found.

Curtis

> ________________________________
> From: mpls-tp-bounces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of Greg=
>  Mirsky [gregimirsky@gmail.com]
> Sent: Wednesday, March 23, 2011 10:57 PM
> To: curtis@occnc.com
> Cc: Robert Rennison; mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.com=
> ; pwe3; HUANG Feng F
> Subject: Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-=
> 00.txt
>  
> Dear Curtis and All,
> I believe that any restriction on placing GAL in a label stack set in Secti=
> on 4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs there ar=
> e no restrictions set in RFC 5886 on where in a label stack GAL might appea=
> r. Some of use cases mentioned by Curtis are outside of MPLS-TP scope and, =
> as I understand, use of GAL in these cases is not regulated by the RFC 5886=
> .
> As to the issue of using GAL in PW there would not be a problem if not for =
> possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type 4=
> , properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 5886=
>  - we might be good.
>  
> Regards,
> Greg
>  
> On Wed, Mar 23, 2011 at 1:25 PM, Curtis Villamizar <curtis@occnc.com<mailto=
> :curtis@occnc.com>> wrote:
>  
> In message <4D88E3A7.4040502@cisco.com<mailto:4D88E3A7.4040502@cisco.com>>
> Stewart Bryant writes:
> >
> > If there is IETF consensus to update RFC5586 with this change then the
> > process is relatively simple:
> >
> > The document making the update notes that it does the update, and the AD
> > draws attention to
> > this in the IETF LC.
> >
> > Stewart
>  
>  
> Stewart,
>  
> The restriction that GAL be at the bottom of stack was simply a
> mistake IMHO.  I stated that during MPLS WG discussion before it
> became an RFC but it went through as is anyway with that restriction.
> Even then it was said that if there were a strong reason to relax it
> that it could be considered later.  That time may have come.
>  
> There are a number of reasons that labels might want to go below GAL,
> including to use OAM to diagnose the connectivity (or lack of) that is
> experienced only for a specific label stack combinations where
> multipath (link bundle, LAG, less applicable is ECMP in this case) is
> used.
>  
> In this case though, the GAL under the LSP label currently indicates
> that after the POP that OAM needs to be done (or more accurately that
> a G-Ach of some type is being carried).  If the GAL is put above the
> PW label it is in that same place and there is an ambiguity.  It is an
> ambiguity that for some but not all defined OAM can be resolved by
> looking at information in BFD that makes it unambiguous.  Unless I'm
> mistaken, in CC/CV the label stack above GAL provides the context.
>  
> Another solution would be to put GAL under the PW label.  It would
> probably be best to put GAL under PW but over the fat-pw label.  The
> PW implementation, seeing the PW was not BOS, could look at the next
> label to see if the label is reserved and specifically if it is GAL,
> and if not process as payload (unless CW is also used).  If CW was not
> used the only advantage is 4 bytes less in payload but the same size
> in OAM packets.  This is an advantage though.
>  
> On a related topic, if we must put ELI plus entropy label on the stack
> we have saved nothing relative to fat-pw plus CW.  ELI as a
> termination of hash search may have other uses though (MPLS-TP).
>  
> I would be in favor of a very short draft just relaxing the
> requirement that GAL be at the bottom of stack, independent of the
> reason for doing so, since a number of reasons have emerged.  The
> behavior would be to throw away the rest of the label stack when the
> GAL label is exposed and look at the MPLS payload interpreting it as
> an G-Ach channel (most often, but not exclusively, as OAM).  This
> relaxation of the BOS restriction would be independent of usage.
>  
> Curtis
>  
>  
> > On 22/03/2011 16:22, Robert Rennison wrote:
> > >
> > > Luca, Thomas,
> > >
> > > A couple of clarification questions.
> > >
> > > I'm trying to understand what the combination of the two drafts,
> > > -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts to.
> > >
> > > So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it's
> > > saying use VCCV type 1 where possible and if not then use the new type
> > > 4, whereby  in type 4 the exception mechanism is triggered by the use
> > > of the GAL,  and I appreciated the diagram in section 3 to lock this
> > > is, so far so good.
> > >
> > > Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these two
> > > drafts could work together since this one is trying to lay the "legal
> > > framework" i.e fix up the RFCs which mandated that the GAL could not
> > > be used with the PW.
> > >
> > > Then I get hit with a brick wall in the form of the statements in the
> > > last 2 paras of section 3 of tp-gal-in-pw which state.
> > >
> > > - Section 4.2
> > > <http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#section-=
> 4.2>.
> > > (GAL Applicability and Usage) in [RFC5586
> > > <http://tools.ietf.org/html/rfc5586>], the
> > >
> > >       original text:
> > >
> > >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> > >
> > >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> > >
> > >           MUST NOT be used with PWs. It MUST always be at the bottom of
> > >
> > >           the label stack (i.e., S bit set to 1). However, in other MPL=
> S
> > >
> > >           environments, this document places no restrictions on where
> > >
> > >           the GAL may appear within the label stack or its use with PWs=
> .
> > >
> > >       is replaced by:
> > >
> > >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> > >
> > >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> > >
> > >           MAY be used with PWs. It MUST always be at the bottom of the
> > >
> > >           label stack (i.e., S bit set to 1). However, in other MPLS
> > >
> > >           environments, this document places no restrictions on where
> > >
> > >           the GAL may appear within the label stack.
> > >
> > > It's the bit about the GAL MUST be at the bottom of the label stack,
> > > this is clearly inconsistent with what is proposed in the
> > > draft-nadeau-pwe3 where one can clearly see the GAL above the PW label
> > > and if one has to use  a GAL with a PW this would be the place to put i=
> t,
> > >
> > > Now I can hear you saying "oh but look at the text below this, where
> > > we state .."However, in other MPLS environments , this document places
> > > no restrictions on where the GAL may appear within the label stack.
> > > This is consistent with draft-nadeau "   In which case I'd retort with
> > > ; what are we to do for PWs in   MPLS-TP, since what's in draft-nadeau
> > > would not be allowed ?
> > >
> > > Clarification /explanation appreciated.
> > >
> > > Cheers
> > >
> > > Rob Rennison
> > >
> [snipped ...]

From Alexander.Vainshtein@ecitele.com  Fri Mar 25 23:42:18 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB4F23A68CF; Fri, 25 Mar 2011 23:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level: 
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[AWL=0.023,  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 6LDbXfxLDkSk; Fri, 25 Mar 2011 23:42:17 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id EF1C83A688C; Fri, 25 Mar 2011 23:42:15 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-ca-4d8d8abfde9a
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id DF.24.19639.FBA8D8D4; Sat, 26 Mar 2011 08:42:07 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Sat, 26 Mar 2011 08:43:49 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@occnc.com" <curtis@occnc.com>
Date: Sat, 26 Mar 2011 08:39:33 +0200
Thread-Topic: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt 
Thread-Index: AcvrWff/aNFHUZqgQHWML9VSACl+fQAJpkhh
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D0E79C@ILPTMAIL02.ecitele.com>
References: Your message of "Thu, 24 Mar 2011 07:44:39 +0200." <A3C5DF08D38B6049839A6F553B331C76D6FB8BEACE@ILPTMAIL02.ecitele.com> ,<201103260202.p2Q22vsK065505@harbor.orleans.occnc.com>
In-Reply-To: <201103260202.p2Q22vsK065505@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
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, Robert Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [PWE3] [mpls-tp] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Mar 2011 06:42:18 -0000

Curtis,=20
Please see inline below. I've snipped the text that is not relevant to my c=
omment.

Regards,
     Sasha

________________________________________
From: curtis@occnc.com [curtis@occnc.com]
Sent: Saturday, March 26, 2011 4:02 AM
To: Alexander Vainshtein
Cc: Greg Mirsky; curtis@occnc.com; Robert Rennison; mpls@ietf.org; mpls-tp@=
ietf.org; lihan@chinamobile.com; pwe3; HUANG Feng F
Subject: Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-=
00.txt

In message <A3C5DF08D38B6049839A6F553B331C76D6FB8BEACE@ILPTMAIL02.ecitele.c=
om>
Alexander Vainshtein writes:
>
... snipped ...
>> And, last but not least, if we decide to allow GAL in the middle of the =
label stack=20
>> (overriding RFC 5586 and RFC 5960), we must also define how a pack et wi=
th GAL=20
>> in the middle of the label stack is forwarded when GAL is exposed,=20
>> similar to what has been done in RFC 3032 for RAL.
>>
>> My 2c,
>>      Sasha

> If GAL is encountered, then it is processed just as it would be if TTL
> was set high and GAL was encountered as a result of the final POP in a
> containing LSP exposing only the GAL.  The G-Ach is after the bottom
> of stack, where ever bottom of stack is found.

> Curtis

IMHO this would not work for, say MS-PWs with GAL above the PW label as pro=
posed in draft-nadeu.



> ________________________________
> From: mpls-tp-bounces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of Gr=
eg=3D
>  Mirsky [gregimirsky@gmail.com]
> Sent: Wednesday, March 23, 2011 10:57 PM
> To: curtis@occnc.com
> Cc: Robert Rennison; mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.c=
om=3D
> ; pwe3; HUANG Feng F
> Subject: Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-p=
w-=3D
> 00.txt
>
> Dear Curtis and All,
> I believe that any restriction on placing GAL in a label stack set in Sec=
ti=3D
> on 4.2, RFC 5886 is relevant only for MPLS-TP PSN. For non-TP PSNs there =
ar=3D
> e no restrictions set in RFC 5886 on where in a label stack GAL might app=
ea=3D
> r. Some of use cases mentioned by Curtis are outside of MPLS-TP scope and=
, =3D
> as I understand, use of GAL in these cases is not regulated by the RFC 58=
86=3D
> .
> As to the issue of using GAL in PW there would not be a problem if not fo=
r =3D
> possible conflict with PW VCCV CC Type 1. If GAL presents PW VCCV CC Type=
 4=3D
> , properly updates RFC 5085, and for MPLS-TP PWs complies with the RFC 58=
86=3D
>  - we might be good.
>
> Regards,
> Greg
>
> On Wed, Mar 23, 2011 at 1:25 PM, Curtis Villamizar <curtis@occnc.com<mail=
to=3D
> :curtis@occnc.com>> wrote:
>
> In message <4D88E3A7.4040502@cisco.com<mailto:4D88E3A7.4040502@cisco.com>=
>
> Stewart Bryant writes:
> >
> > If there is IETF consensus to update RFC5586 with this change then the
> > process is relatively simple:
> >
> > The document making the update notes that it does the update, and the A=
D
> > draws attention to
> > this in the IETF LC.
> >
> > Stewart
>
>
> Stewart,
>
> The restriction that GAL be at the bottom of stack was simply a
> mistake IMHO.  I stated that during MPLS WG discussion before it
> became an RFC but it went through as is anyway with that restriction.
> Even then it was said that if there were a strong reason to relax it
> that it could be considered later.  That time may have come.
>
> There are a number of reasons that labels might want to go below GAL,
> including to use OAM to diagnose the connectivity (or lack of) that is
> experienced only for a specific label stack combinations where
> multipath (link bundle, LAG, less applicable is ECMP in this case) is
> used.
>
> In this case though, the GAL under the LSP label currently indicates
> that after the POP that OAM needs to be done (or more accurately that
> a G-Ach of some type is being carried).  If the GAL is put above the
> PW label it is in that same place and there is an ambiguity.  It is an
> ambiguity that for some but not all defined OAM can be resolved by
> looking at information in BFD that makes it unambiguous.  Unless I'm
> mistaken, in CC/CV the label stack above GAL provides the context.
>
> Another solution would be to put GAL under the PW label.  It would
> probably be best to put GAL under PW but over the fat-pw label.  The
> PW implementation, seeing the PW was not BOS, could look at the next
> label to see if the label is reserved and specifically if it is GAL,
> and if not process as payload (unless CW is also used).  If CW was not
> used the only advantage is 4 bytes less in payload but the same size
> in OAM packets.  This is an advantage though.
>
> On a related topic, if we must put ELI plus entropy label on the stack
> we have saved nothing relative to fat-pw plus CW.  ELI as a
> termination of hash search may have other uses though (MPLS-TP).
>
> I would be in favor of a very short draft just relaxing the
> requirement that GAL be at the bottom of stack, independent of the
> reason for doing so, since a number of reasons have emerged.  The
> behavior would be to throw away the rest of the label stack when the
> GAL label is exposed and look at the MPLS payload interpreting it as
> an G-Ach channel (most often, but not exclusively, as OAM).  This
> relaxation of the BOS restriction would be independent of usage.
>
> Curtis
>
>
> > On 22/03/2011 16:22, Robert Rennison wrote:
> > >
> > > Luca, Thomas,
> > >
> > > A couple of clarification questions.
> > >
> > > I'm trying to understand what the combination of the two drafts,
> > > -lm-pwe3-mpls-tp-gal-in-pw, and draft-nadeau-pwe3-vccv-2amounts to.
> > >
> > > So, I think I understood the draft-nadeau-pwe3-vccv-2 in that it's
> > > saying use VCCV type 1 where possible and if not then use the new typ=
e
> > > 4, whereby  in type 4 the exception mechanism is triggered by the use
> > > of the GAL,  and I appreciated the diagram in section 3 to lock this
> > > is, so far so good.
> > >
> > > Now I read -pwe3-mpls-tp-gal-in-pw and I'm thinking , Ok these two
> > > drafts could work together since this one is trying to lay the "legal
> > > framework" i.e fix up the RFCs which mandated that the GAL could not
> > > be used with the PW.
> > >
> > > Then I get hit with a brick wall in the form of the statements in the
> > > last 2 paras of section 3 of tp-gal-in-pw which state.
> > >
> > > - Section 4.2
> > > <http://tools.ietf.org/html/draft-lm-pwe3-mpls-tp-gal-in-pw-00#sectio=
n-=3D
> 4.2>.
> > > (GAL Applicability and Usage) in [RFC5586
> > > <http://tools.ietf.org/html/rfc5586>], the
> > >
> > >       original text:
> > >
> > >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> > >
> > >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> > >
> > >           MUST NOT be used with PWs. It MUST always be at the bottom =
of
> > >
> > >           the label stack (i.e., S bit set to 1). However, in other M=
PL=3D
> S
> > >
> > >           environments, this document places no restrictions on where
> > >
> > >           the GAL may appear within the label stack or its use with P=
Ws=3D
> .
> > >
> > >       is replaced by:
> > >
> > >           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> > >
> > >           LSPs, Concatenated Segments of LSPs, and with Sections, and
> > >
> > >           MAY be used with PWs. It MUST always be at the bottom of th=
e
> > >
> > >           label stack (i.e., S bit set to 1). However, in other MPLS
> > >
> > >           environments, this document places no restrictions on where
> > >
> > >           the GAL may appear within the label stack.
> > >
> > > It's the bit about the GAL MUST be at the bottom of the label stack,
> > > this is clearly inconsistent with what is proposed in the
> > > draft-nadeau-pwe3 where one can clearly see the GAL above the PW labe=
l
> > > and if one has to use  a GAL with a PW this would be the place to put=
 i=3D
> t,
> > >
> > > Now I can hear you saying "oh but look at the text below this, where
> > > we state .."However, in other MPLS environments , this document place=
s
> > > no restrictions on where the GAL may appear within the label stack.
> > > This is consistent with draft-nadeau "   In which case I'd retort wit=
h
> > > ; what are we to do for PWs in   MPLS-TP, since what's in draft-nadea=
u
> > > would not be allowed ?
> > >
> > > Clarification /explanation appreciated.
> > >
> > > Cheers
> > >
> > > Rob Rennison
> > >
> [snipped ...]=

From curtis@occnc.com  Sun Mar 27 12:00:29 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5B3F3A6950; Sun, 27 Mar 2011 12:00:28 -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 M+IFinKuQuqi; Sun, 27 Mar 2011 12:00:26 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 3C7B13A68F8; Sun, 27 Mar 2011 12:00:25 -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 p2RJ1j3k011592; Sun, 27 Mar 2011 15:01:45 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103271901.p2RJ1j3k011592@harbor.orleans.occnc.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Sat, 26 Mar 2011 08:39:33 +0200." <A3C5DF08D38B6049839A6F553B331C76D722D0E79C@ILPTMAIL02.ecitele.com> 
Date: Sun, 27 Mar 2011 15:01:45 -0400
Sender: curtis@occnc.com
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, pwe3 <pwe3@ietf.org>, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, Robert Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Mar 2011 19:00:30 -0000

Sasha,

Thanks for trimming.  I further trimmed and also dropped mpls-tp.

This email has suggested change to the internet-draft below.

It is important that any proposal to use GAL with PW not break
traceroute on the containing LSP.  Since a goal is to also suport
MS-PW (as you point out below) and LSP hierarchy, an LSR needs to be
able to forward payload containing GAL.  See inline to keep the
context.

Btw - the new name of the document is:
draft-ietf-pwe3-mpls-tp-gal-in-pw-00.txt

Another suggestion is why not drop the -TP from the title.  GAL
applies to all MPLS, not just -TP.

Curtis


In message <A3C5DF08D38B6049839A6F553B331C76D722D0E79C@ILPTMAIL02.ecitele.com>
Alexander Vainshtein writes:
>  
> Curtis, 
> Please see inline below. I've snipped the text that is not relevant
> to my comment.
>  
> Regards,
>      Sasha
>  
> ________________________________________
> From: curtis@occnc.com [curtis@occnc.com]
> Sent: Saturday, March 26, 2011 4:02 AM
> To: Alexander Vainshtein
> Cc: Greg Mirsky; curtis@occnc.com; Robert Rennison; mpls@ietf.org; mpls-tp@ietf.org; lihan@chinamobile.com; pwe3; HUANG Feng F
> Subject: Re: [mpls-tp] [PWE3] [mpls] WG LC draft-lm-pwe3-mpls-tp-gal-in-pw-00.txt
>  
> In message <A3C5DF08D38B6049839A6F553B331C76D6FB8BEACE@ILPTMAIL02.ecitele.com>
> Alexander Vainshtein writes:
> >
> ... snipped ...
> >> And, last but not least, if we decide to allow GAL in the middle
> >> of the label stack  
> >> (overriding RFC 5586 and RFC 5960), we must also define how a
> >> pack et with GAL  
> >> in the middle of the label stack is forwarded when GAL is exposed, 
> >> similar to what has been done in RFC 3032 for RAL.
> >>
> >> My 2c,
> >>      Sasha
>  
> > If GAL is encountered, then it is processed just as it would be if TTL
> > was set high and GAL was encountered as a result of the final POP in a
> > containing LSP exposing only the GAL.  The G-Ach is after the bottom
> > of stack, where ever bottom of stack is found.
>  
> > Curtis
>  
> IMHO this would not work for, say MS-PWs with GAL above the PW label
> as proposed in draft-nadeu. 


A few simple rules would work for LSP ping (not using TTL), LSP
traceroute (using TTL), PW ping (including MS-PW, not using TTL), and
MS-PW traceroute (using TTL to identify the set of S-PE).

  original (rfc5586.txt):

   In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
   Concatenated Segments of LSPs, and with Sections, and MUST NOT be
   used with PWs.  It MUST always be at the bottom of the label stack
   (i.e., S bit set to 1).  However, in other MPLS environments, this
   document places no restrictions on where the GAL may appear within
   the label stack or its use with PWs.  Where the GAL is at the bottom
   of the label stack (i.e., S bit set to 1), then it MUST always be
   followed by an ACH.

   The GAL MUST NOT appear in the label stack when transporting normal
   user-plane packets.  Furthermore, when present, the GAL MUST NOT
   appear more than once in the label stack.

  replacement:

   In MPLS and MPLS-TP, the GAL MUST be used with packets on a G-ACh
   on LSPs, Concatenated Segments of LSPs, and with Sections.  GAL MAY
   be used with PWs.  It MUST always be at the bottom of the label
   stack (i.e., S bit set to 1).  GAL must appear immediately below
   the label for which a G-Ach is associated.  The ingress SHOULD
   determine whether labels below GAL are supported by intermediate
   and egress LSR, otherwise GAL must also be at the bottom of the
   stack.  

   The GAL MUST NOT be added to normal user-plane packets.  User-plane
   packets which already contain GAL may be transported.  When
   present, the GAL MUST NOT appear more than once in the label stack.

At some later point in the document (could be section 3 and 4) add:

  Backwards compatibility:

   In order to insure that LSR which strictly conform to [RFC5586] and
   require that GAL be on the bottom of the stack, an ingress SHOULD
   determine whether all intermediate LSR and the egress LSR support
   labels after the GAL label.

   <<< add mechanism to advertise capability here or disclaimer that
       it is elsewere in some ISIS or OSPF extensions >>>

  Rules for handling GAL and TTL expired with GAL:

   GAL MUST be place directly beneath label for the LSP or PW for
   which the channel is relevant.  Additional labels MAY be placed
   below GAL to affect packet entropy based decisions at multipoint
   links such as link bundles and Ethernet LAG.  See [Backwards
   compatibility] for limitations on labels below GAL.

   LSR using label stack based packet entropy based decisions at
   multipoint links SHOULD ignore a GAL label for the purpose of
   entropy harvesting and continue entropy harvesting as though GAL
   were not present.

   When processing TTL Expiration on a packet, if the label
   immediately following is GAL, then a ACH MUST be immediately below
   the bottom of the MSPL stack and the ACH must be processed.

   When a LSP POP or PW POP occurs, if the next label is GAL, then a
   ACH MUST be immediately below the bottom of the MSPL stack and the
   ACH must be processed.

Note that for PW, GAL is after the PW label and before the fat-pw
label (if present).

We also need to change the security section a bit.

   Refer to [RFC5586] for general MPLS security considerations.

   GAL in user payload must be forwarded to support GAL at a client
   layer.  If an LSR interprets GAL at the bottom of stack to be
   relevant to a G-Ach for the label for which a TTL has expired, then
   a client layer G-Ach payload may be applied to a server layer.
   Use of the uniform model, or a pipe model TTL set too low with an
   attack which increases hop count (physical attack), plus an LSR
   that erroneously interprets GAL anywhere in the stack or at bottom
   of stack to be a G-Ach at the layer for which TTL has expired,
   provides a low probability attack vector.

   This attack vector would only exist if intermediate LSR on the path
   interpretted TTL anywhere in the stack or at bottom of stack as
   their own G-Ach.  This document requires that the GAL only be
   considered if it is immediately following a TTL expire or POP.
   [RFC5586] is silent on forwarding (or not forwarding packets
   contraining GAL at the ingress to a hierarchical LSP, and is
   unclear as to whether TTL expired can be applied to GAL at the
   bottom of stack well below the label for which TTL expired.

   The vulnerability is associated with the behaviour defined in
   [RFC5586] and would be fixed if all LSR conformed to the updates to
   [RFC5586] in this document.

   The potential for this attack vector to become exploitable as a
   result of an older LSR which adheres only to [RFC5586] can be
   eliminated by offering an option to block forwarding of traffic
   containing GAL if the backward compatibility check defined in
   [Backwards compatibility] reveals intermediate or egres LSR not
   advertising the capability defined in this document.  LSR SHOULD
   provide such an option.


From david.i.allan@ericsson.com  Mon Mar 28 02:07:03 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD1F13A696F for <pwe3@core3.amsl.com>; Mon, 28 Mar 2011 02:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.492
X-Spam-Level: 
X-Spam-Status: No, score=-4.492 tagged_above=-999 required=5 tests=[AWL=2.106,  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 R-HJz3P57jKv for <pwe3@core3.amsl.com>; Mon, 28 Mar 2011 02:07:00 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id B716E3A696E for <pwe3@ietf.org>; Mon, 28 Mar 2011 02:07:00 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2S98aKt018559 for <pwe3@ietf.org>; Mon, 28 Mar 2011 04:08:38 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.203]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Mon, 28 Mar 2011 05:08:37 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Date: Mon, 28 Mar 2011 05:08:36 -0400
Thread-Topic: Re: negotiation of CC encapsulation
Thread-Index: AcvtJ7hz5rP3OquvSkWUAD9ataaoQQ==
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51D529A572@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_60C093A41B5E45409A19D42CF7786DFD51D529A572EUSAACMS0703e_"
MIME-Version: 1.0
Subject: Re: [PWE3] negotiation of CC encapsulation
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 09:07:03 -0000

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

HI:

Yakov raised some interesting points during PWE today.

My concern is receiving something unexpected could be an indication of more=
 than simply poor configuration. So it would be useful for an implementatio=
n to go further than simple silent discard. It MAY examine the unexpected f=
rame to see if it is coming from an unexpected source. Sufficient informati=
on exists in some cases to do so (e.g. NOT RFC 5885 encap)...

My 2 cents
D




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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial, sans-serif" size=3D"2">
<div>HI:</div>
<div>&nbsp;</div>
<div>Yakov raised some interesting points during PWE today.</div>
<div>&nbsp;</div>
<div>My concern is receiving something unexpected could be an indication of=
 more than simply poor configuration. So it would be useful for an implemen=
tation to go further than simple silent discard. It MAY examine the unexpec=
ted frame to see if it is coming
from an unexpected source. Sufficient information exists in some cases to d=
o so (e.g. NOT RFC 5885 encap)&#8230;</div>
<div>&nbsp;</div>
<div>My 2 cents</div>
<div>D</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_60C093A41B5E45409A19D42CF7786DFD51D529A572EUSAACMS0703e_--

From Alexander.Vainshtein@ecitele.com  Mon Mar 28 02:32:34 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FC273A681B; Mon, 28 Mar 2011 02:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level: 
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[AWL=0.022,  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 08MrnwAi2oYX; Mon, 28 Mar 2011 02:32:31 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id DD53F3A6965; Mon, 28 Mar 2011 02:32:30 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-16-4d9055a8eb0b
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id 1B.90.19639.8A5509D4; Mon, 28 Mar 2011 11:32:24 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Mon, 28 Mar 2011 11:33:51 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Yaakov Stein <yaakov_s@rad.com>
Date: Mon, 28 Mar 2011 11:33:46 +0200
Thread-Topic: PW status TLV vs BFD diagnostic codes
Thread-Index: AcvtKzzBfTFGRp2nRfKcXlXec7dbvg==
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D06BCA@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_A3C5DF08D38B6049839A6F553B331C76D722D06BCAILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, pwe3 <pwe3@ietf.org>, Robert Rennison <Robert.Rennison@ecitele.com>
Subject: [PWE3] PW status TLV vs BFD diagnostic codes
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 09:32:35 -0000

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

Yaakov and all,
I'd like to reiterate the point Rob and I have made in the PWE3 meeting tod=
ay:

The status mechanisms based on BFD diagnostic codes does not support (and, =
AFAIK, cannot support) the PW redundancy mechanism.

Regards,
     Sasha


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 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;}
.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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Yaakov and all,<=
o:p></o:p></p><p class=3DMsoNormal>I&#8217;d like to reiterate the point Ro=
b and I have made in the PWE3 meeting today:<o:p></o:p></p><p class=3DMsoNo=
rmal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The status mechanisms based =
on BFD diagnostic codes does not support (and, AFAIK, cannot support) the P=
W redundancy mechanism.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></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_A3C5DF08D38B6049839A6F553B331C76D722D06BCAILPTMAIL02eci_--

From curtis@occnc.com  Mon Mar 28 02:34:27 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8141A3A68F9 for <pwe3@core3.amsl.com>; Mon, 28 Mar 2011 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 ddCnNE-yymdr for <pwe3@core3.amsl.com>; Mon, 28 Mar 2011 02:34:26 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id B88EB3A68B0 for <pwe3@ietf.org>; Mon, 28 Mar 2011 02:34:25 -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 p2S9ZxbT040737; Mon, 28 Mar 2011 05:35:59 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103280935.p2S9ZxbT040737@harbor.orleans.occnc.com>
To: David Allan I <david.i.allan@ericsson.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Mon, 28 Mar 2011 05:08:36 EDT." <60C093A41B5E45409A19D42CF7786DFD51D529A572@EUSAACMS0703.eamcs.ericsson.se>
Date: Mon, 28 Mar 2011 05:35:59 -0400
Sender: curtis@occnc.com
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] negotiation of CC encapsulation
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 09:34:27 -0000

In message <60C093A41B5E45409A19D42CF7786DFD51D529A572@EUSAACMS0703.eamcs.ericsson.se>
David Allan I writes:
>  
> Hi:
>  
> Yakov raised some interesting points during PWE today.
>  
> My concern is receiving something unexpected could be an indication of more=
>  than simply poor configuration. So it would be useful for an implementatio=
> n to go further than simple silent discard. It MAY examine the unexpected f=
> rame to see if it is coming from an unexpected source. Sufficient informati=
> on exists in some cases to do so (e.g. NOT RFC 5885 encap)...
>  
> My 2 cents
> D


MS-PW may force the use of both CW or GAL and TTL, with TTL used to
traceroute a MS-PW and CW or GAL used when addressing the end node.

Unless I'm mistaken, preferring CW or GAL but accepting CW or GAL (or
both) and also accepting TTL would not be a problem.  Sending TTL in
that case for traceroute only might yield a dead spot just like
hitting an IP router with ICMP on TTL disabled does today.

Curtis
 

From prvs=1068dc6f10=edwin.mallette@bhnis.com  Mon Mar 28 03:23:17 2011
Return-Path: <prvs=1068dc6f10=edwin.mallette@bhnis.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6ACBD3A68C0; Mon, 28 Mar 2011 03:23:17 -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 UA6tpMh1XoaB; Mon, 28 Mar 2011 03:23:16 -0700 (PDT)
Received: from mx2.mybrighthouse.com (MX3.mybrighthouse.com [209.16.122.105]) by core3.amsl.com (Postfix) with ESMTP id 1B0A23A6838; Mon, 28 Mar 2011 03:23:15 -0700 (PDT)
Received: from pps.filterd (mx3 [127.0.0.1]) by mx3.mybrighthouse.com (8.14.3/8.14.3) with SMTP id p2SAKB41008188; Mon, 28 Mar 2011 06:24:49 -0400
Received: from tbstpcas02.corp.local ([10.226.201.192]) by mx3.mybrighthouse.com with ESMTP id vamu70jmr-1 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 28 Mar 2011 06:24:49 -0400
Received: from CNEMAIL.corp.local ([10.225.1.130]) by tbstpcas02.corp.local ([10.226.201.192]) with mapi; Mon, 28 Mar 2011 06:24:48 -0400
From: "Mallette, Edwin" <Edwin.Mallette@bhnis.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, Yaakov Stein <yaakov_s@rad.com>
Date: Mon, 28 Mar 2011 06:24:45 -0400
Thread-Topic: [PWE3] PW status TLV vs BFD diagnostic codes
Thread-Index: AcvtMlz50jSGmY11RkaLjNsiZKZ5hA==
Message-ID: <C9B6299F.9BFF%edwin.mallette@bhnis.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D722D06BCA@ILPTMAIL02.ecitele.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C9B6299F9BFFedwinmallettebhniscom_"
MIME-Version: 1.0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1012030000 definitions=main-1103280029
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, pwe3 <pwe3@ietf.org>, Robert, Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [PWE3] PW status TLV vs BFD diagnostic codes
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 10:23:17 -0000

--_000_C9B6299F9BFFedwinmallettebhniscom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Yaakov,

It also strikes me that this is an attempt at solving a narrow corner case =
with additional specification language.  Protocol inter-dependence is commo=
n, so I'm not sure why the need to split this particular hair.  IMO the mec=
hanism BFD -> PW status TLV works fine.   I suppose your point is that if y=
ou don't support PW status TLV that then you have to use label withdrawals,=
 not ideal perhaps, but is this really a problem in existing deployments ? =
  Is there a broad deployment of PWs out there that don't support PW Status=
 TLV ?  I don't think so.

And to Sasha's point, a large reason I would use BFD would be for PW Redund=
ancy fault detection and I wouldn't want to be muddying those waters overmu=
ch.

Cheers!
Ed

From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexand=
er.Vainshtein@ecitele.com>>
Date: Mon, 28 Mar 2011 05:33:46 -0400
To: Yaakov Stein <yaakov_s@rad.com<mailto:yaakov_s@rad.com>>
Cc: "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rt=
g-bfd@ietf.org>>, pwe3 <pwe3@ietf.org<mailto:pwe3@ietf.org>>, Robert Rennis=
on <robert.rennison@ecitele.com<mailto:robert.rennison@ecitele.com>>
Subject: [PWE3] PW status TLV vs BFD diagnostic codes

Yaakov and all,
I=92d like to reiterate the point Rob and I have made in the PWE3 meeting t=
oday:

The status mechanisms based on BFD diagnostic codes does not support (and, =
AFAIK, cannot support) the PW redundancy mechanism.

Regards,
     Sasha


________________________________
CONFIDENTIALITY NOTICE: This e-mail may contain information that is privile=
ged, confidential or otherwise protected from disclosure. If you are not th=
e intended recipient of this e-mail, please notify the sender immediately b=
y return e-mail, purge it and do not disseminate or copy it.

--_000_C9B6299F9BFFedwinmallettebhniscom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Yaakov,</div>
<div><br>
</div>
<div>It also strikes me that this is an attempt at solving a narrow corner =
case with additional specification language. &nbsp;Protocol inter-dependenc=
e is common, so I'm not sure why the need to split this particular hair. &n=
bsp;IMO the mechanism BFD -&gt; PW status TLV
 works fine. &nbsp; I suppose your point is that if you don't support PW st=
atus TLV that then you have to use label withdrawals, not ideal perhaps, bu=
t is this really a problem in existing deployments ? &nbsp; Is there a broa=
d deployment of PWs out there that don't support
 PW Status TLV ? &nbsp;I don't think so.</div>
<div><br>
</div>
<div>And to Sasha's point, a large reason I would use BFD would be for PW R=
edundancy fault detection and I wouldn't want to be muddying those waters o=
vermuch.</div>
<div><br>
</div>
<div>Cheers!</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Ed</di=
v>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Alexander Vainshtein &lt;<a h=
ref=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshtein@ecitel=
e.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Mon, 28 Mar 2011 05:33:46 -04=
00<br>
<span style=3D"font-weight:bold">To: </span>Yaakov Stein &lt;<a href=3D"mai=
lto:yaakov_s@rad.com">yaakov_s@rad.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:rtg-bfd=
@ietf.org">rtg-bfd@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtg-bfd@ietf.or=
g">rtg-bfd@ietf.org</a>&gt;, pwe3 &lt;<a href=3D"mailto:pwe3@ietf.org">pwe3=
@ietf.org</a>&gt;, Robert Rennison &lt;<a href=3D"mailto:robert.rennison@ec=
itele.com">robert.rennison@ecitele.com</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[PWE3] PW status TLV vs BF=
D diagnostic codes<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<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;}
.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]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Yaakov and all,<o:p></o:p></p>
<p class=3D"MsoNormal">I=92d like to reiterate the point Rob and I have mad=
e in the PWE3 meeting today:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The status mechanisms based on BFD diagnostic codes =
does not support (and, AFAIK, cannot support) the PW redundancy mechanism.<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">CONFIDENTIALITY NOTICE: This=
 e-mail may contain information that is privileged, confidential or otherwi=
se protected from disclosure. If you are not the intended recipient of this=
 e-mail, please notify the sender immediately
 by return e-mail, purge it and do not disseminate or copy it.<br>
</font>
</body>
</html>

--_000_C9B6299F9BFFedwinmallettebhniscom_--

From Alexander.Vainshtein@ecitele.com  Mon Mar 28 11:34:07 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BAD663A68E7 for <pwe3@core3.amsl.com>; Mon, 28 Mar 2011 11:34:07 -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 A2eu3j-8hoad for <pwe3@core3.amsl.com>; Mon, 28 Mar 2011 11:34:05 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id 311433A6825 for <pwe3@ietf.org>; Mon, 28 Mar 2011 11:34:03 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-00-4d90d49670d6
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id 7C.9E.19639.694D09D4; Mon, 28 Mar 2011 20:33:58 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Mon, 28 Mar 2011 20:34:16 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Andrew G. Malis" <amalis@gmail.com>, Thomas Nadeau <tnadeau@lucidvision.com>, "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
Date: Mon, 28 Mar 2011 20:34:11 +0200
Thread-Topic: [PWE3] FW: New Version Notification for draft-delregno-pw-vccv-impl-survey-results-00
Thread-Index: AcvljY66xv/4wWnsSSKppyCoJJhupQH6AZuA
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D06E0A@ILPTMAIL02.ecitele.com>
References: <14584D6EE26B314187A4F68BA206060006CCDB13@ASHEVS008.mcilink.com> <07F7D7DED63154409F13298786A2ADC903D16E0F@EXRAD5.ad.rad.co.il> <4D7F944E.2040903@cisco.com> <538B1799-C583-4192-B170-170F00FEDA7D@lucidvision.com> <14584D6EE26B314187A4F68BA206060006E297A0@ASHEVS008.mcilink.com> <4CC0A1A4-E6C1-40D6-B05E-508D26C1C0BD@lucidvision.com> <AANLkTinCpnvfszZ0VfFDt7EUh_ezZ0+A-zKhyPZZjXe_@mail.gmail.com>
In-Reply-To: <AANLkTinCpnvfszZ0VfFDt7EUh_ezZ0+A-zKhyPZZjXe_@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="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: pwe3 <pwe3@ietf.org>, Yaakov Stein <yaakov_s@rad.com>, Luca Martini <lmartini@cisco.com>
Subject: Re: [PWE3] FW: New Version Notification for	draft-delregno-pw-vccv-impl-survey-results-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 18:34:07 -0000

Andy, Tom, Nick and all,
I support Tom's suggestion.=20

I would also like to suggest one more extension to the survey.

In its present form, it says how many *operators* can use CW in this or tha=
t PW type where it is optional, and how many *operators* actually use it - =
again, per PW type. It also says how many PWs of this or that type have bee=
n actually deployed.

IMHO and FWIW, it would be most helpful if we could have the information ab=
out the number of *PW instances* that use (or do not use) an optional  CW -=
 again, per PW type.


Regards,
     Sasha

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> Andrew G. Malis
> Sent: Friday, March 18, 2011 6:57 PM
> To: Thomas Nadeau
> Cc: Luca Martini; Yaakov Stein; pwe3
> Subject: Re: [PWE3] FW: New Version Notification for draft-delregno-pw-
> vccv-impl-survey-results-00
>=20
> Are there any objections in the WG to Tom's suggestion?
>=20
> Thanks,
> Andy
>=20
> On Thu, Mar 17, 2011 at 1:03 PM, Thomas Nadeau
> <tnadeau@lucidvision.com> wrote:
> > That's precisely what I'm asking for: for the wg to agree to augment
> the existing survey with a short additional one that focuses in the
> missing bfd mode only.
> >
> > Tom
> >
> > On Mar 17, 2011, at 12:03 PM, "Delregno, Christopher N (Nick
> DelRegno)" <nick.delregno@verizon.com> wrote:
> >
> >> Tom:
> >>
> >> Please pose that question to the WG (maybe that's what you were
> doing).
> >> When we crafted the survey, omitting BFD was an oversight. =A0However,
> the
> >> list of questions was sent to the WG for comment before the survey
> was
> >> conducted. =A0If the WG would like, I can contact the respondents
> directly
> >> to inquire of their BFD usage as well. =A0However, I don't think the
> >> survey should be reopened.
> >>
> >> Thanks,
> >> Nick
> >>
> >> -----Original Message-----
> >> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
> >> Sent: Tuesday, March 15, 2011 2:18 PM
> >> To: Luca Martini
> >> Cc: Delregno, Christopher N (Nick DelRegno); Yaakov Stein; pwe3
> >> Subject: Re: [PWE3] FW: New Version Notification for
> >> draft-delregno-pw-vccv-impl-survey-results-00
> >>
> >>
> >> =A0 =A0One thing I'd ask is that we augment the survey to ask about th=
e
> >> BFD mode for
> >> VCCV. It seems to have been left out of the survey, potentially
> skewing
> >> the results.
> >> As I understand it, this is the most popular mode.
> >>
> >> =A0 =A0--Tom
> >>
> >>
> >>
> >>
> >> On Mar 15, 2011, at 12:31 PM, Luca Martini wrote:
> >>
> >>> Nick,
> >>> Good survey, thanks for the work.
> >>>
> >>> Are we going to publish this as informational ?
> >>> I think we should .
> >>> Also there is a mention of AToM in section 2.7 item 5 . It should
> be
> >>> changed to PWE ( AToM is a cisco marketing term , so we want o keep
> >> this
> >>> anonymous )
> >>> Thanks.
> >>> Luca
> >>>
> >>>
> >>>
> >>> On 03/15/2011 09:41 AM, Yaakov Stein wrote:
> >>>> Nick,
> >>>>
> >>>> In section 2.2 the percentages make sense under the assumption of
> 18
> >> respondents :
> >>>> 5.6% =A0 =3D =A01 / 18
> >>>> 11.1% =A0=3D =A02 / 18
> >>>> 16.7% =A0=3D =A03 / 18
> >>>> 22.2% =A0=3D =A04 / 18
> >>>> 44.4% =A0=3D =A08 / 18
> >>>> 77.8% =A0=3D 14 / 18
> >>>>
> >>>> but section 2.1 only lists 17 :
> >>>> 1. =A0 =A0Time Warner Cable
> >>>> 2. =A0 =A0Bright House Networks
> >>>> 3. =A0 =A0Tinet
> >>>> 4. =A0 =A0AboveNet
> >>>> 5. =A0 =A0Telecom New Zealand
> >>>> 6. =A0 =A0Cox Communications
> >>>> 7. =A0 =A0MTN South Africa
> >>>> 8. =A0 =A0Wipro Technologies
> >>>> 9. =A0 =A0Verizon
> >>>> 10. =A0 =A0AMS-IX
> >>>> 11. =A0 =A0Superonline
> >>>> 12. =A0 =A0Deutsche Telekom AG
> >>>> 13. =A0 =A0Internet Solution
> >>>> 14. =A0 =A0Easynet Global Services
> >>>> 15. =A0 =A0Telstra Corporation
> >>>> 16. =A0 =A0OJSC MegaFon
> >>>> 17. =A0 =A0France Telecom Orange
> >>>>
> >>>> Did you leave someone off, or did someone answer twice ?
> >>>>
> >>>> Y(J)S
> >>>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> Behalf
> >> Of Delregno, Christopher N (Nick DelRegno)
> >>>> Sent: Tuesday, March 08, 2011 16:27
> >>>> To: pwe3
> >>>> Subject: [PWE3] FW: New Version Notification for
> >> draft-delregno-pw-vccv-impl-survey-results-00
> >>>>
> >>>> Folks:
> >>>>
> >>>> The 00 draft of the PW/VCCV Implementation Survey Results have
> been
> >> uploaded. =A0I will be presenting the results at IETF80.
> >>>>
> >>>>
> >> https://datatracker.ietf.org/doc/draft-delregno-pw-vccv-impl-survey-
> resu
> >> lts/
> >>>>
> >>>> Thanks,
> >>>> Nick
> >>>>
> >>>> Christopher N. Del Regno, PMTS
> >>>> C&T, Ethernet Network Architecture & Design
> >>>> 400 International Pkwy
> >>>> Richardson, TX =A075081
> >>>> 972-729-3411
> >>>> nick.delregno@verizon.com
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> >>>> Sent: Tuesday, March 08, 2011 8:16 AM
> >>>> To: Delregno, Christopher N (Nick DelRegno)
> >>>> Subject: New Version Notification for
> >> draft-delregno-pw-vccv-impl-survey-results-00
> >>>>
> >>>>
> >>>> A new version of I-D,
> >> draft-delregno-pw-vccv-impl-survey-results-00.txt has been
> successfully
> >> submitted by Nick Del Regno and posted to the IETF repository.
> >>>>
> >>>> Filename: =A0 =A0 draft-delregno-pw-vccv-impl-survey-results
> >>>> Revision: =A0 =A0 00
> >>>> Title: =A0 =A0 =A0 =A0 The Pseudowire (PW) & Virtual Circuit
> >> Connectivity Verification (VCCV) Implementation Survey Results
> >>>> Creation_date: =A0 =A0 2011-03-07
> >>>> WG ID: =A0 =A0 =A0 =A0 Independent Submission
> >>>> Number_of_pages: 16
> >>>>
> >>>> Abstract:
> >>>> Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations
> mandate
> >>>> the use of the Control Word (CW) in order to better emulate the
> >>>> services for which the encapsulations have been defined. =A0However,
> >>>> some encapulations treat the Control Word as optional. =A0As a
> result,
> >>>> implementations of the CW, for encapsulations for which it is
> >>>> optional, vary by equipment manufacturer, equipment model and
> service
> >>>> provider network. =A0Similarly, Virtual Circuit Connectivity
> >>>> Verification (VCCV) supports three Control Channel (CC) types and
> >>>> multiple Connectivity Verification (CV) Types. =A0This flexibility
> has
> >>>> led to reports of interoperability issues within deployed networks
> >>>> and associated drafts to attempt to remedy the situation. =A0This
> >>>> survey of the PW/VCCV user community was conducted to determine
> >>>> implementation trends. =A0The survey and results is presented
> herein.
> >>>>
> >>>>
> >>>>
> >>>> The IETF Secretariat.
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> pwe3 mailing list
> >>>> pwe3@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/pwe3
> >>>> _______________________________________________
> >>>> pwe3 mailing list
> >>>> pwe3@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/pwe3
> >>>
> >>> _______________________________________________
> >>> pwe3 mailing list
> >>> pwe3@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/pwe3
> >>>
> >>
> >>
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> >
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

From tochio@jp.fujitsu.com  Mon Mar 28 23:38:55 2011
Return-Path: <tochio@jp.fujitsu.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4AC03A67D0 for <pwe3@core3.amsl.com>; Mon, 28 Mar 2011 23:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.09
X-Spam-Level: 
X-Spam-Status: No, score=-102.09 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  HTML_MESSAGE=0.001, 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 ZItgS7-EfGp0 for <pwe3@core3.amsl.com>; Mon, 28 Mar 2011 23:38:54 -0700 (PDT)
Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by core3.amsl.com (Postfix) with ESMTP id 6A9EB3A683B for <pwe3@ietf.org>; Mon, 28 Mar 2011 23:38:54 -0700 (PDT)
Received: from m4.gw.fujitsu.co.jp (unknown [10.0.50.74]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id B54173EE0B6 for <pwe3@ietf.org>; Tue, 29 Mar 2011 15:40:28 +0900 (JST)
Received: from smail (m4 [127.0.0.1]) by outgoing.m4.gw.fujitsu.co.jp (Postfix) with ESMTP id 9AF3545DE51 for <pwe3@ietf.org>; Tue, 29 Mar 2011 15:40:28 +0900 (JST)
Received: from s4.gw.fujitsu.co.jp (s4.gw.fujitsu.co.jp [10.0.50.94]) by m4.gw.fujitsu.co.jp (Postfix) with ESMTP id 7937345DE4F for <pwe3@ietf.org>; Tue, 29 Mar 2011 15:40:28 +0900 (JST)
Received: from s4.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 6C11B1DB8042 for <pwe3@ietf.org>; Tue, 29 Mar 2011 15:40:28 +0900 (JST)
Received: from sw11.gw.fujitsu.co.jp (sw11.gw.fujitsu.co.jp [10.0.76.51]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 3C8131DB803E for <pwe3@ietf.org>; Tue, 29 Mar 2011 15:40:28 +0900 (JST)
Received: from [127.0.0.1] ([172.31.166.153]) by sw11.gw.fujitsu.co.jp with ESMTP id p2T6eOgI039376 for <pwe3@ietf.org>; Tue, 29 Mar 2011 15:40:27 +0900 (JST)
X-SecurityPolicyCheck: OK by SHieldMailChecker v1.5.1
Message-ID: <4D917ED2.1090008@jp.fujitsu.com>
Date: Tue, 29 Mar 2011 08:40:18 +0200
From: Yuji Tochio <tochio@jp.fujitsu.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: pwe3@ietf.org
References: <C99576C3.A8DA%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <C99576C3.A8DA%matthew.bocci@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------000507010001030300080002"
Subject: Re: [PWE3] WG Last Call for draft-ietf-pwe3-mpls-eth-oam-iwk-04.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 06:38:55 -0000

This is a multi-part message in MIME format.
--------------000507010001030300080002
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

WG chairs,

Sorry for late reply on this:

My comments given in August 2010 is at:
http://www.ietf.org/mail-archive/web/pwe3/current/msg11545.html
Similar comment can be found in:
http://tools.ietf.org/wg/pwe3/minutes?item=minutes78.html

And I found another comment/questions (not mime) in archive as
http://www.ietf.org/mail-archive/web/pwe3/current/msg11624.html

Regards,
Yuji

(2011/03/03 17:48), Bocci, Matthew (Matthew) wrote:
> This email begins a working group last call for draft-ietf-pwe3-mpls-eth-oam-iwk-04.txt <http://tools.ietf.org/html/draft-ietf-pwe3-mpls-eth-oam-iwk-04.txt>.
>
> We are running this LC for three weeks due to its proximity to the Prague IETF. 
> This WG LC will end on 25th March 2011.
>
> Please respond with any comments to the PWE3 mailing list.
>
> Regards,
>
> Matthew and Andy
>  
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3


--------------000507010001030300080002
Content-Type: text/html; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-2022-JP"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    WG chairs,<br>
    <br>
    Sorry for late reply on this:<br>
    <br>
    My comments given in August 2010 is at:<br>
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/mail-archive/web/pwe3/current/msg11545.html">http://www.ietf.org/mail-archive/web/pwe3/current/msg11545.html</a><br>
    Similar comment can be found in:<br>
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/wg/pwe3/minutes?item=minutes78.html">http://tools.ietf.org/wg/pwe3/minutes?item=minutes78.html</a><br>
    <br>
    And I found another comment/questions (not mime) in archive as<br>
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/mail-archive/web/pwe3/current/msg11624.html">http://www.ietf.org/mail-archive/web/pwe3/current/msg11624.html</a><br>
    <br>
    Regards,<br>
    Yuji<br>
    <br>
    (2011/03/03 17:48), Bocci, Matthew (Matthew) wrote:
    <blockquote
      cite="mid:C99576C3.A8DA%25matthew.bocci@alcatel-lucent.com"
      type="cite">
      <div><span class="Apple-style-span" style="font-family: Times;
          font-size: medium;">
          <pre style="white-space: pre-wrap; word-wrap: break-word; width: 1123px;">This email begins a working group last call for <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-pwe3-mpls-eth-oam-iwk-04.txt">draft-ietf-pwe3-mpls-eth-oam-iwk-04.txt</a>.

We are running this LC for three weeks due to its proximity to the Prague IETF.&nbsp;</pre>
          <pre style="white-space: pre-wrap; word-wrap: break-word; width: 1123px;">This WG LC will end on 25th March 2011.

Please respond with any comments to the PWE3 mailing list.

Regards,

Matthew and Andy
 </pre>
        </span></div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
pwe3 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pwe3@ietf.org">pwe3@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pwe3">https://www.ietf.org/mailman/listinfo/pwe3</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------000507010001030300080002--


From nick.delregno@verizon.com  Tue Mar 29 01:32:13 2011
Return-Path: <nick.delregno@verizon.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 089883A6ABB for <pwe3@core3.amsl.com>; Tue, 29 Mar 2011 01:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.249,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 ZCNtlK71Lotv for <pwe3@core3.amsl.com>; Tue, 29 Mar 2011 01:32:09 -0700 (PDT)
Received: from ashesmtp03.verizonbusiness.com (ashesmtp03.verizonbusiness.com [198.4.8.167]) by core3.amsl.com (Postfix) with ESMTP id 469593A6A9D for <pwe3@ietf.org>; Tue, 29 Mar 2011 01:32:06 -0700 (PDT)
Received: from omzismtp01.vzbi.com ([unknown] [165.122.46.164]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LIT000ZA946FM60@firewall.verizonbusiness.com> for pwe3@ietf.org; Tue, 29 Mar 2011 08:33:43 +0000 (GMT)
Received: from omzismtp01.vzbi.com ([unknown] [127.0.0.1]) by omzismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LIT009H3946QZ00@omzismtp01.vzbi.com> for pwe3@ietf.org; Tue, 29 Mar 2011 08:33:42 +0000 (GMT)
Received: from ASHSRV141.mcilink.com ([unknown] [153.39.68.167]) by omzismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LIT00A1G9451C00@omzismtp01.vzbi.com> for pwe3@ietf.org; Tue, 29 Mar 2011 08:33:42 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV141.mcilink.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 29 Mar 2011 08:33:40 +0000
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_01CBEDEC.01B34435"
Date: Tue, 29 Mar 2011 08:33:41 +0000
Message-id: <14584D6EE26B314187A4F68BA206060006FE2275@ASHEVS008.mcilink.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: PW/VCCV Implementation Survey Results Draft Posted...
Thread-index: Acvt6w0cljxMk3KoRvm0e9JP7sJJUQ==
From: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
To: pwe3@ietf.org
X-OriginalArrivalTime: 29 Mar 2011 08:33:40.0916 (UTC) FILETIME=[01D78F40:01CBEDEC]
Subject: [PWE3] PW/VCCV Implementation Survey Results Draft Posted...
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 08:32:13 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBEDEC.01B34435
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All:

=20

I have uploaded the draft with the complete survey results.  In my haste
to post the original draft before the deadline, and attempting to
resolve some IDNITS, I goofed on the draft name.  I have incorporated
list comments on the original draft as well as added the Appendix which
contains the verbatim (except for User/Vendor name scrub) responses.=20

=20

The draft can be found here:
http://www.ietf.org/id/draft-delregno-pwe3-pw-vccv-impl-survey-results-0
0.txt

=20

Thanks again to all who provided the valuable data contained therein.

=20

Regards,

Nick

=20

Christopher N. "Nick" Del Regno, PMTS

Verizon, CTO, Ethernet Technology & Transport

400 International Pkwy, 2C107

Richardson, TX  75081

972-729-3411

nick.delregno@verizon.com

=20


------_=_NextPart_001_01CBEDEC.01B34435
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: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 14 =
(filtered medium)"><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;}
/* 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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>All:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I have =
uploaded the draft with the complete survey results.&nbsp; In my haste =
to post the original draft before the deadline, and attempting to =
resolve some IDNITS, I goofed on the draft name.&nbsp; I have =
incorporated list comments on the original draft as well as added the =
Appendix which contains the verbatim (except for User/Vendor name scrub) =
responses. <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The draft can be found here: <a =
href=3D"http://www.ietf.org/id/draft-delregno-pwe3-pw-vccv-impl-survey-re=
sults-00.txt">http://www.ietf.org/id/draft-delregno-pwe3-pw-vccv-impl-sur=
vey-results-00.txt</a><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thanks again =
to all who provided the valuable data contained =
therein.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Regards,<o:p></o:p></p><p =
class=3DMsoNormal>Nick<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Christopher =
N. &#8220;Nick&#8221; Del Regno, PMTS<o:p></o:p></p><p =
class=3DMsoNormal>Verizon, CTO, Ethernet Technology &amp; =
Transport<o:p></o:p></p><p class=3DMsoNormal>400 International Pkwy, =
2C107<o:p></o:p></p><p class=3DMsoNormal>Richardson, TX&nbsp; =
75081<o:p></o:p></p><p class=3DMsoNormal>972-729-3411<o:p></o:p></p><p =
class=3DMsoNormal>nick.delregno@verizon.com<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------_=_NextPart_001_01CBEDEC.01B34435--

From yaakov_s@rad.com  Tue Mar 29 05:32:13 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 71DBD3A68C3 for <pwe3@core3.amsl.com>; Tue, 29 Mar 2011 05:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.211
X-Spam-Level: 
X-Spam-Status: No, score=-102.211 tagged_above=-999 required=5 tests=[AWL=0.388, 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 M+kp49k3+yHs for <pwe3@core3.amsl.com>; Tue, 29 Mar 2011 05:32:12 -0700 (PDT)
Received: from antivir2.rad.co.il (mx2-q.rad.co.il [80.74.100.144]) by core3.amsl.com (Postfix) with ESMTP id 303A43A6882 for <pwe3@ietf.org>; Tue, 29 Mar 2011 05:32:11 -0700 (PDT)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir2.rad.co.il with ESMTP; 29 Mar 2011 14:33:49 +0200
Received: from EXUS4-DRP.ad.rad.co.il (192.114.24.119) by EXRAD5.ad.rad.co.il (192.114.24.28) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 29 Mar 2011 14:33:49 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Tue, 29 Mar 2011 14:33:48 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, pwe3 <pwe3@ietf.org>
Thread-Topic: [PWE3] draft-li-pwe3-ms-pw-pon-03
Thread-Index: AQHL6srdlXenPcvrIk65/amkDPuQaJRELkCA
Date: Tue, 29 Mar 2011 12:33:48 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903D1F7A1@EXRAD5.ad.rad.co.il>
References: <4D8C592C.6010802@cisco.com>
In-Reply-To: <4D8C592C.6010802@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [207.232.33.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-li-pwe3-ms-pw-pon@tools.ietf.org" <draft-li-pwe3-ms-pw-pon@tools.ietf.org>
Subject: Re: [PWE3] draft-li-pwe3-ms-pw-pon-03
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 12:32:13 -0000

draft-li-pwe3-ms-pw-pon authors,=20

I have only scanned the first few pages, but already have a question.

Why is this draft limited to GPON ?
It makes equal sense to open PWs over EPON (and I know of 2 vendors doing t=
his).

Obviously you wanted this to be a general PON solution,=20
since you call the draft "pw-pon" and not "pw-gpon".

Can the mechanisms defined for the OMCI management channel,
be similarly defined for EPON using MPCP control packets ?
Admittedly G.984.4 already explicitly defines PW functionality,
but this is only TDM PWs; and MPCP certainly has plenty of available opcode=
s ...

Y(J)S


-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Ste=
wart Bryant
Sent: Friday, March 25, 2011 11:58
To: pwe3
Cc: draft-li-pwe3-ms-pw-pon@tools.ietf.org
Subject: [PWE3] draft-li-pwe3-ms-pw-pon-03

I have received a request to sponsor this draft to publication,
and believe that the draft is worth publication.

The draft is not within the scope of PWE3, but none-the-less,
review by members of the PWE3 WG would be useful.

Please can I have any review comments  by 18th April.

Thanks

Stewart


> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> Sent: 11 March 2011 14:27
> To: hongyu.lihongyu@huawei.com
> Cc: robin@huawei.com; Adrian.Farrel@huawei.com
> Subject: New Version Notification for draft-li-pwe3-ms-pw-pon-03
>
>
> A new version of I-D, draft-li-pwe3-ms-pw-pon-03.txt has been successfull=
y
> submitted by Li Hongyu and posted to the IETF repository.
>
> Filename:	 draft-li-pwe3-ms-pw-pon
> Revision:	 03
> Title:		 Multisegment Pseudowires in Passive Optical Networks
> Creation_date:	 2011-03-11
> WG ID:		 Independent Submission
> Number_of_pages: 12
>
> Abstract:
> This document describes the application of MPLS multi-segment
> pseudowires (MS-PWs) in a dual-technology environment comprising a
> Passive Optical Network (PON) and an MPLS Packet Switched Network
> (PSN).
>
> PON technology may be used in mobile backhaul networks to support the
> end segments closest to the aggregation devices.  In these cases,
> there may be a very large number of PW Terminating Provider Edge
> nodes (T-PEs).  The MPLS control plane could be used to provision
> these end segments, but support for the necessary protocols would
> complicate the management of the T-PEs and would significantly
> increase their expense.  Alternatively, static, or management plane,
> configuration could be used to configure the end segments, but the
> very large number of such segments in a PON places a very heavy
> burden on the network manager.
>
> This document describes how to set up the end segment of an end-to-
> end MPLS PW over a Gigabit-capable Passive Optical Network (GPON)
> using the GPON management protocol, Optical Network Termination
> Management and Control Interface (OMCI).  This simplifies and speeds
> up PW provisioning.
>
> This document also shows how a MS-PW may be constructed from an end
> segment supported over a PON, and stitched to one or more segments
> supported over an MPLS PSN.
>
>
>
> The IETF Secretariat.



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

From agmalis@gmail.com  Wed Mar 30 00:41:51 2011
Return-Path: <agmalis@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B50A73A6B20 for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 00:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, 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 RU4T3vdhyrjU for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 00:41:50 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id B29473A6A1F for <pwe3@ietf.org>; Wed, 30 Mar 2011 00:41:50 -0700 (PDT)
Received: by vxg33 with SMTP id 33so928555vxg.31 for <pwe3@ietf.org>; Wed, 30 Mar 2011 00:43:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; bh=sV9pVWPnUKk4iYV7lkE90a5anS0ymPbuDcLHnQoRG1E=; b=F5aJlU10BsbnXU6dlMATNBx2S4gmqw00loKkHg/6Vr73bxE4M7VA5wN31tuErvCSba JNmDHtyez0NgT3aaAa/0lqzeQVF2TNEvLq5JCKOnQ8nvHiW6sYJyfciKpHLZfthDp3TK axK9rtf7m//GuMNfY2cm26rHT/9me2ak2DaRY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=Lb/HzWea0D2LS8U8F29rv0ZWWdqwiLz64VD2ueZ4f2Wk4LWnNTvYOPOtWRDoPqTB4P YVQwo5bR1Ep/gK2rHmqmHGFJgslIPlNfjn1XjC23gQ3tOR+IZ4q3IZ2ddHc92Iy9Ff/i Hcy5VboYc6FxqqbsfVyl3gMz3HCWpzuCZc3Hs=
Received: by 10.220.193.193 with SMTP id dv1mr224481vcb.97.1301471009181; Wed, 30 Mar 2011 00:43:29 -0700 (PDT)
MIME-Version: 1.0
Sender: agmalis@gmail.com
Received: by 10.220.192.198 with HTTP; Wed, 30 Mar 2011 00:43:09 -0700 (PDT)
In-Reply-To: <0bb501cbeeac$e6a72390$b3f56ab0$@huawei.com>
References: <0bb501cbeeac$e6a72390$b3f56ab0$@huawei.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Date: Wed, 30 Mar 2011 09:43:09 +0200
X-Google-Sender-Auth: f345TB7jdxPiMLk0tJf3WlBc51o
Message-ID: <AANLkTimWfkQo7LcSawWVVH25LdsErQzRn3GnmS=QxYsM@mail.gmail.com>
To: pwe3@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [PWE3] Fwd: Routing Area Open Meeting room change
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 07:41:51 -0000

PWE3 WG - please note the room change below - the routing area open
meeting has moved next door to be able to fit more people in the
meeting.

Cheers,
Andy

---------- Forwarded message ----------
From: 80all-bounces@ietf.org [mailto:80all-bounces@ietf.org] On Behalf
Of Wanda Lo
Sent: 30 March 2011 09:01
To: 80all@ietf.org
Subject: [80all] Wednesday 3-30-2011 Agenda Change

Hi Everyone,

There's a room change in today's afternoon session I (13:00-15:00).

RTGAREA has moved to Congress Hall II.

CLUE has moved to Congress Hall I.

Please note it in on your pocket agenda to reflect the change. =A0Of
course, the agenda on the IETF website
(https://datatracker.ietf.org/meeting/80/agenda.html) always has the
most up-to-date information.

Thanks,
Wanda

From Alexander.Vainshtein@ecitele.com  Wed Mar 30 01:36:50 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE09F3A6919 for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.018,  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 CKJmpOguZHsm for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:36:47 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id 9E9AA3A6B23 for <pwe3@ietf.org>; Wed, 30 Mar 2011 01:36:46 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-07-4d92eb9a3f4c
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id B5.2D.19639.A9BE29D4; Wed, 30 Mar 2011 10:36:42 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 30 Mar 2011 10:37:07 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>, Luca Martini <lmartini@cisco.com>
Date: Wed, 30 Mar 2011 10:36:48 +0200
Thread-Topic: GAL above and below the PW label
Thread-Index: AcvutZvlGmSRrVeFSXC5cusO2AV7Yg==
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D07246@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_A3C5DF08D38B6049839A6F553B331C76D722D07246ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: pwe3 <pwe3@ietf.org>
Subject: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 08:36:50 -0000

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

Tom, Luca and all,
I would like to clarify - again - my position regarding GAL above the PW la=
bel.
I think that, other issues notwithstanding, it would create an issue if use=
d with MS-PWs:

*         GAL would be exposed at each S-PE (making a presumably end-to-end=
 OAM message to be intercepted)

*         What is even worse, there is no rule for forwarding the packet th=
at has been intercepted due to an exposed GAL (until you count the statemen=
t in 5586 requesting that a packet MUST NOT be ever forwarded based on GAL:=
)).  Hence it would be perfectly valid just to drop such a packet at the fi=
rst S-PE it crosses...
This said, I still  do not think using GAL below the PW label is a good ide=
a either. But this is a different story...

Regards,
     Sasha


--_000_A3C5DF08D38B6049839A6F553B331C76D722D07246ILPTMAIL02eci_
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-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	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;}
.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;}
/* List Definitions */
@list l0
	{mso-list-id:2080134743;
	mso-list-type:hybrid;
	mso-list-template-ids:1120185242 67698689 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Tom, Luca and al=
l,<o:p></o:p></p><p class=3DMsoNormal>I would like to clarify &#8211; again=
 &#8211; my position regarding GAL above the PW label.<o:p></o:p></p><p cla=
ss=3DMsoNormal>I think that, other issues notwithstanding, it would create =
an issue if used with MS-PWs:<o:p></o:p></p><p class=3DMsoListParagraph sty=
le=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><sp=
an style=3D'font-family:Symbol'><span style=3D'mso-list:Ignore'>&middot;<sp=
an style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; </span></span></span><![endif]><span dir=3DLTR></span>GAL w=
ould be exposed at each S-PE (making a presumably end-to-end OAM message to=
 be intercepted)<o:p></o:p></p><p class=3DMsoListParagraph style=3D'text-in=
dent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=3D'f=
ont-family:Symbol'><span style=3D'mso-list:Ignore'>&middot;<span style=3D'f=
ont:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; </span></span></span><![endif]><span dir=3DLTR></span>What is even worse=
, there is no rule for forwarding the packet that has been intercepted due =
to an exposed GAL (until you count the statement in 5586 requesting that a =
packet MUST NOT be ever forwarded based on GAL<span style=3D'font-family:Wi=
ngdings'>J</span>).&nbsp; Hence it would be perfectly valid just to drop su=
ch a packet at the first S-PE it crosses&#8230;<o:p></o:p></p><p class=3DMs=
oNormal>This said, I still&nbsp; do not think using GAL below the PW label =
is a good idea either. But this is a different story&#8230;<o:p></o:p></p><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></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_A3C5DF08D38B6049839A6F553B331C76D722D07246ILPTMAIL02eci_--

From loa@pi.nu  Wed Mar 30 01:42:51 2011
Return-Path: <loa@pi.nu>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2B443A6AFB for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P-Gl7NMG-eW0 for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:42:50 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 1F6EA3A6919 for <pwe3@ietf.org>; Wed, 30 Mar 2011 01:42:49 -0700 (PDT)
Received: from [130.129.22.69] (dhcp-1645.meeting.ietf.org [130.129.22.69]) (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 02B2D2A8001 for <pwe3@ietf.org>; Wed, 30 Mar 2011 10:44:27 +0200 (CEST)
Message-ID: <4D92ED69.1040204@pi.nu>
Date: Wed, 30 Mar 2011 10:44:25 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: pwe3@ietf.org
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 08:42:51 -0000

Sasha,

what do you mean with "exposed" I thought that what is gpoing on
in an S-PE is normal MPLS label switching.

/Loa

On 2011-03-30 10:36, Alexander Vainshtein wrote:
> Tom, Luca and all,
>
> I would like to clarify – again – my position regarding GAL above the PW
> label.
>
> I think that, other issues notwithstanding, it would create an issue if
> used with MS-PWs:
>
> ·GAL would be exposed at each S-PE (making a presumably end-to-end OAM
> message to be intercepted)
>
> ·What is even worse, there is no rule for forwarding the packet that has
> been intercepted due to an exposed GAL (until you count the statement in
> 5586 requesting that a packet MUST NOT be ever forwarded based on GALJ).
> Hence it would be perfectly valid just to drop such a packet at the
> first S-PE it crosses…
>
> This said, I still do not think using GAL below the PW label is a good
> idea either. But this is a different story…
>
> Regards,
>
> Sasha
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

-- 


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 aldrin.ietf@gmail.com  Wed Mar 30 01:50:09 2011
Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C361D28C0DB for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 116BDRIAIAAl for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:50:09 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id A637E28C0DD for <pwe3@ietf.org>; Wed, 30 Mar 2011 01:50:08 -0700 (PDT)
Received: by bwz13 with SMTP id 13so860910bwz.31 for <pwe3@ietf.org>; Wed, 30 Mar 2011 01:51:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:x-mailer:from :subject:date:to; bh=I1KYcn6LjvAsCKzhiFKZUaHIV/PqnyL2JKiLmJnhOew=; b=BJtYbKzfIzz0d+zZuRiqeOSHug5g+9+eg/OkWog0LIUrMOUW4QHtdcnsf/KjvOGvGE ZvG78Bju6ZfEy2FUkW0DF8WPPqgHyJULbzq8XWpCAEW6hu7ch1bNe0ADk/RnhlSbM2fO lh3QncilJjjZ7/ErLzg1xmKt2eU8dNwteBBgg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; b=HtW2veIsdNcXsl91wOEGAogi36PgBXxxEaR5gbZ+Stk0nSfGliFhgHVcH6WXqFKvQ7 GLYaH6DH98kK5YJ/Q6p4ZwT0Vj+NS/9zvRXl+A7M7ZeqAFmWEzdfPRm3k2C+6Qx8DMd+ U8j+Z6zlz37h7/+/w3jwUv0OPCnSd55kg+LJ4=
Received: by 10.204.126.148 with SMTP id c20mr759476bks.87.1301475106381; Wed, 30 Mar 2011 01:51:46 -0700 (PDT)
Received: from [130.129.17.216] (dhcp-11d8.meeting.ietf.org [130.129.17.216]) by mx.google.com with ESMTPS id t1sm3926607bkx.19.2011.03.30.01.51.41 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Mar 2011 01:51:42 -0700 (PDT)
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com> <4D92ED69.1040204@pi.nu>
In-Reply-To: <4D92ED69.1040204@pi.nu>
Mime-Version: 1.0 (iPad Mail 8G4)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <51C51C1B-906E-4108-98C8-D2D86B69D682@gmail.com>
X-Mailer: iPad Mail (8G4)
From: Sam Aldrin <aldrin.ietf@gmail.com>
Date: Wed, 30 Mar 2011 01:51:40 -0700
To: Loa Andersson <loa@pi.nu>
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 08:50:09 -0000

When ms-pw ping is performed, the packet should not be processed at S-PE, un=
less the PW label ttl is expired. With the proposed GAL label above PW label=
, how do you ensure the OAM packet take the same data path to reach far-end T=
-PE, without getting processed/punted at S-PE? Or for that matter go beyond f=
irst S-PE?

-sam

Sent from my iPad

On Mar 30, 2011, at 1:44 AM, Loa Andersson <loa@pi.nu> wrote:

> Sasha,
>=20
> what do you mean with "exposed" I thought that what is gpoing on
> in an S-PE is normal MPLS label switching.
>=20
> /Loa
>=20
> On 2011-03-30 10:36, Alexander Vainshtein wrote:
>> Tom, Luca and all,
>>=20
>> I would like to clarify =E2=80=93 again =E2=80=93 my position regarding G=
AL above the PW
>> label.
>>=20
>> I think that, other issues notwithstanding, it would create an issue if
>> used with MS-PWs:
>>=20
>> =C2=B7GAL would be exposed at each S-PE (making a presumably end-to-end O=
AM
>> message to be intercepted)
>>=20
>> =C2=B7What is even worse, there is no rule for forwarding the packet that=
 has
>> been intercepted due to an exposed GAL (until you count the statement in
>> 5586 requesting that a packet MUST NOT be ever forwarded based on GALJ).
>> Hence it would be perfectly valid just to drop such a packet at the
>> first S-PE it crosses=E2=80=A6
>>=20
>> This said, I still do not think using GAL below the PW label is a good
>> idea either. But this is a different story=E2=80=A6
>>=20
>> Regards,
>>=20
>> Sasha
>>=20
>>=20
>>=20
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>=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
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

From DanielC@orckit.com  Wed Mar 30 01:50:41 2011
Return-Path: <DanielC@orckit.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AB743A6AFB for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:50:41 -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=[AWL=-0.002,  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 aNqFutaNKLIf for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:50:37 -0700 (PDT)
Received: from tlvmail1.orckit.com (tlvmail1.orckit.com [213.31.203.2]) by core3.amsl.com (Postfix) with ESMTP id 4D7903A6919 for <pwe3@ietf.org>; Wed, 30 Mar 2011 01:50:36 -0700 (PDT)
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_01CBEEB7.C443D51A"
Date: Wed, 30 Mar 2011 10:52:15 +0200
Message-ID: <44F4E579A764584EA9BDFD07D0CA0813069E1510@tlvmail1>
In-reply-to: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] GAL above and below the PW label
Thread-Index: AcvutZvlGmSRrVeFSXC5cusO2AV7YgAAT6SQ
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com>
From: "Daniel Cohn" <DanielC@orckit.com>
To: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
Cc: pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 08:50:41 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBEEB7.C443D51A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

=20

Why would S-PE look beyond PW label if TTL has not expired?

=20

DC

=20

From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Alexander Vainshtein
Sent: Wednesday, March 30, 2011 10:37 AM
To: Thomas Nadeau; Luca Martini
Cc: pwe3
Subject: [PWE3] GAL above and below the PW label

=20

Tom, Luca and all,

I would like to clarify - again - my position regarding GAL above the PW
label.

I think that, other issues notwithstanding, it would create an issue if
used with MS-PWs:

*         GAL would be exposed at each S-PE (making a presumably
end-to-end OAM message to be intercepted)

*         What is even worse, there is no rule for forwarding the packet
that has been intercepted due to an exposed GAL (until you count the
statement in 5586 requesting that a packet MUST NOT be ever forwarded
based on GALJ).  Hence it would be perfectly valid just to drop such a
packet at the first S-PE it crosses...

This said, I still  do not think using GAL below the PW label is a good
idea either. But this is a different story...

=20

Regards,

     Sasha

=20


------_=_NextPart_001_01CBEEB7.C443D51A
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)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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;}
/* List Definitions */
@list l0
	{mso-list-id:2080134743;
	mso-list-type:hybrid;
	mso-list-template-ids:1120185242 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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'>Hi,<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'>Why would S-PE look =
beyond PW label if TTL has not expired?<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'>DC<o:p></o:p></span></p><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"'> =
pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] <b>On Behalf Of =
</b>Alexander Vainshtein<br><b>Sent:</b> Wednesday, March 30, 2011 10:37 =
AM<br><b>To:</b> Thomas Nadeau; Luca Martini<br><b>Cc:</b> =
pwe3<br><b>Subject:</b> [PWE3] GAL above and below the PW =
label<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Tom, Luca =
and all,<o:p></o:p></p><p class=3DMsoNormal>I would like to clarify =
&#8211; again &#8211; my position regarding GAL above the PW =
label.<o:p></o:p></p><p class=3DMsoNormal>I think that, other issues =
notwithstanding, it would create an issue if used with =
MS-PWs:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span>GAL would be =
exposed at each S-PE (making a presumably end-to-end OAM message to be =
intercepted)<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span>What is even =
worse, there is no rule for forwarding the packet that has been =
intercepted due to an exposed GAL (until you count the statement in 5586 =
requesting that a packet MUST NOT be ever forwarded based on GAL<span =
style=3D'font-family:Wingdings'>J</span>).&nbsp; Hence it would be =
perfectly valid just to drop such a packet at the first S-PE it =
crosses&#8230;<o:p></o:p></p><p class=3DMsoNormal>This said, I =
still&nbsp; do not think using GAL below the PW label is a good idea =
either. But this is a different story&#8230;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></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>
------_=_NextPart_001_01CBEEB7.C443D51A--

From Alexander.Vainshtein@ecitele.com  Wed Mar 30 01:50:52 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B11F73A6919 for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018,  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 iwQ7KTnhu9Ee for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:50:51 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id 6706428C111 for <pwe3@ietf.org>; Wed, 30 Mar 2011 01:50:51 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-8e-4d92eee791cc
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id 5A.8D.19639.7EEE29D4; Wed, 30 Mar 2011 10:50:47 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 30 Mar 2011 10:52:07 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Loa Andersson <loa@pi.nu>
Date: Wed, 30 Mar 2011 10:51:59 +0200
Thread-Topic: [PWE3] GAL above and below the PW label
Thread-Index: AcvutshayaskeNZEQU2HvklLSBNAZAAADu6Q
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D0725E@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com> <4D92ED69.1040204@pi.nu>
In-Reply-To: <4D92ED69.1040204@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
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 08:50:52 -0000

Loa,
The VCCV Type 4 draft (http://tools.ietf.org/html/draft-nadeau-pwe3-vccv-2)=
 proposed having the GAL above the PW label and ACH header below it.


I include the relevant fragment of the draft below:
<quote>
3. VCCV Control Channel When The Control Word is Not Used

   When the PWE3 Control Word is not used a new CC Type 4 is defined
as follows.

0                   1                   2                   3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                              GAL                              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                            PW Label                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 1|Version|   Reserved    |  Associated Channel Type      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
~                        VCCV Message Body                      ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<end quote>

If this occurs happens in the MS-PW scenario, GAL would be exposed at the f=
irst S-PE that happens to receive the packet (because the tunnel label is t=
erminated at S-PE). =20

Hopefully this clarifies my concern.

Regards,
     Sasha


> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> Loa Andersson
> Sent: Wednesday, March 30, 2011 10:44 AM
> To: pwe3@ietf.org
> Subject: Re: [PWE3] GAL above and below the PW label
>=20
> Sasha,
>=20
> what do you mean with "exposed" I thought that what is gpoing on
> in an S-PE is normal MPLS label switching.
>=20
> /Loa
>=20
> On 2011-03-30 10:36, Alexander Vainshtein wrote:
> > Tom, Luca and all,
> >
> > I would like to clarify - again - my position regarding GAL above the
> PW
> > label.
> >
> > I think that, other issues notwithstanding, it would create an issue
> if
> > used with MS-PWs:
> >
> > *GAL would be exposed at each S-PE (making a presumably end-to-end
> OAM
> > message to be intercepted)
> >
> > *What is even worse, there is no rule for forwarding the packet that
> has
> > been intercepted due to an exposed GAL (until you count the statement
> in
> > 5586 requesting that a packet MUST NOT be ever forwarded based on
> GALJ).
> > Hence it would be perfectly valid just to drop such a packet at the
> > first S-PE it crosses...
> >
> > This said, I still do not think using GAL below the PW label is a
> good
> > idea either. But this is a different story...
> >
> > Regards,
> >
> > Sasha
> >
> >
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
>=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
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

From david.i.allan@ericsson.com  Wed Mar 30 01:50:55 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D0C03A6B2A for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.013
X-Spam-Level: 
X-Spam-Status: No, score=-5.013 tagged_above=-999 required=5 tests=[AWL=1.585,  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 NdUgTVFLiymF for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:50:50 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 93B453A6B24 for <pwe3@ietf.org>; Wed, 30 Mar 2011 01:50:50 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2U8qPPZ004740; Wed, 30 Mar 2011 03:52:26 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.203]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 30 Mar 2011 04:52:19 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, Thomas Nadeau <tnadeau@lucidvision.com>, Luca Martini <lmartini@cisco.com>
Date: Wed, 30 Mar 2011 04:52:18 -0400
Thread-Topic: GAL above and below the PW label
Thread-Index: AcvutZvlGmSRrVeFSXC5cusO2AV7YgAAT/bw
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se>
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D722D07246@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_60C093A41B5E45409A19D42CF7786DFD51D5310B53EUSAACMS0703e_"
MIME-Version: 1.0
Cc: pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 08:50:55 -0000

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

It does become a new behavior, GAL with S=3D0. However the combination of G=
AL being top label at the S-PE and TTL being encoded in the PW label means =
that fate sharing is broken at every S-PE. Life only gets a little more str=
ange if there is a FAT label as well...

That being said, GAL as bottom label is broken in any ECMP environment, whi=
ch is why GAL is a TP construct.

my 2 cents
D

________________________________
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Ale=
xander Vainshtein
Sent: Wednesday, March 30, 2011 10:37 AM
To: Thomas Nadeau; Luca Martini
Cc: pwe3
Subject: [PWE3] GAL above and below the PW label

Tom, Luca and all,
I would like to clarify - again - my position regarding GAL above the PW la=
bel.
I think that, other issues notwithstanding, it would create an issue if use=
d with MS-PWs:

*         GAL would be exposed at each S-PE (making a presumably end-to-end=
 OAM message to be intercepted)

*         What is even worse, there is no rule for forwarding the packet th=
at has been intercepted due to an exposed GAL (until you count the statemen=
t in 5586 requesting that a packet MUST NOT be ever forwarded based on GAL:=
)).  Hence it would be perfectly valid just to drop such a packet at the fi=
rst S-PE it crosses...
This said, I still  do not think using GAL below the PW label is a good ide=
a either. But this is a different story...

Regards,
     Sasha


--_000_60C093A41B5E45409A19D42CF7786DFD51D5310B53EUSAACMS0703e_
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.18565" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Wingdings;
}
@font-face {
	font-family: Wingdings;
}
@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
}
P.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
LI.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe=
rsonal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
OL {
	MARGIN-BOTTOM: 0cm
}
UL {
	MARGIN-BOTTOM: 0cm
}
</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=3D832444508-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>It does&nbsp;become a new behavior, GAL with S=3D0=
. However=20
the combination of GAL being top label at the S-PE and TTL being encoded in=
 the=20
PW label means that fate sharing is broken at every S-PE. Life only gets a=
=20
little more strange if there is a FAT label as well...</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D832444508-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D832444508-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>That being said, GAL as bottom label is broken in =
any ECMP=20
environment, which is why GAL is a TP construct.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D832444508-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D832444508-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>my 2 cents</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D832444508-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>D</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> pwe3-bounces@ietf.org=20
[mailto:pwe3-bounces@ietf.org] <B>On Behalf Of </B>Alexander=20
Vainshtein<BR><B>Sent:</B> Wednesday, March 30, 2011 10:37 AM<BR><B>To:</B>=
=20
Thomas Nadeau; Luca Martini<BR><B>Cc:</B> pwe3<BR><B>Subject:</B> [PWE3] GA=
L=20
above and below the PW label<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DWordSection1>
<P class=3DMsoNormal>Tom, Luca and all,<o:p></o:p></P>
<P class=3DMsoNormal>I would like to clarify &#8211; again &#8211; my posit=
ion regarding GAL=20
above the PW label.<o:p></o:p></P>
<P class=3DMsoNormal>I think that, other issues notwithstanding, it would c=
reate=20
an issue if used with MS-PWs:<o:p></o:p></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -18pt; mso-list: l0 level=
1 lfo1"><![if !supportLists]><SPAN=20
style=3D"FONT-FAMILY: Symbol"><SPAN style=3D"mso-list: Ignore">&middot;<SPA=
N=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><![endif]><SPAN dir=3Dltr></SPAN>GAL would be exposed =
at each=20
S-PE (making a presumably end-to-end OAM message to be=20
intercepted)<o:p></o:p></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -18pt; mso-list: l0 level=
1 lfo1"><![if !supportLists]><SPAN=20
style=3D"FONT-FAMILY: Symbol"><SPAN style=3D"mso-list: Ignore">&middot;<SPA=
N=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><![endif]><SPAN dir=3Dltr></SPAN>What is even worse, t=
here is=20
no rule for forwarding the packet that has been intercepted due to an expos=
ed=20
GAL (until you count the statement in 5586 requesting that a packet MUST NO=
T be=20
ever forwarded based on GAL<SPAN style=3D"FONT-FAMILY: Wingdings">J</SPAN>)=
.&nbsp;=20
Hence it would be perfectly valid just to drop such a packet at the first S=
-PE=20
it crosses&#8230;<o:p></o:p></P>
<P class=3DMsoNormal>This said, I still&nbsp; do not think using GAL below =
the PW=20
label is a good idea either. But this is a different story&#8230;<o:p></o:p=
></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></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_60C093A41B5E45409A19D42CF7786DFD51D5310B53EUSAACMS0703e_--

From Alexander.Vainshtein@ecitele.com  Wed Mar 30 01:57:06 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90BD93A6957 for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.017,  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 Z8-6K8WCuNZj for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 01:57:01 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id DEAD428C0F0 for <pwe3@ietf.org>; Wed, 30 Mar 2011 01:57:00 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-4c-4d92f057d167
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id 25.BD.19639.750F29D4; Wed, 30 Mar 2011 10:56:56 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 30 Mar 2011 10:56:45 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: David Allan I <david.i.allan@ericsson.com>
Date: Wed, 30 Mar 2011 10:56:34 +0200
Thread-Topic: GAL above and below the PW label
Thread-Index: AcvutZvlGmSRrVeFSXC5cusO2AV7YgAAT/bwAABLXqA=
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D07263@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51D5310B53@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_A3C5DF08D38B6049839A6F553B331C76D722D07263ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: pwe3 <pwe3@ietf.org>, Luca, Martini <lmartini@cisco.com>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 08:57:06 -0000

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

Dave,
GAL may be a TP construct, but, IMO, MS-PWs (if not the other things) will =
easily break the demarcation lines between TP and non-TP areas.

If we stick with GAL being an MPLS-TP construct we should, IMHO, drop the a=
ttempts to use it with Ws.

Regards,
     Sasha

From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: Wednesday, March 30, 2011 10:52 AM
To: Alexander Vainshtein; Thomas Nadeau; Luca Martini
Cc: pwe3
Subject: RE: GAL above and below the PW label

It does become a new behavior, GAL with S=3D0. However the combination of G=
AL being top label at the S-PE and TTL being encoded in the PW label means =
that fate sharing is broken at every S-PE. Life only gets a little more str=
ange if there is a FAT label as well...

That being said, GAL as bottom label is broken in any ECMP environment, whi=
ch is why GAL is a TP construct.

my 2 cents
D

________________________________
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Ale=
xander Vainshtein
Sent: Wednesday, March 30, 2011 10:37 AM
To: Thomas Nadeau; Luca Martini
Cc: pwe3
Subject: [PWE3] GAL above and below the PW label
Tom, Luca and all,
I would like to clarify - again - my position regarding GAL above the PW la=
bel.
I think that, other issues notwithstanding, it would create an issue if use=
d with MS-PWs:

*         GAL would be exposed at each S-PE (making a presumably end-to-end=
 OAM message to be intercepted)

*         What is even worse, there is no rule for forwarding the packet th=
at has been intercepted due to an exposed GAL (until you count the statemen=
t in 5586 requesting that a packet MUST NOT be ever forwarded based on GAL:=
)).  Hence it would be perfectly valid just to drop such a packet at the fi=
rst S-PE it crosses...
This said, I still  do not think using GAL below the PW label is a good ide=
a either. But this is a different story...

Regards,
     Sasha


--_000_A3C5DF08D38B6049839A6F553B331C76D722D07263ILPTMAIL02eci_
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-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator 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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Dave,<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>GAL may be a TP construct, but, IMO, MS-PWs (if not the =
other things) will easily break the demarcation lines between TP and non-TP=
 areas.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F4=
97D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'color:=
#1F497D'>If we stick with GAL being an MPLS-TP construct we should, IMHO, d=
rop the attempts to use it with Ws.<o:p></o:p></span></p><p class=3DMsoNorm=
al><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><p class=
=3DMsoNormal><span style=3D'color:#1F497D'>Regards,<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; S=
asha<o:p></o:p></span></p></div><p class=3DMsoNormal><span style=3D'color:#=
1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:s=
olid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;b=
order-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNorm=
al><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Fr=
om:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-se=
rif"'> David Allan I [mailto:david.i.allan@ericsson.com] <br><b>Sent:</b> W=
ednesday, March 30, 2011 10:52 AM<br><b>To:</b> Alexander Vainshtein; Thoma=
s Nadeau; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> RE: GAL above =
and below the PW label<o:p></o:p></span></p></div></div><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt=
;font-family:"Arial","sans-serif";color:blue'>It does&nbsp;become a new beh=
avior, GAL with S=3D0. However the combination of GAL being top label at th=
e S-PE and TTL being encoded in the PW label means that fate sharing is bro=
ken at every S-PE. Life only gets a little more strange if there is a FAT l=
abel as well...</span><span style=3D'font-size:12.0pt;font-family:"Times Ne=
w 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","sans-serif";color:blue'>That being said, GAL as bottom label is br=
oken in any ECMP environment, which is why GAL is a TP construct.</span><sp=
an 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-fa=
mily:"Times New Roman","serif"'>&nbsp;<o:p></o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";colo=
r:blue'>my 2 cents</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:10.0pt;font-family:"Arial","sans-serif";color:blue'>D</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"'><o:p>&nbsp;</o:p></span></p><div class=3D=
MsoNormal align=3Dcenter style=3D'text-align:center'><span style=3D'font-si=
ze: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:1=
2.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","san=
s-serif"'> pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] <b>On Behal=
f Of </b>Alexander Vainshtein<br><b>Sent:</b> Wednesday, March 30, 2011 10:=
37 AM<br><b>To:</b> Thomas Nadeau; Luca Martini<br><b>Cc:</b> pwe3<br><b>Su=
bject:</b> [PWE3] GAL above and below the PW label</span><span style=3D'fon=
t-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>=
<p class=3DMsoNormal>Tom, Luca and all,<o:p></o:p></p><p class=3DMsoNormal>=
I would like to clarify &#8211; again &#8211; my position regarding GAL abo=
ve the PW label.<o:p></o:p></p><p class=3DMsoNormal>I think that, other iss=
ues notwithstanding, it would create an issue if used with MS-PWs:<o:p></o:=
p></p><p class=3DMsoListParagraph style=3D'text-indent:-18.0pt'><span style=
=3D'font-family:Symbol'>&middot;</span><span style=3D'font-size:7.0pt;font-=
family:"Times New Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; </span>GAL would be exposed at each S-PE (making a presumably end-t=
o-end OAM message to be intercepted)<o:p></o:p></p><p class=3DMsoListParagr=
aph style=3D'text-indent:-18.0pt'><span style=3D'font-family:Symbol'>&middo=
t;</span><span style=3D'font-size:7.0pt;font-family:"Times New Roman","seri=
f"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>What is even wo=
rse, there is no rule for forwarding the packet that has been intercepted d=
ue to an exposed GAL (until you count the statement in 5586 requesting that=
 a packet MUST NOT be ever forwarded based on GAL<span style=3D'font-family=
:Wingdings'>J</span>).&nbsp; Hence it would be perfectly valid just to drop=
 such a packet at the first S-PE it crosses&#8230;<o:p></o:p></p><p class=
=3DMsoNormal>This said, I still&nbsp; do not think using GAL below the PW l=
abel is a good idea either. But this is a different story&#8230;<o:p></o:p>=
</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></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></div></body></html>=

--_000_A3C5DF08D38B6049839A6F553B331C76D722D07263ILPTMAIL02eci_--

From david.i.allan@ericsson.com  Wed Mar 30 02:18:08 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF8BF3A697A for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 02:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.157
X-Spam-Level: 
X-Spam-Status: No, score=-5.157 tagged_above=-999 required=5 tests=[AWL=1.441,  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 y05WokVL-UFl for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 02:18:03 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 1C7B13A6875 for <pwe3@ietf.org>; Wed, 30 Mar 2011 02:18:03 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2U9Jccf005130; Wed, 30 Mar 2011 04:19:39 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.203]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Wed, 30 Mar 2011 05:19:32 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Date: Wed, 30 Mar 2011 05:19:29 -0400
Thread-Topic: GAL above and below the PW label
Thread-Index: AcvutZvlGmSRrVeFSXC5cusO2AV7YgAAT/bwAABLXqAAALAbwA==
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51D5310B6D@EUSAACMS0703.eamcs.ericsson.se>
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se> <A3C5DF08D38B6049839A6F553B331C76D722D07263@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D722D07263@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_60C093A41B5E45409A19D42CF7786DFD51D5310B6DEUSAACMS0703e_"
MIME-Version: 1.0
Cc: pwe3 <pwe3@ietf.org>, Luca, Martini <lmartini@cisco.com>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 09:18:09 -0000

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

Well one use case is PW interworking between MPLS-TP and MPLS domains....MS=
-PWs over multiple domains

The choice is fate sharing with the MPLS path in ECMP and not fate sharing =
with the S-PE implementation OR vice versa....depending on GAL above or bel=
ow

"damned if you do...damned if you don't"

So as the GAL is really a TP construct and cannot be made to work in a usef=
ul fashion for the above use case, I think I agree.

D

________________________________
From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
Sent: Wednesday, March 30, 2011 10:57 AM
To: David Allan I
Cc: pwe3; Thomas Nadeau; Luca Martini
Subject: RE: GAL above and below the PW label

Dave,
GAL may be a TP construct, but, IMO, MS-PWs (if not the other things) will =
easily break the demarcation lines between TP and non-TP areas.

If we stick with GAL being an MPLS-TP construct we should, IMHO, drop the a=
ttempts to use it with Ws.

Regards,
     Sasha

From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: Wednesday, March 30, 2011 10:52 AM
To: Alexander Vainshtein; Thomas Nadeau; Luca Martini
Cc: pwe3
Subject: RE: GAL above and below the PW label

It does become a new behavior, GAL with S=3D0. However the combination of G=
AL being top label at the S-PE and TTL being encoded in the PW label means =
that fate sharing is broken at every S-PE. Life only gets a little more str=
ange if there is a FAT label as well...

That being said, GAL as bottom label is broken in any ECMP environment, whi=
ch is why GAL is a TP construct.

my 2 cents
D

________________________________
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Ale=
xander Vainshtein
Sent: Wednesday, March 30, 2011 10:37 AM
To: Thomas Nadeau; Luca Martini
Cc: pwe3
Subject: [PWE3] GAL above and below the PW label
Tom, Luca and all,
I would like to clarify - again - my position regarding GAL above the PW la=
bel.
I think that, other issues notwithstanding, it would create an issue if use=
d with MS-PWs:

*         GAL would be exposed at each S-PE (making a presumably end-to-end=
 OAM message to be intercepted)

*         What is even worse, there is no rule for forwarding the packet th=
at has been intercepted due to an exposed GAL (until you count the statemen=
t in 5586 requesting that a packet MUST NOT be ever forwarded based on GAL:=
)).  Hence it would be perfectly valid just to drop such a packet at the fi=
rst S-PE it crosses...
This said, I still  do not think using GAL below the PW label is a good ide=
a either. But this is a different story...

Regards,
     Sasha


--_000_60C093A41B5E45409A19D42CF7786DFD51D5310B6DEUSAACMS0703e_
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.18565" 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: Wingdings;
}
@font-face {
	font-family: Wingdings;
}
@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.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
LI.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
SPAN.EmailStyle18 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe=
rsonal
}
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=3D463521309-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Well&nbsp;one use case is PW interworking between =
MPLS-TP=20
and MPLS domains....MS-PWs over multiple domains</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D463521309-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D463521309-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>The choice is fate sharing with the MPLS path in E=
CMP and=20
not fate sharing with the S-PE implementation&nbsp;OR vice versa....dependi=
ng on=20
GAL above or below</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D463521309-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D463521309-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>"damned if you do...damned if you=20
don't"</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D463521309-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D463521309-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>So as the GAL is really a TP construct and cannot =
be made=20
to work in a useful fashion for the above use case, I think I=20
agree.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D463521309-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D463521309-30032011><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>D</FONT></SPAN></DIV><BR>
<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> Wednesday, March=
 30,=20
2011 10:57 AM<BR><B>To:</B> David Allan I<BR><B>Cc:</B> pwe3; Thomas Nadeau=
;=20
Luca Martini<BR><B>Subject:</B> RE: GAL above and below the PW=20
label<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DWordSection1>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Dave,<o:p></o:p></SPAN>=
</P>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">GAL may be a TP constru=
ct, but,=20
IMO, MS-PWs (if not the other things) will easily break the demarcation lin=
es=20
between TP and non-TP areas.<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">If we stick with GAL be=
ing an=20
MPLS-TP construct we should, IMHO, drop the attempts to use it with=20
Ws.<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">Regards,<o:p></o:p></SP=
AN></P>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">&nbsp;&nbsp;&nbsp;&nbsp=
;=20
Sasha<o:p></o:p></SPAN></P></DIV>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p>&nbsp;</o:p></SPAN=
></P>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium =
none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: blue 1.5pt solid=
; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none">
<DIV>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df=
 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium non=
e; 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'"> David Allan =
I=20
[mailto:david.i.allan@ericsson.com] <BR><B>Sent:</B> Wednesday, March 30, 2=
011=20
10:52 AM<BR><B>To:</B> Alexander Vainshtein; Thomas Nadeau; Luca=20
Martini<BR><B>Cc:</B> pwe3<BR><B>Subject:</B> RE: GAL above and below the P=
W=20
label<o:p></o:p></SPAN></P></DIV></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'">I=
t=20
does&nbsp;become a new behavior, GAL with S=3D0. However the combination of=
 GAL=20
being top label at the S-PE and TTL being encoded in the PW label means tha=
t=20
fate sharing is broken at every S-PE. Life only gets a little more strange =
if=20
there is a FAT label as well...</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'">T=
hat=20
being said, GAL as bottom label is broken in any ECMP environment, which is=
 why=20
GAL is a TP construct.</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'">m=
y 2=20
cents</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: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">D=
</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'"><o:p>&nbs=
p;</o:p></SPAN></P>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><SPAN=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:</SPAN><=
/B><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] <B>On Behalf Of=20
</B>Alexander Vainshtein<BR><B>Sent:</B> Wednesday, March 30, 2011 10:37=20
AM<BR><B>To:</B> Thomas Nadeau; Luca Martini<BR><B>Cc:</B>=20
pwe3<BR><B>Subject:</B> [PWE3] GAL above and below the PW label</SPAN><SPAN=
=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:=
p></SPAN></P>
<P class=3DMsoNormal>Tom, Luca and all,<o:p></o:p></P>
<P class=3DMsoNormal>I would like to clarify &#8211; again &#8211; my posit=
ion regarding GAL=20
above the PW label.<o:p></o:p></P>
<P class=3DMsoNormal>I think that, other issues notwithstanding, it would c=
reate=20
an issue if used with MS-PWs:<o:p></o:p></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -18pt"><SPAN=20
style=3D"FONT-FAMILY: Symbol">&middot;</SPAN><SPAN=20
style=3D"FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>GAL would be exposed at each S-PE (making a presumably end-to-end OA=
M=20
message to be intercepted)<o:p></o:p></P>
<P class=3DMsoListParagraph style=3D"TEXT-INDENT: -18pt"><SPAN=20
style=3D"FONT-FAMILY: Symbol">&middot;</SPAN><SPAN=20
style=3D"FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>What is even worse, there is no rule for forwarding the packet that =
has=20
been intercepted due to an exposed GAL (until you count the statement in 55=
86=20
requesting that a packet MUST NOT be ever forwarded based on GAL<SPAN=20
style=3D"FONT-FAMILY: Wingdings">J</SPAN>).&nbsp; Hence it would be perfect=
ly=20
valid just to drop such a packet at the first S-PE it crosses&#8230;<o:p></=
o:p></P>
<P class=3DMsoNormal>This said, I still&nbsp; do not think using GAL below =
the PW=20
label is a good idea either. But this is a different story&#8230;<o:p></o:p=
></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></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></DIV></BODY></HTML>

--_000_60C093A41B5E45409A19D42CF7786DFD51D5310B6DEUSAACMS0703e_--

From loa@pi.nu  Wed Mar 30 02:18:45 2011
Return-Path: <loa@pi.nu>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 105183A6B3C for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 02:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DmID1OLC8yRr for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 02:18:42 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id 92E9B3A6B41 for <pwe3@ietf.org>; Wed, 30 Mar 2011 02:18:41 -0700 (PDT)
Received: from [130.129.22.69] (dhcp-1645.meeting.ietf.org [130.129.22.69]) (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 A05802A8001 for <pwe3@ietf.org>; Wed, 30 Mar 2011 11:20:19 +0200 (CEST)
Message-ID: <4D92F5D3.6080609@pi.nu>
Date: Wed, 30 Mar 2011 11:20:19 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: pwe3@ietf.org
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 09:18:45 -0000

All,

missed a nuance in Sasha subject line.

We have two issues

- where the GAL is placed relative to the PW label, I  believe it is
   necessary to have the GAL below the PW label.

- whether the the GAL label needs to be bottom of stack or not, it
   figure that this is really a discussion if it is possible to have
   a FAT label below the GAL or not. I'm not sure  about my preferences
   but I think it is possible.

/Loa

On 2011-03-30 10:52, David Allan I wrote:
> It does become a new behavior, GAL with S=0. However the combination of
> GAL being top label at the S-PE and TTL being encoded in the PW label
> means that fate sharing is broken at every S-PE. Life only gets a little
> more strange if there is a FAT label as well...
> That being said, GAL as bottom label is broken in any ECMP environment,
> which is why GAL is a TP construct.
> my 2 cents
> D
>
> ------------------------------------------------------------------------
> *From:* pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] *On Behalf
> Of *Alexander Vainshtein
> *Sent:* Wednesday, March 30, 2011 10:37 AM
> *To:* Thomas Nadeau; Luca Martini
> *Cc:* pwe3
> *Subject:* [PWE3] GAL above and below the PW label
>
> Tom, Luca and all,
>
> I would like to clarify – again – my position regarding GAL above the PW
> label.
>
> I think that, other issues notwithstanding, it would create an issue if
> used with MS-PWs:
>
> ·GAL would be exposed at each S-PE (making a presumably end-to-end OAM
> message to be intercepted)
>
> ·What is even worse, there is no rule for forwarding the packet that has
> been intercepted due to an exposed GAL (until you count the statement in
> 5586 requesting that a packet MUST NOT be ever forwarded based on GALJ).
> Hence it would be perfectly valid just to drop such a packet at the
> first S-PE it crosses…
>
> This said, I still do not think using GAL below the PW label is a good
> idea either. But this is a different story…
>
> Regards,
>
> Sasha
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

-- 


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 Alexander.Vainshtein@ecitele.com  Wed Mar 30 02:28:14 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF30128C124 for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 02:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017,  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 BBgaGc8YcVcW for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 02:28:13 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id 4511B28C0DB for <pwe3@ietf.org>; Wed, 30 Mar 2011 02:28:13 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-b9-4d92f7a80675
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id 25.CE.19639.8A7F29D4; Wed, 30 Mar 2011 11:28:08 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 30 Mar 2011 11:29:27 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Loa Andersson <loa@pi.nu>
Date: Wed, 30 Mar 2011 11:29:20 +0200
Thread-Topic: [PWE3] GAL above and below the PW label
Thread-Index: Acvuu8ApgmFzvCzbQRGIyjw3OuM6EAAAFKxQ
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D072AF@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se> <4D92F5D3.6080609@pi.nu>
In-Reply-To: <4D92F5D3.6080609@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
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 09:28:14 -0000

Loa,
My concerns have been specifically about the GAL ABOVE the PW label as spec=
ified in draft-nadeau.

Having the GAL below the PW label, or Gal above the Fat PW label are not fr=
ee from their own concerns, but these would be quite different concerns:-).

Regards,
     Sasha


> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> Loa Andersson
> Sent: Wednesday, March 30, 2011 11:20 AM
> To: pwe3@ietf.org
> Subject: Re: [PWE3] GAL above and below the PW label
>=20
> All,
>=20
> missed a nuance in Sasha subject line.
>=20
> We have two issues
>=20
> - where the GAL is placed relative to the PW label, I  believe it is
>    necessary to have the GAL below the PW label.
>=20
> - whether the the GAL label needs to be bottom of stack or not, it
>    figure that this is really a discussion if it is possible to have
>    a FAT label below the GAL or not. I'm not sure  about my preferences
>    but I think it is possible.
>=20
> /Loa
>=20
> On 2011-03-30 10:52, David Allan I wrote:
> > It does become a new behavior, GAL with S=3D0. However the combination
> of
> > GAL being top label at the S-PE and TTL being encoded in the PW label
> > means that fate sharing is broken at every S-PE. Life only gets a
> little
> > more strange if there is a FAT label as well...
> > That being said, GAL as bottom label is broken in any ECMP
> environment,
> > which is why GAL is a TP construct.
> > my 2 cents
> > D
> >
> > ---------------------------------------------------------------------
> ---
> > *From:* pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] *On
> Behalf
> > Of *Alexander Vainshtein
> > *Sent:* Wednesday, March 30, 2011 10:37 AM
> > *To:* Thomas Nadeau; Luca Martini
> > *Cc:* pwe3
> > *Subject:* [PWE3] GAL above and below the PW label
> >
> > Tom, Luca and all,
> >
> > I would like to clarify - again - my position regarding GAL above the
> PW
> > label.
> >
> > I think that, other issues notwithstanding, it would create an issue
> if
> > used with MS-PWs:
> >
> > *GAL would be exposed at each S-PE (making a presumably end-to-end
> OAM
> > message to be intercepted)
> >
> > *What is even worse, there is no rule for forwarding the packet that
> has
> > been intercepted due to an exposed GAL (until you count the statement
> in
> > 5586 requesting that a packet MUST NOT be ever forwarded based on
> GALJ).
> > Hence it would be perfectly valid just to drop such a packet at the
> > first S-PE it crosses...
> >
> > This said, I still do not think using GAL below the PW label is a
> good
> > idea either. But this is a different story...
> >
> > Regards,
> >
> > Sasha
> >
> >
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
>=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
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

From gregimirsky@gmail.com  Wed Mar 30 06:54:13 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6FE43A6915 for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 06:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.792
X-Spam-Level: 
X-Spam-Status: No, score=-2.792 tagged_above=-999 required=5 tests=[AWL=-0.194, 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 0AFSxeSZX-DJ for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 06:54:12 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 7232D3A68DB for <pwe3@ietf.org>; Wed, 30 Mar 2011 06:54:12 -0700 (PDT)
Received: by vxg33 with SMTP id 33so1180003vxg.31 for <pwe3@ietf.org>; Wed, 30 Mar 2011 06:55:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=1mncYkotsK63nWULvj0J+v7WWxykpQ23Cua58+H3p2s=; b=tmCmnMxdod+5c6HGmft0FuQX/yxcaxnA0k2icTfmSUu996U23Nf5in7Y314iQAohVV 8zy3ZK5CIMFGRru4ajNj5iFpe0z7CxGz35z514QCJhRKZoHEJnV4djccZxQo8pAqgBaa 05g3cFg4e8k3JBp0OzajJ4QegP+iAP6vsoWIM=
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=wZDFmPK78BWhakvJS10g+rIaNQYRrAE8XRHp56/MFX2BISigsoatWfHf7dX3E0TBmg LaEjH8WyDJ0ph2qhG/8i0VfLbOu+MLFoHtbwWwoeaIdLi+xC7L5S3Sr66lb4rmafcLWo P8yVuwCdF7oPRvVPMUNPNPYIV3Dwoojk6l7z4=
MIME-Version: 1.0
Received: by 10.52.179.138 with SMTP id dg10mr1620190vdc.55.1301493350940; Wed, 30 Mar 2011 06:55:50 -0700 (PDT)
Received: by 10.52.161.198 with HTTP; Wed, 30 Mar 2011 06:55:50 -0700 (PDT)
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D722D07263@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se> <A3C5DF08D38B6049839A6F553B331C76D722D07263@ILPTMAIL02.ecitele.com>
Date: Wed, 30 Mar 2011 06:55:50 -0700
Message-ID: <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Content-Type: multipart/alternative; boundary=bcaec5014c85dc4062049fb388ce
Cc: Luca@core3.amsl.com, Martini <lmartini@cisco.com>, pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 13:54:13 -0000

--bcaec5014c85dc4062049fb388ce
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Dear Sasha,
I believe that there should not be MS-PW that crosses TP and non-TP domains=
.
GAL might be used in each domain under different rules. If we strongly
recommend that rule, then anyone not following it, at his/her free will and
risk, just might be shooting themselves in a foot.

Regards,
Greg

On Wed, Mar 30, 2011 at 1:56 AM, Alexander Vainshtein <
Alexander.Vainshtein@ecitele.com> wrote:

> Dave,
>
> GAL may be a TP construct, but, IMO, MS-PWs (if not the other things) wil=
l
> easily break the demarcation lines between TP and non-TP areas.
>
>
>
> If we stick with GAL being an MPLS-TP construct we should, IMHO, drop the
> attempts to use it with Ws.
>
>
>
> Regards,
>
>      Sasha
>
>
>
> *From:* David Allan I [mailto:david.i.allan@ericsson.com]
> *Sent:* Wednesday, March 30, 2011 10:52 AM
> *To:* Alexander Vainshtein; Thomas Nadeau; Luca Martini
> *Cc:* pwe3
> *Subject:* RE: GAL above and below the PW label
>
>
>
> It does become a new behavior, GAL with S=3D0. However the combination of=
 GAL
> being top label at the S-PE and TTL being encoded in the PW label means t=
hat
> fate sharing is broken at every S-PE. Life only gets a little more strang=
e
> if there is a FAT label as well...
>
>
>
> That being said, GAL as bottom label is broken in any ECMP environment,
> which is why GAL is a TP construct.
>
>
>
> my 2 cents
>
> D
>
>
> ------------------------------
>
> *From:* pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] *On Behalf O=
f
> *Alexander Vainshtein
> *Sent:* Wednesday, March 30, 2011 10:37 AM
> *To:* Thomas Nadeau; Luca Martini
> *Cc:* pwe3
> *Subject:* [PWE3] GAL above and below the PW label
>
> Tom, Luca and all,
>
> I would like to clarify =96 again =96 my position regarding GAL above the=
 PW
> label.
>
> I think that, other issues notwithstanding, it would create an issue if
> used with MS-PWs:
>
> =B7         GAL would be exposed at each S-PE (making a presumably
> end-to-end OAM message to be intercepted)
>
> =B7         What is even worse, there is no rule for forwarding the packe=
t
> that has been intercepted due to an exposed GAL (until you count the
> statement in 5586 requesting that a packet MUST NOT be ever forwarded bas=
ed
> on GALJ).  Hence it would be perfectly valid just to drop such a packet a=
t
> the first S-PE it crosses=85
>
> This said, I still  do not think using GAL below the PW label is a good
> idea either. But this is a different story=85
>
>
>
> Regards,
>
>      Sasha
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>

--bcaec5014c85dc4062049fb388ce
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Dear Sasha,<br>I believe that there should not be MS-PW that crosses TP and=
 non-TP domains. GAL might be used in each domain under different rules. If=
 we strongly recommend that rule, then anyone not following it, at his/her =
free will and risk, just might be shooting themselves in a foot.<br>
<br>Regards,<br>Greg<br><br><div class=3D"gmail_quote">On Wed, Mar 30, 2011=
 at 1:56 AM, Alexander Vainshtein <span dir=3D"ltr">&lt;<a href=3D"mailto:A=
lexander.Vainshtein@ecitele.com">Alexander.Vainshtein@ecitele.com</a>&gt;</=
span> wrote:<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 link=3D"blue=
" vlink=3D"purple" lang=3D"EN-US"><div><p class=3D"MsoNormal"><span style=
=3D"color: rgb(31, 73, 125);">Dave,</span></p>
<p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">GAL may be =
a TP construct, but, IMO, MS-PWs (if not the other things) will easily brea=
k the demarcation lines between TP and non-TP areas.</span></p><p class=3D"=
MsoNormal">
<span style=3D"color: rgb(31, 73, 125);">=A0</span></p><p class=3D"MsoNorma=
l"><span style=3D"color: rgb(31, 73, 125);">If we stick with GAL being an M=
PLS-TP construct we should, IMHO, drop the attempts to use it with Ws.</spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">=A0</span><=
/p><div><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">Reg=
ards,</span></p><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 12=
5);">=A0=A0=A0=A0 Sasha</span></p>
</div><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">=A0</=
span></p><div style=3D"border-width: medium medium medium 1.5pt; border-sty=
le: none none none solid; border-color: -moz-use-text-color -moz-use-text-c=
olor -moz-use-text-color blue; padding: 0cm 0cm 0cm 4pt;">
<div><div style=3D"border-width: 1pt medium medium; border-style: solid non=
e none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-=
color; padding: 3pt 0cm 0cm;"><p class=3D"MsoNormal"><b><span style=3D"font=
-size: 10pt;">From:</span></b><span style=3D"font-size: 10pt;"> David Allan=
 I [mailto:<a href=3D"mailto:david.i.allan@ericsson.com" target=3D"_blank">=
david.i.allan@ericsson.com</a>] <br>
<b>Sent:</b> Wednesday, March 30, 2011 10:52 AM<br><b>To:</b> Alexander Vai=
nshtein; Thomas Nadeau; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> =
RE: GAL above and below the PW label</span></p></div></div><div><div></div>
<div class=3D"h5"><p class=3D"MsoNormal">=A0</p><p class=3D"MsoNormal"><spa=
n style=3D"font-size: 10pt; color: blue;">It does=A0become a new behavior, =
GAL with S=3D0. However the combination of GAL being top label at the S-PE =
and TTL being encoded in the PW label means that fate sharing is broken at =
every S-PE. Life only gets a little more strange if there is a FAT label as=
 well...</span><span style=3D"font-size: 12pt; font-family: &quot;Times New=
 Roman&quot;,&quot;serif&quot;;"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: &quot;T=
imes New Roman&quot;,&quot;serif&quot;;">=A0</span></p><p class=3D"MsoNorma=
l"><span style=3D"font-size: 10pt; color: blue;">That being said, GAL as bo=
ttom label is broken in any ECMP environment, which is why GAL is a TP cons=
truct.</span><span style=3D"font-size: 12pt; font-family: &quot;Times New R=
oman&quot;,&quot;serif&quot;;"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: &quot;T=
imes New Roman&quot;,&quot;serif&quot;;">=A0</span></p><p class=3D"MsoNorma=
l"><span style=3D"font-size: 10pt; color: blue;">my 2 cents</span><span sty=
le=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif=
&quot;;"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;">D</spa=
n><span style=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot;,=
&quot;serif&quot;;"></span></p><p class=3D"MsoNormal"><span style=3D"font-s=
ize: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">=A0=
</span></p>
<div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center"><sp=
an style=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot=
;serif&quot;;"><hr width=3D"100%" align=3D"center" size=3D"2"></span></div>=
<p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;">
<b><span style=3D"font-size: 10pt;">From:</span></b><span style=3D"font-siz=
e: 10pt;"> <a href=3D"mailto:pwe3-bounces@ietf.org" target=3D"_blank">pwe3-=
bounces@ietf.org</a> [mailto:<a href=3D"mailto:pwe3-bounces@ietf.org" targe=
t=3D"_blank">pwe3-bounces@ietf.org</a>] <b>On Behalf Of </b>Alexander Vains=
htein<br>
<b>Sent:</b> Wednesday, March 30, 2011 10:37 AM<br><b>To:</b> Thomas Nadeau=
; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> [PWE3] GAL above and b=
elow the PW label</span><span style=3D"font-size: 12pt; font-family: &quot;=
Times New Roman&quot;,&quot;serif&quot;;"></span></p>
<p class=3D"MsoNormal">Tom, Luca and all,</p><p class=3D"MsoNormal">I would=
 like to clarify =96 again =96 my position regarding GAL above the PW label=
.</p><p class=3D"MsoNormal">I think that, other issues notwithstanding, it =
would create an issue if used with MS-PWs:</p>
<p><span style=3D"font-family: Symbol;">=B7</span><span style=3D"font-size:=
 7pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">=A0=A0=
=A0=A0=A0=A0=A0=A0 </span>GAL would be exposed at each S-PE (making a presu=
mably end-to-end OAM message to be intercepted)</p>
<p><span style=3D"font-family: Symbol;">=B7</span><span style=3D"font-size:=
 7pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">=A0=A0=
=A0=A0=A0=A0=A0=A0 </span>What is even worse, there is no rule for forwardi=
ng the packet that has been intercepted due to an exposed GAL (until you co=
unt the statement in 5586 requesting that a packet MUST NOT be ever forward=
ed based on GAL<span style=3D"font-family: Wingdings;">J</span>).=A0 Hence =
it would be perfectly valid just to drop such a packet at the first S-PE it=
 crosses=85</p>
<p class=3D"MsoNormal">This said, I still=A0 do not think using GAL below t=
he PW label is a good idea either. But this is a different story=85</p><p c=
lass=3D"MsoNormal">=A0</p><p class=3D"MsoNormal">Regards,</p><p class=3D"Ms=
oNormal">=A0=A0=A0=A0 Sasha</p>
<p class=3D"MsoNormal">=A0</p></div></div></div></div></div><br>___________=
____________________________________<br>
pwe3 mailing list<br>
<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/pwe3</a><br>
<br></blockquote></div><br>

--bcaec5014c85dc4062049fb388ce--

From Alexander.Vainshtein@ecitele.com  Wed Mar 30 07:09:13 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20E4F3A6A1D for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 07:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.016,  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 R2liYv5023Hy for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 07:09:07 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id 3D9EF28C18C for <pwe3@ietf.org>; Wed, 30 Mar 2011 07:09:06 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-d3-4d93397db3a4
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id 73.C4.19639.D79339D4; Wed, 30 Mar 2011 16:09:01 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 30 Mar 2011 16:10:39 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 30 Mar 2011 16:10:29 +0200
Thread-Topic: [PWE3] GAL above and below the PW label
Thread-Index: Acvu4jBON5JUq0CZSXK6ST/nRNeR/wAAbl5A
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D073F5@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se> <A3C5DF08D38B6049839A6F553B331C76D722D07263@ILPTMAIL02.ecitele.com> <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@mail.gmail.com>
In-Reply-To: <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@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_A3C5DF08D38B6049839A6F553B331C76D722D073F5ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "Luca@core3.amsl.com" <Luca@core3.amsl.com>, Martini <lmartini@cisco.com>, pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 14:09:13 -0000

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

Dear Greg,
Please see some comments inline below.

Regards,
     Sasha

From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: Wednesday, March 30, 2011 3:56 PM
To: Alexander Vainshtein
Cc: David Allan I; pwe3; Luca@core3.amsl.com; Martini
Subject: Re: [PWE3] GAL above and below the PW label

Dear Sasha,
I believe that there should not be MS-PW that crosses TP and non-TP domains=
.
[[[Sasha]]] I do not see any technical reasons to disallow that.
GAL might be used in each domain under different rules.
[[[Sasha]]] I believe that this would violate the requirement for the commo=
n data plane of MPLS and MPLS-TP.
If we strongly recommend that rule, then anyone not following it, at his/he=
r free will and risk, just might be shooting themselves in a foot.

Regards,
Greg
On Wed, Mar 30, 2011 at 1:56 AM, Alexander Vainshtein <Alexander.Vainshtein=
@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
Dave,
GAL may be a TP construct, but, IMO, MS-PWs (if not the other things) will =
easily break the demarcation lines between TP and non-TP areas.

If we stick with GAL being an MPLS-TP construct we should, IMHO, drop the a=
ttempts to use it with Ws.

Regards,
     Sasha

From: David Allan I [mailto:david.i.allan@ericsson.com<mailto:david.i.allan=
@ericsson.com>]
Sent: Wednesday, March 30, 2011 10:52 AM
To: Alexander Vainshtein; Thomas Nadeau; Luca Martini
Cc: pwe3
Subject: RE: GAL above and below the PW label

It does become a new behavior, GAL with S=3D0. However the combination of G=
AL being top label at the S-PE and TTL being encoded in the PW label means =
that fate sharing is broken at every S-PE. Life only gets a little more str=
ange if there is a FAT label as well...

That being said, GAL as bottom label is broken in any ECMP environment, whi=
ch is why GAL is a TP construct.

my 2 cents
D

________________________________
From: pwe3-bounces@ietf.org<mailto:pwe3-bounces@ietf.org> [mailto:pwe3-boun=
ces@ietf.org<mailto:pwe3-bounces@ietf.org>] On Behalf Of Alexander Vainshte=
in
Sent: Wednesday, March 30, 2011 10:37 AM
To: Thomas Nadeau; Luca Martini
Cc: pwe3
Subject: [PWE3] GAL above and below the PW label
Tom, Luca and all,
I would like to clarify - again - my position regarding GAL above the PW la=
bel.
I think that, other issues notwithstanding, it would create an issue if use=
d with MS-PWs:

*         GAL would be exposed at each S-PE (making a presumably end-to-end=
 OAM message to be intercepted)

*         What is even worse, there is no rule for forwarding the packet th=
at has been intercepted due to an exposed GAL (until you count the statemen=
t in 5586 requesting that a packet MUST NOT be ever forwarded based on GAL:=
)).  Hence it would be perfectly valid just to drop such a packet at the fi=
rst S-PE it crosses...
This said, I still  do not think using GAL below the PW label is a good ide=
a either. But this is a different story...

Regards,
     Sasha


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


--_000_A3C5DF08D38B6049839A6F553B331C76D722D073F5ILPTMAIL02eci_
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-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator 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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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: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;}
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.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Dear Greg=
,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'>Please see some comments=
 inline below.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-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'>Regards,<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o:p></o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'=
border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><d=
iv style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0c=
m 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"'> Greg Mirsky [mailto:gregimirsky@gmail.com] =
<br><b>Sent:</b> Wednesday, March 30, 2011 3:56 PM<br><b>To:</b> Alexander =
Vainshtein<br><b>Cc:</b> David Allan I; pwe3; Luca@core3.amsl.com; Martini<=
br><b>Subject:</b> Re: [PWE3] GAL above and below the PW label<o:p></o:p></=
span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DM=
soNormal style=3D'margin-bottom:12.0pt'>Dear Sasha,<br>I believe that there=
 should not be MS-PW that crosses TP and non-TP domains.<span style=3D'colo=
r:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-botto=
m:12.0pt'><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>[[[Sasha]]] I do not see any technical reasons to di=
sallow that.<o:p></o:p></span></i></b></p><p class=3DMsoNormal style=3D'mar=
gin-bottom:12.0pt'> GAL might be used in each domain under different rules.=
 <span style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal s=
tyle=3D'margin-bottom:12.0pt'><b><i><span style=3D'font-size:11.0pt;font-fa=
mily:"Calibri","sans-serif";color:#1F497D'>[[[Sasha]]] I believe that this =
would violate the requirement for the common data plane of MPLS and MPLS-TP=
.<o:p></o:p></span></i></b></p><p class=3DMsoNormal style=3D'margin-bottom:=
12.0pt'>If we strongly recommend that rule, then anyone not following it, a=
t his/her free will and risk, just might be shooting themselves in a foot.<=
br><br>Regards,<br>Greg<o:p></o:p></p><div><p class=3DMsoNormal>On Wed, Mar=
 30, 2011 at 1:56 AM, Alexander Vainshtein &lt;<a href=3D"mailto:Alexander.=
Vainshtein@ecitele.com">Alexander.Vainshtein@ecitele.com</a>&gt; wrote:<o:p=
></o:p></p><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;=
mso-margin-bottom-alt:auto'><span style=3D'color:#1F497D'>Dave,</span><o:p>=
</o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-=
bottom-alt:auto'><span style=3D'color:#1F497D'>GAL may be a TP construct, b=
ut, IMO, MS-PWs (if not the other things) will easily break the demarcation=
 lines between TP and non-TP areas.</span><o:p></o:p></p><p class=3DMsoNorm=
al style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=
=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'colo=
r:#1F497D'>If we stick with GAL being an MPLS-TP construct we should, IMHO,=
 drop the attempts to use it with Ws.</span><o:p></o:p></p><p class=3DMsoNo=
rmal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span sty=
le=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D=
'color:#1F497D'>Regards,</span><o:p></o:p></p><p class=3DMsoNormal style=3D=
'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'color:#=
1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</span><o:p></o:p></p></div><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><=
span style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div style=3D'bord=
er:none;border-left:solid windowtext 1.5pt;padding:0cm 0cm 0cm 4.0pt;border=
-color:-moz-use-text-color -moz-use-text-color -moz-use-text-color blue'><d=
iv><div style=3D'border:none;border-top:solid windowtext 1.0pt;padding:3.0p=
t 0cm 0cm 0cm;border-color:-moz-use-text-color -moz-use-text-color'><p clas=
s=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>=
<b><span style=3D'font-size:10.0pt'>From:</span></b><span style=3D'font-siz=
e:10.0pt'> David Allan I [mailto:<a href=3D"mailto:david.i.allan@ericsson.c=
om" target=3D"_blank">david.i.allan@ericsson.com</a>] <br><b>Sent:</b> Wedn=
esday, March 30, 2011 10:52 AM<br><b>To:</b> Alexander Vainshtein; Thomas N=
adeau; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> RE: GAL above and=
 below the PW label</span><o:p></o:p></p></div></div><div><div><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp=
;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto'><span style=3D'font-size:10.0pt;color:blue'>It does&=
nbsp;become a new behavior, GAL with S=3D0. However the combination of GAL =
being top label at the S-PE and TTL being encoded in the PW label means tha=
t fate sharing is broken at every S-PE. Life only gets a little more strang=
e if there is a FAT label as well...</span><o:p></o:p></p><p class=3DMsoNor=
mal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p=
></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin=
-bottom-alt:auto'><span style=3D'font-size:10.0pt;color:blue'>That being sa=
id, GAL as bottom label is broken in any ECMP environment, which is why GAL=
 is a TP construct.</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-=
margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><p cla=
ss=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'=
><span style=3D'font-size:10.0pt;color:blue'>my 2 cents</span><o:p></o:p></=
p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto'><span style=3D'font-size:10.0pt;color:blue'>D</span><o:p></o:p></p=
><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto'>&nbsp;<o:p></o:p></p><div class=3DMsoNormal align=3Dcenter style=3D=
'text-align:center'><hr size=3D2 width=3D"100%" align=3Dcenter></div><p cla=
ss=3DMsoNormal style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><b><s=
pan style=3D'font-size:10.0pt'>From:</span></b><span style=3D'font-size:10.=
0pt'> <a href=3D"mailto:pwe3-bounces@ietf.org" target=3D"_blank">pwe3-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:pwe3-bounces@ietf.org" target=3D"=
_blank">pwe3-bounces@ietf.org</a>] <b>On Behalf Of </b>Alexander Vainshtein=
<br><b>Sent:</b> Wednesday, March 30, 2011 10:37 AM<br><b>To:</b> Thomas Na=
deau; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> [PWE3] GAL above a=
nd below the PW label</span><o:p></o:p></p><p class=3DMsoNormal style=3D'ms=
o-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Tom, Luca and all,<o:p></=
o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto'>I would like to clarify &#8211; again &#8211; my position re=
garding GAL above the PW label.<o:p></o:p></p><p class=3DMsoNormal style=3D=
'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I think that, other is=
sues notwithstanding, it would create an issue if used with MS-PWs:<o:p></o=
:p></p><p><span style=3D'font-family:Symbol'>&middot;</span><span style=3D'=
font-size:7.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>GA=
L would be exposed at each S-PE (making a presumably end-to-end OAM message=
 to be intercepted)<o:p></o:p></p><p><span style=3D'font-family:Symbol'>&mi=
ddot;</span><span style=3D'font-size:7.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; </span>What is even worse, there is no rule for forwardin=
g the packet that has been intercepted due to an exposed GAL (until you cou=
nt the statement in 5586 requesting that a packet MUST NOT be ever forwarde=
d based on GAL<span style=3D'font-family:Wingdings'>J</span>).&nbsp; Hence =
it would be perfectly valid just to drop such a packet at the first S-PE it=
 crosses&#8230;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-=
alt:auto;mso-margin-bottom-alt:auto'>This said, I still&nbsp; do not think =
using GAL below the PW label is a good idea either. But this is a different=
 story&#8230;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-al=
t:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><p class=3DMsoNorma=
l style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards,<o:p=
></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin=
-bottom-alt:auto'>&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o:p></o:p></p><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp=
;<o:p></o:p></p></div></div></div></div></div><p class=3DMsoNormal style=3D=
'margin-bottom:12.0pt'><br>_______________________________________________<=
br>pwe3 mailing list<br><a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><=
br><a href=3D"https://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/pwe3</a><o:p></o:p></p></div><p clas=
s=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>=

--_000_A3C5DF08D38B6049839A6F553B331C76D722D073F5ILPTMAIL02eci_--

From Alexander.Vainshtein@ecitele.com  Wed Mar 30 07:25:14 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 363033A67FC for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 07:25:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.016,  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 LMJgcOIFMPU2 for <pwe3@core3.amsl.com>; Wed, 30 Mar 2011 07:25:10 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id 29D1D3A6936 for <pwe3@ietf.org>; Wed, 30 Mar 2011 07:25:08 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-89-4d933d414b5c
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id A7.25.19639.14D339D4; Wed, 30 Mar 2011 16:25:05 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 30 Mar 2011 16:26:42 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
Date: Wed, 30 Mar 2011 16:26:34 +0200
Thread-Topic: PW/VCCV Implementation Survey Results Draft Posted...
Thread-Index: Acvt6w0cljxMk3KoRvm0e9JP7sJJUQA+d0aA
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D07407@ILPTMAIL02.ecitele.com>
References: <14584D6EE26B314187A4F68BA206060006FE2275@ASHEVS008.mcilink.com>
In-Reply-To: <14584D6EE26B314187A4F68BA206060006FE2275@ASHEVS008.mcilink.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_A3C5DF08D38B6049839A6F553B331C76D722D07407ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] PW/VCCV Implementation Survey Results Draft Posted...
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 14:25:14 -0000

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

Nick,
Lots of thanks for posting the version of the draft with the complete surve=
y results.
I have to admit that these results have changed, to some extent, my underst=
anding of the overall picture.

E.g., it was good to know that bore than 90K of Ethernet Raw Mode PWs have =
been deployed; but it is even more interesting to know that 50K out of the =
total have been deployed by a single respondent (#12).

Regards,
     Sasha

From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Del=
regno, Christopher N (Nick DelRegno)
Sent: Tuesday, March 29, 2011 10:34 AM
To: pwe3@ietf.org
Subject: [PWE3] PW/VCCV Implementation Survey Results Draft Posted...

All:

I have uploaded the draft with the complete survey results.  In my haste to=
 post the original draft before the deadline, and attempting to resolve som=
e IDNITS, I goofed on the draft name.  I have incorporated list comments on=
 the original draft as well as added the Appendix which contains the verbat=
im (except for User/Vendor name scrub) responses.

The draft can be found here: http://www.ietf.org/id/draft-delregno-pwe3-pw-=
vccv-impl-survey-results

Thanks again to all who provided the valuable data contained therein.

Regards,
Nick

Christopher N. "Nick" Del Regno, PMTS
Verizon, CTO, Ethernet Technology & Transport
400 International Pkwy, 2C107
Richardson, TX  75081
972-729-3411
nick.delregno@verizon.com


--_000_A3C5DF08D38B6049839A6F553B331C76D722D07407ILPTMAIL02eci_
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-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator 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: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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Nick,<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>Lots of thanks for posting the version of the draft with=
 the complete survey results.<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'color:#1F497D'>I have to admit that these results have changed,=
 to some extent, my understanding of the overall picture.<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>E.g., it was goo=
d to know that bore than 90K of Ethernet Raw Mode PWs have been deployed; b=
ut it is even more interesting to know that 50K out of the total have been =
deployed by a single respondent (#12).<o:p></o:p></span></p><p class=3DMsoN=
ormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><p cla=
ss=3DMsoNormal><span style=3D'color:#1F497D'>Regards,<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 style=3D'border:none;border-left=
:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none=
;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNo=
rmal><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"'> pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] <b>On Behalf =
Of </b>Delregno, Christopher N (Nick DelRegno)<br><b>Sent:</b> Tuesday, Mar=
ch 29, 2011 10:34 AM<br><b>To:</b> pwe3@ietf.org<br><b>Subject:</b> [PWE3] =
PW/VCCV Implementation Survey Results Draft Posted...<o:p></o:p></span></p>=
</div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>=
All:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMso=
Normal>I have uploaded the draft with the complete survey results.&nbsp; In=
 my haste to post the original draft before the deadline, and attempting to=
 resolve some IDNITS, I goofed on the draft name.&nbsp; I have incorporated=
 list comments on the original draft as well as added the Appendix which co=
ntains the verbatim (except for User/Vendor name scrub) responses. <o:p></o=
:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The d=
raft can be found here: <a href=3D"http://www.ietf.org/id/draft-delregno-pw=
e3-pw-vccv-impl-survey-results"><span style=3D'color:#1F497D'>http://www.ie=
tf.org/id/draft-delregno-pwe3-pw-vccv-impl-survey-results</span></a><o:p></=
o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Than=
ks again to all who provided the valuable data contained therein.<o:p></o:p=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Regards=
,<o:p></o:p></p><p class=3DMsoNormal>Nick<o:p></o:p></p><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Christopher N. &#8220;Nick&#822=
1; Del Regno, PMTS<o:p></o:p></p><p class=3DMsoNormal>Verizon, CTO, Etherne=
t Technology &amp; Transport<o:p></o:p></p><p class=3DMsoNormal>400 Interna=
tional Pkwy, 2C107<o:p></o:p></p><p class=3DMsoNormal>Richardson, TX&nbsp; =
75081<o:p></o:p></p><p class=3DMsoNormal>972-729-3411<o:p></o:p></p><p clas=
s=3DMsoNormal>nick.delregno@verizon.com<o:p></o:p></p><p class=3DMsoNormal>=
<o:p>&nbsp;</o:p></p></div></div></body></html>=

--_000_A3C5DF08D38B6049839A6F553B331C76D722D07407ILPTMAIL02eci_--

From curtis@occnc.com  Thu Mar 31 00:01:40 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAB013A6AFA for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 00:01:40 -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 qvQscwXZiBJL for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 00:01:39 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id A252F3A680E for <pwe3@ietf.org>; Thu, 31 Mar 2011 00:01:39 -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 p2V73Hrx045107; Thu, 31 Mar 2011 03:03:17 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103310703.p2V73Hrx045107@harbor.orleans.occnc.com>
To: Loa Andersson <loa@pi.nu>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Wed, 30 Mar 2011 11:20:19 +0200." <4D92F5D3.6080609@pi.nu> 
Date: Thu, 31 Mar 2011 03:03:17 -0400
Sender: curtis@occnc.com
Cc: pwe3@ietf.org
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 07:01:40 -0000

Loa, Dave, Sasha,

I've snipped from various posts on the thread that Sasha started.  See
inline.

In message <4D92F5D3.6080609@pi.nu>
Loa Andersson writes:
>  
> All,
>  
> missed a nuance in Sasha subject line.
>  
> We have two issues
>  
> - where the GAL is placed relative to the PW label, I  believe it is
>    necessary to have the GAL below the PW label.
>  
> - whether the the GAL label needs to be bottom of stack or not, it
>    figure that this is really a discussion if it is possible to have
>    a FAT label below the GAL or not. I'm not sure  about my preferences
>    but I think it is possible.
>  
> /Loa

I agree with Loa's summary.  Not putting GAL at the bottom may confuse
some LSR, but putting it above the PW label is likely to be even more
problematic.


In message <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se>
David Allan I writes:
>  
> It does become a new behavior, GAL with S=3D0. However the combination of G=
> AL being top label at the S-PE and TTL being encoded in the PW label means =
> that fate sharing is broken at every S-PE. Life only gets a little more str=
> ange if there is a FAT label as well...
>  
> That being said, GAL as bottom label is broken in any ECMP environment, whi=
> ch is why GAL is a TP construct.
>  
> my 2 cents
> D

Dave,

If GAL is broken for ECMP, which it is, then all TP OAM is broken.
If all it takes to fix it is simple then lets just fix it.

This is what we'd have to do.

  1) Relax the requirement that GAL be at the bottom

  2) Have the ingress insert GAL in the stack immediately below the
     label for which the measurement is made, keeping the rest of the
     label stack in place.

The only thing the midpoing LSR at a multipath (LAG, link bundle for
MPLS) has to do is skip over the GAL when hashing, as if the GAL
wasn't there.  That will yield the same hash value and it will
preserve fate-sharing across multipath.

I prefer that we fix things rather than complain that they are broken.

Curtis

From david.i.allan@ericsson.com  Thu Mar 31 00:22:21 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96B7C28C223 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 00:22:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.277
X-Spam-Level: 
X-Spam-Status: No, score=-5.277 tagged_above=-999 required=5 tests=[AWL=1.322,  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 don2kGA0YNPW for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 00:22:20 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 7061F28C226 for <pwe3@ietf.org>; Thu, 31 Mar 2011 00:22:20 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2V7NwsZ015246; Thu, 31 Mar 2011 02:23:59 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.203]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Thu, 31 Mar 2011 03:23:53 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "curtis@occnc.com" <curtis@occnc.com>, Loa Andersson <loa@pi.nu>
Date: Thu, 31 Mar 2011 03:23:51 -0400
Thread-Topic: [PWE3] GAL above and below the PW label
Thread-Index: AcvvcbsWZMtufsxuQleqGANEtzAjuQAAoutg
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51D531132B@EUSAACMS0703.eamcs.ericsson.se>
References: Your message of "Wed, 30 Mar 2011 11:20:19 +0200." <4D92F5D3.6080609@pi.nu> <201103310703.p2V73Hrx045107@harbor.orleans.occnc.com>
In-Reply-To: <201103310703.p2V73Hrx045107@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: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 07:22:21 -0000

HI Curtis:

My suggestion is to avoid the GAL for PWs if it is to be a homogenizing age=
nt across TP and IP/MPLS domains in the form of MS-PWs. The scenarios in wh=
ich it was broken was simply a statement of fact.

As for the problem GAL was proposed to fix (lack of CW), there are solution=
s on the table, just not palatable...

D

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Cur=
tis Villamizar
Sent: Thursday, March 31, 2011 9:03 AM
To: Loa Andersson
Cc: pwe3@ietf.org
Subject: Re: [PWE3] GAL above and below the PW label


Loa, Dave, Sasha,

I've snipped from various posts on the thread that Sasha started.  See inli=
ne.

In message <4D92F5D3.6080609@pi.nu>
Loa Andersson writes:
> =20
> All,
> =20
> missed a nuance in Sasha subject line.
> =20
> We have two issues
> =20
> - where the GAL is placed relative to the PW label, I  believe it is
>    necessary to have the GAL below the PW label.
> =20
> - whether the the GAL label needs to be bottom of stack or not, it
>    figure that this is really a discussion if it is possible to have
>    a FAT label below the GAL or not. I'm not sure  about my preferences
>    but I think it is possible.
> =20
> /Loa

I agree with Loa's summary.  Not putting GAL at the bottom may confuse some=
 LSR, but putting it above the PW label is likely to be even more problemat=
ic.


In message <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.e=
ricsson.se>
David Allan I writes:
> =20
> It does become a new behavior, GAL with S=3D3D0. However the combination=
=20
> of G=3D AL being top label at the S-PE and TTL being encoded in the PW=20
> label means =3D that fate sharing is broken at every S-PE. Life only=20
> gets a little more str=3D ange if there is a FAT label as well...
> =20
> That being said, GAL as bottom label is broken in any ECMP=20
> environment, whi=3D ch is why GAL is a TP construct.
> =20
> my 2 cents
> D

Dave,

If GAL is broken for ECMP, which it is, then all TP OAM is broken.
If all it takes to fix it is simple then lets just fix it.

This is what we'd have to do.

  1) Relax the requirement that GAL be at the bottom

  2) Have the ingress insert GAL in the stack immediately below the
     label for which the measurement is made, keeping the rest of the
     label stack in place.

The only thing the midpoing LSR at a multipath (LAG, link bundle for
MPLS) has to do is skip over the GAL when hashing, as if the GAL wasn't the=
re.  That will yield the same hash value and it will preserve fate-sharing =
across multipath.

I prefer that we fix things rather than complain that they are broken.

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

From gregimirsky@gmail.com  Thu Mar 31 00:31:25 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B1ED28C212 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 00:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.273
X-Spam-Level: 
X-Spam-Status: No, score=-3.273 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 XwCAAXOm4ERO for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 00:31:24 -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 B62FA28C1FD for <pwe3@ietf.org>; Thu, 31 Mar 2011 00:31:23 -0700 (PDT)
Received: by vws12 with SMTP id 12so1905004vws.31 for <pwe3@ietf.org>; Thu, 31 Mar 2011 00:33:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7LxUiQywiiRPNZe7+j+DWO2bXeuBQeJiOpeO3LVrBZ4=; b=DRBFLse6hCXbdhB+3bLegwl+lEKr9LTi6BNYt5NR4YRSAaJe7qwpE0dzJ6mz4aGKZx TBQI7u/VqJZzdIGmUTgKXqhY+CpOpqkDtTYy8b/48LIVHchFacEkVJwAIieuTbBkxKyK p9VDjQEkQ/QdSfykzf/gMhaOFH+4mNADGuRPU=
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=fBC0ujmpBBGvrstoXEe8mn9aQ0vvX5ep+XrX5M8c58b+V7qR7jlJrxGwO8kA8/usW9 d3SaYkG6jxwr1T1jr6m0v7t1bAnD0EkeNgdu9H+Junus3l1tpclpeEIsADWuR4Ab7D6B QhuqJx1xoPFILdsee2iyE1CYC8G5YNLkliAb8=
MIME-Version: 1.0
Received: by 10.52.159.70 with SMTP id xa6mr3013824vdb.135.1301556782670; Thu, 31 Mar 2011 00:33:02 -0700 (PDT)
Received: by 10.52.161.198 with HTTP; Thu, 31 Mar 2011 00:33:02 -0700 (PDT)
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D722D073F5@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se> <A3C5DF08D38B6049839A6F553B331C76D722D07263@ILPTMAIL02.ecitele.com> <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D722D073F5@ILPTMAIL02.ecitele.com>
Date: Thu, 31 Mar 2011 00:33:02 -0700
Message-ID: <AANLkTi=VQQdXL-avxbK0_R9EssbzWdQP-Fmh8Nyhvqq4@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Content-Type: multipart/alternative; boundary=bcaec53f9787afa3c8049fc24dd9
Cc: Martini <lmartini@cisco.com>, pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 07:31:25 -0000

--bcaec53f9787afa3c8049fc24dd9
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Dear Sasha,
would your argument illustrate that use of GAL with PW label not only in
MPLS-TP but in non-TP MPLS PW is strongly problematic? Should we leave RFC
5586 as is?

Regards,
Greg

On Wed, Mar 30, 2011 at 7:10 AM, Alexander Vainshtein <
Alexander.Vainshtein@ecitele.com> wrote:

> Dear Greg,
>
> Please see some comments inline below.
>
>
>
> Regards,
>
>      Sasha
>
>
>
> *From:* Greg Mirsky [mailto:gregimirsky@gmail.com]
> *Sent:* Wednesday, March 30, 2011 3:56 PM
> *To:* Alexander Vainshtein
> *Cc:* David Allan I; pwe3; Luca@core3.amsl.com; Martini
> *Subject:* Re: [PWE3] GAL above and below the PW label
>
>
>
> Dear Sasha,
> I believe that there should not be MS-PW that crosses TP and non-TP
> domains.
>
> *[[[Sasha]]] I do not see any technical reasons to disallow that.*
>
> GAL might be used in each domain under different rules.
>
> *[[[Sasha]]] I believe that this would violate the requirement for the
> common data plane of MPLS and MPLS-TP.*
>
> If we strongly recommend that rule, then anyone not following it, at
> his/her free will and risk, just might be shooting themselves in a foot.
>
> Regards,
> Greg
>
> On Wed, Mar 30, 2011 at 1:56 AM, Alexander Vainshtein <
> Alexander.Vainshtein@ecitele.com> wrote:
>
> Dave,
>
> GAL may be a TP construct, but, IMO, MS-PWs (if not the other things) wil=
l
> easily break the demarcation lines between TP and non-TP areas.
>
>
>
> If we stick with GAL being an MPLS-TP construct we should, IMHO, drop the
> attempts to use it with Ws.
>
>
>
> Regards,
>
>      Sasha
>
>
>
> *From:* David Allan I [mailto:david.i.allan@ericsson.com]
> *Sent:* Wednesday, March 30, 2011 10:52 AM
> *To:* Alexander Vainshtein; Thomas Nadeau; Luca Martini
> *Cc:* pwe3
> *Subject:* RE: GAL above and below the PW label
>
>
>
> It does become a new behavior, GAL with S=3D0. However the combination of=
 GAL
> being top label at the S-PE and TTL being encoded in the PW label means t=
hat
> fate sharing is broken at every S-PE. Life only gets a little more strang=
e
> if there is a FAT label as well...
>
>
>
> That being said, GAL as bottom label is broken in any ECMP environment,
> which is why GAL is a TP construct.
>
>
>
> my 2 cents
>
> D
>
>
> ------------------------------
>
> *From:* pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] *On Behalf O=
f
> *Alexander Vainshtein
> *Sent:* Wednesday, March 30, 2011 10:37 AM
> *To:* Thomas Nadeau; Luca Martini
> *Cc:* pwe3
> *Subject:* [PWE3] GAL above and below the PW label
>
> Tom, Luca and all,
>
> I would like to clarify =96 again =96 my position regarding GAL above the=
 PW
> label.
>
> I think that, other issues notwithstanding, it would create an issue if
> used with MS-PWs:
>
> =B7         GAL would be exposed at each S-PE (making a presumably
> end-to-end OAM message to be intercepted)
>
> =B7         What is even worse, there is no rule for forwarding the packe=
t
> that has been intercepted due to an exposed GAL (until you count the
> statement in 5586 requesting that a packet MUST NOT be ever forwarded bas=
ed
> on GALJ).  Hence it would be perfectly valid just to drop such a packet a=
t
> the first S-PE it crosses=85
>
> This said, I still  do not think using GAL below the PW label is a good
> idea either. But this is a different story=85
>
>
>
> Regards,
>
>      Sasha
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>
>

--bcaec53f9787afa3c8049fc24dd9
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Dear Sasha,<br>would your argument illustrate that use of GAL with PW label=
 not only in MPLS-TP but in non-TP MPLS PW is strongly problematic? Should =
we leave RFC 5586 as is?<br><br>Regards,<br>Greg<br><br><div class=3D"gmail=
_quote">
On Wed, Mar 30, 2011 at 7:10 AM, Alexander Vainshtein <span dir=3D"ltr">&lt=
;<a href=3D"mailto:Alexander.Vainshtein@ecitele.com" target=3D"_blank">Alex=
ander.Vainshtein@ecitele.com</a>&gt;</span> wrote:<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 link=3D"blue=
" vlink=3D"purple" lang=3D"EN-US"><div><p class=3D"MsoNormal"><span style=
=3D"font-size: 11pt; color: rgb(31, 73, 125);">Dear Greg,</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">Please see some comments inline below.</span></p><p class=3D"MsoNorma=
l"><span style=3D"font-size: 11pt; color: rgb(31, 73, 125);">=A0</span></p>=
<p class=3D"MsoNormal">

<span style=3D"font-size: 11pt; color: rgb(31, 73, 125);">Regards,</span></=
p><p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73,=
 125);">=A0=A0=A0=A0 Sasha</span></p><p class=3D"MsoNormal"><span style=3D"=
font-size: 11pt; color: rgb(31, 73, 125);">=A0</span></p>

<div style=3D"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: 0cm 0cm 0cm 4pt;"><div><div style=3D"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 0cm 0c=
m;">

<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt;">From:</span></b>=
<span style=3D"font-size: 10pt;"> Greg Mirsky [mailto:<a href=3D"mailto:gre=
gimirsky@gmail.com" target=3D"_blank">gregimirsky@gmail.com</a>] <br><b>Sen=
t:</b> Wednesday, March 30, 2011 3:56 PM<br>

<b>To:</b> Alexander Vainshtein<br><b>Cc:</b> David Allan I; pwe3; <a href=
=3D"mailto:Luca@core3.amsl.com" target=3D"_blank">Luca@core3.amsl.com</a>; =
Martini<br><b>Subject:</b> Re: [PWE3] GAL above and below the PW label</spa=
n></p>

</div></div><div><p class=3D"MsoNormal">=A0</p><p class=3D"MsoNormal" style=
=3D"margin-bottom: 12pt;">Dear Sasha,<br>I believe that there should not be=
 MS-PW that crosses TP and non-TP domains.<span style=3D"color: rgb(31, 73,=
 125);"></span></p>

</div><p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;"><b><i><span sty=
le=3D"font-size: 11pt; color: rgb(31, 73, 125);">[[[Sasha]]] I do not see a=
ny technical reasons to disallow that.</span></i></b></p><div><p class=3D"M=
soNormal" style=3D"margin-bottom: 12pt;">

 GAL might be used in each domain under different rules. <span style=3D"col=
or: rgb(31, 73, 125);"></span></p></div><p class=3D"MsoNormal" style=3D"mar=
gin-bottom: 12pt;"><b><i><span style=3D"font-size: 11pt; color: rgb(31, 73,=
 125);">[[[Sasha]]] I believe that this would violate the requirement for t=
he common data plane of MPLS and MPLS-TP.</span></i></b></p>

<div><div></div><div><p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;">=
If we strongly recommend that rule, then anyone not following it, at his/he=
r free will and risk, just might be shooting themselves in a foot.<br>
<br>Regards,<br>Greg</p><div><p class=3D"MsoNormal">On Wed, Mar 30, 2011 at=
 1:56 AM, Alexander Vainshtein &lt;<a href=3D"mailto:Alexander.Vainshtein@e=
citele.com" target=3D"_blank">Alexander.Vainshtein@ecitele.com</a>&gt; wrot=
e:</p>

<div><div><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">D=
ave,</span></p><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125=
);">GAL may be a TP construct, but, IMO, MS-PWs (if not the other things) w=
ill easily break the demarcation lines between TP and non-TP areas.</span><=
/p>

<p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">=A0</span><=
/p><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">If we st=
ick with GAL being an MPLS-TP construct we should, IMHO, drop the attempts =
to use it with Ws.</span></p>

<p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">=A0</span><=
/p><div><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">Reg=
ards,</span></p><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 12=
5);">=A0=A0=A0=A0 Sasha</span></p>

</div><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">=A0</=
span></p><div style=3D"border-width: medium medium medium 1.5pt; border-sty=
le: none none none solid; padding: 0cm 0cm 0cm 4pt; border-color: -moz-use-=
text-color -moz-use-text-color -moz-use-text-color blue;">

<div><div style=3D"border-width: 1pt medium medium; border-style: solid non=
e none; padding: 3pt 0cm 0cm; border-color: -moz-use-text-color;"><p class=
=3D"MsoNormal"><b><span style=3D"font-size: 10pt;">From:</span></b><span st=
yle=3D"font-size: 10pt;"> David Allan I [mailto:<a href=3D"mailto:david.i.a=
llan@ericsson.com" target=3D"_blank">david.i.allan@ericsson.com</a>] <br>

<b>Sent:</b> Wednesday, March 30, 2011 10:52 AM<br><b>To:</b> Alexander Vai=
nshtein; Thomas Nadeau; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> =
RE: GAL above and below the PW label</span></p></div></div><div><div><p cla=
ss=3D"MsoNormal">

=A0</p><p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;"=
>It does=A0become a new behavior, GAL with S=3D0. However the combination o=
f GAL being top label at the S-PE and TTL being encoded in the PW label mea=
ns that fate sharing is broken at every S-PE. Life only gets a little more =
strange if there is a FAT label as well...</span></p>

<p class=3D"MsoNormal">=A0</p><p class=3D"MsoNormal"><span style=3D"font-si=
ze: 10pt; color: blue;">That being said, GAL as bottom label is broken in a=
ny ECMP environment, which is why GAL is a TP construct.</span></p><p class=
=3D"MsoNormal">

=A0</p><p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;"=
>my 2 cents</span></p><p class=3D"MsoNormal"><span style=3D"font-size: 10pt=
; color: blue;">D</span></p><p class=3D"MsoNormal">=A0</p><div class=3D"Mso=
Normal" style=3D"text-align: center;" align=3D"center">

<hr width=3D"100%" align=3D"center" size=3D"2"></div><p class=3D"MsoNormal"=
 style=3D"margin-bottom: 12pt;"><b><span style=3D"font-size: 10pt;">From:</=
span></b><span style=3D"font-size: 10pt;"> <a href=3D"mailto:pwe3-bounces@i=
etf.org" target=3D"_blank">pwe3-bounces@ietf.org</a> [mailto:<a href=3D"mai=
lto:pwe3-bounces@ietf.org" target=3D"_blank">pwe3-bounces@ietf.org</a>] <b>=
On Behalf Of </b>Alexander Vainshtein<br>

<b>Sent:</b> Wednesday, March 30, 2011 10:37 AM<br><b>To:</b> Thomas Nadeau=
; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> [PWE3] GAL above and b=
elow the PW label</span></p><p class=3D"MsoNormal">Tom, Luca and all,</p>

<p class=3D"MsoNormal">I would like to clarify =96 again =96 my position re=
garding GAL above the PW label.</p><p class=3D"MsoNormal">I think that, oth=
er issues notwithstanding, it would create an issue if used with MS-PWs:</p=
><p>

<span style=3D"font-family: Symbol;">=B7</span><span style=3D"font-size: 7p=
t;">=A0=A0=A0=A0=A0=A0=A0=A0 </span>GAL would be exposed at each S-PE (maki=
ng a presumably end-to-end OAM message to be intercepted)</p><p><span style=
=3D"font-family: Symbol;">=B7</span><span style=3D"font-size: 7pt;">=A0=A0=
=A0=A0=A0=A0=A0=A0 </span>What is even worse, there is no rule for forwardi=
ng the packet that has been intercepted due to an exposed GAL (until you co=
unt the statement in 5586 requesting that a packet MUST NOT be ever forward=
ed based on GAL<span style=3D"font-family: Wingdings;">J</span>).=A0 Hence =
it would be perfectly valid just to drop such a packet at the first S-PE it=
 crosses=85</p>

<p class=3D"MsoNormal">This said, I still=A0 do not think using GAL below t=
he PW label is a good idea either. But this is a different story=85</p><p c=
lass=3D"MsoNormal">=A0</p><p class=3D"MsoNormal">Regards,</p><p class=3D"Ms=
oNormal">
=A0=A0=A0=A0 Sasha</p>
<p class=3D"MsoNormal">=A0</p></div></div></div></div></div><p class=3D"Mso=
Normal" style=3D"margin-bottom: 12pt;"><br>________________________________=
_______________<br>pwe3 mailing list<br><a href=3D"mailto:pwe3@ietf.org" ta=
rget=3D"_blank">pwe3@ietf.org</a><br>

<a href=3D"https://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/pwe3</a></p></div><p class=3D"MsoNormal=
">=A0</p></div></div></div></div></div></blockquote></div><br>

--bcaec53f9787afa3c8049fc24dd9--

From Alexander.Vainshtein@ecitele.com  Thu Mar 31 00:33:37 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B0B43A699D for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 00:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level: 
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.015,  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 hPJzhMai6SUu for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 00:33:30 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id 89C613A6850 for <pwe3@ietf.org>; Thu, 31 Mar 2011 00:33:29 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-ad-4d942e45e273
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id D6.CD.19639.54E249D4; Thu, 31 Mar 2011 09:33:25 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Thu, 31 Mar 2011 09:35:07 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 31 Mar 2011 09:34:57 +0200
Thread-Topic: [PWE3] GAL above and below the PW label
Thread-Index: Acvvdd+TZQga6p7QRrepa3RsWIBWRgAAA8yw
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D07531@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se> <A3C5DF08D38B6049839A6F553B331C76D722D07263@ILPTMAIL02.ecitele.com> <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D722D073F5@ILPTMAIL02.ecitele.com> <AANLkTi=VQQdXL-avxbK0_R9EssbzWdQP-Fmh8Nyhvqq4@mail.gmail.com>
In-Reply-To: <AANLkTi=VQQdXL-avxbK0_R9EssbzWdQP-Fmh8Nyhvqq4@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_A3C5DF08D38B6049839A6F553B331C76D722D07531ILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: Martini <lmartini@cisco.com>, pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 07:33:37 -0000

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

Dear Greg,
Yes I think we should leave 5586 "as it is" - or clean it up removing somew=
hat mysterious comments regarding non-TP usages.

Regards,
     Sasha

From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: Thursday, March 31, 2011 9:33 AM
To: Alexander Vainshtein
Cc: David Allan I; pwe3; Martini
Subject: Re: [PWE3] GAL above and below the PW label

Dear Sasha,
would your argument illustrate that use of GAL with PW label not only in MP=
LS-TP but in non-TP MPLS PW is strongly problematic? Should we leave RFC 55=
86 as is?

Regards,
Greg
On Wed, Mar 30, 2011 at 7:10 AM, Alexander Vainshtein <Alexander.Vainshtein=
@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
Dear Greg,
Please see some comments inline below.

Regards,
     Sasha

From: Greg Mirsky [mailto:gregimirsky@gmail.com<mailto:gregimirsky@gmail.co=
m>]
Sent: Wednesday, March 30, 2011 3:56 PM
To: Alexander Vainshtein
Cc: David Allan I; pwe3; Luca@core3.amsl.com<mailto:Luca@core3.amsl.com>; M=
artini
Subject: Re: [PWE3] GAL above and below the PW label

Dear Sasha,
I believe that there should not be MS-PW that crosses TP and non-TP domains=
.
[[[Sasha]]] I do not see any technical reasons to disallow that.
GAL might be used in each domain under different rules.
[[[Sasha]]] I believe that this would violate the requirement for the commo=
n data plane of MPLS and MPLS-TP.
If we strongly recommend that rule, then anyone not following it, at his/he=
r free will and risk, just might be shooting themselves in a foot.

Regards,
Greg
On Wed, Mar 30, 2011 at 1:56 AM, Alexander Vainshtein <Alexander.Vainshtein=
@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
Dave,
GAL may be a TP construct, but, IMO, MS-PWs (if not the other things) will =
easily break the demarcation lines between TP and non-TP areas.

If we stick with GAL being an MPLS-TP construct we should, IMHO, drop the a=
ttempts to use it with Ws.

Regards,
     Sasha

From: David Allan I [mailto:david.i.allan@ericsson.com<mailto:david.i.allan=
@ericsson.com>]
Sent: Wednesday, March 30, 2011 10:52 AM
To: Alexander Vainshtein; Thomas Nadeau; Luca Martini
Cc: pwe3
Subject: RE: GAL above and below the PW label

It does become a new behavior, GAL with S=3D0. However the combination of G=
AL being top label at the S-PE and TTL being encoded in the PW label means =
that fate sharing is broken at every S-PE. Life only gets a little more str=
ange if there is a FAT label as well...

That being said, GAL as bottom label is broken in any ECMP environment, whi=
ch is why GAL is a TP construct.

my 2 cents
D

________________________________
From: pwe3-bounces@ietf.org<mailto:pwe3-bounces@ietf.org> [mailto:pwe3-boun=
ces@ietf.org<mailto:pwe3-bounces@ietf.org>] On Behalf Of Alexander Vainshte=
in
Sent: Wednesday, March 30, 2011 10:37 AM
To: Thomas Nadeau; Luca Martini
Cc: pwe3
Subject: [PWE3] GAL above and below the PW label
Tom, Luca and all,
I would like to clarify - again - my position regarding GAL above the PW la=
bel.
I think that, other issues notwithstanding, it would create an issue if use=
d with MS-PWs:

*         GAL would be exposed at each S-PE (making a presumably end-to-end=
 OAM message to be intercepted)

*         What is even worse, there is no rule for forwarding the packet th=
at has been intercepted due to an exposed GAL (until you count the statemen=
t in 5586 requesting that a packet MUST NOT be ever forwarded based on GAL:=
)).  Hence it would be perfectly valid just to drop such a packet at the fi=
rst S-PE it crosses...
This said, I still  do not think using GAL below the PW label is a good ide=
a either. But this is a different story...

Regards,
     Sasha


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



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#def=
ault#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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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: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;}
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.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Dear Greg=
,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'>Yes I think we should le=
ave 5586 &#8220;as it is&#8221; &#8211; or clean it up removing somewhat my=
sterious comments regarding non-TP usages.<o:p></o:p></span></p><p class=3D=
MsoNormal><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 sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Re=
gards,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&=
nbsp; Sasha<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize: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;paddin=
g:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4D=
F 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Greg Mirsky [ma=
ilto:gregimirsky@gmail.com] <br><b>Sent:</b> Thursday, March 31, 2011 9:33 =
AM<br><b>To:</b> Alexander Vainshtein<br><b>Cc:</b> David Allan I; pwe3; Ma=
rtini<br><b>Subject:</b> Re: [PWE3] GAL above and below the PW label<o:p></=
o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cla=
ss=3DMsoNormal style=3D'margin-bottom:12.0pt'>Dear Sasha,<br>would your arg=
ument illustrate that use of GAL with PW label not only in MPLS-TP but in n=
on-TP MPLS PW is strongly problematic? Should we leave RFC 5586 as is?<br><=
br>Regards,<br>Greg<o:p></o:p></p><div><p class=3DMsoNormal>On Wed, Mar 30,=
 2011 at 7:10 AM, Alexander Vainshtein &lt;<a href=3D"mailto:Alexander.Vain=
shtein@ecitele.com" target=3D"_blank">Alexander.Vainshtein@ecitele.com</a>&=
gt; wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;c=
olor:#1F497D'>Dear Greg,</span><o:p></o:p></p><p class=3DMsoNormal style=3D=
'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-si=
ze:11.0pt;color:#1F497D'>Please see some comments inline below.</span><o:p>=
</o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-=
bottom-alt:auto'><span style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;color:#1F497D'>Rega=
rds,</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:=
auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;color:#1F4=
97D'>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</span><o:p></o:p></p><p class=3DMsoNorm=
al style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=
=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p><div style=
=3D'border:none;border-left:solid windowtext 1.5pt;padding:0cm 0cm 0cm 4.0p=
t;border-color:-moz-use-text-color -moz-use-text-color -moz-use-text-color =
blue'><div><div style=3D'border:none;border-top:solid windowtext 1.0pt;padd=
ing:3.0pt 0cm 0cm 0cm;border-color:-moz-use-text-color -moz-use-text-color'=
><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto'><b><span style=3D'font-size:10.0pt'>From:</span></b><span style=3D'=
font-size:10.0pt'> Greg Mirsky [mailto:<a href=3D"mailto:gregimirsky@gmail.=
com" target=3D"_blank">gregimirsky@gmail.com</a>] <br><b>Sent:</b> Wednesda=
y, March 30, 2011 3:56 PM<br><b>To:</b> Alexander Vainshtein<br><b>Cc:</b> =
David Allan I; pwe3; <a href=3D"mailto:Luca@core3.amsl.com" target=3D"_blan=
k">Luca@core3.amsl.com</a>; Martini<br><b>Subject:</b> Re: [PWE3] GAL above=
 and below the PW label</span><o:p></o:p></p></div></div><div><p class=3DMs=
oNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;=
<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;margin=
-bottom:12.0pt'>Dear Sasha,<br>I believe that there should not be MS-PW tha=
t crosses TP and non-TP domains.<o:p></o:p></p></div><p class=3DMsoNormal s=
tyle=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><b><i><span style=3D'=
font-size:11.0pt;color:#1F497D'>[[[Sasha]]] I do not see any technical reas=
ons to disallow that.</span></i></b><o:p></o:p></p><div><p class=3DMsoNorma=
l style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>GAL might be used =
in each domain under different rules. <o:p></o:p></p></div><p class=3DMsoNo=
rmal style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><b><i><span sty=
le=3D'font-size:11.0pt;color:#1F497D'>[[[Sasha]]] I believe that this would=
 violate the requirement for the common data plane of MPLS and MPLS-TP.</sp=
an></i></b><o:p></o:p></p><div><div><p class=3DMsoNormal style=3D'mso-margi=
n-top-alt:auto;margin-bottom:12.0pt'>If we strongly recommend that rule, th=
en anyone not following it, at his/her free will and risk, just might be sh=
ooting themselves in a foot.<br><br>Regards,<br>Greg<o:p></o:p></p><div><p =
class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:au=
to'>On Wed, Mar 30, 2011 at 1:56 AM, Alexander Vainshtein &lt;<a href=3D"ma=
ilto:Alexander.Vainshtein@ecitele.com" target=3D"_blank">Alexander.Vainshte=
in@ecitele.com</a>&gt; wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D=
'color:#1F497D'>Dave,</span><o:p></o:p></p><p class=3DMsoNormal style=3D'ms=
o-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'color:#1F4=
97D'>GAL may be a TP construct, but, IMO, MS-PWs (if not the other things) =
will easily break the demarcation lines between TP and non-TP areas.</span>=
<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto'><span style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p=
></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto'><span style=3D'color:#1F497D'>If we stick with GAL being an MPL=
S-TP construct we should, IMHO, drop the attempts to use it with Ws.</span>=
<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto'><span style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p=
></p><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-=
bottom-alt:auto'><span style=3D'color:#1F497D'>Regards,</span><o:p></o:p></=
p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto'><span style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</span=
><o:p></o:p></p></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto=
;mso-margin-bottom-alt:auto'><span style=3D'color:#1F497D'>&nbsp;</span><o:=
p></o:p></p><div style=3D'border:none;border-left:solid windowtext 1.5pt;pa=
dding:0cm 0cm 0cm 4.0pt;border-color:-moz-use-text-color -moz-use-text-colo=
r -moz-use-text-color blue'><div><div style=3D'border:none;border-top:solid=
 windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;border-color:-moz-use-text-colo=
r'><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto'><b><span style=3D'font-size:10.0pt'>From:</span></b><span style=
=3D'font-size:10.0pt'> David Allan I [mailto:<a href=3D"mailto:david.i.alla=
n@ericsson.com" target=3D"_blank">david.i.allan@ericsson.com</a>] <br><b>Se=
nt:</b> Wednesday, March 30, 2011 10:52 AM<br><b>To:</b> Alexander Vainshte=
in; Thomas Nadeau; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> RE: G=
AL above and below the PW label</span><o:p></o:p></p></div></div><div><div>=
<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'>&nbsp;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-al=
t:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:10.0pt;color:bl=
ue'>It does&nbsp;become a new behavior, GAL with S=3D0. However the combina=
tion of GAL being top label at the S-PE and TTL being encoded in the PW lab=
el means that fate sharing is broken at every S-PE. Life only gets a little=
 more strange if there is a FAT label as well...</span><o:p></o:p></p><p cl=
ass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
'>&nbsp;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:aut=
o;mso-margin-bottom-alt:auto'><span style=3D'font-size:10.0pt;color:blue'>T=
hat being said, GAL as bottom label is broken in any ECMP environment, whic=
h is why GAL is a TP construct.</span><o:p></o:p></p><p class=3DMsoNormal s=
tyle=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:=
p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span style=3D'font-size:10.0pt;color:blue'>my 2 cents</span><=
o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-mar=
gin-bottom-alt:auto'><span style=3D'font-size:10.0pt;color:blue'>D</span><o=
:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-marg=
in-bottom-alt:auto'>&nbsp;<o:p></o:p></p><div class=3DMsoNormal align=3Dcen=
ter style=3D'text-align:center'><hr size=3D2 width=3D"100%" align=3Dcenter>=
</div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;margin-bottom:1=
2.0pt'><b><span style=3D'font-size:10.0pt'>From:</span></b><span style=3D'f=
ont-size:10.0pt'> <a href=3D"mailto:pwe3-bounces@ietf.org" target=3D"_blank=
">pwe3-bounces@ietf.org</a> [mailto:<a href=3D"mailto:pwe3-bounces@ietf.org=
" target=3D"_blank">pwe3-bounces@ietf.org</a>] <b>On Behalf Of </b>Alexande=
r Vainshtein<br><b>Sent:</b> Wednesday, March 30, 2011 10:37 AM<br><b>To:</=
b> Thomas Nadeau; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> [PWE3]=
 GAL above and below the PW label</span><o:p></o:p></p><p class=3DMsoNormal=
 style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Tom, Luca and=
 all,<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;m=
so-margin-bottom-alt:auto'>I would like to clarify &#8211; again &#8211; my=
 position regarding GAL above the PW label.<o:p></o:p></p><p class=3DMsoNor=
mal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I think th=
at, other issues notwithstanding, it would create an issue if used with MS-=
PWs:<o:p></o:p></p><p><span style=3D'font-family:Symbol'>&middot;</span><sp=
an style=3D'font-size:7.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; </span>GAL would be exposed at each S-PE (making a presumably end-to-end=
 OAM message to be intercepted)<o:p></o:p></p><p><span style=3D'font-family=
:Symbol'>&middot;</span><span style=3D'font-size:7.0pt'>&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>What is even worse, there is no rule f=
or forwarding the packet that has been intercepted due to an exposed GAL (u=
ntil you count the statement in 5586 requesting that a packet MUST NOT be e=
ver forwarded based on GAL<span style=3D'font-family:Wingdings'>J</span>).&=
nbsp; Hence it would be perfectly valid just to drop such a packet at the f=
irst S-PE it crosses&#8230;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso=
-margin-top-alt:auto;mso-margin-bottom-alt:auto'>This said, I still&nbsp; d=
o not think using GAL below the PW label is a good idea either. But this is=
 a different story&#8230;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-m=
argin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><p clas=
s=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>=
Regards,<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:aut=
o;mso-margin-bottom-alt:auto'>&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o:p></o:p></p>=
<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'>&nbsp;<o:p></o:p></p></div></div></div></div></div><p class=3DMsoNor=
mal style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><br>____________=
___________________________________<br>pwe3 mailing list<br><a href=3D"mail=
to:pwe3@ietf.org" target=3D"_blank">pwe3@ietf.org</a><br><a href=3D"https:/=
/www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">https://www.ietf.org=
/mailman/listinfo/pwe3</a><o:p></o:p></p></div><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></=
p></div></div></div></div></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p></div></div></body></html>=

--_000_A3C5DF08D38B6049839A6F553B331C76D722D07531ILPTMAIL02eci_--

From sriganeshkini@gmail.com  Thu Mar 31 01:07:35 2011
Return-Path: <sriganeshkini@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6B8C28C227 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 01:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.889
X-Spam-Level: 
X-Spam-Status: No, score=-2.889 tagged_above=-999 required=5 tests=[AWL=0.089,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 Bzl6JjBCweai for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 01:07:34 -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 C1AD328C11C for <pwe3@ietf.org>; Thu, 31 Mar 2011 01:07:34 -0700 (PDT)
Received: by qwg5 with SMTP id 5so1531090qwg.31 for <pwe3@ietf.org>; Thu, 31 Mar 2011 01:09:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=0uF3tle7j4nFsToDdKOCzhOH8SGh9yzvb8YA8Uf6cKg=; b=jLdGsW7UBgW9hcZBfriONbc9lBMYb9RF3m2dgMIhHxt7hynozByFyo5HkkieDT9GvS 3aolyB6ouUkiFLVH5GYR6JGPKn3Qd3SIJK+ng1snv5FHe3G2d/9cV5dFDio1QeuI+/B4 zmcjVAWB1VUefBlHahd1L7wUA6APaw3OmazJA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=U/Xx0gxjyxDV8njttE5ai1NJkh7UKaewmcUnpvlYe9B76iC8iwAhtgsevKUIdBDpVk 9f7I6QJDJS6ZOS4Ua1tS/EjRwwOoSWiTC38aZnnF3w6FR8BHcKUQWQkwqikkX+Qlk+Vj PNnQtSe0l6SOmSscy6Oeaxi9L0CQeUa7zwwpg=
Received: by 10.224.190.68 with SMTP id dh4mr2011349qab.256.1301558954134; Thu, 31 Mar 2011 01:09:14 -0700 (PDT)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.229.136.12 with HTTP; Thu, 31 Mar 2011 01:08:44 -0700 (PDT)
In-Reply-To: <201103310703.p2V73Hrx045107@harbor.orleans.occnc.com>
References: <4D92F5D3.6080609@pi.nu> <201103310703.p2V73Hrx045107@harbor.orleans.occnc.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Thu, 31 Mar 2011 01:08:44 -0700
X-Google-Sender-Auth: -6nLFTmLdm7EbvReqCnR-ANG1eE
Message-ID: <AANLkTimwxBexevis2-5-vrGM-hA2APZeC0djwxUyV0jU@mail.gmail.com>
To: curtis@occnc.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: pwe3@ietf.org
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 08:07:35 -0000

All,

Just an FYI that a proposal for fate-sharing PW OAM and data given in
draft-kini-pwe3-inband-cc-offset

Just to summarize the proposal.
1. It does not require GAL in PW. TTL expiry is used to alert the S/T-PE.
2. It is mainly applicable when CW is not used in the PW.
3. It uses a fixed offset (negotiated between PW endpoints) after the
label stack before starting the OAM msg.
4. The bytes between the label-stack and the fixed offset is referred
to as a pseudoflow header and is filled with byte-values (by the PE)
that represent the flow for which OAM is desired. This helps PW OAM
and data to fate-share even when the intermediate node looks beyond
label stack to do multipath forwarding decisions.


On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar <curtis@occnc.com> wrot=
e:
>
> Loa, Dave, Sasha,
>
> I've snipped from various posts on the thread that Sasha started. =A0See
> inline.
>
> In message <4D92F5D3.6080609@pi.nu>
> Loa Andersson writes:
>>
>> All,
>>
>> missed a nuance in Sasha subject line.
>>
>> We have two issues
>>
>> - where the GAL is placed relative to the PW label, I =A0believe it is
>> =A0 =A0necessary to have the GAL below the PW label.
>>
>> - whether the the GAL label needs to be bottom of stack or not, it
>> =A0 =A0figure that this is really a discussion if it is possible to have
>> =A0 =A0a FAT label below the GAL or not. I'm not sure =A0about my prefer=
ences
>> =A0 =A0but I think it is possible.
>>
>> /Loa
>
> I agree with Loa's summary. =A0Not putting GAL at the bottom may confuse
> some LSR, but putting it above the PW label is likely to be even more
> problematic.
>
>
> In message <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs=
.ericsson.se>
> David Allan I writes:
>>
>> It does become a new behavior, GAL with S=3D3D0. However the combination=
 of G=3D
>> AL being top label at the S-PE and TTL being encoded in the PW label mea=
ns =3D
>> that fate sharing is broken at every S-PE. Life only gets a little more =
str=3D
>> ange if there is a FAT label as well...
>>
>> That being said, GAL as bottom label is broken in any ECMP environment, =
whi=3D
>> ch is why GAL is a TP construct.
>>
>> my 2 cents
>> D
>
> Dave,
>
> If GAL is broken for ECMP, which it is, then all TP OAM is broken.
> If all it takes to fix it is simple then lets just fix it.
>
> This is what we'd have to do.
>
> =A01) Relax the requirement that GAL be at the bottom
>
> =A02) Have the ingress insert GAL in the stack immediately below the
> =A0 =A0 label for which the measurement is made, keeping the rest of the
> =A0 =A0 label stack in place.
>
> The only thing the midpoing LSR at a multipath (LAG, link bundle for
> MPLS) has to do is skip over the GAL when hashing, as if the GAL
> wasn't there. =A0That will yield the same hash value and it will
> preserve fate-sharing across multipath.
>
> I prefer that we fix things rather than complain that they are broken.
>
> Curtis
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>



--=20
- Sri

From Alexander.Vainshtein@ecitele.com  Thu Mar 31 01:14:18 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56EE23A6B2C for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 01:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level: 
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.015,  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 GdUQB04e97kY for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 01:14:17 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id B5C4E3A69B7 for <pwe3@ietf.org>; Thu, 31 Mar 2011 01:14:16 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-f8-4d9437d4ee0a
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id CE.EE.19639.4D7349D4; Thu, 31 Mar 2011 10:14:12 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Thu, 31 Mar 2011 10:15:54 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Sriganesh Kini <sriganesh.kini@ericsson.com>, "curtis@occnc.com" <curtis@occnc.com>
Date: Thu, 31 Mar 2011 10:15:45 +0200
Thread-Topic: [PWE3] GAL above and below the PW label
Thread-Index: AcvvevAqNqiYaAWSQd6Q/GeBWx5uAAAACBow
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D07565@ILPTMAIL02.ecitele.com>
References: <4D92F5D3.6080609@pi.nu> <201103310703.p2V73Hrx045107@harbor.orleans.occnc.com> <AANLkTimwxBexevis2-5-vrGM-hA2APZeC0djwxUyV0jU@mail.gmail.com>
In-Reply-To: <AANLkTimwxBexevis2-5-vrGM-hA2APZeC0djwxUyV0jU@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="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 08:14:18 -0000

Sriganesh, Curtis and all,
IMHO and FWIW I think that the only problem with VCCV Type 3 is the risk of=
 OAM packets leaking out of T-PE towards the AC (if you accidentally set th=
e TTL value too high). To the best of my understanding the offset proposal =
does not solve that - or did I miss something?

One way to solve it is to use VCCV Type 1 (clean where applicable).
Another way would be by using GAL below the PW label (possible but messy). =
If the industry moves towards deprecating Ethernet PWs without CW,  it beco=
mes completely unnecessary.

My 2c,
     Sasha


> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> Sriganesh Kini
> Sent: Thursday, March 31, 2011 10:09 AM
> To: curtis@occnc.com
> Cc: pwe3@ietf.org
> Subject: Re: [PWE3] GAL above and below the PW label
>=20
> All,
>=20
> Just an FYI that a proposal for fate-sharing PW OAM and data given in
> draft-kini-pwe3-inband-cc-offset
>=20
> Just to summarize the proposal.
> 1. It does not require GAL in PW. TTL expiry is used to alert the S/T-
> PE.
> 2. It is mainly applicable when CW is not used in the PW.
> 3. It uses a fixed offset (negotiated between PW endpoints) after the
> label stack before starting the OAM msg.
> 4. The bytes between the label-stack and the fixed offset is referred
> to as a pseudoflow header and is filled with byte-values (by the PE)
> that represent the flow for which OAM is desired. This helps PW OAM
> and data to fate-share even when the intermediate node looks beyond
> label stack to do multipath forwarding decisions.
>=20
>=20
> On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar <curtis@occnc.com>
> wrote:
> >
> > Loa, Dave, Sasha,
> >
> > I've snipped from various posts on the thread that Sasha started.
> =A0See
> > inline.
> >
> > In message <4D92F5D3.6080609@pi.nu>
> > Loa Andersson writes:
> >>
> >> All,
> >>
> >> missed a nuance in Sasha subject line.
> >>
> >> We have two issues
> >>
> >> - where the GAL is placed relative to the PW label, I =A0believe it is
> >> =A0 =A0necessary to have the GAL below the PW label.
> >>
> >> - whether the the GAL label needs to be bottom of stack or not, it
> >> =A0 =A0figure that this is really a discussion if it is possible to ha=
ve
> >> =A0 =A0a FAT label below the GAL or not. I'm not sure =A0about my
> preferences
> >> =A0 =A0but I think it is possible.
> >>
> >> /Loa
> >
> > I agree with Loa's summary. =A0Not putting GAL at the bottom may
> confuse
> > some LSR, but putting it above the PW label is likely to be even more
> > problematic.
> >
> >
> > In message
> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson
> .se>
> > David Allan I writes:
> >>
> >> It does become a new behavior, GAL with S=3D3D0. However the
> combination of G=3D
> >> AL being top label at the S-PE and TTL being encoded in the PW label
> means =3D
> >> that fate sharing is broken at every S-PE. Life only gets a little
> more str=3D
> >> ange if there is a FAT label as well...
> >>
> >> That being said, GAL as bottom label is broken in any ECMP
> environment, whi=3D
> >> ch is why GAL is a TP construct.
> >>
> >> my 2 cents
> >> D
> >
> > Dave,
> >
> > If GAL is broken for ECMP, which it is, then all TP OAM is broken.
> > If all it takes to fix it is simple then lets just fix it.
> >
> > This is what we'd have to do.
> >
> > =A01) Relax the requirement that GAL be at the bottom
> >
> > =A02) Have the ingress insert GAL in the stack immediately below the
> > =A0 =A0 label for which the measurement is made, keeping the rest of th=
e
> > =A0 =A0 label stack in place.
> >
> > The only thing the midpoing LSR at a multipath (LAG, link bundle for
> > MPLS) has to do is skip over the GAL when hashing, as if the GAL
> > wasn't there. =A0That will yield the same hash value and it will
> > preserve fate-sharing across multipath.
> >
> > I prefer that we fix things rather than complain that they are
> broken.
> >
> > Curtis
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> >
>=20
>=20
>=20
> --
> - Sri
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

From stbryant@cisco.com  Thu Mar 31 01:19:23 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CB0D3A6826 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 01:19:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.478
X-Spam-Level: 
X-Spam-Status: No, score=-110.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 6zssqMYCIqkk for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 01:19:22 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 4D60C3A676A for <pwe3@ietf.org>; Thu, 31 Mar 2011 01:19:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=242; q=dns/txt; s=iport; t=1301559662; x=1302769262; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=ZEu0yx4WPesYtBmV51QGoi7d8Hc+QtVorFL2yri1DPA=; b=A3GOm3rNiPjcq22/4qvsDRs1U4umYQumgI/XcTTNgreDKMk9f77fyMrV BvxXAqDo70Sglph1JPKo5nbOA8UWj/5AL1gsEbT+TlNadRV0UjkiDKxxZ 5b8fjTHFLoOl3pqteEFMUIlMPkGRtfUulcL10zAV4nOfycADveS8MVkTE 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiUGAOs4lE2Q/khLgWdsb2JhbACYTI0DFAEBFiYlok+CcA4BmQaFawSNEQ
X-IronPort-AV: E=Sophos;i="4.63,274,1299456000"; d="scan'208";a="81595925"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 31 Mar 2011 08:21:01 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2V8L0SE001525 for <pwe3@ietf.org>; Thu, 31 Mar 2011 08:21:00 GMT
Received: from dhcp-55d0.meeting.ietf.org (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p2V8KxU20641; Thu, 31 Mar 2011 09:21:00 +0100 (BST)
Message-ID: <4D94396B.40101@cisco.com>
Date: Thu, 31 Mar 2011 09:20:59 +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.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: pwe3@ietf.org
References: <A3C5DF08D38B6049839A6F553B331C76D722D07246@ILPTMAIL02.ecitele.com>	<60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se>	<A3C5DF08D38B6049839A6F553B331C76D722D07263@ILPTMAIL02.ecitele.com> <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@mail.gmail.com>
In-Reply-To: <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 08:19:23 -0000

On 30/03/2011 14:55, Greg Mirsky wrote:
> Dear Sasha,
> I believe that there should not be MS-PW that crosses TP and non-TP 
> domains. 
That diminishes the generality of the design, which would in my view be 
a bad thing.

- Stewart

From curtis@occnc.com  Thu Mar 31 01:49:56 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBEA728C0F7 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 01:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level: 
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[AWL=-2.597,  BAYES_00=-2.599, J_CHICKENPOX_34=0.6, MANGLED_BELOW=2.3, MANGLED_SIZE=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 UXnBYV3Dlbip for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 01:49: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 4F2D028C0FD for <pwe3@ietf.org>; Thu, 31 Mar 2011 01:49:52 -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 p2V8pPZI047812; Thu, 31 Mar 2011 04:51:25 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103310851.p2V8pPZI047812@harbor.orleans.occnc.com>
To: Greg Mirsky <gregimirsky@gmail.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Wed, 30 Mar 2011 06:55:50 PDT." <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@mail.gmail.com> 
Date: Thu, 31 Mar 2011 04:51:25 -0400
Sender: curtis@occnc.com
Cc: Luca@core3.amsl.com, pwe3 <pwe3@ietf.org>, Martini <lmartini@cisco.com>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 08:49:57 -0000

In message <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@mail.gmail.com>
Greg Mirsky writes:
>  
> Dear Sasha,
>  
> I believe that there should not be MS-PW that crosses TP and non-TP
> domains.  GAL might be used in each domain under different rules. If
> we strongly recommend that rule, then anyone not following it, at
> his/her free will and risk, just might be shooting themselves in a
> foot.
>  
> Regards,
> Greg


Greg,

I think you are agreeing with Sasha on this.  You are both arguing
that the same MS-PW GAL may cross MPLS and MPLS-TP LSP and needs to
use a common PW OAM encaps, not a TP PW OAM encaps in one case and a
non-PT PW OAM encaps in another.

Curtis


> On Wed, Mar 30, 2011 at 1:56 AM, Alexander Vainshtein <
> Alexander.Vainshtein@ecitele.com> wrote:
>  
> > Dave,
> >
> > GAL may be a TP construct, but, IMO, MS-PWs (if not the other things) wil=
> l
> > easily break the demarcation lines between TP and non-TP areas.
> >
> >
> >
> > If we stick with GAL being an MPLS-TP construct we should, IMHO, drop the
> > attempts to use it with Ws.
> >
> >
> >
> > Regards,
> >
> >      Sasha
> >
> >
> >
> > *From:* David Allan I [mailto:david.i.allan@ericsson.com]
> > *Sent:* Wednesday, March 30, 2011 10:52 AM
> > *To:* Alexander Vainshtein; Thomas Nadeau; Luca Martini
> > *Cc:* pwe3
> > *Subject:* RE: GAL above and below the PW label
> >
> >
> >
> > It does become a new behavior, GAL with S=3D0. However the combination of=
>  GAL
> > being top label at the S-PE and TTL being encoded in the PW label means t=
> hat
> > fate sharing is broken at every S-PE. Life only gets a little more strang=
> e
> > if there is a FAT label as well...
> >
> >
> >
> > That being said, GAL as bottom label is broken in any ECMP environment,
> > which is why GAL is a TP construct.
> >
> >
> >
> > my 2 cents
> >
> > D
> >
> >
> > ------------------------------
> >
> > *From:* pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] *On Behalf O=
> f
> > *Alexander Vainshtein
> > *Sent:* Wednesday, March 30, 2011 10:37 AM
> > *To:* Thomas Nadeau; Luca Martini
> > *Cc:* pwe3
> > *Subject:* [PWE3] GAL above and below the PW label
> >
> > Tom, Luca and all,
> >
> > I would like to clarify =96 again =96 my position regarding GAL above the=
>  PW
> > label.
> >
> > I think that, other issues notwithstanding, it would create an issue if
> > used with MS-PWs:
> >
> > =B7         GAL would be exposed at each S-PE (making a presumably
> > end-to-end OAM message to be intercepted)
> >
> > =B7         What is even worse, there is no rule for forwarding the packe=
> t
> > that has been intercepted due to an exposed GAL (until you count the
> > statement in 5586 requesting that a packet MUST NOT be ever forwarded bas=
> ed
> > on GALJ).  Hence it would be perfectly valid just to drop such a packet a=
> t
> > the first S-PE it crosses=85
> >
> > This said, I still  do not think using GAL below the PW label is a good
> > idea either. But this is a different story=85
> >
> >
> >
> > Regards,
> >
> >      Sasha
> >
> >
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> >
> >
>  
> --bcaec5014c85dc4062049fb388ce
> Content-Type: text/html; charset=windows-1252
> Content-Transfer-Encoding: quoted-printable
>  
> Dear Sasha,<br>I believe that there should not be MS-PW that crosses TP and=
>  non-TP domains. GAL might be used in each domain under different rules. If=
>  we strongly recommend that rule, then anyone not following it, at his/her =
> free will and risk, just might be shooting themselves in a foot.<br>
> <br>Regards,<br>Greg<br><br><div class=3D"gmail_quote">On Wed, Mar 30, 2011=
>  at 1:56 AM, Alexander Vainshtein <span dir=3D"ltr">&lt;<a href=3D"mailto:A=
> lexander.Vainshtein@ecitele.com">Alexander.Vainshtein@ecitele.com</a>&gt;</=
> span> wrote:<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 link=3D"blue=
> " vlink=3D"purple" lang=3D"EN-US"><div><p class=3D"MsoNormal"><span style=
> =3D"color: rgb(31, 73, 125);">Dave,</span></p>
> <p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">GAL may be =
> a TP construct, but, IMO, MS-PWs (if not the other things) will easily brea=
> k the demarcation lines between TP and non-TP areas.</span></p><p class=3D"=
> MsoNormal">
> <span style=3D"color: rgb(31, 73, 125);">=A0</span></p><p class=3D"MsoNorma=
> l"><span style=3D"color: rgb(31, 73, 125);">If we stick with GAL being an M=
> PLS-TP construct we should, IMHO, drop the attempts to use it with Ws.</spa=
> n></p>
> <p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">=A0</span><=
> /p><div><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">Reg=
> ards,</span></p><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 12=
> 5);">=A0=A0=A0=A0 Sasha</span></p>
> </div><p class=3D"MsoNormal"><span style=3D"color: rgb(31, 73, 125);">=A0</=
> span></p><div style=3D"border-width: medium medium medium 1.5pt; border-sty=
> le: none none none solid; border-color: -moz-use-text-color -moz-use-text-c=
> olor -moz-use-text-color blue; padding: 0cm 0cm 0cm 4pt;">
> <div><div style=3D"border-width: 1pt medium medium; border-style: solid non=
> e none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-=
> color; padding: 3pt 0cm 0cm;"><p class=3D"MsoNormal"><b><span style=3D"font=
> -size: 10pt;">From:</span></b><span style=3D"font-size: 10pt;"> David Allan=
>  I [mailto:<a href=3D"mailto:david.i.allan@ericsson.com" target=3D"_blank">=
> david.i.allan@ericsson.com</a>] <br>
> <b>Sent:</b> Wednesday, March 30, 2011 10:52 AM<br><b>To:</b> Alexander Vai=
> nshtein; Thomas Nadeau; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> =
> RE: GAL above and below the PW label</span></p></div></div><div><div></div>
> <div class=3D"h5"><p class=3D"MsoNormal">=A0</p><p class=3D"MsoNormal"><spa=
> n style=3D"font-size: 10pt; color: blue;">It does=A0become a new behavior, =
> GAL with S=3D0. However the combination of GAL being top label at the S-PE =
> and TTL being encoded in the PW label means that fate sharing is broken at =
> every S-PE. Life only gets a little more strange if there is a FAT label as=
>  well...</span><span style=3D"font-size: 12pt; font-family: &quot;Times New=
>  Roman&quot;,&quot;serif&quot;;"></span></p>
> <p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: &quot;T=
> imes New Roman&quot;,&quot;serif&quot;;">=A0</span></p><p class=3D"MsoNorma=
> l"><span style=3D"font-size: 10pt; color: blue;">That being said, GAL as bo=
> ttom label is broken in any ECMP environment, which is why GAL is a TP cons=
> truct.</span><span style=3D"font-size: 12pt; font-family: &quot;Times New R=
> oman&quot;,&quot;serif&quot;;"></span></p>
> <p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: &quot;T=
> imes New Roman&quot;,&quot;serif&quot;;">=A0</span></p><p class=3D"MsoNorma=
> l"><span style=3D"font-size: 10pt; color: blue;">my 2 cents</span><span sty=
> le=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif=
> &quot;;"></span></p>
> <p class=3D"MsoNormal"><span style=3D"font-size: 10pt; color: blue;">D</spa=
> n><span style=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot;,=
> &quot;serif&quot;;"></span></p><p class=3D"MsoNormal"><span style=3D"font-s=
> ize: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">=A0=
> </span></p>
> <div class=3D"MsoNormal" style=3D"text-align: center;" align=3D"center"><sp=
> an style=3D"font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot=
> ;serif&quot;;"><hr width=3D"100%" align=3D"center" size=3D"2"></span></div>=
> <p class=3D"MsoNormal" style=3D"margin-bottom: 12pt;">
> <b><span style=3D"font-size: 10pt;">From:</span></b><span style=3D"font-siz=
> e: 10pt;"> <a href=3D"mailto:pwe3-bounces@ietf.org" target=3D"_blank">pwe3-=
> bounces@ietf.org</a> [mailto:<a href=3D"mailto:pwe3-bounces@ietf.org" targe=
> t=3D"_blank">pwe3-bounces@ietf.org</a>] <b>On Behalf Of </b>Alexander Vains=
> htein<br>
> <b>Sent:</b> Wednesday, March 30, 2011 10:37 AM<br><b>To:</b> Thomas Nadeau=
> ; Luca Martini<br><b>Cc:</b> pwe3<br><b>Subject:</b> [PWE3] GAL above and b=
> elow the PW label</span><span style=3D"font-size: 12pt; font-family: &quot;=
> Times New Roman&quot;,&quot;serif&quot;;"></span></p>
> <p class=3D"MsoNormal">Tom, Luca and all,</p><p class=3D"MsoNormal">I would=
>  like to clarify =96 again =96 my position regarding GAL above the PW label=
> .</p><p class=3D"MsoNormal">I think that, other issues notwithstanding, it =
> would create an issue if used with MS-PWs:</p>
> <p><span style=3D"font-family: Symbol;">=B7</span><span style=3D"font-size:=
>  7pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">=A0=A0=
> =A0=A0=A0=A0=A0=A0 </span>GAL would be exposed at each S-PE (making a presu=
> mably end-to-end OAM message to be intercepted)</p>
> <p><span style=3D"font-family: Symbol;">=B7</span><span style=3D"font-size:=
>  7pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">=A0=A0=
> =A0=A0=A0=A0=A0=A0 </span>What is even worse, there is no rule for forwardi=
> ng the packet that has been intercepted due to an exposed GAL (until you co=
> unt the statement in 5586 requesting that a packet MUST NOT be ever forward=
> ed based on GAL<span style=3D"font-family: Wingdings;">J</span>).=A0 Hence =
> it would be perfectly valid just to drop such a packet at the first S-PE it=
>  crosses=85</p>
> <p class=3D"MsoNormal">This said, I still=A0 do not think using GAL below t=
> he PW label is a good idea either. But this is a different story=85</p><p c=
> lass=3D"MsoNormal">=A0</p><p class=3D"MsoNormal">Regards,</p><p class=3D"Ms=
> oNormal">=A0=A0=A0=A0 Sasha</p>
> <p class=3D"MsoNormal">=A0</p></div></div></div></div></div><br>___________=
> ____________________________________<br>
> pwe3 mailing list<br>
> <a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>
> <a href=3D"https://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">ht=
> tps://www.ietf.org/mailman/listinfo/pwe3</a><br>
> <br></blockquote></div><br>
>  
> --bcaec5014c85dc4062049fb388ce--
>  
> --===============0069009002==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>  
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>  
> --===============0069009002==--


From curtis@occnc.com  Thu Mar 31 02:00:40 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA5893A6C1D for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.478
X-Spam-Level: 
X-Spam-Status: No, score=-2.478 tagged_above=-999 required=5 tests=[AWL=0.121,  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 NOwOFFHv4XMf for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:00:39 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 9A19A3A6C12 for <pwe3@ietf.org>; Thu, 31 Mar 2011 02:00:39 -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 p2V929iQ048044; Thu, 31 Mar 2011 05:02:10 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103310902.p2V929iQ048044@harbor.orleans.occnc.com>
To: Greg Mirsky <gregimirsky@gmail.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Wed, 30 Mar 2011 06:55:50 PDT." <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@mail.gmail.com> 
Date: Thu, 31 Mar 2011 05:02:09 -0400
Sender: curtis@occnc.com
Cc: Luca@core3.amsl.com, pwe3 <pwe3@ietf.org>, Martini <lmartini@cisco.com>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 09:00:40 -0000

In message <AANLkTinTKnr6UaurF4QxLwfjVdxZS0VO3svbq-GCY7Y+@mail.gmail.com>
Greg Mirsky writes:

> I believe that there should not be MS-PW that crosses TP and non-TP
> domains.

Oops.  I missed the "not".  I agree with Sasha, that this violates the
"one data plane" requirement.

Reality is that the core in any major provider packet netowrk today is
MPLS and will remain MPLS.  It may be MPLS carrying TP if we move
forward with work that will support that.  OTOH, if TP advocates keep
trying to make sure that MPLS and MPLS-TP are as incompatible as
possible, then they may be effectively killing TP.

Restricting MS-PW to use MPLS on all segments or MPLS-TP on all
segments but not both should *not* be a goal.  Allowing some segments
of a MS-PW to be MPLS an other segments to be MPLS-TP should be an
explicit goal.

Curtis

From curtis@occnc.com  Thu Mar 31 02:09:13 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B35D28C216 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  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 p+kG1LkGtSCO for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:09: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 BF0DF28C20B for <pwe3@ietf.org>; Thu, 31 Mar 2011 02:09: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 p2V9AbZ5048623; Thu, 31 Mar 2011 05:10:37 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103310910.p2V9AbZ5048623@harbor.orleans.occnc.com>
To: David Allan I <david.i.allan@ericsson.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 31 Mar 2011 03:23:51 EDT." <60C093A41B5E45409A19D42CF7786DFD51D531132B@EUSAACMS0703.eamcs.ericsson.se>
Date: Thu, 31 Mar 2011 05:10:37 -0400
Sender: curtis@occnc.com
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 09:09:13 -0000

In message <60C093A41B5E45409A19D42CF7786DFD51D531132B@EUSAACMS0703.eamcs.ericsson.se>
David Allan I writes:
>  
> HI Curtis:
>  
> My suggestion is to avoid the GAL for PWs if it is to be a
> homogenizing agent across TP and IP/MPLS domains in the form of
> MS-PWs. The scenarios in which it was broken was simply a statement of
> fact.
>  
> As for the problem GAL was proposed to fix (lack of CW), there are
> solutions on the table, just not palatable...
>  
> D


Dave,

I think we are in agreement.

We either use a non-GAL mechanism, or we fix GAL by removing the
bottom of stack restriction and use GAL.

I prefer the latter option, fix GAL.

I support not using GAL at all in PW if GAL can't be fixed.

Fixing GAL should really be an MPLS WG discussion.  The result of that
discussion in MPLS should gate whether any PW proposal to use GAL can
be moved forward.

Curtis


> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Curtis Villamizar
> Sent: Thursday, March 31, 2011 9:03 AM
> To: Loa Andersson
> Cc: pwe3@ietf.org
> Subject: Re: [PWE3] GAL above and below the PW label
>  
>  
> Loa, Dave, Sasha,
>  
> I've snipped from various posts on the thread that Sasha started.  See inline.
>  
> In message <4D92F5D3.6080609@pi.nu>
> Loa Andersson writes:
> >  
> > All,
> >  
> > missed a nuance in Sasha subject line.
> >  
> > We have two issues
> >  
> > - where the GAL is placed relative to the PW label, I  believe it is
> >    necessary to have the GAL below the PW label.
> >  
> > - whether the the GAL label needs to be bottom of stack or not, it
> >    figure that this is really a discussion if it is possible to have
> >    a FAT label below the GAL or not. I'm not sure  about my preferences
> >    but I think it is possible.
> >  
> > /Loa
>  
> I agree with Loa's summary.  Not putting GAL at the bottom may confuse some LSR, but putting it above the PW label is likely to be even more problematic.
>  
>  
> In message <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson.se>
> David Allan I writes:
> >  
> > It does become a new behavior, GAL with S=3D0. However the combination 
> > of G= AL being top label at the S-PE and TTL being encoded in the PW 
> > label means = that fate sharing is broken at every S-PE. Life only 
> > gets a little more str= ange if there is a FAT label as well...
> >  
> > That being said, GAL as bottom label is broken in any ECMP 
> > environment, whi= ch is why GAL is a TP construct.
> >  
> > my 2 cents
> > D
>  
> Dave,
>  
> If GAL is broken for ECMP, which it is, then all TP OAM is broken.
> If all it takes to fix it is simple then lets just fix it.
>  
> This is what we'd have to do.
>  
>   1) Relax the requirement that GAL be at the bottom
>  
>   2) Have the ingress insert GAL in the stack immediately below the
>      label for which the measurement is made, keeping the rest of the
>      label stack in place.
>  
> The only thing the midpoing LSR at a multipath (LAG, link bundle for
> MPLS) has to do is skip over the GAL when hashing, as if the GAL wasn't there.  That will yield the same hash value and it will preserve fate-sharing across multipath.
>  
> I prefer that we fix things rather than complain that they are broken.
>  
> Curtis
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3


From curtis@occnc.com  Thu Mar 31 02:15:10 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 208F03A6AD5 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.488
X-Spam-Level: 
X-Spam-Status: No, score=-2.488 tagged_above=-999 required=5 tests=[AWL=0.111,  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 ByTawz-QCGoD for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:15:09 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 71FE628C0DF for <pwe3@ietf.org>; Thu, 31 Mar 2011 02:15:08 -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 p2V9Gh0m048734; Thu, 31 Mar 2011 05:16:43 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103310916.p2V9Gh0m048734@harbor.orleans.occnc.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 31 Mar 2011 10:15:45 +0200." <A3C5DF08D38B6049839A6F553B331C76D722D07565@ILPTMAIL02.ecitele.com> 
Date: Thu, 31 Mar 2011 05:16:43 -0400
Sender: curtis@occnc.com
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 09:15:10 -0000

In message <A3C5DF08D38B6049839A6F553B331C76D722D07565@ILPTMAIL02.ecitele.com>
Alexander Vainshtein writes:
>  
> Sriganesh, Curtis and all,
>  
> IMHO and FWIW I think that the only problem with VCCV Type 3 is the
> risk of OAM packets leaking out of T-PE towards the AC (if you
> accidentally set the TTL value too high). To the best of my
> understanding the offset proposal does not solve that - or did I miss
> something?

That can be fixed by looking at the next label (if there is one) before
forwarding at PW egress to the AC.  The implementation already has to
make a similar chack on every packet if CW is used, but looking after
the S=1 label entry.  If CW is used it would be wise to do both checks
(be liberal in what you accept and careful in what you forward).

> One way to solve it is to use VCCV Type 1 (clean where applicable).
> Another way would be by using GAL below the PW label (possible but
> messy). If the industry moves towards deprecating Ethernet PWs without
> CW, it becomes completely unnecessary.

I agree with your last sentence but I don't know that non-CW can be
depricated.

> My 2c,
>      Sasha

Curtis


> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> > Sriganesh Kini
> > Sent: Thursday, March 31, 2011 10:09 AM
> > To: curtis@occnc.com
> > Cc: pwe3@ietf.org
> > Subject: Re: [PWE3] GAL above and below the PW label
> > 
> > All,
> > 
> > Just an FYI that a proposal for fate-sharing PW OAM and data given in
> > draft-kini-pwe3-inband-cc-offset
> > 
> > Just to summarize the proposal.
> > 1. It does not require GAL in PW. TTL expiry is used to alert the S/T-
> > PE.
> > 2. It is mainly applicable when CW is not used in the PW.
> > 3. It uses a fixed offset (negotiated between PW endpoints) after the
> > label stack before starting the OAM msg.
> > 4. The bytes between the label-stack and the fixed offset is referred
> > to as a pseudoflow header and is filled with byte-values (by the PE)
> > that represent the flow for which OAM is desired. This helps PW OAM
> > and data to fate-share even when the intermediate node looks beyond
> > label stack to do multipath forwarding decisions.
> > 
> > 
> > On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar <curtis@occnc.com>
> > wrote:
> > >
> > > Loa, Dave, Sasha,
> > >
> > > I've snipped from various posts on the thread that Sasha started.
> >  See
> > > inline.
> > >
> > > In message <4D92F5D3.6080609@pi.nu>
> > > Loa Andersson writes:
> > >>
> > >> All,
> > >>
> > >> missed a nuance in Sasha subject line.
> > >>
> > >> We have two issues
> > >>
> > >> - where the GAL is placed relative to the PW label, I  believe it is
> > >>    necessary to have the GAL below the PW label.
> > >>
> > >> - whether the the GAL label needs to be bottom of stack or not, it
> > >>    figure that this is really a discussion if it is possible to have
> > >>    a FAT label below the GAL or not. I'm not sure  about my
> > preferences
> > >>    but I think it is possible.
> > >>
> > >> /Loa
> > >
> > > I agree with Loa's summary.  Not putting GAL at the bottom may
> > confuse
> > > some LSR, but putting it above the PW label is likely to be even more
> > > problematic.
> > >
> > >
> > > In message
> > <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson
> > .se>
> > > David Allan I writes:
> > >>
> > >> It does become a new behavior, GAL with S=3D0. However the
> > combination of G=
> > >> AL being top label at the S-PE and TTL being encoded in the PW label
> > means =
> > >> that fate sharing is broken at every S-PE. Life only gets a little
> > more str=
> > >> ange if there is a FAT label as well...
> > >>
> > >> That being said, GAL as bottom label is broken in any ECMP
> > environment, whi=
> > >> ch is why GAL is a TP construct.
> > >>
> > >> my 2 cents
> > >> D
> > >
> > > Dave,
> > >
> > > If GAL is broken for ECMP, which it is, then all TP OAM is broken.
> > > If all it takes to fix it is simple then lets just fix it.
> > >
> > > This is what we'd have to do.
> > >
> > >  1) Relax the requirement that GAL be at the bottom
> > >
> > >  2) Have the ingress insert GAL in the stack immediately below the
> > >     label for which the measurement is made, keeping the rest of the
> > >     label stack in place.
> > >
> > > The only thing the midpoing LSR at a multipath (LAG, link bundle for
> > > MPLS) has to do is skip over the GAL when hashing, as if the GAL
> > > wasn't there.  That will yield the same hash value and it will
> > > preserve fate-sharing across multipath.
> > >
> > > I prefer that we fix things rather than complain that they are
> > broken.
> > >
> > > Curtis
> > > _______________________________________________
> > > pwe3 mailing list
> > > pwe3@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pwe3
> > >
> > 
> > 
> > 
> > --
> > - Sri
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3


From sriganeshkini@gmail.com  Thu Mar 31 02:16:40 2011
Return-Path: <sriganeshkini@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8786828C1FC for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.903
X-Spam-Level: 
X-Spam-Status: No, score=-2.903 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 UAdLLzFL7XHg for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:16:39 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 0E97728C108 for <pwe3@ietf.org>; Thu, 31 Mar 2011 02:16:38 -0700 (PDT)
Received: by qyk7 with SMTP id 7so1452525qyk.10 for <pwe3@ietf.org>; Thu, 31 Mar 2011 02:18:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=sE0/pY+y50GMRzNOM06iwMn8hEP9GEzrVFL5xBuvqTs=; b=li+53oM8qLA9nB0n8SNF/KJ6J6xR8ydiH73RrqO4zCyN9hF7ZTVxpl5JI6IcOvsXhu nPRAwkuNM1iPS9exmX7kOMlIOUFghIQm/MxV0dXSAQdf4LHkN2TvhzAPCtjQfa66LB7O q8OSgxEsEMIM4p9indZwIB9qBhXXqEciWKMXI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=k74WUc+S1QF4rhgSib6rBrSlh4aqceHbx8U1aThovBBTX2KY6foCH0URxOwMR2pN+Z w5fD/JbADtKPEBSa6w3Juf6XSysh+JlgKTGQLc4sUDwCS25MXCYRYUMftBysEr8xUI0r liFzjyCNC1YgPmnIPe7PN1J7clJiyElueX0f0=
Received: by 10.229.82.84 with SMTP id a20mr1984841qcl.104.1301563098182; Thu, 31 Mar 2011 02:18:18 -0700 (PDT)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.229.136.12 with HTTP; Thu, 31 Mar 2011 02:17:48 -0700 (PDT)
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D722D07565@ILPTMAIL02.ecitele.com>
References: <4D92F5D3.6080609@pi.nu> <201103310703.p2V73Hrx045107@harbor.orleans.occnc.com> <AANLkTimwxBexevis2-5-vrGM-hA2APZeC0djwxUyV0jU@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D722D07565@ILPTMAIL02.ecitele.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Thu, 31 Mar 2011 02:17:48 -0700
X-Google-Sender-Auth: C_ogObjX83rQ2ygiwleMA8aYKA8
Message-ID: <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe@mail.gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 09:16:40 -0000

Sasha, that issue with VCCV Type-3 (without CW) is not addressed by
the draft. Practically, is that a major issue ? Especially setting TTL
> 1 for SS PW is possible I guess but would be some kind of serious
operational oversight. Besides such a packet would fail some check
along the path.

Also, what I heard at the mic regarding impl results is that it
doesn't make sense to deprecate what is already deployed.

Note that CC Type 1 prevents ECMP (when FAT-PW is not available).
Using GAL below PW also requires ECMP based on label hashing to ignore
reserved labels.

2011/3/31 Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>:
> Sriganesh, Curtis and all,
> IMHO and FWIW I think that the only problem with VCCV Type 3 is the risk =
of OAM packets leaking out of T-PE towards the AC (if you accidentally set =
the TTL value too high). To the best of my understanding the offset proposa=
l does not solve that - or did I miss something?
>
> One way to solve it is to use VCCV Type 1 (clean where applicable).
> Another way would be by using GAL below the PW label (possible but messy)=
. If the industry moves towards deprecating Ethernet PWs without CW, =A0it =
becomes completely unnecessary.
>
> My 2c,
> =A0 =A0 Sasha
>
>
>> -----Original Message-----
>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
>> Sriganesh Kini
>> Sent: Thursday, March 31, 2011 10:09 AM
>> To: curtis@occnc.com
>> Cc: pwe3@ietf.org
>> Subject: Re: [PWE3] GAL above and below the PW label
>>
>> All,
>>
>> Just an FYI that a proposal for fate-sharing PW OAM and data given in
>> draft-kini-pwe3-inband-cc-offset
>>
>> Just to summarize the proposal.
>> 1. It does not require GAL in PW. TTL expiry is used to alert the S/T-
>> PE.
>> 2. It is mainly applicable when CW is not used in the PW.
>> 3. It uses a fixed offset (negotiated between PW endpoints) after the
>> label stack before starting the OAM msg.
>> 4. The bytes between the label-stack and the fixed offset is referred
>> to as a pseudoflow header and is filled with byte-values (by the PE)
>> that represent the flow for which OAM is desired. This helps PW OAM
>> and data to fate-share even when the intermediate node looks beyond
>> label stack to do multipath forwarding decisions.
>>
>>
>> On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar <curtis@occnc.com>
>> wrote:
>> >
>> > Loa, Dave, Sasha,
>> >
>> > I've snipped from various posts on the thread that Sasha started.
>> =A0See
>> > inline.
>> >
>> > In message <4D92F5D3.6080609@pi.nu>
>> > Loa Andersson writes:
>> >>
>> >> All,
>> >>
>> >> missed a nuance in Sasha subject line.
>> >>
>> >> We have two issues
>> >>
>> >> - where the GAL is placed relative to the PW label, I =A0believe it i=
s
>> >> =A0 =A0necessary to have the GAL below the PW label.
>> >>
>> >> - whether the the GAL label needs to be bottom of stack or not, it
>> >> =A0 =A0figure that this is really a discussion if it is possible to h=
ave
>> >> =A0 =A0a FAT label below the GAL or not. I'm not sure =A0about my
>> preferences
>> >> =A0 =A0but I think it is possible.
>> >>
>> >> /Loa
>> >
>> > I agree with Loa's summary. =A0Not putting GAL at the bottom may
>> confuse
>> > some LSR, but putting it above the PW label is likely to be even more
>> > problematic.
>> >
>> >
>> > In message
>> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson
>> .se>
>> > David Allan I writes:
>> >>
>> >> It does become a new behavior, GAL with S=3D3D0. However the
>> combination of G=3D
>> >> AL being top label at the S-PE and TTL being encoded in the PW label
>> means =3D
>> >> that fate sharing is broken at every S-PE. Life only gets a little
>> more str=3D
>> >> ange if there is a FAT label as well...
>> >>
>> >> That being said, GAL as bottom label is broken in any ECMP
>> environment, whi=3D
>> >> ch is why GAL is a TP construct.
>> >>
>> >> my 2 cents
>> >> D
>> >
>> > Dave,
>> >
>> > If GAL is broken for ECMP, which it is, then all TP OAM is broken.
>> > If all it takes to fix it is simple then lets just fix it.
>> >
>> > This is what we'd have to do.
>> >
>> > =A01) Relax the requirement that GAL be at the bottom
>> >
>> > =A02) Have the ingress insert GAL in the stack immediately below the
>> > =A0 =A0 label for which the measurement is made, keeping the rest of t=
he
>> > =A0 =A0 label stack in place.
>> >
>> > The only thing the midpoing LSR at a multipath (LAG, link bundle for
>> > MPLS) has to do is skip over the GAL when hashing, as if the GAL
>> > wasn't there. =A0That will yield the same hash value and it will
>> > preserve fate-sharing across multipath.
>> >
>> > I prefer that we fix things rather than complain that they are
>> broken.
>> >
>> > Curtis
>> > _______________________________________________
>> > pwe3 mailing list
>> > pwe3@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pwe3
>> >
>>
>>
>>
>> --
>> - Sri
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>



--=20
- Sri

From Alexander.Vainshtein@ecitele.com  Thu Mar 31 02:27:10 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA09D28C1F2 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014,  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 x+2kxZ9majuZ for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:27:08 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id E058628C1CE for <pwe3@ietf.org>; Thu, 31 Mar 2011 02:23:51 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-c1-4d94481c0786
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id B5.E0.19639.C18449D4; Thu, 31 Mar 2011 11:23:40 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Thu, 31 Mar 2011 11:25:22 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@occnc.com" <curtis@occnc.com>
Date: Thu, 31 Mar 2011 11:25:12 +0200
Thread-Topic: [PWE3] GAL above and below the PW label 
Thread-Index: AcvvhF/PLPK3W6DpQVCbmWVpzR+SfwAACFHw
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D075E4@ILPTMAIL02.ecitele.com>
References: Your message of "Thu, 31 Mar 2011 10:15:45 +0200." <A3C5DF08D38B6049839A6F553B331C76D722D07565@ILPTMAIL02.ecitele.com> <201103310916.p2V9Gh0m048734@harbor.orleans.occnc.com>
In-Reply-To: <201103310916.p2V9Gh0m048734@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="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 09:27:11 -0000

Curtis,
The results of the PWE3 survey (it is difficult to say how representative i=
t really is) seem to indicate=20
that ability to support CW in the Ethernet PW encapsulation is quite common=
 (13-14 out of 17 respondents)
and reasonably used (8 out of 17 respondents).

This survey does not provide any information about using GAL with PWs. Mayb=
e we should extend the survey to learn that?
My expectation, not based on any facts, is that no one has been using it at=
 the moment:-).

So if the choice is between fixing an old bug at the root (by deprecating P=
W encapsulations without CW) or adding a new patch (GAL in the PW) for the =
same purpose, I clearly prefer the first option.=20

Regards,
     Sasha


> -----Original Message-----
> From: curtis@occnc.com [mailto:curtis@occnc.com]
> Sent: Thursday, March 31, 2011 11:17 AM
> To: Alexander Vainshtein
> Cc: Sriganesh Kini; curtis@occnc.com; pwe3@ietf.org
> Subject: Re: [PWE3] GAL above and below the PW label
>=20
>=20
> In message
> <A3C5DF08D38B6049839A6F553B331C76D722D07565@ILPTMAIL02.ecitele.com>
> Alexander Vainshtein writes:
> >
> > Sriganesh, Curtis and all,
> >
> > IMHO and FWIW I think that the only problem with VCCV Type 3 is the
> > risk of OAM packets leaking out of T-PE towards the AC (if you
> > accidentally set the TTL value too high). To the best of my
> > understanding the offset proposal does not solve that - or did I miss
> > something?
>=20
> That can be fixed by looking at the next label (if there is one) before
> forwarding at PW egress to the AC.  The implementation already has to
> make a similar chack on every packet if CW is used, but looking after
> the S=3D1 label entry.  If CW is used it would be wise to do both checks
> (be liberal in what you accept and careful in what you forward).
>=20
> > One way to solve it is to use VCCV Type 1 (clean where applicable).
> > Another way would be by using GAL below the PW label (possible but
> > messy). If the industry moves towards deprecating Ethernet PWs
> without
> > CW, it becomes completely unnecessary.
>=20
> I agree with your last sentence but I don't know that non-CW can be
> depricated.
>=20
> > My 2c,
> >      Sasha
>=20
> Curtis
>=20
>=20
> > > -----Original Message-----
> > > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> Behalf Of
> > > Sriganesh Kini
> > > Sent: Thursday, March 31, 2011 10:09 AM
> > > To: curtis@occnc.com
> > > Cc: pwe3@ietf.org
> > > Subject: Re: [PWE3] GAL above and below the PW label
> > >
> > > All,
> > >
> > > Just an FYI that a proposal for fate-sharing PW OAM and data given
> in
> > > draft-kini-pwe3-inband-cc-offset
> > >
> > > Just to summarize the proposal.
> > > 1. It does not require GAL in PW. TTL expiry is used to alert the
> S/T-
> > > PE.
> > > 2. It is mainly applicable when CW is not used in the PW.
> > > 3. It uses a fixed offset (negotiated between PW endpoints) after
> the
> > > label stack before starting the OAM msg.
> > > 4. The bytes between the label-stack and the fixed offset is
> referred
> > > to as a pseudoflow header and is filled with byte-values (by the
> PE)
> > > that represent the flow for which OAM is desired. This helps PW OAM
> > > and data to fate-share even when the intermediate node looks beyond
> > > label stack to do multipath forwarding decisions.
> > >
> > >
> > > On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar
> <curtis@occnc.com>
> > > wrote:
> > > >
> > > > Loa, Dave, Sasha,
> > > >
> > > > I've snipped from various posts on the thread that Sasha started.
> > > =A0See
> > > > inline.
> > > >
> > > > In message <4D92F5D3.6080609@pi.nu>
> > > > Loa Andersson writes:
> > > >>
> > > >> All,
> > > >>
> > > >> missed a nuance in Sasha subject line.
> > > >>
> > > >> We have two issues
> > > >>
> > > >> - where the GAL is placed relative to the PW label, I =A0believe
> it is
> > > >> =A0 =A0necessary to have the GAL below the PW label.
> > > >>
> > > >> - whether the the GAL label needs to be bottom of stack or not,
> it
> > > >> =A0 =A0figure that this is really a discussion if it is possible t=
o
> have
> > > >> =A0 =A0a FAT label below the GAL or not. I'm not sure =A0about my
> > > preferences
> > > >> =A0 =A0but I think it is possible.
> > > >>
> > > >> /Loa
> > > >
> > > > I agree with Loa's summary. =A0Not putting GAL at the bottom may
> > > confuse
> > > > some LSR, but putting it above the PW label is likely to be even
> more
> > > > problematic.
> > > >
> > > >
> > > > In message
> > >
> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson
> > > .se>
> > > > David Allan I writes:
> > > >>
> > > >> It does become a new behavior, GAL with S=3D3D0. However the
> > > combination of G=3D
> > > >> AL being top label at the S-PE and TTL being encoded in the PW
> label
> > > means =3D
> > > >> that fate sharing is broken at every S-PE. Life only gets a
> little
> > > more str=3D
> > > >> ange if there is a FAT label as well...
> > > >>
> > > >> That being said, GAL as bottom label is broken in any ECMP
> > > environment, whi=3D
> > > >> ch is why GAL is a TP construct.
> > > >>
> > > >> my 2 cents
> > > >> D
> > > >
> > > > Dave,
> > > >
> > > > If GAL is broken for ECMP, which it is, then all TP OAM is
> broken.
> > > > If all it takes to fix it is simple then lets just fix it.
> > > >
> > > > This is what we'd have to do.
> > > >
> > > > =A01) Relax the requirement that GAL be at the bottom
> > > >
> > > > =A02) Have the ingress insert GAL in the stack immediately below
> the
> > > > =A0 =A0 label for which the measurement is made, keeping the rest o=
f
> the
> > > > =A0 =A0 label stack in place.
> > > >
> > > > The only thing the midpoing LSR at a multipath (LAG, link bundle
> for
> > > > MPLS) has to do is skip over the GAL when hashing, as if the GAL
> > > > wasn't there. =A0That will yield the same hash value and it will
> > > > preserve fate-sharing across multipath.
> > > >
> > > > I prefer that we fix things rather than complain that they are
> > > broken.
> > > >
> > > > Curtis
> > > > _______________________________________________
> > > > pwe3 mailing list
> > > > pwe3@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/pwe3
> > > >
> > >
> > >
> > >
> > > --
> > > - Sri
> > > _______________________________________________
> > > pwe3 mailing list
> > > pwe3@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pwe3


From Alexander.Vainshtein@ecitele.com  Thu Mar 31 02:33:00 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F0FF28C266 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:33:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.285
X-Spam-Level: 
X-Spam-Status: No, score=-2.285 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, J_CHICKENPOX_57=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 ba6OVIAcm-Cj for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 02:32:58 -0700 (PDT)
Received: from ilptbmg02.ecitele.com (ilptbmg02-out.ecitele.com [147.234.242.235]) by core3.amsl.com (Postfix) with ESMTP id 78C4E28C26C for <pwe3@ietf.org>; Thu, 31 Mar 2011 02:32:47 -0700 (PDT)
X-AuditID: 93eaf2e8-b7bb7ae000004cb7-36-4d944a3be317
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Brightmail Gateway) with SMTP id A2.31.19639.B3A449D4; Thu, 31 Mar 2011 11:32:44 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Thu, 31 Mar 2011 11:34:25 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Thu, 31 Mar 2011 11:34:15 +0200
Thread-Topic: [PWE3] GAL above and below the PW label
Thread-Index: AcvvhJf0AWxQRkQvTyWSRvALen5W2QAARrww
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D722D075EE@ILPTMAIL02.ecitele.com>
References: <4D92F5D3.6080609@pi.nu> <201103310703.p2V73Hrx045107@harbor.orleans.occnc.com> <AANLkTimwxBexevis2-5-vrGM-hA2APZeC0djwxUyV0jU@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D722D07565@ILPTMAIL02.ecitele.com> <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe@mail.gmail.com>
In-Reply-To: <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe@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="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 09:33:00 -0000

Sriganesh,
Please see inline below.

Regards,
     Sasha


> -----Original Message-----
> From: sriganeshkini@gmail.com [mailto:sriganeshkini@gmail.com] On
> Behalf Of Sriganesh Kini
> Sent: Thursday, March 31, 2011 11:18 AM
> To: Alexander Vainshtein
> Cc: curtis@occnc.com; pwe3@ietf.org
> Subject: Re: [PWE3] GAL above and below the PW label
>=20
> Sasha, that issue with VCCV Type-3 (without CW) is not addressed by
> the draft.=20
[[[Sasha]]] That is what I said:-(
> > Practically, is that a major issue ? Especially setting TTL
> > 1 for SS PW is possible I guess but would be some kind of serious
> operational oversight. Besides such a packet would fail some check
> along the path.
[[[Sasha]]] If you mean SS-PW, then the chance for an error(sending an OAM =
packet with TTL > 1
or sending a data packet with TTL =3D 1) is small and should be treated as =
an implementation bug.
With  dynamic MS-PWs, the number of segments of a MS-PW can change with tim=
e, so that the originally=20
Correct TTL setting would suddenly result in leakage of OAM packets out of =
the AC.
All this is described in detail in 6073.
>=20
> Also, what I heard at the mic regarding impl results is that it
> doesn't make sense to deprecate what is already deployed.
>=20
[[[Sasha]]] To the best of my recollection, what has been said at the mike =
is that you cannot
change optional CW usage to mandatory when you progress from PS to DS.
But, to the best of my understanding of the IETF process and practice, noth=
ing prevents us
from publishing a BCP document that would declare non-usage of the CW depre=
cated.
This would push the vendors to support it in their new boxes (SW upgrades),=
 and it would
be understood by the operators as a suggestion to transit to using the CW i=
f their equipment
supports it -- all that without outlawing non-usage of the CW.

> Note that CC Type 1 prevents ECMP (when FAT-PW is not available).
> Using GAL below PW also requires ECMP based on label hashing to ignore
> reserved labels.
>=20
> 2011/3/31 Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>:
> > Sriganesh, Curtis and all,
> > IMHO and FWIW I think that the only problem with VCCV Type 3 is the
> risk of OAM packets leaking out of T-PE towards the AC (if you
> accidentally set the TTL value too high). To the best of my
> understanding the offset proposal does not solve that - or did I miss
> something?
> >
> > One way to solve it is to use VCCV Type 1 (clean where applicable).
> > Another way would be by using GAL below the PW label (possible but
> messy). If the industry moves towards deprecating Ethernet PWs without
> CW, =A0it becomes completely unnecessary.
> >
> > My 2c,
> > =A0 =A0 Sasha
> >
> >
> >> -----Original Message-----
> >> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf
> Of
> >> Sriganesh Kini
> >> Sent: Thursday, March 31, 2011 10:09 AM
> >> To: curtis@occnc.com
> >> Cc: pwe3@ietf.org
> >> Subject: Re: [PWE3] GAL above and below the PW label
> >>
> >> All,
> >>
> >> Just an FYI that a proposal for fate-sharing PW OAM and data given
> in
> >> draft-kini-pwe3-inband-cc-offset
> >>
> >> Just to summarize the proposal.
> >> 1. It does not require GAL in PW. TTL expiry is used to alert the
> S/T-
> >> PE.
> >> 2. It is mainly applicable when CW is not used in the PW.
> >> 3. It uses a fixed offset (negotiated between PW endpoints) after
> the
> >> label stack before starting the OAM msg.
> >> 4. The bytes between the label-stack and the fixed offset is
> referred
> >> to as a pseudoflow header and is filled with byte-values (by the PE)
> >> that represent the flow for which OAM is desired. This helps PW OAM
> >> and data to fate-share even when the intermediate node looks beyond
> >> label stack to do multipath forwarding decisions.
> >>
> >>
> >> On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar
> <curtis@occnc.com>
> >> wrote:
> >> >
> >> > Loa, Dave, Sasha,
> >> >
> >> > I've snipped from various posts on the thread that Sasha started.
> >> =A0See
> >> > inline.
> >> >
> >> > In message <4D92F5D3.6080609@pi.nu>
> >> > Loa Andersson writes:
> >> >>
> >> >> All,
> >> >>
> >> >> missed a nuance in Sasha subject line.
> >> >>
> >> >> We have two issues
> >> >>
> >> >> - where the GAL is placed relative to the PW label, I =A0believe it
> is
> >> >> =A0 =A0necessary to have the GAL below the PW label.
> >> >>
> >> >> - whether the the GAL label needs to be bottom of stack or not,
> it
> >> >> =A0 =A0figure that this is really a discussion if it is possible to
> have
> >> >> =A0 =A0a FAT label below the GAL or not. I'm not sure =A0about my
> >> preferences
> >> >> =A0 =A0but I think it is possible.
> >> >>
> >> >> /Loa
> >> >
> >> > I agree with Loa's summary. =A0Not putting GAL at the bottom may
> >> confuse
> >> > some LSR, but putting it above the PW label is likely to be even
> more
> >> > problematic.
> >> >
> >> >
> >> > In message
> >>
> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson
> >> .se>
> >> > David Allan I writes:
> >> >>
> >> >> It does become a new behavior, GAL with S=3D3D0. However the
> >> combination of G=3D
> >> >> AL being top label at the S-PE and TTL being encoded in the PW
> label
> >> means =3D
> >> >> that fate sharing is broken at every S-PE. Life only gets a
> little
> >> more str=3D
> >> >> ange if there is a FAT label as well...
> >> >>
> >> >> That being said, GAL as bottom label is broken in any ECMP
> >> environment, whi=3D
> >> >> ch is why GAL is a TP construct.
> >> >>
> >> >> my 2 cents
> >> >> D
> >> >
> >> > Dave,
> >> >
> >> > If GAL is broken for ECMP, which it is, then all TP OAM is broken.
> >> > If all it takes to fix it is simple then lets just fix it.
> >> >
> >> > This is what we'd have to do.
> >> >
> >> > =A01) Relax the requirement that GAL be at the bottom
> >> >
> >> > =A02) Have the ingress insert GAL in the stack immediately below the
> >> > =A0 =A0 label for which the measurement is made, keeping the rest of
> the
> >> > =A0 =A0 label stack in place.
> >> >
> >> > The only thing the midpoing LSR at a multipath (LAG, link bundle
> for
> >> > MPLS) has to do is skip over the GAL when hashing, as if the GAL
> >> > wasn't there. =A0That will yield the same hash value and it will
> >> > preserve fate-sharing across multipath.
> >> >
> >> > I prefer that we fix things rather than complain that they are
> >> broken.
> >> >
> >> > Curtis
> >> > _______________________________________________
> >> > pwe3 mailing list
> >> > pwe3@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/pwe3
> >> >
> >>
> >>
> >>
> >> --
> >> - Sri
> >> _______________________________________________
> >> pwe3 mailing list
> >> pwe3@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pwe3
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> >
>=20
>=20
>=20
> --
> - Sri

From giles.heron@gmail.com  Thu Mar 31 04:25:17 2011
Return-Path: <giles.heron@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4F7F28C1D6 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 04:25:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.209
X-Spam-Level: 
X-Spam-Status: No, score=-3.209 tagged_above=-999 required=5 tests=[AWL=0.390,  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 pB-O2UdbI2ke for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 04:25:17 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id EC93F28C136 for <pwe3@ietf.org>; Thu, 31 Mar 2011 04:25:16 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1873275wwa.13 for <pwe3@ietf.org>; Thu, 31 Mar 2011 04:26:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:user-agent:date:subject:from:to:message-id :thread-topic:thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=w/f3lGjrSiM8SU2txt2UBZ+J6jCQ1xn3vu8p9DRbaqA=; b=M7amCan0ks+FS4Cq2C1wuSwaiqMCKPNqv16eKiDk1MZJ0IZtSuZrsGqOwDbcepyTib lDxDxm7GCjAYcer/7IW3h9UljUTyqCxgdTNuJ/1uxNS3ap2fTjUW7O4Cv91gNVikdRf1 Ds2rCS4tRVA15ATLjC28LkQs7HhviJCrUM/6k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=BtavpBxAhveIghqwVK/qXm9R1TEhEfwZHP4qgC94PIV2wvDCaaEQq5wXlk5w8QudVl AjwYqzCeoEv5ofHjBhkCA6Q9PUULY/VPcSk5YTkR40dgodPrIJNuYjRsTC5kuopFV4gZ OCFKkAgLYyDn7Ei/98ZmP1gzQ5dr5dWAEOBa8=
Received: by 10.227.39.66 with SMTP id f2mr2607102wbe.2.1301570815914; Thu, 31 Mar 2011 04:26:55 -0700 (PDT)
Received: from [10.61.106.177] (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id z13sm587893wbd.63.2011.03.31.04.26.53 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 31 Mar 2011 04:26:54 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.28.0.101117
Date: Thu, 31 Mar 2011 12:27:24 +0100
From: Giles Heron <giles.heron@gmail.com>
To: <stbryant@cisco.com>, <pwe3@ietf.org>
Message-ID: <C9BA23AC.7C00%giles.heron@gmail.com>
Thread-Topic: [PWE3] GAL above and below the PW label
Thread-Index: AcvvlptPR+no7KgHi0uaTzhOd/BMfA==
In-Reply-To: <4D94396B.40101@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 11:25:18 -0000

On 31/03/2011 09:20, "Stewart Bryant" <stbryant@cisco.com> wrote:

> On 30/03/2011 14:55, Greg Mirsky wrote:
>> Dear Sasha,
>> I believe that there should not be MS-PW that crosses TP and non-TP
>> domains. 
> That diminishes the generality of the design, which would in my view be
> a bad thing.

Agreed.  I'd expect the most common use case for TP is in the
access/aggregation.  So you might have an MS-PW with 3 segments:

MPLS TP <-> IP/MPLS <-> MPLS-TP.

Giles



From sriganeshkini@gmail.com  Thu Mar 31 04:37:17 2011
Return-Path: <sriganeshkini@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 353B028C12D for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 04:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.614
X-Spam-Level: 
X-Spam-Status: No, score=-2.614 tagged_above=-999 required=5 tests=[AWL=-0.237, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_57=0.6, 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 7U3MfLgN6vRr for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 04:37:16 -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 ECD9728C112 for <pwe3@ietf.org>; Thu, 31 Mar 2011 04:37:15 -0700 (PDT)
Received: by qwg5 with SMTP id 5so1651542qwg.31 for <pwe3@ietf.org>; Thu, 31 Mar 2011 04:38:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=Umn0OlAHBk9cebFBXYwEYRuABc11sPaOkIKgQzGkGeA=; b=IE45VYxNXc8ebFBHLxQBNuHE4laHDlXiYiTF0IrLlXodZKHR3M3e3WWt4DqEWFk3h6 DZR4vlcfVwCYxCJi6bTOTsOAy158QNdUSk9QKqAAQFQ+zrdnZ1kkzoewFvZBr9Y4Duie yC7RjviuNiqmR2ggrXqleDpAVKKMEe33hi5W8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=h9QRkIlO8JpOyVAHslhMcxfREVGlr5+AaI3eOAzikpEwiqb0zpclyhMD3YYWnghyAP A8pYE6eQVTMm+N575PI0yFoxd5VZ8WYufx17HZELvwKWdEaNUica1zUJlL05a0PJL5aN sYP7NNVgcrn7bAcqQFecavH0Z123Y+k/mVliY=
Received: by 10.229.1.93 with SMTP id 29mr2112309qce.66.1301571535167; Thu, 31 Mar 2011 04:38:55 -0700 (PDT)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.229.136.12 with HTTP; Thu, 31 Mar 2011 04:38:25 -0700 (PDT)
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D722D075EE@ILPTMAIL02.ecitele.com>
References: <4D92F5D3.6080609@pi.nu> <201103310703.p2V73Hrx045107@harbor.orleans.occnc.com> <AANLkTimwxBexevis2-5-vrGM-hA2APZeC0djwxUyV0jU@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D722D07565@ILPTMAIL02.ecitele.com> <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C76D722D075EE@ILPTMAIL02.ecitele.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Thu, 31 Mar 2011 04:38:25 -0700
X-Google-Sender-Auth: L7ZgsqZR8OOHhRTQucH-5SEiKfM
Message-ID: <AANLkTintVVmft+Uuv8-1acrLgahyzHy22kbKB2O=6kMk@mail.gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 11:37:17 -0000

Sasha,

Can you point to the text in RFC 6073 that in your interpretation
results in the number of segments in a PW dynamically changing but the
PE being unaware of it (and using the incorrect TTL value).

Thanks

2011/3/31 Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>:
> Sriganesh,
> Please see inline below.
>
> Regards,
> =A0 =A0 Sasha
>
>
>> -----Original Message-----
>> From: sriganeshkini@gmail.com [mailto:sriganeshkini@gmail.com] On
>> Behalf Of Sriganesh Kini
>> Sent: Thursday, March 31, 2011 11:18 AM
>> To: Alexander Vainshtein
>> Cc: curtis@occnc.com; pwe3@ietf.org
>> Subject: Re: [PWE3] GAL above and below the PW label
>>
>> Sasha, that issue with VCCV Type-3 (without CW) is not addressed by
>> the draft.
> [[[Sasha]]] That is what I said:-(
>> > Practically, is that a major issue ? Especially setting TTL
>> > 1 for SS PW is possible I guess but would be some kind of serious
>> operational oversight. Besides such a packet would fail some check
>> along the path.
> [[[Sasha]]] If you mean SS-PW, then the chance for an error(sending an OA=
M packet with TTL > 1
> or sending a data packet with TTL =3D 1) is small and should be treated a=
s an implementation bug.
> With =A0dynamic MS-PWs, the number of segments of a MS-PW can change with=
 time, so that the originally
> Correct TTL setting would suddenly result in leakage of OAM packets out o=
f the AC.
> All this is described in detail in 6073.
>>
>> Also, what I heard at the mic regarding impl results is that it
>> doesn't make sense to deprecate what is already deployed.
>>
> [[[Sasha]]] To the best of my recollection, what has been said at the mik=
e is that you cannot
> change optional CW usage to mandatory when you progress from PS to DS.
> But, to the best of my understanding of the IETF process and practice, no=
thing prevents us
> from publishing a BCP document that would declare non-usage of the CW dep=
recated.
> This would push the vendors to support it in their new boxes (SW upgrades=
), and it would
> be understood by the operators as a suggestion to transit to using the CW=
 if their equipment
> supports it -- all that without outlawing non-usage of the CW.
>
>> Note that CC Type 1 prevents ECMP (when FAT-PW is not available).
>> Using GAL below PW also requires ECMP based on label hashing to ignore
>> reserved labels.
>>
>> 2011/3/31 Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>:
>> > Sriganesh, Curtis and all,
>> > IMHO and FWIW I think that the only problem with VCCV Type 3 is the
>> risk of OAM packets leaking out of T-PE towards the AC (if you
>> accidentally set the TTL value too high). To the best of my
>> understanding the offset proposal does not solve that - or did I miss
>> something?
>> >
>> > One way to solve it is to use VCCV Type 1 (clean where applicable).
>> > Another way would be by using GAL below the PW label (possible but
>> messy). If the industry moves towards deprecating Ethernet PWs without
>> CW, =A0it becomes completely unnecessary.
>> >
>> > My 2c,
>> > =A0 =A0 Sasha
>> >
>> >
>> >> -----Original Message-----
>> >> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf
>> Of
>> >> Sriganesh Kini
>> >> Sent: Thursday, March 31, 2011 10:09 AM
>> >> To: curtis@occnc.com
>> >> Cc: pwe3@ietf.org
>> >> Subject: Re: [PWE3] GAL above and below the PW label
>> >>
>> >> All,
>> >>
>> >> Just an FYI that a proposal for fate-sharing PW OAM and data given
>> in
>> >> draft-kini-pwe3-inband-cc-offset
>> >>
>> >> Just to summarize the proposal.
>> >> 1. It does not require GAL in PW. TTL expiry is used to alert the
>> S/T-
>> >> PE.
>> >> 2. It is mainly applicable when CW is not used in the PW.
>> >> 3. It uses a fixed offset (negotiated between PW endpoints) after
>> the
>> >> label stack before starting the OAM msg.
>> >> 4. The bytes between the label-stack and the fixed offset is
>> referred
>> >> to as a pseudoflow header and is filled with byte-values (by the PE)
>> >> that represent the flow for which OAM is desired. This helps PW OAM
>> >> and data to fate-share even when the intermediate node looks beyond
>> >> label stack to do multipath forwarding decisions.
>> >>
>> >>
>> >> On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar
>> <curtis@occnc.com>
>> >> wrote:
>> >> >
>> >> > Loa, Dave, Sasha,
>> >> >
>> >> > I've snipped from various posts on the thread that Sasha started.
>> >> =A0See
>> >> > inline.
>> >> >
>> >> > In message <4D92F5D3.6080609@pi.nu>
>> >> > Loa Andersson writes:
>> >> >>
>> >> >> All,
>> >> >>
>> >> >> missed a nuance in Sasha subject line.
>> >> >>
>> >> >> We have two issues
>> >> >>
>> >> >> - where the GAL is placed relative to the PW label, I =A0believe i=
t
>> is
>> >> >> =A0 =A0necessary to have the GAL below the PW label.
>> >> >>
>> >> >> - whether the the GAL label needs to be bottom of stack or not,
>> it
>> >> >> =A0 =A0figure that this is really a discussion if it is possible t=
o
>> have
>> >> >> =A0 =A0a FAT label below the GAL or not. I'm not sure =A0about my
>> >> preferences
>> >> >> =A0 =A0but I think it is possible.
>> >> >>
>> >> >> /Loa
>> >> >
>> >> > I agree with Loa's summary. =A0Not putting GAL at the bottom may
>> >> confuse
>> >> > some LSR, but putting it above the PW label is likely to be even
>> more
>> >> > problematic.
>> >> >
>> >> >
>> >> > In message
>> >>
>> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson
>> >> .se>
>> >> > David Allan I writes:
>> >> >>
>> >> >> It does become a new behavior, GAL with S=3D3D0. However the
>> >> combination of G=3D
>> >> >> AL being top label at the S-PE and TTL being encoded in the PW
>> label
>> >> means =3D
>> >> >> that fate sharing is broken at every S-PE. Life only gets a
>> little
>> >> more str=3D
>> >> >> ange if there is a FAT label as well...
>> >> >>
>> >> >> That being said, GAL as bottom label is broken in any ECMP
>> >> environment, whi=3D
>> >> >> ch is why GAL is a TP construct.
>> >> >>
>> >> >> my 2 cents
>> >> >> D
>> >> >
>> >> > Dave,
>> >> >
>> >> > If GAL is broken for ECMP, which it is, then all TP OAM is broken.
>> >> > If all it takes to fix it is simple then lets just fix it.
>> >> >
>> >> > This is what we'd have to do.
>> >> >
>> >> > =A01) Relax the requirement that GAL be at the bottom
>> >> >
>> >> > =A02) Have the ingress insert GAL in the stack immediately below th=
e
>> >> > =A0 =A0 label for which the measurement is made, keeping the rest o=
f
>> the
>> >> > =A0 =A0 label stack in place.
>> >> >
>> >> > The only thing the midpoing LSR at a multipath (LAG, link bundle
>> for
>> >> > MPLS) has to do is skip over the GAL when hashing, as if the GAL
>> >> > wasn't there. =A0That will yield the same hash value and it will
>> >> > preserve fate-sharing across multipath.
>> >> >
>> >> > I prefer that we fix things rather than complain that they are
>> >> broken.
>> >> >
>> >> > Curtis
>> >> > _______________________________________________
>> >> > pwe3 mailing list
>> >> > pwe3@ietf.org
>> >> > https://www.ietf.org/mailman/listinfo/pwe3
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> - Sri
>> >> _______________________________________________
>> >> pwe3 mailing list
>> >> pwe3@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/pwe3
>> > _______________________________________________
>> > pwe3 mailing list
>> > pwe3@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pwe3
>> >
>>
>>
>>
>> --
>> - Sri
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>



--=20
- Sri

From curtis@occnc.com  Thu Mar 31 04:38:55 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDF353A6961 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 04:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.497
X-Spam-Level: 
X-Spam-Status: No, score=-2.497 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 jPAHqpQ0G6tA for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 04:38:54 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 010493A6947 for <pwe3@ietf.org>; Thu, 31 Mar 2011 04:38: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 p2VBeSfh083040; Thu, 31 Mar 2011 07:40:28 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103311140.p2VBeSfh083040@harbor.orleans.occnc.com>
To: Sriganesh Kini <sriganesh.kini@ericsson.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 31 Mar 2011 02:17:48 PDT." <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe@mail.gmail.com> 
Date: Thu, 31 Mar 2011 07:40:28 -0400
Sender: curtis@occnc.com
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 11:38:55 -0000

Sriganesh, Sasha, Loa, Dave,

Would you please not top post.  See inline.

Curtis

In message <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe@mail.gmail.com>
Sriganesh Kini writes:
>  
> Sasha, that issue with VCCV Type-3 (without CW) is not addressed by
> the draft. Practically, is that a major issue ? Especially setting TTL
> > 1 for SS PW is possible I guess but would be some kind of serious
> operational oversight. Besides such a packet would fail some check
> along the path.

End to end OAM should set TTL>1 and not use VCCV Type-3.  The T-PE may
not have reliable information to set TTL, so in MS-PW it might be
worth discouraging VCCV Type-3 except for use as a traceroute
capability or to address S-PEs by node distance along the path.

> Also, what I heard at the mic regarding impl results is that it
> doesn't make sense to deprecate what is already deployed.

Yes.  But VCCV Type-3 with MS-PW is not already deployed.

> Note that CC Type 1 prevents ECMP (when FAT-PW is not available).
> Using GAL below PW also requires ECMP based on label hashing to ignore
> reserved labels.

You don't want ECMP to hash on PW payload.  With CW and without
fat-pw, you don't get ECMP on a PW but you do get ECMP on an LSP
containing many PW.

> 2011/3/31 Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>:
> > Sriganesh, Curtis and all,
> > IMHO and FWIW I think that the only problem with VCCV Type 3 is the
> > risk of OAM packets leaking out of T-PE towards the AC (if you
> > accidentally set the TTL value too high). To the best of my
> > understanding the offset proposal does not solve that - or did I miss
> > something? 
> >
> > One way to solve it is to use VCCV Type 1 (clean where applicable).
> > Another way would be by using GAL below the PW label (possible but
> > messy). If the industry moves towards deprecating Ethernet PWs
> > without CW,  it becomes completely unnecessary. 
> >
> > My 2c,
> >     Sasha

This is the context suggesting a potential problem with VCCV Type 3.

> >> -----Original Message-----
> >> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> >> Sriganesh Kini
> >> Sent: Thursday, March 31, 2011 10:09 AM
> >> To: curtis@occnc.com
> >> Cc: pwe3@ietf.org
> >> Subject: Re: [PWE3] GAL above and below the PW label
> >>
> >> All,
> >>
> >> Just an FYI that a proposal for fate-sharing PW OAM and data given in
> >> draft-kini-pwe3-inband-cc-offset
> >>
> >> Just to summarize the proposal.
> >> 1. It does not require GAL in PW. TTL expiry is used to alert the S/T-
> >> PE.
> >> 2. It is mainly applicable when CW is not used in the PW.
> >> 3. It uses a fixed offset (negotiated between PW endpoints) after the
> >> label stack before starting the OAM msg.
> >> 4. The bytes between the label-stack and the fixed offset is referred
> >> to as a pseudoflow header and is filled with byte-values (by the PE)
> >> that represent the flow for which OAM is desired. This helps PW OAM
> >> and data to fate-share even when the intermediate node looks beyond
> >> label stack to do multipath forwarding decisions.
> >>
> >>
> >> On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar <curtis@occnc.com>
> >> wrote:
> >> >
> >> > Loa, Dave, Sasha,
> >> >
> >> > I've snipped from various posts on the thread that Sasha started.
> >>  See
> >> > inline.
> >> >
> >> > In message <4D92F5D3.6080609@pi.nu>
> >> > Loa Andersson writes:
> >> >>
> >> >> All,
> >> >>
> >> >> missed a nuance in Sasha subject line.
> >> >>
> >> >> We have two issues
> >> >>
> >> >> - where the GAL is placed relative to the PW label, I  believe it is
> >> >>    necessary to have the GAL below the PW label.
> >> >>
> >> >> - whether the the GAL label needs to be bottom of stack or not, it
> >> >>    figure that this is really a discussion if it is possible to have
> >> >>    a FAT label below the GAL or not. I'm not sure  about my
> >> preferences
> >> >>    but I think it is possible.
> >> >>
> >> >> /Loa
> >> >
> >> > I agree with Loa's summary.  Not putting GAL at the bottom may
> >> confuse
> >> > some LSR, but putting it above the PW label is likely to be even more
> >> > problematic.
> >> >
> >> >
> >> > In message
> >> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson
> >> .se>
> >> > David Allan I writes:
> >> >>
> >> >> It does become a new behavior, GAL with S=3D0. However the
> >> combination of G=
> >> >> AL being top label at the S-PE and TTL being encoded in the PW label
> >> means =
> >> >> that fate sharing is broken at every S-PE. Life only gets a little
> >> more str=
> >> >> ange if there is a FAT label as well...
> >> >>
> >> >> That being said, GAL as bottom label is broken in any ECMP
> >> environment, whi=
> >> >> ch is why GAL is a TP construct.
> >> >>
> >> >> my 2 cents
> >> >> D
> >> >
> >> > Dave,
> >> >
> >> > If GAL is broken for ECMP, which it is, then all TP OAM is broken.
> >> > If all it takes to fix it is simple then lets just fix it.
> >> >
> >> > This is what we'd have to do.
> >> >
> >> >  1) Relax the requirement that GAL be at the bottom
> >> >
> >> >  2) Have the ingress insert GAL in the stack immediately below the
> >> >     label for which the measurement is made, keeping the rest of the
> >> >     label stack in place.
> >> >
> >> > The only thing the midpoing LSR at a multipath (LAG, link bundle for
> >> > MPLS) has to do is skip over the GAL when hashing, as if the GAL
> >> > wasn't there.  That will yield the same hash value and it will
> >> > preserve fate-sharing across multipath.
> >> >
> >> > I prefer that we fix things rather than complain that they are
> >> broken.
> >> >
> >> > Curtis
> >> > _______________________________________________
> >> > pwe3 mailing list
> >> > pwe3@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/pwe3
> >> >
> >>
> >>
> >>
> >> --
> >> - Sri
> >> _______________________________________________
> >> pwe3 mailing list
> >> pwe3@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pwe3
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> >
>  
>  
>  
> -- 
> - Sri
>  
>  

From curtis@occnc.com  Thu Mar 31 04:47:59 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 126D33A6B0E for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 04:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.099, 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 A0cPVtBed5tf for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 04:47:57 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 251103A6947 for <pwe3@ietf.org>; Thu, 31 Mar 2011 04:47:57 -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 p2VBnWQQ083145; Thu, 31 Mar 2011 07:49:32 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103311149.p2VBnWQQ083145@harbor.orleans.occnc.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 31 Mar 2011 11:25:12 +0200." <A3C5DF08D38B6049839A6F553B331C76D722D075E4@ILPTMAIL02.ecitele.com> 
Date: Thu, 31 Mar 2011 07:49:32 -0400
Sender: curtis@occnc.com
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 11:47:59 -0000

In message <A3C5DF08D38B6049839A6F553B331C76D722D075E4@ILPTMAIL02.ecitele.com>
Alexander Vainshtein writes:
>  
> Curtis,
>  
> The results of the PWE3 survey (it is difficult to say how
> representative it really is) seem to indicate that ability to support
> CW in the Ethernet PW encapsulation is quite common (13-14 out of 17
> respondents) and reasonably used (8 out of 17 respondents).

Yes.  I personally would have liked to require CW.  Some operators
have indicated a preference for no CW, understanding that it won't
work for multipath, but will work in metro/access or small networks.

> This survey does not provide any information about using GAL with
> PWs. Maybe we should extend the survey to learn that?  My expectation,
> not based on any facts, is that no one has been using it at the
> moment:-).

I doubt anyone has implemented GAL with PW already.

> So if the choice is between fixing an old bug at the root (by
> deprecating PW encapsulations without CW) or adding a new patch (GAL
> in the PW) for the same purpose, I clearly prefer the first option.

Realistically we not be able to require CW at this point.  If we
could, I'd be in favor of doing so.  If not, then we are stuck with
GAL to provide one good method which will work fine with or without CW.


> Regards,
>      Sasha

Curtis


> > -----Original Message-----
> > From: curtis@occnc.com [mailto:curtis@occnc.com]
> > Sent: Thursday, March 31, 2011 11:17 AM
> > To: Alexander Vainshtein
> > Cc: Sriganesh Kini; curtis@occnc.com; pwe3@ietf.org
> > Subject: Re: [PWE3] GAL above and below the PW label
> > 
> > 
> > In message
> > <A3C5DF08D38B6049839A6F553B331C76D722D07565@ILPTMAIL02.ecitele.com>
> > Alexander Vainshtein writes:
> > >
> > > Sriganesh, Curtis and all,
> > >
> > > IMHO and FWIW I think that the only problem with VCCV Type 3 is the
> > > risk of OAM packets leaking out of T-PE towards the AC (if you
> > > accidentally set the TTL value too high). To the best of my
> > > understanding the offset proposal does not solve that - or did I miss
> > > something?
> > 
> > That can be fixed by looking at the next label (if there is one) before
> > forwarding at PW egress to the AC.  The implementation already has to
> > make a similar chack on every packet if CW is used, but looking after
> > the S=1 label entry.  If CW is used it would be wise to do both checks
> > (be liberal in what you accept and careful in what you forward).
> > 
> > > One way to solve it is to use VCCV Type 1 (clean where applicable).
> > > Another way would be by using GAL below the PW label (possible but
> > > messy). If the industry moves towards deprecating Ethernet PWs
> > without
> > > CW, it becomes completely unnecessary.
> > 
> > I agree with your last sentence but I don't know that non-CW can be
> > depricated.
> > 
> > > My 2c,
> > >      Sasha
> > 
> > Curtis
> > 
> > 
> > > > -----Original Message-----
> > > > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> > Behalf Of
> > > > Sriganesh Kini
> > > > Sent: Thursday, March 31, 2011 10:09 AM
> > > > To: curtis@occnc.com
> > > > Cc: pwe3@ietf.org
> > > > Subject: Re: [PWE3] GAL above and below the PW label
> > > >
> > > > All,
> > > >
> > > > Just an FYI that a proposal for fate-sharing PW OAM and data given
> > in
> > > > draft-kini-pwe3-inband-cc-offset
> > > >
> > > > Just to summarize the proposal.
> > > > 1. It does not require GAL in PW. TTL expiry is used to alert the
> > S/T-
> > > > PE.
> > > > 2. It is mainly applicable when CW is not used in the PW.
> > > > 3. It uses a fixed offset (negotiated between PW endpoints) after
> > the
> > > > label stack before starting the OAM msg.
> > > > 4. The bytes between the label-stack and the fixed offset is
> > referred
> > > > to as a pseudoflow header and is filled with byte-values (by the
> > PE)
> > > > that represent the flow for which OAM is desired. This helps PW OAM
> > > > and data to fate-share even when the intermediate node looks beyond
> > > > label stack to do multipath forwarding decisions.
> > > >
> > > >
> > > > On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar
> > <curtis@occnc.com>
> > > > wrote:
> > > > >
> > > > > Loa, Dave, Sasha,
> > > > >
> > > > > I've snipped from various posts on the thread that Sasha started.
> > > >  See
> > > > > inline.
> > > > >
> > > > > In message <4D92F5D3.6080609@pi.nu>
> > > > > Loa Andersson writes:
> > > > >>
> > > > >> All,
> > > > >>
> > > > >> missed a nuance in Sasha subject line.
> > > > >>
> > > > >> We have two issues
> > > > >>
> > > > >> - where the GAL is placed relative to the PW label, I  believe
> > it is
> > > > >>    necessary to have the GAL below the PW label.
> > > > >>
> > > > >> - whether the the GAL label needs to be bottom of stack or not,
> > it
> > > > >>    figure that this is really a discussion if it is possible to
> > have
> > > > >>    a FAT label below the GAL or not. I'm not sure  about my
> > > > preferences
> > > > >>    but I think it is possible.
> > > > >>
> > > > >> /Loa
> > > > >
> > > > > I agree with Loa's summary.  Not putting GAL at the bottom may
> > > > confuse
> > > > > some LSR, but putting it above the PW label is likely to be even
> > more
> > > > > problematic.
> > > > >
> > > > >
> > > > > In message
> > > >
> > <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson
> > > > .se>
> > > > > David Allan I writes:
> > > > >>
> > > > >> It does become a new behavior, GAL with S=3D0. However the
> > > > combination of G=
> > > > >> AL being top label at the S-PE and TTL being encoded in the PW
> > label
> > > > means =
> > > > >> that fate sharing is broken at every S-PE. Life only gets a
> > little
> > > > more str=
> > > > >> ange if there is a FAT label as well...
> > > > >>
> > > > >> That being said, GAL as bottom label is broken in any ECMP
> > > > environment, whi=
> > > > >> ch is why GAL is a TP construct.
> > > > >>
> > > > >> my 2 cents
> > > > >> D
> > > > >
> > > > > Dave,
> > > > >
> > > > > If GAL is broken for ECMP, which it is, then all TP OAM is
> > broken.
> > > > > If all it takes to fix it is simple then lets just fix it.
> > > > >
> > > > > This is what we'd have to do.
> > > > >
> > > > >  1) Relax the requirement that GAL be at the bottom
> > > > >
> > > > >  2) Have the ingress insert GAL in the stack immediately below
> > the
> > > > >     label for which the measurement is made, keeping the rest of
> > the
> > > > >     label stack in place.
> > > > >
> > > > > The only thing the midpoing LSR at a multipath (LAG, link bundle
> > for
> > > > > MPLS) has to do is skip over the GAL when hashing, as if the GAL
> > > > > wasn't there.  That will yield the same hash value and it will
> > > > > preserve fate-sharing across multipath.
> > > > >
> > > > > I prefer that we fix things rather than complain that they are
> > > > broken.
> > > > >
> > > > > Curtis
> > > > > _______________________________________________
> > > > > pwe3 mailing list
> > > > > pwe3@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/pwe3
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > - Sri
> > > > _______________________________________________
> > > > pwe3 mailing list
> > > > pwe3@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/pwe3

From curtis@occnc.com  Thu Mar 31 05:16:44 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8435228C0DB for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 05:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 yrjD-Zg+UEIB for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 05:16:43 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 890DC3A6767 for <pwe3@ietf.org>; Thu, 31 Mar 2011 05:16:43 -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 p2VCIGFd083577; Thu, 31 Mar 2011 08:18:16 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103311218.p2VCIGFd083577@harbor.orleans.occnc.com>
To: Greg Mirsky <gregimirsky@gmail.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 31 Mar 2011 00:33:02 PDT." <AANLkTi=VQQdXL-avxbK0_R9EssbzWdQP-Fmh8Nyhvqq4@mail.gmail.com> 
Date: Thu, 31 Mar 2011 08:18:16 -0400
Sender: curtis@occnc.com
Cc: pwe3 <pwe3@ietf.org>, Martini <lmartini@cisco.com>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 12:16:44 -0000

In message <AANLkTi=VQQdXL-avxbK0_R9EssbzWdQP-Fmh8Nyhvqq4@mail.gmail.com>
Greg Mirsky writes:
>  
> Dear Sasha,
> would your argument illustrate that use of GAL with PW label not only in
> MPLS-TP but in non-TP MPLS PW is strongly problematic? Should we leave RFC
> 5586 as is?
>  
> Regards,
> Greg


Greg,

His argument is that specifying that PW can be used for MPLS-TP only
or MPLS only would be a violation of the requirement for a common data
set.

There is no technical problem with use of GAL in a mixed TP and non-TP
MS-PW as long as the requirement that GAL be at BOS is relaxed.  There
may be a political problem in relaxing that restriction.

Curtis


> On Wed, Mar 30, 2011 at 7:10 AM, Alexander Vainshtein <
> Alexander.Vainshtein@ecitele.com> wrote:
>  
> > Dear Greg,
> >
> > Please see some comments inline below.
> >
> >
> >
> > Regards,
> >
> >      Sasha
> >
> >
> >
> > *From:* Greg Mirsky [mailto:gregimirsky@gmail.com]
> > *Sent:* Wednesday, March 30, 2011 3:56 PM
> > *To:* Alexander Vainshtein
> > *Cc:* David Allan I; pwe3; Luca@core3.amsl.com; Martini
> > *Subject:* Re: [PWE3] GAL above and below the PW label
> >
> >
> >
> > Dear Sasha,
> > I believe that there should not be MS-PW that crosses TP and non-TP
> > domains.
> >
> > *[[[Sasha]]] I do not see any technical reasons to disallow that.*
> >
> > GAL might be used in each domain under different rules.
> >
> > *[[[Sasha]]] I believe that this would violate the requirement for the
> > common data plane of MPLS and MPLS-TP.*
> >
> > If we strongly recommend that rule, then anyone not following it, at
> > his/her free will and risk, just might be shooting themselves in a foot.
> >
> > Regards,
> > Greg
 

From curtis@occnc.com  Thu Mar 31 05:23:54 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24B103A6AFA for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 05:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.51
X-Spam-Level: 
X-Spam-Status: No, score=-2.51 tagged_above=-999 required=5 tests=[AWL=0.089,  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 dr6pLxluZlUu for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 05:23:52 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id E09D63A6B12 for <pwe3@ietf.org>; Thu, 31 Mar 2011 05:23:51 -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 p2VCPP4n083693; Thu, 31 Mar 2011 08:25:25 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103311225.p2VCPP4n083693@harbor.orleans.occnc.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 31 Mar 2011 09:34:57 +0200." <A3C5DF08D38B6049839A6F553B331C76D722D07531@ILPTMAIL02.ecitele.com> 
Date: Thu, 31 Mar 2011 08:25:25 -0400
Sender: curtis@occnc.com
Cc: pwe3 <pwe3@ietf.org>, Martini <lmartini@cisco.com>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 12:23:54 -0000

In message <A3C5DF08D38B6049839A6F553B331C76D722D07531@ILPTMAIL02.ecitele.com>
Alexander Vainshtein writes:
>  
> Dear Greg,
>  
> Yes I think we should leave 5586 "as it is" - or clean it up removing
> somew= hat mysterious comments regarding non-TP usages.
>  
> Regards,
>      Sasha

Sasha,

What text is that?

In RFC 5586 I found:

   Also note that the GAL and ACH are applicable to MPLS and PWs in
   general.  This document specifies general mechanism and uses MPLS-TP
   as an example application.  The application of the GAL and ACH to
   other specific MPLS uses is outside the scope of this document.

Did you mean the second sentence?

   In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
   Concatenated Segments of LSPs, and with Sections, and MUST NOT be
   used with PWs.  It MUST always be at the bottom of the label stack
   (i.e., S bit set to 1).  However, in other MPLS environments, this
   document places no restrictions on where the GAL may appear within
   the label stack or its use with PWs.  Where the GAL is at the bottom
   of the label stack (i.e., S bit set to 1), then it MUST always be
   followed by an ACH.

Since this text indicates that "However, in other MPLS environments,
this document places no restrictions on where the GAL may appear
within the label stack or its use with PWs", we have a violation of
the requirement that there be one data plane for TP and non-TP MPLS.

If we want to maximize incompatibility, we can leave it as is (and
expect vendors to provide and option to ignore the restriction and
providers to use it).  :-)

Curtis


> From: Greg Mirsky [mailto:gregimirsky@gmail.com]
> Sent: Thursday, March 31, 2011 9:33 AM
> To: Alexander Vainshtein
> Cc: David Allan I; pwe3; Martini
> Subject: Re: [PWE3] GAL above and below the PW label
>  
> Dear Sasha,
> would your argument illustrate that use of GAL with PW label not only in MP=
> LS-TP but in non-TP MPLS PW is strongly problematic? Should we leave RFC 55=
> 86 as is?
>  
> Regards,
> Greg
> On Wed, Mar 30, 2011 at 7:10 AM, Alexander Vainshtein <Alexander.Vainshtein=
> @ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
> Dear Greg,
> Please see some comments inline below.
>  
> Regards,
>      Sasha
>  
> From: Greg Mirsky [mailto:gregimirsky@gmail.com<mailto:gregimirsky@gmail.co=
> m>]
> Sent: Wednesday, March 30, 2011 3:56 PM
> To: Alexander Vainshtein
> Cc: David Allan I; pwe3; Luca@core3.amsl.com<mailto:Luca@core3.amsl.com>; M=
> artini
> Subject: Re: [PWE3] GAL above and below the PW label
>  
> Dear Sasha,
> I believe that there should not be MS-PW that crosses TP and non-TP domains=
> .
> [[[Sasha]]] I do not see any technical reasons to disallow that.
> GAL might be used in each domain under different rules.
> [[[Sasha]]] I believe that this would violate the requirement for the commo=
> n data plane of MPLS and MPLS-TP.
> If we strongly recommend that rule, then anyone not following it, at his/he=
> r free will and risk, just might be shooting themselves in a foot.
>  
> Regards,
> Greg
> On Wed, Mar 30, 2011 at 1:56 AM, Alexander Vainshtein <Alexander.Vainshtein=
> @ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
> Dave,
> GAL may be a TP construct, but, IMO, MS-PWs (if not the other things) will =
> easily break the demarcation lines between TP and non-TP areas.
>  
> If we stick with GAL being an MPLS-TP construct we should, IMHO, drop the a=
> ttempts to use it with Ws.
>  
> Regards,
>      Sasha
>  
> From: David Allan I [mailto:david.i.allan@ericsson.com<mailto:david.i.allan=
> @ericsson.com>]
> Sent: Wednesday, March 30, 2011 10:52 AM
> To: Alexander Vainshtein; Thomas Nadeau; Luca Martini
> Cc: pwe3
> Subject: RE: GAL above and below the PW label
>  
> It does become a new behavior, GAL with S=3D0. However the combination of G=
> AL being top label at the S-PE and TTL being encoded in the PW label means =
> that fate sharing is broken at every S-PE. Life only gets a little more str=
> ange if there is a FAT label as well...
>  
> That being said, GAL as bottom label is broken in any ECMP environment, whi=
> ch is why GAL is a TP construct.
>  
> my 2 cents
> D
>  
> ________________________________
> From: pwe3-bounces@ietf.org<mailto:pwe3-bounces@ietf.org> [mailto:pwe3-boun=
> ces@ietf.org<mailto:pwe3-bounces@ietf.org>] On Behalf Of Alexander Vainshte=
> in
> Sent: Wednesday, March 30, 2011 10:37 AM
> To: Thomas Nadeau; Luca Martini
> Cc: pwe3
> Subject: [PWE3] GAL above and below the PW label
> Tom, Luca and all,
> I would like to clarify - again - my position regarding GAL above the PW la=
> bel.
> I think that, other issues notwithstanding, it would create an issue if use=
> d with MS-PWs:
>  
> *         GAL would be exposed at each S-PE (making a presumably end-to-end=
>  OAM message to be intercepted)
>  
> *         What is even worse, there is no rule for forwarding the packet th=
> at has been intercepted due to an exposed GAL (until you count the statemen=
> t in 5586 requesting that a packet MUST NOT be ever forwarded based on GAL:=
> )).  Hence it would be perfectly valid just to drop such a packet at the fi=
> rst S-PE it crosses...
> This said, I still  do not think using GAL below the PW label is a good ide=
> a either. But this is a different story...
>  
> Regards,
>      Sasha

From sriganeshkini@gmail.com  Thu Mar 31 05:39:00 2011
Return-Path: <sriganeshkini@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3469A28C0E4 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 05:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.884
X-Spam-Level: 
X-Spam-Status: No, score=-2.884 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 js-WHRXBIZQm for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 05:38:59 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id CB91428C0D6 for <pwe3@ietf.org>; Thu, 31 Mar 2011 05:38:58 -0700 (PDT)
Received: by qyk7 with SMTP id 7so1557834qyk.10 for <pwe3@ietf.org>; Thu, 31 Mar 2011 05:40:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=AELbcnnY/+B107Thazg1UKIwXJyL80db2b6QNZPA+dw=; b=mjnzmcej/7vliF3dHGUFdccNh0lh83Qw5JhOVJ/XqhnsdWaQ1EVSXHBfY2txKvgKx+ 2bUWEoyjz6kWS27ifLs929OpIANkfJppLb6y4kLkvKbxBLRirUJeVNpcE1/Ly5VFNjIh 7lzvBSL5aKhNm3ZW5fSc5PbEat8z5QIqTTarg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=exFPbVYZkn0tdqbW9pufa0bYBRYoVx9OMtlRakPYWrELxfxkFpbZ3ApyX0bI293WBy /mHAfkED97OaKoaFurDQOAIM293wGzndlfclG9RrPemKxXCBug+zy5ZZF7Q/pehINgpi 2KWTVBQl3Pkbjvo1kVjabYKeyeMg0bLq+wKP4=
Received: by 10.229.1.93 with SMTP id 29mr2162509qce.66.1301575237121; Thu, 31 Mar 2011 05:40:37 -0700 (PDT)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.229.136.12 with HTTP; Thu, 31 Mar 2011 05:40:07 -0700 (PDT)
In-Reply-To: <201103311140.p2VBeSfh083040@harbor.orleans.occnc.com>
References: <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe@mail.gmail.com> <201103311140.p2VBeSfh083040@harbor.orleans.occnc.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Thu, 31 Mar 2011 05:40:07 -0700
X-Google-Sender-Auth: pfEo3eLAFW34rmPrOyIWphwhARM
Message-ID: <AANLkTi=fuSg1iBy+jz0SvsfNpGrd-=32p+KMV7Q=hOSv@mail.gmail.com>
To: curtis@occnc.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 12:39:00 -0000

See inline

On Thu, Mar 31, 2011 at 4:40 AM, Curtis Villamizar <curtis@occnc.com> wrote=
:
>
> Sriganesh, Sasha, Loa, Dave,
>
> Would you please not top post. =A0See inline.
>
> Curtis
>
> In message <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe@mail.gmail.com>
> Sriganesh Kini writes:
>>
>> Sasha, that issue with VCCV Type-3 (without CW) is not addressed by
>> the draft. Practically, is that a major issue ? Especially setting TTL
>> > 1 for SS PW is possible I guess but would be some kind of serious
>> operational oversight. Besides such a packet would fail some check
>> along the path.
>
> End to end OAM should set TTL>1 and not use VCCV Type-3. =A0The T-PE may
> not have reliable information to set TTL, so in MS-PW it might be
> worth discouraging VCCV Type-3 except for use as a traceroute
> capability or to address S-PEs by node distance along the path.

If there is indeed a concern of TTL exceeding number of segments (with
Type-3 and no CW), the same concern would apply when tracing. So
tracing would be impossible.

>
>> Also, what I heard at the mic regarding impl results is that it
>> doesn't make sense to deprecate what is already deployed.
>
> Yes. =A0But VCCV Type-3 with MS-PW is not already deployed.

I am not aware of the survey addressing this.

>
>> Note that CC Type 1 prevents ECMP (when FAT-PW is not available).
>> Using GAL below PW also requires ECMP based on label hashing to ignore
>> reserved labels.
>
> You don't want ECMP to hash on PW payload. =A0With CW and without
> fat-pw, you don't get ECMP on a PW but you do get ECMP on an LSP
> containing many PW.

When the PW payload is IP, the hashing it for ECMP is useful (If the
payload is not IP then use CW). FAT-PW may not be present in all
deployments.

>
>> 2011/3/31 Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>:
>> > Sriganesh, Curtis and all,
>> > IMHO and FWIW I think that the only problem with VCCV Type 3 is the
>> > risk of OAM packets leaking out of T-PE towards the AC (if you
>> > accidentally set the TTL value too high). To the best of my
>> > understanding the offset proposal does not solve that - or did I miss
>> > something?
>> >
>> > One way to solve it is to use VCCV Type 1 (clean where applicable).
>> > Another way would be by using GAL below the PW label (possible but
>> > messy). If the industry moves towards deprecating Ethernet PWs
>> > without CW, =A0it becomes completely unnecessary.
>> >
>> > My 2c,
>> > =A0 =A0 Sasha
>
> This is the context suggesting a potential problem with VCCV Type 3.
>
>> >> -----Original Message-----
>> >> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf =
Of
>> >> Sriganesh Kini
>> >> Sent: Thursday, March 31, 2011 10:09 AM
>> >> To: curtis@occnc.com
>> >> Cc: pwe3@ietf.org
>> >> Subject: Re: [PWE3] GAL above and below the PW label
>> >>
>> >> All,
>> >>
>> >> Just an FYI that a proposal for fate-sharing PW OAM and data given in
>> >> draft-kini-pwe3-inband-cc-offset
>> >>
>> >> Just to summarize the proposal.
>> >> 1. It does not require GAL in PW. TTL expiry is used to alert the S/T=
-
>> >> PE.
>> >> 2. It is mainly applicable when CW is not used in the PW.
>> >> 3. It uses a fixed offset (negotiated between PW endpoints) after the
>> >> label stack before starting the OAM msg.
>> >> 4. The bytes between the label-stack and the fixed offset is referred
>> >> to as a pseudoflow header and is filled with byte-values (by the PE)
>> >> that represent the flow for which OAM is desired. This helps PW OAM
>> >> and data to fate-share even when the intermediate node looks beyond
>> >> label stack to do multipath forwarding decisions.
>> >>
>> >>
>> >> On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar <curtis@occnc.com=
>
>> >> wrote:
>> >> >
>> >> > Loa, Dave, Sasha,
>> >> >
>> >> > I've snipped from various posts on the thread that Sasha started.
>> >> =A0See
>> >> > inline.
>> >> >
>> >> > In message <4D92F5D3.6080609@pi.nu>
>> >> > Loa Andersson writes:
>> >> >>
>> >> >> All,
>> >> >>
>> >> >> missed a nuance in Sasha subject line.
>> >> >>
>> >> >> We have two issues
>> >> >>
>> >> >> - where the GAL is placed relative to the PW label, I =A0believe i=
t is
>> >> >> =A0 =A0necessary to have the GAL below the PW label.
>> >> >>
>> >> >> - whether the the GAL label needs to be bottom of stack or not, it
>> >> >> =A0 =A0figure that this is really a discussion if it is possible t=
o have
>> >> >> =A0 =A0a FAT label below the GAL or not. I'm not sure =A0about my
>> >> preferences
>> >> >> =A0 =A0but I think it is possible.
>> >> >>
>> >> >> /Loa
>> >> >
>> >> > I agree with Loa's summary. =A0Not putting GAL at the bottom may
>> >> confuse
>> >> > some LSR, but putting it above the PW label is likely to be even mo=
re
>> >> > problematic.
>> >> >
>> >> >
>> >> > In message
>> >> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericss=
on
>> >> .se>
>> >> > David Allan I writes:
>> >> >>
>> >> >> It does become a new behavior, GAL with S=3D3D0. However the
>> >> combination of G=3D
>> >> >> AL being top label at the S-PE and TTL being encoded in the PW lab=
el
>> >> means =3D
>> >> >> that fate sharing is broken at every S-PE. Life only gets a little
>> >> more str=3D
>> >> >> ange if there is a FAT label as well...
>> >> >>
>> >> >> That being said, GAL as bottom label is broken in any ECMP
>> >> environment, whi=3D
>> >> >> ch is why GAL is a TP construct.
>> >> >>
>> >> >> my 2 cents
>> >> >> D
>> >> >
>> >> > Dave,
>> >> >
>> >> > If GAL is broken for ECMP, which it is, then all TP OAM is broken.
>> >> > If all it takes to fix it is simple then lets just fix it.
>> >> >
>> >> > This is what we'd have to do.
>> >> >
>> >> > =A01) Relax the requirement that GAL be at the bottom
>> >> >
>> >> > =A02) Have the ingress insert GAL in the stack immediately below th=
e
>> >> > =A0 =A0 label for which the measurement is made, keeping the rest o=
f the
>> >> > =A0 =A0 label stack in place.
>> >> >
>> >> > The only thing the midpoing LSR at a multipath (LAG, link bundle fo=
r
>> >> > MPLS) has to do is skip over the GAL when hashing, as if the GAL
>> >> > wasn't there. =A0That will yield the same hash value and it will
>> >> > preserve fate-sharing across multipath.
>> >> >
>> >> > I prefer that we fix things rather than complain that they are
>> >> broken.
>> >> >
>> >> > Curtis
>> >> > _______________________________________________
>> >> > pwe3 mailing list
>> >> > pwe3@ietf.org
>> >> > https://www.ietf.org/mailman/listinfo/pwe3
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> - Sri
>> >> _______________________________________________
>> >> pwe3 mailing list
>> >> pwe3@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/pwe3
>> > _______________________________________________
>> > pwe3 mailing list
>> > pwe3@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pwe3
>> >
>>
>>
>>
>> --
>> - Sri
>>
>>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>



--=20
- Sri

From curtis@occnc.com  Thu Mar 31 05:47:55 2011
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 965EA3A6B12 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 05:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.216
X-Spam-Level: 
X-Spam-Status: No, score=-2.216 tagged_above=-999 required=5 tests=[AWL=-0.217, 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 e3XEIR6FQJkT for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 05:47:54 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 2033C28C0EB for <pwe3@ietf.org>; Thu, 31 Mar 2011 05:47:54 -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 p2VCnU9Y085450; Thu, 31 Mar 2011 08:49:30 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103311249.p2VCnU9Y085450@harbor.orleans.occnc.com>
To: Sriganesh Kini <sriganesh.kini@ericsson.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Thu, 31 Mar 2011 05:40:07 PDT." <AANLkTi=fuSg1iBy+jz0SvsfNpGrd-=32p+KMV7Q=hOSv@mail.gmail.com> 
Date: Thu, 31 Mar 2011 08:49:30 -0400
Sender: curtis@occnc.com
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 12:47:55 -0000

In message <AANLkTi=fuSg1iBy+jz0SvsfNpGrd-=32p+KMV7Q=hOSv@mail.gmail.com>
Sriganesh Kini writes:
>  
> See inline
>  
> On Thu, Mar 31, 2011 at 4:40 AM, Curtis Villamizar <curtis@occnc.com> wrote:
> >
> > Sriganesh, Sasha, Loa, Dave,
> >
> > Would you please not top post.  See inline.
> >
> > Curtis
> >
> > In message <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe@mail.gmail.com>
> > Sriganesh Kini writes:
> >>
> >> Sasha, that issue with VCCV Type-3 (without CW) is not addressed by
> >> the draft. Practically, is that a major issue ? Especially setting TTL
> >> > 1 for SS PW is possible I guess but would be some kind of serious
> >> operational oversight. Besides such a packet would fail some check
> >> along the path.
> >
> > End to end OAM should set TTL>1 and not use VCCV Type-3.  The T-PE may
> > not have reliable information to set TTL, so in MS-PW it might be
> > worth discouraging VCCV Type-3 except for use as a traceroute
> > capability or to address S-PEs by node distance along the path.
>  
> If there is indeed a concern of TTL exceeding number of segments (with
> Type-3 and no CW), the same concern would apply when tracing. So
> tracing would be impossible.

traceroute stops when it hits the egress.

> >> Also, what I heard at the mic regarding impl results is that it
> >> doesn't make sense to deprecate what is already deployed.
> >
> > Yes.  But VCCV Type-3 with MS-PW is not already deployed.
>  
> I am not aware of the survey addressing this.

AFAIK Type-1 is being used, but I could be wrong.  Maybe someone who
has implemented and knows of a deployment or someone who has deployed
can reply so we don't need another survey.

> >> Note that CC Type 1 prevents ECMP (when FAT-PW is not available).
> >> Using GAL below PW also requires ECMP based on label hashing to ignore
> >> reserved labels.
> >
> > You don't want ECMP to hash on PW payload.  With CW and without
> > fat-pw, you don't get ECMP on a PW but you do get ECMP on an LSP
> > containing many PW.
>  
> When the PW payload is IP, the hashing it for ECMP is useful (If the
> payload is not IP then use CW). FAT-PW may not be present in all
> deployments.

I really don't know that any PW are carrying IP.  That was not in the
survey.  L3VPN would be carrying IP.

> >> 2011/3/31 Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>:
> >> > Sriganesh, Curtis and all,
> >> > IMHO and FWIW I think that the only problem with VCCV Type 3 is the
> >> > risk of OAM packets leaking out of T-PE towards the AC (if you
> >> > accidentally set the TTL value too high). To the best of my
> >> > understanding the offset proposal does not solve that - or did I miss
> >> > something?
> >> >
> >> > One way to solve it is to use VCCV Type 1 (clean where applicable).
> >> > Another way would be by using GAL below the PW label (possible but
> >> > messy). If the industry moves towards deprecating Ethernet PWs
> >> > without CW,  it becomes completely unnecessary.
> >> >
> >> > My 2c,
> >> >     Sasha
> >
> > This is the context suggesting a potential problem with VCCV Type 3.
> >
> >> >> -----Original Message-----
> >> >> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> >> >> Sriganesh Kini
> >> >> Sent: Thursday, March 31, 2011 10:09 AM
> >> >> To: curtis@occnc.com
> >> >> Cc: pwe3@ietf.org
> >> >> Subject: Re: [PWE3] GAL above and below the PW label
> >> >>
> >> >> All,
> >> >>
> >> >> Just an FYI that a proposal for fate-sharing PW OAM and data given in
> >> >> draft-kini-pwe3-inband-cc-offset
> >> >>
> >> >> Just to summarize the proposal.
> >> >> 1. It does not require GAL in PW. TTL expiry is used to alert the S/T-
> >> >> PE.
> >> >> 2. It is mainly applicable when CW is not used in the PW.
> >> >> 3. It uses a fixed offset (negotiated between PW endpoints) after the
> >> >> label stack before starting the OAM msg.
> >> >> 4. The bytes between the label-stack and the fixed offset is referred
> >> >> to as a pseudoflow header and is filled with byte-values (by the PE)
> >> >> that represent the flow for which OAM is desired. This helps PW OAM
> >> >> and data to fate-share even when the intermediate node looks beyond
> >> >> label stack to do multipath forwarding decisions.
> >> >>
> >> >>
> >> >> On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar <curtis@occnc.com>
> >> >> wrote:
> >> >> >
> >> >> > Loa, Dave, Sasha,
> >> >> >
> >> >> > I've snipped from various posts on the thread that Sasha started.
> >> >>  See
> >> >> > inline.
> >> >> >
> >> >> > In message <4D92F5D3.6080609@pi.nu>
> >> >> > Loa Andersson writes:
> >> >> >>
> >> >> >> All,
> >> >> >>
> >> >> >> missed a nuance in Sasha subject line.
> >> >> >>
> >> >> >> We have two issues
> >> >> >>
> >> >> >> - where the GAL is placed relative to the PW label, I  believe it is
> >> >> >>    necessary to have the GAL below the PW label.
> >> >> >>
> >> >> >> - whether the the GAL label needs to be bottom of stack or not, it
> >> >> >>    figure that this is really a discussion if it is possible to have
> >> >> >>    a FAT label below the GAL or not. I'm not sure  about my
> >> >> preferences
> >> >> >>    but I think it is possible.
> >> >> >>
> >> >> >> /Loa
> >> >> >
> >> >> > I agree with Loa's summary.  Not putting GAL at the bottom may
> >> >> confuse
> >> >> > some LSR, but putting it above the PW label is likely to be even more
> >> >> > problematic.
> >> >> >
> >> >> >
> >> >> > In message
> >> >> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.ericsson
> >> >> .se>
> >> >> > David Allan I writes:
> >> >> >>
> >> >> >> It does become a new behavior, GAL with S=3D0. However the
> >> >> combination of G=
> >> >> >> AL being top label at the S-PE and TTL being encoded in the PW label
> >> >> means =
> >> >> >> that fate sharing is broken at every S-PE. Life only gets a little
> >> >> more str=
> >> >> >> ange if there is a FAT label as well...
> >> >> >>
> >> >> >> That being said, GAL as bottom label is broken in any ECMP
> >> >> environment, whi=
> >> >> >> ch is why GAL is a TP construct.
> >> >> >>
> >> >> >> my 2 cents
> >> >> >> D
> >> >> >
> >> >> > Dave,
> >> >> >
> >> >> > If GAL is broken for ECMP, which it is, then all TP OAM is broken.
> >> >> > If all it takes to fix it is simple then lets just fix it.
> >> >> >
> >> >> > This is what we'd have to do.
> >> >> >
> >> >> >  1) Relax the requirement that GAL be at the bottom
> >> >> >
> >> >> >  2) Have the ingress insert GAL in the stack immediately below the
> >> >> >     label for which the measurement is made, keeping the rest of the
> >> >> >     label stack in place.
> >> >> >
> >> >> > The only thing the midpoing LSR at a multipath (LAG, link bundle for
> >> >> > MPLS) has to do is skip over the GAL when hashing, as if the GAL
> >> >> > wasn't there.  That will yield the same hash value and it will
> >> >> > preserve fate-sharing across multipath.
> >> >> >
> >> >> > I prefer that we fix things rather than complain that they are
> >> >> broken.
> >> >> >
> >> >> > Curtis
> >> >> > _______________________________________________
> >> >> > pwe3 mailing list
> >> >> > pwe3@ietf.org
> >> >> > https://www.ietf.org/mailman/listinfo/pwe3
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> - Sri
> >> >> _______________________________________________
> >> >> pwe3 mailing list
> >> >> pwe3@ietf.org
> >> >> https://www.ietf.org/mailman/listinfo/pwe3
> >> > _______________________________________________
> >> > pwe3 mailing list
> >> > pwe3@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/pwe3
> >> >
> >>
> >>
> >>
> >> --
> >> - Sri
> >>
> >>
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3

From sriganeshkini@gmail.com  Thu Mar 31 06:34:47 2011
Return-Path: <sriganeshkini@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4335528C141 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 06:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.595
X-Spam-Level: 
X-Spam-Status: No, score=-2.595 tagged_above=-999 required=5 tests=[AWL=-0.218, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=0.6, 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 Af1ELnw9CRKd for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 06:34:46 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id D77EF3A6AB2 for <pwe3@ietf.org>; Thu, 31 Mar 2011 06:34:45 -0700 (PDT)
Received: by qyk29 with SMTP id 29so3341118qyk.10 for <pwe3@ietf.org>; Thu, 31 Mar 2011 06:36:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=A+vOatCHfOjZApN0E5yyinhuXIRZkYjTT7i6/+y5GRI=; b=OFt+lkWg+fovMGSRWve+7FsSjiqfq272VYgTC7TlwERM0yzysYgCBAsCB5m3odhT2N 0EyO74FE/X6wILVxasY1LH8mMxD6D392XLS8GRfnqIIqGnJxX2Yf6PTJzDN+9wZtq6dd w/NhWavvVJM7iCESsjJF38Id8YgUq+z95WMxg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=CvmfIfuKmyWajzqum1g4zmHnattN67oLkrAHwMKMO45NU6eQ9B4lC0or/0Coow2naZ d5nqj+Ulcwo221mbSGynICRBrHshs8ppnDeGatxlk2Mu4ot75YHcVk39xPW1szv9WbUN A9+fjVEqqWZyJO4pcmbHXXv2ydnhHLn3r9dXk=
Received: by 10.229.78.22 with SMTP id i22mr2222245qck.28.1301578585142; Thu, 31 Mar 2011 06:36:25 -0700 (PDT)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.229.136.12 with HTTP; Thu, 31 Mar 2011 06:35:55 -0700 (PDT)
In-Reply-To: <201103311249.p2VCnU9Y085450@harbor.orleans.occnc.com>
References: <AANLkTi=fuSg1iBy+jz0SvsfNpGrd-=32p+KMV7Q=hOSv@mail.gmail.com> <201103311249.p2VCnU9Y085450@harbor.orleans.occnc.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Thu, 31 Mar 2011 06:35:55 -0700
X-Google-Sender-Auth: w0r8pBJbxgV0XEdRNeFGbdgrSfQ
Message-ID: <AANLkTin2-kqMtPraKsdqKHv5VbJpC_JQrwmnjwHw7OXc@mail.gmail.com>
To: curtis@occnc.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 13:34:47 -0000

inline

On Thu, Mar 31, 2011 at 5:49 AM, Curtis Villamizar <curtis@occnc.com> wrote=
:
>
> In message <AANLkTi=3DfuSg1iBy+jz0SvsfNpGrd-=3D32p+KMV7Q=3DhOSv@mail.gmai=
l.com>
> Sriganesh Kini writes:
>>
>> See inline
>>
>> On Thu, Mar 31, 2011 at 4:40 AM, Curtis Villamizar <curtis@occnc.com> wr=
ote:
>> >
>> > Sriganesh, Sasha, Loa, Dave,
>> >
>> > Would you please not top post. =A0See inline.
>> >
>> > Curtis
>> >
>> > In message <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe@mail.gmail.c=
om>
>> > Sriganesh Kini writes:
>> >>
>> >> Sasha, that issue with VCCV Type-3 (without CW) is not addressed by
>> >> the draft. Practically, is that a major issue ? Especially setting TT=
L
>> >> > 1 for SS PW is possible I guess but would be some kind of serious
>> >> operational oversight. Besides such a packet would fail some check
>> >> along the path.
>> >
>> > End to end OAM should set TTL>1 and not use VCCV Type-3. =A0The T-PE m=
ay
>> > not have reliable information to set TTL, so in MS-PW it might be
>> > worth discouraging VCCV Type-3 except for use as a traceroute
>> > capability or to address S-PEs by node distance along the path.
>>
>> If there is indeed a concern of TTL exceeding number of segments (with
>> Type-3 and no CW), the same concern would apply when tracing. So
>> tracing would be impossible.
>
> traceroute stops when it hits the egress.

That is exactly the point I am trying to make. Why would the TTL from
that information not be reliable for other OAM operations ?

>
>> >> Also, what I heard at the mic regarding impl results is that it
>> >> doesn't make sense to deprecate what is already deployed.
>> >
>> > Yes. =A0But VCCV Type-3 with MS-PW is not already deployed.
>>
>> I am not aware of the survey addressing this.
>
> AFAIK Type-1 is being used, but I could be wrong. =A0Maybe someone who
> has implemented and knows of a deployment or someone who has deployed
> can reply so we don't need another survey.
>
>> >> Note that CC Type 1 prevents ECMP (when FAT-PW is not available).
>> >> Using GAL below PW also requires ECMP based on label hashing to ignor=
e
>> >> reserved labels.
>> >
>> > You don't want ECMP to hash on PW payload. =A0With CW and without
>> > fat-pw, you don't get ECMP on a PW but you do get ECMP on an LSP
>> > containing many PW.
>>
>> When the PW payload is IP, the hashing it for ECMP is useful (If the
>> payload is not IP then use CW). FAT-PW may not be present in all
>> deployments.
>
> I really don't know that any PW are carrying IP. =A0That was not in the
> survey. =A0L3VPN would be carrying IP.

IPLS would be another case.

>
>> >> 2011/3/31 Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>:
>> >> > Sriganesh, Curtis and all,
>> >> > IMHO and FWIW I think that the only problem with VCCV Type 3 is the
>> >> > risk of OAM packets leaking out of T-PE towards the AC (if you
>> >> > accidentally set the TTL value too high). To the best of my
>> >> > understanding the offset proposal does not solve that - or did I mi=
ss
>> >> > something?
>> >> >
>> >> > One way to solve it is to use VCCV Type 1 (clean where applicable).
>> >> > Another way would be by using GAL below the PW label (possible but
>> >> > messy). If the industry moves towards deprecating Ethernet PWs
>> >> > without CW, =A0it becomes completely unnecessary.
>> >> >
>> >> > My 2c,
>> >> > =A0 =A0 Sasha
>> >
>> > This is the context suggesting a potential problem with VCCV Type 3.
>> >
>> >> >> -----Original Message-----
>> >> >> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Beha=
lf Of
>> >> >> Sriganesh Kini
>> >> >> Sent: Thursday, March 31, 2011 10:09 AM
>> >> >> To: curtis@occnc.com
>> >> >> Cc: pwe3@ietf.org
>> >> >> Subject: Re: [PWE3] GAL above and below the PW label
>> >> >>
>> >> >> All,
>> >> >>
>> >> >> Just an FYI that a proposal for fate-sharing PW OAM and data given=
 in
>> >> >> draft-kini-pwe3-inband-cc-offset
>> >> >>
>> >> >> Just to summarize the proposal.
>> >> >> 1. It does not require GAL in PW. TTL expiry is used to alert the =
S/T-
>> >> >> PE.
>> >> >> 2. It is mainly applicable when CW is not used in the PW.
>> >> >> 3. It uses a fixed offset (negotiated between PW endpoints) after =
the
>> >> >> label stack before starting the OAM msg.
>> >> >> 4. The bytes between the label-stack and the fixed offset is refer=
red
>> >> >> to as a pseudoflow header and is filled with byte-values (by the P=
E)
>> >> >> that represent the flow for which OAM is desired. This helps PW OA=
M
>> >> >> and data to fate-share even when the intermediate node looks beyon=
d
>> >> >> label stack to do multipath forwarding decisions.
>> >> >>
>> >> >>
>> >> >> On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar <curtis@occnc.=
com>
>> >> >> wrote:
>> >> >> >
>> >> >> > Loa, Dave, Sasha,
>> >> >> >
>> >> >> > I've snipped from various posts on the thread that Sasha started=
.
>> >> >> =A0See
>> >> >> > inline.
>> >> >> >
>> >> >> > In message <4D92F5D3.6080609@pi.nu>
>> >> >> > Loa Andersson writes:
>> >> >> >>
>> >> >> >> All,
>> >> >> >>
>> >> >> >> missed a nuance in Sasha subject line.
>> >> >> >>
>> >> >> >> We have two issues
>> >> >> >>
>> >> >> >> - where the GAL is placed relative to the PW label, I =A0believ=
e it is
>> >> >> >> =A0 =A0necessary to have the GAL below the PW label.
>> >> >> >>
>> >> >> >> - whether the the GAL label needs to be bottom of stack or not,=
 it
>> >> >> >> =A0 =A0figure that this is really a discussion if it is possibl=
e to have
>> >> >> >> =A0 =A0a FAT label below the GAL or not. I'm not sure =A0about =
my
>> >> >> preferences
>> >> >> >> =A0 =A0but I think it is possible.
>> >> >> >>
>> >> >> >> /Loa
>> >> >> >
>> >> >> > I agree with Loa's summary. =A0Not putting GAL at the bottom may
>> >> >> confuse
>> >> >> > some LSR, but putting it above the PW label is likely to be even=
 more
>> >> >> > problematic.
>> >> >> >
>> >> >> >
>> >> >> > In message
>> >> >> <60C093A41B5E45409A19D42CF7786DFD51D5310B53@EUSAACMS0703.eamcs.eri=
csson
>> >> >> .se>
>> >> >> > David Allan I writes:
>> >> >> >>
>> >> >> >> It does become a new behavior, GAL with S=3D3D0. However the
>> >> >> combination of G=3D
>> >> >> >> AL being top label at the S-PE and TTL being encoded in the PW =
label
>> >> >> means =3D
>> >> >> >> that fate sharing is broken at every S-PE. Life only gets a lit=
tle
>> >> >> more str=3D
>> >> >> >> ange if there is a FAT label as well...
>> >> >> >>
>> >> >> >> That being said, GAL as bottom label is broken in any ECMP
>> >> >> environment, whi=3D
>> >> >> >> ch is why GAL is a TP construct.
>> >> >> >>
>> >> >> >> my 2 cents
>> >> >> >> D
>> >> >> >
>> >> >> > Dave,
>> >> >> >
>> >> >> > If GAL is broken for ECMP, which it is, then all TP OAM is broke=
n.
>> >> >> > If all it takes to fix it is simple then lets just fix it.
>> >> >> >
>> >> >> > This is what we'd have to do.
>> >> >> >
>> >> >> > =A01) Relax the requirement that GAL be at the bottom
>> >> >> >
>> >> >> > =A02) Have the ingress insert GAL in the stack immediately below=
 the
>> >> >> > =A0 =A0 label for which the measurement is made, keeping the res=
t of the
>> >> >> > =A0 =A0 label stack in place.
>> >> >> >
>> >> >> > The only thing the midpoing LSR at a multipath (LAG, link bundle=
 for
>> >> >> > MPLS) has to do is skip over the GAL when hashing, as if the GAL
>> >> >> > wasn't there. =A0That will yield the same hash value and it will
>> >> >> > preserve fate-sharing across multipath.
>> >> >> >
>> >> >> > I prefer that we fix things rather than complain that they are
>> >> >> broken.
>> >> >> >
>> >> >> > Curtis
>> >> >> > _______________________________________________
>> >> >> > pwe3 mailing list
>> >> >> > pwe3@ietf.org
>> >> >> > https://www.ietf.org/mailman/listinfo/pwe3
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> - Sri
>> >> >> _______________________________________________
>> >> >> pwe3 mailing list
>> >> >> pwe3@ietf.org
>> >> >> https://www.ietf.org/mailman/listinfo/pwe3
>> >> > _______________________________________________
>> >> > pwe3 mailing list
>> >> > pwe3@ietf.org
>> >> > https://www.ietf.org/mailman/listinfo/pwe3
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> - Sri
>> >>
>> >>
>> >
>> > _______________________________________________
>> > pwe3 mailing list
>> > pwe3@ietf.org
>> > https://www.ietf.org/mailman/listinfo/pwe3
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>



--=20
- Sri

From venkatflex@gmail.com  Thu Mar 31 12:43:54 2011
Return-Path: <venkatflex@gmail.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A42DD28C0FB for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 12:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.276
X-Spam-Level: 
X-Spam-Status: No, score=-3.276 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, 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 mnSPla6urW+s for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 12:43:52 -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 BD4823A6949 for <pwe3@ietf.org>; Thu, 31 Mar 2011 12:43:51 -0700 (PDT)
Received: by vws12 with SMTP id 12so2531002vws.31 for <pwe3@ietf.org>; Thu, 31 Mar 2011 12:45:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=F1rgl9wFbsdaT3WWR2Lu0ANoREVntd9qtCD7bgbSIzE=; b=mAIQCOIPCf/rsIWPQM06Eys/EErxqpXwRc/o1E9eT0bvjRybjFmr4krDhr2GWzakvU njLXy7V0EwSmFuj5Dx3u4ya+bDyCTIVSqF1Pv6vSHI9nygQi75Fr1U/1PK9VPIDWY0bi EtYwUzB/LEKGjBjAjVo6z1ox1MlBMVH6vSKtU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=EdjETF9Fi2YqyPCmmsprlkJuwfp+j+1Kh+7KGzCCu9lay/ZvjORzx3asqTokCpPG1b 2/v6yF5CA9oJm8t7UeQftlCVAVNneXiZ4JPGsdaB/FnsAtbNiRPfaaoV8PSQSUsXSX1h HAbtihn9QzTAVbcThkiFPFhz0XqL3znHJM/DA=
MIME-Version: 1.0
Received: by 10.52.92.161 with SMTP id cn1mr4175304vdb.253.1301600731169; Thu, 31 Mar 2011 12:45:31 -0700 (PDT)
Received: by 10.52.164.230 with HTTP; Thu, 31 Mar 2011 12:45:31 -0700 (PDT)
Date: Thu, 31 Mar 2011 15:45:31 -0400
Message-ID: <AANLkTi=ZirXML6gepT2pJGXgmxi3Y4C-X8aT1uxMGThO@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: sriganesh.kini@ericsson.com, pwe3@ietf.org
Content-Type: multipart/alternative; boundary=20cf3071ced8388408049fcc8931
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 19:43:54 -0000

--20cf3071ced8388408049fcc8931
Content-Type: text/plain; charset=ISO-8859-1

Hi,

>> > You don't want ECMP to hash on PW payload.  With CW and without
>> > fat-pw, you don't get ECMP on a PW but you do get ECMP on an LSP
>> > containing many PW.
>>
>> When the PW payload is IP, the hashing it for ECMP is useful (If the
>> payload is not IP then use CW). FAT-PW may not be present in all
>> deployments.
>
> I really don't know that any PW are carrying IP.  That was not in the
> survey.  L3VPN would be carrying IP.

Why are we very much concerned about the ECMP in MPLS-TP networks?
I think, as per the RFC-5960,

   Equal-Cost Multi-Path (ECMP) load-balancing MUST NOT be performed on
   an MPLS-TP LSP.


Thanks,
Venkat.
Re: [PWE3] GAL above and below the PW label
------------------------------

   - *To*: curtis at occnc.com <curtis@DOMAIN.HIDDEN>
   - *Subject*: Re: [PWE3] GAL above and below the PW label
   - *From*: Sriganesh Kini <sriganesh.kini at
ericsson.com<sriganesh.kini@DOMAIN.HIDDEN>
   >
   - *Date*: Thu, 31 Mar 2011 06:35:55 -0700
   - *Cc*: "pwe3 at ietf.org <pwe3@DOMAIN.HIDDEN>" <pwe3 at
ietf.org<pwe3@DOMAIN.HIDDEN>
   >
   - *Delivered-to*: pwe3 at core3.amsl.com <pwe3@DOMAIN.HIDDEN>
   - *Dkim-signature*: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com;
   s=gamma;
   h=domainkey-signature:mime-version:sender:in-reply-to:references:from
   :date:x-google-sender-auth:message-id:subject:to:cc:content-type
   :content-transfer-encoding; bh=A+vOatCHfOjZApN0E5yyinhuXIRZkYjTT7i6/+y5GRI=;
   b=OFt+lkWg+fovMGSRWve+7FsSjiqfq272VYgTC7TlwERM0yzysYgCBAsCB5m3odhT2N
   0EyO74FE/X6wILVxasY1LH8mMxD6D392XLS8GRfnqIIqGnJxX2Yf6PTJzDN+9wZtq6dd
   w/NhWavvVJM7iCESsjJF38Id8YgUq+z95WMxg=
   - *Domainkey-signature*: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
   h=mime-version:sender:in-reply-to:references:from:date
   :x-google-sender-auth:message-id:subject:to:cc:content-type
   :content-transfer-encoding;
   b=CvmfIfuKmyWajzqum1g4zmHnattN67oLkrAHwMKMO45NU6eQ9B4lC0or/0Coow2naZ
   d5nqj+Ulcwo221mbSGynICRBrHshs8ppnDeGatxlk2Mu4ot75YHcVk39xPW1szv9WbUN
   A9+fjVEqqWZyJO4pcmbHXXv2ydnhHLn3r9dXk=
   - *In-reply-to*: <201103311249.p2VCnU9Y085450 at
harbor.orleans.occnc.com<201103311249.p2VCnU9Y085450@DOMAIN.HIDDEN>
   >
   - *List-archive*: <http://www.ietf.org/mail-archive/web/pwe3>
   - *List-help*:
<mailto:pwe3-request@ietf.org?subject=help<pwe3-request@ietf.org?subject=help>
   >
   - *List-id*: Pseudo Wires Edge to Edge <pwe3.ietf.org>
   - *List-post*: <mailto:pwe3@ietf.org <pwe3@ietf.org>>
   - *List-subscribe*: <https://www.ietf.org/mailman/listinfo/pwe3>, <
   mailto:pwe3-request@ietf.org?subject=subscribe<pwe3-request@ietf.org?subject=subscribe>
   >
   - *List-unsubscribe*: <https://www.ietf.org/mailman/listinfo/pwe3>, <
   mailto:pwe3-request@ietf.org?subject=unsubscribe<pwe3-request@ietf.org?subject=unsubscribe>
   >
   - *References*: <AANLkTi=fuSg1iBy+jz0SvsfNpGrd-=32p+KMV7Q=hOSv at
   mail.gmail.com<AANLkTi%3DfuSg1iBy%2Bjz0SvsfNpGrd-%3D32p%2BKMV7Q%3DhOSv@DOMAIN.HIDDEN>>
   <201103311249.p2VCnU9Y085450 at
harbor.orleans.occnc.com<201103311249.p2VCnU9Y085450@DOMAIN.HIDDEN>
   >
   - *Sender*: sriganeshkini at gmail.com <sriganeshkini@DOMAIN.HIDDEN>

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

inline

On Thu, Mar 31, 2011 at 5:49 AM, Curtis Villamizar <curtis at occnc.com> wrote:
>
> In message <AANLkTi=fuSg1iBy+jz0SvsfNpGrd-=32p+KMV7Q=hOSv at mail.gmail.com>
> Sriganesh Kini writes:
>>
>> See inline
>>
>> On Thu, Mar 31, 2011 at 4:40 AM, Curtis Villamizar <curtis at occnc.com> wrote:
>> >
>> > Sriganesh, Sasha, Loa, Dave,
>> >
>> > Would you please not top post.  See inline.
>> >
>> > Curtis
>> >
>> > In message <AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe at mail.gmail.com>
>> > Sriganesh Kini writes:
>> >>
>> >> Sasha, that issue with VCCV Type-3 (without CW) is not addressed by
>> >> the draft. Practically, is that a major issue ? Especially setting TTL
>> >> > 1 for SS PW is possible I guess but would be some kind of serious
>> >> operational oversight. Besides such a packet would fail some check
>> >> along the path.
>> >
>> > End to end OAM should set TTL>1 and not use VCCV Type-3.  The T-PE may
>> > not have reliable information to set TTL, so in MS-PW it might be
>> > worth discouraging VCCV Type-3 except for use as a traceroute
>> > capability or to address S-PEs by node distance along the path.
>>
>> If there is indeed a concern of TTL exceeding number of segments (with
>> Type-3 and no CW), the same concern would apply when tracing. So
>> tracing would be impossible.
>
> traceroute stops when it hits the egress.

That is exactly the point I am trying to make. Why would the TTL from
that information not be reliable for other OAM operations ?

>
>> >> Also, what I heard at the mic regarding impl results is that it
>> >> doesn't make sense to deprecate what is already deployed.
>> >
>> > Yes.  But VCCV Type-3 with MS-PW is not already deployed.
>>
>> I am not aware of the survey addressing this.
>
> AFAIK Type-1 is being used, but I could be wrong.  Maybe someone who
> has implemented and knows of a deployment or someone who has deployed
> can reply so we don't need another survey.
>
>> >> Note that CC Type 1 prevents ECMP (when FAT-PW is not available).
>> >> Using GAL below PW also requires ECMP based on label hashing to ignore
>> >> reserved labels.
>> >
>> > You don't want ECMP to hash on PW payload.  With CW and without
>> > fat-pw, you don't get ECMP on a PW but you do get ECMP on an LSP
>> > containing many PW.
>>
>> When the PW payload is IP, the hashing it for ECMP is useful (If the
>> payload is not IP then use CW). FAT-PW may not be present in all
>> deployments.
>
> I really don't know that any PW are carrying IP.  That was not in the
> survey.  L3VPN would be carrying IP.

IPLS would be another case.

>
>> >> 2011/3/31 Alexander Vainshtein <Alexander.Vainshtein at ecitele.com>:
>> >> > Sriganesh, Curtis and all,
>> >> > IMHO and FWIW I think that the only problem with VCCV Type 3 is the
>> >> > risk of OAM packets leaking out of T-PE towards the AC (if you
>> >> > accidentally set the TTL value too high). To the best of my
>> >> > understanding the offset proposal does not solve that - or did I miss
>> >> > something?
>> >> >
>> >> > One way to solve it is to use VCCV Type 1 (clean where applicable).
>> >> > Another way would be by using GAL below the PW label (possible but
>> >> > messy). If the industry moves towards deprecating Ethernet PWs
>> >> > without CW,  it becomes completely unnecessary.
>> >> >
>> >> > My 2c,
>> >> >     Sasha
>> >
>> > This is the context suggesting a potential problem with VCCV Type 3.
>> >
>> >> >> -----Original Message-----
>> >> >> From: pwe3-bounces at ietf.org [mailto:pwe3-bounces <pwe3-bounces> at ietf.org] On Behalf Of
>> >> >> Sriganesh Kini
>> >> >> Sent: Thursday, March 31, 2011 10:09 AM
>> >> >> To: curtis at occnc.com
>> >> >> Cc: pwe3 at ietf.org
>> >> >> Subject: Re: [PWE3] GAL above and below the PW label
>> >> >>
>> >> >> All,
>> >> >>
>> >> >> Just an FYI that a proposal for fate-sharing PW OAM and data given in
>> >> >> draft-kini-pwe3-inband-cc-offset
>> >> >>
>> >> >> Just to summarize the proposal.
>> >> >> 1. It does not require GAL in PW. TTL expiry is used to alert the S/T-
>> >> >> PE.
>> >> >> 2. It is mainly applicable when CW is not used in the PW.
>> >> >> 3. It uses a fixed offset (negotiated between PW endpoints) after the
>> >> >> label stack before starting the OAM msg.
>> >> >> 4. The bytes between the label-stack and the fixed offset is referred
>> >> >> to as a pseudoflow header and is filled with byte-values (by the PE)
>> >> >> that represent the flow for which OAM is desired. This helps PW OAM
>> >> >> and data to fate-share even when the intermediate node looks beyond
>> >> >> label stack to do multipath forwarding decisions.
>> >> >>
>> >> >>
>> >> >> On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villamizar <curtis at occnc.com>
>> >> >> wrote:
>> >> >> >
>> >> >> > Loa, Dave, Sasha,
>> >> >> >
>> >> >> > I've snipped from various posts on the thread that Sasha started.
>> >> >>  See
>> >> >> > inline.
>> >> >> >
>> >> >> > In message <4D92F5D3.6080609 at pi.nu>
>> >> >> > Loa Andersson writes:
>> >> >> >>
>> >> >> >> All,
>> >> >> >>
>> >> >> >> missed a nuance in Sasha subject line.
>> >> >> >>
>> >> >> >> We have two issues
>> >> >> >>
>> >> >> >> - where the GAL is placed relative to the PW label, I  believe it is
>> >> >> >>    necessary to have the GAL below the PW label.
>> >> >> >>
>> >> >> >> - whether the the GAL label needs to be bottom of stack or not, it
>> >> >> >>    figure that this is really a discussion if it is possible to have
>> >> >> >>    a FAT label below the GAL or not. I'm not sure  about my
>> >> >> preferences
>> >> >> >>    but I think it is possible.
>> >> >> >>
>> >> >> >> /Loa
>> >> >> >
>> >> >> > I agree with Loa's summary.  Not putting GAL at the bottom may
>> >> >> confuse
>> >> >> > some LSR, but putting it above the PW label is likely to be even more
>> >> >> > problematic.
>> >> >> >
>> >> >> >
>> >> >> > In message
>> >> >> <60C093A41B5E45409A19D42CF7786DFD51D5310B53 at EUSAACMS0703.eamcs.ericsson
>> >> >> .se>
>> >> >> > David Allan I writes:
>> >> >> >>
>> >> >> >> It does become a new behavior, GAL with S=3D0. However the
>> >> >> combination of G=
>> >> >> >> AL being top label at the S-PE and TTL being encoded in the PW label
>> >> >> means =
>> >> >> >> that fate sharing is broken at every S-PE. Life only gets a little
>> >> >> more str=
>> >> >> >> ange if there is a FAT label as well...
>> >> >> >>
>> >> >> >> That being said, GAL as bottom label is broken in any ECMP
>> >> >> environment, whi=
>> >> >> >> ch is why GAL is a TP construct.
>> >> >> >>
>> >> >> >> my 2 cents
>> >> >> >> D
>> >> >> >
>> >> >> > Dave,
>> >> >> >
>> >> >> > If GAL is broken for ECMP, which it is, then all TP OAM is broken.
>> >> >> > If all it takes to fix it is simple then lets just fix it.
>> >> >> >
>> >> >> > This is what we'd have to do.
>> >> >> >
>> >> >> >  1) Relax the requirement that GAL be at the bottom
>> >> >> >
>> >> >> >  2) Have the ingress insert GAL in the stack immediately below the
>> >> >> >     label for which the measurement is made, keeping the rest of the
>> >> >> >     label stack in place.
>> >> >> >
>> >> >> > The only thing the midpoing LSR at a multipath (LAG, link bundle for
>> >> >> > MPLS) has to do is skip over the GAL when hashing, as if the GAL
>> >> >> > wasn't there.  That will yield the same hash value and it will
>> >> >> > preserve fate-sharing across multipath.
>> >> >> >
>> >> >> > I prefer that we fix things rather than complain that they are
>> >> >> broken.
>> >> >> >
>> >> >> > Curtis
>> >> >> > _______________________________________________
>> >> >> > pwe3 mailing list
>> >> >> > pwe3 at ietf.org
>> >> >> > https://www.ietf.org/mailman/listinfo/pwe3
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> - Sri
>> >> >> _______________________________________________
>> >> >> pwe3 mailing list
>> >> >> pwe3 at ietf.org
>> >> >> https://www.ietf.org/mailman/listinfo/pwe3
>> >> > _______________________________________________
>> >> > pwe3 mailing list
>> >> > pwe3 at ietf.org
>> >> > https://www.ietf.org/mailman/listinfo/pwe3
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> - Sri
>> >>
>> >>

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

<h1 style=3D"font-family: &#39;Times New Roman&#39;; font-size: medium; ">H=
i,</h1><div><span class=3D"Apple-style-span" style=3D"font-size: medium; ">=
<pre style=3D"white-space: pre-wrap; word-wrap: break-word; width: 1122px; =
font-family: &#39;Times New Roman&#39;; ">
&gt;&gt; &gt; You don&#39;t want ECMP to hash on PW payload. =A0With CW and=
 without
&gt;&gt; &gt; fat-pw, you don&#39;t get ECMP on a PW but you do get ECMP on=
 an LSP
&gt;&gt; &gt; containing many PW.
&gt;&gt;
&gt;&gt; When the PW payload is IP, the hashing it for ECMP is useful (If t=
he
&gt;&gt; payload is not IP then use CW). FAT-PW may not be present in all
&gt;&gt; deployments.
&gt;
&gt; I really don&#39;t know that any PW are carrying IP. =A0That was not i=
n the
&gt; survey. =A0L3VPN would be carrying IP.
</pre><div style=3D"font-family: &#39;Times New Roman&#39;; ">Why are we ve=
ry much concerned about the ECMP in MPLS-TP networks?</div><div style=3D"fo=
nt-family: &#39;Times New Roman&#39;; ">I think, as per the RFC-5960,=A0</d=
iv>
<div style=3D"font-family: &#39;Times New Roman&#39;; "><span class=3D"Appl=
e-style-span" style=3D"color: rgb(46, 44, 44); font-family: Georgia, &#39;T=
imes New Roman&#39;, Times, serif; font-size: 15px; line-height: 22px; -web=
kit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "=
><pre style=3D"text-align: left; ">
   Equal-Cost Multi-Path (ECMP) load-balancing MUST NOT be performed on
   an MPLS-TP LSP.</pre></span></div><div style=3D"font-family: &#39;Times =
New Roman&#39;; "><br></div><div style=3D"font-family: &#39;Times New Roman=
&#39;; ">Thanks,</div><div style=3D"font-family: &#39;Times New Roman&#39;;=
 ">
Venkat.</div></span></div><h1 style=3D"font-family: &#39;Times New Roman&#3=
9;; font-size: medium; ">Re: [PWE3] GAL above and below the PW label</h1><h=
r style=3D"font-family: &#39;Times New Roman&#39;; font-size: medium; "><ul=
 style=3D"font-family: &#39;Times New Roman&#39;; font-size: medium; ">
<li><em>To</em>:=A0<a href=3D"mailto:curtis@DOMAIN.HIDDEN">curtis at occnc.=
com</a></li><li><em>Subject</em>: Re: [PWE3] GAL above and below the PW lab=
el</li><li><em>From</em>: Sriganesh Kini &lt;<a href=3D"mailto:sriganesh.ki=
ni@DOMAIN.HIDDEN">sriganesh.kini at ericsson.com</a>&gt;</li>
<li><em>Date</em>: Thu, 31 Mar 2011 06:35:55 -0700</li><li><em>Cc</em>: &qu=
ot;<a href=3D"mailto:pwe3@DOMAIN.HIDDEN">pwe3 at ietf.org</a>&quot; &lt;<a =
href=3D"mailto:pwe3@DOMAIN.HIDDEN">pwe3 at ietf.org</a>&gt;</li><li><em>Del=
ivered-to</em>:=A0<a href=3D"mailto:pwe3@DOMAIN.HIDDEN">pwe3 at core3.amsl.=
com</a></li>
<li><em>Dkim-signature</em>: v=3D1; a=3Drsa-sha256; c=3Drelaxed/relaxed; d=
=3D<a href=3D"http://gmail.com">gmail.com</a>; s=3Dgamma; h=3Ddomainkey-sig=
nature:mime-version:sender:in-reply-to:references:from :date:x-google-sende=
r-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=
=3DA+vOatCHfOjZApN0E5yyinhuXIRZkYjTT7i6/+y5GRI=3D; b=3DOFt+lkWg+fovMGSRWve+=
7FsSjiqfq272VYgTC7TlwERM0yzysYgCBAsCB5m3odhT2N 0EyO74FE/X6wILVxasY1LH8mMxD6=
D392XLS8GRfnqIIqGnJxX2Yf6PTJzDN+9wZtq6dd w/NhWavvVJM7iCESsjJF38Id8YgUq+z95W=
Mxg=3D</li>
<li><em>Domainkey-signature</em>: a=3Drsa-sha1; c=3Dnofws; d=3D<a href=3D"h=
ttp://gmail.com">gmail.com</a>; s=3Dgamma; h=3Dmime-version:sender:in-reply=
-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:con=
tent-type :content-transfer-encoding; b=3DCvmfIfuKmyWajzqum1g4zmHnattN67oLk=
rAHwMKMO45NU6eQ9B4lC0or/0Coow2naZ d5nqj+Ulcwo221mbSGynICRBrHshs8ppnDeGatxlk=
2Mu4ot75YHcVk39xPW1szv9WbUN A9+fjVEqqWZyJO4pcmbHXXv2ydnhHLn3r9dXk=3D</li>
<li><em>In-reply-to</em>: &lt;<a href=3D"mailto:201103311249.p2VCnU9Y085450=
@DOMAIN.HIDDEN">201103311249.p2VCnU9Y085450 at harbor.orleans.occnc.com</a>=
&gt;</li><li><em>List-archive</em>: &lt;<a href=3D"http://www.ietf.org/mail=
-archive/web/pwe3">http://www.ietf.org/mail-archive/web/pwe3</a>&gt;</li>
<li><em>List-help</em>: &lt;<a href=3D"mailto:pwe3-request@ietf.org?subject=
=3Dhelp">mailto:pwe3-request@ietf.org?subject=3Dhelp</a>&gt;</li><li><em>Li=
st-id</em>: Pseudo Wires Edge to Edge &lt;<a href=3D"http://pwe3.ietf.org">=
pwe3.ietf.org</a>&gt;</li>
<li><em>List-post</em>: &lt;<a href=3D"mailto:pwe3@ietf.org">mailto:pwe3@ie=
tf.org</a>&gt;</li><li><em>List-subscribe</em>: &lt;<a href=3D"https://www.=
ietf.org/mailman/listinfo/pwe3">https://www.ietf.org/mailman/listinfo/pwe3<=
/a>&gt;, &lt;<a href=3D"mailto:pwe3-request@ietf.org?subject=3Dsubscribe">m=
ailto:pwe3-request@ietf.org?subject=3Dsubscribe</a>&gt;</li>
<li><em>List-unsubscribe</em>: &lt;<a href=3D"https://www.ietf.org/mailman/=
listinfo/pwe3">https://www.ietf.org/mailman/listinfo/pwe3</a>&gt;, &lt;<a h=
ref=3D"mailto:pwe3-request@ietf.org?subject=3Dunsubscribe">mailto:pwe3-requ=
est@ietf.org?subject=3Dunsubscribe</a>&gt;</li>
<li><em>References</em>: &lt;<a href=3D"mailto:AANLkTi%3DfuSg1iBy%2Bjz0Svsf=
NpGrd-%3D32p%2BKMV7Q%3DhOSv@DOMAIN.HIDDEN">AANLkTi=3DfuSg1iBy+jz0SvsfNpGrd-=
=3D32p+KMV7Q=3DhOSv at mail.gmail.com</a>&gt; &lt;<a href=3D"mailto:2011033=
11249.p2VCnU9Y085450@DOMAIN.HIDDEN">201103311249.p2VCnU9Y085450 at harbor.o=
rleans.occnc.com</a>&gt;</li>
<li><em>Sender</em>:=A0<a href=3D"mailto:sriganeshkini@DOMAIN.HIDDEN">sriga=
neshkini at gmail.com</a></li></ul><hr style=3D"font-family: &#39;Times New=
 Roman&#39;; font-size: medium; "><span class=3D"Apple-style-span" style=3D=
"font-family: &#39;Times New Roman&#39;; font-size: medium; "><pre style=3D=
"white-space: pre-wrap; word-wrap: break-word; width: 1122px; ">
inline

On Thu, Mar 31, 2011 at 5:49 AM, Curtis Villamizar &lt;curtis at <a href=3D=
"http://occnc.com">occnc.com</a>&gt; wrote:
&gt;
&gt; In message &lt;AANLkTi=3DfuSg1iBy+jz0SvsfNpGrd-=3D32p+KMV7Q=3DhOSv at =
<a href=3D"http://mail.gmail.com">mail.gmail.com</a>&gt;
&gt; Sriganesh Kini writes:
&gt;&gt;
&gt;&gt; See inline
&gt;&gt;
&gt;&gt; On Thu, Mar 31, 2011 at 4:40 AM, Curtis Villamizar &lt;curtis at <=
a href=3D"http://occnc.com">occnc.com</a>&gt; wrote:
&gt;&gt; &gt;
&gt;&gt; &gt; Sriganesh, Sasha, Loa, Dave,
&gt;&gt; &gt;
&gt;&gt; &gt; Would you please not top post. =A0See inline.
&gt;&gt; &gt;
&gt;&gt; &gt; Curtis
&gt;&gt; &gt;
&gt;&gt; &gt; In message &lt;AANLkTimGJTVa42CFsj-PRcLiPLGTBhZ-t3sNRcTadHHe =
at <a href=3D"http://mail.gmail.com">mail.gmail.com</a>&gt;
&gt;&gt; &gt; Sriganesh Kini writes:
&gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; Sasha, that issue with VCCV Type-3 (without CW) is not ad=
dressed by
&gt;&gt; &gt;&gt; the draft. Practically, is that a major issue ? Especiall=
y setting TTL
&gt;&gt; &gt;&gt; &gt; 1 for SS PW is possible I guess but would be some ki=
nd of serious
&gt;&gt; &gt;&gt; operational oversight. Besides such a packet would fail s=
ome check
&gt;&gt; &gt;&gt; along the path.
&gt;&gt; &gt;
&gt;&gt; &gt; End to end OAM should set TTL&gt;1 and not use VCCV Type-3. =
=A0The T-PE may
&gt;&gt; &gt; not have reliable information to set TTL, so in MS-PW it migh=
t be
&gt;&gt; &gt; worth discouraging VCCV Type-3 except for use as a traceroute
&gt;&gt; &gt; capability or to address S-PEs by node distance along the pat=
h.
&gt;&gt;
&gt;&gt; If there is indeed a concern of TTL exceeding number of segments (=
with
&gt;&gt; Type-3 and no CW), the same concern would apply when tracing. So
&gt;&gt; tracing would be impossible.
&gt;
&gt; traceroute stops when it hits the egress.

That is exactly the point I am trying to make. Why would the TTL from
that information not be reliable for other OAM operations ?

&gt;
&gt;&gt; &gt;&gt; Also, what I heard at the mic regarding impl results is t=
hat it
&gt;&gt; &gt;&gt; doesn&#39;t make sense to deprecate what is already deplo=
yed.
&gt;&gt; &gt;
&gt;&gt; &gt; Yes. =A0But VCCV Type-3 with MS-PW is not already deployed.
&gt;&gt;
&gt;&gt; I am not aware of the survey addressing this.
&gt;
&gt; AFAIK Type-1 is being used, but I could be wrong. =A0Maybe someone who
&gt; has implemented and knows of a deployment or someone who has deployed
&gt; can reply so we don&#39;t need another survey.
&gt;
&gt;&gt; &gt;&gt; Note that CC Type 1 prevents ECMP (when FAT-PW is not ava=
ilable).
&gt;&gt; &gt;&gt; Using GAL below PW also requires ECMP based on label hash=
ing to ignore
&gt;&gt; &gt;&gt; reserved labels.
&gt;&gt; &gt;
&gt;&gt; &gt; You don&#39;t want ECMP to hash on PW payload. =A0With CW and=
 without
&gt;&gt; &gt; fat-pw, you don&#39;t get ECMP on a PW but you do get ECMP on=
 an LSP
&gt;&gt; &gt; containing many PW.
&gt;&gt;
&gt;&gt; When the PW payload is IP, the hashing it for ECMP is useful (If t=
he
&gt;&gt; payload is not IP then use CW). FAT-PW may not be present in all
&gt;&gt; deployments.
&gt;
&gt; I really don&#39;t know that any PW are carrying IP. =A0That was not i=
n the
&gt; survey. =A0L3VPN would be carrying IP.

IPLS would be another case.

&gt;
&gt;&gt; &gt;&gt; 2011/3/31 Alexander Vainshtein &lt;Alexander.Vainshtein a=
t <a href=3D"http://ecitele.com">ecitele.com</a>&gt;:
&gt;&gt; &gt;&gt; &gt; Sriganesh, Curtis and all,
&gt;&gt; &gt;&gt; &gt; IMHO and FWIW I think that the only problem with VCC=
V Type 3 is the
&gt;&gt; &gt;&gt; &gt; risk of OAM packets leaking out of T-PE towards the =
AC (if you
&gt;&gt; &gt;&gt; &gt; accidentally set the TTL value too high). To the bes=
t of my
&gt;&gt; &gt;&gt; &gt; understanding the offset proposal does not solve tha=
t - or did I miss
&gt;&gt; &gt;&gt; &gt; something?
&gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt; One way to solve it is to use VCCV Type 1 (clean whe=
re applicable).
&gt;&gt; &gt;&gt; &gt; Another way would be by using GAL below the PW label=
 (possible but
&gt;&gt; &gt;&gt; &gt; messy). If the industry moves towards deprecating Et=
hernet PWs
&gt;&gt; &gt;&gt; &gt; without CW, =A0it becomes completely unnecessary.
&gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt; My 2c,
&gt;&gt; &gt;&gt; &gt; =A0 =A0 Sasha
&gt;&gt; &gt;
&gt;&gt; &gt; This is the context suggesting a potential problem with VCCV =
Type 3.
&gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; -----Original Message-----
&gt;&gt; &gt;&gt; &gt;&gt; From: pwe3-bounces at <a href=3D"http://ietf.org=
">ietf.org</a> [<a rel=3D"nofollow" href=3D"mailto:pwe3-bounces">mailto:pwe=
3-bounces</a> at <a href=3D"http://ietf.org">ietf.org</a>] On Behalf Of
&gt;&gt; &gt;&gt; &gt;&gt; Sriganesh Kini
&gt;&gt; &gt;&gt; &gt;&gt; Sent: Thursday, March 31, 2011 10:09 AM
&gt;&gt; &gt;&gt; &gt;&gt; To: curtis at <a href=3D"http://occnc.com">occnc=
.com</a>
&gt;&gt; &gt;&gt; &gt;&gt; Cc: pwe3 at <a href=3D"http://ietf.org">ietf.org=
</a>
&gt;&gt; &gt;&gt; &gt;&gt; Subject: Re: [PWE3] GAL above and below the PW l=
abel
&gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; All,
&gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; Just an FYI that a proposal for fate-sharing PW =
OAM and data given in
&gt;&gt; &gt;&gt; &gt;&gt; draft-kini-pwe3-inband-cc-offset
&gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; Just to summarize the proposal.
&gt;&gt; &gt;&gt; &gt;&gt; 1. It does not require GAL in PW. TTL expiry is =
used to alert the S/T-
&gt;&gt; &gt;&gt; &gt;&gt; PE.
&gt;&gt; &gt;&gt; &gt;&gt; 2. It is mainly applicable when CW is not used i=
n the PW.
&gt;&gt; &gt;&gt; &gt;&gt; 3. It uses a fixed offset (negotiated between PW=
 endpoints) after the
&gt;&gt; &gt;&gt; &gt;&gt; label stack before starting the OAM msg.
&gt;&gt; &gt;&gt; &gt;&gt; 4. The bytes between the label-stack and the fix=
ed offset is referred
&gt;&gt; &gt;&gt; &gt;&gt; to as a pseudoflow header and is filled with byt=
e-values (by the PE)
&gt;&gt; &gt;&gt; &gt;&gt; that represent the flow for which OAM is desired=
. This helps PW OAM
&gt;&gt; &gt;&gt; &gt;&gt; and data to fate-share even when the intermediat=
e node looks beyond
&gt;&gt; &gt;&gt; &gt;&gt; label stack to do multipath forwarding decisions=
.
&gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; On Thu, Mar 31, 2011 at 12:03 AM, Curtis Villami=
zar &lt;curtis at <a href=3D"http://occnc.com">occnc.com</a>&gt;
&gt;&gt; &gt;&gt; &gt;&gt; wrote:
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; Loa, Dave, Sasha,
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; I&#39;ve snipped from various posts on the =
thread that Sasha started.
&gt;&gt; &gt;&gt; &gt;&gt; =A0See
&gt;&gt; &gt;&gt; &gt;&gt; &gt; inline.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; In message &lt;4D92F5D3.6080609 at <a href=
=3D"http://pi.nu">pi.nu</a>&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; Loa Andersson writes:
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; All,
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; missed a nuance in Sasha subject line.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; We have two issues
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; - where the GAL is placed relative to t=
he PW label, I =A0believe it is
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; =A0 =A0necessary to have the GAL below =
the PW label.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; - whether the the GAL label needs to be=
 bottom of stack or not, it
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; =A0 =A0figure that this is really a dis=
cussion if it is possible to have
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; =A0 =A0a FAT label below the GAL or not=
. I&#39;m not sure =A0about my
&gt;&gt; &gt;&gt; &gt;&gt; preferences
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; =A0 =A0but I think it is possible.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; /Loa
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; I agree with Loa&#39;s summary. =A0Not putt=
ing GAL at the bottom may
&gt;&gt; &gt;&gt; &gt;&gt; confuse
&gt;&gt; &gt;&gt; &gt;&gt; &gt; some LSR, but putting it above the PW label=
 is likely to be even more
&gt;&gt; &gt;&gt; &gt;&gt; &gt; problematic.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; In message
&gt;&gt; &gt;&gt; &gt;&gt; &lt;60C093A41B5E45409A19D42CF7786DFD51D5310B53 a=
t EUSAACMS0703.eamcs.ericsson
&gt;&gt; &gt;&gt; &gt;&gt; .se&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; David Allan I writes:
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; It does become a new behavior, GAL with=
 S=3D3D0. However the
&gt;&gt; &gt;&gt; &gt;&gt; combination of G=3D
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; AL being top label at the S-PE and TTL =
being encoded in the PW label
&gt;&gt; &gt;&gt; &gt;&gt; means =3D
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; that fate sharing is broken at every S-=
PE. Life only gets a little
&gt;&gt; &gt;&gt; &gt;&gt; more str=3D
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; ange if there is a FAT label as well...
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; That being said, GAL as bottom label is=
 broken in any ECMP
&gt;&gt; &gt;&gt; &gt;&gt; environment, whi=3D
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; ch is why GAL is a TP construct.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; my 2 cents
&gt;&gt; &gt;&gt; &gt;&gt; &gt;&gt; D
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; Dave,
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; If GAL is broken for ECMP, which it is, the=
n all TP OAM is broken.
&gt;&gt; &gt;&gt; &gt;&gt; &gt; If all it takes to fix it is simple then le=
ts just fix it.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; This is what we&#39;d have to do.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; =A01) Relax the requirement that GAL be at =
the bottom
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; =A02) Have the ingress insert GAL in the st=
ack immediately below the
&gt;&gt; &gt;&gt; &gt;&gt; &gt; =A0 =A0 label for which the measurement is =
made, keeping the rest of the
&gt;&gt; &gt;&gt; &gt;&gt; &gt; =A0 =A0 label stack in place.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; The only thing the midpoing LSR at a multip=
ath (LAG, link bundle for
&gt;&gt; &gt;&gt; &gt;&gt; &gt; MPLS) has to do is skip over the GAL when h=
ashing, as if the GAL
&gt;&gt; &gt;&gt; &gt;&gt; &gt; wasn&#39;t there. =A0That will yield the sa=
me hash value and it will
&gt;&gt; &gt;&gt; &gt;&gt; &gt; preserve fate-sharing across multipath.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; I prefer that we fix things rather than com=
plain that they are
&gt;&gt; &gt;&gt; &gt;&gt; broken.
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt; &gt; Curtis
&gt;&gt; &gt;&gt; &gt;&gt; &gt; ___________________________________________=
____
&gt;&gt; &gt;&gt; &gt;&gt; &gt; pwe3 mailing list
&gt;&gt; &gt;&gt; &gt;&gt; &gt; pwe3 at <a href=3D"http://ietf.org">ietf.or=
g</a>
&gt;&gt; &gt;&gt; &gt;&gt; &gt; <a rel=3D"nofollow" href=3D"https://www.iet=
f.org/mailman/listinfo/pwe3">https://www.ietf.org/mailman/listinfo/pwe3</a>
&gt;&gt; &gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; &gt;&gt; --
&gt;&gt; &gt;&gt; &gt;&gt; - Sri
&gt;&gt; &gt;&gt; &gt;&gt; _______________________________________________
&gt;&gt; &gt;&gt; &gt;&gt; pwe3 mailing list
&gt;&gt; &gt;&gt; &gt;&gt; pwe3 at <a href=3D"http://ietf.org">ietf.org</a>
&gt;&gt; &gt;&gt; &gt;&gt; <a rel=3D"nofollow" href=3D"https://www.ietf.org=
/mailman/listinfo/pwe3">https://www.ietf.org/mailman/listinfo/pwe3</a>
&gt;&gt; &gt;&gt; &gt; _______________________________________________
&gt;&gt; &gt;&gt; &gt; pwe3 mailing list
&gt;&gt; &gt;&gt; &gt; pwe3 at <a href=3D"http://ietf.org">ietf.org</a>
&gt;&gt; &gt;&gt; &gt; <a rel=3D"nofollow" href=3D"https://www.ietf.org/mai=
lman/listinfo/pwe3">https://www.ietf.org/mailman/listinfo/pwe3</a>
&gt;&gt; &gt;&gt; &gt;
&gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt; --
&gt;&gt; &gt;&gt; - Sri
&gt;&gt; &gt;&gt;
&gt;&gt; &gt;&gt;</pre></span>

--20cf3071ced8388408049fcc8931--

From stbryant@cisco.com  Thu Mar 31 15:46:30 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC2BE3A6993 for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 15:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.478
X-Spam-Level: 
X-Spam-Status: No, score=-110.478 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 BzUJU3eFLxTW for <pwe3@core3.amsl.com>; Thu, 31 Mar 2011 15:46:29 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 910423A6949 for <pwe3@ietf.org>; Thu, 31 Mar 2011 15:46:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=2392; q=dns/txt; s=iport; t=1301611689; x=1302821289; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=rFYH6LMmVSzV7wtoIsMEYugwmBwGbolAzr9OdtWFpiU=; b=Q79syTX7s0o5EKSLesKgwIQ5co+4klacRjx3TTMyG4v1dTmup+gyI6Wo McozmIOfMokXl2IwpULYBnG4XGs3ZYrlMg9zlHaAvKb7WLuVEL5HcTyDF 2BCc7CSkU4NJLchLI1ZnU63a+qYZU6vq0sh12Va3yCnHK+k7ePKRNYZ22 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsIEAA8ElU2Q/khMgWdsb2JhbACCXqJ7FAEBFiYliHmbHoJwDgGZOIVrBI0R
X-IronPort-AV: E=Sophos;i="4.63,278,1299456000"; d="scan'208,217";a="24019741"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 31 Mar 2011 22:48:08 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2VMm8Eh001145; Thu, 31 Mar 2011 22:48:08 GMT
Received: from dhcp-4265.meeting.ietf.org (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p2VMm7U27089; Thu, 31 Mar 2011 23:48:08 +0100 (BST)
Message-ID: <4D9504A6.40008@cisco.com>
Date: Thu, 31 Mar 2011 23:48:06 +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.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: venkatesan mahalingam <venkatflex@gmail.com>
References: <AANLkTi=ZirXML6gepT2pJGXgmxi3Y4C-X8aT1uxMGThO@mail.gmail.com>
In-Reply-To: <AANLkTi=ZirXML6gepT2pJGXgmxi3Y4C-X8aT1uxMGThO@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090706080402050500030103"
Cc: pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] GAL above and below the PW label
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 22:46:30 -0000

This is a multi-part message in MIME format.
--------------090706080402050500030103
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


> Why are we very much concerned about the ECMP in MPLS-TP networks?
> I think, as per the RFC-5960,
>     Equal-Cost Multi-Path (ECMP) load-balancing MUST NOT be performed on
>     an MPLS-TP LSP.
No, but the packet may get handed off to a regular MPLS n/w.

As far as a -TP P router is concerned it never sees the PW or FAT or Ent 
label - just the top
label. So I wonder if we were too restrictive. Note I am NOT proposing 
label based ECMP in
the -TP segment.

- Stewart





--------------090706080402050500030103
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 text="#000000" bgcolor="#ffffff">
    <br>
    <blockquote
      cite="mid:AANLkTi=ZirXML6gepT2pJGXgmxi3Y4C-X8aT1uxMGThO@mail.gmail.com"
      type="cite">
      <div><span class="Apple-style-span" style="font-size: medium;">
          <div style="font-family: 'Times New Roman';">Why are we very
            much concerned about the ECMP in MPLS-TP networks?</div>
          <div style="font-family: 'Times New Roman';">I think, as per
            the RFC-5960,&nbsp;</div>
          <div style="font-family: 'Times New Roman';"><span
              class="Apple-style-span" style="color: rgb(46, 44, 44);
              font-family: Georgia,'Times New Roman',Times,serif;
              font-size: 15px; line-height: 22px;">
              <pre style="text-align: left;">   Equal-Cost Multi-Path (ECMP) load-balancing MUST NOT be performed on
   an MPLS-TP LSP.</pre>
            </span></div>
        </span></div>
    </blockquote>
    No, but the packet may get handed off to a regular MPLS n/w.<br>
    <br>
    As far as a -TP P router is concerned it never sees the PW or FAT or
    Ent label - just the top<br>
    label. So I wonder if we were too restrictive. Note I am NOT
    proposing label based ECMP in<br>
    the -TP segment.<br>
    <br>
    - Stewart<br>
    <br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------090706080402050500030103--
