
From y.kamite@ntt.com  Mon Nov  4 18:09:39 2013
Return-Path: <y.kamite@ntt.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38D2B21E8172 for <pwe3@ietfa.amsl.com>; Mon,  4 Nov 2013 18:09:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.845
X-Spam-Level: 
X-Spam-Status: No, score=-0.845 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0y5mPzNIQ7nl for <pwe3@ietfa.amsl.com>; Mon,  4 Nov 2013 18:09:35 -0800 (PST)
Received: from mgw020.noc.ntt.com (mgw020.noc.ntt.com [210.160.55.2]) by ietfa.amsl.com (Postfix) with ESMTP id D9AF111E814B for <pwe3@ietf.org>; Mon,  4 Nov 2013 18:09:33 -0800 (PST)
Received: from c0043i0.coe.ntt.com (unknown [10.18.161.12]) by mgw020.noc.ntt.com (NTT Com MailSV) with ESMTP id 260E24460556; Tue,  5 Nov 2013 11:09:32 +0900 (JST)
Received: from C0036I0.coe.ntt.com (10.18.160.40) by c0043i0.coe.ntt.com (10.18.161.12) with Microsoft SMTP Server (TLS) id 14.1.438.0; Tue, 5 Nov 2013 11:09:31 +0900
Received: from C0007I0.coe.ntt.com ([169.254.1.138]) by C0036I0.coe.ntt.com ([10.18.160.40]) with mapi id 14.01.0438.000; Tue, 5 Nov 2013 11:09:31 +0900
From: Yuji Kamite <y.kamite@ntt.com>
To: "Andrew G. Malis" <amalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Second WG last call (and IPR call) for draft-ietf-pwe3-p2mp-pw-requirements
Thread-Index: AQHO1AcqZtmNS/plakiJsj3ZshTO4JoV74PA
Date: Tue, 5 Nov 2013 02:09:30 +0000
Message-ID: <1A095D7ECD89A64C9D3C77AE2DDE660B57F45509@C0007I0.coe.ntt.com>
References: <CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com>
In-Reply-To: <CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ccmail-original-to: amalis@gmail.com, pwe3@ietf.org
x-ccmail-original-cc: raggarwa_1@yahoo.com
x-originating-ip: [10.14.150.185]
Content-Type: multipart/alternative; boundary="_000_1A095D7ECD89A64C9D3C77AE2DDE660B57F45509C0007I0coenttco_"
MIME-Version: 1.0
Cc: Rahul Aggarwal <raggarwa_1@yahoo.com>
Subject: Re: [PWE3] Second WG last call (and IPR call) for	draft-ietf-pwe3-p2mp-pw-requirements
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 05 Nov 2013 02:09:39 -0000

--_000_1A095D7ECD89A64C9D3C77AE2DDE660B57F45509C0007I0coenttco_
Content-Type: text/plain; charset="iso-2022-jp"

Hi,

I$B!G(Bm not aware of any IPR information about this draft.

Best regards,
Yuji


From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
Sent: Tuesday, October 29, 2013 2:56 AM
To: pwe3@ietf.org
Cc: Rahul Aggarwal
Subject: [PWE3] Second WG last call (and IPR call) for draft-ietf-pwe3-p2mp-pw-requirements

PWE3ers,
You may recall that almost exactly two years ago, we sent draft-ietf-pwe3-p2mp-pw-requirements-05 to the IESG. It was sent back to the WG in February of 2012, and it took a while, but we now have that rewrite to submit back to the IESG.
However, because of the length of time, and the fact that -06 just came out about a week ago (so few people have had a chance to re-read it), we are going to have a second WG last call before sending it back to the IESG.
So please review the draft, which you can find at https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requirements-06 . If you would like to see what's changed, you can easily see that here: https://tools.ietf.org/rfcdiff?url2=draft-ietf-pwe3-p2mp-pw-requirements-06.txt .

Coincidentally, we are also polling for knowledge of IPR that
applies to this draft to ensure that IPR has been disclosed in
compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378
for more details). To date, there have been no IPR declarations on this
draft.

If you are listed as a document author or contributor please respond
to this email whether or not you are aware of any additional IPR. The
draft will not be forwarded to the IESG until a response has been
received from each author and contributor. See the list of contributing
authors in Section 8 to refresh your memory.

If you are on the PWE3 WG email list but are not listed as an author
or contributor, then please explicitly respond only if you are aware
of any IPR that has not yet been disclosed in conformance with IETF
rules.
Also, if you are listed as an author or contributor and your address info has changed, please email back privately so that we can get that updated before submitting it to the IESG.

Because this last call spans the IETF meeting, it will be open for three weeks, ending on November 18.
Thanks,
Andy

--_000_1A095D7ECD89A64C9D3C77AE2DDE660B57F45509C0007I0coenttco_
Content-Type: text/html; charset="iso-2022-jp"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PWlzby0yMDIyLWpwIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIg
Y29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwh
LS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Ik1T
IEdvdGhpYyI7DQoJcGFub3NlLTE6MiAxMSA2IDkgNyAyIDUgOCAyIDQ7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiTVMgR290aGljIjsNCglwYW5vc2UtMToyIDExIDYgOSA3IDIgNSA4IDIg
NDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJNUyBHb3RoaWMiOw0KCXBhbm9zZS0xOjIg
MTEgNiA5IDcgMiA1IDggMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6VGFob21hOw0K
CXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICov
DQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowbW07
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1p
bHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5r
DQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlv
bjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZTt9DQpzcGFuLjE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZv
bnQtZmFtaWx5OiJBcmlhbCIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0No
cERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkFy
aWFsIiwic2Fucy1zZXJpZiI7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3
OTIuMHB0Ow0KCW1hcmdpbjo5OS4yNXB0IDMwLjBtbSAzMC4wbW0gMzAuMG1tO30NCmRpdi5Xb3Jk
U2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBt
c28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYi
Pg0KPHY6dGV4dGJveCBpbnNldD0iNS44NXB0LC43cHQsNS44NXB0LC43cHQiIC8+DQo8L286c2hh
cGVkZWZhdWx0cz48L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIx
IiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkg
bGFuZz0iSkEiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNl
Y3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPkkbJEIhRxsoQm0gbm90IGF3YXJlIG9mIGFueSBJUFIgaW5mb3JtYXRpb24gYWJvdXQg
dGhpcyBkcmFmdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5CZXN0IHJlZ2FyZHMs
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+WXVqaTxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+IHB3ZTMtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnB3ZTMtYm91bmNlc0BpZXRmLm9yZ10N
CjxiPk9uIEJlaGFsZiBPZiA8L2I+QW5kcmV3IEcuIE1hbGlzPGJyPg0KPGI+U2VudDo8L2I+IFR1
ZXNkYXksIE9jdG9iZXIgMjksIDIwMTMgMjo1NiBBTTxicj4NCjxiPlRvOjwvYj4gcHdlM0BpZXRm
Lm9yZzxicj4NCjxiPkNjOjwvYj4gUmFodWwgQWdnYXJ3YWw8YnI+DQo8Yj5TdWJqZWN0OjwvYj4g
W1BXRTNdIFNlY29uZCBXRyBsYXN0IGNhbGwgKGFuZCBJUFIgY2FsbCkgZm9yIGRyYWZ0LWlldGYt
cHdlMy1wMm1wLXB3LXJlcXVpcmVtZW50czxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPlBXRTNl
cnMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5Zb3UgbWF5IHJl
Y2FsbCB0aGF0IGFsbW9zdCBleGFjdGx5IHR3byB5ZWFycyBhZ28sIHdlIHNlbnQgZHJhZnQtaWV0
Zi1wd2UzLXAybXAtcHctcmVxdWlyZW1lbnRzLTA1IHRvIHRoZSBJRVNHLiBJdCB3YXMgc2VudCBi
YWNrIHRvIHRoZSBXRyBpbiBGZWJydWFyeSBvZiAyMDEyLCBhbmQgaXQgdG9vayBhIHdoaWxlLCBi
dXQgd2Ugbm93DQogaGF2ZSB0aGF0IHJld3JpdGUgdG8gc3VibWl0IGJhY2sgdG8gdGhlIElFU0cu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5Ib3dldmVyLCBiZWNh
dXNlIG9mIHRoZSBsZW5ndGggb2YgdGltZSwgYW5kIHRoZSBmYWN0IHRoYXQgLTA2IGp1c3QgY2Ft
ZSBvdXQgYWJvdXQgYSB3ZWVrIGFnbyAoc28gZmV3IHBlb3BsZSBoYXZlIGhhZCBhIGNoYW5jZSB0
byByZS1yZWFkIGl0KSwgd2UgYXJlIGdvaW5nIHRvIGhhdmUgYSBzZWNvbmQgV0cgbGFzdCBjYWxs
IGJlZm9yZQ0KIHNlbmRpbmcgaXQgYmFjayB0byB0aGUgSUVTRy48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEy
LjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPlNvIHBsZWFzZSByZXZpZXcgdGhlIGRyYWZ0LCB3aGlj
aCB5b3UgY2FuIGZpbmQgYXQNCjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9k
cmFmdC1pZXRmLXB3ZTMtcDJtcC1wdy1yZXF1aXJlbWVudHMtMDYiPmh0dHBzOi8vdG9vbHMuaWV0
Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXB3ZTMtcDJtcC1wdy1yZXF1aXJlbWVudHMtMDY8L2E+IC4g
SWYgeW91IHdvdWxkIGxpa2UgdG8gc2VlIHdoYXQncyBjaGFuZ2VkLCB5b3UgY2FuIGVhc2lseSBz
ZWUgdGhhdCBoZXJlOg0KPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmP3Vy
bDI9ZHJhZnQtaWV0Zi1wd2UzLXAybXAtcHctcmVxdWlyZW1lbnRzLTA2LnR4dCI+DQpodHRwczov
L3Rvb2xzLmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRmLXB3ZTMtcDJtcC1wdy1yZXF1
aXJlbWVudHMtMDYudHh0PC9hPiAuPGJyPg0KPGJyPg0KQ29pbmNpZGVudGFsbHksIHdlIGFyZSBh
bHNvIHBvbGxpbmcgZm9yIGtub3dsZWRnZSBvZiBJUFIgdGhhdDxicj4NCmFwcGxpZXMgdG8gdGhp
cyBkcmFmdCB0byBlbnN1cmUgdGhhdCBJUFIgaGFzIGJlZW4gZGlzY2xvc2VkIGluPGJyPg0KY29t
cGxpYW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzIChzZWUgUkZDcyAzOTc5LCA0ODc5LCAzNjY5IGFu
ZCA1Mzc4IDxicj4NCmZvciBtb3JlIGRldGFpbHMpLiBUbyBkYXRlLCB0aGVyZSBoYXZlIGJlZW4g
bm8gSVBSIGRlY2xhcmF0aW9ucyBvbiB0aGlzPGJyPg0KZHJhZnQuPGJyPg0KPGJyPg0KSWYgeW91
IGFyZSBsaXN0ZWQgYXMgYSBkb2N1bWVudCBhdXRob3Igb3IgY29udHJpYnV0b3IgcGxlYXNlIHJl
c3BvbmQ8YnI+DQp0byB0aGlzIGVtYWlsIHdoZXRoZXIgb3Igbm90IHlvdSBhcmUgYXdhcmUgb2Yg
YW55IGFkZGl0aW9uYWwgSVBSLiBUaGU8YnI+DQpkcmFmdCB3aWxsIG5vdCBiZSBmb3J3YXJkZWQg
dG8gdGhlIElFU0cgdW50aWwgYSByZXNwb25zZSBoYXMgYmVlbjxicj4NCnJlY2VpdmVkIGZyb20g
ZWFjaCBhdXRob3IgYW5kIGNvbnRyaWJ1dG9yLiBTZWUgdGhlIGxpc3Qgb2YgY29udHJpYnV0aW5n
PGJyPg0KYXV0aG9ycyBpbiBTZWN0aW9uIDggdG8gcmVmcmVzaCB5b3VyIG1lbW9yeS48YnI+DQo8
YnI+DQpJZiB5b3UgYXJlIG9uIHRoZSBQV0UzIFdHIGVtYWlsIGxpc3QgYnV0IGFyZSBub3QgbGlz
dGVkIGFzIGFuIGF1dGhvcjxicj4NCm9yIGNvbnRyaWJ1dG9yLCB0aGVuIHBsZWFzZSBleHBsaWNp
dGx5IHJlc3BvbmQgb25seSBpZiB5b3UgYXJlIGF3YXJlPGJyPg0Kb2YgYW55IElQUiB0aGF0IGhh
cyBub3QgeWV0IGJlZW4gZGlzY2xvc2VkIGluIGNvbmZvcm1hbmNlIHdpdGggSUVURjxicj4NCnJ1
bGVzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5BbHNvLCBpZiB5b3UgYXJlIGxpc3RlZCBhcyBhbiBh
dXRob3Igb3IgY29udHJpYnV0b3IgYW5kIHlvdXIgYWRkcmVzcyBpbmZvIGhhcyBjaGFuZ2VkLCBw
bGVhc2UgZW1haWwgYmFjayBwcml2YXRlbHkgc28gdGhhdCB3ZSBjYW4gZ2V0IHRoYXQgdXBkYXRl
ZCBiZWZvcmUgc3VibWl0dGluZyBpdCB0byB0aGUgSUVTRy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyI+
QmVjYXVzZSB0aGlzIGxhc3QgY2FsbCBzcGFucyB0aGUgSUVURiBtZWV0aW5nLCBpdCB3aWxsIGJl
IG9wZW4gZm9yIHRocmVlIHdlZWtzLCBlbmRpbmcgb24gTm92ZW1iZXIgMTguPG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyI+VGhhbmtzLDxicj4NCkFuZHk8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8
L2h0bWw+DQo=

--_000_1A095D7ECD89A64C9D3C77AE2DDE660B57F45509C0007I0coenttco_--

From y.kamite@ntt.com  Mon Nov  4 18:21:36 2013
Return-Path: <y.kamite@ntt.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BBD21E82C2 for <pwe3@ietfa.amsl.com>; Mon,  4 Nov 2013 18:21:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.845
X-Spam-Level: 
X-Spam-Status: No, score=-1.845 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UkzLYaPr3vYS for <pwe3@ietfa.amsl.com>; Mon,  4 Nov 2013 18:21:32 -0800 (PST)
Received: from mgw010.noc.ntt.com (mgw010.noc.ntt.com [210.160.55.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1143821E8357 for <pwe3@ietf.org>; Mon,  4 Nov 2013 18:21:15 -0800 (PST)
Received: from c0044i0.coe.ntt.com (unknown [10.18.161.13]) by mgw010.noc.ntt.com (NTT Com MailSV) with ESMTP id 1EFBE57A0569; Tue,  5 Nov 2013 11:21:10 +0900 (JST)
Received: from C0038I0.coe.ntt.com (10.18.160.42) by c0044i0.coe.ntt.com (10.18.161.13) with Microsoft SMTP Server (TLS) id 14.1.438.0; Tue, 5 Nov 2013 11:21:08 +0900
Received: from C0007I0.coe.ntt.com ([169.254.1.138]) by C0038I0.coe.ntt.com ([10.18.160.42]) with mapi id 14.01.0438.000; Tue, 5 Nov 2013 11:21:09 +0900
From: Yuji Kamite <y.kamite@ntt.com>
To: "Andrew G. Malis" <amalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Second WG last call (and IPR call) for draft-ietf-pwe3-p2mp-pw-requirements
Thread-Index: AQHO1AcqZtmNS/plakiJsj3ZshTO4JoV8kWQ
Date: Tue, 5 Nov 2013 02:21:08 +0000
Message-ID: <1A095D7ECD89A64C9D3C77AE2DDE660B57F4552B@C0007I0.coe.ntt.com>
References: <CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com>
In-Reply-To: <CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ccmail-original-to: amalis@gmail.com, pwe3@ietf.org
x-ccmail-original-cc: raggarwa_1@yahoo.com
x-originating-ip: [10.14.150.185]
Content-Type: multipart/alternative; boundary="_000_1A095D7ECD89A64C9D3C77AE2DDE660B57F4552BC0007I0coenttco_"
MIME-Version: 1.0
Cc: Rahul Aggarwal <raggarwa_1@yahoo.com>
Subject: Re: [PWE3] Second WG last call (and IPR call) for	draft-ietf-pwe3-p2mp-pw-requirements
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 05 Nov 2013 02:21:37 -0000

--_000_1A095D7ECD89A64C9D3C77AE2DDE660B57F4552BC0007I0coenttco_
Content-Type: text/plain; charset="iso-2022-jp"

Hi all,

Just for your information, I will share the revised points from -05 to -06:

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

Major changes:

 - Removed multi-segment PWE cases all (Deleted Sec. 4.1-4.6 of old ver)

     --> Only SS-PW is defined now: "SS P2MP-PW over P2MP-LSP."

         MS-PW model is made out of scope of the document (Sec.1.2 in new ver)

- Added explanation based on RFC5332 (multicast encap) (Sec. 3.2 in new ver)

     --> Applied the basic notion of RFC5332 to PW context to justify the approach.

         (Label assignment's detail is not requirement work, so just having reference to RFC5331.)

- Removed ingress replication schemes (Sec. 3.2 in new ver)

     --> Previous draft-05 used to have a method to combine multiple P2P/P2MP-LSPs for

        conducting ingress replication.  But this is too complex and being apart from RFC5332.



Editorial changes:

- Adopted the latest boilerplate (xml2rfc)

- Used convention terms (capital letters in RFC2119)

- Any minor edits to remove MS-PW parts (e.g., terminology section)
--------------------------------------------------------------------------------

Regards,
-Yuji



From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
Sent: Tuesday, October 29, 2013 2:56 AM
To: pwe3@ietf.org
Cc: Rahul Aggarwal
Subject: [PWE3] Second WG last call (and IPR call) for draft-ietf-pwe3-p2mp-pw-requirements

PWE3ers,
You may recall that almost exactly two years ago, we sent draft-ietf-pwe3-p2mp-pw-requirements-05 to the IESG. It was sent back to the WG in February of 2012, and it took a while, but we now have that rewrite to submit back to the IESG.
However, because of the length of time, and the fact that -06 just came out about a week ago (so few people have had a chance to re-read it), we are going to have a second WG last call before sending it back to the IESG.
So please review the draft, which you can find at https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requirements-06 . If you would like to see what's changed, you can easily see that here: https://tools.ietf.org/rfcdiff?url2=draft-ietf-pwe3-p2mp-pw-requirements-06.txt .

Coincidentally, we are also polling for knowledge of IPR that
applies to this draft to ensure that IPR has been disclosed in
compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378
for more details). To date, there have been no IPR declarations on this
draft.

If you are listed as a document author or contributor please respond
to this email whether or not you are aware of any additional IPR. The
draft will not be forwarded to the IESG until a response has been
received from each author and contributor. See the list of contributing
authors in Section 8 to refresh your memory.

If you are on the PWE3 WG email list but are not listed as an author
or contributor, then please explicitly respond only if you are aware
of any IPR that has not yet been disclosed in conformance with IETF
rules.
Also, if you are listed as an author or contributor and your address info has changed, please email back privately so that we can get that updated before submitting it to the IESG.

Because this last call spans the IETF meeting, it will be open for three weeks, ending on November 18.
Thanks,
Andy

--_000_1A095D7ECD89A64C9D3C77AE2DDE660B57F4552BC0007I0coenttco_
Content-Type: text/html; charset="iso-2022-jp"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PWlzby0yMDIyLWpwIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIg
Y29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwh
LS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Ik1T
IEdvdGhpYyI7DQoJcGFub3NlLTE6MiAxMSA2IDkgNyAyIDUgOCAyIDQ7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiTVMgR290aGljIjsNCglwYW5vc2UtMToyIDExIDYgOSA3IDIgNSA4IDIg
NDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJNUyBHb3RoaWMiOw0KCXBhbm9zZS0xOjIg
MTEgNiA5IDcgMiA1IDggMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6VGFob21hOw0K
CXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICov
DQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowbW07
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1p
bHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5r
DQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlv
bjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZTt9DQpwLk1zb1BsYWluVGV4dCwgbGkuTXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5U
ZXh0DQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiXDY2RjhcNUYw
RlwzMDZBXDMwNTcgXChcNjU4N1w1QjU3XCkiOw0KCW1hcmdpbjowbW07DQoJbWFyZ2luLWJvdHRv
bTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6Ik1TIEdvdGhpYyI7
fQ0Kc3Bhbi4xNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWls
eToiQXJpYWwiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uYQ0KCXttc28t
c3R5bGUtbmFtZToiXDY2RjhcNUYwRlwzMDZBXDMwNTcgXChcNjU4N1w1QjU3XCkiOw0KCW1zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazpcNjZGOFw1RjBGXDMwNkFcMzA1NzsN
Cglmb250LWZhbWlseToiTVMgR290aGljIjt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUt
dHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQXJpYWwiLCJzYW5zLXNlcmlmIjt9DQpA
cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjk5LjI1
cHQgMzAuMG1tIDMwLjBtbSAzMC4wbW07fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRT
ZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVk
ZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiI+DQo8djp0ZXh0Ym94IGluc2V0PSI1
Ljg1cHQsLjdwdCw1Ljg1cHQsLjdwdCIgLz4NCjwvbzpzaGFwZWRlZmF1bHRzPjwveG1sPjwhW2Vu
ZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVk
aXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+
PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJKQSIgbGluaz0iYmx1ZSIg
dmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkhpIGFsbCw8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDsiPkp1c3QgZm9yIHlvdXIgaW5mb3JtYXRpb24sIEkgd2lsbCBzaGFyZSB0aGUgcmV2aXNlZCBw
b2ludHMgZnJvbSAtMDUgdG8gLTA2OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1V
UyI+TWFqb3IgY2hhbmdlczogPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOy0gUmVtb3ZlZCBtdWx0aS1zZWdtZW50
IFBXRSBjYXNlcyBhbGwgKERlbGV0ZWQgU2VjLiA0LjEtNC42IG9mIG9sZCB2ZXIpPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMi
PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAtLSZndDsgT25seSBTUy1QVyBpcyBkZWZpbmVkIG5v
dzogJnF1b3Q7U1MgUDJNUC1QVyBvdmVyIFAyTVAtTFNQLiZxdW90OzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgTVMtUFcgbW9kZWwgaXMg
bWFkZSBvdXQgb2Ygc2NvcGUgb2YgdGhlIGRvY3VtZW50IChTZWMuMS4yIGluIG5ldyB2ZXIpPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0i
RU4tVVMiPi0gQWRkZWQgZXhwbGFuYXRpb24gYmFzZWQgb24gUkZDNTMzMiAobXVsdGljYXN0IGVu
Y2FwKSAoU2VjLiAzLjIgaW4gbmV3IHZlcik8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7IC0tJmd0OyBBcHBsaWVkIHRoZSBiYXNpYyBub3Rpb24gb2YgUkZDNTMzMiB0byBQVyBjb250
ZXh0IHRvIGp1c3RpZnkgdGhlIGFwcHJvYWNoLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyhMYWJlbCBhc3NpZ25tZW50J3Mg
ZGV0YWlsIGlzIG5vdCByZXF1aXJlbWVudCB3b3JrLCBzbyBqdXN0IGhhdmluZyByZWZlcmVuY2Ug
dG8gUkZDNTMzMS4pPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gbGFuZz0iRU4tVVMiPi0gUmVtb3ZlZCBpbmdyZXNzIHJlcGxpY2F0aW9uIHNjaGVt
ZXMgKFNlYy4gMy4yIGluIG5ldyB2ZXIpPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyAtLSZndDsgUHJldmlvdXMgZHJhZnQtMDUgdXNlZCB0byBoYXZlIGEgbWV0aG9kIHRvIGNvbWJp
bmUgbXVsdGlwbGUgUDJQL1AyTVAtTFNQcyBmb3I8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGNvbmR1Y3RpbmcgaW5ncmVzcyByZXBsaWNhdGlvbi4m
bmJzcDsgQnV0IHRoaXMgaXMgdG9vIGNvbXBsZXggYW5kIGJlaW5nIGFwYXJ0IGZyb20gUkZDNTMz
Mi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBs
YW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPkVkaXRvcmlhbCBjaGFuZ2VzOjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4t
IEFkb3B0ZWQgdGhlIGxhdGVzdCBib2lsZXJwbGF0ZSAoeG1sMnJmYyk8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+LSBVc2Vk
IGNvbnZlbnRpb24gdGVybXMgKGNhcGl0YWwgbGV0dGVycyBpbiBSRkMyMTE5KTxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4t
IEFueSBtaW5vciBlZGl0cyB0byByZW1vdmUgTVMtUFcgcGFydHMgKGUuZy4sIHRlcm1pbm9sb2d5
IHNlY3Rpb24pPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPi0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFs
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4tWXVqaTxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJv
bTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IHB3
ZTMtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnB3ZTMtYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9u
IEJlaGFsZiBPZiA8L2I+QW5kcmV3IEcuIE1hbGlzPGJyPg0KPGI+U2VudDo8L2I+IFR1ZXNkYXks
IE9jdG9iZXIgMjksIDIwMTMgMjo1NiBBTTxicj4NCjxiPlRvOjwvYj4gcHdlM0BpZXRmLm9yZzxi
cj4NCjxiPkNjOjwvYj4gUmFodWwgQWdnYXJ3YWw8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gW1BXRTNd
IFNlY29uZCBXRyBsYXN0IGNhbGwgKGFuZCBJUFIgY2FsbCkgZm9yIGRyYWZ0LWlldGYtcHdlMy1w
Mm1wLXB3LXJlcXVpcmVtZW50czxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPlBXRTNlcnMsPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5Zb3UgbWF5IHJlY2FsbCB0
aGF0IGFsbW9zdCBleGFjdGx5IHR3byB5ZWFycyBhZ28sIHdlIHNlbnQgZHJhZnQtaWV0Zi1wd2Uz
LXAybXAtcHctcmVxdWlyZW1lbnRzLTA1IHRvIHRoZSBJRVNHLiBJdCB3YXMgc2VudCBiYWNrIHRv
IHRoZSBXRyBpbiBGZWJydWFyeSBvZiAyMDEyLCBhbmQgaXQgdG9vayBhIHdoaWxlLCBidXQgd2Ug
bm93DQogaGF2ZSB0aGF0IHJld3JpdGUgdG8gc3VibWl0IGJhY2sgdG8gdGhlIElFU0cuPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5Ib3dldmVyLCBiZWNhdXNlIG9m
IHRoZSBsZW5ndGggb2YgdGltZSwgYW5kIHRoZSBmYWN0IHRoYXQgLTA2IGp1c3QgY2FtZSBvdXQg
YWJvdXQgYSB3ZWVrIGFnbyAoc28gZmV3IHBlb3BsZSBoYXZlIGhhZCBhIGNoYW5jZSB0byByZS1y
ZWFkIGl0KSwgd2UgYXJlIGdvaW5nIHRvIGhhdmUgYSBzZWNvbmQgV0cgbGFzdCBjYWxsIGJlZm9y
ZQ0KIHNlbmRpbmcgaXQgYmFjayB0byB0aGUgSUVTRy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+
PHNwYW4gbGFuZz0iRU4tVVMiPlNvIHBsZWFzZSByZXZpZXcgdGhlIGRyYWZ0LCB3aGljaCB5b3Ug
Y2FuIGZpbmQgYXQNCjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1p
ZXRmLXB3ZTMtcDJtcC1wdy1yZXF1aXJlbWVudHMtMDYiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
aHRtbC9kcmFmdC1pZXRmLXB3ZTMtcDJtcC1wdy1yZXF1aXJlbWVudHMtMDY8L2E+IC4gSWYgeW91
IHdvdWxkIGxpa2UgdG8gc2VlIHdoYXQncyBjaGFuZ2VkLCB5b3UgY2FuIGVhc2lseSBzZWUgdGhh
dCBoZXJlOg0KPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJh
ZnQtaWV0Zi1wd2UzLXAybXAtcHctcmVxdWlyZW1lbnRzLTA2LnR4dCI+DQpodHRwczovL3Rvb2xz
LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRmLXB3ZTMtcDJtcC1wdy1yZXF1aXJlbWVu
dHMtMDYudHh0PC9hPiAuPGJyPg0KPGJyPg0KQ29pbmNpZGVudGFsbHksIHdlIGFyZSBhbHNvIHBv
bGxpbmcgZm9yIGtub3dsZWRnZSBvZiBJUFIgdGhhdDxicj4NCmFwcGxpZXMgdG8gdGhpcyBkcmFm
dCB0byBlbnN1cmUgdGhhdCBJUFIgaGFzIGJlZW4gZGlzY2xvc2VkIGluPGJyPg0KY29tcGxpYW5j
ZSB3aXRoIElFVEYgSVBSIHJ1bGVzIChzZWUgUkZDcyAzOTc5LCA0ODc5LCAzNjY5IGFuZCA1Mzc4
IDxicj4NCmZvciBtb3JlIGRldGFpbHMpLiBUbyBkYXRlLCB0aGVyZSBoYXZlIGJlZW4gbm8gSVBS
IGRlY2xhcmF0aW9ucyBvbiB0aGlzPGJyPg0KZHJhZnQuPGJyPg0KPGJyPg0KSWYgeW91IGFyZSBs
aXN0ZWQgYXMgYSBkb2N1bWVudCBhdXRob3Igb3IgY29udHJpYnV0b3IgcGxlYXNlIHJlc3BvbmQ8
YnI+DQp0byB0aGlzIGVtYWlsIHdoZXRoZXIgb3Igbm90IHlvdSBhcmUgYXdhcmUgb2YgYW55IGFk
ZGl0aW9uYWwgSVBSLiBUaGU8YnI+DQpkcmFmdCB3aWxsIG5vdCBiZSBmb3J3YXJkZWQgdG8gdGhl
IElFU0cgdW50aWwgYSByZXNwb25zZSBoYXMgYmVlbjxicj4NCnJlY2VpdmVkIGZyb20gZWFjaCBh
dXRob3IgYW5kIGNvbnRyaWJ1dG9yLiBTZWUgdGhlIGxpc3Qgb2YgY29udHJpYnV0aW5nPGJyPg0K
YXV0aG9ycyBpbiBTZWN0aW9uIDggdG8gcmVmcmVzaCB5b3VyIG1lbW9yeS48YnI+DQo8YnI+DQpJ
ZiB5b3UgYXJlIG9uIHRoZSBQV0UzIFdHIGVtYWlsIGxpc3QgYnV0IGFyZSBub3QgbGlzdGVkIGFz
IGFuIGF1dGhvcjxicj4NCm9yIGNvbnRyaWJ1dG9yLCB0aGVuIHBsZWFzZSBleHBsaWNpdGx5IHJl
c3BvbmQgb25seSBpZiB5b3UgYXJlIGF3YXJlPGJyPg0Kb2YgYW55IElQUiB0aGF0IGhhcyBub3Qg
eWV0IGJlZW4gZGlzY2xvc2VkIGluIGNvbmZvcm1hbmNlIHdpdGggSUVURjxicj4NCnJ1bGVzLjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIj5BbHNvLCBpZiB5b3UgYXJlIGxpc3RlZCBhcyBhbiBhdXRob3Ig
b3IgY29udHJpYnV0b3IgYW5kIHlvdXIgYWRkcmVzcyBpbmZvIGhhcyBjaGFuZ2VkLCBwbGVhc2Ug
ZW1haWwgYmFjayBwcml2YXRlbHkgc28gdGhhdCB3ZSBjYW4gZ2V0IHRoYXQgdXBkYXRlZCBiZWZv
cmUgc3VibWl0dGluZyBpdCB0byB0aGUgSUVTRy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyI+QmVjYXVz
ZSB0aGlzIGxhc3QgY2FsbCBzcGFucyB0aGUgSUVURiBtZWV0aW5nLCBpdCB3aWxsIGJlIG9wZW4g
Zm9yIHRocmVlIHdlZWtzLCBlbmRpbmcgb24gTm92ZW1iZXIgMTguPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1i
b3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyI+VGhhbmtzLDxicj4NCkFuZHk8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+
DQo=

--_000_1A095D7ECD89A64C9D3C77AE2DDE660B57F4552BC0007I0coenttco_--

From raggarwa_1@yahoo.com  Mon Nov  4 18:24:31 2013
Return-Path: <raggarwa_1@yahoo.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B706B21E8118 for <pwe3@ietfa.amsl.com>; Mon,  4 Nov 2013 18:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fS2fbEmYr3RK for <pwe3@ietfa.amsl.com>; Mon,  4 Nov 2013 18:24:23 -0800 (PST)
Received: from nm13-vm5.bullet.mail.ne1.yahoo.com (nm13-vm5.bullet.mail.ne1.yahoo.com [98.138.91.235]) by ietfa.amsl.com (Postfix) with ESMTP id 567F911E8245 for <pwe3@ietf.org>; Mon,  4 Nov 2013 18:24:22 -0800 (PST)
Received: from [98.138.100.115] by nm13.bullet.mail.ne1.yahoo.com with NNFMP; 05 Nov 2013 02:24:21 -0000
Received: from [98.138.89.172] by tm106.bullet.mail.ne1.yahoo.com with NNFMP; 05 Nov 2013 02:24:21 -0000
Received: from [127.0.0.1] by omp1028.mail.ne1.yahoo.com with NNFMP; 05 Nov 2013 02:24:21 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 704422.54400.bm@omp1028.mail.ne1.yahoo.com
Received: (qmail 22070 invoked by uid 60001); 5 Nov 2013 02:24:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1383618261; bh=xPFJMPvz3HUqYj1/B6jnHx4sw/TPAxASz6HH5UC1tes=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=gqLNMeFkkXcyeHVxFXN1slH7pxMK6dM9ebOB0EWJbZzcxf27Rb8V/+WIR0bRPJCDMuUUdk9K+3rcxMhg0RX0opuj0+prlyZHVYn/E7QiMO4jfW5zChb40fvlkq5EpDAwfcov4AVRyfsNVbkPY3MslBjm86fF9pxaxQIoXH5x36I=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=ElZfJW2D0DoS9MsRcjx72MhAf673AUwYzY9FpxMBB9q6AmK80zcqVO45XVCGH8ljBmw0AchX70osqZFj0dlscw3eriRf7s5ckrK/2AZ77PJviqSNcz4/M8f68uIO5eSkAtLSc4pH8elFStJI/3D7LSzLp0VllfPnxC9Qw89SBYQ=;
X-YMail-OSG: SBjOdvgVM1lCdxR3okSWLjD4KQIYP9Igh11TNbijLTzBD6t 0_8vX89oqmqcDBwURFjeb4bH3IWzmnIXQRoyoELf_z7ojy0LAYDYuepLJbPH Wo9_AFXurXrt0sFTS1LI7rTFvradcqGZkzCkpHAjbUcjRThGb6Sts6ng_aEa WXHmyvDlAm4P6SalwXDgLZGcWD_3xKHUSmGZqvJXn9mdTINSbWPU5gPhi7xR gzSnqVsCl8iU0FurRP2Y1w7hn_sndDJBgdQBstuYBYgYT5ePKPb0FQGOSzeP rfpUnxv1ZqB98W_YctE7JE2uwWtHMqTSeUyG86Ksv1.Fw0oCI_g1rzQ0N3Kp n1jZ_uqBZav624RU1StamqhZ2NmckGj6MggWMFWYEm0Nb9TlGMNm4e83TRow bleiOBVz8q1coN1L9gvBHLJEC..tzD3p4kA2uBE4gJzjn.npL1vuiqsp5B6p bbGqIhPejLsIla3Hd__IkQWF8xQqibRGT._SYYhtfRQPdJiPozJD2nQ6EfAX wqk4JCMd9o3cgfqQ4RD.zUjgAi8i_aOc_Gj_0lIcvMrv8j61vlkzrZLSQmoU 5848MFe9aLVGXI9jCAgj2G44WUHOHx4jInmJA
Received: from [50.174.16.100] by web120003.mail.ne1.yahoo.com via HTTP; Mon, 04 Nov 2013 18:24:21 PST
X-Rocket-MIMEInfo: 002.001, SSBhbSBub3QgYXdhcmUgb2YgYW55IGFkZGl0aW9uYWwgSVBSIHJlbGF0ZWQgdG8gdGhpcyBkcmFmdC4KCgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCiBGcm9tOiBZdWppIEthbWl0ZSA8eS5rYW1pdGVAbnR0LmNvbT4KVG86IEFuZHJldyBHLiBNYWxpcyA8YW1hbGlzQGdtYWlsLmNvbT47ICJwd2UzQGlldGYub3JnIiA8cHdlM0BpZXRmLm9yZz4gCkNjOiBSYWh1bCBBZ2dhcndhbCA8cmFnZ2Fyd2FfMUB5YWhvby5jb20.IApTZW50OiBUdWVzZGF5LCBOb3ZlbWJlciA1LCAyMDEzIDI6MDkgQU0BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.161.596
References: <CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com> <1A095D7ECD89A64C9D3C77AE2DDE660B57F45509@C0007I0.coe.ntt.com>
Message-ID: <1383618261.21713.YahooMailNeo@web120003.mail.ne1.yahoo.com>
Date: Mon, 4 Nov 2013 18:24:21 -0800 (PST)
From: Rahul Aggarwal <raggarwa_1@yahoo.com>
To: Yuji Kamite <y.kamite@ntt.com>, "Andrew G. Malis" <amalis@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
In-Reply-To: <1A095D7ECD89A64C9D3C77AE2DDE660B57F45509@C0007I0.coe.ntt.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-1007318780-1809654511-1383618261=:21713"
Subject: Re: [PWE3] Second WG last call (and IPR call) for	draft-ietf-pwe3-p2mp-pw-requirements
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Rahul Aggarwal <raggarwa_1@yahoo.com>
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 05 Nov 2013 02:24:31 -0000

---1007318780-1809654511-1383618261=:21713
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

I am not aware of any additional IPR related to this draft.=0A=0A=0A=0A=0A_=
_______________________________=0A From: Yuji Kamite <y.kamite@ntt.com>=0AT=
o: Andrew G. Malis <amalis@gmail.com>; "pwe3@ietf.org" <pwe3@ietf.org> =0AC=
c: Rahul Aggarwal <raggarwa_1@yahoo.com> =0ASent: Tuesday, November 5, 2013=
 2:09 AM=0ASubject: RE: [PWE3] Second WG last call (and IPR call) for=09dra=
ft-ietf-pwe3-p2mp-pw-requirements=0A =0A=0A=0AHi,=0A=C2=A0=0AI=E2=80=99m no=
t aware of any IPR information about this draft.=0A=C2=A0=0ABest regards,=
=0AYuji=0A=C2=A0=0A=C2=A0=0AFrom:pwe3-bounces@ietf.org [mailto:pwe3-bounces=
@ietf.org] On Behalf Of Andrew G. Malis=0ASent: Tuesday, October 29, 2013 2=
:56 AM=0ATo: pwe3@ietf.org=0ACc: Rahul Aggarwal=0ASubject: [PWE3] Second WG=
 last call (and IPR call) for draft-ietf-pwe3-p2mp-pw-requirements=0A=C2=A0=
=0APWE3ers,=0AYou may recall that almost exactly two years ago, we sent dra=
ft-ietf-pwe3-p2mp-pw-requirements-05 to the IESG. It was sent back to the W=
G in February of 2012, and it took a while, but we now have that rewrite to=
 submit back to the IESG.=0AHowever, because of the length of time, and the=
 fact that -06 just came out about a week ago (so few people have had a cha=
nce to re-read it), we are going to have a second WG last call before sendi=
ng it back to the IESG.=0ASo please review the draft, which you can find at=
 https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requirements-06 . If y=
ou would like to see what's changed, you can easily see that here: https://=
tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-p2mp-pw-requirements-06.txt .=
=0A=0ACoincidentally, we are also polling for knowledge of IPR that=0Aappli=
es to this draft to ensure that IPR has been disclosed in=0Acompliance with=
 IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 =0Afor more details). T=
o date, there have been no IPR declarations on this=0Adraft.=0A=0AIf you ar=
e listed as a document author or contributor please respond=0Ato this email=
 whether or not you are aware of any additional IPR. The=0Adraft will not b=
e forwarded to the IESG until a response has been=0Areceived from each auth=
or and contributor. See the list of contributing=0Aauthors in Section 8 to =
refresh your memory.=0A=0AIf you are on the PWE3 WG email list but are not =
listed as an author=0Aor contributor, then please explicitly respond only i=
f you are aware=0Aof any IPR that has not yet been disclosed in conformance=
 with IETF=0Arules.=0AAlso, if you are listed as an author or contributor a=
nd your address info has changed, please email back privately so that we ca=
n get that updated before submitting it to the IESG.=0A=C2=A0=0ABecause thi=
s last call spans the IETF meeting, it will be open for three weeks, ending=
 on November 18.=0AThanks,=0AAndy
---1007318780-1809654511-1383618261=:21713
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:12pt">I am not aware of any=
 additional IPR related to this draft.<br><div><span><br></span></div><div>=
<br></div>  <div style=3D"font-family: times new roman, new york, times, se=
rif; font-size: 12pt;"> <div style=3D"font-family: times new roman, new yor=
k, times, serif; font-size: 12pt;"> <div dir=3D"ltr"> <hr size=3D"1">  <fon=
t face=3D"Arial" size=3D"2"> <b><span style=3D"font-weight:bold;">From:</sp=
an></b> Yuji Kamite &lt;y.kamite@ntt.com&gt;<br> <b><span style=3D"font-wei=
ght: bold;">To:</span></b> Andrew G. Malis &lt;amalis@gmail.com&gt;; "pwe3@=
ietf.org" &lt;pwe3@ietf.org&gt; <br><b><span style=3D"font-weight: bold;">C=
c:</span></b> Rahul Aggarwal &lt;raggarwa_1@yahoo.com&gt; <br> <b><span sty=
le=3D"font-weight: bold;">Sent:</span></b> Tuesday, November 5, 2013 2:09 A=
M<br> <b><span style=3D"font-weight: bold;">Subject:</span></b> RE: [PWE3] =
Second WG last
 call (and IPR call) for=09draft-ietf-pwe3-p2mp-pw-requirements<br> </font>=
 </div> <div class=3D"y_msg_container"><br><div id=3D"yiv4360109180"><style=
>#yiv4360109180 #yiv4360109180 --=0A =0A _filtered #yiv4360109180 {panose-1=
:2 11 6 9 7 2 5 8 2 4;}=0A _filtered #yiv4360109180 {panose-1:2 11 6 9 7 2 =
5 8 2 4;}=0A _filtered #yiv4360109180 {panose-1:2 11 6 9 7 2 5 8 2 4;}=0A _=
filtered #yiv4360109180 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}=
=0A#yiv4360109180  =0A#yiv4360109180 p.yiv4360109180MsoNormal, #yiv43601091=
80 li.yiv4360109180MsoNormal, #yiv4360109180 div.yiv4360109180MsoNormal=0A=
=09{margin:0mm;margin-bottom:.0001pt;font-size:12.0pt;}=0A#yiv4360109180 a:=
link, #yiv4360109180 span.yiv4360109180MsoHyperlink=0A=09{color:blue;text-d=
ecoration:underline;}=0A#yiv4360109180 a:visited, #yiv4360109180 span.yiv43=
60109180MsoHyperlinkFollowed=0A=09{color:purple;text-decoration:underline;}=
=0A#yiv4360109180 span.yiv436010918017=0A=09{color:#1F497D;}=0A#yiv43601091=
80 .yiv4360109180MsoChpDefault=0A=09{}=0A _filtered #yiv4360109180 {margin:=
99.25pt 30.0mm 30.0mm 30.0mm;}=0A#yiv4360109180 div.yiv4360109180WordSectio=
n1=0A=09{}=0A#yiv4360109180 </style><div>=0A<div class=3D"yiv4360109180Word=
Section1">=0A<div class=3D"yiv4360109180MsoNormal"><span style=3D"font-size=
:10.0pt;" lang=3D"EN-US">Hi,</span></div> =0A<div class=3D"yiv4360109180Mso=
Normal"><span style=3D"font-size:10.0pt;" lang=3D"EN-US"> &nbsp;</span></di=
v> =0A<div class=3D"yiv4360109180MsoNormal"><span style=3D"font-size:10.0pt=
;" lang=3D"EN-US">I=E2=80=99m not aware of any IPR information about this d=
raft.</span></div> =0A<div class=3D"yiv4360109180MsoNormal"><span style=3D"=
font-size:10.0pt;" lang=3D"EN-US"> &nbsp;</span></div> =0A<div class=3D"yiv=
4360109180MsoNormal"><span style=3D"font-size:10.0pt;" lang=3D"EN-US">Best =
regards,</span></div> =0A<div class=3D"yiv4360109180MsoNormal"><span style=
=3D"font-size:10.0pt;" lang=3D"EN-US">Yuji</span></div> =0A<div class=3D"yi=
v4360109180MsoNormal"><span style=3D"font-size:10.0pt;" lang=3D"EN-US"> &nb=
sp;</span></div> =0A<div class=3D"yiv4360109180MsoNormal"><span style=3D"fo=
nt-size:10.0pt;" lang=3D"EN-US"> &nbsp;</span></div> =0A<div class=3D"yiv43=
60109180yqt9027208838" id=3D"yiv4360109180yqt91294"><div class=3D"yiv436010=
9180MsoNormal"><b><span style=3D"font-size:10.0pt;" lang=3D"EN-US">From:</s=
pan></b><span style=3D"font-size:10.0pt;" lang=3D"EN-US"> pwe3-bounces@ietf=
.org [mailto:pwe3-bounces@ietf.org]=0A<b>On Behalf Of </b>Andrew G. Malis<b=
r clear=3D"none">=0A<b>Sent:</b> Tuesday, October 29, 2013 2:56 AM<br clear=
=3D"none">=0A<b>To:</b> pwe3@ietf.org<br clear=3D"none">=0A<b>Cc:</b> Rahul=
 Aggarwal<br clear=3D"none">=0A<b>Subject:</b> [PWE3] Second WG last call (=
and IPR call) for draft-ietf-pwe3-p2mp-pw-requirements</span></div> =0A<div=
 class=3D"yiv4360109180MsoNormal"><span lang=3D"EN-US"> &nbsp;</span></div>=
 =0A<div>=0A<div>=0A<div>=0A<div>=0A<div>=0A<div class=3D"yiv4360109180MsoN=
ormal" style=3D"margin-bottom:12.0pt;"><span lang=3D"EN-US">PWE3ers,</span>=
</div> =0A</div>=0A<div class=3D"yiv4360109180MsoNormal" style=3D"margin-bo=
ttom:12.0pt;"><span lang=3D"EN-US">You may recall that almost exactly two y=
ears ago, we sent draft-ietf-pwe3-p2mp-pw-requirements-05 to the IESG. It w=
as sent back to the WG in February of 2012, and it took a while, but we now=
=0A have that rewrite to submit back to the IESG.</span></div> =0A</div>=0A=
<div class=3D"yiv4360109180MsoNormal" style=3D"margin-bottom:12.0pt;"><span=
 lang=3D"EN-US">However, because of the length of time, and the fact that -=
06 just came out about a week ago (so few people have had a chance to re-re=
ad it), we are going to have a second WG last call before=0A sending it bac=
k to the IESG.</span></div> =0A</div>=0A<div class=3D"yiv4360109180MsoNorma=
l" style=3D"margin-bottom:12.0pt;"><span lang=3D"EN-US">So please review th=
e draft, which you can find at=0A<a rel=3D"nofollow" shape=3D"rect" target=
=3D"_blank" href=3D"https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-req=
uirements-06">https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requireme=
nts-06</a> . If you would like to see what's changed, you can easily see th=
at here:=0A<a rel=3D"nofollow" shape=3D"rect" target=3D"_blank" href=3D"htt=
ps://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-p2mp-pw-requirements-06.=
txt">=0Ahttps://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-p2mp-pw-requi=
rements-06.txt</a> .<br clear=3D"none">=0A<br clear=3D"none">=0ACoincidenta=
lly, we are also polling for knowledge of IPR that<br clear=3D"none">=0Aapp=
lies to this draft to ensure that IPR has been disclosed in<br clear=3D"non=
e">=0Acompliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 <b=
r clear=3D"none">=0Afor more details). To date, there have been no IPR decl=
arations on this<br clear=3D"none">=0Adraft.<br clear=3D"none">=0A<br clear=
=3D"none">=0AIf you are listed as a document author or contributor please r=
espond<br clear=3D"none">=0Ato this email whether or not you are aware of a=
ny additional IPR. The<br clear=3D"none">=0Adraft will not be forwarded to =
the IESG until a response has been<br clear=3D"none">=0Areceived from each =
author and contributor. See the list of contributing<br clear=3D"none">=0Aa=
uthors in Section 8 to refresh your memory.<br clear=3D"none">=0A<br clear=
=3D"none">=0AIf you are on the PWE3 WG email list but are not listed as an =
author<br clear=3D"none">=0Aor contributor, then please explicitly respond =
only if you are aware<br clear=3D"none">=0Aof any IPR that has not yet been=
 disclosed in conformance with IETF<br clear=3D"none">=0Arules.</span></div=
> =0A</div>=0A<div>=0A<div class=3D"yiv4360109180MsoNormal"><span lang=3D"E=
N-US">Also, if you are listed as an author or contributor and your address =
info has changed, please email back privately so that we can get that updat=
ed before submitting it to the IESG.</span></div> =0A</div>=0A<div>=0A<div =
class=3D"yiv4360109180MsoNormal"><span lang=3D"EN-US"> &nbsp;</span></div> =
=0A</div>=0A<div>=0A<div class=3D"yiv4360109180MsoNormal" style=3D"margin-b=
ottom:12.0pt;"><span lang=3D"EN-US">Because this last call spans the IETF m=
eeting, it will be open for three weeks, ending on November 18.</span></div=
> =0A</div>=0A<div>=0A<div class=3D"yiv4360109180MsoNormal" style=3D"margin=
-bottom:12.0pt;"><span lang=3D"EN-US">Thanks,<br clear=3D"none">=0AAndy</sp=
an></div> =0A</div>=0A</div></div>=0A</div>=0A</div></div><br><br></div> </=
div> </div>  </div></body></html>
---1007318780-1809654511-1383618261=:21713--

From amalis@gmail.com  Mon Nov  4 19:43:01 2013
Return-Path: <amalis@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB7C21E811C for <pwe3@ietfa.amsl.com>; Mon,  4 Nov 2013 19:43:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.092
X-Spam-Level: 
X-Spam-Status: No, score=-103.092 tagged_above=-999 required=5 tests=[AWL=0.907, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001,  J_CHICKENPOX_33=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9IvVN3mz9-N2 for <pwe3@ietfa.amsl.com>; Mon,  4 Nov 2013 19:43:00 -0800 (PST)
Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id AFC4F21E81F1 for <pwe3@ietf.org>; Mon,  4 Nov 2013 19:42:52 -0800 (PST)
Received: by mail-oa0-f45.google.com with SMTP id i4so8140276oah.18 for <pwe3@ietf.org>; Mon, 04 Nov 2013 19:42:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=U1V22wonFkkPRblNS7Ks7ssZiNSqudolhWGGWBdb9m4=; b=maNAcyz+bFwvKE/HDr8c5D+gMV/VPPtHlTqhOz/EWzc/YYv0RiD1ZQsYhYfRtqzsSH viwuiq9nvIcM322itV6Ju7vY78F05MAfb7XOnEiF5sv7u76a2Vz9uSd8iRVcAW/0G4Eg OjF3HUuRvEJHrLsT1b8r9PQAf2RO9waSreFOyyM8hfpkrfwtJsQgK0kx0r9hCCZLBx/q iWrxdlkis0uFts4/UhptZGJD84o+ZyHlIUQ21j0xiW+uL1AEGaJGaHulBg/KrYoyTm30 9UgSd0QcgaTX9iP1BAVrK9Gc239eje4Dpt/SbQUtLz/TO4FnXW2/yASz38bcdQDutbP4 KewA==
X-Received: by 10.182.48.130 with SMTP id l2mr4723577obn.44.1383622972341; Mon, 04 Nov 2013 19:42:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.182.9 with HTTP; Mon, 4 Nov 2013 19:42:32 -0800 (PST)
In-Reply-To: <1A095D7ECD89A64C9D3C77AE2DDE660B57F4552B@C0007I0.coe.ntt.com>
References: <CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com> <1A095D7ECD89A64C9D3C77AE2DDE660B57F4552B@C0007I0.coe.ntt.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Date: Mon, 4 Nov 2013 22:42:32 -0500
Message-ID: <CAK+d4xv1_soG8s9b8pS4j-TU8JpKC8qCnnCmuv2kc8Ty0_56Ow@mail.gmail.com>
To: Yuji Kamite <y.kamite@ntt.com>
Content-Type: multipart/alternative; boundary=089e0160b3dcc502cf04ea65d3bb
Cc: Rahul Aggarwal <raggarwa_1@yahoo.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Second WG last call (and IPR call) for draft-ietf-pwe3-p2mp-pw-requirements
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 05 Nov 2013 03:43:01 -0000

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

Yugi,

Thanks!

Cheers,
Andy


On Mon, Nov 4, 2013 at 9:21 PM, Yuji Kamite <y.kamite@ntt.com> wrote:

>  Hi all,
>
>
>
> Just for your information, I will share the revised points from -05 to -06:
>
>
>
>
> --------------------------------------------------------------------------------
>
> Major changes:
>
>  - Removed multi-segment PWE cases all (Deleted Sec. 4.1-4.6 of old ver)
>
>      --> Only SS-PW is defined now: "SS P2MP-PW over P2MP-LSP."
>
>          MS-PW model is made out of scope of the document (Sec.1.2 in new
> ver)
>
> - Added explanation based on RFC5332 (multicast encap) (Sec. 3.2 in new
> ver)
>
>      --> Applied the basic notion of RFC5332 to PW context to justify the
> approach.
>
>          (Label assignment's detail is not requirement work, so just
> having reference to RFC5331.)
>
> - Removed ingress replication schemes (Sec. 3.2 in new ver)
>
>      --> Previous draft-05 used to have a method to combine multiple
> P2P/P2MP-LSPs for
>
>         conducting ingress replication.  But this is too complex and being
> apart from RFC5332.
>
>
>
> Editorial changes:
>
> - Adopted the latest boilerplate (xml2rfc)
>
> - Used convention terms (capital letters in RFC2119)
>
> - Any minor edits to remove MS-PW parts (e.g., terminology section)
>
>
> --------------------------------------------------------------------------------
>
>
>
> Regards,
>
> -Yuji
>
>
>
>
>
>
>
> *From:* pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] *On Behalf
> Of *Andrew G. Malis
> *Sent:* Tuesday, October 29, 2013 2:56 AM
> *To:* pwe3@ietf.org
> *Cc:* Rahul Aggarwal
> *Subject:* [PWE3] Second WG last call (and IPR call) for
> draft-ietf-pwe3-p2mp-pw-requirements
>
>
>
> PWE3ers,
>
> You may recall that almost exactly two years ago, we sent
> draft-ietf-pwe3-p2mp-pw-requirements-05 to the IESG. It was sent back to
> the WG in February of 2012, and it took a while, but we now have that
> rewrite to submit back to the IESG.
>
> However, because of the length of time, and the fact that -06 just came
> out about a week ago (so few people have had a chance to re-read it), we
> are going to have a second WG last call before sending it back to the IESG.
>
> So please review the draft, which you can find at
> https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requirements-06 . If
> you would like to see what's changed, you can easily see that here:
> https://tools.ietf.org/rfcdiff?url2=draft-ietf-pwe3-p2mp-pw-requirements-06.txt.
>
> Coincidentally, we are also polling for knowledge of IPR that
> applies to this draft to ensure that IPR has been disclosed in
> compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378
> for more details). To date, there have been no IPR declarations on this
> draft.
>
> If you are listed as a document author or contributor please respond
> to this email whether or not you are aware of any additional IPR. The
> draft will not be forwarded to the IESG until a response has been
> received from each author and contributor. See the list of contributing
> authors in Section 8 to refresh your memory.
>
> If you are on the PWE3 WG email list but are not listed as an author
> or contributor, then please explicitly respond only if you are aware
> of any IPR that has not yet been disclosed in conformance with IETF
> rules.
>
> Also, if you are listed as an author or contributor and your address info
> has changed, please email back privately so that we can get that updated
> before submitting it to the IESG.
>
>
>
> Because this last call spans the IETF meeting, it will be open for three
> weeks, ending on November 18.
>
> Thanks,
> Andy
>

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

<div dir=3D"ltr"><div><div>Yugi,<br><br>Thanks!<br><br></div>Cheers,<br></d=
iv>Andy<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quo=
te">On Mon, Nov 4, 2013 at 9:21 PM, Yuji Kamite <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:y.kamite@ntt.com" target=3D"_blank">y.kamite@ntt.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 link=3D"blue" vlink=3D"purple" lang=3D"JA">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;" lang=3D"EN-US">Hi all,<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;" lang=3D"EN-US"><u></u>=A0<u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;" lang=3D"EN-US">Just for your information,=
 I will share the revised points from -05 to -06:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;" lang=3D"EN-US"><u></u>=A0<u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;" lang=3D"EN-US">--------------------------=
------------------------------------------------------<u></u><u></u></span>=
</p>


<p><span lang=3D"EN-US">Major changes: <u></u><u></u></span></p>
<p><span lang=3D"EN-US">=A0- Removed multi-segment PWE cases all (Deleted S=
ec. 4.1-4.6 of old ver)<u></u><u></u></span></p>
<p><span lang=3D"EN-US">=A0=A0=A0=A0 --&gt; Only SS-PW is defined now: &quo=
t;SS P2MP-PW over P2MP-LSP.&quot;<u></u><u></u></span></p>
<p><span lang=3D"EN-US">=A0=A0=A0=A0=A0=A0=A0=A0 MS-PW model is made out of=
 scope of the document (Sec.1.2 in new ver)<u></u><u></u></span></p>
<p><span lang=3D"EN-US">- Added explanation based on RFC5332 (multicast enc=
ap) (Sec. 3.2 in new ver)<u></u><u></u></span></p>
<p><span lang=3D"EN-US">=A0=A0=A0=A0 --&gt; Applied the basic notion of RFC=
5332 to PW context to justify the approach.
<u></u><u></u></span></p>
<p><span lang=3D"EN-US">=A0=A0=A0=A0=A0=A0=A0=A0=A0(Label assignment&#39;s =
detail is not requirement work, so just having reference to RFC5331.)<u></u=
><u></u></span></p>
<p><span lang=3D"EN-US">- Removed ingress replication schemes (Sec. 3.2 in =
new ver)<u></u><u></u></span></p>
<p><span lang=3D"EN-US">=A0=A0=A0=A0 --&gt; Previous draft-05 used to have =
a method to combine multiple P2P/P2MP-LSPs for<u></u><u></u></span></p>
<p><span lang=3D"EN-US">=A0=A0=A0=A0=A0=A0=A0 conducting ingress replicatio=
n.=A0 But this is too complex and being apart from RFC5332.<u></u><u></u></=
span></p>
<p><span lang=3D"EN-US"><u></u>=A0<u></u></span></p>
<p><span lang=3D"EN-US">Editorial changes:<u></u><u></u></span></p>
<p><span lang=3D"EN-US">- Adopted the latest boilerplate (xml2rfc)<u></u><u=
></u></span></p>
<p><span lang=3D"EN-US">- Used convention terms (capital letters in RFC2119=
)<u></u><u></u></span></p>
<p><span lang=3D"EN-US">- Any minor edits to remove MS-PW parts (e.g., term=
inology section)<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;" lang=3D"EN-US">--------------------------=
------------------------------------------------------<u></u><u></u></span>=
</p>


<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;" lang=3D"EN-US"><u></u>=A0<u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;" lang=3D"EN-US">Regards,<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;" lang=3D"EN-US">-Yuji<u></u><u></u></span>=
</p><div class=3D"im">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#1f497d" lang=3D"EN-US"><u></u>=A0<u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#1f497d" lang=3D"EN-US"><u></u>=A0<u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#1f497d" lang=3D"EN-US"><u></u>=A0<u=
></u></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;" lang=3D"EN-US">From:</span></b><span =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&q=
uot;" lang=3D"EN-US"> <a href=3D"mailto:pwe3-bounces@ietf.org" target=3D"_b=
lank">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>Andrew G. Malis<br>
<b>Sent:</b> Tuesday, October 29, 2013 2:56 AM<br>
<b>To:</b> <a href=3D"mailto:pwe3@ietf.org" target=3D"_blank">pwe3@ietf.org=
</a><br>
<b>Cc:</b> Rahul Aggarwal<br>
<b>Subject:</b> [PWE3] Second WG last call (and IPR call) for draft-ietf-pw=
e3-p2mp-pw-requirements<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=A0<u></u></span></p>
</div><div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
PWE3ers,<u></u><u></u></span></p>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
You may recall that almost exactly two years ago, we sent draft-ietf-pwe3-p=
2mp-pw-requirements-05 to the IESG. It was sent back to the WG in February =
of 2012, and it took a while, but we now
 have that rewrite to submit back to the IESG.<u></u><u></u></span></p>
</div></div></div><div><div class=3D"h5">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
However, because of the length of time, and the fact that -06 just came out=
 about a week ago (so few people have had a chance to re-read it), we are g=
oing to have a second WG last call before
 sending it back to the IESG.<u></u><u></u></span></p>
</div></div></div><div><div class=3D"h5">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
So please review the draft, which you can find at
<a href=3D"https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requirements=
-06" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-=
requirements-06</a> . If you would like to see what&#39;s changed, you can =
easily see that here:
<a href=3D"https://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-p2mp-pw-re=
quirements-06.txt" target=3D"_blank">
https://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-p2mp-pw-requirements-=
06.txt</a> .<br>
<br>
Coincidentally, we are also polling for knowledge of IPR that<br>
applies to this draft to ensure that IPR has been disclosed in<br>
compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 <br>
for more details). To date, there have been no IPR declarations on this<br>
draft.<br>
<br>
If you are listed as a document author or contributor please respond<br>
to this email whether or not you are aware of any additional IPR. The<br>
draft will not be forwarded to the IESG until a response has been<br>
received from each author and contributor. See the list of contributing<br>
authors in Section 8 to refresh your memory.<br>
<br>
If you are on the PWE3 WG email list but are not listed as an author<br>
or contributor, then please explicitly respond only if you are aware<br>
of any IPR that has not yet been disclosed in conformance with IETF<br>
rules.<u></u><u></u></span></p>
</div></div></div><div><div class=3D"h5">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Also, if you are listed as an a=
uthor or contributor and your address info has changed, please email back p=
rivately so that we can get that updated before submitting it to the IESG.<=
u></u><u></u></span></p>


</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
Because this last call spans the IETF meeting, it will be open for three we=
eks, ending on November 18.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
Thanks,<br>
Andy<u></u><u></u></span></p>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div>

--089e0160b3dcc502cf04ea65d3bb--

From lizho.jin@gmail.com  Tue Nov  5 01:19:19 2013
Return-Path: <lizho.jin@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9C011E8267 for <pwe3@ietfa.amsl.com>; Tue,  5 Nov 2013 01:19:19 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0E9rfYwKq46P for <pwe3@ietfa.amsl.com>; Tue,  5 Nov 2013 01:19:18 -0800 (PST)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 1297C11E813D for <pwe3@ietf.org>; Tue,  5 Nov 2013 01:19:13 -0800 (PST)
Received: by mail-pa0-f46.google.com with SMTP id rd3so8385168pab.19 for <pwe3@ietf.org>; Tue, 05 Nov 2013 01:19:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :content-transfer-encoding:thread-index:content-language; bh=mhljvc7tiYraDtCreIDbOfQ03alv28sxAcTvcMiYXYM=; b=mVC2Lz0W4Un0vq2A5TIG65ykMdIO5N+riSO5BrpGWhfauORpc7hjCgJAg+PfrP57hQ nYmDpEVvpd2COeob0z7Zwa49v6nfo6aqxK25z8lD7DDq2Ad+6WVYm8KnHGPpRFSnv6Zo bQwDt4AXTVtiIy6zk6SCU9SGopLNnFBS1/LS9hQXOSo/KjJm4BarnxJwadtG6+GHOhbg aCdhkUuyjZiqVB02SW+jPImHdc7foT6mLAPGS+thd2D3umzQIYBbWcmfh+Ly3A3hkJMm lP33j3nm+zjpjmE7dRz1TMgJokqCeECXZLj+EN2uln8VQKLuPeImV+RVsT8YvkypxJOs GGTA==
X-Received: by 10.68.182.3 with SMTP id ea3mr22181314pbc.124.1383643153581; Tue, 05 Nov 2013 01:19:13 -0800 (PST)
Received: from LIZHONGJ ([180.166.53.21]) by mx.google.com with ESMTPSA id go4sm33325852pbb.15.2013.11.05.01.19.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 05 Nov 2013 01:19:12 -0800 (PST)
From: "Lizhong Jin" <lizho.jin@gmail.com>
To: <pwe3@ietf.org>
Date: Tue, 5 Nov 2013 17:19:06 +0800
Message-ID: <077d01ceda08$172ece20$458c6a60$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac7aB/euObsr4QVYQO+mK0lfTFfcyA==
Content-Language: zh-cn
Subject: Re: [PWE3] Second WG last call (and IPR call) for draft-ietf-pwe3-p2mp-pw-requirements
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 05 Nov 2013 09:19:19 -0000

Hi,
I'm not aware of any IPR related to this draft.

Lizhong

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

Message: 1
Date: Mon, 28 Oct 2013 13:56:01 -0400
From: "Andrew G. Malis" <amalis@gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Cc: Rahul Aggarwal <raggarwa_1@yahoo.com>
Subject: [PWE3] Second WG last call (and IPR call) for
	draft-ietf-pwe3-p2mp-pw-requirements
Message-ID:
	<CAK+d4xsvbGWT5MRLHV-0TbwpxSxwLvJHR+mx7qGaPGaWyVGe5w@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

PWE3ers,

You may recall that almost exactly two years ago, we sent
draft-ietf-pwe3-p2mp-pw-requirements-05 to the IESG. It was sent back to the
WG in February of 2012, and it took a while, but we now have that rewrite to
submit back to the IESG.

However, because of the length of time, and the fact that -06 just came out
about a week ago (so few people have had a chance to re-read it), we are
going to have a second WG last call before sending it back to the IESG.

So please review the draft, which you can find at
https://tools.ietf.org/html/draft-ietf-pwe3-p2mp-pw-requirements-06 . If you
would like to see what's changed, you can easily see that here:
https://tools.ietf.org/rfcdiff?url2=draft-ietf-pwe3-p2mp-pw-requirements-06.
txt.

Coincidentally, we are also polling for knowledge of IPR that applies to
this draft to ensure that IPR has been disclosed in compliance with IETF IPR
rules (see RFCs 3979, 4879, 3669 and 5378 for more details). To date, there
have been no IPR declarations on this draft.

If you are listed as a document author or contributor please respond to this
email whether or not you are aware of any additional IPR. The draft will not
be forwarded to the IESG until a response has been received from each author
and contributor. See the list of contributing authors in Section 8 to
refresh your memory.

If you are on the PWE3 WG email list but are not listed as an author or
contributor, then please explicitly respond only if you are aware of any IPR
that has not yet been disclosed in conformance with IETF rules.

Also, if you are listed as an author or contributor and your address info
has changed, please email back privately so that we can get that updated
before submitting it to the IESG.

Because this last call spans the IETF meeting, it will be open for three
weeks, ending on November 18.

Thanks,
Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.ietf.org/mail-archive/web/pwe3/attachments/20131028/3e70c6f3/att
achment.htm>

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

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


End of pwe3 Digest, Vol 114, Issue 13
*************************************


From zhangmingui@huawei.com  Thu Nov  7 14:15:44 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D84711E8282; Thu,  7 Nov 2013 14:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.467
X-Spam-Level: 
X-Spam-Status: No, score=-5.467 tagged_above=-999 required=5 tests=[AWL=1.131,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rm8c27hyyAZq; Thu,  7 Nov 2013 14:15:39 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 19C0F21E80B0; Thu,  7 Nov 2013 14:15:24 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAA55974; Thu, 07 Nov 2013 22:15:22 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 7 Nov 2013 22:14:33 +0000
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 7 Nov 2013 22:15:20 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.179]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Fri, 8 Nov 2013 06:15:12 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Thread-Topic: Why we consider the method of "label sharing for fast PE protection"
Thread-Index: AQHO2+geoImqeN4PM02OPNhQaq9T5JoaTP2jgAACoOM=
Date: Thu, 7 Nov 2013 22:15:10 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E733660E8C@nkgeml508-mbx.china.huawei.com>
References: <4552F0907735844E9204A62BBDD325E733660DBA@nkgeml508-mbx.china.huawei.com>, <2F3EBB88EC3A454AAB08915FBF0B8C7E02EB9CCC@eusaamb109.ericsson.se>
In-Reply-To: <2F3EBB88EC3A454AAB08915FBF0B8C7E02EB9CCC@eusaamb109.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.151.219]
Content-Type: multipart/alternative; boundary="_000_4552F0907735844E9204A62BBDD325E733660E8Cnkgeml508mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Why we consider the method of "label sharing for fast PE protection"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 07 Nov 2013 22:15:44 -0000

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

Hi Jakob,



There are three ways,



1. Always, this label can be configured.



2. We do have a companion draft to realize this. Please look at http://tool=
s.ietf.org/html/draft-zhang-pwe3-iccp-label-sharing-00 . We already present=
ed this draft in pwe3. (Let me copy this track to the pwe3 mailing list.) W=
ith the ICCP connection established, PEs can negotiate this label.



2. The last choice is to use a global label if it was supported.


Thanks,
Mingui
________________________________
From: Jakob Heitz [jakob.heitz@ericsson.com]
Sent: Friday, November 08, 2013 5:50
To: Mingui Zhang; l3vpn@ietf.org
Subject: RE: Why we consider the method of "label sharing for fast PE prote=
ction"

Several people at the mike asked this question:
How do you make sure that the PEs allocate the same label?

This needs to be part of the document, because it is quite important.
If an external entity allocates the labels, the protocol
between the PEs and that entity needs to be standardized.
Since this is a feature that provides redundancy, the
label allocating entity also needs to be backed up by a
redundant entity. The protocol between the redundant
label allocators needs to be standardized.


--

Jakob Heitz.

________________________________
From: l3vpn-bounces@ietf.org [l3vpn-bounces@ietf.org] on behalf of Mingui Z=
hang [zhangmingui@huawei.com]
Sent: Thursday, 07 November 2013 11:40 AM
To: l3vpn@ietf.org
Subject: Why we consider the method of "label sharing for fast PE protectio=
n"

Hi,

As a choice of fast PE protection,

1. This solution is simple and light-weight. We need not introduce the comp=
lex context label table in PE routers. So label table need not be stored re=
peatedly on RG members.

2. Also, it=92s easy to be deployed. It does not bring any change to P rout=
ers (control plane & data plane). It even does not change the data plane of=
 PE routers.

3. In addition, it does not bear the restriction of =93no penultimate-hop-p=
opping=94.

Thanks,
Mingui

--_000_4552F0907735844E9204A62BBDD325E733660E8Cnkgeml508mbxchi_
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">
<style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle=3D"1" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">
<p>Hi Jakob,</p>
<p>&nbsp;</p>
<p>There are three ways, </p>
<p>&nbsp;</p>
<p>1. Always, this label can be configured.</p>
<p>&nbsp;</p>
<p>2. We do have a companion draft to realize this. Please look at <a href=
=3D"http://tools.ietf.org/html/draft-zhang-pwe3-iccp-label-sharing-00">
http://tools.ietf.org/html/draft-zhang-pwe3-iccp-label-sharing-00</a>&nbsp;=
.&nbsp;We already presented this draft in pwe3. (Let me&nbsp;copy this trac=
k to the pwe3 mailing list.)&nbsp;With the ICCP connection established, PEs=
 can&nbsp;negotiate this label.
</p>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">&nbsp;</div>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">
<p>2. The last choice is to use a global label if it was supported.</p>
</div>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">&nbsp;</div>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">Thanks,</div>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">Mingui</div>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">
<hr tabindex=3D"-1">
<div style=3D"DIRECTION: ltr" id=3D"divRpF636724"><font color=3D"#000000" s=
ize=3D"2" face=3D"Tahoma"><b>From:</b> Jakob Heitz [jakob.heitz@ericsson.co=
m]<br>
<b>Sent:</b> Friday, November 08, 2013 5:50<br>
<b>To:</b> Mingui Zhang; l3vpn@ietf.org<br>
<b>Subject:</b> RE: Why we consider the method of &quot;label sharing for f=
ast PE protection&quot;<br>
</font><br>
</div>
<div></div>
<div>
<div style=3D"FONT-FAMILY: Lucida Console; DIRECTION: ltr; COLOR: #993366; =
FONT-SIZE: 10pt">
<div>Several people at the mike asked this question:</div>
How do you make sure that the PEs allocate the same label?
<div><br>
<div>This needs to be part of the document, because it is quite important.<=
/div>
<div>If an external entity allocates the labels, the protocol</div>
<div>between the PEs and that entity needs to be standardized.</div>
<div>Since this is a feature that provides redundancy, the</div>
<div>label allocating entity also needs to be backed up by a</div>
<div>redundant entity. The protocol between the redundant</div>
<div>label allocators needs to be standardized.<br>
<div><br>
<div style=3D"FONT-FAMILY: Tahoma; FONT-SIZE: 13px">
<p>--</p>
<p>Jakob Heitz.</p>
</div>
</div>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">
<hr tabindex=3D"-1">
<div style=3D"DIRECTION: ltr" id=3D"divRpF173592"><font color=3D"#000000" s=
ize=3D"2" face=3D"Tahoma"><b>From:</b> l3vpn-bounces@ietf.org [l3vpn-bounce=
s@ietf.org] on behalf of Mingui Zhang [zhangmingui@huawei.com]<br>
<b>Sent:</b> Thursday, 07 November 2013 11:40 AM<br>
<b>To:</b> l3vpn@ietf.org<br>
<b>Subject:</b> Why we consider the method of &quot;label sharing for fast =
PE protection&quot;<br>
</font><br>
</div>
<div></div>
<div>
<div style=3D"FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZ=
E: 10pt">
<p style=3D"LINE-HEIGHT: normal; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><=
span style=3D"LAYOUT-GRID-MODE: both; FONT-FAMILY: 'Arial','sans-serif'; FO=
NT-SIZE: 11pt" lang=3D"EN-US">Hi,<br>
&nbsp;<br>
As a choice of fast PE protection, <br>
&nbsp;<br>
1. This solution is simple and light-weight. We need not introduce the comp=
lex context label table in PE routers. So label table need not be stored&nb=
sp;repeatedly on RG members.</span></p>
<span style=3D"LAYOUT-GRID-MODE: both; FONT-FAMILY: 'Arial','sans-serif'; F=
ONT-SIZE: 11pt" lang=3D"EN-US">
<p style=3D"LINE-HEIGHT: normal; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><=
br>
2. Also, it=92s easy to be deployed. It does not bring any change to P rout=
ers (control plane &amp; data plane). It even does not change the data plan=
e of PE routers.</p>
<p style=3D"LINE-HEIGHT: normal; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><=
br>
3. In addition, it does not bear the restriction of =93no penultimate-hop-p=
opping=94.</p>
<p style=3D"LINE-HEIGHT: normal; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><=
span style=3D"LAYOUT-GRID-MODE: both; FONT-FAMILY: 'Arial','sans-serif'; FO=
NT-SIZE: 11pt" lang=3D"EN-US"></span>&nbsp;</p>
<p style=3D"LINE-HEIGHT: normal; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><=
span style=3D"LAYOUT-GRID-MODE: both; FONT-FAMILY: 'Arial','sans-serif'; FO=
NT-SIZE: 11pt" lang=3D"EN-US">Thanks,<br>
Mingui<br>
</span></p>
</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_4552F0907735844E9204A62BBDD325E733660E8Cnkgeml508mbxchi_--

From rraszuk@gmail.com  Fri Nov  8 22:20:32 2013
Return-Path: <rraszuk@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D196911E8100; Fri,  8 Nov 2013 22:20:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level: 
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NjvCBJUoEPUU; Fri,  8 Nov 2013 22:20:32 -0800 (PST)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2628311E80E7; Fri,  8 Nov 2013 22:20:31 -0800 (PST)
Received: by mail-ie0-f170.google.com with SMTP id at1so4815125iec.15 for <multiple recipients>; Fri, 08 Nov 2013 22:20:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=pnVsQgy79nSZm1oGcUgWHTollFDy1wznQ0OjeMevqXo=; b=BJR34vi4F6JLQjW1scPSuVhl5UyYOw8CKxzXO2BYPFCCM7YpYTUbfKAh+fzjmGbkGV mNYqq+QpX7o6KpH+Lm9VTK2++ieY0pq5X0oxMom0pG6uTSuDIbLX7nxusDx/TmC84gBI x9ijd0BgPbSa1p1CdPYPAkXhhqh4XFycKrcNEoHlTTAuBPedOHH42XSVfkIiyLwlL6pN WVFUXhtkpywCMPDEc5yrvJ35e9/EHlNIJ4OKKbC0lBzWp3aXXaqYZ7SXVrt+OFzYd19N l+zWDeQ3UVPUm3iFPa8kaauj4wSF3pHPUqy06lhStiH9TKU5JPzDPCGcBiLr8wVaFySu u7yw==
MIME-Version: 1.0
X-Received: by 10.50.117.103 with SMTP id kd7mr5482569igb.4.1383978028020; Fri, 08 Nov 2013 22:20:28 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.61.129 with HTTP; Fri, 8 Nov 2013 22:20:27 -0800 (PST)
In-Reply-To: <4552F0907735844E9204A62BBDD325E733660E8C@nkgeml508-mbx.china.huawei.com>
References: <4552F0907735844E9204A62BBDD325E733660DBA@nkgeml508-mbx.china.huawei.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E02EB9CCC@eusaamb109.ericsson.se> <4552F0907735844E9204A62BBDD325E733660E8C@nkgeml508-mbx.china.huawei.com>
Date: Sat, 9 Nov 2013 07:20:27 +0100
X-Google-Sender-Auth: 7KZb6tGUQkNU4SdN1Wj4j9UdeoQ
Message-ID: <CA+b+ERnZO8UN3Ofkn_DfVyYRxp7J5z=SABOY7LkqWqSXj575VA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Mingui Zhang <zhangmingui@huawei.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: Jakob Heitz <jakob.heitz@ericsson.com>, "pwe3@ietf.org" <pwe3@ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Subject: Re: [PWE3] Why we consider the method of "label sharing for fast PE protection"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 09 Nov 2013 06:20:33 -0000

Hi Mingui,

If your implementation configures a same VPN label across N sites
manual or by SDN magic you are free to advertise it along with VPNv4
routes. I am not sure why any draft is needed for that at all. After
all it is your implementation.

To the best of my knowledge L3VPN spec does not prohibit in any RFC to
advertise the same label across N PEs. In fact it does not mandate any
correlation of label value across PEs so you are pretty free to go.

However if you go that path please notice that this is not just about
.. "let's configure same VPN label".

We do have three types of VPN labels:

- per vrf
- per next hop
- per prefix

I am a bit implicitly assuming you are talking about per vrf label
only. Other modes of label allocation would be rather cumbersome to be
done manually or even programmatically as their appearance and
allocation must be coordinated with new CE or new VPN advertisement in
any VPN site and across existence of already provisioned sites.

As Eric mentioned today devil is in details and where you go down to
actually implement robust solution I can bet that you will start very
much to like to concept of context labels for protection and
independent VPN (or for that matter any other application - pwe3/l2vpn
etc) label allocation pardigm :)

Best regards,
R.





On Thu, Nov 7, 2013 at 11:15 PM, Mingui Zhang <zhangmingui@huawei.com> wrot=
e:
> Hi Jakob,
>
>
>
> There are three ways,
>
>
>
> 1. Always, this label can be configured.
>
>
>
> 2. We do have a companion draft to realize this. Please look at
> http://tools.ietf.org/html/draft-zhang-pwe3-iccp-label-sharing-00 . We
> already presented this draft in pwe3. (Let me copy this track to the pwe3
> mailing list.) With the ICCP connection established, PEs can negotiate th=
is
> label.
>
>
>
> 2. The last choice is to use a global label if it was supported.
>
>
> Thanks,
> Mingui
> ________________________________
> From: Jakob Heitz [jakob.heitz@ericsson.com]
> Sent: Friday, November 08, 2013 5:50
> To: Mingui Zhang; l3vpn@ietf.org
> Subject: RE: Why we consider the method of "label sharing for fast PE
> protection"
>
> Several people at the mike asked this question:
> How do you make sure that the PEs allocate the same label?
>
> This needs to be part of the document, because it is quite important.
> If an external entity allocates the labels, the protocol
> between the PEs and that entity needs to be standardized.
> Since this is a feature that provides redundancy, the
> label allocating entity also needs to be backed up by a
> redundant entity. The protocol between the redundant
> label allocators needs to be standardized.
>
> --
>
> Jakob Heitz.
>
> ________________________________
> From: l3vpn-bounces@ietf.org [l3vpn-bounces@ietf.org] on behalf of Mingui
> Zhang [zhangmingui@huawei.com]
> Sent: Thursday, 07 November 2013 11:40 AM
> To: l3vpn@ietf.org
> Subject: Why we consider the method of "label sharing for fast PE
> protection"
>
> Hi,
>
> As a choice of fast PE protection,
>
> 1. This solution is simple and light-weight. We need not introduce the
> complex context label table in PE routers. So label table need not be sto=
red
> repeatedly on RG members.
>
>
> 2. Also, it=92s easy to be deployed. It does not bring any change to P ro=
uters
> (control plane & data plane). It even does not change the data plane of P=
E
> routers.
>
>
> 3. In addition, it does not bear the restriction of =93no
> penultimate-hop-popping=94.
>
>
>
> Thanks,
> Mingui

From zhangmingui@huawei.com  Sat Nov  9 00:33:14 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 656B821F9F19; Sat,  9 Nov 2013 00:33:14 -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.605,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bluFnTIrR7ar; Sat,  9 Nov 2013 00:33:10 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7B82A21F9F01; Sat,  9 Nov 2013 00:33:09 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAB76209; Sat, 09 Nov 2013 08:33:07 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 9 Nov 2013 08:32:59 +0000
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 9 Nov 2013 08:33:02 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.179]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Sat, 9 Nov 2013 16:32:57 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: Robert Raszuk <robert@raszuk.net>
Thread-Topic: Why we consider the method of "label sharing for fast PE protection"
Thread-Index: AQHO2+geoImqeN4PM02OPNhQaq9T5JoaTP2jgAACoOOAAZoGgIAAp16e
Date: Sat, 9 Nov 2013 08:32:57 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7336612A0@nkgeml508-mbx.china.huawei.com>
References: <4552F0907735844E9204A62BBDD325E733660DBA@nkgeml508-mbx.china.huawei.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E02EB9CCC@eusaamb109.ericsson.se> <4552F0907735844E9204A62BBDD325E733660E8C@nkgeml508-mbx.china.huawei.com>, <CA+b+ERnZO8UN3Ofkn_DfVyYRxp7J5z=SABOY7LkqWqSXj575VA@mail.gmail.com>
In-Reply-To: <CA+b+ERnZO8UN3Ofkn_DfVyYRxp7J5z=SABOY7LkqWqSXj575VA@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.148.66]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Jakob Heitz <jakob.heitz@ericsson.com>, "pwe3@ietf.org" <pwe3@ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Subject: Re: [PWE3] Why we consider the method of "label sharing for fast PE protection"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 09 Nov 2013 08:33:14 -0000

Hi Robert,

Thanks for your comments!

>If your implementation configures a same VPN label across N sites
>manual or by SDN magic you are free to advertise it along with VPNv4
>routes. I am not sure why any draft is needed for that at all. After
>all it is your implementation.

[ZMG] The point is that each PE used to allocate the VPN label for each VRF=
 locally without knowing what label has been assigned by other PEs. Now, we=
 need them =93happen to=94 allocate the same label for each VRF.=20
>To the best of my knowledge L3VPN spec does not prohibit in any RFC to
>advertise the same label across N PEs. In fact it does not mandate any
>correlation of label value across PEs so you are pretty free to go.

[ZMG] Or you can speak in this way. It=92s free for this draft to mandate a=
 REQ to the label allocation that PEs in a Redundant Group always allocate =
the same label for each VRF.

<snip>
>I am a bit implicitly assuming you are talking about per vrf label
>only.=20

[ZMG] Yes, you are right. We are assuming the =93per VRF=94 allocation in o=
ur draft for the sake of scalability.=20

>Other modes of label allocation would be rather cumbersome=20

[ZMG] I agree with you. Other two finer grained label allocations are not r=
ecommended.=20

<snip>
>As Eric mentioned today devil is in details and where you go down to
>actually implement robust solution I can bet that you will start very
>much to like to concept of context labels for protection and
>independent VPN (or for that matter any other application - pwe3/l2vpn
>etc) label allocation pardigm :)

[ZMG] I believe when Eric made that statement, he assumed the label allocat=
ion was done by a =93SDN central controller=94. I guess that was simply an =
abstraction caused by the chaos of the =93central controlled=94 conception.=
=20

[ZMG] To make the discussion clear, let=92s forget about the =93central con=
trolled=94 like stuff from now on. We proposed the draft leveraging ICCP co=
nnection to do the label negotiation. Please focus on that choice.  ICCP ha=
s already provided that robustness. Why reinvent the wheel? :)

Regards,
Mingui



________________________________________
From: rraszuk@gmail.com [rraszuk@gmail.com] on behalf of Robert Raszuk [rob=
ert@raszuk.net]
Sent: Saturday, November 09, 2013 14:20
To: Mingui Zhang
Cc: Jakob Heitz; l3vpn@ietf.org; pwe3@ietf.org
Subject: Re: Why we consider the method of "label sharing for fast PE prote=
ction"

Hi Mingui,

If your implementation configures a same VPN label across N sites
manual or by SDN magic you are free to advertise it along with VPNv4
routes. I am not sure why any draft is needed for that at all. After
all it is your implementation.

To the best of my knowledge L3VPN spec does not prohibit in any RFC to
advertise the same label across N PEs. In fact it does not mandate any
correlation of label value across PEs so you are pretty free to go.

However if you go that path please notice that this is not just about
.. "let's configure same VPN label".

We do have three types of VPN labels:

- per vrf
- per next hop
- per prefix

I am a bit implicitly assuming you are talking about per vrf label
only. Other modes of label allocation would be rather cumbersome to be
done manually or even programmatically as their appearance and
allocation must be coordinated with new CE or new VPN advertisement in
any VPN site and across existence of already provisioned sites.

As Eric mentioned today devil is in details and where you go down to
actually implement robust solution I can bet that you will start very
much to like to concept of context labels for protection and
independent VPN (or for that matter any other application - pwe3/l2vpn
etc) label allocation pardigm :)

Best regards,
R.





On Thu, Nov 7, 2013 at 11:15 PM, Mingui Zhang <zhangmingui@huawei.com> wrot=
e:
> Hi Jakob,
>
>
>
> There are three ways,
>
>
>
> 1. Always, this label can be configured.
>
>
>
> 2. We do have a companion draft to realize this. Please look at
> http://tools.ietf.org/html/draft-zhang-pwe3-iccp-label-sharing-00 . We
> already presented this draft in pwe3. (Let me copy this track to the pwe3
> mailing list.) With the ICCP connection established, PEs can negotiate th=
is
> label.
>
>
>
> 2. The last choice is to use a global label if it was supported.
>
>
> Thanks,
> Mingui
> ________________________________
> From: Jakob Heitz [jakob.heitz@ericsson.com]
> Sent: Friday, November 08, 2013 5:50
> To: Mingui Zhang; l3vpn@ietf.org
> Subject: RE: Why we consider the method of "label sharing for fast PE
> protection"
>
> Several people at the mike asked this question:
> How do you make sure that the PEs allocate the same label?
>
> This needs to be part of the document, because it is quite important.
> If an external entity allocates the labels, the protocol
> between the PEs and that entity needs to be standardized.
> Since this is a feature that provides redundancy, the
> label allocating entity also needs to be backed up by a
> redundant entity. The protocol between the redundant
> label allocators needs to be standardized.
>
> --
>
> Jakob Heitz.
>
> ________________________________
> From: l3vpn-bounces@ietf.org [l3vpn-bounces@ietf.org] on behalf of Mingui
> Zhang [zhangmingui@huawei.com]
> Sent: Thursday, 07 November 2013 11:40 AM
> To: l3vpn@ietf.org
> Subject: Why we consider the method of "label sharing for fast PE
> protection"
>
> Hi,
>
> As a choice of fast PE protection,
>
> 1. This solution is simple and light-weight. We need not introduce the
> complex context label table in PE routers. So label table need not be sto=
red
> repeatedly on RG members.
>
>
> 2. Also, it=92s easy to be deployed. It does not bring any change to P ro=
uters
> (control plane & data plane). It even does not change the data plane of P=
E
> routers.
>
>
> 3. In addition, it does not bear the restriction of =93no
> penultimate-hop-popping=94.
>
>
>
> Thanks,
> Mingui=

From internet-drafts@ietf.org  Mon Nov 11 13:57:00 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B231621E8089; Mon, 11 Nov 2013 13:57:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.436
X-Spam-Level: 
X-Spam-Status: No, score=-102.436 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SrrIho5QwqnN; Mon, 11 Nov 2013 13:57:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4467411E8114; Mon, 11 Nov 2013 13:57:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131111215700.20279.65906.idtracker@ietfa.amsl.com>
Date: Mon, 11 Nov 2013 13:57:00 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action: draft-ietf-pwe3-mpls-tp-cv-adv-02.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Nov 2013 21:57:00 -0000

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

	Title           : VCCV MPLS-TP Connectivity Verification (CV) Capability A=
dvertisement
	Author(s)       : Greg Mirsky
	Filename        : draft-ietf-pwe3-mpls-tp-cv-adv-02.txt
	Pages           : 7
	Date            : 2013-11-11

Abstract:
   This document specifies how use of proactive Connectivity
   Verification, Continuity Check, and Remote Defect Indication for the
   MPLS Transport Profile [RFC6428] affects operation and management
   function election for PW VCCV [RFC5085], [RFC5885].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-cv-adv

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-cv-adv-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-mpls-tp-cv-adv-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From gregory.mirsky@ericsson.com  Mon Nov 11 14:01:21 2013
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7596E21E8092 for <pwe3@ietfa.amsl.com>; Mon, 11 Nov 2013 14:01:21 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5GfwHIDel7v for <pwe3@ietfa.amsl.com>; Mon, 11 Nov 2013 14:01:15 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 7634B11E80F9 for <pwe3@ietf.org>; Mon, 11 Nov 2013 14:01:15 -0800 (PST)
X-AuditID: c6180641-b7fbd8e0000011cc-84-528153a95c69
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 87.E5.04556.9A351825; Mon, 11 Nov 2013 23:01:13 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0328.009; Mon, 11 Nov 2013 17:01:13 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "Andrew G. Malis" <amalis@gmail.com>
Thread-Topic: Shepherd's review of draft-ietf-pwe3-mpls-tp-cv-adv-01
Thread-Index: AQHOz2XLYUaC0PamkE6Z/HzHOxwGypogs6AA
Date: Mon, 11 Nov 2013 22:01:13 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B70FFAE@eusaamb103.ericsson.se>
References: <CAK+d4xt5TFG604PpQ74u-4_9-i_i6spDx0oeMiycbEcN2qmdPA@mail.gmail.com>
In-Reply-To: <CAK+d4xt5TFG604PpQ74u-4_9-i_i6spDx0oeMiycbEcN2qmdPA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/mixed; boundary="_004_7347100B5761DC41A166AC17F22DF1121B70FFAEeusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA2WSf0yMcRzHfZ/nueeebuHrXPrIZXRrGiKn6UJoYdnQL8OYH4dnNOF2V80/ pqSVc6ym6I500Y9DarhRRK0dhzRibEQTknRMp5wzi7vne6zx3+v92fv7+Xyez/vhaKmRDeJS d6fz2t3qtBBWwhzLaFwTfi4lOzmixjVP1fm0Sqw66rQyi6j4BtMrcXxFhZtKpNZJ5m/j01Iz ee3MBZslO159PIA0d+3U3sJOM5WFHhdTeuTHAY6E0rxnPh4HjzrrWD2ScFJsQ9Dk7qOIqEbQ cqKM9bpYrIQPlwxiL8twGJj7HwqvaayAaydzBM9YHAefC14zxLMYrtrdtB5xHlbC4BuhzOBQ MOdYRF4eiVdA/fHTyMtSnAh6a7nQxg8ngdlUJ7RHnuVc92t8owLhxbsy39Iy6GpvZQkHQO/b IRFhBbhOkVk0ToUu102azBoD94zvmAIUYBrWyjTMZhpmI/U98LzyPCI8Hcw3nCzhaVBV3kf/ 4QfNb6n/63K4UnzI81bi4VwEOYYmQUixFYG75D1NxCUEPZYrYiIaELQVlfpsRQjMxocMEQUI HM/ahOlSfNUTii3pr8tpyBdWZPE8qLXYBZMMzwbjt6++dUlAJiGgWDj4vUpkEkJZCo23dMQ+ A/SOATGxRIGhuFb4Cm9YZT/PishlYqGneUio++M5kJ9dwxLWQN29iz7WQcndXPbfC4Pneo7C kz6OAWvHHdqMos4jLkPHZ+7arpx1GXl+7zvAxtYjszO6BU3gmJDAkQOf4pKleLs6nd/J8xpe u0mbkcbrWhDF+QVloTE2ZeEC+UzFk/jSwYgfuG/ZypTQdLt0Y/aGl41b/Zsnt55RBS/nNh6O Lof2TYxG+mW1fMs+u6PeGNw/IiZlLd/ds/Z2gyr4NXTLqhOWLC8Yb2vtHV25PzwvuiPSMeXX qtqF8nFTD4RVKkp6r8sDEyYdyYs4O2LUxNDNlo71uXOpCyGMbod61lRaq1P/BkD9/IesAwAA
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Shepherd's review of draft-ietf-pwe3-mpls-tp-cv-adv-01
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Nov 2013 22:01:21 -0000

--_004_7347100B5761DC41A166AC17F22DF1121B70FFAEeusaamb103erics_
Content-Type: multipart/alternative;
	boundary="_000_7347100B5761DC41A166AC17F22DF1121B70FFAEeusaamb103erics_"

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

Dear Andy, et. al,
I've posted updated version to address idnits and the shepherd's comments.
Please let me know if there's anything I can help with.

                Regards,
                                Greg


From: Andrew G. Malis [mailto:amalis@gmail.com]
Sent: Tuesday, October 22, 2013 1:32 PM
To: Gregory Mirsky
Cc: pwe3@ietf.org
Subject: Shepherd's review of draft-ietf-pwe3-mpls-tp-cv-adv-01

Greg,
As document shepherd for draft-ietf-pwe3-mpls-tp-cv-adv, I did a WG last ca=
ll review and have some comments. The good news is that the draft is mostly=
 in good shape for publication, it just needs a quick revision to address t=
he comments below. Also, there were no other WG last call comments which ne=
ed to be addressed.
First of all, there are some idnits issues that need to be addressed:

  Miscellaneous warnings:

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



  =3D=3D The document doesn't use any RFC 2119 keywords, yet seems to have =
RFC

     2119 boilerplate text.



  -- The document date (September 20, 2013) is 32 days in the past.  Is thi=
s

     intentional?





  Checking references for intended status: Proposed Standard

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



     (See RFCs 3967 and 4897 for information about using normative referenc=
es

     to lower-maturity documents in RFCs)



  =3D=3D Unused Reference: 'RFC5882' is defined on line 270, but no explici=
t

     reference was found in the text



  -- Obsolete informational reference (is this intentional?): RFC 2434

     (Obsoleted by RFC 5226)
I also have some comments of my own, which are mostly editorial in nature. =
They are embedded in the text below. Just do an update to address the nits =
and these comments, and I'll be able to forward the draft for publication.

Thanks,
Andy

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

1.  Introduction

   Proactive Connectivity Verification (CV), Continuity Check (CC), and
   Remote Defect Indication (RDI) for the MPLS Transport Profile
   [RFC6428] are applicable to all constructs of the MPLS-TP, including
   pseudowires (PWs).  If Control Plane is used to operate and manage PW
s/Control Plane/a control plane/
s/PW/PWs/
   then procedure defined in [RFC5085] and [RFC5885] should be used to
s/procedure/the procedures/
   select proper type of Control Channel and corresponding type of
   Connectivity Verification.  This document specifies how signaling and
   selection process modified to ensure backward compatibility and allow
s/process modified/processes are modified/
   use of proactive CV-CC-RDI over MPLS-TP PWs.

1.1.  Conventions used in this document

1.1.1.  Terminology

   BFD: Bidirectional Forwarding Detection

   CC: Continuity Check

   CV: Connectivity Verification

   PE: Provider Edge

   VCCV: Virtual Circuit Connectivity Verification

   VCCV CC: VCCV Control Channel

1.1.2.  Requirements Language

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


2.  MPLS-TP CC-CV on Pseudowires

   PW VCCV can support several CV Types.  Ability to support arbitrary
s/Types.  Ability to support/Types, and can support/
   combination of CV modes advertised in CV Types field of VCCV
s/in CV/in the CV/
   Interface Parameter sub-TLV [RFC4446], [RFC4447].  Currently six
   types of CV been defined for PW VCCV out of eight bit long field.
s/VCCV out of eight bit long field/VCCV/
   This document introduces four new CV types and, to accommodate them,
   a new VCCV Extended CV parameter for PW Interface Parameters Sub-TLV
   is defined.






Mirsky                   Expires March 24, 2014                 [Page 3]

Internet-Draft               VCCV MPLS-TP CV              September 2013


2.1.  VCCV Extended CV Advertisement sub-TLV

   The format of VCCV Extended CV Advertisement is a TLV where:

    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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | Type =3D 0x19 |    Length     |   CV Type    |   Reserved     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                Figure 1: VCCV Extended CV parameter format

   Length - the length of the sub-TLV, including type and the Length
s/Length -/The Length field is/
   field itself.  Minimum length is 4.  It it isrecommended that
s/Minimum/The minimum/
   extensions to the sub-TLV be done in 4 bytes increments with Reserved
   field being set to zero on transmit and ignored on receipt.

   Reserved field must be set to zeroes on transmit and ignored on
   receive.
s/Reserved/The Reserved/

   CV Type field is a bitmask that lists types of CV monitoring that a
s/CV Type/The CV Type/
   PE is capable to support.  VCCV Extended CV parameter sub-TLV must
s/VCCV/The VCCV/
   appear in combination with VCCV parameter sub-TLV.  If VCCV parameter
s/VCCV/the VCCV/ (twice in this line)
   sub-TLV is missing then VCCV Extended CV parameter sub-TLV should be
s/VCCV/the VCCV/
   ignored.

2.2.  MPLS-TP CC-CV Types

   The [RFC6428] defines coordinated and independent modes of monitoring
S/The //
   point-to-point bi-directional connection that can be applied to
   monitoring PWs.  At the same time [RFC6310] defines how BFD-based OAM
   can map and be mapped to status of an Attachment Circuit.  Thus there
   could be four MPLS-TP CV types as combination of modes and
   functionality:

   +---------------+-------------------+-------------------------------+
   |     Modes     |  Fault Detection  |   Fault Detection and Status  |
   |               |        Only       |           Signalling          |
   +---------------+-------------------+-------------------------------+
   |  Independent  |        0x01       |              0x02             |
   |      Mode     |                   |                               |
   |  Coordinated  |        0x04       |              0x08             |
   |      Mode     |                   |                               |
   +---------------+-------------------+-------------------------------+

               Table 1: Bitmask Values for MPLS-TP CV Types





Mirsky                   Expires March 24, 2014                 [Page 4]

Internet-Draft               VCCV MPLS-TP CV              September 2013


2.3.  MPLS-TP CC-CV Type Operation

   Connectivity verification according to [RFC6428] is part of MPLS-TP
   CC/CV operation that can be used with VCCV Control Channel Type 1
   [RFC5085] .  If VCCV CC Type 1 selected, then PEs might select one of
   MPLS-TP CC-CV types as VCCV CV mechanism to be used for this PW.

2.4.  CV Type Selection

   CV selection rules that have been defined in Section 7 of [RFC5085]
   and updated Section 4 of [RFC5885] are augmented in this document.

   If VCCV Control Channel Type 1 is chosen according to Section 7
   [RFC5085] and common set of proactive CV types advertized by both PEs
   includes MPLS-TP CC-CV types and some BFD CV types, then MPLS-TP
   CC-CV takes precedence over any type of BFD CV.  If multiple MPLS-TP
   CV types advertised by both PEs, then following list sorted in
   descending priority order is used:

   1.  0x08 - coordinated mode for PW Fault Detection and AC/PW Fault
       Status Signaling

   2.  0x04 - coordinated mode for PW Fault Detection only

   3.  0x02 - independent mode for PW Fault Detection and AC/PW Fault
       Status Signaling

   4.  0x01 - independent mode for PW Fault Detection only


3.  IANA Considerations

   The PW Interface Parameters Sub-TLV registry defined in [RFC4446].
s/registry defined/registry is defined/

   IANA is requested to reserve a new PW Interface Parameters Sub-TLV
   type as follows:

   +-------------+--------+----------------------------+---------------+
   |  Parameter  | Length |         Description        | Reference     |
   |      ID     |        |                            |               |
   +-------------+--------+----------------------------+---------------+
   |     0x19    | 4      | VCCV Extended CV Parameter | This document |
   +-------------+--------+----------------------------+---------------+

               Table 2: New PW Interface Parameters Sub-TLV






Mirsky                   Expires March 24, 2014                 [Page 5]

Internet-Draft               VCCV MPLS-TP CV              September 2013


3.1.  VCCV Extended CV Types

   IANA is requested to set up a registry of ?VCCV Extended CV Types?.
s/?// (twice)
   These are 8 bitfield values.  Extended CV Type values 0x01, 0x02,
s/bitfield/bit/
   0x04 and 0x08 are specified in Section 2.2 of this document.  The
   remaining bitfield values (0x10 through 0x80) are to be assigned by
s/bitfield//
   IANA using the "IETF Consensus" policy defined in [RFC2434].  A VCCV
   Extended Control Verification Type description and a reference to an
   RFC approved by the IESG are required for any assignment from this
   registry.

   +--------------+----------------------------------------------------+
   |  Bit(Value)  | Description                                        |
   +--------------+----------------------------------------------------+
   | Bit 0 (0x01) | Independent mode for PW Fault Detection only       |
   | Bit 1 (0x02) | Independent mode for PW Fault Detection and AC/PW  |
   |              | Fault Status Signaling                             |
   | Bit 2 (0x04) | Coordinated mode for PW Fault Detection only       |
   | Bit 3 (0x08) | Coordinated mode for PW Fault Detection and AC/PW  |
   |              | Fault Status Signaling                             |
   | Bit 4 (0x10) | Reserved                                           |
   | Bit 5 (0x20) | Reserved                                           |
   | Bit 6 (0x40) | Reserved                                           |
   | Bit 7 (0x80) | Reserved                                           |
   +--------------+----------------------------------------------------+

            Table 3: MPLS Connectivity Verification (CV) Types



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family: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";}
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.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:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dear Andy, et. al,<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I&#8217;ve posted updated=
 version to address idnits and the shepherd&#8217;s comments.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Please let me know if the=
re&#8217;s anything I can help with.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regards,<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; Greg<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Andrew G=
. Malis [mailto:amalis@gmail.com]
<br>
<b>Sent:</b> Tuesday, October 22, 2013 1:32 PM<br>
<b>To:</b> Gregory Mirsky<br>
<b>Cc:</b> pwe3@ietf.org<br>
<b>Subject:</b> Shepherd's review of draft-ietf-pwe3-mpls-tp-cv-adv-01<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Greg,<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">As document shepherd =
for draft-ietf-pwe3-mpls-tp-cv-adv, I did a WG last call review and have so=
me comments. The good news is that the draft is mostly in good shape for pu=
blication, it just needs a quick revision
 to address the comments below. Also, there were no other WG last call comm=
ents which need to be addressed.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">First of all, there a=
re some idnits issues that need to be addressed:<o:p></o:p></p>
<pre><span style=3D"font-size:7.5pt">&nbsp; Miscellaneous warnings:<o:p></o=
:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp; -------------------------------=
---------------------------------------------<o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp; =3D=3D The document doesn't use=
 any RFC 2119 keywords, yet seems to have RFC<o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp;&nbsp;&nbsp;&nbsp; 2119 boilerpl=
ate text.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp; -- The document date (September=
 20, 2013) is 32 days in the past.&nbsp; Is this<o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp;&nbsp;&nbsp;&nbsp; intentional?<=
o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:7.5pt"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp; Checking references for intende=
d status: Proposed Standard<o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp; -------------------------------=
---------------------------------------------<o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp;&nbsp;&nbsp;&nbsp; (See RFCs 396=
7 and 4897 for information about using normative references<o:p></o:p></spa=
n></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp;&nbsp;&nbsp;&nbsp; to lower-matu=
rity documents in RFCs)<o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp; =3D=3D Unused Reference: 'RFC58=
82' is defined on line 270, but no explicit<o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp;&nbsp;&nbsp;&nbsp; reference was=
 found in the text<o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp; -- Obsolete informational refer=
ence (is this intentional?): RFC 2434<o:p></o:p></span></pre>
<pre><span style=3D"font-size:7.5pt">&nbsp;&nbsp;&nbsp;&nbsp; (Obsoleted by=
 RFC 5226)<o:p></o:p></span></pre>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">I also have some comm=
ents of my own, which are mostly editorial in nature. They are embedded in =
the text below. Just do an update to address the nits and these comments, a=
nd I'll be able to forward the draft
 for publication.<br>
<br>
Thanks,<br>
Andy<br>
<br>
------------<br>
<br>
<span style=3D"font-size:7.5pt;font-family:&quot;Courier New&quot;">1.&nbsp=
; Introduction<br>
<br>
&nbsp;&nbsp; Proactive Connectivity Verification (CV), Continuity Check (CC=
), and<br>
&nbsp;&nbsp; Remote Defect Indication (RDI) for the MPLS Transport Profile<=
br>
&nbsp;&nbsp; [RFC6428] are applicable to all constructs of the MPLS-TP, inc=
luding<br>
&nbsp;&nbsp; pseudowires (PWs).&nbsp; If Control Plane is used to operate a=
nd manage PW<br>
s/Control Plane/a control plane/<br>
s/PW/PWs/<br>
&nbsp;&nbsp; then procedure defined in [RFC5085] and [RFC5885] should be us=
ed to<br>
s/procedure/the procedures/<br>
&nbsp;&nbsp; select proper type of Control Channel and corresponding type o=
f<br>
&nbsp;&nbsp; Connectivity Verification.&nbsp; This document specifies how s=
ignaling and<br>
&nbsp;&nbsp; selection process modified to ensure backward compatibility an=
d allow<br>
s/process modified/processes are modified/<br>
&nbsp;&nbsp; use of proactive CV-CC-RDI over MPLS-TP PWs.<br>
<br>
1.1.&nbsp; Conventions used in this document<br>
<br>
1.1.1.&nbsp; Terminology<br>
<br>
&nbsp;&nbsp; BFD: Bidirectional Forwarding Detection<br>
<br>
&nbsp;&nbsp; CC: Continuity Check<br>
<br>
&nbsp;&nbsp; CV: Connectivity Verification<br>
<br>
&nbsp;&nbsp; PE: Provider Edge<br>
<br>
&nbsp;&nbsp; VCCV: Virtual Circuit Connectivity Verification<br>
<br>
&nbsp;&nbsp; VCCV CC: VCCV Control Channel<br>
<br>
1.1.2.&nbsp; Requirements Language<br>
<br>
&nbsp;&nbsp; The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;RE=
QUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,<br>
&nbsp;&nbsp; &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&=
quot;, &quot;NOT RECOMMENDED&quot;, &quot;MAY&quot;, and<br>
&nbsp;&nbsp; &quot;OPTIONAL&quot; in this document are to be interpreted as=
 described in<br>
&nbsp;&nbsp; [RFC2119].<br>
<br>
<br>
2.&nbsp; MPLS-TP CC-CV on Pseudowires<br>
<br>
&nbsp;&nbsp; PW VCCV can support several CV Types.&nbsp; Ability to support=
 arbitrary<br>
s/Types.&nbsp; Ability to support/Types, and can support/<br>
&nbsp;&nbsp; combination of CV modes advertised in CV Types field of VCCV<b=
r>
s/in CV/in the CV/<br>
&nbsp;&nbsp; Interface Parameter sub-TLV [RFC4446], [RFC4447].&nbsp; Curren=
tly six<br>
&nbsp;&nbsp; types of CV been defined for PW VCCV out of eight bit long fie=
ld.<br>
s/VCCV out of eight bit long field/VCCV/<br>
&nbsp;&nbsp; This document introduces four new CV types and, to accommodate=
 them,<br>
&nbsp;&nbsp; a new VCCV Extended CV parameter for PW Interface Parameters S=
ub-TLV<br>
&nbsp;&nbsp; is defined.<br>
<br>
<br>
<br>
<br>
<br>
<br>
Mirsky&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Expires March 24, 2014&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; [Page 3]<br>
<br>
Internet-Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; VCCV MPLS-TP CV&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; September 2013<br>
<br>
<br>
2.1.&nbsp; VCCV Extended CV Advertisement sub-TLV<br>
<br>
&nbsp;&nbsp; The format of VCCV Extended CV Advertisement is a TLV where:<b=
r>
<br>
&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<br>
&nbsp;&nbsp;&nbsp; 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>
&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<br>
&nbsp;&nbsp;&nbsp; | Type =3D 0x19 |&nbsp;&nbsp;&nbsp; Length&nbsp;&nbsp;&n=
bsp;&nbsp; |&nbsp;&nbsp; CV Type&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; Reserved&n=
bsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Figure 1: VCCV Extended CV parameter format<br>
<br>
&nbsp;&nbsp; Length - the length of the sub-TLV, including type and the Len=
gth<br>
s/Length -/The Length field is/<br>
&nbsp;&nbsp; field itself.&nbsp; Minimum length is 4.&nbsp; It it isrecomme=
nded that<br>
s/Minimum/The minimum/<br>
&nbsp;&nbsp; extensions to the sub-TLV be done in 4 bytes increments with R=
eserved<br>
&nbsp;&nbsp; field being set to zero on transmit and ignored on receipt.<br=
>
<br>
&nbsp;&nbsp; Reserved field must be set to zeroes on transmit and ignored o=
n<br>
&nbsp;&nbsp; receive.<br>
s/Reserved/The Reserved/<br>
<br>
&nbsp;&nbsp; CV Type field is a bitmask that lists types of CV monitoring t=
hat a<br>
s/CV Type/The CV Type/<br>
&nbsp;&nbsp; PE is capable to support.&nbsp; VCCV Extended CV parameter sub=
-TLV must<br>
s/VCCV/The VCCV/<br>
&nbsp;&nbsp; appear in combination with VCCV parameter sub-TLV.&nbsp; If VC=
CV parameter<br>
s/VCCV/the VCCV/ (twice in this line)<br>
&nbsp;&nbsp; sub-TLV is missing then VCCV Extended CV parameter sub-TLV sho=
uld be<br>
s/VCCV/the VCCV/<br>
&nbsp;&nbsp; ignored.<br>
<br>
2.2.&nbsp; MPLS-TP CC-CV Types<br>
<br>
&nbsp;&nbsp; The [RFC6428] defines coordinated and independent modes of mon=
itoring<br>
S/The //<br>
&nbsp;&nbsp; point-to-point bi-directional connection that can be applied t=
o<br>
&nbsp;&nbsp; monitoring PWs.&nbsp; At the same time [RFC6310] defines how B=
FD-based OAM<br>
&nbsp;&nbsp; can map and be mapped to status of an Attachment Circuit.&nbsp=
; Thus there<br>
&nbsp;&nbsp; could be four MPLS-TP CV types as combination of modes and<br>
&nbsp;&nbsp; functionality:<br>
<br>
&nbsp;&nbsp; &#43;---------------&#43;-------------------&#43;-------------=
------------------&#43;<br>
&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; Modes&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp=
; Fault Detection&nbsp; |&nbsp;&nbsp; Fault Detection and Status&nbsp; |<br=
>
&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Only&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Signalling&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; |<br>
&nbsp;&nbsp; &#43;---------------&#43;-------------------&#43;-------------=
------------------&#43;<br>
&nbsp;&nbsp; |&nbsp; Independent&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; 0x01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x02&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mode&nbsp;&nbsp;&nbsp;&nbsp; |=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; |&nbsp; Coordinated&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; 0x04&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x08&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mode&nbsp;&nbsp;&nbsp;&nbsp; |=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; &#43;---------------&#43;-------------------&#43;-------------=
------------------&#43;<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; Table 1: Bitmask Values for MPLS-TP CV Types<br>
<br>
<br>
<br>
<br>
<br>
Mirsky&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Expires March 24, 2014&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; [Page 4]<br>
<br>
Internet-Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; VCCV MPLS-TP CV&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; September 2013<br>
<br>
<br>
2.3.&nbsp; MPLS-TP CC-CV Type Operation<br>
<br>
&nbsp;&nbsp; Connectivity verification according to [RFC6428] is part of MP=
LS-TP<br>
&nbsp;&nbsp; CC/CV operation that can be used with VCCV Control Channel Typ=
e 1<br>
&nbsp;&nbsp; [RFC5085] .&nbsp; If VCCV CC Type 1 selected, then PEs might s=
elect one of<br>
&nbsp;&nbsp; MPLS-TP CC-CV types as VCCV CV mechanism to be used for this P=
W.<br>
<br>
2.4.&nbsp; CV Type Selection<br>
<br>
&nbsp;&nbsp; CV selection rules that have been defined in Section 7 of [RFC=
5085]<br>
&nbsp;&nbsp; and updated Section 4 of [RFC5885] are augmented in this docum=
ent.<br>
<br>
&nbsp;&nbsp; If VCCV Control Channel Type 1 is chosen according to Section =
7<br>
&nbsp;&nbsp; [RFC5085] and common set of proactive CV types advertized by b=
oth PEs<br>
&nbsp;&nbsp; includes MPLS-TP CC-CV types and some BFD CV types, then MPLS-=
TP<br>
&nbsp;&nbsp; CC-CV takes precedence over any type of BFD CV.&nbsp; If multi=
ple MPLS-TP<br>
&nbsp;&nbsp; CV types advertised by both PEs, then following list sorted in=
<br>
&nbsp;&nbsp; descending priority order is used:<br>
<br>
&nbsp;&nbsp; 1.&nbsp; 0x08 - coordinated mode for PW Fault Detection and AC=
/PW Fault<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Status Signaling<br>
<br>
&nbsp;&nbsp; 2.&nbsp; 0x04 - coordinated mode for PW Fault Detection only<b=
r>
<br>
&nbsp;&nbsp; 3.&nbsp; 0x02 - independent mode for PW Fault Detection and AC=
/PW Fault<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Status Signaling<br>
<br>
&nbsp;&nbsp; 4.&nbsp; 0x01 - independent mode for PW Fault Detection only<b=
r>
<br>
<br>
3.&nbsp; IANA Considerations<br>
<br>
&nbsp;&nbsp; The PW Interface Parameters Sub-TLV registry defined in [RFC44=
46].<br>
s/registry defined/registry is defined/<br>
<br>
&nbsp;&nbsp; IANA is requested to reserve a new PW Interface Parameters Sub=
-TLV<br>
&nbsp;&nbsp; type as follows:<br>
<br>
&nbsp;&nbsp; &#43;-------------&#43;--------&#43;--------------------------=
--&#43;---------------&#43;<br>
&nbsp;&nbsp; |&nbsp; Parameter&nbsp; | Length |&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
| Reference&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ID&nbsp;&nbsp;&nbsp;&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; &#43;-------------&#43;--------&#43;--------------------------=
--&#43;---------------&#43;<br>
&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; 0x19&nbsp;&nbsp;&nbsp; | 4&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; | VCCV Extended CV Parameter | This document |<br>
&nbsp;&nbsp; &#43;-------------&#43;--------&#43;--------------------------=
--&#43;---------------&#43;<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; Table 2: New PW Interface Parameters Sub-TLV<br>
<br>
<br>
<br>
<br>
<br>
<br>
Mirsky&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Expires March 24, 2014&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; [Page 5]<br>
<br>
Internet-Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; VCCV MPLS-TP CV&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; September 2013<br>
<br>
<br>
3.1.&nbsp; VCCV Extended CV Types<br>
<br>
&nbsp;&nbsp; IANA is requested to set up a registry of ?VCCV Extended CV Ty=
pes?.<br>
s/?// (twice)<br>
&nbsp;&nbsp; These are 8 bitfield values.&nbsp; Extended CV Type values 0x0=
1, 0x02,<br>
s/bitfield/bit/<br>
&nbsp;&nbsp; 0x04 and 0x08 are specified in Section 2.2 of this document.&n=
bsp; The<br>
&nbsp;&nbsp; remaining bitfield values (0x10 through 0x80) are to be assign=
ed by<br>
s/bitfield//<br>
&nbsp;&nbsp; IANA using the &quot;IETF Consensus&quot; policy defined in [R=
FC2434].&nbsp; A VCCV<br>
&nbsp;&nbsp; Extended Control Verification Type description and a reference=
 to an<br>
&nbsp;&nbsp; RFC approved by the IESG are required for any assignment from =
this<br>
&nbsp;&nbsp; registry.<br>
<br>
&nbsp;&nbsp; &#43;--------------&#43;--------------------------------------=
--------------&#43;<br>
&nbsp;&nbsp; |&nbsp; Bit(Value)&nbsp; | Description&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; &#43;--------------&#43;--------------------------------------=
--------------&#43;<br>
&nbsp;&nbsp; | Bit 0 (0x01) | Independent mode for PW Fault Detection only&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; | Bit 1 (0x02) | Independent mode for PW Fault Detection and A=
C/PW&nbsp; |<br>
&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; | Fault Status Signaling&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; | Bit 2 (0x04) | Coordinated mode for PW Fault Detection only&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; | Bit 3 (0x08) | Coordinated mode for PW Fault Detection and A=
C/PW&nbsp; |<br>
&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; | Fault Status Signaling&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; | Bit 4 (0x10) | Reserved&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; | Bit 5 (0x20) | Reserved&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; | Bit 6 (0x40) | Reserved&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; | Bit 7 (0x80) | Reserved&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp; &#43;--------------&#43;--------------------------------------=
--------------&#43;<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Table 3:=
 MPLS Connectivity Verification (CV) Types<br>
</span><span style=3D"font-family:&quot;Courier New&quot;"><br>
<br>
</span><o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_7347100B5761DC41A166AC17F22DF1121B70FFAEeusaamb103erics_--

--_004_7347100B5761DC41A166AC17F22DF1121B70FFAEeusaamb103erics_
Content-Type: message/rfc822
Content-Disposition: attachment;
	creation-date="Mon, 11 Nov 2013 22:01:12 GMT";
	modification-date="Mon, 11 Nov 2013 22:01:12 GMT"

Received: from ESESSHC011.ericsson.se (153.88.183.51) by
 EUSAAHC008.ericsson.se (147.117.188.96) with Microsoft SMTP Server (TLS) id
 14.2.328.9; Mon, 11 Nov 2013 16:57:42 -0500
Received: from sesbmg10.ericsson.net (153.88.183.153) by
 smtp.internal.ericsson.com (153.88.183.52) with Microsoft SMTP Server id
 14.2.328.9; Mon, 11 Nov 2013 22:57:41 +0100
Received: from mail.ietf.org (mail.ietf.org [12.22.58.30])	by
 sesbmg10.ericsson.net (Symantec Mail Security) with SMTP id
 57.C3.01845.4D251825; Mon, 11 Nov 2013 22:57:40 +0100 (CET)
Received: from ietfa.amsl.com (localhost [IPv6:::1])	by ietfa.amsl.com
 (Postfix) with ESMTP id 7896F21E80F1;	Mon, 11 Nov 2013 13:57:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])	by ietfa.amsl.com (Postfix)
 with ESMTP id B231621E8089;	Mon, 11 Nov 2013 13:57:00 -0800 (PST)
Received: from mail.ietf.org ([12.22.58.30])	by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024)	with ESMTP id SrrIho5QwqnN; Mon, 11
 Nov 2013 13:57:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1])	by ietfa.amsl.com
 (Postfix) with ESMTP id 4467411E8114;	Mon, 11 Nov 2013 13:57:00 -0800 (PST)
From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
To: "i-d-announce@ietf.org" <i-d-announce@ietf.org>
CC: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: [PWE3] I-D Action: draft-ietf-pwe3-mpls-tp-cv-adv-02.txt
Thread-Topic: [PWE3] I-D Action: draft-ietf-pwe3-mpls-tp-cv-adv-02.txt
Thread-Index: AQHO3ykMxMN+6j+n/Ui0yCXWrRmKYA==
Sender: "pwe3-bounces@ietf.org" <pwe3-bounces@ietf.org>
Date: Mon, 11 Nov 2013 21:57:00 +0000
Message-ID: <20131111215700.20279.65906.idtracker@ietfa.amsl.com>
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>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: ESESSHC011.ericsson.se
X-MS-Has-Attach: 
X-Auto-Response-Suppress: All
X-MS-TNEF-Correlator: 
x-brightmail-tracker: H4sIAAAAAAAAA1WTWUwTURSGuZ3pzFA7OJQCl7pSo+ICQuJyJcb1xQc1yqOaaIGBVkshndGA
	SyLGGq1atWqDFZEIwYALiwYwvEAjiEoiNlbU4IJWwCpWRS1qrM50iujbf89/zv/dk9xLYapi
	UkOxhTxrNumMWkKBK+PSJyc/zCjOSP3SvwB53n8i0JX+chK1Ojeja2/6ZWioohpHzR+DJHJc
	qpKhvvtNGBr85CZR75djGGp5VEuid0moufEXgez3NqEBrxUg99FBErkuVmIoWHaLQI4zbzHU
	+8IqR8O+ZPT14ymArC0dBHrk7ZGja+/eyJcnrP7x1UOsBxsVS7JZo2Ena563dKtCX2fxYAWH
	xhVa655h+4Al0goiKcjMhzZXJZB0HOx+XktYgYJSMU0AfjtYTEoHB4A/Gw8D8YAzAQweCuyX
	SyNaeMQSwESNM4mw8kWbXJqwA1htOx1uSoIl1d3CNCXo8fCqa9oorrTnahgdBR8MjsgkfRzA
	20dzpJxGADv998auMWjtC9FoJhreOevFRU0wk+FlnyOUpGYSoLPrPCklqeEHj9Qv0iqG/KE6
	EPpHOl6HaAzDwKC9G5cyV8CB1iAmXhRnpsOaU1FiGRNQw4HO0C4xQsuBkarwXhr4xNMeXiAB
	Wo95Q/FKJh0OXH8e1hws6bQQkl4M6522cD0ROqqGiRNghvOfbZwh3FxY3vKZkPQU2DRUipUD
	rAbEciyXmZeblprCmg1ZHJdvSjGxfAMQ3l3bjZ9LmkGfN80FEiiZNpbuWlOcoYrKzM8u0us4
	/RbzDiPLucAECtfG04uSujaomFwdz25n2QLWPOpOpCgtpPdvECajzWwuW5hjMPJjtoyKdAFI
	KbVqukzsobkCXR5nyJX8uyBRE08fEA1GNPQ7TH9nR3+GG0zSxNAgIiJCpRS4eQb+f98H4img
	jaGNYorSYOL/pvsEsEwAL/ftFcG8bszS7AMn7dzmK1TqSFmy7feFhqys5k5N7+3ZDXr/TZd/
	28DMkpX563r2rMpJnrSq4/sE366ijZr2XVO9MaTa/Sy4Z2722tboOeeG6hfGPwbLKlamKGrs
	ma3D6/vhOLunNvaBejc/dWdgEZ9e5EaWuJMvc2x3eg9ilqcrTj+d5X8VFclcnKPFOb0ubTZm
	5nR/AKsi6/gUBAAA
x-auditid: c1b4fb3c-b7ff28e000000735-24-528152d45c04
errors-to: pwe3-bounces@ietf.org
x-beenthere: pwe3@ietf.org
list-id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
x-mailman-version: 2.1.12
list-post: <mailto:pwe3@ietf.org>
list-archive: <http://www.ietf.org/mail-archive/web/pwe3>
x-original-to: pwe3@ietfa.amsl.com
delivered-to: pwe3@ietfa.amsl.com
x-spam-level: 
x-spam-status: No, score=-102.436 tagged_above=-999 required=5
	tests=[AWL=0.164, BAYES_00=-2.599, NO_RELAYS=-0.001,	USER_IN_WHITELIST=-100]
x-spam-flag: NO
x-spam-score: -102.436
x-virus-scanned: amavisd-new at amsl.com
dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1384207024; bh=fSTJ/+qtR+xV0YxpNftVqXnOOq51gIxEc08a/IkM6Ro=;
	h=MIME-Version:From:To:Message-ID:Date:Cc:Subject:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 Content-Type:Content-Transfer-Encoding:Sender;
	b=Q2Y0dBgkoAHMk9+a34TEKlfvfZT6vtGl+jP8FAo7kTBoqnCFdCOaqqWZBaQpht7MV
	 YLI+Ds7YQLwBhxPYl71nvA0uSQX+3SdtkrcuxHpuRwWUnKt3TkvB/VzIbj01HIoNj8
	 hC3Pp9qfk+oVJl2dk2/vd/3giPzUdx0snd7A94jE=
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3093776D514E66419100270383AEFD14@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


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

	Title           : VCCV MPLS-TP Connectivity Verification (CV) Capability A=
dvertisement
	Author(s)       : Greg Mirsky
	Filename        : draft-ietf-pwe3-mpls-tp-cv-adv-02.txt
	Pages           : 7
	Date            : 2013-11-11

Abstract:
   This document specifies how use of proactive Connectivity
   Verification, Continuity Check, and Remote Defect Indication for the
   MPLS Transport Profile [RFC6428] affects operation and management
   function election for PW VCCV [RFC5085], [RFC5885].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-cv-adv

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-cv-adv-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-mpls-tp-cv-adv-02


Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

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

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

--_004_7347100B5761DC41A166AC17F22DF1121B70FFAEeusaamb103erics_--

From matthew.bocci@alcatel-lucent.com  Tue Nov 12 02:30:24 2013
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ACBC21F9C10 for <pwe3@ietfa.amsl.com>; Tue, 12 Nov 2013 02:30:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.261
X-Spam-Level: 
X-Spam-Status: No, score=-110.261 tagged_above=-999 required=5 tests=[AWL=0.338, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g9R4p6eJuMnH for <pwe3@ietfa.amsl.com>; Tue, 12 Nov 2013 02:30:09 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 3491721F9FF6 for <pwe3@ietf.org>; Tue, 12 Nov 2013 02:30:09 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rACAU4mu018897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 12 Nov 2013 04:30:07 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rACAU17M031098 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Nov 2013 11:30:04 +0100
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.146]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Tue, 12 Nov 2013 11:30:03 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, pwe3 <pwe3@ietf.org>, "draft-ietf-pwe3-dynamic-ms-pw@tools.ietf.org" <draft-ietf-pwe3-dynamic-ms-pw@tools.ietf.org>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>
Thread-Topic: AD comments on draft-ietf-pwe3-dynamic-ms-pw
Thread-Index: AQHO1Xsgrwsk4EgL6UysIRoHs1t7wJohaJAA
Date: Tue, 12 Nov 2013 10:30:03 +0000
Message-ID: <CEA7ADA9.57647%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <52711561.1090209@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <563737A6EDF32742B274E8667099CD31@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: Re: [PWE3] AD comments on draft-ietf-pwe3-dynamic-ms-pw
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 12 Nov 2013 10:30:24 -0000

Stewart

Thanks for your comments. Please see below.

Matthew

On 30/10/2013 14:19, "Stewart Bryant" <stbryant@cisco.com> wrote:

>I am about to put this into IETF LC.
>
>Please consider the following as LC comments.
>
>- Stewart
>
>Network Working Group                                 Luca Martini (Ed.)
>Internet Draft                                        Cisco Systems Inc.
>Expires: April 2014
>Intended status: Standards Track                     Matthew Bocci (Ed.)
>Updates: 6073                                         Florin Balus (Ed.)
>                                                           Alcatel-Lucent
>
>                                                          October 8, 2013
>
>
>              Dynamic Placement of Multi-Segment Pseudowires
>
>
>                   draft-ietf-pwe3-dynamic-ms-pw-19.txt
>
>SB> it updates the length value of the PW Switching Point PE Sub-TLV Type
>0x06 to 14.
>SB> It is confusing to talk about the "length value" of a TLV. I think you
>SB> mean "length"

MB> It should probably say "the value of the length field", since this
value was incorrectly specified in RFC6073.


>
>
>
>
>
>2.1. Changes to Existing PW Signaling
>
>
>    This document also updates the length value of the PW Switching Point
>    PE Sub-TLV Type 0x06 to 14.
>
>SB> Same comment as above
>
>
>
>4.2. LDP Signaling
>
>
>    The complete definitions of the content of the SENDER_TSPEC objects
>    are found in [TSPEC] section 3.1.
>
>SB> TSPEC is actually RFC2210 isn't it?
>SB> If so that would be a much better reference identifier


MB> agreed

>
>
>
>4.2.1. Equal Cost Multi Path (ECMP) in PW Routing
>
>    A next hop selection for a specific PW may find a match with a PW
>    route that has multiple next hops associated with it. Multiple next
>    hops may be either configured explicitly as static routes or may be
>    learned through BGP routing procedures. Implementations at and S-PE
>SB> s/and/an/
>
>    or T-PE MAY use selection algorithms, such as CRC32 on the FEC TLV,
>    for load balancing of PWs across multiple next-hops. The details of
>    such selection algorithms are outside the scope of this document.
>
>SB> Presumable FAT is another option?

MB> Yes. Fat PW didn=B9t exist when this was written. I=B9ll rephrase to
=B3=8A,for example CRC32 on the FEC TLV, or Flow Aware Transport PW [RFC639=
1]=8A=B2

>
>  4.2.2. Active/Passive T-PE Election Procedure
>
>
>    The determination of which T-PE assumes the active role SHOULD be
>    done as follows: the Source Attachment Individual Identifier (SAII)
>    and TAII are compared as unsigned integers, if the SAII is bigger
>    then the T-PE assumes the active role.
>
>SB> This does not look quite precise enough. You need to specify which
>bytes
>SB> and the bit order. What you say is technically correct
>SB> but isn't it clearer to say that the T-PE with the larger
>SB> SAII is active?

MB> Yes. I=B9ll rephrase. I=B9ll also need to confirm the bit ordering.

>SB> I do not see (pointer to) a definition of SAII or TAII in this draft

MB> It should be RFC6074, with the AII format for the SAII and TAII as per
Section 3.1 of this draft. I=B9ll add text to clarify.
>
>
>
>6. Operations and Maintenance (OAM)
>
>    In this case, the following TLV type (0x06) MUST be used
>    in place of type 0x01 in the PW switching point TLV:
>
>SB> This is "PW Switching Point PE sub-TLV" in RFC6073

MB> Yes. I=B9ll correct.

>SB>
>
>SB> Are there any interoperability issues with the change of length to
>SB> 14, i.e. is there any length 12 code in the wild?

MB> If you implement 6073 with a length field of 12, then the RFC6073
implementation would have problems, not just in the context of this draft,
but in general. I believe that known implementations of 6073 that work
correctly use a value of 14 for SP-PE TLV today.



>
>
>
>
>
>
>
>
>
>
>
>
>
>


From loa@pi.nu  Tue Nov 12 13:59:48 2013
Return-Path: <loa@pi.nu>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 248E311E810B; Tue, 12 Nov 2013 13:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Qn+RDHoi6yV; Tue, 12 Nov 2013 13:59:43 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id DE7B611E80E6; Tue, 12 Nov 2013 13:59:39 -0800 (PST)
Received: from [192.168.252.96] (107-1-141-74-ip-static.hfc.comcastbusiness.net [107.1.141.74]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 93B2B1802038; Tue, 12 Nov 2013 22:59:37 +0100 (CET)
Message-ID: <5282A4C9.4080603@pi.nu>
Date: Tue, 12 Nov 2013 13:59:37 -0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>,  "pwe3@ietf.org" <pwe3@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, l2vpn@ietf.org, L3VPN <l3vpn@ietf.org>, Vero Zheng <vero.zheng@huawei.com>, Adrian Farrel <adrian@olddog.co.uk>,  "stbryant@cisco.com" <stbryant@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PWE3] MPLS VPN Scaling Bof in London
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 12 Nov 2013 21:59:48 -0000

Working Groups,

We will run a non-Working Group forming BoF in London to discuss
issues around Scaling of MPLS VPNs.

Lou Berger and i have accepted to chair this BoF, Vero Zheng will
take on the role as list admin and secretary.

We plan to kick-off the discussion on a problem statement as soon
as we have enough participants on the mailing list

We gave a heads up for this BoF in Vancouver - these slides were
presented in the RTG Area Open Meeting.

http://www.ietf.org/proceedings/88/slides/slides-88-rtgarea-5.pptx

We have started to prepare the BoF, and the discussion on how we set
it up will take place on a new mailing list:

    scale-request@ietf.org

Please subscribe to this list through:

https://www.ietf.org/mailman/listinfo/scale

/Loa



-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From ietf-ipr@ietf.org  Wed Nov 13 08:46:46 2013
Return-Path: <ietf-ipr@ietf.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1597111E8180; Wed, 13 Nov 2013 08:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.319
X-Spam-Level: 
X-Spam-Status: No, score=-102.319 tagged_above=-999 required=5 tests=[AWL=0.281, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HdEtxSQou9Oo; Wed, 13 Nov 2013 08:46:45 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E385F21F9FC7; Wed, 13 Nov 2013 08:46:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-ipr@ietf.org>
To: matthew.bocci@alcatel-lucent.co.uk, giheron@cisco.com, y.kamite@ntt.com, frederic.jounay@orange.ch
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131113164642.17217.59948.idtracker@ietfa.amsl.com>
Date: Wed, 13 Nov 2013 08:46:42 -0800
Cc: pwe3@ietf.org, ipr-announce@ietf.org, stbryant@cisco.com
Subject: [PWE3] IPR Disclosure: ORANGE's Statement about IPR related to	draft-ietf-pwe3-p2mp-pw-requirements-06
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Nov 2013 16:46:46 -0000

Dear Matthew Bocci, Giles Heron, Yuji Kamite, Frederic JOUNAY:

 An IPR disclosure that pertains to your Internet-Draft entitled "Requireme=
nts
and Framework for Point-to-Multipoint Pseudowires over MPLS PSNs" (draft-ie=
tf-
pwe3-p2mp-pw-requirements) was submitted to the IETF Secretariat on 2013-11=
-13
and has been posted on the "IETF Page of Intellectual Property Rights
Disclosures" (https://datatracker.ietf.org/ipr/2249/). The title of the IPR
disclosure is "ORANGE's Statement about IPR related to draft-ietf-pwe3-p2mp=
-pw-
requirements-06."");

The IETF Secretariat


From zhangmingui@huawei.com  Wed Nov 13 20:57:35 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71C1221E81A5; Wed, 13 Nov 2013 20:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.61
X-Spam-Level: 
X-Spam-Status: No, score=-5.61 tagged_above=-999 required=5 tests=[AWL=0.389,  BAYES_00=-2.599, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a97NuEDesaFG; Wed, 13 Nov 2013 20:57:31 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6B31521E81A4; Wed, 13 Nov 2013 20:57:30 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAG45685; Thu, 14 Nov 2013 04:57:29 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 14 Nov 2013 04:56:29 +0000
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 14 Nov 2013 04:57:28 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.179]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Thu, 14 Nov 2013 12:57:23 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Thread-Topic: Why we consider the method of "label sharing for fast PE protection"
Thread-Index: AQHO2+geoImqeN4PM02OPNhQaq9T5JohspVQgAJ79ZA=
Date: Thu, 14 Nov 2013 04:57:23 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7336623C5@nkgeml508-mbx.china.huawei.com>
References: <4552F0907735844E9204A62BBDD325E733660DBA@nkgeml508-mbx.china.huawei.com> <19124_1384271977_52825069_19124_7825_1_53C29892C857584299CBF5D05346208A070A3C8F@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <19124_1384271977_52825069_19124_7825_1_53C29892C857584299CBF5D05346208A070A3C8F@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Subject: Re: [PWE3] Why we consider the method of "label sharing for fast PE protection"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2013 04:57:36 -0000

Hi Bruno,=20

My comments inline below. [Mingui]

>1)      The document does not describe the scaling impact on the core as i=
t
>creates, in the core IGP, states on a per CE (customers'site) basis. For l=
arge SP,
>this will represent a significant impact on the IGP and will degrade the I=
GP
>convergence time. ( o(number of important IGP prefixes to rewrite) )

[Mingui] Here, I need to point out that the vNH is not created per CE. If m=
ultiple CEs are connected to an RG, one vNH is enough. When you read the fi=
rst sentence of Section 2.1, you will be clear.
[Mingui] "A vNH router is created in IGP to represent the set of CEs which =
are dual-homed to the same egress PEs in the Service Provider's backbone".
[Mingui] Exactly, it's per RG basis. In a real network, the numbers of RGs =
is comparable to the number of PEs, so it's similar to the per PE basis cho=
ice (the best choice) in draft-minto.

>2)  > A master PE is elected in the same way the DR is selected (see secti=
on 7.3
>of [RFC2328] <http://tools.ietf.org/html/rfc2328#section-7.3> ), or the DI=
S is
>selected [ISIS
><http://tools.ietf.org/html/draft-zhang-l3vpn-label-sharing-01#ref-ISIS> ]=
.
>I don't think that this is directly applicable. You may need to elaborate =
on this
>and specify the corner cases (e.g. CE starts and advertise its routes to b=
oth PE
>at the same time. Hence both PE believes they are the first one and hence =
are
>the master.) Also in BGP VPN or IGP there is no advertisement of "Router
>Priority". I guess that this can always be specified, but this remains to =
be done.

[Mingui] That's a valid point. We did define the "Priority" in the "vNH TLV=
" in Section 2.3.3 of the companion draft (http://tools.ietf.org/html/draft=
-zhang-pwe3-iccp-label-sharing-00). We can change the words to fix this inc=
onsistence.

<snip>
>IMHO additional elaboration may be required as the nominal PE
>may be the nominal because it has advertised a more specific route. Hence =
a
>look up in the VRF will match the more specific route from the nominal/fai=
led PE.
>Not sure how a vanilia PE implementation would react. The issue is that wh=
en
>receiving the packet, the backup PE does not know whether the nominal is d=
ead
>or not. In contrast to draft-minto for which the PE know whether it's used=
 as
>backup or not, thanks to the contextual label.

[Mingui] So you propose the scenario that the backup PE directs packets to =
the primary PE since the primary PE advertised a more specific route. This =
makes the primary PE be an inevitable point on all forwarding paths to the =
CE. Eric ever used "BGP LOCAL_PREF" to compose a similar scenario (http://w=
ww.ietf.org/mail-archive/web/l3vpn/current/msg03691.html).

[Mingui] For this subtle case, the redundant connection is not utilized in =
the first place. If customers prefer resilience to more specific routes, th=
e backup PE should not use the primary PE as the next hop.=20

[Mingui] All in all, if customers really want the resilience, those routes =
via the primary PE SHOULD NOT be installed in the FIBs of backup PEs.=20

[Mingui] By the way, the scenario you designed may suffer from transient lo=
op issue. Imagine that the more specific routes fails on the primary PE, th=
e primary PE will resort to the backup PE. At that time, it's probably that=
 the backup PE is unaware of the failure. It will send packet back to the p=
rimary PE. Oops, loop occurs. Following the above "SHOULD NOT be installed"=
 requirement, such kind of loops can be avoided.

<snip>
>More seriously:
>- Draft minto does not need to define a new protocol (ICCP) in order to le=
arn the
>labels of the backup PE. BGP already provides this. While ICCP is a 79 pag=
es
>draft, plus 11 for the extension.
>- Draft zhang relies on the having the same label on redundant PE. While t=
his is
>doable, this is a significant change compared to the existing deployed mod=
el.
>- regarding context label tabel
>                  - From a standardization standpoint, context-specific la=
bel
>space is already defined in RFC 5331, so nothing new.
>                  - From an implementation standpoint, I agree that this
>requires some additional resources in the forwarding plane. But draft mint=
o
>does not require that all PE support this. This can be performed by a prot=
ector
>PE if some PE do not support it.

[Mingui] If nothing new for protocols, this becomes an implementation issue=
. Then, should this be considered in IETF? :-)

[Mingui] We do not define ICCP, we make use of it. If we can have a solutio=
n happen in purely the control plane, as IETFers, we should be happy. If cu=
stomers want this feature, I promise you will see this feature supported by=
 products in several months. For vendors who have already implemented ICCP,=
 it can be faster. More importantly, this is a "once for all" effort compar=
ed to the redundant forwarding tables.=20

[Mingui] As Robert and I discussed previously, existing deploy model does n=
ot prohibit PE to advertise the same label. I don't think this changes the =
existing deploy model.

>So label table need not be stored repeatedly on RG members.
>
>#Bruno: agreed.
>
>
>2. Also, it's easy to be deployed. It does not bring any change to P route=
rs
>(control plane & data plane). It even does not change the data plane of PE
>routers.
>
>#Bruno: It's not easy to deploy as it mandates to update all PE routers, b=
oth
>nominal and backup. While with draft-minto-2547-egress-node-fast-protectio=
n
><http://tools.ietf.org/html/draft-minto-2547-egress-node-fast-protection-0=
2>
>the deployment of a single protector PE can fast protect all PE of the AS =
with no
>change on existing PE.

[Mingui] As I explained above, the update to the control plane should be OK=
.

[Mingui] OK. Let me give an analysis of the draft-minto-2547-egress-node-fa=
st-protection. I hope this is constructive when the draft is updated.

[Mingui] a.	The co-located and hybrid models require configuration, which i=
s error prone and increases a management burden to operators.
[Mingui] b.	The centralized model is not robust. How do you handle the fail=
ure of the centralized protector itself? This problem had been proposed for=
 the "central controller" stuff.=20
[Mingui] c.	The delegation of protector is topology dependent. I guess the =
number of possible alternative paths held by the protector is a much smalle=
r set of all possible alternative paths.=20
[Mingui] d.	The centralized protector has to manage the context label assig=
nment and maintain multiple forwarding tables for all RGs. I am afraid this=
 model is not scalable.=20
[Mingui] e.	There is a brief description on Fast ReRoute in Section 5.3. Fo=
r the "RSVP" choice, it depends on another individual draft [http://tools.i=
etf.org/html/draft-minto-2547-egress-node-fast-protection-02]. Does this dr=
aft mandates update on P and PE routers? For the "LDP" choice, it's not cle=
ar how IGP can find alternative paths (I find the "beyond the scope" words.=
). I think the coverage of alternative paths cannot be very good, especiall=
y when the centralized protector is used.

>3. In addition, it does not bear the restriction of "no penultimate-hop-po=
pping".
>
>#Bruno: ultimate hop poping is only required for the label associated with=
 the
>context table of the backup PE. This is required to identify the context-s=
pecific
>label space. This is not an additional argument compared to 1 (context lab=
el
>table).

[Mingui] I agree.=20

Thanks,
Mingui

From bruno.decraene@orange.com  Thu Nov 14 02:12:30 2013
Return-Path: <bruno.decraene@orange.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C31F221E808D; Thu, 14 Nov 2013 02:12:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.866
X-Spam-Level: 
X-Spam-Status: No, score=-1.866 tagged_above=-999 required=5 tests=[AWL=-0.218, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_16=0.6, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rn+sh-ceHyOb; Thu, 14 Nov 2013 02:12:26 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by ietfa.amsl.com (Postfix) with ESMTP id 90CD321E81DD; Thu, 14 Nov 2013 02:12:24 -0800 (PST)
Received: from opfeda41.si.francetelecom.fr (unknown [10.98.245.92]) by omfeda10.si.francetelecom.fr (ESMTP service) with ESMTP id 24726376BA8; Thu, 14 Nov 2013 11:12:23 +0100 (CET)
Received: from opfeda41.si.francetelecom.fr (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id EBFFF821AC_284A25DB; Thu, 14 Nov 2013 10:13:49 +0000 (GMT)
Received: from omfeda05.si.francetelecom.fr (omfeda05.si.francetelecom.fr [xx.xx.xx.198]) by opfeda41.si.francetelecom.fr (Sophos Email Appliance) with ESMTP id 9D25A7F4B0_284A25DF; Thu, 14 Nov 2013 10:13:49 +0000 (GMT)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id 90A73180274; Thu, 14 Nov 2013 11:12:22 +0100 (CET)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0158.001; Thu, 14 Nov 2013 11:12:22 +0100
From: <bruno.decraene@orange.com>
To: Mingui Zhang <zhangmingui@huawei.com>
Thread-Topic: Why we consider the method of "label sharing for fast PE protection"
Thread-Index: AQHO2+geoImqeN4PM02OPNhQaq9T5JohspVQgAJ79ZCAAEGdEA==
Date: Thu, 14 Nov 2013 10:12:21 +0000
Message-ID: <28062_1384423942_5284A206_28062_2935_1_53C29892C857584299CBF5D05346208A070A4BFE@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <4552F0907735844E9204A62BBDD325E733660DBA@nkgeml508-mbx.china.huawei.com> <19124_1384271977_52825069_19124_7825_1_53C29892C857584299CBF5D05346208A070A3C8F@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4552F0907735844E9204A62BBDD325E7336623C5@nkgeml508-mbx.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E7336623C5@nkgeml508-mbx.china.huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.14.23914
X-Mailman-Approved-At: Thu, 14 Nov 2013 08:02:07 -0800
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Subject: Re: [PWE3] Why we consider the method of "label sharing for fast PE	protection"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2013 10:12:30 -0000

Hi Mingui,

Thanks for the answers.
You have added pwe in cc. I'm not sure why as I'm following up on your pres=
entation during L3 VPN WG on L3 VPN PE protection.

My comments inline below [Bruno]

>From: >Mingui Zhang >Sent: Thursday, November 14, 2013 5:57 AM
>
>Hi Bruno,
>
>My comments inline below. [Mingui]
>
>>1)      The document does not describe the scaling impact on the core as =
it
>>creates, in the core IGP, states on a per CE (customers'site) basis. For =
large SP,
>>this will represent a significant impact on the IGP and will degrade the =
IGP
>>convergence time. ( o(number of important IGP prefixes to rewrite) )
>
>[Mingui] Here, I need to point out that the vNH is not created per CE. If
>multiple CEs are connected to an RG, one vNH is enough. When you read the
>first sentence of Section 2.1, you will be clear.
>[Mingui] "A vNH router is created in IGP to represent the set of CEs which
>are dual-homed to the same egress PEs in the Service Provider's backbone".

[Bruno] Agreed.=20

>[Mingui] Exactly, it's per RG basis. In a real network, the numbers of RGs
>is comparable to the number of PEs, so it's similar to the per PE basis
>choice (the best choice) in draft-minto.

[Bruno] First, consider that in a "POP" there may be multiple PE, i.e. more=
 than the 2 required for the dual homing. Let's say 5 PE.
The number of RG is flexible, but this also comes with drawbacks.
One option is to have a single RG. In this case, you indeed need a single v=
NH but you require global label allocation for the perimeter of those 5 PE.=
 Which roughly divide the available label space by 5. Then if this represen=
ts a scaling issue, I guess you can call for bigger labels, e.g. by stackin=
g 2 labels. But this requires more lookup work in the forwarding plane. Rou=
ghly equivalent to the label context space that you did not want in the fir=
st time...
Another option is to have one RG per couple of PE. In this case you need 10=
 vNH (IINM). That's roughly the number of PE but that's still *3 the number=
 of states in the IGP so I think the document should talk about this.


>>2)  > A master PE is elected in the same way the DR is selected (see
>section 7.3
>>of [RFC2328] <http://tools.ietf.org/html/rfc2328#section-7.3> ), or the D=
IS
>is
>>selected [ISIS
>><http://tools.ietf.org/html/draft-zhang-l3vpn-label-sharing-01#ref-ISIS> =
].
>>I don't think that this is directly applicable. You may need to elaborate
>on this
>>and specify the corner cases (e.g. CE starts and advertise its routes to
>both PE
>>at the same time. Hence both PE believes they are the first one and hence
>are
>>the master.) Also in BGP VPN or IGP there is no advertisement of "Router
>>Priority". I guess that this can always be specified, but this remains to
>be done.
>
>[Mingui] That's a valid point. We did define the "Priority" in the "vNH TL=
V"
>in Section 2.3.3 of the companion draft (http://tools.ietf.org/html/draft-
>zhang-pwe3-iccp-label-sharing-00). We can change the words to fix this
>inconsistence.

[Bruno] Ack.=20

><snip>
>>IMHO additional elaboration may be required as the nominal PE
>>may be the nominal because it has advertised a more specific route. Hence=
 a
>>look up in the VRF will match the more specific route from the
>nominal/failed PE.
>>Not sure how a vanilia PE implementation would react. The issue is that
>when
>>receiving the packet, the backup PE does not know whether the nominal is
>dead
>>or not. In contrast to draft-minto for which the PE know whether it's used
>as
>>backup or not, thanks to the contextual label.
>
>[Mingui] So you propose the scenario that the backup PE directs packets to
>the primary PE since the primary PE advertised a more specific route. This
>makes the primary PE be an inevitable point on all forwarding paths to the
>CE. Eric ever used "BGP LOCAL_PREF" to compose a similar scenario
>(http://www.ietf.org/mail-archive/web/l3vpn/current/msg03691.html).
>
>[Mingui] For this subtle case, the redundant connection is not utilized in
>the first place. If customers prefer resilience to more specific routes, t=
he
>backup PE should not use the primary PE as the next hop.

[Bruno] IMO this is a normal routing behavior which needs to be supported. =
It doesn't mean that the redundant is not utilized because another more spe=
cific prefix could be "attached" to this redundant connection. It probably =
means that the CE/customer is using TE to better load balance the flows acr=
oss both connections.

>[Mingui] All in all, if customers really want the resilience, those routes
>via the primary PE SHOULD NOT be installed in the FIBs of backup PEs.

[Bruno] Good point. So you probably should add this to the document.

>[Mingui] By the way, the scenario you designed may suffer from transient
>loop issue. Imagine that the more specific routes fails on the primary PE,
>the primary PE will resort to the backup PE. At that time, it's probably
>that the backup PE is unaware of the failure. It will send packet back to
>the primary PE. Oops, loop occurs. Following the above "SHOULD NOT be
>installed" requirement, such kind of loops can be avoided.

[Bruno] You are right. I suspect that RFC 4364 implies that a PE should not=
 reflect back to the core, a VPN packet received from the core. But I haven=
't checked.

><snip>
>>More seriously:
>>- Draft minto does not need to define a new protocol (ICCP) in order to
>learn the
>>labels of the backup PE. BGP already provides this. While ICCP is a 79
>pages
>>draft, plus 11 for the extension.
>>- Draft zhang relies on the having the same label on redundant PE. While
>this is
>>doable, this is a significant change compared to the existing deployed
>model.
>>- regarding context label tabel
>>                  - From a standardization standpoint, context-specific
>label
>>space is already defined in RFC 5331, so nothing new.
>>                  - From an implementation standpoint, I agree that this
>>requires some additional resources in the forwarding plane. But draft min=
to
>>does not require that all PE support this. This can be performed by a
>protector
>>PE if some PE do not support it.
>
>[Mingui] If nothing new for protocols, this becomes an implementation issu=
e.
>Then, should this be considered in IETF? :-)

[Bruno] That's not a local implementation issue as this is a global behavio=
r/feature at the network level. And to allow this behavior we need all impl=
ementations to implement this feature.
Note that all IETF documents do not describe change of the bits sent on the=
 wire.
Finally, one protocol changed will be required.

>[Mingui] We do not define ICCP, we make use of it.

[Bruno] idem for context label :-)

> If we can have a solution happen in purely the control plane, as IETFers,=
 we should be happy.=20

[Bruno] Sure. But the solution relies on global VPN labels which is not wha=
t is deployed today. So it all depends on whether you will be able to deplo=
y such change before. Which will requires all implementations to do it whil=
e draft minto has no such dependency.

> If customers want this feature, I promise you will see this feature suppo=
rted
>by products in several months.

[Bruno] Ok. But I guess you mean a subset of the products currently deploye=
d. There may be multiple vendors/implementations in a given network. And so=
me implementations are sometimes even considered as legacy (by the vendor).

> For vendors who have already implemented
>ICCP, it can be faster. More importantly, this is a "once for all" effort
>compared to the redundant forwarding tables.
>
>[Mingui] As Robert and I discussed previously, existing deploy model does
>not prohibit PE to advertise the same label.=20

[Bruno] Agreed.

> I don't think this changes the existing deploy model.

[Bruno] I think it does.


>>So label table need not be stored repeatedly on RG members.
>>
>>#Bruno: agreed.
>>
>>
>>2. Also, it's easy to be deployed. It does not bring any change to P
>routers
>>(control plane & data plane). It even does not change the data plane of PE
>>routers.
>>
>>#Bruno: It's not easy to deploy as it mandates to update all PE routers,
>both
>>nominal and backup. While with draft-minto-2547-egress-node-fast-protecti=
on
>><http://tools.ietf.org/html/draft-minto-2547-egress-node-fast-protection-
>02>
>>the deployment of a single protector PE can fast protect all PE of the AS
>with no
>>change on existing PE.
>
>[Mingui] As I explained above, the update to the control plane should be O=
K.
>
>[Mingui] OK. Let me give an analysis of the draft-minto-2547-egress-node-
>fast-protection. I hope this is constructive when the draft is updated.
>
>[Mingui] a.	The co-located and hybrid models require configuration, which =
is
>error prone and increases a management burden to operators.

#Bruno: You need to configure the pairs of PE. But this is a one time confi=
guration on a per PE basis when the PE is provisioned. I don't think per VP=
N configuration is required as by listening to BGP routes, the backup PE ca=
n discover that it needs to back up the nominal one. Your proposition proba=
bly need the same configuration effort (configuring RG and vNH)

>[Mingui] b.	The centralized model is not robust. How do you handle the
>failure of the centralized protector itself? This problem had been proposed
>for the "central controller" stuff.

#Bruno: If one wants to protect the protection one may use a second (redund=
ant) protector.=20
However, as the protector is expected to be in use only few seconds per day=
 at most, I'm not sure people would consider such specific case of double f=
ailure.

>[Mingui] c.	The delegation of protector is topology dependent. I guess the
>number of possible alternative paths held by the protector is a much small=
er
>set of all possible alternative paths.

#Bruno: Indeed, currently the location of the protector is topology indepen=
dent. Simply because this relies on the existing FRR mechanism used in the =
core and this FRR may have coverage limitations (e.g. LFA). There are plans=
 to remove this limitation.
I'm not sure to understand your second point (second sentence).

>[Mingui] d.	The centralized protector has to manage the context label
>assignment and maintain multiple forwarding tables for all RGs. I am afraid
>this model is not scalable.

#Bruno: Just like a PE does (maintain multiple forwarding tables) so I thin=
k this is just as scalable as 4364 VPNs are. Besides, we are talking about =
dedicated protector PE so it can be choosen to scale in that direction (jus=
t like for VPN BGP RR)

>[Mingui] e.	There is a brief description on Fast ReRoute in Section 5.3. F=
or
>the "RSVP" choice, it depends on another individual draft
>[http://tools.ietf.org/html/draft-minto-2547-egress-node-fast-protection-
>02]. Does this draft mandates update on P and PE routers? For the "LDP"
>choice, it's not clear how IGP can find alternative paths (I find the
>"beyond the scope" words.). I think the coverage of alternative paths cann=
ot
>be very good, especially when the centralized protector is used.

#Bruno: For LDP, cf 2 points above.

>>3. In addition, it does not bear the restriction of "no penultimate-hop-
>popping".
>>
>>#Bruno: ultimate hop poping is only required for the label associated with
>the
>>context table of the backup PE. This is required to identify the context-
>specific
>>label space. This is not an additional argument compared to 1 (context
>label
>>table).
>
>[Mingui] I agree.
>
>Thanks,
>Mingui

___________________________________________________________________________=
______________________________________________

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

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


From zhangmingui@huawei.com  Mon Nov 18 01:32:59 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58ED811E81FD; Mon, 18 Nov 2013 01:32:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjLVpJc-1Rln; Mon, 18 Nov 2013 01:32:52 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id DC39511E81E6; Mon, 18 Nov 2013 01:32:01 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXZ72481; Mon, 18 Nov 2013 09:31:52 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 18 Nov 2013 09:31:45 +0000
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 18 Nov 2013 09:31:48 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.180]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Mon, 18 Nov 2013 17:31:42 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Thread-Topic: Why we consider the method of "label sharing for fast PE protection"
Thread-Index: AQHO4SIRsyqoYXqpzk6PHbocPpEtZZoqX9ZQ
Date: Mon, 18 Nov 2013 09:31:41 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E73367FF3A@nkgeml508-mbx.china.huawei.com>
References: <4552F0907735844E9204A62BBDD325E733660DBA@nkgeml508-mbx.china.huawei.com> <19124_1384271977_52825069_19124_7825_1_53C29892C857584299CBF5D05346208A070A3C8F@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4552F0907735844E9204A62BBDD325E7336623C5@nkgeml508-mbx.china.huawei.com> <28062_1384423942_5284A206_28062_2935_1_53C29892C857584299CBF5D05346208A070A4BFE@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <28062_1384423942_5284A206_28062_2935_1_53C29892C857584299CBF5D05346208A070A4BFE@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Subject: Re: [PWE3] Why we consider the method of "label sharing for fast PE	protection"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 18 Nov 2013 09:32:59 -0000

Hi Bruno,

Please find my comments inline below [Mingui].

>You have added pwe in cc. I'm not sure why as I'm following up on your
>presentation during L3 VPN WG on L3 VPN PE protection.

[Mingui] Sorry that I didn't explain the reason every time. There was a com=
panion draft presented in pwe3 for this l3vpn-PE-protection draft. Pwe3 WG =
determined they also need know the progress of this l3vpn draft.

>[Bruno] First, consider that in a "POP" there may be multiple PE, i.e. mor=
e than
>the 2 required for the dual homing. Let's say 5 PE.
>The number of RG is flexible, but this also comes with drawbacks.
>One option is to have a single RG. In this case, you indeed need a single =
vNH but
>you require global label allocation for the perimeter of those 5 PE. Which=
 roughly
>divide the available label space by 5.=20

[Mingui] That is a misinterpretation. Actually, all 5 PEs share the same la=
bel range (e.g., 1~1100) rather than dividing the label space. There is no =
scaling issue.

>Then if this represents a scaling issue, I
>guess you can call for bigger labels, e.g. by stacking 2 labels. But this =
requires
>more lookup work in the forwarding plane.=20

[Mingui] As explained above, it does not need multiple lookup. Remember, we=
 do not want to change the forwarding plane.

>Roughly equivalent to the label
>context space that you did not want in the first time...
>Another option is to have one RG per couple of PE. In this case you need 1=
0 vNH
>(IINM). That's roughly the number of PE but that's still *3 the number of =
states
>in the IGP so I think the document should talk about this.

[Mingui] On one hand, the above extreme case happens only in theory. The re=
ason we scope the document to talk about 2 PEs is that duel homing is the B=
CP. Think about the real deployment, I believe most POPs will use two PEs f=
or the redundant connection. On the other hand, even if you have 5 PEs in o=
ne POP, just put them into one RG. Therefore, the increase of the number of=
 states in the IGP is not so big.

[Mingui] But I agree with your advice that we can spend some words to addre=
ss this scaling issue in the document.

<snip>
>>[Mingui] All in all, if customers really want the resilience, those
>>routes via the primary PE SHOULD NOT be installed in the FIBs of backup P=
Es.
>
>[Bruno] Good point. So you probably should add this to the document.

[Mingui] Sure.

>>[Mingui] By the way, the scenario you designed may suffer from
>>transient loop issue. Imagine that the more specific routes fails on
>>the primary PE, the primary PE will resort to the backup PE. At that
>>time, it's probably that the backup PE is unaware of the failure. It
>>will send packet back to the primary PE. Oops, loop occurs. Following
>>the above "SHOULD NOT be installed" requirement, such kind of loops can b=
e
>avoided.
>
>[Bruno] You are right. I suspect that RFC 4364 implies that a PE should no=
t
>reflect back to the core, a VPN packet received from the core. But I haven=
't
>checked.

[Mingui] OK. How about the local-repair and label-retention technique? With=
 that technique, the primary PE may cache the route advertised by the backu=
p PE and use it when the route it learns from the CE fails. I guess this is=
sue is kind of off the track. We can talk more about it between us two.

>[Bruno] Sure. But the solution relies on global VPN labels which is not wh=
at is
>deployed today. So it all depends on whether you will be able to deploy su=
ch
>change before. Which will requires all implementations to do it while draf=
t minto
>has no such dependency.

[Mingui] The solution does not rely on *global* VPN labels. They are still =
locally assigned in the scope of the RG.

>> If customers want this feature, I promise you will see this feature
>>supported by products in several months.
>
>[Bruno] Ok. But I guess you mean a subset of the products currently deploy=
ed.
>There may be multiple vendors/implementations in a given network. And some
>implementations are sometimes even considered as legacy (by the vendor).

[Mingui] For those legacy products, operators can update their software. If=
 bare legacy PEs and label-sharing PEs are interconnected, ICCP connection =
will not be established. It allows PEs falls back to the non-redundant conn=
ection. For those label-sharing PEs from different vendors, if they impleme=
nt the same RFC, they are supposed to be interoperable.

>>[Mingui] c.	The delegation of protector is topology dependent. I guess th=
e
>>number of possible alternative paths held by the protector is a much
>>smaller set of all possible alternative paths.
>
>#Bruno: Indeed, currently the location of the protector is topology indepe=
ndent.
>Simply because this relies on the existing FRR mechanism used in the core =
and
>this FRR may have coverage limitations (e.g. LFA). There are plans to remo=
ve
>this limitation.
>I'm not sure to understand your second point (second sentence).

[Mingui] The central protector is delegated as the PLR, right? This further=
 reduces the coverage of LFA. As we know, a free LFA can have any router as=
 the PLR.

Thanks,
Mingui

From Alexander.Vainshtein@ecitele.com  Wed Nov 20 06:35:55 2013
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6B0A1AE35E; Wed, 20 Nov 2013 06:35:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level: 
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LxhtWoFcRyVP; Wed, 20 Nov 2013 06:35:53 -0800 (PST)
Received: from ilptbmg01-out.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9F11AE369; Wed, 20 Nov 2013 06:35:51 -0800 (PST)
X-AuditID: 93eaf2e7-b7f088e00000131c-1e-528cd73bc5eb
Received: from ILPTWPVEXCA02.ecitele.com ( [172.31.244.232]) by ilptbmg01-out.ecitele.com (Symantec Messaging Gateway) with SMTP id 3C.65.04892.B37DC825; Wed, 20 Nov 2013 17:37:31 +0200 (IST)
Received: from ILPTWPVEXMB01.ecitele.com ([fe80::f152:8eaf:8fb0:a5da]) by ILPTWPVEXCA02.ecitele.com ([::1]) with mapi id 14.03.0123.003; Wed, 20 Nov 2013 16:35:43 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@occnc.com" <curtis@occnc.com>, "kireeti@juniper.net" <kireeti@juniper.net>, "samante@apple.com" <samante@apple.com>, "agmalis@gmail.com" <agmalis@gmail.com>, "cpignata@cisco.com" <cpignata@cisco.com>
Thread-Topic: Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
Thread-Index: Ac7l/cfceKBnwYAgQmeoXy+M5Z0ABw==
Date: Wed, 20 Nov 2013 14:35:41 +0000
Message-ID: <F9336571731ADE42A5397FC831CEAA025392F92F@ILPTWPVEXMB01.ecitele.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.4.216.148]
Content-Type: multipart/alternative; boundary="_000_F9336571731ADE42A5397FC831CEAA025392F92FILPTWPVEXMB01ec_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHLsWRmVeSWpSXmKPExsUy+dWnL7o213uCDE4tYbY4/fwUm8WndztY LA4fmM5u8WPHJnaLf3PnMFvcWrqS1aLv0xYWi+PvP7BZfOj6werA6bH15A82jym/N7J67Jx1 l91jyZKfTB7Xm66yeyz+4ucxa3obm8ektWkBHFENjDaJeXn5JYklqQopqcXJtkoBRZllicmV SgqZKbZKhkoKBTmJyam5qXkltkqJBQWpeSlKdlwKGMAGqCwzTyE1Lzk/JTMv3VbJM9hf18LC 1FLXUMlOTdnQ2JorJCOzWCFVNzcxM0chN7W4ODE9VQEokrCFOWPys50sBRt1KtrunmJpYFyh 1sXIySEhYCLR+3kmM4QtJnHh3nq2LkYuDiGBg4wSS1dMYoFw1jBKrFvynR2kik3AVmLT6rtg VSICNxkltj/pZQdxmAXWMUq07XrNClIlLBAisbXlAiOILSIQKbHy8wMmCFtPYs38p2A2i4Cq xN+OpWwgNq9AgMTSd6fBehmB7vh+ag1YDbOAuMStJ/OZIO4TkFiy5zzUraISLx//Y4WwFSTu L/4IdAQHUH2+xKHrLBAjBSVOznzCAlEiKXFwxQ2WCYwis5BMnYXQMQtJB0SJjsSC3Z/YIGxt iWULXzPD2GcOPGZCFl/AyL6KUTQzp6AkKTfdwFAvNTmzJDUnVS85P3cTIySNPd/B+Gu+yiFG AQ5GJR5eyz3dQUKsiWXFlbmHGCU5mJREeYOO9QQJ8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuHt 2guU401JrKxKLcqHSQUBw28isxR3cj4wNeeVxBsbGBDJURLnXd4Q7i8kkA5Mj9mpqQWpRTBD ZTg4lCR49x8H2idYlJqeWpGWmVOCkGbi4AS5iQfoplsgNbzFBYm5xZnpEPlTjLoct35++sYo xJKXn5cqJc57F6RIAKQoozQPbg4s271iFAeGhjDvU5AqHmCmhJv0CmgJE9ASdslukCXAfAOX kmpgPFQ0VdBK7LPpUr68XvGJZufFv01pP7v+U/l6nrsz94fuzWtXEauecMf+bcYF24cqXSka 6oF79XaJ3J9Rzvg0781zo1L+Lx27BSomBXk4z/h+fuNLcY3FFpOagnZv5dh9VHefU3mt+Zwd jTMvvUgvWeFyQVJsjsiqT2d0vS7fPTuxMrtq++EdV5VYijMSDbWYi4oTATLGZPBRBAAA
Cc: "mpls@ietf.org" <mpls@ietf.org>, "Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, "pwe3 \(pwe3@ietf.org\)" <pwe3@ietf.org>
Subject: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 20 Nov 2013 14:35:55 -0000

--_000_F9336571731ADE42A5397FC831CEAA025392F92FILPTWPVEXMB01ec_
Content-Type: text/plain; charset="us-ascii"
content-transfer-encoding: quoted-printable

Hi all,
I would like to comment on the text in Section 2.1.8.1 "Pseudowire Sequence=
 Number" in
draft-ietf-mpls-forwarding-03 - MPLS Forwarding Compliance and Performance R=
equirements<http://tools.ietf.org/html/draft-ietf-mpls-forwarding-03>.

This section states, in short, that the main drive for using the sequence nu=
mber in the PW Control Word is handling of packet reordering events. TDM PWs=
 are presented as a major example, with CBR ATM services as another example.

In fact, this statement is not accurate.

The main drive for mandating the use of sequence number in TM PWs is the nee=
d to detect and count lost packets because the egress PE MUST compensate the=
 lost payload bit for bit.

Ability to compensate reordering of PW packets at egress is a side effect of=
 (a) sequence number usage and (b) usage of the de-jitter buffer in the egre=
ss PW. It is not mandatory and in any case is limited by the depth of the de=
-jitter buffer: re-ordered packets that cannot be accommodated within this b=
uffer are treated as lost.

Additional details can be found, e.g., in section 6.2.2 of RFC 4553<http://t=
ools.ietf.org/html/rfc4553>. Ability to re-order mis-ordered PW packets is d=
efined there as OPTIONAL, while replacement of the payload of lost PW packet=
s is defined as MANDATORY.

Hopefully these notes will be useful.


Regards,
     Sasha



This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


--_000_F9336571731ADE42A5397FC831CEAA025392F92FILPTWPVEXMB01ec_
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-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xm=
lns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http://w=
ww.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* 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;
	font-family:"Calibri","sans-serif";}
@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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all,<o:p></o:p></p>
<p class=3D"MsoNormal">I would like to comment on the text in Section 2.1.8.=
1 &#8220;Pseudowire Sequence Number&#8221; in
<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-mpls=
-forwarding-03">draft-ietf-mpls-forwarding-03 - MPLS Forwarding Compliance a=
nd Performance Requirements</a>.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This section states, in short, that the main drive fo=
r using the sequence number in the PW Control Word is handling of packet reo=
rdering events. TDM PWs are presented as a major example, with CBR ATM servi=
ces as another example.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In fact, this statement is not accurate.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The main drive for mandating the use of sequence numb=
er in TM PWs is the need to detect and count lost packets because the egress=
 PE MUST compensate the lost payload bit for bit.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ability to compensate reordering of PW packets at egr=
ess is a side effect of (a) sequence number usage and (b) usage of the de-ji=
tter buffer in the egress PW. It is not mandatory and in any case is limited=
 by the depth of the de-jitter
 buffer: re-ordered packets that cannot be accommodated within this buffer a=
re treated as lost.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Additional details can be found, e.g., in section 6.2=
.2 of <a href=3D"http://tools.ietf.org/html/rfc4553">
RFC 4553</a>. Ability to re-order mis-ordered PW packets is defined there as=
 OPTIONAL, while replacement of the payload of lost PW packets is defined as=
 MANDATORY.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hopefully these notes will be useful.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</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>
<p>
This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.
</p>
</body>
</html>

--_000_F9336571731ADE42A5397FC831CEAA025392F92FILPTWPVEXMB01ec_--

From curtis@occnc.com  Wed Nov 20 16:22:50 2013
Return-Path: <curtis@occnc.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D02AC1AE0C1; Wed, 20 Nov 2013 16:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_FAIL=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ToeVrAI63-dy; Wed, 20 Nov 2013 16:22:47 -0800 (PST)
Received: from daor.pair.com (daor.pair.com [209.68.5.146]) by ietfa.amsl.com (Postfix) with ESMTP id A39571ADF5E; Wed, 20 Nov 2013 16:22:47 -0800 (PST)
Received: from [173.9.106.154] (unknown [173.9.106.154]) by daor.pair.com (Postfix) with ESMTPSA id A9C7810E4A9; Wed, 20 Nov 2013 19:22:36 -0500 (EST)
Date: Wed, 20 Nov 2013 19:22:20 -0500
Message-ID: <qxj5mxxg6qtwdky8ij7uvwrl.1384993340457@email.android.com>
From: Curtis Villamizar <curtis@occnc.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=--_com.android.email_335386853140080_alt
Cc: samante@apple.com, "	Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, mpls@ietf.org, "kireeti@juniper.net	" <kireeti@juniper.net>, "cpignata@cisco.com	" <cpignata@cisco.com>, "pwe3 \(pwe3@ietf.org\)	" <pwe3@ietf.org>
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 21 Nov 2013 00:22:51 -0000

----_com.android.email_335386853140080_alt
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

U2FzaGEsCgpUaGFua3MgZm9yIHBvaW50aW5nIHRoaXMgb3V0LiAgSSdsbCBwcm9wb3NlIHJlcGxh
Y2VtZW50IHRleHQgc2hvcnRseS4KCkN1cnRpcwoKU2VudCBmcm9tIG15IFZlcml6b24gV2lyZWxl
c3MgNEcgTFRFIERST0lECgpBbGV4YW5kZXIgVmFpbnNodGVpbiA8QWxleGFuZGVyLlZhaW5zaHRl
aW5AZWNpdGVsZS5jb20+IHdyb3RlOgoKPjwhLS0gLyogRm9udCBEZWZpbml0aW9ucyAqLyBAZm9u
dC1mYWNlIAl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsgCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMg
MiA0O30gLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8gcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwg
ZGl2Lk1zb05vcm1hbCAJe21hcmdpbjowY207IAltYXJnaW4tYm90dG9tOi4wMDAxcHQ7IAlmb250
LXNpemU6MTEuMHB0OyAJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9IGE6bGlu
aywgc3Bhbi5Nc29IeXBlcmxpbmsgCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7IAljb2xvcjpibHVl
OyAJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9IGE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxp
bmtGb2xsb3dlZCAJe21zby1zdHlsZS1wcmlvcml0eTo5OTsgCWNvbG9yOnB1cnBsZTsgCXRleHQt
ZGVjb3JhdGlvbjp1bmRlcmxpbmU7fSBzcGFuLkVtYWlsU3R5bGUxNyAJe21zby1zdHlsZS10eXBl
OnBlcnNvbmFsLWNvbXBvc2U7IAlmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOyAJ
Y29sb3I6d2luZG93dGV4dDt9IC5Nc29DaHBEZWZhdWx0IAl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0
LW9ubHk7IAlmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30gQHBhZ2UgV29yZFNl
Y3Rpb24xIAl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7IAltYXJnaW46NzIuMHB0IDkwLjBwdCA3Mi4w
cHQgOTAuMHB0O30gZGl2LldvcmRTZWN0aW9uMSAJe3BhZ2U6V29yZFNlY3Rpb24xO30gLS0+IAo+
Cj5IaSBhbGwsCj4KPkkgd291bGQgbGlrZSB0byBjb21tZW50IG9uIHRoZSB0ZXh0IGluIFNlY3Rp
b24gMi4xLjguMSDigJxQc2V1ZG93aXJlIFNlcXVlbmNlIE51bWJlcuKAnSBpbiAKPgo+ZHJhZnQt
aWV0Zi1tcGxzLWZvcndhcmRpbmctMDMgLSBNUExTIEZvcndhcmRpbmcgQ29tcGxpYW5jZSBhbmQg
UGVyZm9ybWFuY2UgUmVxdWlyZW1lbnRzLgo+Cj7CoAo+Cj5UaGlzIHNlY3Rpb24gc3RhdGVzLCBp
biBzaG9ydCwgdGhhdCB0aGUgbWFpbiBkcml2ZSBmb3IgdXNpbmcgdGhlIHNlcXVlbmNlIG51bWJl
ciBpbiB0aGUgUFcgQ29udHJvbCBXb3JkIGlzIGhhbmRsaW5nIG9mIHBhY2tldCByZW9yZGVyaW5n
IGV2ZW50cy4gVERNIFBXcyBhcmUgcHJlc2VudGVkIGFzIGEgbWFqb3IgZXhhbXBsZSwgd2l0aCBD
QlIgQVRNIHNlcnZpY2VzIGFzIGFub3RoZXIgZXhhbXBsZS4KPgo+wqAKPgo+SW4gZmFjdCwgdGhp
cyBzdGF0ZW1lbnQgaXMgbm90IGFjY3VyYXRlLgo+Cj7CoAo+Cj5UaGUgbWFpbiBkcml2ZSBmb3Ig
bWFuZGF0aW5nIHRoZSB1c2Ugb2Ygc2VxdWVuY2UgbnVtYmVyIGluIFRNIFBXcyBpcyB0aGUgbmVl
ZCB0byBkZXRlY3QgYW5kIGNvdW50IGxvc3QgcGFja2V0cyBiZWNhdXNlIHRoZSBlZ3Jlc3MgUEUg
TVVTVCBjb21wZW5zYXRlIHRoZSBsb3N0IHBheWxvYWQgYml0IGZvciBiaXQuIAo+Cj7CoAo+Cj5B
YmlsaXR5IHRvIGNvbXBlbnNhdGUgcmVvcmRlcmluZyBvZiBQVyBwYWNrZXRzIGF0IGVncmVzcyBp
cyBhIHNpZGUgZWZmZWN0IG9mIChhKSBzZXF1ZW5jZSBudW1iZXIgdXNhZ2UgYW5kIChiKSB1c2Fn
ZSBvZiB0aGUgZGUtaml0dGVyIGJ1ZmZlciBpbiB0aGUgZWdyZXNzIFBXLiBJdCBpcyBub3QgbWFu
ZGF0b3J5IGFuZCBpbiBhbnkgY2FzZSBpcyBsaW1pdGVkIGJ5IHRoZSBkZXB0aCBvZiB0aGUgZGUt
aml0dGVyIGJ1ZmZlcjogcmUtb3JkZXJlZCBwYWNrZXRzIHRoYXQgY2Fubm90IGJlIGFjY29tbW9k
YXRlZCB3aXRoaW4gdGhpcyBidWZmZXIgYXJlIHRyZWF0ZWQgYXMgbG9zdC4KPgo+wqAKPgo+QWRk
aXRpb25hbCBkZXRhaWxzIGNhbiBiZSBmb3VuZCwgZS5nLiwgaW4gc2VjdGlvbiA2LjIuMiBvZiBS
RkMgNDU1My4gQWJpbGl0eSB0byByZS1vcmRlciBtaXMtb3JkZXJlZCBQVyBwYWNrZXRzIGlzIGRl
ZmluZWQgdGhlcmUgYXMgT1BUSU9OQUwsIHdoaWxlIHJlcGxhY2VtZW50IG9mIHRoZSBwYXlsb2Fk
IG9mIGxvc3QgUFcgcGFja2V0cyBpcyBkZWZpbmVkIGFzIE1BTkRBVE9SWS4KPgo+wqAKPgo+SG9w
ZWZ1bGx5IHRoZXNlIG5vdGVzIHdpbGwgYmUgdXNlZnVsLgo+Cj7CoAo+Cj7CoAo+Cj5SZWdhcmRz
LAo+Cj7CoMKgwqDCoCBTYXNoYQo+Cj7CoAo+Cj5UaGlzIGUtbWFpbCBtZXNzYWdlIGlzIGludGVu
ZGVkIGZvciB0aGUgcmVjaXBpZW50IG9ubHkgYW5kIGNvbnRhaW5zIGluZm9ybWF0aW9uIHdoaWNo
IGlzIENPTkZJREVOVElBTCBhbmQgd2hpY2ggbWF5IGJlIHByb3ByaWV0YXJ5IHRvIEVDSSBUZWxl
Y29tLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgcGxl
YXNlIGluZm9ybSB1cyBieSBlLW1haWwsIHBob25lIG9yIGZheCwgYW5kIHRoZW4gZGVsZXRlIHRo
ZSBvcmlnaW5hbCBhbmQgYWxsIGNvcGllcyB0aGVyZW9mLiAKPgo=
----_com.android.email_335386853140080_alt
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGRpdj48ZGl2PlNhc2hhLDwvZGl2PjxkaXY+PGJyLz48L2Rpdj48ZGl2PlRoYW5rcyBmb3IgcG9p
bnRpbmcgdGhpcyBvdXQuJiMxNjA7IEkmIzM5O2xsIHByb3Bvc2UgcmVwbGFjZW1lbnQgdGV4dCBz
aG9ydGx5LjwvZGl2PjxkaXY+PGJyLz48L2Rpdj48ZGl2PkN1cnRpczwvZGl2PjxkaXY+PGJyLz48
L2Rpdj48ZGl2Pjxmb250IHN0eWxlPSJjb2xvcjojMzMzMzMzIj48aT5TZW50IGZyb20gbXkgVmVy
aXpvbiBXaXJlbGVzcyA0RyBMVEUgRFJPSUQ8L2k+PC9mb250PjwvZGl2PjwvZGl2Pjxicj48YnI+
QWxleGFuZGVyIFZhaW5zaHRlaW4gJmx0O0FsZXhhbmRlci5WYWluc2h0ZWluQGVjaXRlbGUuY29t
Jmd0OyB3cm90ZTo8YnI+PGJyPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkhpIGFsbCw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
Pkkgd291bGQgbGlrZSB0byBjb21tZW50IG9uIHRoZSB0ZXh0IGluIFNlY3Rpb24gMi4xLjguMSAm
IzgyMjA7UHNldWRvd2lyZSBTZXF1ZW5jZSBOdW1iZXImIzgyMjE7IGluDQo8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9o
dG1sL2RyYWZ0LWlldGYtbXBscy1mb3J3YXJkaW5nLTAzIj5kcmFmdC1pZXRmLW1wbHMtZm9yd2Fy
ZGluZy0wMyAtIE1QTFMgRm9yd2FyZGluZyBDb21wbGlhbmNlIGFuZCBQZXJmb3JtYW5jZSBSZXF1
aXJlbWVudHM8L2E+LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIHNlY3Rpb24gc3RhdGVz
LCBpbiBzaG9ydCwgdGhhdCB0aGUgbWFpbiBkcml2ZSBmb3IgdXNpbmcgdGhlIHNlcXVlbmNlIG51
bWJlciBpbiB0aGUgUFcgQ29udHJvbCBXb3JkIGlzIGhhbmRsaW5nIG9mIHBhY2tldCByZW9yZGVy
aW5nIGV2ZW50cy4gVERNIFBXcyBhcmUgcHJlc2VudGVkIGFzIGEgbWFqb3IgZXhhbXBsZSwgd2l0
aCBDQlIgQVRNIHNlcnZpY2VzIGFzIGFub3RoZXIgZXhhbXBsZS48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+SW4gZmFjdCwgdGhpcyBzdGF0ZW1lbnQgaXMgbm90IGFjY3VyYXRlLjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5UaGUgbWFpbiBkcml2ZSBmb3IgbWFuZGF0aW5nIHRoZSB1c2Ugb2Ygc2Vx
dWVuY2UgbnVtYmVyIGluIFRNIFBXcyBpcyB0aGUgbmVlZCB0byBkZXRlY3QgYW5kIGNvdW50IGxv
c3QgcGFja2V0cyBiZWNhdXNlIHRoZSBlZ3Jlc3MgUEUgTVVTVCBjb21wZW5zYXRlIHRoZSBsb3N0
IHBheWxvYWQgYml0IGZvciBiaXQuDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWJpbGl0eSB0
byBjb21wZW5zYXRlIHJlb3JkZXJpbmcgb2YgUFcgcGFja2V0cyBhdCBlZ3Jlc3MgaXMgYSBzaWRl
IGVmZmVjdCBvZiAoYSkgc2VxdWVuY2UgbnVtYmVyIHVzYWdlIGFuZCAoYikgdXNhZ2Ugb2YgdGhl
IGRlLWppdHRlciBidWZmZXIgaW4gdGhlIGVncmVzcyBQVy4gSXQgaXMgbm90IG1hbmRhdG9yeSBh
bmQgaW4gYW55IGNhc2UgaXMgbGltaXRlZCBieSB0aGUgZGVwdGggb2YgdGhlIGRlLWppdHRlcg0K
IGJ1ZmZlcjogcmUtb3JkZXJlZCBwYWNrZXRzIHRoYXQgY2Fubm90IGJlIGFjY29tbW9kYXRlZCB3
aXRoaW4gdGhpcyBidWZmZXIgYXJlIHRyZWF0ZWQgYXMgbG9zdC48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+QWRkaXRpb25hbCBkZXRhaWxzIGNhbiBiZSBmb3VuZCwgZS5nLiwgaW4gc2VjdGlvbiA2
LjIuMiBvZiA8YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM0NTUzIj4NClJG
QyA0NTUzPC9hPi4gQWJpbGl0eSB0byByZS1vcmRlciBtaXMtb3JkZXJlZCBQVyBwYWNrZXRzIGlz
IGRlZmluZWQgdGhlcmUgYXMgT1BUSU9OQUwsIHdoaWxlIHJlcGxhY2VtZW50IG9mIHRoZSBwYXls
b2FkIG9mIGxvc3QgUFcgcGFja2V0cyBpcyBkZWZpbmVkIGFzIE1BTkRBVE9SWS48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+SG9wZWZ1bGx5IHRoZXNlIG5vdGVzIHdpbGwgYmUgdXNlZnVsLjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPlJlZ2FyZHMsPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgU2FzaGE8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cD4NClRoaXMgZS1tYWlsIG1l
c3NhZ2UgaXMgaW50ZW5kZWQgZm9yIHRoZSByZWNpcGllbnQgb25seSBhbmQgY29udGFpbnMgaW5m
b3JtYXRpb24gd2hpY2ggaXMgQ09ORklERU5USUFMIGFuZCB3aGljaCBtYXkgYmUgcHJvcHJpZXRh
cnkgdG8gRUNJIFRlbGVjb20uIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9u
IGluIGVycm9yLCBwbGVhc2UgaW5mb3JtIHVzIGJ5IGUtbWFpbCwgcGhvbmUgb3IgZmF4LCBhbmQg
dGhlbiBkZWxldGUgdGhlIG9yaWdpbmFsIGFuZCBhbGwgY29waWVzIHRoZXJlb2YuDQo8L3A+DQo=
----_com.android.email_335386853140080_alt--


From zhangmingui@huawei.com  Wed Nov 20 19:13:12 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0F431ADE87 for <pwe3@ietfa.amsl.com>; Wed, 20 Nov 2013 19:13:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.726
X-Spam-Level: 
X-Spam-Status: No, score=-4.726 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id StxM0gCrHXHj for <pwe3@ietfa.amsl.com>; Wed, 20 Nov 2013 19:13:11 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 387001ADBCF for <pwe3@ietf.org>; Wed, 20 Nov 2013 19:13:11 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAN75501; Thu, 21 Nov 2013 03:13:04 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 21 Nov 2013 03:12:51 +0000
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 21 Nov 2013 03:13:03 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.180]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Thu, 21 Nov 2013 11:12:58 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: Any comments on the draft of STP Application of ICCP ?
Thread-Index: AQHO5meUAD6ywCXV6UKW4/do2PsE7w==
Date: Thu, 21 Nov 2013 03:12:58 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E733686A38@nkgeml508-mbx.china.huawei.com>
References: <4552F0907735844E9204A62BBDD325E733643462@nkgeml508-mbx.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E733643462@nkgeml508-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [PWE3] Any comments on the draft of STP Application of ICCP ?
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 21 Nov 2013 03:13:13 -0000

Hi There,=20

In the Vancouver meeting, we presented the following draft
STP Application of ICCP, http://tools.ietf.org/html/draft-zhang-pwe3-iccp-s=
tp-00

Authors would like to see more feedbacks on this draft. Please help to revi=
ew it and send your comments on the mailing list. Would be highly appreciat=
ed!

Thanks,
Mingui

From matthew.bocci@alcatel-lucent.com  Thu Nov 21 17:15:43 2013
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBA361AE0E2; Thu, 21 Nov 2013 17:15:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W-ontaDgs0W0; Thu, 21 Nov 2013 17:15:41 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id A89441A1F77; Thu, 21 Nov 2013 17:15:41 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id rAM1FVu5026672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 21 Nov 2013 19:15:33 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rAM1FUCU021525 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Nov 2013 02:15:31 +0100
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.146]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Fri, 22 Nov 2013 02:15:30 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: Response to Liaison on Clarifying P2MP Combinations
Thread-Index: AQHO5yBViXeYAQSEMkaxB6wA8sJs3w==
Date: Fri, 22 Nov 2013 01:15:29 +0000
Message-ID: <CEB45EA6.580D2%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.3.9.131030
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_CEB45EA6580D2matthewboccialcatellucentcom_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: [PWE3] Response to Liaison on Clarifying P2MP Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 22 Nov 2013 01:15:44 -0000

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

PWE3 and MPLS Working Groups

Please find below a draft response to the liaison from ITU-T SG15 of July 2=
013 on clarifying combinations of point to multipoint pseudowires and LSPs.

Please direct any discussion to the PWE3 list.

We would like to reply to the ITU by Wednesday 27th November.

Regards

Matthew and Andy

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

Body:

Thank you for your liaison of July 2013 inquiring on the valid use of p2mp =
pseudowires and LSPs. A new version of the "Requirements and Framework for =
Point-to-Multipoint Pseudowires over MPLS PSNs" is available (see  draft-ie=
tf-pwe3-p2mp-pw-requirements-06.txt) that should help to clarify some of th=
e points in your liaison.

In general, point-to-point PWs are not intended to be used in conjunction w=
ith P2MP LSPs.  There is currently no way for the PEs terminating all of th=
e P2MP LSP leaves to establish the applicable PW/FEC label mappings.  We do=
 not believe that this case is supported by the PWE3 architecture.  The onl=
y current valid case for P2MP PWs is when used with corresponding P2MP LSPs=
, as described in the draft referenced above.

Best regards,


Matthew Bocci
Andrew Malis

IETF PWE3 Working Group Chairs

--_000_CEB45EA6580D2matthewboccialcatellucentcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <26F0E485C898B54CB160CEFFFE82C5D2@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>PWE3 and MPLS Working Groups</div>
<div><br>
</div>
<div>Please find below a draft response to the liaison from ITU-T SG15 of J=
uly 2013 on clarifying combinations of point to multipoint pseudowires and =
LSPs.</div>
<div><br>
</div>
<div>Please direct any discussion to the PWE3 list.</div>
<div><br>
</div>
<div>We would like to reply to the ITU by Wednesday 27th November.</div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>Matthew and Andy</div>
<div><br>
</div>
<div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div>
<div><br>
</div>
<div>Body:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>=
</div>
<div><br>
</div>
<div>Thank you for your liaison of July 2013 inquiring on the valid use of =
p2mp pseudowires and LSPs. A new version of the &quot;Requirements and Fram=
ework for Point-to-Multipoint Pseudowires over MPLS PSNs&quot; is available=
 (see &nbsp;draft-ietf-pwe3-p2mp-pw-requirements-06.txt)
 that should help to clarify some of the points in your liaison.</div>
<div>&nbsp;&nbsp;</div>
<div>In general, point-to-point PWs are not intended to be used in conjunct=
ion with P2MP LSPs. &nbsp;There is currently no way for the PEs terminating=
 all of the P2MP LSP leaves to establish the applicable PW/FEC label mappin=
gs. &nbsp;We do not believe that this case
 is supported by the PWE3 architecture. &nbsp;The only current valid case f=
or P2MP PWs is when used with corresponding P2MP LSPs, as described in the =
draft referenced above.</div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div><br>
</div>
<div>Matthew Bocci</div>
<div>Andrew Malis</div>
<div><br>
</div>
<div>IETF PWE3 Working Group Chairs</div>
</body>
</html>

--_000_CEB45EA6580D2matthewboccialcatellucentcom_--

From fenghaisheng@huawei.com  Thu Nov 21 02:56:58 2013
Return-Path: <fenghaisheng@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDF681AE011 for <pwe3@ietfa.amsl.com>; Thu, 21 Nov 2013 02:56:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.725
X-Spam-Level: 
X-Spam-Status: No, score=-4.725 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wiZ6OlBZPvhP for <pwe3@ietfa.amsl.com>; Thu, 21 Nov 2013 02:56:57 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id CD5DF1AD958 for <pwe3@ietf.org>; Thu, 21 Nov 2013 02:56:56 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYE09216; Thu, 21 Nov 2013 10:56:49 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 21 Nov 2013 10:56:35 +0000
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 21 Nov 2013 10:56:48 +0000
Received: from NKGEML503-MBS.china.huawei.com ([169.254.6.87]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Thu, 21 Nov 2013 18:56:43 +0800
From: Fenghaisheng <fenghaisheng@huawei.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: Feedback on "Any comments on the draft of STP Application of ICCP ?" 
Thread-Index: Ac7mqFwbNyxm3E5XSoig0DW8/btf0A==
Date: Thu, 21 Nov 2013 10:56:42 +0000
Message-ID: <077FD3C0391C334DA3885E1D5729450846670BD3@nkgeml503-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.30.116]
Content-Type: multipart/alternative; boundary="_000_077FD3C0391C334DA3885E1D5729450846670BD3nkgeml503mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [PWE3] Feedback on "Any comments on the draft of STP Application of ICCP ?"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 22 Nov 2013 02:16:01 -0000

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


I think the proposal can be useful. When one connection fails, the other co=
nnection can be leveraged after a spanning tree recalculation. This kind of=
 multiple attachments offers certain reliability.

Thanks,
Haisheng Feng
_________

Hi There,

In the Vancouver meeting, we presented the following draft STP Application =
of ICCP, http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00

Authors would like to see more feedbacks on this draft. Please help to revi=
ew it and send your comments on the mailing list. Would be highly appreciat=
ed!

Thanks,
Mingui


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@\5B8B\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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 Definitions */
@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=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:&#23435=
;&#20307;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black">I thin=
k the proposal can be useful. When one connection fails, the other connecti=
on can be leveraged after a spanning tree
 recalculation. This kind of multiple attachments offers certain reliabilit=
y.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black">Thanks=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black">Haishe=
ng Feng<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black">______=
___<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black">Hi The=
re,
<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black">In the=
 Vancouver meeting, we presented the following draft STP Application of ICC=
P,
<a href=3D"http://tools.ietf.org/html/draft-zhang-pwe3-iccp-stp-00"><span s=
tyle=3D"color:black;text-decoration:none">http://tools.ietf.org/html/draft-=
zhang-pwe3-iccp-stp-00</span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black">Author=
s would like to see more feedbacks on this draft. Please help to review it =
and send your comments on the mailing list.
 Would be highly appreciated!<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black">Thanks=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-autospa=
ce:none"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black">Mingui=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_077FD3C0391C334DA3885E1D5729450846670BD3nkgeml503mbschi_--

From zhai.hongjun@zte.com.cn  Fri Nov 22 05:27:27 2013
Return-Path: <zhai.hongjun@zte.com.cn>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17EE51ADEB4 for <pwe3@ietfa.amsl.com>; Fri, 22 Nov 2013 05:27:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.992
X-Spam-Level: 
X-Spam-Status: No, score=-98.992 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.525, USER_IN_WHITELIST=-100] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o_cYLnae1UpL for <pwe3@ietfa.amsl.com>; Fri, 22 Nov 2013 05:27:23 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id C5C541ADBD4 for <pwe3@ietf.org>; Fri, 22 Nov 2013 05:27:22 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 5A21D7BFA6F for <pwe3@ietf.org>; Fri, 22 Nov 2013 21:26:59 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 41749734C42 for <pwe3@ietf.org>; Fri, 22 Nov 2013 21:26:58 +0800 (CST)
Received: (from root@localhost) by mse01.zte.com.cn id rAMDRAeT059109 for <pwe3@ietf.org>; Fri, 22 Nov 2013 21:27:10 +0800 (GMT-8) (envelope-from zhai.hongjun@zte.com.cn)
Message-Id: <201311221327.rAMDRAeT059109@mse01.zte.com.cn>
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id rAM2sEsf044062; Fri, 22 Nov 2013 10:54:14 +0800 (GMT-8) (envelope-from zhai.hongjun@zte.com.cn)
In-Reply-To: <077FD3C0391C334DA3885E1D5729450846670BD3@nkgeml503-mbs.china.huawei.com>
To: Fenghaisheng <fenghaisheng@huawei.com>
MIME-Version: 1.0
X-KeepSent: 85999368:10469D6A-48257C2B:000CB2B5; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
From: zhai.hongjun@zte.com.cn
Date: Fri, 22 Nov 2013 10:54:03 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-11-22 10:54:07, Serialize complete at 2013-11-22 10:54:07
Content-Type: multipart/alternative; boundary="=_alternative 001030D948257C2B_="
X-MAIL: mse01.zte.com.cn rAMDRAeT059109
X-MSS: AUDITRELEASE@mse01.zte.com.cn
Cc: pwe3 <pwe3-bounces@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Feedback on "Any comments on the draft of STP Application of ICCP ?"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 22 Nov 2013 13:27:27 -0000

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

SGksDQoNCkkgcmV2aWV3ZWQgdGhpcyBkcmFmdCwgaXQncyB1c2VmdWwuIEkgaGF2ZSBhIGNvbW1l
bnQuDQoNCkluIHRoZSAiU1RQIERpc2Nvbm5lY3QgQ2F1c2UgVExWIiwgd2h5IGEgc3RyaW5nIGZp
ZWxkIHJhdGhlciB0aGFuIA0Kd2VsbC1kZWZpbmVkIGludGVnZXIgY29kZXMgZmllbGQgaXMgdXNl
ZCB0byBjYXJyeSB0aGUgZGlzY29ubmVjdCBjYXVzZT8gDQpHZXJuZXJhbGx5LCBhbiBpbnRlZ2Vy
IGNhbiByZWR1Y2UgdGhlIG5lY2Vzc2FyeSBiaXRzIGluIHBhY2tldCB0aGFuIGEgDQpzdHJpbmcu
DQoNCg0KVGhhbmtzLA0KSG9uZ2p1biBaaGFpDQoNCg0KDQoNCkZlbmdoYWlzaGVuZyA8ZmVuZ2hh
aXNoZW5nQGh1YXdlaS5jb20+IA0Kt6K8/sjLOiAgInB3ZTMiIDxwd2UzLWJvdW5jZXNAaWV0Zi5v
cmc+DQoyMDEzLTExLTIxIDE4OjU2DQoNCsrVvP7Iyw0KInB3ZTNAaWV0Zi5vcmciIDxwd2UzQGll
dGYub3JnPg0Ks63LzQ0KDQrW98ziDQpbUFdFM10gRmVlZGJhY2sgb24gIkFueSBjb21tZW50cyBv
biB0aGUgZHJhZnQgb2YgU1RQIEFwcGxpY2F0aW9uIG9mIElDQ1AgDQo/Ig0KDQoNCg0KDQoNCg0K
IA0KSSB0aGluayB0aGUgcHJvcG9zYWwgY2FuIGJlIHVzZWZ1bC4gV2hlbiBvbmUgY29ubmVjdGlv
biBmYWlscywgdGhlIG90aGVyIA0KY29ubmVjdGlvbiBjYW4gYmUgbGV2ZXJhZ2VkIGFmdGVyIGEg
c3Bhbm5pbmcgdHJlZSByZWNhbGN1bGF0aW9uLiBUaGlzIGtpbmQgDQpvZiBtdWx0aXBsZSBhdHRh
Y2htZW50cyBvZmZlcnMgY2VydGFpbiByZWxpYWJpbGl0eS4NCiANClRoYW5rcywNCkhhaXNoZW5n
IEZlbmcNCl9fX19fX19fXw0KIA0KSGkgVGhlcmUsIA0KIA0KSW4gdGhlIFZhbmNvdXZlciBtZWV0
aW5nLCB3ZSBwcmVzZW50ZWQgdGhlIGZvbGxvd2luZyBkcmFmdCBTVFAgQXBwbGljYXRpb24gDQpv
ZiBJQ0NQLCBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC16aGFuZy1wd2UzLWljY3At
c3RwLTAwDQogDQpBdXRob3JzIHdvdWxkIGxpa2UgdG8gc2VlIG1vcmUgZmVlZGJhY2tzIG9uIHRo
aXMgZHJhZnQuIFBsZWFzZSBoZWxwIHRvIA0KcmV2aWV3IGl0IGFuZCBzZW5kIHlvdXIgY29tbWVu
dHMgb24gdGhlIG1haWxpbmcgbGlzdC4gV291bGQgYmUgaGlnaGx5IA0KYXBwcmVjaWF0ZWQhDQog
DQpUaGFua3MsDQpNaW5ndWkNCiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KcHdlMyBtYWlsaW5nIGxpc3QNCnB3ZTNAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHdlMw0KDQoNCg==
--=_alternative 001030D948257C2B_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpLDwvZm9udD4NCjxicj4NCjxi
cj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+SSByZXZpZXdlZCB0aGlzIGRyYWZ0LCBp
dCdzIHVzZWZ1bC4NCkkgaGF2ZSBhIGNvbW1lbnQuPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNp
emU9MiBmYWNlPSJzYW5zLXNlcmlmIj5JbiB0aGUgJnF1b3Q7U1RQIERpc2Nvbm5lY3QgQ2F1c2Ug
VExWJnF1b3Q7LA0Kd2h5IGEgc3RyaW5nIGZpZWxkIHJhdGhlciB0aGFuIHdlbGwtZGVmaW5lZCBp
bnRlZ2VyIGNvZGVzIGZpZWxkIGlzIHVzZWQNCnRvIGNhcnJ5IHRoZSBkaXNjb25uZWN0IGNhdXNl
PyBHZXJuZXJhbGx5LCBhbiBpbnRlZ2VyIGNhbiByZWR1Y2UgdGhlIG5lY2Vzc2FyeQ0KYml0cyBp
biBwYWNrZXQgdGhhbiBhIHN0cmluZy48L2ZvbnQ+PHR0Pjxmb250IHNpemU9Mz48YnI+DQo8L2Zv
bnQ+PC90dD4NCjx0YWJsZT4NCjx0cj4NCjx0ZD48Zm9udCBzaXplPTI+PGJyPg0KPC9mb250Pjxm
b250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5UaGFua3MsPC9mb250Pg0KPGJyPjxmb250IHNp
emU9MiBmYWNlPSJzYW5zLXNlcmlmIj5Ib25nanVuIFpoYWk8L2ZvbnQ+PC90YWJsZT4NCjxicj4N
Cjxicj4NCjxicj4NCjxicj4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8
dGQgd2lkdGg9MzYlPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj48Yj5GZW5naGFpc2hl
bmcgJmx0O2ZlbmdoYWlzaGVuZ0BodWF3ZWkuY29tJmd0OzwvYj4NCjwvZm9udD4NCjxicj48Zm9u
dCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+t6K8/sjLOiAmbmJzcDsmcXVvdDtwd2UzJnF1b3Q7
ICZsdDtwd2UzLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7PC9mb250Pg0KPHA+PGZvbnQgc2l6ZT0xIGZh
Y2U9InNhbnMtc2VyaWYiPjIwMTMtMTEtMjEgMTg6NTY8L2ZvbnQ+DQo8dGQgd2lkdGg9NjMlPg0K
PHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmln
aHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPsrVvP7IyzwvZm9udD48L2Rpdj4NCjx0
ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+JnF1b3Q7cHdlM0BpZXRmLm9yZyZxdW90
OyAmbHQ7cHdlM0BpZXRmLm9yZyZndDs8L2ZvbnQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxk
aXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPrOty808L2ZvbnQ+
PC9kaXY+DQo8dGQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZv
bnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPtb3zOI8L2ZvbnQ+PC9kaXY+DQo8dGQ+PGZvbnQg
c2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPltQV0UzXSBGZWVkYmFjayBvbiAmcXVvdDtBbnkgY29t
bWVudHMNCm9uIHRoZSBkcmFmdCBvZiBTVFAgQXBwbGljYXRpb24gb2YgSUNDUCA/JnF1b3Q7PC9m
b250PjwvdGFibGU+DQo8YnI+DQo8dGFibGU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjx0ZD48
L3RhYmxlPg0KPGJyPjwvdGFibGU+DQo8YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0zIGZhY2U9
IsvOzOUiPiZuYnNwOzwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0iQ2FsaWJyaSI+SSB0
aGluayB0aGUgcHJvcG9zYWwgY2FuIGJlIHVzZWZ1bC4gV2hlbg0Kb25lIGNvbm5lY3Rpb24gZmFp
bHMsIHRoZSBvdGhlciBjb25uZWN0aW9uIGNhbiBiZSBsZXZlcmFnZWQgYWZ0ZXIgYSBzcGFubmlu
Zw0KdHJlZSByZWNhbGN1bGF0aW9uLiBUaGlzIGtpbmQgb2YgbXVsdGlwbGUgYXR0YWNobWVudHMg
b2ZmZXJzIGNlcnRhaW4gcmVsaWFiaWxpdHkuPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNl
PSJDYWxpYnJpIj4mbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkNhbGlicmki
PlRoYW5rcyw8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkNhbGlicmkiPkhhaXNoZW5n
IEZlbmc8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkNhbGlicmkiPl9fX19fX19fXzwv
Zm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0iQ2FsaWJyaSI+Jm5ic3A7PC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJDYWxpYnJpIj5IaSBUaGVyZSwgPC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBmYWNlPSJDYWxpYnJpIj4mbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZh
Y2U9IkNhbGlicmkiPkluIHRoZSBWYW5jb3V2ZXIgbWVldGluZywgd2UgcHJlc2VudGVkDQp0aGUg
Zm9sbG93aW5nIGRyYWZ0IFNUUCBBcHBsaWNhdGlvbiBvZiBJQ0NQLCA8L2ZvbnQ+PGEgaHJlZj0i
aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtemhhbmctcHdlMy1pY2NwLXN0cC0wMCI+
PGZvbnQgc2l6ZT0yIGZhY2U9IkNhbGlicmkiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LXpoYW5nLXB3ZTMtaWNjcC1zdHAtMDA8L2ZvbnQ+PC9hPg0KPGJyPjxmb250IHNpemU9MiBm
YWNlPSJDYWxpYnJpIj4mbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkNhbGli
cmkiPkF1dGhvcnMgd291bGQgbGlrZSB0byBzZWUgbW9yZSBmZWVkYmFja3MNCm9uIHRoaXMgZHJh
ZnQuIFBsZWFzZSBoZWxwIHRvIHJldmlldyBpdCBhbmQgc2VuZCB5b3VyIGNvbW1lbnRzIG9uIHRo
ZSBtYWlsaW5nDQpsaXN0LiBXb3VsZCBiZSBoaWdobHkgYXBwcmVjaWF0ZWQhPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJDYWxpYnJpIj4mbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6
ZT0yIGZhY2U9IkNhbGlicmkiPlRoYW5rcyw8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9
IkNhbGlicmkiPk1pbmd1aTwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0iQ2FsaWJyaSI+
Jm5ic3A7PC9mb250Pjx0dD48Zm9udCBzaXplPTI+X19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX188YnI+DQpwd2UzIG1haWxpbmcgbGlzdDxicj4NCnB3ZTNAaWV0
Zi5vcmc8YnI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3B3ZTM8YnI+
DQo8L2ZvbnQ+PC90dD4NCjxicj4NCg==
--=_alternative 001030D948257C2B_=--

From loa@pi.nu  Fri Nov 22 20:14:13 2013
Return-Path: <loa@pi.nu>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 332641AD986; Fri, 22 Nov 2013 20:14:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level: 
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WBme8SHfTKSJ; Fri, 22 Nov 2013 20:14:10 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6011AD8F2; Fri, 22 Nov 2013 20:14:10 -0800 (PST)
Received: from [192.168.1.12] (unknown [112.208.29.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id D2A621802038; Sat, 23 Nov 2013 05:14:00 +0100 (CET)
Message-ID: <52902B86.7040901@pi.nu>
Date: Sat, 23 Nov 2013 12:13:58 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>,  "pwe3@ietf.org" <pwe3@ietf.org>
References: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] Response to Liaison on Clarifying P2MP Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 23 Nov 2013 04:14:13 -0000

Mathew, working groups,

Good response! I'm OK with sending this!

Thanks for the all the work! One small question and one suggetion.

Ouestion:
Is this intended to be sent "For Information"?

Suggestuion:
Since this was sent in two identical liaisons to PWE# and MPLS can we
send it from the chairs of both working groups?

/Loa
mpls wg co-chair


On 2013-11-22 09:15, Bocci, Matthew (Matthew) wrote:
> PWE3 and MPLS Working Groups
>
> Please find below a draft response to the liaison from ITU-T SG15 of
> July 2013 on clarifying combinations of point to multipoint pseudowires
> and LSPs.
>
> Please direct any discussion to the PWE3 list.
>
> We would like to reply to the ITU by Wednesday 27th November.
>
> Regards
>
> Matthew and Andy
>
> ===============
>
> Body:
>
> Thank you for your liaison of July 2013 inquiring on the valid use of
> p2mp pseudowires and LSPs. A new version of the "Requirements and
> Framework for Point-to-Multipoint Pseudowires over MPLS PSNs" is
> available (see  draft-ietf-pwe3-p2mp-pw-requirements-06.txt) that should
> help to clarify some of the points in your liaison.
> In general, point-to-point PWs are not intended to be used in
> conjunction with P2MP LSPs.  There is currently no way for the PEs
> terminating all of the P2MP LSP leaves to establish the applicable
> PW/FEC label mappings.  We do not believe that this case is supported by
> the PWE3 architecture.  The only current valid case for P2MP PWs is when
> used with corresponding P2MP LSPs, as described in the draft referenced
> above.
>
> Best regards,
>
>
> Matthew Bocci
> Andrew Malis
>
> IETF PWE3 Working Group Chairs
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From agmalis@gmail.com  Sat Nov 23 06:14:47 2013
Return-Path: <agmalis@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 546FC1AE2F4; Sat, 23 Nov 2013 06:14:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N3C0gaZeDcAy; Sat, 23 Nov 2013 06:14:45 -0800 (PST)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id F33B11ADEB5; Sat, 23 Nov 2013 06:14:44 -0800 (PST)
Received: by mail-wi0-f173.google.com with SMTP id hm4so1889841wib.0 for <multiple recipients>; Sat, 23 Nov 2013 06:14:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OaM68BZbAW8ZvTRxUz6YkXHOD6kGhi8CY5ny7MWOjyw=; b=l6bxA8mXPa3iNZOH2cWaU2uF7Xj+aZdnDJ0gVkLSgbP0ubo9YVhpb5c+EBOSG8ASUU HKvSVkVVbLIe8vhWRHxfdvVjqtq9XRCWbVCdmxf8Xmp1Ym9fKjvquOrjoBFnRV17tJHp D77tkJofpYm3gFT33X1NajAt5c84hreAyNicDWQTEmEXH47vJESt/IdHJciM2XWMKIFP l47AaSgwnNeT/Cr/HogyENCazBoZR8i0jBUrZkWbAaCEBPysTTNGUJtmKny3djmoKlQ6 JokqVxZ/1vbv6jQc9DryNcLi58BnDZkVfijFmKDiUbd4DyyDWCvqueNd7TE60CfNo39v EfDQ==
X-Received: by 10.180.91.11 with SMTP id ca11mr6823833wib.39.1385216077082; Sat, 23 Nov 2013 06:14:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.127.68 with HTTP; Sat, 23 Nov 2013 06:14:17 -0800 (PST)
In-Reply-To: <52902B86.7040901@pi.nu>
References: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com> <52902B86.7040901@pi.nu>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sat, 23 Nov 2013 09:14:17 -0500
Message-ID: <CAA=duU0_94QqWK0o1PFoygKS8mThadLT+RBCur1Lm+iGczKvug@mail.gmail.com>
To: Loa Andersson <loa@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] Response to Liaison on Clarifying P2MP Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 23 Nov 2013 14:14:47 -0000

Loa,

Yes, this is meant for information, not for action, and it's a good
idea for it to come from both WGs in one response.

Cheers,
Andy

On Fri, Nov 22, 2013 at 11:13 PM, Loa Andersson <loa@pi.nu> wrote:
> Mathew, working groups,
>
> Good response! I'm OK with sending this!
>
> Thanks for the all the work! One small question and one suggetion.
>
> Ouestion:
> Is this intended to be sent "For Information"?
>
> Suggestuion:
> Since this was sent in two identical liaisons to PWE# and MPLS can we
> send it from the chairs of both working groups?
>
> /Loa
> mpls wg co-chair
>
>
>
> On 2013-11-22 09:15, Bocci, Matthew (Matthew) wrote:
>>
>> PWE3 and MPLS Working Groups
>>
>> Please find below a draft response to the liaison from ITU-T SG15 of
>> July 2013 on clarifying combinations of point to multipoint pseudowires
>> and LSPs.
>>
>> Please direct any discussion to the PWE3 list.
>>
>> We would like to reply to the ITU by Wednesday 27th November.
>>
>> Regards
>>
>> Matthew and Andy
>>
>> ===============
>>
>> Body:
>>
>> Thank you for your liaison of July 2013 inquiring on the valid use of
>> p2mp pseudowires and LSPs. A new version of the "Requirements and
>> Framework for Point-to-Multipoint Pseudowires over MPLS PSNs" is
>> available (see  draft-ietf-pwe3-p2mp-pw-requirements-06.txt) that should
>> help to clarify some of the points in your liaison.
>> In general, point-to-point PWs are not intended to be used in
>> conjunction with P2MP LSPs.  There is currently no way for the PEs
>> terminating all of the P2MP LSP leaves to establish the applicable
>> PW/FEC label mappings.  We do not believe that this case is supported by
>> the PWE3 architecture.  The only current valid case for P2MP PWs is when
>> used with corresponding P2MP LSPs, as described in the draft referenced
>> above.
>>
>> Best regards,
>>
>>
>> Matthew Bocci
>> Andrew Malis
>>
>> IETF PWE3 Working Group Chairs
>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>
> --
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

From huubatwork@gmail.com  Sat Nov 23 06:43:16 2013
Return-Path: <huubatwork@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4A371ADF10; Sat, 23 Nov 2013 06:43:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CvFCkhJAnleP; Sat, 23 Nov 2013 06:43:15 -0800 (PST)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB021AE0A3; Sat, 23 Nov 2013 06:43:14 -0800 (PST)
Received: by mail-wi0-f179.google.com with SMTP id ez12so3785890wid.0 for <multiple recipients>; Sat, 23 Nov 2013 06:43:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=TceBZQJM4EcekVi9YiPgJFTZ6Wm0b8HRlr5yw1mFj3s=; b=GF7s6aOQbtN2rqQ6ByWvvU8bgq5XADF+zr1COPlCjQQfQPx19II1MeHS3QMVMgZng8 mvL3XAoXDeGM7E0WDJHnr4fLiE1g9/+/GWKHEQLazSDUvcYsWQ/8b6sa/uTIGfAMk7kg pItyEMc67w3PKG9oQg67YMMCU4KYi/iHnZHYGBkDs35gq/Op9jcKTTZq2bxNGKvtC1Gu ZGhr4D28Ju6/fLBweiC3L4mx9B+HagPBUBy6Vzw8Av4lnKovsIXvny0yOKO8/cIK/CH0 mmIyTImtt2IL3PM9cisybncrss9AP2OJV/2wYzg3NXr17mg+EIiGUFcjBFbI3bGSv1UV fgkg==
X-Received: by 10.180.185.242 with SMTP id ff18mr6998649wic.44.1385217786724;  Sat, 23 Nov 2013 06:43:06 -0800 (PST)
Received: from McAsterix.local (g215085.upc-g.chello.nl. [80.57.215.85]) by mx.google.com with ESMTPSA id f15sm135747wik.6.2013.11.23.06.43.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 23 Nov 2013 06:43:06 -0800 (PST)
Message-ID: <5290BEFC.20308@gmail.com>
Date: Sat, 23 Nov 2013 15:43:08 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>,  "pwe3@ietf.org" <pwe3@ietf.org>
References: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] [mpls] Response to Liaison on Clarifying P2MP Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 23 Nov 2013 14:43:17 -0000

Hello Matthew,

You wrote:

 > PWE3 and MPLS Working Groups
>
> Please find below a draft response to the liaison from ITU-T SG15 of
> July 2013 on clarifying combinations of point to multipoint pseudowires
> and LSPs.

Please see in-line [hvh]
Best regards, Huub.

> ===============
> Body:
>
> Thank you for your liaison of July 2013 inquiring on the valid use of
> p2mp pseudowires and LSPs. A new version of the "Requirements and
> Framework for Point-to-Multipoint Pseudowires over MPLS PSNs" is
> available (see  draft-ietf-pwe3-p2mp-pw-requirements-06.txt) that should
> help to clarify some of the points in your liaison.

[hvh] you mention that some of the points are clarified, are the 
remaining points clarified by another liaison or by the text that
follows?

> In general, point-to-point PWs are not intended to be used in
> conjunction with P2MP LSPs.  There is currently no way for the PEs
> terminating all of the P2MP LSP leaves to establish the applicable
> PW/FEC label mappings.  We do not believe that this case is supported by
> the PWE3 architecture.  The only current valid case for P2MP PWs is when
> used with corresponding P2MP LSPs, as described in the draft referenced
> above.
>
> Best regards,
>
>
> Matthew Bocci
> Andrew Malis
>
> IETF PWE3 Working Group Chairs
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


-- 
*****************************************************************
               请记住，你是独一无二的，就像其他每一个人一样

From loa@pi.nu  Sun Nov 24 17:21:08 2013
Return-Path: <loa@pi.nu>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE7061AE35E; Sun, 24 Nov 2013 17:21:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level: 
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7KXIXAuxmE6U; Sun, 24 Nov 2013 17:21:07 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 22D991AE206; Sun, 24 Nov 2013 17:21:07 -0800 (PST)
Received: from [192.168.1.12] (unknown [112.208.29.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 1A02F18014F6; Mon, 25 Nov 2013 02:20:56 +0100 (CET)
Message-ID: <5292A5F7.3010609@pi.nu>
Date: Mon, 25 Nov 2013 09:20:55 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: huubatwork@gmail.com,  "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>, "pwe3@ietf.org" <pwe3@ietf.org>
References: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com> <5290BEFC.20308@gmail.com>
In-Reply-To: <5290BEFC.20308@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] [mpls] Response to Liaison on Clarifying P2MP Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 25 Nov 2013 01:21:09 -0000

Folks,

I think what should be done is to drop "some of" from the first
paragraph and in the second say "Additionally, point-to-point PWs are
not in general intended to ..."

/Loa

On 2013-11-23 22:43, Huub van Helvoort wrote:
> Hello Matthew,
>
> You wrote:
>
>  > PWE3 and MPLS Working Groups
>>
>> Please find below a draft response to the liaison from ITU-T SG15 of
>> July 2013 on clarifying combinations of point to multipoint pseudowires
>> and LSPs.
>
> Please see in-line [hvh]
> Best regards, Huub.
>
>> ===============
>> Body:
>>
>> Thank you for your liaison of July 2013 inquiring on the valid use of
>> p2mp pseudowires and LSPs. A new version of the "Requirements and
>> Framework for Point-to-Multipoint Pseudowires over MPLS PSNs" is
>> available (see  draft-ietf-pwe3-p2mp-pw-requirements-06.txt) that should
>> help to clarify some of the points in your liaison.
>
> [hvh] you mention that some of the points are clarified, are the
> remaining points clarified by another liaison or by the text that
> follows?
>
>> In general, point-to-point PWs are not intended to be used in
>> conjunction with P2MP LSPs.  There is currently no way for the PEs
>> terminating all of the P2MP LSP leaves to establish the applicable
>> PW/FEC label mappings.  We do not believe that this case is supported by
>> the PWE3 architecture.  The only current valid case for P2MP PWs is when
>> used with corresponding P2MP LSPs, as described in the draft referenced
>> above.
>>
>> Best regards,
>>
>>
>> Matthew Bocci
>> Andrew Malis
>>
>> IETF PWE3 Working Group Chairs
>>
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From zhangmingui@huawei.com  Sun Nov 24 18:33:59 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8851A1F1B; Sun, 24 Nov 2013 18:33:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.148
X-Spam-Level: 
X-Spam-Status: No, score=0.148 tagged_above=-999 required=5 tests=[MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MlBXtkbCrOpc; Sun, 24 Nov 2013 18:33:58 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 91B1B1A16F0; Sun, 24 Nov 2013 18:33:57 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAQ87423; Mon, 25 Nov 2013 02:33:57 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 25 Nov 2013 02:33:34 +0000
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 25 Nov 2013 02:33:56 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.180]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Mon, 25 Nov 2013 10:33:48 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, Fenghaisheng <fenghaisheng@huawei.com>
Thread-Topic: [PWE3] Feedback on "Any comments on the draft of STP Application of ICCP ?"
Thread-Index: Ac7mqFwbNyxm3E5XSoig0DW8/btf0AAQq+yAAKRskIA=
Date: Mon, 25 Nov 2013 02:33:47 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E733689299@nkgeml508-mbx.china.huawei.com>
References: <077FD3C0391C334DA3885E1D5729450846670BD3@nkgeml503-mbs.china.huawei.com> <201311221327.rAMDRAeT059109@mse01.zte.com.cn>
In-Reply-To: <201311221327.rAMDRAeT059109@mse01.zte.com.cn>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: pwe3 <pwe3-bounces@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Feedback on "Any comments on the draft of STP Application of ICCP ?"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 25 Nov 2013 02:33:59 -0000

SGkgSG9uZ2p1biwNCg0KVGhhbmtzIGZvciB0aGUgY29tbWVudC4NCg0KSW4gSUNDUCwgdGhpcyBr
aW5kIG9mIGNvZGUgcG9pbnRzIGFyZSBlbWJvZGllZCBhcyB0aGUgIiBJQ0NQIFN0YXR1cyBDb2Rl
IiBpbiB0aGUgIiBEaXNjb25uZWN0IENvZGUgVExWIiBpbiB0aGUgIlJHIERpc2Nvbm5lY3QgTWVz
c2FnZSAiLiBBbmQgdGhlICIgRGlzY29ubmVjdCBDYXVzZSBTdHJpbmcgIiBpcyBpbmNsdWRlZCBp
biB0aGUgIiBEaXNjb25uZWN0IENhdXNlIFRMViIgaW4gdGhlICIgRGlzY29ubmVjdCBUTFYgImlu
IHRoZSAiUkcgRGlzY29ubmVjdCBNZXNzYWdlICIuIEFzIGRlZmluZWQgaW4gdGhlIHByb3Bvc2Fs
LCB0aGUgRGlzY29ubmVjdCBDYXVzZSBTdHJpbmcgaXMgdXNlZCBmb3IgbmV0d29yayBtYW5hZ2Vt
ZW50LiBUaGUgc3RyaW5nIHZhbHVlIGlzIHN0cmFpZ2h0Zm9yd2FyZCB0byBiZSB1bmRlcnN0YW5k
IGJ5IHRoZSBvcGVyYXRvci4gDQoNClNvIHlvdXIgYWR2aWNlIGFuZCBvdXIgcHJvcG9zZWQgYXJl
IG5vdCBpbmNvbnNpc3RlbnQuDQoNCkJlc3QgUmVnYXJkcywNCk1pbmd1aQ0KDQo+LS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj5Gcm9tOiBwd2UzIFttYWlsdG86cHdlMy1ib3VuY2VzQGlldGYu
b3JnXSBPbiBCZWhhbGYgT2YNCj56aGFpLmhvbmdqdW5AenRlLmNvbS5jbg0KPlNlbnQ6IEZyaWRh
eSwgTm92ZW1iZXIgMjIsIDIwMTMgMTA6NTQgQU0NCj5UbzogRmVuZ2hhaXNoZW5nDQo+Q2M6IHB3
ZTM7IHB3ZTNAaWV0Zi5vcmcNCj5TdWJqZWN0OiBSZTogW1BXRTNdIEZlZWRiYWNrIG9uICJBbnkg
Y29tbWVudHMgb24gdGhlIGRyYWZ0IG9mIFNUUCBBcHBsaWNhdGlvbg0KPm9mIElDQ1AgPyINCj4N
Cj4NCj5IaSwNCj4NCj5JIHJldmlld2VkIHRoaXMgZHJhZnQsIGl0J3MgdXNlZnVsLiBJIGhhdmUg
YSBjb21tZW50Lg0KPg0KPkluIHRoZSAiU1RQIERpc2Nvbm5lY3QgQ2F1c2UgVExWIiwgd2h5IGEg
c3RyaW5nIGZpZWxkIHJhdGhlciB0aGFuIHdlbGwtZGVmaW5lZA0KPmludGVnZXIgY29kZXMgZmll
bGQgaXMgdXNlZCB0byBjYXJyeSB0aGUgZGlzY29ubmVjdCBjYXVzZT8gR2VybmVyYWxseSwgYW4g
aW50ZWdlcg0KPmNhbiByZWR1Y2UgdGhlIG5lY2Vzc2FyeSBiaXRzIGluIHBhY2tldCB0aGFuIGEg
c3RyaW5nLg0KPg0KPg0KPlRoYW5rcywNCj5Ib25nanVuIFpoYWkNCj4NCj4NCj4NCj4NCj5GZW5n
aGFpc2hlbmcgPGZlbmdoYWlzaGVuZ0BodWF3ZWkuY29tPg0KPreivP7IyzogICJwd2UzIiA8cHdl
My1ib3VuY2VzQGlldGYub3JnPg0KPg0KPjIwMTMtMTEtMjEgMTg6NTYgytW8/sjLDQo+InB3ZTNA
aWV0Zi5vcmciIDxwd2UzQGlldGYub3JnPg0KPrOty80NCj7W98ziDQo+W1BXRTNdIEZlZWRiYWNr
IG9uICJBbnkgY29tbWVudHMgb24gdGhlIGRyYWZ0IG9mIFNUUCBBcHBsaWNhdGlvbiBvZiBJQ0NQ
ID8iDQo+DQo+DQo+DQo+DQo+DQo+DQo+DQo+SSB0aGluayB0aGUgcHJvcG9zYWwgY2FuIGJlIHVz
ZWZ1bC4gV2hlbiBvbmUgY29ubmVjdGlvbiBmYWlscywgdGhlIG90aGVyDQo+Y29ubmVjdGlvbiBj
YW4gYmUgbGV2ZXJhZ2VkIGFmdGVyIGEgc3Bhbm5pbmcgdHJlZSByZWNhbGN1bGF0aW9uLiBUaGlz
IGtpbmQgb2YNCj5tdWx0aXBsZSBhdHRhY2htZW50cyBvZmZlcnMgY2VydGFpbiByZWxpYWJpbGl0
eS4NCj4NCj5UaGFua3MsDQo+SGFpc2hlbmcgRmVuZw0KPl9fX19fX19fXw0KPg0KPkhpIFRoZXJl
LA0KPg0KPkluIHRoZSBWYW5jb3V2ZXIgbWVldGluZywgd2UgcHJlc2VudGVkIHRoZSBmb2xsb3dp
bmcgZHJhZnQgU1RQIEFwcGxpY2F0aW9uIG9mDQo+SUNDUCwgaHR0cDovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtemhhbmctcHdlMy1pY2NwLXN0cC0wMA0KPjxodHRwOi8vdG9vbHMuaWV0Zi5v
cmcvaHRtbC9kcmFmdC16aGFuZy1wd2UzLWljY3Atc3RwLTAwPg0KPg0KPkF1dGhvcnMgd291bGQg
bGlrZSB0byBzZWUgbW9yZSBmZWVkYmFja3Mgb24gdGhpcyBkcmFmdC4gUGxlYXNlIGhlbHAgdG8g
cmV2aWV3IGl0DQo+YW5kIHNlbmQgeW91ciBjb21tZW50cyBvbiB0aGUgbWFpbGluZyBsaXN0LiBX
b3VsZCBiZSBoaWdobHkgYXBwcmVjaWF0ZWQhDQo+DQo+VGhhbmtzLA0KPk1pbmd1aQ0KPiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPnB3ZTMgbWFpbGlu
ZyBsaXN0DQo+cHdlM0BpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vcHdlMw0KPg0KDQo=

From matthew.bocci@alcatel-lucent.com  Mon Nov 25 04:44:34 2013
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5B21AD687; Mon, 25 Nov 2013 04:44:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8h4Vy-AycCj0; Mon, 25 Nov 2013 04:44:32 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id E01671AD959; Mon, 25 Nov 2013 04:44:31 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id rAPCiRKt008087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 25 Nov 2013 06:44:29 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rAPCiR5K006356 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Nov 2013 13:44:27 +0100
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.146]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 25 Nov 2013 13:44:27 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: Loa Andersson <loa@pi.nu>, "huubatwork@gmail.com" <huubatwork@gmail.com>,  "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] [mpls] Response to Liaison on Clarifying P2MP Combinations
Thread-Index: AQHO5yBViXeYAQSEMkaxB6wA8sJs35oy1aIAgAJEhoCAAL7ggA==
Date: Mon, 25 Nov 2013 12:44:26 +0000
Message-ID: <CEB8F662.58233%matthew.bocci@alcatel-lucent.com>
References: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com> <5290BEFC.20308@gmail.com> <5292A5F7.3010609@pi.nu>
In-Reply-To: <5292A5F7.3010609@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FF9C7792FE06384ABDBE9E7D9D03579C@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] [mpls] Response to Liaison on Clarifying P2MP Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 25 Nov 2013 12:44:34 -0000

Loa,=20

Yes, I agree with your suggested clarification.

Best regards

Matthew

On 25/11/2013 01:20, "Loa Andersson" <loa@pi.nu> wrote:

>Folks,
>
>I think what should be done is to drop "some of" from the first
>paragraph and in the second say "Additionally, point-to-point PWs are
>not in general intended to ..."
>
>/Loa
>
>On 2013-11-23 22:43, Huub van Helvoort wrote:
>> Hello Matthew,
>>
>> You wrote:
>>
>>  > PWE3 and MPLS Working Groups
>>>
>>> Please find below a draft response to the liaison from ITU-T SG15 of
>>> July 2013 on clarifying combinations of point to multipoint pseudowires
>>> and LSPs.
>>
>> Please see in-line [hvh]
>> Best regards, Huub.
>>
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> Body:
>>>
>>> Thank you for your liaison of July 2013 inquiring on the valid use of
>>> p2mp pseudowires and LSPs. A new version of the "Requirements and
>>> Framework for Point-to-Multipoint Pseudowires over MPLS PSNs" is
>>> available (see  draft-ietf-pwe3-p2mp-pw-requirements-06.txt) that
>>>should
>>> help to clarify some of the points in your liaison.
>>
>> [hvh] you mention that some of the points are clarified, are the
>> remaining points clarified by another liaison or by the text that
>> follows?
>>
>>> In general, point-to-point PWs are not intended to be used in
>>> conjunction with P2MP LSPs.  There is currently no way for the PEs
>>> terminating all of the P2MP LSP leaves to establish the applicable
>>> PW/FEC label mappings.  We do not believe that this case is supported
>>>by
>>> the PWE3 architecture.  The only current valid case for P2MP PWs is
>>>when
>>> used with corresponding P2MP LSPs, as described in the draft referenced
>>> above.
>>>
>>> Best regards,
>>>
>>>
>>> Matthew Bocci
>>> Andrew Malis
>>>
>>> IETF PWE3 Working Group Chairs
>>>
>>>
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>>
>>
>
>--=20
>
>
>Loa Andersson                        email: loa@mail01.huawei.com
>Senior MPLS Expert                          loa@pi.nu
>Huawei Technologies (consultant)     phone: +46 739 81 21 64


From eric.gray@ericsson.com  Mon Nov 25 06:14:58 2013
Return-Path: <eric.gray@ericsson.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDD31ADBE5; Mon, 25 Nov 2013 06:14:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJkfDLh7fVej; Mon, 25 Nov 2013 06:14:56 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF801AD957; Mon, 25 Nov 2013 06:14:56 -0800 (PST)
X-AuditID: c6180641-b7fbd8e0000011cc-43-52935b5e4e99
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 4A.13.04556.E5B53925; Mon, 25 Nov 2013 15:14:55 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0328.009; Mon, 25 Nov 2013 09:14:54 -0500
From: Eric Gray <eric.gray@ericsson.com>
To: Loa Andersson <loa@pi.nu>, "huubatwork@gmail.com" <huubatwork@gmail.com>,  "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [mpls] [PWE3] Response to Liaison on Clarifying P2MP Combinations
Thread-Index: AQHO6Xyexx76EhHG0UaIpalLNAEwWZo1+VIw
Date: Mon, 25 Nov 2013 14:14:53 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF6329A3272@eusaamb107.ericsson.se>
References: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com> <5290BEFC.20308@gmail.com> <5292A5F7.3010609@pi.nu>
In-Reply-To: <5292A5F7.3010609@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyuXRPlG589OQggxtLRS1mzL7MavFv7hxm i8Nddxktbi1dyWrR92kLiwOrR+uzvaweO2fdZfdYsuQnk8es6W1sASxRXDYpqTmZZalF+nYJ XBlrFr9nLvgnU7FixWuWBsZXYl2MnBwSAiYSp2asZYewxSQu3FvPBmILCRxhlLh8UqGLkQvI Xs4ocedEJwtIgk1AQ+LYnbWMILaIwAZGiWU7NLsYOTiYBZQlTt2VAQkLCwRInNv+DKokUGLC yWdsELaRxJaX18F2sQioSjw9eJcJpJVXwFeid1YWxNpiiVtPf7KC2JxAJQdurAArZwQ67fup NUwgNrOAuMStJ/OZIE4WkFiy5zwzhC0q8fLxP1YIW1liyZP9LBD1OhILdn9ig7C1JZYtfA1W zysgKHFy5hOWCYxis5CMnYWkZRaSlllIWhYwsqxi5CgtTi3LTTcy3MQIjKljEmyOOxgXfLI8 xCjNwaIkzvvlrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsZom1n5F4UFT2SsiU11Y7m/ zt3W577wvu4tnc2uYvtkODZkr8ib3+qqX/x86ZTXa/1DvvJa8tUbfGgM/m+YteTr4l3BmUtK blZtkX653dw66XfkO9Fyi9k6b381GRRHsD5MCT8y68S6LZP2/VgU/inW4dfGTzLewX42YUFT WxsfL7a/c/T1y3VKLMUZiYZazEXFiQDVB2UCdwIAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] [mpls] Response to Liaison on Clarifying P2MP	Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 25 Nov 2013 14:14:58 -0000

In addition, should the last sentence in the proposed liaison letter text b=
e changed
from:

  "The only current valid case for P2MP PWs is when used with corresponding=
 P2MP=20
    LSPs, as described in the draft referenced above"

to:

  "The only current valid case for PW use in a point-to-multipoint scenario=
 is when=20
    a P2MP PW is used with a corresponding P2MP LSP, as described in the dr=
aft=20
    referenced above"?

I believe we are trying to say two things:

1) use of multiple P2P PWs in conjunction with a single P2MP LSP is (genera=
lly?)=20
     not valid;
2) use of a P2MP PW in conjunction with one or more P2P LSPs is definitely =
not=20
     valid.

We make the point (in the second paragraph) that there is (currently?) an i=
ssue
(potentially pathological?) associated with use of P2P PWs with a P2MP.  I =
would
think we want to discourage this usage.

The current text makes the second point, more than it makes the first.  As =
it is
currently worded, this text implies that use of multiple P2P PWs _might_ be=
 a
valid use case, even though this seems to differ slightly from what I think=
 we're
trying to say in the second paragraph...

--
Eric

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: Sunday, November 24, 2013 8:21 PM
To: huubatwork@gmail.com; Bocci, Matthew (Matthew); pwe3@ietf.org
Cc: mpls@ietf.org
Subject: Re: [mpls] [PWE3] Response to Liaison on Clarifying P2MP Combinati=
ons

Folks,

I think what should be done is to drop "some of" from the first paragraph a=
nd in the second say "Additionally, point-to-point PWs are not in general i=
ntended to ..."

/Loa

On 2013-11-23 22:43, Huub van Helvoort wrote:
> Hello Matthew,
>
> You wrote:
>
>  > PWE3 and MPLS Working Groups
>>
>> Please find below a draft response to the liaison from ITU-T SG15 of=20
>> July 2013 on clarifying combinations of point to multipoint=20
>> pseudowires and LSPs.
>
> Please see in-line [hvh]
> Best regards, Huub.
>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Body:
>>
>> Thank you for your liaison of July 2013 inquiring on the valid use of=20
>> p2mp pseudowires and LSPs. A new version of the "Requirements and=20
>> Framework for Point-to-Multipoint Pseudowires over MPLS PSNs" is=20
>> available (see  draft-ietf-pwe3-p2mp-pw-requirements-06.txt) that=20
>> should help to clarify some of the points in your liaison.
>
> [hvh] you mention that some of the points are clarified, are the=20
> remaining points clarified by another liaison or by the text that=20
> follows?
>
>> In general, point-to-point PWs are not intended to be used in=20
>> conjunction with P2MP LSPs.  There is currently no way for the PEs=20
>> terminating all of the P2MP LSP leaves to establish the applicable=20
>> PW/FEC label mappings.  We do not believe that this case is supported=20
>> by the PWE3 architecture.  The only current valid case for P2MP PWs=20
>> is when used with corresponding P2MP LSPs, as described in the draft=20
>> referenced above.
>>
>> Best regards,
>>
>>
>> Matthew Bocci
>> Andrew Malis
>>
>> IETF PWE3 Working Group Chairs
>>
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
>

--=20


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From loa@pi.nu  Mon Nov 25 20:16:52 2013
Return-Path: <loa@pi.nu>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D12161AE10F; Mon, 25 Nov 2013 20:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bjrxnXaG_9RW; Mon, 25 Nov 2013 20:16:50 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6C1B51ADFC6; Mon, 25 Nov 2013 20:16:50 -0800 (PST)
Received: from [192.168.1.12] (unknown [112.208.29.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id A3C2C1802038; Tue, 26 Nov 2013 05:16:47 +0100 (CET)
Message-ID: <529420AD.5080405@pi.nu>
Date: Tue, 26 Nov 2013 12:16:45 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Eric Gray <eric.gray@ericsson.com>,  "huubatwork@gmail.com" <huubatwork@gmail.com>, "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>,  "pwe3@ietf.org" <pwe3@ietf.org>
References: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com> <5290BEFC.20308@gmail.com> <5292A5F7.3010609@pi.nu> <48E1A67CB9CA044EADFEAB87D814BFF6329A3272@eusaamb107.ericsson.se>
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF6329A3272@eusaamb107.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] [mpls] Response to Liaison on Clarifying P2MP Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 26 Nov 2013 04:16:53 -0000

<snip>
> 2) use of a P2MP PW in conjunction with one or more P2P LSPs is definitely not
>       valid.
>
snip>

Well a MS-PW could do P2MP over P2P LSPs, right?

/Loa

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From eric.gray@ericsson.com  Tue Nov 26 06:45:34 2013
Return-Path: <eric.gray@ericsson.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E06D1AE221; Tue, 26 Nov 2013 06:45:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gX-xydjY6VDO; Tue, 26 Nov 2013 06:45:32 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 892AC1AD8F5; Tue, 26 Nov 2013 06:45:32 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-81-5294b4084262
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id A1.74.23183.804B4925; Tue, 26 Nov 2013 15:45:29 +0100 (CET)
Received: from EUSAAMB104.ericsson.se ([147.117.188.121]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0328.009; Tue, 26 Nov 2013 09:45:29 -0500
From: Eric Gray <eric.gray@ericsson.com>
To: Loa Andersson <loa@pi.nu>, "huubatwork@gmail.com" <huubatwork@gmail.com>,  "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [mpls] [PWE3] Response to Liaison on Clarifying P2MP Combinations
Thread-Index: AQHO6l5VFd3RTdWJ902+UNphv84vuZo3kP7g
Date: Tue, 26 Nov 2013 14:45:28 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF6329A8587@eusaamb104.ericsson.se>
References: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com> <5290BEFC.20308@gmail.com> <5292A5F7.3010609@pi.nu> <48E1A67CB9CA044EADFEAB87D814BFF6329A3272@eusaamb107.ericsson.se> <529420AD.5080405@pi.nu>
In-Reply-To: <529420AD.5080405@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyuXRPuC7nlilBBkuuC1rMmH2Z1eLf3DnM Foe77jJa3Fq6ktWi79MWFgdWj9Zne1k9ds66y+6xZMlPJo9Z09vYAliiuGxSUnMyy1KL9O0S uDIuH5Ao+CxYseqyUQPjBd4uRk4OCQETif7DX5ggbDGJC/fWs3UxcnEICRxhlFjV2ckO4Sxn lOh8f4QdpIpNQEPi2J21jCC2iMAGRollOzS7GDk4mAWUJU7dlQEJCwsESGxvX8sKURIo8e/h fRYI20ji4fXzYMtYBFQlfrYdABvDK+ArMf36TajFlxglPp65DFbECVR0+818sCJGoOu+n1oD FmcWEJe49WQ+1NUCEkv2nGeGsEUlXj7+xwphK0ssebKfBaJeR2LB7k9sELa2xLKFr5khFgtK nJz5hGUCo9gsJGNnIWmZhaRlFpKWBYwsqxg5SotTy3LTjQw2MQKj6pgEm+4Oxj0vLQ8xSnOw KInzfnnrHCQkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBUc806YkF+56uMD2u76yO3Nfmsu/e H+c3Z/oV08kV+xbcv3tFsCHZ5/DN61NfvE/Vt7L+5V6s+/v8CT5B87yH83J2LlgadXIZo/ez wwtE1JPVFhyLUbPRM3185IV0OY/iKdk3ggqXu0zOT/z7UNfe443Q62cnY9+9+nD01AuhV0I9 LI/+Gf1SOajEUpyRaKjFXFScCABAc7ZpeAIAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] [mpls] Response to Liaison on Clarifying P2MP Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 26 Nov 2013 14:45:34 -0000

Loa,

	I think you mean on a per-segment basis, where a group of PW-branches
would traverse the segment using the same segment-ingress/egress pair, righ=
t?

	If so, this is not logically different from having the same set of PW-bran=
ches
traversing a common link.  I guess it is possible that a P2MP MS-PW would o=
nly use=20
P2P LSPs in every segment; that would require every branching point to be a=
t the
points where the P2P LSP in one domain terminates and two or more P2P LSPs =
are
used to forward distinct subsets of the P2MP PW through the next domain.  T=
his
seems likely (to me, anyway) only if the LSR at the domain boundary belongs=
 to
both domains (not the common case, I believe). =20

	If there was no branching at domain boundaries, and no P2MP LSPs in any=20
domain, it beggars the imagination as to why a P2MP PW would be used in the=
 first=20
place, so the overall set of LSPs would effectively be P2MP - wouldn't they=
?

	But, if you think transport of a P2MP PW over a set of P2P LSPs exclusivel=
y=20
is a valid scenario to consider, why include the text in question at all?

	Since you snipped it, I am adding back the text in question.  It says:

  " The only current valid case for P2MP PWs is when used with correspondin=
g P2MP=20
    LSPs, as described in the draft referenced above."

	The primary message in this text is that carrying a P2MP PW over anything=
=20
other than a P2MP LSP is invalid.  If that is not the clarification we want=
 to provide,
then we need to change this text, or remove it.

--
Eric

-----Original Message-----
From: Loa Andersson [mailto:loa@pi.nu]=20
Sent: Monday, November 25, 2013 11:17 PM
To: Eric Gray; huubatwork@gmail.com; Bocci, Matthew (Matthew); pwe3@ietf.or=
g
Cc: mpls@ietf.org
Subject: Re: [mpls] [PWE3] Response to Liaison on Clarifying P2MP Combinati=
ons
Importance: High



<snip>
> 2) use of a P2MP PW in conjunction with one or more P2P LSPs is definitel=
y not
>       valid.
>
snip>

Well a MS-PW could do P2MP over P2P LSPs, right?

/Loa

--=20


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From matthew.bocci@alcatel-lucent.com  Tue Nov 26 07:56:18 2013
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E6FE1AD8DA; Tue, 26 Nov 2013 07:56:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1slG6FHoaC1h; Tue, 26 Nov 2013 07:56:16 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 310691AC85E; Tue, 26 Nov 2013 07:56:16 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rAQFu91W009260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 26 Nov 2013 09:56:11 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rAQFu9xF022774 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 Nov 2013 16:56:09 +0100
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.146]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Tue, 26 Nov 2013 16:56:08 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: Eric Gray <eric.gray@ericsson.com>, Loa Andersson <loa@pi.nu>, "huubatwork@gmail.com" <huubatwork@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [mpls] [PWE3] Response to Liaison on Clarifying P2MP Combinations
Thread-Index: AQHO6l5XcbLTsfzeX02Vye95ekPlR5o3hssAgAATvAA=
Date: Tue, 26 Nov 2013 15:56:08 +0000
Message-ID: <CEBA7291.58351%matthew.bocci@alcatel-lucent.com>
References: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com> <5290BEFC.20308@gmail.com> <5292A5F7.3010609@pi.nu> <48E1A67CB9CA044EADFEAB87D814BFF6329A3272@eusaamb107.ericsson.se> <529420AD.5080405@pi.nu> <48E1A67CB9CA044EADFEAB87D814BFF6329A8587@eusaamb104.ericsson.se>
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF6329A8587@eusaamb104.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <CDC39A8ECF16C74893E324818E1D105B@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] [mpls] Response to Liaison on Clarifying P2MP Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 26 Nov 2013 15:56:18 -0000

Eric

Theoretically it is possible, but the key is in the word =8Ccurrent=B9. The
P2MP requirements/framework was deliberately scoped down after AD review,
from the problem of any P2MP PW over any underlying LSP type. Trying to
define all possible combinations in a single document (when we hadn=B9t eve=
n
characterised the simplest case) was going far beyond the basic
requirements from VPMS.

Maybe we should rephrase the sentence below as follows:

" The only use case for P2MP PWs described in the draft referenced above
is when used with corresponding P2MP
    LSPs. Other more complex use cases are for further study. If required,
participants are encouraged to bring extensions to this architecture to
the PWE3 working group."


Matthew


On 26/11/2013 14:45, "Eric Gray" <eric.gray@ericsson.com> wrote:

>Loa,
>
>	I think you mean on a per-segment basis, where a group of PW-branches
>would traverse the segment using the same segment-ingress/egress pair,
>right?
>
>	If so, this is not logically different from having the same set of
>PW-branches
>traversing a common link.  I guess it is possible that a P2MP MS-PW would
>only use=20
>P2P LSPs in every segment; that would require every branching point to be
>at the
>points where the P2P LSP in one domain terminates and two or more P2P
>LSPs are
>used to forward distinct subsets of the P2MP PW through the next domain.
>This
>seems likely (to me, anyway) only if the LSR at the domain boundary
>belongs to
>both domains (not the common case, I believe).
>
>	If there was no branching at domain boundaries, and no P2MP LSPs in any
>domain, it beggars the imagination as to why a P2MP PW would be used in
>the first=20
>place, so the overall set of LSPs would effectively be P2MP - wouldn't
>they?
>
>	But, if you think transport of a P2MP PW over a set of P2P LSPs
>exclusively=20
>is a valid scenario to consider, why include the text in question at all?
>
>	Since you snipped it, I am adding back the text in question.  It says:
>
>  " The only current valid case for P2MP PWs is when used with
>corresponding P2MP
>    LSPs, as described in the draft referenced above."
>
>	The primary message in this text is that carrying a P2MP PW over
>anything=20
>other than a P2MP LSP is invalid.  If that is not the clarification we
>want to provide,
>then we need to change this text, or remove it.
>
>--
>Eric
>
>-----Original Message-----
>From: Loa Andersson [mailto:loa@pi.nu]
>Sent: Monday, November 25, 2013 11:17 PM
>To: Eric Gray; huubatwork@gmail.com; Bocci, Matthew (Matthew);
>pwe3@ietf.org
>Cc: mpls@ietf.org
>Subject: Re: [mpls] [PWE3] Response to Liaison on Clarifying P2MP
>Combinations
>Importance: High
>
>
>
><snip>
>> 2) use of a P2MP PW in conjunction with one or more P2P LSPs is
>>definitely not
>>       valid.
>>
>snip>
>
>Well a MS-PW could do P2MP over P2P LSPs, right?
>
>/Loa
>
>--=20
>
>
>Loa Andersson                        email: loa@mail01.huawei.com
>Senior MPLS Expert                          loa@pi.nu
>Huawei Technologies (consultant)     phone: +46 739 81 21 64


From eric.gray@ericsson.com  Tue Nov 26 07:59:07 2013
Return-Path: <eric.gray@ericsson.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3991AD8F2; Tue, 26 Nov 2013 07:59:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNCieAsslrrK; Tue, 26 Nov 2013 07:59:05 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 338611AC85E; Tue, 26 Nov 2013 07:59:05 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-e7-5294c5462169
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 75.E8.23183.645C4925; Tue, 26 Nov 2013 16:59:02 +0100 (CET)
Received: from EUSAAMB104.ericsson.se ([147.117.188.121]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0328.009; Tue, 26 Nov 2013 10:59:01 -0500
From: Eric Gray <eric.gray@ericsson.com>
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>, "Loa Andersson" <loa@pi.nu>, "huubatwork@gmail.com" <huubatwork@gmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [mpls] [PWE3] Response to Liaison on Clarifying P2MP Combinations
Thread-Index: AQHO6l5VFd3RTdWJ902+UNphv84vuZo3kP7ggABuIQD//6x2QA==
Date: Tue, 26 Nov 2013 15:59:01 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF6329A970C@eusaamb104.ericsson.se>
References: <CEB45EA6.580D2%matthew.bocci@alcatel-lucent.com> <5290BEFC.20308@gmail.com> <5292A5F7.3010609@pi.nu> <48E1A67CB9CA044EADFEAB87D814BFF6329A3272@eusaamb107.ericsson.se> <529420AD.5080405@pi.nu> <48E1A67CB9CA044EADFEAB87D814BFF6329A8587@eusaamb104.ericsson.se> <CEBA7291.58351%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <CEBA7291.58351%matthew.bocci@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOLMWRmVeSWpSXmKPExsUyuXSPt67b0SlBBusvGFnMmH2Z1eLf3DnM Foe77jJa3Fq6ktWi79MWFgdWj9Zne1k9ds66y+6xZMlPJo9Z09vYAliiuGxSUnMyy1KL9O0S uDLmbX3EVDBXpuL82QfsDYyzxLoYOTkkBEwk2g9eYIKwxSQu3FvP1sXIxSEkcIRR4tuLflYI ZzmjRMuv76wgVWwCGhLH7qxlBEmICGxilNj45x9QOwcHs4CyxKm7MiA1wgIBEtvb14LViwgE Svx7eJ8FpEREwEni9xYvkDCLgKrErW+L2UFsXgFfiTt7d0MtPsUksaTnAliCU8BO4srf2Ywg NiPQdd9PrQG7lFlAXOLWk/lQVwtILNlznhnCFpV4+fgfK4StLLHkyX4WiHoDiS/vb0PZ2hLL Fr5mhlgsKHFy5hOWCYxis5CMnYWkZRaSlllIWhYwsqxi5CgtTi3LTTcy2MQIjKxjEmy6Oxj3 vLQ8xCjNwaIkzvvlrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsYYNkZNbelEDq6GrjA5 rsPP70nG2GqXpM9qqv3wIqnRYMarfQtnnwg+cnLFLg4hh1nKWQViE9iLJ786ocJT2HxrgaRY +uRWsawFTXttOZ+3NW2cdXmeS1pulRxDz52o7tasg3ve24RtzYqQ3fmaj+lmUJNgyy/BQ593 Tsv1SL0vur/qe6Z/phJLcUaioRZzUXEiAIurtbt6AgAA
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] [mpls] Response to Liaison on Clarifying P2MP Combinations
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 26 Nov 2013 15:59:07 -0000

Matthew,

	Your wording is acceptable to me.  It certainly makes the clarification cl=
earer.

:-)
--
Eric

-----Original Message-----
From: Bocci, Matthew (Matthew) [mailto:matthew.bocci@alcatel-lucent.com]=20
Sent: Tuesday, November 26, 2013 10:56 AM
To: Eric Gray; Loa Andersson; huubatwork@gmail.com; pwe3@ietf.org
Cc: mpls@ietf.org
Subject: Re: [mpls] [PWE3] Response to Liaison on Clarifying P2MP Combinati=
ons
Importance: High

Eric

Theoretically it is possible, but the key is in the word =8Ccurrent=B9. The
P2MP requirements/framework was deliberately scoped down after AD review,
from the problem of any P2MP PW over any underlying LSP type. Trying to
define all possible combinations in a single document (when we hadn=B9t eve=
n
characterised the simplest case) was going far beyond the basic
requirements from VPMS.

Maybe we should rephrase the sentence below as follows:

" The only use case for P2MP PWs described in the draft referenced above
is when used with corresponding P2MP
    LSPs. Other more complex use cases are for further study. If required,
participants are encouraged to bring extensions to this architecture to
the PWE3 working group."


Matthew


On 26/11/2013 14:45, "Eric Gray" <eric.gray@ericsson.com> wrote:

>Loa,
>
>	I think you mean on a per-segment basis, where a group of PW-branches
>would traverse the segment using the same segment-ingress/egress pair,
>right?
>
>	If so, this is not logically different from having the same set of
>PW-branches
>traversing a common link.  I guess it is possible that a P2MP MS-PW would
>only use=20
>P2P LSPs in every segment; that would require every branching point to be
>at the
>points where the P2P LSP in one domain terminates and two or more P2P
>LSPs are
>used to forward distinct subsets of the P2MP PW through the next domain.
>This
>seems likely (to me, anyway) only if the LSR at the domain boundary
>belongs to
>both domains (not the common case, I believe).
>
>	If there was no branching at domain boundaries, and no P2MP LSPs in any
>domain, it beggars the imagination as to why a P2MP PW would be used in
>the first=20
>place, so the overall set of LSPs would effectively be P2MP - wouldn't
>they?
>
>	But, if you think transport of a P2MP PW over a set of P2P LSPs
>exclusively=20
>is a valid scenario to consider, why include the text in question at all?
>
>	Since you snipped it, I am adding back the text in question.  It says:
>
>  " The only current valid case for P2MP PWs is when used with
>corresponding P2MP
>    LSPs, as described in the draft referenced above."
>
>	The primary message in this text is that carrying a P2MP PW over
>anything=20
>other than a P2MP LSP is invalid.  If that is not the clarification we
>want to provide,
>then we need to change this text, or remove it.
>
>--
>Eric
>
>-----Original Message-----
>From: Loa Andersson [mailto:loa@pi.nu]
>Sent: Monday, November 25, 2013 11:17 PM
>To: Eric Gray; huubatwork@gmail.com; Bocci, Matthew (Matthew);
>pwe3@ietf.org
>Cc: mpls@ietf.org
>Subject: Re: [mpls] [PWE3] Response to Liaison on Clarifying P2MP
>Combinations
>Importance: High
>
>
>
><snip>
>> 2) use of a P2MP PW in conjunction with one or more P2P LSPs is
>>definitely not
>>       valid.
>>
>snip>
>
>Well a MS-PW could do P2MP over P2P LSPs, right?
>
>/Loa
>
>--=20
>
>
>Loa Andersson                        email: loa@mail01.huawei.com
>Senior MPLS Expert                          loa@pi.nu
>Huawei Technologies (consultant)     phone: +46 739 81 21 64


From Alexander.Vainshtein@ecitele.com  Tue Nov 26 08:26:51 2013
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9281F1ACC91; Tue, 26 Nov 2013 08:26:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJlCjE3Yw83G; Tue, 26 Nov 2013 08:26:48 -0800 (PST)
Received: from ilptbmg01-out.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by ietfa.amsl.com (Postfix) with ESMTP id 15E821AC85E; Tue, 26 Nov 2013 08:26:46 -0800 (PST)
X-AuditID: 93eaf2e7-b7f908e000003da1-57-5294da5ac419
Received: from ILPTWPVEXCA01.ecitele.com ( [172.31.244.224]) by ilptbmg01-out.ecitele.com (Symantec Messaging Gateway) with SMTP id 08.E7.15777.A5AD4925; Tue, 26 Nov 2013 19:28:58 +0200 (IST)
Received: from ILPTWPVEXMB02.ecitele.com ([fe80::5979:ca8d:419f:56df]) by ILPTWPVEXCA01.ecitele.com ([fe80::ac15:43ab:d541:dfa7%12]) with mapi id 14.03.0123.003; Tue, 26 Nov 2013 18:26:44 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Thread-Topic: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
Thread-Index: AQHO6gxo3oQggiALO0KcL/+gtz2uy5o3rlNQ
Date: Tue, 26 Nov 2013 16:26:43 +0000
Message-ID: <F9336571731ADE42A5397FC831CEAA025AC56C9D@ILPTWPVEXMB02.ecitele.com>
References: Your message of "Wed, 20 Nov 2013 14:35:41 GMT." <F9336571731ADE42A5397FC831CEAA025392F92F@ILPTWPVEXMB01.ecitele.com> <201311251829.rAPIThSu096500@gateway1.ipv6.occnc.com>
In-Reply-To: <201311251829.rAPIThSu096500@gateway1.ipv6.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.4.35.10]
Content-Type: text/plain; charset="us-ascii"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrILsWRmVeSWpSXmKPExsUy+dWnL7pRt6YEGcw+KW1x+vkpNotP73aw WEyedYbN4vCB6ewWP3ZsYre4tXQlq0Xfpy0sFsfff2Cz+ND1g9WB02PryR9sHlN+b2T12Dnr LrvHkiU/mTyW3b/I5nG96Sq7x+Ivfh6T1qYFcEQ1MNok5uXllySWpCqkpBYn2yoFFGWWJSZX KilkptgqGSopFOQkJqfmpuaV2ColFhSk5qUo2XEpYAAboLLMPIXUvOT8lMy8dFslz2B/XQsL U0tdQyU7NWVDY2uukIzMYoVU3dzEzByF3NTi4sT0VAWgSMIW5ozdx4QL9lpUvPgxg6WB8adO FyMnh4SAicTNua8YIWwxiQv31rN1MXJxCAkcZJQ4sucGlHOUUWLh6VVsIFVsArYSm1bfBbNF BIwl/rbdBStiFrjDJDHv1D0gh4NDWCBeYt12DoiaBImdByewQNhGEjefzmMFsVkEVCWWdM4E s3kFAiSOXmljhFh2nFHi9uNHYA2cAk4S866eAjuPEei876fWMIHYzALiEreezGeCOFtAYsme 88wQtqjEy8f/WCFsOYknT06xQNTrSCzY/YkNwtaWWLbwNTPEYkGJkzOfsEDUS0ocXHGDZQKj +CwkK2YhaZ+FpH0WkvYFjCyrGEUzcwpKknLTDQz1UpMzS1JzUvWS83M3MULS2PMdjL/mqxxi FOBgVOLhNZw3OUiINbGsuDL3EKMkB5OSKO+L41OChPiS8lMqMxKLM+KLSnNSiw8xSnAwK4nw bjwBlONNSaysSi3Kh0m5AoNwIrMUd3I+MDXnlcQbGxjg5iiJ885pBhoikA5MgtmpqQWpRTBz ZDg4lCR4z5wCygoWpaanVqRl5pQgpJk4OEHO4AE64xxIDW9xQWJucWY6RP4Uoy7HrZ+fvjEK seTl56VKifNeASkSACnKKM2DmwPLaa8YxYEBIMx7A6SKB5gP4Sa9AlrCBLSky2gyyBJgVoFL STUwHlh7jGWVnm1bxSTBUyfDRa8W8DW6v4vmCcyQCVzvvVA8Ie87c2H1lrplvKk2SWYzOydq imm331njGcTPfOHpW8+M2kSZKyJhFez51hK9npfS1C4YXpZtt01+qzGd73ar/NNJiusqInQD Jn9fJPJvW89t06UmL6pfmf5Sf1FQfcJ6r0n0bUUlluKMREMt5qLiRAARe5RiRAQAAA==
Cc: "samante@apple.com" <samante@apple.com>, "Yaakov Stein \(yaakov_s@rad.com\)" <yaakov_s@rad.com>, "cpignata@cisco.com" <cpignata@cisco.com>, "kireeti@juniper.net" <kireeti@juniper.net>, "mpls@ietf.org" <mpls@ietf.org>, "curtis@occnc.com" <curtis@occnc.com>, "pwe3 \(pwe3@ietf.org\)" <pwe3@ietf.org>
Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-forwarding: a minor comment
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 26 Nov 2013 16:26:51 -0000

Curtis,
Lots of thanks for a prompt and very detailed response.
May I suggest an alternative version of the following text fragment?

<Curtis>
>   Identifying the position of any lost packets is important
>    for PW services which are attempting to reconstruct a bit stream
>    which maintains bit timing, such as time division multiplexing (TDM)
>    services.  TDM and other PW services which require strict ordering
>    also require that misordered packets be either dropped or reordered. 
 <Sasha>
Identifying lost PW packets and exact amount of lost payload is critical for=
 PW services
which maintain bit timing, such as Time Division Multiplexing (TDM) services=
 since
these services MUST compensate lost payload on a bit-for-bit basis. 

With these services PW packets that have been received out of order also MUS=
T also be identified and may be either re-ordered or dropped. 
Reordering requires, in addition to sequence numbering, a "de-jitter buffer"=
 in the egress PE, and ability to reorder is limited by the depth of this bu=
ffer. The down side of maintaining a de-jitter buffer is 
added end-to-end service delay.
</Sasha>

Hopefully this will be useful.


Regards,
     Sasha

> -----Original Message-----
> From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]
> Sent: Monday, November 25, 2013 8:30 PM
> To: Alexander Vainshtein
> Cc: curtis@occnc.com; kireeti@juniper.net; samante@apple.com;
> agmalis@gmail.com; cpignata@cisco.com; mpls@ietf.org; Yaakov Stein
> (yaakov_s@rad.com); pwe3 (pwe3@ietf.org)
> Subject: Re: [PWE3] Pseudowire Sequence Number in draft-ietf-mpls-
> forwarding: a minor comment
> 
> 
> In message
> <F9336571731ADE42A5397FC831CEAA025392F92F@ILPTWPVEXMB01.ecitele.c
> om>
> Alexander Vainshtein writes:
> >
> > Hi all,
> >
> > I would like to comment on the text in Section 2.1.8.1 "Pseudowire
> > Sequence Number" in draft-ietf-mpls-forwarding-03 - MPLS Forwarding
> > Compliance and Performance Requirements
> > <http://tools.ietf.org/html/draft-ietf-mpls-forwarding-03>.
> >
> > This section states, in short, that the main drive for using the
> > sequence number in the PW Control Word is handling of packet
> > reordering events. TDM PWs are presented as a major example, with CBR
> > ATM services as another example.
> >
> > In fact, this statement is not accurate.
> 
> Yes.  You are correct in pointing this out as inaccurate by omitting
> the other important function of identifying drops for the purpose of
> recunstructing TDM bit streams.
> 
> Andy brought up resequencing being a strong provider request.
> Reordering is far more common than loss particularly for high priority
> services on provider networks and without resequencing reorder results
> in PW loss in what could otherwise be lossless service.
> 
> So we should get the base requirements right but still reflect this,
> but strictly as advice with no normative wording.  We had used the
> phrase "is beneficial" and will retain that.
> 
> Andy brought up the topic.  The incorrect wording in the existing
> draft is my fault.  This text went in fairly early with a lot of other
> changes and it appears that no one had since given it a careful enough
> read and review until you came along.
> 
> > The main drive for mandating the use of sequence number in TM PWs is
> > the need to detect and count lost packets because the egress PE MUST
> > compensate the lost payload bit for bit.
> >
> > Ability to compensate reordering of PW packets at egress is a side
> > effect of (a) sequence number usage and (b) usage of the de-jitter
> > buffer in the egress PW. It is not mandatory and in any case is
> > limited by the depth of the de-jitter buffer: re-ordered packets that
> > cannot be accommodated within this buffer are treated as lost.
> >
> > Additional details can be found, e.g., in section 6.2.2 of RFC
> > 4553<http://tools.ietf.org/html/rfc4553>. Ability to re-order
> > mis-ordered PW packets is defined there as OPTIONAL, while replacement
> > of the payload of lost PW packets is defined as MANDATORY.
> 
> The change below at the top of the section more accurately reflects
> requirements in the RFCs but still states that resequencing can be
> beneficial.  The comments about EPD and PPD are dropped and therefore
> also the informative reference.
> 
>  Context:
> 
>  2.1.8.1.  Pseudowire Sequence Number
> 
>  OLD
> 
>    Pseudowire (PW) sequence number support is most important for PW
>    payload types with a high expectation of in-order delivery.
>    Resequencing support, rather than dropping at egress on out of order
>    arrival, is most important for PW payload types with a high
>    expectation of lossless delivery.  For example, TDM payloads require
>    sequence number support and require resequencing support.  The same
>    is true of ATM CBR service.  ATM VBR or ABR may have somewhat relaxed
>    requirements, but generally require ATM Early Packet Discard (EPD) or
>    ATM Partial Packet Discard (PPD) [ATM-EPD-and-PPD].  Though sequence
>    number support and resequencing support are beneficial to PW packet
>    oriented payloads such as FR and Ethernet, they are highly desirable
>    but not as strongly required.
> 
> NEW
> 
>    Pseudowire (PW) sequence number support is most important for PW
>    payload types with a high expectation of lossless and/or in-order
>    delivery.  Identifying the position of any lost packets is important
>    for PW services which are attempting to reconstruct a bit stream
>    which maintains bit timing, such as time division multiplexing (TDM)
>    services.  TDM and other PW services which require strict ordering
>    also require that misordered packets be either dropped or reordered.
> 
>    PW services which are not timing critical bit streams in nature are
>    cell oriented or frame oriented.  Though resequencing support is
>    beneficial to PW cell and frame oriented payloads such as ATM, FR and
>    Ethernet, they are highly desirable but not required.
> 
> NEW (end of subsection after list of possible reording causes)
> 
>    In provider networks which use multipath techniques and which may
>    occassionally rebalance traffic or which may change PW paths
>    occasionally for other reasons, reordering may be far more common
>    than loss.  Where reordering is more common than loss, resequencing
>    packets is beneficial, rather than dropping packets at egress when
>    out of order arrival occus.  Resequencing is most important for PW
>    payload types with a high expectation of lossless delivery since in
>    such cases out of order delivery within the network results in PW
>    loss.
> 
> The final paragraph sums up the motivation for highlighting
> resequencing as beneficial and desirable.  It does so without any
> normative wording.
> 
> > Hopefully these notes will be useful.
> >
> > Regards,
> >      Sasha
> 
> These notes are very useful.  Thank you.
> 
> Please let us know if you (and the WG) are OK with the rewording
> proposed above.
> 
> Curtis


This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


From adam.zhang@huawei.com  Tue Nov 26 23:40:00 2013
Return-Path: <adam.zhang@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C8B41AE24A for <pwe3@ietfa.amsl.com>; Tue, 26 Nov 2013 23:40:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1_i5fzf8ulv for <pwe3@ietfa.amsl.com>; Tue, 26 Nov 2013 23:39:58 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id BED321AE243 for <pwe3@ietf.org>; Tue, 26 Nov 2013 23:39:57 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYJ02288; Wed, 27 Nov 2013 07:39:56 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 27 Nov 2013 07:39:22 +0000
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 27 Nov 2013 07:39:50 +0000
Received: from NKGEML503-MBS.china.huawei.com ([169.254.6.87]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Wed, 27 Nov 2013 15:39:38 +0800
From: "Zhangdasheng (Adam)" <adam.zhang@huawei.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: Feedback on "Any comments on the draft of STP Application of ICCP ?"
Thread-Index: Ac7qS4iJGhFx5FPkQD2klOdFbQtN3w==
Date: Wed, 27 Nov 2013 07:39:37 +0000
Message-ID: <37AEFF83F27FB94D91E00430E0EDB3B34FB1D246@nkgeml503-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.30.174]
Content-Type: multipart/alternative; boundary="_000_37AEFF83F27FB94D91E00430E0EDB3B34FB1D246nkgeml503mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "Yuyong \(YuYong, RouterPDU\)" <yuyong@huawei.com>, Jsnj fanbin <jsnj.fanbin@huawei.com>
Subject: [PWE3] Feedback on "Any comments on the draft of STP Application of ICCP ?"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 27 Nov 2013 07:40:01 -0000

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


When I read the draft, I find the draft makes the PE transmit the "STP Conf=
iguration Digest". I am not clear what its purpose is.

Adam.zhang


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	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-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=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">When I read th=
e draft, I find the draft makes the PE transmit the &#8220;STP Configuratio=
n Digest&#8221;. I am not clear what its purpose is.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Adam.zhang<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">&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;
</span><span lang=3D"EN-US"><o:p></o:p></span></p>
</div>
</body>
</html>

--_000_37AEFF83F27FB94D91E00430E0EDB3B34FB1D246nkgeml503mbschi_--

From wenhuafeng@huawei.com  Wed Nov 27 03:10:36 2013
Return-Path: <wenhuafeng@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 876361AE110 for <pwe3@ietfa.amsl.com>; Wed, 27 Nov 2013 03:10:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.749
X-Spam-Level: *
X-Spam-Status: No, score=1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4wutSoXfGoP8 for <pwe3@ietfa.amsl.com>; Wed, 27 Nov 2013 03:10:34 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 20E6E1AE2A7 for <pwe3@ietf.org>; Wed, 27 Nov 2013 03:07:22 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAT47572; Wed, 27 Nov 2013 11:07:22 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 27 Nov 2013 11:06:48 +0000
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 27 Nov 2013 11:07:16 +0000
Received: from NKGEML503-MBS.china.huawei.com ([169.254.6.87]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Wed, 27 Nov 2013 19:07:04 +0800
From: Wenhuafeng <wenhuafeng@huawei.com>
To: "Zhangdasheng (Adam)" <adam.zhang@huawei.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Feedback on "Any comments on the draft of STP Application of	ICCP ?"
Thread-Index: Ac7qS4iJGhFx5FPkQD2klOdFbQtN3wBFRD8i
Date: Wed, 27 Nov 2013 11:07:03 +0000
Message-ID: <B51493B1D374244F9572F031F74684294FDCCDFC@nkgeml503-mbs.china.huawei.com>
References: <37AEFF83F27FB94D91E00430E0EDB3B34FB1D246@nkgeml503-mbs.china.huawei.com>
In-Reply-To: <37AEFF83F27FB94D91E00430E0EDB3B34FB1D246@nkgeml503-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.30.158]
Content-Type: multipart/alternative; boundary="_000_B51493B1D374244F9572F031F74684294FDCCDFCnkgeml503mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "zengweizhi@huaewi.com" <zengweizhi@huaewi.com>
Subject: [PWE3] =?gb2312?b?tPC4tDogIEZlZWRiYWNrIG9uICJBbnkgY29tbWVudHMg?= =?gb2312?b?b24gdGhlIGRyYWZ0IG9mIFNUUCBBcHBsaWNhdGlvbiBvZglJQ0NQID8i?=
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 27 Nov 2013 11:10:36 -0000

--_000_B51493B1D374244F9572F031F74684294FDCCDFCnkgeml503mbschi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

VGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzLiBUaGUgUEUgY2FsY3VsYXRlcyB0aGUgVkxBTiB0byBp
bnN0YW5jZSBtYXBwaW5nIHVzaW5nIG1kNSBhbGdvcml0aG0gYW5kIGRlbGl2ZXIgdGhlIG1hcHBp
bmcgZGlnZXN0IHRvIHRoZSBwZWVyaW5nIFBFLiBUaGlzIG1hcHBpbmcgY2FuIGJlIHVzZWQgdG8g
ZmluZCB0aGUgbWlzLWNvbmZpZ3VyYXRpb24gb24gbWFwcGluZy4NCg0KVGhhbmtzDQpIdWFmZW5n
DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQq3orz+yMs6IHB3ZTMgW3B3ZTMt
Ym91bmNlc0BpZXRmLm9yZ10gtPqx7SBaaGFuZ2Rhc2hlbmcgKEFkYW0pIFthZGFtLnpoYW5nQGh1
YXdlaS5jb21dDQq3osvNyrG85DogMjAxM8TqMTHUwjI3yNUgMTU6MzkNCsrVvP7IyzogcHdlM0Bp
ZXRmLm9yZw0Ks63LzTogWXV5b25nIChZdVlvbmcsIFJvdXRlclBEVSk7IEpzbmogZmFuYmluDQrW
98ziOiBbUFdFM10gRmVlZGJhY2sgb24gIkFueSBjb21tZW50cyBvbiB0aGUgZHJhZnQgb2YgU1RQ
IEFwcGxpY2F0aW9uIG9mIElDQ1AgPyINCg0KDQpXaGVuIEkgcmVhZCB0aGUgZHJhZnQsIEkgZmlu
ZCB0aGUgZHJhZnQgbWFrZXMgdGhlIFBFIHRyYW5zbWl0IHRoZSChsFNUUCBDb25maWd1cmF0aW9u
IERpZ2VzdKGxLiBJIGFtIG5vdCBjbGVhciB3aGF0IGl0cyBwdXJwb3NlIGlzLg0KDQpBZGFtLnpo
YW5nDQoNCg==

--_000_B51493B1D374244F9572F031F74684294FDCCDFCnkgeml503mbschi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<style>=0A=
<!--=0A=
@font-face=0A=
	{font-family:SimSun}=0A=
@font-face=0A=
	{font-family:"Cambria Math"}=0A=
@font-face=0A=
	{font-family:Calibri}=0A=
@font-face=0A=
	{font-family:SimSun}=0A=
p.MsoNormal, li.MsoNormal, div.MsoNormal=0A=
	{margin:0cm;=0A=
	margin-bottom:.0001pt;=0A=
	text-align:justify;=0A=
	font-size:10.5pt;=0A=
	font-family:"Calibri","sans-serif"}=0A=
a:link, span.MsoHyperlink=0A=
	{color:blue;=0A=
	text-decoration:underline}=0A=
a:visited, span.MsoHyperlinkFollowed=0A=
	{color:purple;=0A=
	text-decoration:underline}=0A=
span.EmailStyle17=0A=
	{font-family:"Calibri","sans-serif";=0A=
	color:windowtext}=0A=
.MsoChpDefault=0A=
	{font-size:10.0pt}=0A=
@page WordSection1=0A=
	{margin:72.0pt 90.0pt 72.0pt 90.0pt}=0A=
-->=0A=
</style><style type=3D"text/css" id=3D"owaParaStyle"></style>
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"" fpstyle=3D"1=
" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">
<div>Thanks for your comments. The PE calculates the VLAN to instance mappi=
ng using md5 algorithm and deliver the mapping digest to the peering PE. Th=
is mapping can be used to find the mis-configuration on mapping.&nbsp;</div=
>
<div><br>
</div>
<div>Thanks</div>
<div>Huafeng</div>
<div><br>
</div>
<div style=3D"font-family: Times New Roman; color: #000000; font-size: 16px=
">
<hr tabindex=3D"-1">
<div id=3D"divRpF741637" style=3D"direction: ltr; "><font face=3D"Tahoma" s=
ize=3D"2" color=3D"#000000"><b>=B7=A2=BC=FE=C8=CB:</b> pwe3 [pwe3-bounces@i=
etf.org] =B4=FA=B1=ED Zhangdasheng (Adam) [adam.zhang@huawei.com]<br>
<b>=B7=A2=CB=CD=CA=B1=BC=E4:</b> 2013=C4=EA11=D4=C227=C8=D5 15:39<br>
<b>=CA=D5=BC=FE=C8=CB:</b> pwe3@ietf.org<br>
<b>=B3=AD=CB=CD:</b> Yuyong (YuYong, RouterPDU); Jsnj fanbin<br>
<b>=D6=F7=CC=E2:</b> [PWE3] Feedback on &quot;Any comments on the draft of =
STP Application of ICCP ?&quot;<br>
</font><br>
</div>
<div></div>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:black">When I read =
the draft, I find the draft makes the PE transmit the =A1=B0STP Configurati=
on Digest=A1=B1. I am not clear what its purpose is.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:black">Adam.zhang</=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:black">&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span lang=3D"EN-US"></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_B51493B1D374244F9572F031F74684294FDCCDFCnkgeml503mbschi_--

From wwwrun@rfc-editor.org  Wed Nov 27 12:12:24 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4812E1AE1D1; Wed, 27 Nov 2013 12:12:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bc3VqfrSZe7d; Wed, 27 Nov 2013 12:12:21 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 887651ADFC2; Wed, 27 Nov 2013 12:06:20 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 417E979E00B; Wed, 27 Nov 2013 12:06:10 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20131127200610.417E979E00B@rfc-editor.org>
Date: Wed, 27 Nov 2013 12:06:10 -0800 (PST)
Cc: drafts-update-ref@iana.org, pwe3@ietf.org, rfc-editor@rfc-editor.org
Subject: [PWE3] RFC 7079 on The Pseudowire (PW) and Virtual Circuit Connectivity Verification (VCCV) Implementation Survey Results
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 27 Nov 2013 20:12:24 -0000

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

        
        RFC 7079

        Title:      The Pseudowire (PW) and Virtual 
                    Circuit Connectivity Verification (VCCV) 
                    Implementation Survey Results 
        Author:     N. Del Regno, Ed.,
                    A. Malis, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       November 2013
        Mailbox:    nick.delregno@verizon.com, 
                    amalis@gmail.com
        Pages:      41
        Characters: 67854
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pwe3-vccv-impl-survey-results-03.txt

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

The IETF Pseudowire Emulation Edge-to-Edge (PWE3) working group has
defined many encapsulations of various layer 1 and layer 2 service-
specific PDUs and circuit data.  In most of these encapsulations, use
of the Pseudowire (PW) Control Word is required.  However, there are
several encapsulations for which the Control Word is optional, and
this optionality has been seen in practice to possibly introduce
interoperability concerns between multiple implementations of those
encapsulations.  This survey of the Pseudowire / Virtual Circuit
Connectivity Verification (VCCV) user community was conducted to
determine implementation trends and the possibility of always
mandating the Control Word.

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


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC



From internet-drafts@ietf.org  Thu Nov 28 00:16:01 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 277411AC7F0; Thu, 28 Nov 2013 00:16:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L_p6duDKwFNA; Thu, 28 Nov 2013 00:15:59 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E8031A1F08; Thu, 28 Nov 2013 00:15:59 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131128081559.27717.27300.idtracker@ietfa.amsl.com>
Date: Thu, 28 Nov 2013 00:15:59 -0800
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action: draft-ietf-pwe3-mpls-tp-pw-over-bidir-lsp-02.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 28 Nov 2013 08:16:01 -0000

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

	Title           : LDP extensions for Pseudowire Binding to LSP Tunnels
	Author(s)       : Mach(Guoyi) Chen
                          Wei Cao
                          Attila Takacs
                          Ping Pan
	Filename        : draft-ietf-pwe3-mpls-tp-pw-over-bidir-lsp-02.txt
	Pages           : 15
	Date            : 2013-11-28

Abstract:
   Many transport services require that user traffic, in the forms of
   Pseudowires (PW), to be delivered on a single co-routed bidirectional
   LSP or two LSPs that share the same routes.  In addition, the user
   traffic may traverse through multiple transport networks.

   This document specifies an optional extension in LDP that enable the
   binding between PWs and the underlying LSPs.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-pw-over-bidir-lsp

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-pw-over-bidir-lsp-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pwe3-mpls-tp-pw-over-bidir-ls=
p-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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

